Using the OSM User Interface & VNF On-boarding

hi folks my name is Noel Seurat I'm from ruff Dario I'm today here presenting OSM today morning francisco and adrienne and and even through some of the reasonings behind or some and some of the key capabilities in our one so the part that i'll be showcasing today will be related to package creation in this case specifically vnf MSD package creation and and some of the UI architecture so i'll show you some screenshots my plan was to actually see if I could show you an actual demo or foreign boarding but the resolution doesn't seem to be aligning with the projector here so I'm gonna skip that well definitely interesting I would walk you through it and and the process that that's required so the first section will focus on here sorry the first section will focus on onboarding of a vnf package so Francis Corley and and Adrienne D both connect touched on one of the process being onboarding of via naps and you know Francisco here some pictures of building blocks with Legos and stuff like that but you know so what I'll go through with over some is the process to do it so there are there are a couple of ways to do that Francisco just went through installation of or some are one here so I'll go through the creation of packages in and order the three ways that is related to it now what is packages so package is what you create to onboard a given V enough or a network service in this case so when you when you take a package you know we we talk about vnf do V enough descriptor files but this profile by itself is not enough if you think about it a the vnf there's an image for the V enough you know maybe there's some icons maybe there's some scripts that only you need to run pre and post instantiation of the vnf so a package you know contains lot of those in mission so in I'll go through a couple of slides I'll show you the actual contents of a package and and what is mandatory in words not mandatory per se but descriptor is one of the key mandatory items so I'll show you that part package also helps you to to provide an interface for you know one stop one click on boarding there's the the given package for awesome there are some mandatory structures identified and I'll show you the structure in the next slide so the the first package is the V&F package the vnf package contains it's at our Lord Jesus I'll once the package created becomes at our GC file and the tar.gz file is used to upload or on board but the package contains a checksum file the second fathers really used to make sure the you know diff given file has not been tampered with right is really for the security part of it there's a readme which is three not mandatory there's a descriptor file which is in Yama format that particular file is mandatory obviously and we'll go through the descriptor contents a little bit here in a second then there are charms I think right after my session mark we'll be talking about some of his favorite topics there are chlorine scripts that you can add to it this will help when you're onboarding or instantiate in the given VM for avi enough in the cloud any function that needs to be run icons if you want to display your given vnf D with a specific icon on the composer the icon buttons are their images specifically refer to the actual vnf image you do have two choices either you can embed the image with the package which probably will make the package pretty big or you can give the the path to where the package can be downloaded in most of the cases the room would already have the image and the idea is that you give the path or the name of the image in here and then scripts the idea here is not slightly different from clouding apart if there are day zero day one configuration scripts are required for you to run with this particularly enough whether it's you know maybe base configuration once we notice up and running those can be added here as well similarly for the network service NSD there's a very similar package and you can see the contents are almost identical the and the NS NS d ml file is important acid can relate it correlates the entire networking service so it includes all the energies of vlds components to create that particular service as well so the the one one difference that you will see from the previous package here is the NS conflict component and I'll kind of show you how to onboard these you know in the next couple of slides so let me just capture again as part of the onboarding process for using the assembly software release 1 here there are two key packages there is a VN FD u descriptor package and NS d descriptor package alright so there are three ways to onboard um or create a package and get them onboard you can use a verb based a utility form you know one of the idea here was that the operators can simply give access to a verb base form to their vendors or vienna vendors and let them log in and be able to create a basic VN FD descriptor package that they can then play with so there was a simple idea so we have created a very simple form or web-based form that you can access and create a very basic VN FD a package from there a second second part is a CLI to the CLI tool once you install or some release one you have access to all this parts you know you have to update the descriptor utility there but you get access to creating a package from CLI and then the third part is to use the you come the UI itself alright so the first you know the first metrology to use is of a base package generator the link is given on the top but end of the day the idea here is we will actually create a link under Etsy portal itself you are welcome to play with it and be able to create basic VN FD packages the information requester is also very minimal you know typically how to give it a name the V CPU memory heart discount where the image is gonna be stored and it gives you the ability to create a package so it just generates a very very basic package for a very basic V enough so it's extremely useful you know as I mentioned earlier a given package is a or GC file so it is a compressed file with specific checksum information in it and specific profiles in it but this actually helped the web-based utility actually helps you to get a very basic VN FD going on and then you can edit it you know make a lot of modifications to to take it to the next level the obviously that's the pros the corn here is that it only supports very basic V enough so very basic information within that Francis Corley talked about supporting an even Adrienne also mention the same thing supporting EP attributes and a bunch of other things they're all you won't see them here but what you get is a package creator you can then edit them to add bunch of those information in it but at least you get you get started alright so the second process is to use the CLI base utility that's there and some of the documentation that I think Adrienne showed earlier francisco showed earlier there was a kind of printed outside there's a PDF available on the website too on the Etsy website has some of information related to how to go about this process alright so this is part of our one you can use the basic package that you created based on the web that I showed earlier when in this case you can also generate the NSD as previously was just to be enough tea that you create from the web based form but now you can also create NSD with this the use case here is again you have a little bit more flexibility now with the web based form is very basic stuff for you it there's not much it that you can do per se but with the CLI base tool you're able to add the icons you're able to you know add the scripts you're able to add the image information you're able to edit the llamó file and add more information into the description and then get the ENFJ or the NSD creator so there are definitely more advantages and uses to this particular methodology the install process is given here I wasn't going to take you through the install process per se but I was going to show you actual generation of our utility if my laptop was able to be working here but all I do have screenshots so I'll go to the screenshots for the time being if anyone is interested to see this actually in action I'll be available here or I'll be in one of our boots here either on the FC butureanu fly boot so definitely stop by anytime and I'll actually take you through with the real process itself but once you install the descriptor package then you get access to the script collagen rate for descriptor package script you go in there and you can obviously do - help to get some information related to what are the actual commands so I know this is hard to read so let me just click on to the next one this specific CLI gives you information related to the options for this particular script I do have a laser alright so the one thing that you see here - - NST by default if you don't select - - NSD you get AV NFD descriptor package created but if you do enable - - NSD then it also creates an NST package along with it the idea is that you again create a very basic descriptor you give a V CPU information on a memory storage the image in this case the part of the image and where you want to store this particular descriptor file or where you want to get this descriptor file creator once that is created you know you can go there and edit it and do a lot more changes and then follow the same process okay so here's an actual example of this of this particular command being used AC is to actually get the get the drugs created NSD to make sure the NSD file is created as well in this particular example we're using four v cpu two gig memory 220 gig storage and we have an image file name with the directory over the images and the tree where you want to get the get this specific package creator so it's it might be pretty hard to see here but in the example that you see here is that the package has been created that's the first line here and I'm actually going into that directory and editing the descriptor file that inside that particular directory where the package core created so if I look at the if I look at the descriptor file that just got created it has some other basic information that you can see you're given and you can see the the VM flavor information given here some of the image file name the image name itself given here etc and the idea is that you should be able to edit this particular Yama file and update it with a lot more information if you want to have a you know proper discover here for a given v n of T all right so the next part here is it shows once you have made modifications to the given Yama file with more updates then you want to regenerate that particular package so that the checksum files updated the entire directory structure is updated I mentioned earlier that some of the components of the package are the icons the scripts that you do the charms all those things are not created by default once you create this directory then you have to follow the process again to manually put the icons manually put the scripts all that kind of stuff once that process is done you can run the generate script package command again with - T and this will recompile and recreate the package for you and in this case book you'll have to do it twice one for the VFD package and one for the package so at this point you actually have an ENFP package that has more information than just the VM flavor information it has this curves it has the icons it has the Judah charms required etc alright this shows the actual output of the package that gets created with this particular script you can see some of the directories that are embedded within that particular tar or GC file basically it has the same structure I showed earlier you see the image to create the script directory the icons etc all of them here but you get a proper package that's created but you can use it at that point all right so you know from a usability standpoint it's a again pretty easy and simple to create basic via Neffs but it does more than the base utility it now allows you to edit and update some of the key things record in terms of icons in terms of scripts in terms of charms all that kind of stuff can be added in so it gives you that particular support model and it's easy to use the template is pretty basics pretty easy to use now in terms of creating a complicated VN FD it's still not the best option because this requires you do learn all the battery you know the syntax and semantics and attributes to get a complicated we kind of created on our llamo so for that we'll go to the next next process alright this takes us to the third method to creating a package this is using the composer the UI component of it and when you log in to once you've installed over some r1 you connect to your to the UI and you log in with your credentials you know you get all this specific menus on top you click on catalog catalog will take you to the composer screen the composer screen on the left side are there a bunch of icons these help if you already have created package in your directory or view at archived or if you have a precompiled pre-created package you can use some of these icons to upload from the UI directly or you have a way to create brand new ones by clicking on the plus button you can create a brand new VN FD create a brand new NST and once you've created it you will see in one of these tabs whether it's a VFD you'll come up here or if it's an ST you will come under the NSD tab as well and you know you will see the middle portion is where it's kind of the the service composer part where you can actually compose from a graphical standpoint the actual winner of deep arts so at the top you have the VN of the construct name then you have each of the kind of icons representing a video or in this case of vm so if you have a multi vm v enough you know this allows you to create a mock through multi vm v ni v NF d for given V enough you can see some of the templates on top here if you want to add a video or a if the given beginner for course will say 3 to 4 or 5 VMs then you click on add video will pop up a similar icon here you enter the information related to the VM flavor and they're a bunch of other information as well it's not just the VM flavoring for itself but EPA information you know some of the other things that you will see coming up some of the script information they all can be populated on the on the form that can it becomes acting on the right side so depending upon which component that you select the form kind of changes to show the specific attributes that's pertaining to that particular component but again the idea is that you you're able to do virtual links internal virtual links videos and you can see you know they're a bunch of these are all templates are kind of created so that you can drag and drop and and create some basic be enough tea packages here once you have created the overall package you edit all the information required for the VFD you can click on onboard to save that particularly in FD so at that point you actually have saved we enough d here you're able to export them I you want to store it on your laptop you're able to export them out etc and you're also able to click on the ml viewer if you want to verify the entire llaman format has been created based on what you did on the composer part alright so from a compulsive standpoint it's um it's very easy to use it and it's not just for you know simple v enough you can actually create a proper complicated VN FD in this case the one of the one of the negative part that's not supported yet hopefully in the next release will be is the actual true package creation part so this creates a proper VN FD but the creation and storing of the icons and scripts are not supported from the UI directly right now but that's coming in for that particular party you will again have to go back and go to generate of the of the package from the CLI so so there are some good things but there so some you know items that are sold missing or some gaps I would say that probably hopefully you know Adrienne and and the whole the end user advisory group will work together to get it moving it's probably have we'll leave it at that ok so so far what we have done is talk about creating of vnf d or NS d package but that by itself you know the job is not done now you have to onboard the package onto either the UI it's before you do any actual instantiation of the network service you obviously want to onboard them so we'll go through some of the steps to get there as well again onboarding of the package can be done by a CLI or it can be done by I'm at the UI as well so we'll go through both this process record lis in order to get the the top part that shows here to get the ISO code it shows you how to get these some of the components of the awesome release one installed once you have that installed you do get a script to onboard the given package if you have the full or some r1 installed the directory kind of changes a little bit but it's the same script that you will be able to access on boarding a package here purely means that you're able then completely on board down to the composer and so that it's the final step before you want to instantiate a given package so in this case using the script you're able to give give the IP address of the launch pad earlier I showed you the composer view the graphical interface it's also called launch pad so you can give the IP address of that specific launch pad you can give the name of the package and then if you have multiple packages to onboard we can you know tag them together and have multiple packages on board at the same time by repeating - you and they get all onboard onto the UI so if you go back to the UI on the launch pad you will actually see them completely onboard there if it was empty before you now see all the packages being there we didn't we didn't touch base on rust interface earlier there was a question to later kinetic enforcement confirmed be supported at some point I think it didn't respond to that part but all the things that you see here on the UI they're all support from a rusty API perspective as well everything that you see URL can be done to rest interface hersa hurt sonic some actual example of a package onboarding given here so in this case it's running the script giving the IP address off in the launch pad the package name and you know the package were it's going to be clear and and the package the second packet the two packets here the vnf D and the NSD though would get on board all right once you run the scripts you will get a succeeded message basically you will see a succeed message for each of the package that gets on board I was gonna see if I could show you the this in live action but since honorable to connect our won't be able to show it I will be here afterwards if anyone wants to go through this whole process in but using it real you know are when I install I have it on my laptop I can actually show it to you take you through this process so once you have done the onboarding before you do that typically this would be empty this hole what would be empty but once you run the script command what you will see here is you will see this particular vnf D being shown here as being on board on the come on di launch pad so once it someone bought it then you can trigger the instantiation of it so now you start the overall process of you know the lifecycle management piece or instance the instantiation of the network service piece again to instantiate there are two ways to do it you can do it through CLI and so there is a command given here and now this one you know the preferred method is to use the UI itself why there's a couple of information that if you really want to do CLI based instantiation you need to get the NS the ID which means you need to open up the the NSC descriptor file get the ID and then you know run this particular command here the data center refers to the actual RO in this case it's opened them connectivity so we're not going through the actual install an integration process of the r1 at least not in my session but when you go through the axle UI one of the things that you will have to do is to configure the open VM trade NGOs or you know the RO open manner or credentials or the Dro current chills and and at that point it will I did identify that as a data center name so that you know kind of completes the just the package creation and onboarding of the of the tools itself I'll take you through some of the UI changes that we did for r1 they'll be next you know release one just got released what last week and you know as Francisco mentioned and Aiden mentioned they were ahead of time so which is great so I'll take you through some of the changes between r0 and r1 so you know one of the biggest change was the whole pluggable architecture based on plugins so many of the key components like account management catalog management lifecycle management they're all Critias plugins in r1 so the key changes here from a framework standpoint you know previously unreleased zero we do have REST API support WebSockets you iack cetera but they're all in different ports so several ports to get each of those components you know head and and used that has been completely changed to cut down that connector and complexity into two specific ports that's one of the big changes we've also added support for WebSockets and secure web sockets in release one and the APS have been more introspective plugins so this this particular part is kind of important even though it's a small statement here it's kind of important because all the plug-in architecture that's required for our one in its taking shape in in the released one rather and what it wasn't really zero all right so we had total of four plugins in release zero that you see here on the left side in release one that has been updated to about seven there these are some when used so the UI and Emily I'll show you some more screenshots coming up on the table you will see bunch of menus and some of the menus that you see now or account config and logging but they're all plugins the idea was that you know you can keep adding plugins and and I'm sure it in in Francisco invited in where other folks to start contributing if you're willing to contribute and add plugins right over the rosin Sdn plug-in whatnot but end of the day you know r1 has seven plugins and this has three key plugins were added with this one the other thing that was added was that test framework so previously we didn't have any test framework on release the robot release one allows you to run a framework where it you can you can test these server-side modules so besides plugins are a bunch of modules that that constitute the entire our entire UI so you do have the ability to run a test framework and test out the module so that when you make changes you're able to test it and kind of get a feedback right away so they're about for several component test cases have been added double run or when you're under test framework the other part is the configuration options through REST API you know something that wasn't there previously the whole configuration option through recipe was not supported it was through the UI directly but now you actually have ability to do REST API based calls to do that alright from a UI perspective the plugins I was talking about at least access to the plugins or some of the menu said you saw on the top but one of the key things was the ammo or display and I think it reinvent through this a little bit as well we can we can take in this profiles in different formats so we can consume a descriptor file in XML format in yeah Mille or JSON but when we just display the actual file format will be in IMO and you will see something similar so you see a multi v-a about three v NS here with multiple virtual link descriptors and you know a corresponding corresponding ml file here another change was done in release the release one earlier in release here or some of the way these icons or the constructs were shown can a causal bit of confusion so some additional information has been added you will see a bar on top that showcases was the vnf d or an NS d to differentiate between an NS d and a v NF d the the color combination relation to v NF VD u VL d or different colors used to now identify those as well as the icon type right so you know three three key changes are done in release one to make sure you are able to differentiate between a v NF v NS d VN FB or a VL d when you do editing of this each kind of components you don't want to be confused with each with either her see an example of the test framework being run another change there was done for release one in in one of the UI once the service is up and running there is this concept of service primitives so you're able to run scripts for service instantiation and when you run those scrubs you know you used to get some kind of status but not really much information in our zero so in our one bunch more information has been added now you get time stamp on on you know how much time has been gone since the the particular job has been instantiated or started you also get some of the parameters obviously you know you want this just an example for passwords typed in but you will get the parameters over run through the particular script so you can identify actually what what script was from what it was for etc and if there is an error then you can get some earth status as well in detail why that particular job or a doubt there's also two buttons here that you see is red they typically turn green if the job is successful alright another component added we in release zero there was support for logging but it wasn't supporting any kind of filter metrology it wasn't supporting any any ways to kind of point to a specific log viewer etc so what was done in ours are one now you do have the capability to filter out the logs are coming in and then you're able to get it displayed on a given analyzer in this case you see a logger and I serve as an example but the idea is that you should be able to use any any log viewer that you want to point you and be able to get it displayed but this whole plugin component was added in release one alright moving forward some of the other components in the UI now once you instantiate the service there are a couple of other components were added or not they're in our zero virtual links so previously we never displayed virtual link information you will see the virtual links in the composer you will see the virtual links in the catalog and you can see what they are right before instantiation but now we are showing the the virtual links once they are once the service is deployed and you see some of the information later cuz the virtual links on the right side as well now outside of that there's one more capability added previously it was almost it was impossible to do any changes to a running service but now you can actually create a virtual link on a running service so this allows you to create an external virtual link on a running service that particular capability has been added as well on release one and you can you can click on create virtual link add the information related to that particular virtual link and in this case it could be an existing network information is already pretty clear now in in your Graham you can in a point to that and get that created all right besides that on the instantiation part previously we had one page to do the instantiation where you select the NSD the res on bordered you kind of verify what's part of the key components of that particular descriptor file and then you can instantiate now you see bunch more functionalities in there one of the key things that both adrian francisco talked about earlier was support for multi them support for multi-site etc so now when you do the instantiation you are you have the capability to select where each of the given be enough has to be placed so when you create a network service via said you it a services formed based on you know multiple we announce coming together forming a use case that becomes a network service so if you have a multi vnf network service and you want to have those v NS launched maybe one of them in one specific whim another warning that the complete different way maybe if it's all the same type may be a different type but you now have the capability to select on a Purvi enough basis where you want to launch that particular V enough so you know you can actually create a network service that's launched across multiple beside you also get additional information that you can input specifically IP parameters for the virtual links while instantiation so these are all information that you can add during the instant or right before the instantiation time another thing previously in released 0u if you need to go and look at the actual console of a given VM it there wasn't an easy step to go directly from the UI or Launchpad we have added additional information there are multiple ways to get to it you are able to now go directly into the VM console of a given vnf once it's launched so you can go it through viewport which is looking at the actual launch instance or you can go it outside of the report and connect to the connect to the VM console another another feature created in release one support for SSH key pairs you may have seen if you manually try to launch a given V and now for a VM for a be enough there are options to do you know creators SSH key or error message key pair for it you have the capability now to create a new key and get it aired as part of the given VM so that particular component has been added in this particular release phone as well I talked about this briefly earlier but this kind of shows the capability to run VN else across or multiple vnfs across multiple controls or multiple rooms so you know the key feature here talk about multi unit row in a multi-site network service okay in release 0 the configuration from an account perspective was very different differently managed in different layouts and stuff like that so at least one we have taken a complete different approach we can see open mono as a complete different component interconnect or Auto config components so now you're able to distinguish between you know on our config versus a rim specific conflict so that part has been added and you're able to get that information updated here as well also added as part of release one when you go to the instantiation page previously you would see a small information related to the descriptor file but purely focused on the image flavor or the VM flavor and EPA if any PS were enabled but now you also get details related to the vlds or part of the component you know the networking constructs or anything else that is part of that particular descriptor file address form this shows some of the some of the information related to you go back quickly so in the previous page the overall workflow for instantiation has been broken down into two parts now previously was just one screen you just look at it and instantiate directly now you are able to click on next and which takes you to the next page and now you go through the actual information related to the instantiation parameters this is where you can provide maybe IP address if you have four specific virtual link or the the via more specific in a side where you want to launch smoothly enough so you can select all those on the next screen and then you get it launched so those are kind of my set of slides but my focus was purely showing you the process to create packages process to onboard packages and some of the key changes in are one that just got released last week so let me stop there and see if there any near questions yes [Music] that's the idea so there it is that you know you so his question is can you can you manage multiple instance of controllers of OpenStack per se I mean that's that's really the idea right and one of the demos were during MWC was to showcase three controllers with you know services launched but in that case it was three separate services launched now the functionality is that you're able to launch one service across multiple controllers or multiple sites correct so you're talking about the van orchestration between the sides so this doesn't involve an orchestration between the sites per said the assumption is that there is connectivity and the vinyl coaster is already done between the controllers francisco´s or anything else that you want to add to that yeah essentially that is is that your the duration is that the new underlying condition are not created on the fly you assume that there are some montalais conditions already available and then you you can play with either the the routing rules or or using them as a layer two connections could you elaborate a little bit on the logging capability and what your plans are to elaborate that yeah so they're a bunch of logs available right now from my UI perspective that gets you know spewed out into a specific file while the service is running those logs can be you know ported out and be viewed through any kind of external losses log viewer you know right and the capability that you have right now is to be able to filter the specific message that you want to see in terms whether it's criticality or you know what kind of process within it and just look at that particular part anything beyond that has to be coming up in next releases which I don't think the content of released to has been fully baked yet but what do you see what you get today is all the all the loss that you get that it gets you know that gets to either send a syslog and whatnot can also be viewed directly on the UI and in order to view that there is there's a there's a log analyzer package that is when you install awesome our one log analyzer also gets installed now and when you click on the school button basically what you have selected here to be displayed gets displayed in that log analyzer package you know on the on the next page any other questions all right thank you [Applause]

Channel: Open Source MANO

Views: 1,993

Rating: 5 out of 5

Keywords: OSM, Open Source MANO, VNF, Onboarding, SDN, Layer123, ETSI

Id: Cv3axZBwF7M

Length: 40min 44sec (2444 seconds)

Published: Mon Nov 21 2016