Brocade Automation Community

Video: Brocade SDN Controller Postman Collection

  • 1.  Video: Brocade SDN Controller Postman Collection

    Posted 04-11-2015 03:52 PM

    This video describes how to obtain the Brocade SDN Controller Postman Collection and provides a brief walk-through of it so you can begin using it to send RESTful calls to the Brocade SDN Controller via the RESTCONF api.  

     

     

     

    Download Links:

    Related Articles:

    More Info Links:

    Video Transcript:

     

    00:00:00.700 --> 00:00:04.299
    tell aprox today wanna talk to you about
    the

    00:00:04.299 --> 00:00:08.189
    BBC postman collection you have
    installed postman

    00:00:08.189 --> 00:00:12.230
    and Google Chrome please go check out
    another video here we're gonna assume

    00:00:12.230 --> 00:00:13.460
    you've got it installed

    00:00:13.460 --> 00:00:18.300
    and that we're going to just focus on
    the BBC collection

    00:00:18.300 --> 00:00:22.150
    replace so if you're not familiar with
    postman postman consists of a set of

    00:00:22.150 --> 00:00:22.850
    calls

    00:00:22.850 --> 00:00:27.440
    so the press will cost you can make to a
    server a collection is just a grouping

    00:00:27.440 --> 00:00:28.210
    up those

    00:00:28.210 --> 00:00:31.380
    and then you can share those collections
    and that's what we're gonna do today

    00:00:31.380 --> 00:00:33.850
    we're gonna show you a collection that
    we're building

    00:00:33.850 --> 00:00:39.809
    that you can just import into your
    postman and begin to use to exercise PVC

    00:00:39.809 --> 00:00:43.580
    and I'm gonna show you how to install
    that now okay so the first thing to do

    00:00:43.580 --> 00:00:45.140
    is open postman so

    00:00:45.140 --> 00:00:48.840
    gonna click on post man over here in the
    right corner and they were in focus on

    00:00:48.840 --> 00:00:50.620
    the collections or click a tab

    00:00:50.620 --> 00:00:54.670
    and then you can import several
    different ways we're gonna focus on

    00:00:54.670 --> 00:00:57.790
    download from a link but we need the
    link so

    00:00:57.790 --> 00:01:01.290
    let me open my browser I'm gonna go to
    get herb dot com

    00:01:01.290 --> 00:01:05.590
    that i'm gonna do a search for BBC the
    very first one should be prepared by a

    00:01:05.590 --> 00:01:06.420
    controller gonna

    00:01:06.420 --> 00:01:10.290
    go there and they're gonna pick the wiki
    link and then we're gonna pick pages in

    00:01:10.290 --> 00:01:12.770
    the upper right corner and they were
    good progress comp tools

    00:01:12.770 --> 00:01:15.940
    rescue tools is where we're storing a
    bunch of tools and one of them is the

    00:01:15.940 --> 00:01:16.720
    postman click

    00:01:16.720 --> 00:01:19.950
    I'm picking the 1.2 oh I'm gonna grab
    the URL for that

    00:01:19.950 --> 00:01:22.969
    only the URL I'm just gonna paste the
    URL

    00:01:22.969 --> 00:01:26.219
    in there and see import and sure enough

    00:01:26.219 --> 00:01:29.950
    if you look over here we now have a
    collection okay

    00:01:29.950 --> 00:01:33.799
    so now let's actually set up our
    environment for this so if you're like

    00:01:33.799 --> 00:01:36.759
    me you're excited you've got a new
    collection you just gonna go ahead

    00:01:36.759 --> 00:01:41.360
    and try one out gonna open up one of
    these folders you gonna pick one of

    00:01:41.360 --> 00:01:42.960
    these calls you can hit send

    00:01:42.960 --> 00:01:46.289
    and you're going to get a big fat
    failure and say what that

    00:01:46.289 --> 00:01:49.859
    attack why's that and you're gonna look
    in your gonna see that

    00:01:49.859 --> 00:01:52.969
    oh what's this thing there's no IP
    address it's got some weird thing

    00:01:52.969 --> 00:01:56.250
    call the variable we need to set up and
    variable

    00:01:56.250 --> 00:01:59.560
    contains the IP address up the target
    PVC

    00:01:59.560 --> 00:02:03.770
    so we're gonna grab the name of that
    variable and copy it

    00:02:03.770 --> 00:02:07.350
    and then over here under environment
    we're gonna actually manage environments

    00:02:07.350 --> 00:02:08.560
    recruit a new environment

    00:02:08.560 --> 00:02:13.290
    call it PVC yeah I'm gonna call it BBC

    00:02:13.290 --> 00:02:16.850
    VirtualBox to differentiate it I'm gonna
    paste in the name of the variable that

    00:02:16.850 --> 00:02:17.440
    i'm gonna put

    00:02:17.440 --> 00:02:21.550
    the IP address of my BBC I'm gonna go
    ahead and save that

    00:02:21.550 --> 00:02:24.780
    and then over here I'm gonna select
    their and now

    00:02:24.780 --> 00:02:30.540
    when I check the details my clicks and
    it actually works

    00:02:30.540 --> 00:02:32.799
    okay so now you actually

    00:02:32.799 --> 00:02:36.629
    imported the up postman collection for
    BBC

    00:02:36.629 --> 00:02:41.120
    and you set up your environment variable
    work good to go

    00:02:41.120 --> 00:02:44.730
    so our postman collection is organized
    into folders that group

    00:02:44.730 --> 00:02:50.060
    arm restful calls that are similar
    together so here's one for

    00:02:50.060 --> 00:02:54.180
    topology in with you see we have a
    get-tough policy each one of these

    00:02:54.180 --> 00:02:57.879
    actually has a description there arm but
    describes it

    00:02:57.879 --> 00:03:02.019
    and then you can click Send and you will
    actually see the results from this

    00:03:02.019 --> 00:03:05.690
    assuming you've got your environment
    variable set to point to your BBC

    00:03:05.690 --> 00:03:09.450
    let's look at another folder here
    control controller flow programming

    00:03:09.450 --> 00:03:13.239
    um you can see that the first call
    allows us to at a flow

    00:03:13.239 --> 00:03:16.799
    it also indicates what you would need to
    change if you need to change anything so

    00:03:16.799 --> 00:03:19.090
    right there on the URL you'd have to
    change

    00:03:19.090 --> 00:03:23.930
    the table if you wanted to quicksand and
    says oh there's a two hundred okay

    00:03:23.930 --> 00:03:27.510
    so we have successfully created that
    flow um

    00:03:27.510 --> 00:03:32.290
    so let's go down too and there's a get
    flows from specific table if we click

    00:03:32.290 --> 00:03:32.769
    that

    00:03:32.769 --> 00:03:36.700
    you can see ok there's the flow that we
    just created so we can validate that we

    00:03:36.700 --> 00:03:41.870
    just did in fact create that flow on our
    BBC here's our man inventory so you can

    00:03:41.870 --> 00:03:43.790
    do it get configured inventory

    00:03:43.790 --> 00:03:47.590
    describes what this will do arm

    00:03:47.590 --> 00:03:51.910
    you can go ahead after you read go ahead
    and click send

    00:03:51.910 --> 00:03:56.069
    and see the results and sure enough
    there's your inventory

    00:03:56.069 --> 00:03:59.359
    you can see that earlier I'd configured
    a couple the rotors

    00:03:59.359 --> 00:04:02.660
    arm and then there's the OpenFlow our

    00:04:02.660 --> 00:04:06.810
    be the OpenFlow switch which is a
    minutes which I've got connected here

    00:04:06.810 --> 00:04:10.010
    you can do get in operational inventory
    so

    00:04:10.010 --> 00:04:14.030
    remember there's a configured database
    in a operational configures what you've

    00:04:14.030 --> 00:04:17.489
    told it the operational is what it
    actually has detected

    00:04:17.489 --> 00:04:21.440
    so we can go ahead and that move on

    00:04:21.440 --> 00:04:24.720
    armed and next one

    00:04:24.720 --> 00:04:29.440
    there's a bunch of other folders here
    that you can check out so here's arm

    00:04:29.440 --> 00:04:33.380
    Traore operations are sees I am you can
    see

    00:04:33.380 --> 00:04:36.919
    if we poke around in here we see
    punching gets arm

    00:04:36.919 --> 00:04:40.220
    here's one for net comp devices you'll
    see a bunch of posts you'll also see

    00:04:40.220 --> 00:04:41.970
    post that begin with RPC

    00:04:41.970 --> 00:04:45.580
    and may indicate unimplemented um those
    indicated

    00:04:45.580 --> 00:04:49.260
    they are real but currently they are not
    yet implemented

    00:04:49.260 --> 00:04:51.490
    an open daylight are more

    00:04:51.490 --> 00:04:55.190
    BC um they will be in the future
    probably so

    00:04:55.190 --> 00:04:59.009
    we put them in here to let you know
    these do exist and you can see

    00:04:59.009 --> 00:05:02.139
    they actually return intelligent message
    which is

    00:05:02.139 --> 00:05:07.610
    that operations not yet supported supped
    you've got the collection what next

    00:05:07.610 --> 00:05:11.960
    well what next year's just keep an eye
    out we're constantly updating this

    00:05:11.960 --> 00:05:15.120
    collection and you want to be able to
    upgrade it that's a simple

    00:05:15.120 --> 00:05:18.220
    job deletion and just three importing

    00:05:18.220 --> 00:05:20.349
    and you'll get the latest and greatest


    #BrocadeAutomationCommunity