<div dir="ltr"><div id="gt-res-content" class=""><div dir="ltr" style="zoom:1"><span id="result_box" class="" lang="en"><span class="">Hello</span>,<br> <span class="">I am now in</span> <span class="">CentOS6.4</span> <span class="">deploy</span> <span class="">OpenStack</span>'s <span class="">Single Flat Network,</span> <span class="">encountered some</span> <span class="">problems</span>, hoping to <span class="">have a friend</span> <span class="">help me.</span> <span class="">Part of the network</span> <span class="">configuration</span> <span class="">on</span> <span class="">I</span> <span class="">refer to the official</span> <span class="">documentation</span> <span class="">bk-quantum-admin-guide-grizzly.pdf,</span> <span class="">but the virtual machine</span> <span class="">is created,</span> <span class="">no address</span>. <span class="">Please</span> <span class="">help me,</span> <span class="">thank you.</span></span></div>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 4, 2013 at 8:00 PM, <span dir="ltr"><<a href="mailto:openstack-operators-request@lists.openstack.org" target="_blank">openstack-operators-request@lists.openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send OpenStack-operators mailing list submissions to<br>
<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:openstack-operators-request@lists.openstack.org">openstack-operators-request@lists.openstack.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:openstack-operators-owner@lists.openstack.org">openstack-operators-owner@lists.openstack.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of OpenStack-operators digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: OpenStack-operators Digest, Vol 35, Issue 1 (Darragh O'Reilly)<br>
2. Getting all the DHCP/L3 agent adresses without admin right<br>
(Robert van Leeuwen)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 3 Sep 2013 14:33:09 +0100 (BST)<br>
From: Darragh O'Reilly <<a href="mailto:dara2002-openstack@yahoo.com">dara2002-openstack@yahoo.com</a>><br>
To: yungho <<a href="mailto:yungho5054@gmail.com">yungho5054@gmail.com</a>><br>
Cc: "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
Subject: Re: [Openstack-operators] OpenStack-operators Digest, Vol 35,<br>
Issue 1<br>
Message-ID:<br>
<<a href="mailto:1378215189.67447.YahooMailNeo@web172401.mail.ir2.yahoo.com">1378215189.67447.YahooMailNeo@web172401.mail.ir2.yahoo.com</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
Yungho,<br>
<br>
just to note: you can use more than one of vlan/gre/flat at the same time - ie your installation can have both gre and vlan.<br>
<br>
<br>
As Lorin says, gre mode is easier to setup because it is completely decoupled from the physical layer 2 network. I think gre would be particularly useful in large installations where tenants frequently create/destroy networks on demand. But the networks are isolated from the real world and require floating ips, and so an l3-agent which might be a chokepoint or a single point of failure - I'm not sure what the l3-agent load balancing or failover options are with Grizzly. Also performance may suffer because the physical NICs TCP off-load engines never get triggered.<br>
<br>
<br>
With vlan mode instances can access real networks and routers without need for floating IPs.<br>
<br>
<br>
Re,<br>
Darragh.<br>
<br>
<br>
>________________________________<br>
> From: Lorin Hochstein <<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>><br>
>To: yungho <<a href="mailto:yungho5054@gmail.com">yungho5054@gmail.com</a>><br>
>Cc: "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>" <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
>Sent: Tuesday, 3 September 2013, 4:24<br>
>Subject: Re: [Openstack-operators] OpenStack-operators Digest, Vol 35,????Issue 1<br>
><br>
><br>
><br>
>Youngho:<br>
><br>
><br>
>On Mon, Sep 2, 2013 at 10:51 PM, yungho <<a href="mailto:yungho5054@gmail.com">yungho5054@gmail.com</a>> wrote:<br>
><br>
>Hello,<br>
>>? ? ? ?I CentOs6.4 environment to deploy OpenStack G version, Controller Node, Network Node, Compute Node. Networks using Quantum, but is still on the Quantum network model do not know, and want to know under what circumstances the use of gre, under what circumstances the vlan mode.<br>
>><br>
>><br>
>><br>
><br>
><br>
>Do you have administrative privileges on the networking switch that connects your compute hosts together? If so, I would recommend using vlan mode. You will need to configure your switch appropriately.<br>
><br>
><br>
>If you aren't able to modify the settings on your switch, or if your nodes are not all connected to the same L2 network, then you will need to use GRE tunnels.<br>
><br>
><br>
>I believe that GRE will work for pretty much all scenarios (since it just requires IP connectivity), but I think it introduces some overhead. However, I have no first-hand experience with it.<br>
><br>
><br>
>Take care,<br>
><br>
><br>
>Lorin<br>
>--?<br>
><br>
>Lorin Hochstein<br>
><br>
>Lead Architect - Cloud Services<br>
>Nimbis Services, Inc.<br>
><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 3 Sep 2013 13:36:52 +0000<br>
From: Robert van Leeuwen <<a href="mailto:Robert.vanLeeuwen@spilgames.com">Robert.vanLeeuwen@spilgames.com</a>><br>
To: "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"<br>
<<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
Subject: [Openstack-operators] Getting all the DHCP/L3 agent adresses<br>
without admin right<br>
Message-ID:<br>
<79E00D9220302D448C1D59B5224ED12D8D9C8225@EchoDB02.spil.local><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi,<br>
<br>
For monitoring purposes I would like to get all dhcp-agent addresses without being an admin.<br>
As an admin in the tenant where the services reside I can get a list of all dhcp agent (IP's)<br>
<br>
I've tried to create a new role to this without admin access.<br>
I've changed the quantum policy file to reflect this changes but I cannot get it to work without being an admin.<br>
Even adding the role to admin_only/admin_or_network_owner/admin_or_owner in the quantum policy file does not work.<br>
<br>
Any suggestions?<br>
It is Grizzly<br>
<br>
Thx,<br>
Robert van Leeuwen<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
<br>
End of OpenStack-operators Digest, Vol 35, Issue 4<br>
**************************************************<br>
</blockquote></div><br></div>