openstack team mailing list archive

[Dan Wendlandt <dan@xxxxxxxxxx>]

Hi Mandar,

The whole "default" stuff is a common point of confusion with
QuantumManager, and something we're planning on getting rid of in Folsom.
 For Essex, I've explained the details below.

On Wed, Apr 11, 2012 at 8:47 PM, Vaze, Mandar <Mandar.Vaze@xxxxxxxxxxx>wrote:

>  Dan,****
>
> Bug you referred to specifically says “default” tenant – which is not the
> case for me.****
>
> I’m not using default tenant – I’m using  uuid of “demo” tenant created by
> stack.sh
>

I suspect you are spinning up VMs using the "demo" tenant, but unless you
have modified your stack.sh, when you create a network using nova-manage,
no "--project_id" flag is specified.  Hence, from a Quantum perspective
that network does not have a tenant, making this a "global" network, which
is owned by a tenant named "default" (this string can be changed using the
quantum_default_tenant_id flag in nova).  For more details on creating
quantum networks with nova-manage, see:
http://docs.openstack.org/incubation/openstack-network/admin/content/Net-Create-dle455.html


> ****
>
> BTW, stack.sh creates incorrect  entries in quantum/mélange DB,  it has
> tenant ID = “default” – This should be uuid of some valid tenant, not
> string “default”
>

This is not actually incorrect, given the logic above, though I admit it is
confusing.  This was really just to provide backward compatibility with old
nova-manage calls that did not specify a project.  In Folsom, we're
planning on requiring a tenant for all Quantum network creation.



> ****
>
> ** **
>
> FWIW, this setup (although seems incorrect) works with quantum+nova_ipam –
> not with quantum+mélange ****
>
> i.e. With quantum+nova_ipam I can just create a VM and ssh to it.
>

Yes, quantum + nova-ipam is a much more tested path.  I suspect you are
just running into the bug I mention below and that your quantum + melange
setup would work once you have that patch in, but I don't know of anyone
using Melange + DHCP in a real deployment, so I wouldn't be surprised if
there were more issues lurking.

Dan



> ****
>
> ** **
>
> -Mandar****
>
> ** **
>
> *From:* Dan Wendlandt [mailto:dan@xxxxxxxxxx]
> *Sent:* Wednesday, April 11, 2012 11:07 PM
> *To:* Vaze, Mandar
> *Cc:* Nicolas de BONFILS; openstack@xxxxxxxxxxxxxxxxxxx
>
> *Subject:* Re: [Openstack] Instance can't reach dhcp or metadata****
>
> ** **
>
> ** **
>
> On Wed, Apr 11, 2012 at 5:24 AM, Vaze, Mandar <Mandar.Vaze@xxxxxxxxxxx>
> wrote:****
>
> I have *never* been able to get to ssh to an instance with Quantum+mélange
> ****
>
> https://lists.launchpad.net/openstack/msg09206.html****
>
> ** **
>
> Looking at that thread, I suspect you may be hitting the same issue I
> mentioned above: https://bugs.launchpad.net/quantum/+bug/949234****
>
> ** **
>
> If you try that fix and either do or don't have luck with it, please add a
> comment to the issue.****
>
> ** **
>
> Dan****
>
> ** **
>
>  ****
>
>   ****
>
> -Mandar****
>
>  ****
>
> *From:* openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx[mailto:
> openstack-bounces+mandar.vaze=nttdata.com@xxxxxxxxxxxxxxxxxxx] *On Behalf
> Of *Nicolas de BONFILS
> *Sent:* Wednesday, April 11, 2012 1:45 AM
> *To:* Dan Wendlandt
> *Cc:* openstack@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Openstack] Instance can't reach dhcp or metadata****
>
>  ****
>
> Hi,
>
> I can't get the ssh connection,VNC doesn't respond and 10.0.0.1 go to
> localhost (ssh to server itself)
> ****
>
>  ****
>
> ---****
>
> Nicolas****
>
> ** **
>
> On Tue, Apr 10, 2012 at 21:42, Dan Wendlandt <dan@xxxxxxxxxx> wrote:****
>
>  ****
>
> On Tue, Apr 10, 2012 at 11:54 AM, Nicolas de BONFILS <ndebonfils@xxxxxxxxx>
> wrote:****
>
> Things starting to work !****
>
> When I boot boot cirros image with ip 10.0.0.1, I can ssh (even if it
> doesn't accept my password), but when I lauch tty-uec image (or other) with
> ip starting at 10.0.0.2, ssh tell "no route to host"****
>
>  ****
>
> If it works on one image, but not another, this is probably an issue with
> the image itself.  The "no route to host" error is likely because the
> gateway interface 10.0.0.1 is arping for 10.0.0.2 and not getting a
> response.  Perhaps the image is not configured to use DCHP on the
> interface?  Or is not correctly launching?  I'd use VNC to login and check
> it out.  ****
>
>  ****
>
> Dan****
>
>  ****
>
>
> I sum up the actual conf****
>
>    - br-int as bridge in OVS, no other conf (nothing in interfaces file),
>    ifconfig show a 10.0.0.1 ip****
>    - nova conf got public_interface=br-int / flat_network_bridge=br-int /
>    flat_interface=eth0****
>    - quantum manage the assignation successfully****
>
>  Thanks****
>
> ---****
>
> Nicolas****
>
>  ****
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp****
>
>
>
> ****
>
>  ****
>
> -- ****
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dan Wendlandt ****
>
> Nicira, Inc: www.nicira.com****
>
> twitter: danwendlandt
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~****
>
>  ****
>
>  ****
>
>
> ______________________________________________________________________
> Disclaimer:This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding****
>
>
>
> ****
>
> ** **
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dan Wendlandt ****
>
> Nicira, Inc: www.nicira.com****
>
> twitter: danwendlandt
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~****
>
> ** **
>
> ______________________________________________________________________
> Disclaimer:This email and any attachments are sent in strictest confidence
> for the sole use of the addressee and may contain legally privileged,
> confidential, and proprietary data. If you are not the intended recipient,
> please advise the sender by replying promptly to this email and then delete
> and destroy this email and any attachments without any further use, copying
> or forwarding
>



-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~