Hi Tomasz,

 

Thanks for your note. I am not sure I completely understand the problems you 
are facing. Please note that the patch you have referred to introduces the 
VIF-driver for Quantum’s Linux Bridge plugin. The behavior of this is slightly 
different from the VIF driver that is used within Nova for plugging into a 
Linux bridge (when using a VLAN-NetworkManager). More responses inline.

 

Thanks,

~Sumit.

 

From: netstack-bounces+snaiksat=cisco....@lists.launchpad.net 
[mailto:netstack-bounces+snaiksat=cisco....@lists.launchpad.net] On Behalf Of 
Tomasz Paszkowski
Sent: Tuesday, March 20, 2012 2:54 PM
To: netstack@lists.launchpad.net
Subject: Re: [Netstack] Fwd: [Openstack] Quantum 2012.1 RC1 available

 



as I wrote in bug report related to linux bridge and quantum in nova this code 
is broken in few places:

 

1)      tap devices for instances are set up (ip link set up) by quantum during 
creation and this is stoping libvirt from changing mac address of this 
interface which is breaking vm startup

 

<Sumit> We have not seen issues with the VM startup. Could you kindly be a 
little more specific as to which MAC address needs to change, and is not 
getting changed?</Sumit>

 

2)      nova-network is not initializing bridge devices on startup and l3 
interfaces

 

 

<Sumit> Did you run the Quantum Linux Bridge agent? The agent does this work, 
and it only happens when the first VM comes up on that network. </Sumit>

 

3)      machine running instances after reboot is loosing all bridges and tap 
devices and there is no code which recreates this. 

 

<Sumit> I have not tested this, but again, if you were running the Quantum 
Linux Bridge agent, the bridges should get created again. The tap devices are 
created in the VIF driver, so that only happens when Nova calls “plug” on VM 
start-up. </Sumit>

 

problem 1 and 2 is resolved by code changes in nova and problem nr. 3 is 
addressed by adapting interface type bridge with quantum linux bridge 
integration.

 

patches are on launchpad https://bugs.launchpad.net/nova/+bug/941794

 

 

At the end in my opinion we don't need an agent for linux bridge integration.

 

<Sumit> As I mentioned earlier, in order to fully support the Quantum 
attach/detach interface semantics, the interface-type has to be set to 
“ethernet” (so that tap devices can be used, and be added to the bridge only 
when attach is called, and vice versa), and the agent has to be run so that the 
per-host configuration is done correctly.  So the agent is needed. Of course, 
if there are any issues, those need to be fixed.</Sumit>


Dnia 20-03-2012 o godz. 22:29 "Sumit Naiksatam (snaiksat)" <snaik...@cisco.com> 
napisał(a):

        Hi Ghe,

         

        Thanks for this update. The Linux Bridge plugin also needs an agent. I 
would imagine that the packaging of that agent would be very similar to that of 
the openvswitch-agent, but I don’t know enough on the packaging to say with any 
certainty.

         

        Also, the Cisco plugin does not use an agent at this time, so no agent 
packaging is required there; just letting you know so that you don’t have to 
spend your time exploring.

         

        If I am not mistaken, the Ryu plugin also uses an agent.

         

        Thanks,

        ~Sumit.

         

        From: netstack-bounces+snaiksat=cisco....@lists.launchpad.net 
[mailto:netstack-bounces+snaiksat <mailto:netstack-bounces%2Bsnaiksat> 
=cisco....@lists.launchpad.net] On Behalf Of Ghe Rivero
        Sent: Tuesday, March 20, 2012 1:17 PM
        To: Dan Wendlandt
        Cc: netstack@lists.launchpad.net
        Subject: Re: [Netstack] Fwd: [Openstack] Quantum 2012.1 RC1 available

         

        Hi,

            Debian packages for quantum-rc1 are ready to install from unstable 
(sid) ditribution. Up to now, the binaries packages that can be installed for 
Debian are:

        Quantum:

        *       quantum-plugin-cisco 
        *       quantum-plugin-linuxbridge
        *       quantum-plugin-nicira
        *       quantum-plugin-openvswitch 
        *       quantum-plugin-openvswitch-agent 
        *       quantum-plugin-ryu 
        *       quantum-plugin-sample
        *       quantum-server 

        Python-quantumclient:

        *       python-quantumclient
        *       quantum-common

         

        Before final release, just a few changes are expected

        *        plugins packages will be revised (I need to check if someone 
else beside openswitch needs an agent and how to handle it)
        *       working default configurations using openvswitch/linuxbridge 
plugins

        Thanks everyone for the great work in this release.

        Ghe Rivero

        On Tue, Mar 20, 2012 at 6:53 AM, Dan Wendlandt <d...@nicira.com> wrote:

        Not sure how many people might be on netstack but not the main 
openstack ML, but Thierry cut the official version of the Quantum RC1 today. 

         

        I'm working with folks from Red Hat & Ubuntu to get binary packages 
based on the RC1 for final testing.  Any other distros that are interested, let 
me know!

         

        Dan

         

        ---------- Forwarded message ----------
        From: Thierry Carrez <thie...@openstack.org>
        Date: Mon, Mar 19, 2012 at 10:00 AM
        Subject: [Openstack] Quantum 2012.1 RC1 available
        To: "openst...@lists.launchpad.net" <openst...@lists.launchpad.net>
        
        
        The first release candidate for Quantum 2012.1 ("Essex") is now
        available at:
        
        https://bugs.launchpad.net/quantum/+milestone/essex-rc1
        
        Unless release-critical issues are found that warrant a release
        candidate respin, this RC1 will be formally released as the 2012.1 final
        version. You are therefore strongly encouraged to test and validate it.
        
        If you find an issue that could be considered release-critical, please
        file it at:
        
        https://bugs.launchpad.net/quantum/+filebug
        
        and tag it "essex-rc-potential" to bring it to Dan's attention.
        
        The "master" branch of Quantum is now open for Folsom development,
        feature freeze restrictions no longer apply.
        
        NB: Quantum is not a core project for the Essex cycle, therefore it's
        not part of OpenStack 2012.1 common release, scheduled for April 5.
        
        --
        Thierry Carrez (ttx)
        Release Manager, OpenStack
        
        _______________________________________________
        Mailing list: https://launchpad.net/~openstack
        Post to     : openst...@lists.launchpad.net
        Unsubscribe : https://launchpad.net/~openstack
        More help   : https://help.launchpad.net/ListHelp

        
        
        

         

        -- 
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Dan Wendlandt 

        Nicira Networks: www.nicira.com

        twitter: danwendlandt
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~

         

        
        --
        Mailing list: https://launchpad.net/~netstack
        Post to     : netstack@lists.launchpad.net
        Unsubscribe : https://launchpad.net/~netstack
        More help   : https://help.launchpad.net/ListHelp

        
        
        

         

        -- 

        Ghe Rivero
        OpenStack & Distribution Engineer
        www.stackops.com <http://www.stackops.com/>  |  ghe.riv...@stackops.com 
<mailto:diego.parri...@stackops.com>  | +34 625 63 45 23 | skype:ghe.rivero
        <http://www.stackops.com/> 

         <http://stackops.s3-external-3.amazonaws.com/STACKOPSLOGO-ICON.png> 

        ******************** ADVERTENCIA LEGAL ******************** 
        Le informamos, como destinatario de este mensaje, que el correo 
electrónico y las comunicaciones por medio de Internet no permiten asegurar ni 
garantizar la confidencialidad de los mensajes transmitidos, así como tampoco 
su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no 
asume responsabilidad alguna por tales circunstancias. Si no consintiese en la 
utilización del correo electrónico o de las comunicaciones vía Internet le 
rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. 
Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene 
información confidencial y sujeta al secreto profesional, cuya divulgación no 
está permitida por la ley. En caso de haber recibido este mensaje por error, le 
rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico 
remitido a nuestra atención y proceda a su eliminación, así como a la de 
cualquier documento adjunto al mismo. Asimismo, le comunicamos que la 
distribución, copia o utilización de este mensaje, o de cualquier documento 
adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la 
ley. 
        
        ***************** PRIVILEGED AND CONFIDENTIAL **************** 
        We hereby inform you, as addressee of this message, that e-mail and 
Internet do not guarantee the confidentiality, nor the completeness or proper 
reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not 
assume any liability for those circumstances. Should you not agree to the use 
of e-mail or to communications via Internet, you are kindly requested to notify 
us immediately. This message is intended exclusively for the person to whom it 
is addressed and contains privileged and confidential information protected 
from disclosure by law. If you are not the addressee indicated in this message, 
you should immediately delete it and any attachments and notify the sender by 
reply e-mail. In such case, you are hereby notified that any dissemination, 
distribution, copying or use of this message or any attachments, for any 
purpose, is strictly prohibited by law.

         

        -- 
        Mailing list: https://launchpad.net/~netstack
        Post to     : netstack@lists.launchpad.net
        Unsubscribe : https://launchpad.net/~netstack
        More help   : https://help.launchpad.net/ListHelp

-- 
Mailing list: https://launchpad.net/~netstack
Post to     : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to