Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2
Hello to all. I just created a document called neutron-ml2-mech-vmware-dvswitch.rst on a git repo clone from neutron-specs as instructed. My problem is, I just cannot submit my Contributor Agreement. I've tried Google Chrome and Firefox to no avail. The error message is always: *** Code Review - Error Server Error Cannot store contact information button: Continue *** Sigh, I even tried Opera. I get always the same error message. I cannot proceed from here. Can anybody help me out? My username/email is sjm at cybercom.fi and my realname contains one non-7bit-ascii character, if it does matter. Other than that, I don't see anything odd here. BR, Sami J. Mäkinen from Cybercom Finland On 06/05/14 20:05, Armando M. wrote: Hi Ilkka, As Mathieu suggested there is a blueprint submission and revision process put in place since the Juno release. Also, since Icehouse, to incorporate a new plugin/mechanism driver into the Neutron source tree, and to be designated as compatible, such a plugin/driver must be accompanied by external third party CI testing (more details in [1]). This means that, once the blueprint work has been approved, the code must be submitted through the same review process adopted for the blueprint, as detailed in [2], and accompanied by validation through third party CI. This sounds like a lot of work, but it is aimed at ensuring all the usual ilities of the software being part of the official source tree. That said, you are not alone and you can tap into the usual channels, like the mailing list or IRC ([3]). If there is anything vmware specific that you would like to address, we are here to help, so feel free to direct your questions to #openstack-vmware. Keep up the good work! Cheers, Armando [1] - https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers [2] - https://wiki.openstack.org/wiki/Gerrit_Workflow [3] - https://wiki.openstack.org/wiki/IRC ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2
Hi Sami, There was discussion around this in IRC yesterday iirc. The process seems to be just broken. As this week is Atlanta Summit week, expect some delays on responses/getting it fixed. - Erno -Original Message- From: Sami J. Mäkinen [mailto:sjm+osde...@hard.ware.fi] Sent: 13 May 2014 13:43 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2 Hello to all. I just created a document called neutron-ml2-mech-vmware-dvswitch.rst on a git repo clone from neutron-specs as instructed. My problem is, I just cannot submit my Contributor Agreement. I've tried Google Chrome and Firefox to no avail. The error message is always: *** Code Review - Error Server Error Cannot store contact information button: Continue *** Sigh, I even tried Opera. I get always the same error message. I cannot proceed from here. Can anybody help me out? My username/email is sjm at cybercom.fi and my realname contains one non-7bit-ascii character, if it does matter. Other than that, I don't see anything odd here. BR, Sami J. Mäkinen from Cybercom Finland On 06/05/14 20:05, Armando M. wrote: Hi Ilkka, As Mathieu suggested there is a blueprint submission and revision process put in place since the Juno release. Also, since Icehouse, to incorporate a new plugin/mechanism driver into the Neutron source tree, and to be designated as compatible, such a plugin/driver must be accompanied by external third party CI testing (more details in [1]). This means that, once the blueprint work has been approved, the code must be submitted through the same review process adopted for the blueprint, as detailed in [2], and accompanied by validation through third party CI. This sounds like a lot of work, but it is aimed at ensuring all the usual ilities of the software being part of the official source tree. That said, you are not alone and you can tap into the usual channels, like the mailing list or IRC ([3]). If there is anything vmware specific that you would like to address, we are here to help, so feel free to direct your questions to #openstack-vmware. Keep up the good work! Cheers, Armando [1] - https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers [2] - https://wiki.openstack.org/wiki/Gerrit_Workflow [3] - https://wiki.openstack.org/wiki/IRC ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2
Hi, Just to give this some context, the original idea for the driver came from the fact that there was no readily available method for using VLAN-backed port groups in dvSwitches with neutron. We tried using nova-network with regular vSwitches and VlanManager to evaluate the VMware driver in nova-compute but it was decided that neutron is a an absolute requirement for production use. The current code of the driver is tested with nova-compute controlling a vSphere 5.1 cluster. Multiple instances were successfully created, attached to the correct port group and network connectivity was achieved. We are not using VXLANs at the moment and are not actively looking into deploying them, so implementing a VXLAN support in the driver is not currently in our interest. Considering that VXLANs are configured as port groups in dvSwitches on the VMware side there isn¹t much difference in that part. However, configuring the VXLANs in the vShield app is something I think is out of the scope of this driver. We¹re interested in going through the blueprint process. Due to a rather tight schedule on our end we had to get a limited-functionality version of the driver ready before we had time to look into the process of submitting a blueprint and the required specs. The current version of the driver implements the only required feature in our environment - attaching virtual machines on the VMware side to correct dvSwitch port groups. Adding features like creating the port groups based on networks defined in neutron etc. are in consideration. I hope this answers some of the questions and I¹m happy to provide more details, if needed. Regards -- Jussi Sorjonen, Systems Specialist, Data Center +358 (0)50 594 7848, jussi.sorjo...@cybercom.com Cybercom Finland Oy, Urho Kekkosen katu 3 B, 00100 Helsinki, FINLAND www.cybercom.fi | www.cybercom.com On 06/05/14 11:17, Mathieu Rohon mathieu.ro...@gmail.com wrote: Hi IIkka, this is a very interesting MD for ML2. Have you ever tried to use your ML2 driver with VMWare drivers on the nova side, so that you could manage your VM with nova, and its network with neutron. Do you think it would be difficult to extend your driver to support vxlan encapsulation? Neutron has a new process to validate BP. Please follow those instructions to submit your spec for review : https://wiki.openstack.org/wiki/Blueprints#Neutron regards On Mon, May 5, 2014 at 2:22 PM, Ilkka Tengvall ilkka.tengv...@cybercom.com wrote: Hi, I would like to start a discussion about a ML2 driver for VMware distributed virtual switch (dvSwitch) for Neutron. There is a new blueprint made by Sami Mäkinen (sjm) in https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dv switch. The driver is described and code is publicly available and hosted in github: https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dv switch We would like to get the driver through contribution process, what ever that exactly means :) The original problem this driver solves for is is the following: We've been running VMware virtualization platform in our data center before OpenStack, and we will keep doing it due existing services. We also have been running OpenStack for a while also. Now we wanted to get the most out of both by combining the customers networks on the both plafroms by using provider networks. The problem is that the networks need two separate managers, neutron and vmware. There was no OpenStack tools to attach the guests on VMware side to OpenStack provider networks during instance creation. Now we are putting our VMware under control of OpenStack. We want to have one master to control the networks, Neutron. We implemented the new ML2 driver to do just that. It is capable of joining the machines created in vSphere to the same provider networks the OpenStack uses, using dvSwitch port groups. I just wanted to open the discussion, for the technical details please contact our experts on the CC list: Sami J. Mäkinen Jussi Sorjonen (freenode: mieleton) BR, Ilkka Tengvall Advisory Consultant, Cloud Architecture email: ilkka.tengv...@cybercom.com mobile: +358408443462 freenode: ikke-t web:http://cybercom.com - http://cybercom.fi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2
Hi, one other part of your future work, if the BP is accepted, is to deploy a third party testing environment. Since your work doesn't rely on opensource solution (VMWare), it won't be tested by the openstack CI. you will have to deploy an infra to test and vote on each patch submitted to neutron that might break your driver. see : http://ci.openstack.org/third_party.html regards On Wed, May 7, 2014 at 8:39 AM, Jussi Sorjonen jussi.sorjo...@cybercom.com wrote: Hi, Just to give this some context, the original idea for the driver came from the fact that there was no readily available method for using VLAN-backed port groups in dvSwitches with neutron. We tried using nova-network with regular vSwitches and VlanManager to evaluate the VMware driver in nova-compute but it was decided that neutron is a an absolute requirement for production use. The current code of the driver is tested with nova-compute controlling a vSphere 5.1 cluster. Multiple instances were successfully created, attached to the correct port group and network connectivity was achieved. We are not using VXLANs at the moment and are not actively looking into deploying them, so implementing a VXLAN support in the driver is not currently in our interest. Considering that VXLANs are configured as port groups in dvSwitches on the VMware side there isn¹t much difference in that part. However, configuring the VXLANs in the vShield app is something I think is out of the scope of this driver. We¹re interested in going through the blueprint process. Due to a rather tight schedule on our end we had to get a limited-functionality version of the driver ready before we had time to look into the process of submitting a blueprint and the required specs. The current version of the driver implements the only required feature in our environment - attaching virtual machines on the VMware side to correct dvSwitch port groups. Adding features like creating the port groups based on networks defined in neutron etc. are in consideration. I hope this answers some of the questions and I¹m happy to provide more details, if needed. Regards -- Jussi Sorjonen, Systems Specialist, Data Center +358 (0)50 594 7848, jussi.sorjo...@cybercom.com Cybercom Finland Oy, Urho Kekkosen katu 3 B, 00100 Helsinki, FINLAND www.cybercom.fi | www.cybercom.com On 06/05/14 11:17, Mathieu Rohon mathieu.ro...@gmail.com wrote: Hi IIkka, this is a very interesting MD for ML2. Have you ever tried to use your ML2 driver with VMWare drivers on the nova side, so that you could manage your VM with nova, and its network with neutron. Do you think it would be difficult to extend your driver to support vxlan encapsulation? Neutron has a new process to validate BP. Please follow those instructions to submit your spec for review : https://wiki.openstack.org/wiki/Blueprints#Neutron regards On Mon, May 5, 2014 at 2:22 PM, Ilkka Tengvall ilkka.tengv...@cybercom.com wrote: Hi, I would like to start a discussion about a ML2 driver for VMware distributed virtual switch (dvSwitch) for Neutron. There is a new blueprint made by Sami Mäkinen (sjm) in https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dv switch. The driver is described and code is publicly available and hosted in github: https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dv switch We would like to get the driver through contribution process, what ever that exactly means :) The original problem this driver solves for is is the following: We've been running VMware virtualization platform in our data center before OpenStack, and we will keep doing it due existing services. We also have been running OpenStack for a while also. Now we wanted to get the most out of both by combining the customers networks on the both plafroms by using provider networks. The problem is that the networks need two separate managers, neutron and vmware. There was no OpenStack tools to attach the guests on VMware side to OpenStack provider networks during instance creation. Now we are putting our VMware under control of OpenStack. We want to have one master to control the networks, Neutron. We implemented the new ML2 driver to do just that. It is capable of joining the machines created in vSphere to the same provider networks the OpenStack uses, using dvSwitch port groups. I just wanted to open the discussion, for the technical details please contact our experts on the CC list: Sami J. Mäkinen Jussi Sorjonen (freenode: mieleton) BR, Ilkka Tengvall Advisory Consultant, Cloud Architecture email: ilkka.tengv...@cybercom.com mobile: +358408443462 freenode: ikke-t web:http://cybercom.com - http://cybercom.fi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___
Re: [openstack-dev] Add VMware dvSwitch/vSphere API support for Neutron ML2
Hi IIkka, this is a very interesting MD for ML2. Have you ever tried to use your ML2 driver with VMWare drivers on the nova side, so that you could manage your VM with nova, and its network with neutron. Do you think it would be difficult to extend your driver to support vxlan encapsulation? Neutron has a new process to validate BP. Please follow those instructions to submit your spec for review : https://wiki.openstack.org/wiki/Blueprints#Neutron regards On Mon, May 5, 2014 at 2:22 PM, Ilkka Tengvall ilkka.tengv...@cybercom.com wrote: Hi, I would like to start a discussion about a ML2 driver for VMware distributed virtual switch (dvSwitch) for Neutron. There is a new blueprint made by Sami Mäkinen (sjm) in https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dvswitch. The driver is described and code is publicly available and hosted in github: https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dvswitch We would like to get the driver through contribution process, what ever that exactly means :) The original problem this driver solves for is is the following: We've been running VMware virtualization platform in our data center before OpenStack, and we will keep doing it due existing services. We also have been running OpenStack for a while also. Now we wanted to get the most out of both by combining the customers networks on the both plafroms by using provider networks. The problem is that the networks need two separate managers, neutron and vmware. There was no OpenStack tools to attach the guests on VMware side to OpenStack provider networks during instance creation. Now we are putting our VMware under control of OpenStack. We want to have one master to control the networks, Neutron. We implemented the new ML2 driver to do just that. It is capable of joining the machines created in vSphere to the same provider networks the OpenStack uses, using dvSwitch port groups. I just wanted to open the discussion, for the technical details please contact our experts on the CC list: Sami J. Mäkinen Jussi Sorjonen (freenode: mieleton) BR, Ilkka Tengvall Advisory Consultant, Cloud Architecture email: ilkka.tengv...@cybercom.com mobile: +358408443462 freenode: ikke-t web:http://cybercom.com - http://cybercom.fi ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
