Hi Fuqiao: This is indeed a big issue that every deployment has and it is great that you have tools to automate this configuration.
I don’t know about Airship so cannot comment on how Airship handles the wiring to the TORs. Best is to have the Airship team drive this with the lab infra team. I will just assume for now that Airship installs either a flat VLAN network or a tenant VLAN network (would be good for the Airship team to confirm). Lincoln: I think having a basic TOR interface configuration programming interface (VLAN and basic admin config) should be sufficient for automating the installation of software components/tools in this context. We’ve had good success using the packet.net REST interface to configure the switch for automating the deployment of NFVbench on packet.net infra – this to handle the wiring to the traffic generator side. For wiring config to the openstack servers side, it is a different and harder problem because there are many more parameters to take into account and the manual wiring itself cannot be automated obviously. All I ask on my side is that the traffic gen facing side of the TOR(s) is defined properly to facilitate the automated deployment of NFVbench. What I would expect in any HW definition file is the description of which 2 TOR interfaces are wired to the traffic generator (interface names) and the VLAN range used for the tenant traffic. With these 2 information + proper REST API , it is possible to write automation to configure the TOR interfaces properly (we obviously also need physical wiring between these 2 interfaces and the 2 NIC ports dedicated for traffic gen). Thanks Alec From: Lincoln Lavoie <lylav...@iol.unh.edu> Date: Thursday, November 14, 2019 at 6:03 PM To: "cntt-ref-...@lists.opnfv.org" <cntt-ref-...@lists.opnfv.org> Cc: "Alec Hothan (ahothan)" <ahot...@cisco.com>, "Rao, Sridhar" <sridhar....@spirent.com>, opnfv-tech-discuss <opnfv-tech-discuss@lists.opnfv.org>, Parker Berberian <pberber...@iol.unh.edu> Subject: Re: [cntt-ref-imp] [opnfv-tech-discuss] RI Lab Infra. Discussion I'm curious what the expectations are on configuration for the TOR. The LaaS project does and some basic provisioning for the switching fabric to support the VLAN scenario. It likely could be augmented to support other methods too, but it depends on the capabilities of the hardware. LaaS won't help with production deployments, but is a solution for dealing with lab setup, etc. In terms installer configuration of the network, I'm curious if the right approach is to handle the configuration of the network / fabric, which by definition brings in all the differences between vendors and management techniques for the switches, etc. Or, if it would make more sense to focus on validation of the network setup as part of the install. For example, if the installer consumes a topology description of the network / fabric, it would seem reasonable it could very quickly check reality against that topology, and for example flag Server N, Port 2 and Port 3 as "incorrect", which could likely mean they are flipped in wiring. Or it could check for basic layer 2 connectivity between ports in the case of VLANs, etc. Cheers, Lincoln On Thu, Nov 14, 2019 at 8:30 PM fuqiao <fuq...@chinamobile.com<mailto:fuq...@chinamobile.com>> wrote: Hi， Alec. Also cc the CNTT RI WS. What you mentioned is very important. Within China Mobile, we are developing our own tools to automaticlly configure the TOR accross different vendors. I have to say this is a hard work since the TOR from different vendors varies a lot. But it really worth the time as what you point out, this is the main area where human errors accor. For CNTT and OPNFV, currently the only active installer is airship. So I guess we will rely on that. Sridhar and the rest of the team is now trying the ariship installer out in POD 10. We are also trying to evolve the installer discription file to include network info, and as you said define HW configuration. You can see the attached PR for more details about this. https://github.com/cntt-n/CNTT/pull/535 ________________________________ 中国移动研究院 网络与IT技术研究所 付乔 15901025951 From: Alec via Lists.Opnfv.Org<mailto:ahothan=cisco....@lists.opnfv.org> Date: 2019-11-14 23:58 To: Rao, Sridhar<mailto:sridhar....@spirent.com> CC: opnfv-tech-discuss<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] RI Lab Infra. Discussion Hi Sridhar [+tech discuss list] From my knowledge, very few NFVi installers know how to configure the TOR(s) and instead just assume that some admin will go and configure the TORs in a way that is compatible with the installer’s own networking blueprint – this is one of the main areas were human errors occur during installation as there can be hundreds of cables to wire manually and as many ports to configure on the TORs. I know at least one (commercial) that does it but it only supports very specific model of TOR and very specific encaps/overlays. My comment to engage the installer team was more related to the wiring design between TOR(s) and servers that make up an openstack platform, which are of predominant importance when it comes to HW configuration. Any openstack installer will have to create a networking blueprint that will dictate how many TORs and how many physical interfaces are needed and what kind of traffic each will carry. Even with simpler VLAN deployment, there are multiple openstack networks to map on physical interfaces and/or VLANs with possibility of VLAN trunking and HA. It is clearly recommended to define the RI HW configuration with proper consultation with the installer team (this includes storage configuration as well as I mentioned in the wiki). As I did not follow on CNTT meetings, I’m not sure which OPNFV team is in charge of installing openstack on the RI and what kind of installer it is. Thanks Alec From: "Rao, Sridhar" <sridhar....@spirent.com<mailto:sridhar....@spirent.com>> Date: Wednesday, November 13, 2019 at 6:51 PM To: "Alec Hothan (ahothan)" <ahot...@cisco.com<mailto:ahot...@cisco.com>> Subject: RI Lab Infra. Discussion Hello Alec, I was reading your points in https://wiki.opnfv.org/display/INF/CNTT+RI+Lab+Infrastructure+Discussion I fully agree with importance of TOR configurations – may I say, underlay network configuration. You mention in multiple places, that this should be done by Installers. Can you please point me to an installer that can do this today. It would be very helpful. Today, in Intel Pods – the underlay network (the type of networks, the IP plan, VLANs and switch configuration) -Ex: Pod 10 (https://wiki.opnfv.org/display/pharos/Intel+POD10) – is setup by Intel team itself. Installer comes into picture only after this is set. I have not seen any installers which can also perform thoses step that Intel team is doing. Cheers, Sridhar _._,_._,_ ________________________________ Links: You receive all messages sent to this group. View/Reply Online (#13)<https://lists.opnfv.org/g/cntt-ref-imp/message/13> | Reply To Group<mailto:cntt-ref-...@lists.opnfv.org?subject=Re:%20Re%3A%20%5Bcntt-ref-imp%5D%20%5Bopnfv-tech-discuss%5D%20RI%20Lab%20Infra.%20Discussion> | Reply To Sender<mailto:fuq...@chinamobile.com?subject=Private:%20Re:%20Re%3A%20%5Bcntt-ref-imp%5D%20%5Bopnfv-tech-discuss%5D%20RI%20Lab%20Infra.%20Discussion> | Mute This Topic<https://lists.opnfv.org/mt/58461608/923460> | New Topic<https://lists.opnfv.org/g/cntt-ref-imp/post> Your Subscription<https://lists.opnfv.org/g/cntt-ref-imp/editsub/923460> | Contact Group Owner<mailto:cntt-ref-imp+ow...@lists.opnfv.org> | Unsubscribe<https://lists.opnfv.org/g/cntt-ref-imp/leave/4657366/2058813752/xyzzy> [lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>] _._,_._,_ -- Lincoln Lavoie Senior Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu> https://www.iol.unh.edu +1-603-674-2755 (m) [http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://www.iol.unh.edu/>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#23723): https://lists.opnfv.org/g/opnfv-tech-discuss/message/23723 Mute This Topic: https://lists.opnfv.org/mt/58495853/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
