something to watch out for - virtualBox gives out Intel pro 1000 adapters by
default. But the linux driver for this nic strips off any vlan tagging
http://architects.dzone.com/articles/advanced-virtualbox-and So using these to
trunk your OVS bridges won't work. Virtio-net nics work ok.
Darragh.
>________________________________
> From: Dan Wendlandt <d...@nicira.com>
>To: Yapeng Wu <yapen...@me.com>; netstack@lists.launchpad.net
>Sent: Tuesday, 21 February 2012, 21:22
>Subject: Re: [Netstack] devstack multi-node ENABLED_SERVICES flags for compute
>node
>
>
>Hi Yapeng, adding the main netstack list so everyone can learn from the
>responses. Comments inline.
>
>
>Dan
>
>
>On Tue, Feb 21, 2012 at 9:52 AM, Yapeng Wu <yapen...@me.com> wrote:
>
>Hello, Dan, Thanks for your reply. Hope your get well soon!
>>
>>
>>I tried IMAGE_URLS in the localrc file last week, but it does not work. I
>>think the image was not imported into Glance properly, I will try to use
>>Glance command manually to import this week. Right now I am still using
>>cirros image file for multi-host testing.
>
>
>interesting... if you figure out why, let me know.
>
>
>>
>>The multi-node devstack setup is working "partially" now. The setup I got is:
>>two compute nodes, and one controller. The quantum service is running with
>>the controller node. I could create several networks and launch VM with one
>>or more than one networks. But for some VM(s), the VM failed to get IP
>>address after several "dhcpc" sending discover packets.
>
>
>Ok, great. Dave from Nicira has also been doing work on multi-node devstack.
>I sent an email to the main list so you two can coordinate.
>
>
>>
>> I have two questions regarding of what I've observed:
>>1. for each virtual L2 quantum network, if I created any VM associated with
>>this network, there is always two type interfaces created in openvSwitch by
>>the agent: gw-xxxx and tapxxxx. From the testing result, gw-xxx is "randomly"
>>created on controller or compute node. I had thought gw-xxxx is the "gateway"
>>interface for the network, it always staying with quantum service or
>>controller node. Is this design intended?
>
>
>to be clear, the agent never creates interface devices. The agent just
>configures them so that they are on the right network (e.g., putting them on a
>particular VLAN)
>
>
>the gateway devices will be created on the node that you are using for
>nova-network. nova-network should only be running on one node.
>
>
>>
>>I read the source code a bit (I don't know much python code), looks like the
>>agent is "listening" to mysql db update. Based on db update, how does the
>>agent determine the interface gw-xxx or tapxxx needs to be created on the
>>vswitch?
>
>
>Agents don't create devices. They look at the 'id' associated with particular
>device, and then figure out what quantum network it belongs on.
>
>
>>
>>2. Does gw-xxx interface also been used by "dhcp server" for this network's
>>subnet? I noticed that sometimes gw-xxx interface could be created on
>>compute node, not on controller node. I am wondering if in this case, how
>>does VM's DHCP works?
>
>
>Yes gw-xxx devices are also used for DHCP. If you only run nova-network on
>the "controller" node, DHCP devices will only be created there.
>
>
>>
>>I have not tried the floating IP yet, does floating IP address working with
>>the current quantum code? I plan to give it a try today or tomorrow.
>
>
>Yes.
>
>
>>
>>I will "polish" the modification of the stack.sh (too many hackings...) and
>>forward to mailing list with I've done.
>
>
>Great!
>
>
>
>
>
>
>>
>>Thanks again,
>>
>>
>>Yapeng
>>
>>On Feb 20, 2012, at 09:51 PM, Dan Wendlandt <d...@nicira.com> wrote:
>>
>>
>>Sorry Yapeng, I was out sick two days last week and as a result am very
>>behind on email.
>>>
>>>
>>>You should be able to do something like this in your localrc within the
>>>devstack directory:
>>>
>>>
>>>IMAGE_URLS="http://www.openvswitch.org/tty-quantum.tgz";
>>>
>>>
>>>By the way, did you get the multi-node devstack setup working? If so, could
>>>you send an email describing this to the list? We should really get that
>>>code committed into the devstack repo.
>>>
>>>
>>>Dan
>>>
>>>
>>>
>>>On Tue, Feb 14, 2012 at 12:58 PM, Yapeng Wu <yapen...@me.com> wrote:
>>>
>>>
>>>>Dan,
>>>>
>>>>
>>>>Thanks for help! It helps me to get hands "dirty" now. I almost get
>>>>multi-host setup working, except the dhcp on extra ethernet interface.
>>>>
>>>>
>>>>Can I ask you one more question? How to import tty-quantum.tgz (you gave
>>>>out the link in last bug squash meeting) image into the glance?
>>>>
>>>>
>>>>Thanks,
>>>>Yapeng
>>>>
>>>>On Feb 14, 2012, at 11:56 AM, Dan Wendlandt <d...@nicira.com> wrote:
>>>>
>>>>
>>>>On Mon, Feb 13, 2012 at 9:18 PM, Yapeng Wu <yapen...@me.com> wrote:
>>>>>> Thanks for your help, Dan.
>>>>>>
>>>>>> I found the problem after looking at the log in the "screen" window. It
>>>>>> is
>>>>>> my own fault.
>>>>>> Now VM starts fine.
>>>>>> But in Horizon dashboard, the "Network" tab has gone away in the Project
>>>>>> Tab.
>>>>>>
>>>>>> "Screen" is a very handy tool. Do you know if I could save the log in the
>>>>>> "screen" window?
>>>>>> n-cpu log scrolls too fast, hard to catch up:)
>>>>>
>>>>>Doing control-A control-[ puts you in "copy mode", where you can
>>>>>scroll up and down using control-u and control-d. Check out the link
>>>>>I sent you.
>>>>>
>>>>>You could also tweak ./stack.sh to redirect the output of certain
>>>>>daemons to a file instead of standard error/out.
>>>>>
>>>>>Dan
>>>>>
>>>>>
>>>>>>
>>>>>> Yapeng
>>>>>>
>>>>>> On Feb 13, 2012, at 04:16 PM, Dan Wendlandt <d...@nicira.com> wrote:
>>>>>>
>>>>>> if you're running devstack, you can just look at the console output of
>>>>>> the services, which are running with screen. Just run:
>>>>>>
>>>>>> screen -x stack
>>>>>>
>>>>>> window #5 is the quantum service
>>>>>> window #6 is the quantum agent
>>>>>> window #7 is nova-compute service
>>>>>> window #8 is nova-network
>>>>>>
>>>>>> if you're new to screen, check out:
>>>>>> http://www.pixelbeat.org/lkdb/screen.html
>>>>>>
>>>>>> Dan
>>>>>>
>>>>>> On Mon, Feb 13, 2012 at 1:09 PM, Yapeng Wu <yapen...@me.com> wrote:
>>>>>>>
>>>>>>> Hello, Dan,
>>>>>>>
>>>>>>> I just tested single node devstack, it is broken with quantum plugin. I
>>>>>>> tested it last Friday, it works fine in single node environment.
>>>>>>>
>>>>>>> Where is the quantum service logs located?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Yapeng
>>>>>>>
>>>>>>> On Feb 13, 2012, at 04:01 PM, Dan Wendlandt <d...@nicira.com> wrote:
>>>>>>>
>>>>>>> On Mon, Feb 13, 2012 at 12:05 PM, Yapeng Wu <yapen...@me.com> wrote:
>>>>>>>> Brad and Dan,
>>>>>>>>
>>>>>>>> Thanks for quick response, I "hacked" devstack stack.sh, the OVS
>>>>>>>> configuration and q-agt is running fine now.
>>>>>>>>
>>>>>>>> I found the master stream of quantum plugin is not working, the VM
>>>>>>>> created
>>>>>>>> in nova is stucked in "Build" state.
>>>>>>>
>>>>>>> Is this the case even in a single node devstack deployment? I'm not
>>>>>>> exactly on master, but I haven't noticed issues in the past week or
>>>>>>> so. Prior to that, a lot of new code went in and destablized things a
>>>>>>> bit. Looking in the logs of nova-network, nova-compute, and the
>>>>>>> quantum service is probably the best route to identifying the issue.
>>>>>>> Feel free to create a launchpad bug on this.
>>>>>>>
>>>>>>>>
>>>>>>>> Is the "essex-3" branch is stable enough to test?
>>>>>>>
>>>>>>> It is generally more stable, if you are running from devstack. Though
>>>>>>> there are a couple known issues around the os-create-server extension
>>>>>>> that are being fixed in master.
>>>>>>>
>>>>>>> Dan
>>>>>>>
>>>>>>>>
>>>>>>>> Yapeng
>>>>>>>>
>>>>>>>>
>>>>>>>> On Feb 13, 2012, at 02:09 PM, Dan Wendlandt <d...@nicira.com> wrote:
>>>>>>>>
>>>>>>>> On Mon, Feb 13, 2012 at 10:41 AM, Brad Hall <b...@nicira.com> wrote:
>>>>>>>>> Hi Yapeng,
>>>>>>>>>
>>>>>>>>> There is probably bug where ovs is only installed if "quantum" is
>>>>>>>>> specified in enabled_services -- I'll take a look at it today.
>>>>>>>>
>>>>>>>> Yes, this is the case. I've worked around this locally, but never
>>>>>>>> pushed it upstream.
>>>>>>>>
>>>>>>>> IIRC, beyond making sure that OVS is installed on a compute only node,
>>>>>>>> there are also some other issues to work around, including needing to
>>>>>>>> make sure the quantum agent code is installed on the compute node
>>>>>>>> (easiest is just to clone entire quantum repo) and to make sure MYSQL
>>>>>>>> permissions are set correctly.
>>>>>>>>
>>>>>>>> dan
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Brad
>>>>>>>>>
>>>>>>>>> On Mon, Feb 13, 2012 at 9:57 AM, Yapeng Wu <yapen...@me.com> wrote:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> I don't know if anyone tried to use devstack to test out the
>>>>>>>>>> multi-node
>>>>>>>>>> setup using quantum openvswitch plugin?
>>>>>>>>>>
>>>>>>>>>> on compute node, I tried the following flag in localrc:
>>>>>>>>>> ENABLED_SERVICES=n-cpu,n-net,n-api,q-agt
>>>>>>>>>> Q_PLUGIN=openvswitch
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> But it failed, looks like openvswitch was not installed.
>>>>>>>>>>
>>>>>>>>>> What else service should I add in ENABLED_SERVICES?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Yapeng
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>> Dan Wendlandt
>>>>>>>> Nicira Networks: www.nicira.com
>>>>>>>> twitter: danwendlandt
>>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>> Dan Wendlandt
>>>>>>> Nicira Networks: www.nicira.com
>>>>>>> twitter: danwendlandt
>>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>> Dan Wendlandt
>>>>>> Nicira Networks: www.nicira.com
>>>>>> twitter: danwendlandt
>>>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>Dan Wendlandt
>>>>>Nicira Networks: www.nicira.com
>>>>>twitter: danwendlandt
>>>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>
>>>
>>>
>>>--
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>Dan Wendlandt
>>>Nicira Networks: www.nicira.com
>>>
>>>twitter: danwendlandt
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>>
>
>
>
>--
>~~~~~~~~~~~~~~~~~~~~~~~~~~~
>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
>
>
>
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
