[Openstack-operators] OpenStack-operators Digest, Vol 35, Issue 4

yungho yungho5054 at gmail.com
Fri Sep 6 10:49:48 UTC 2013


Hello,
      I am now in CentOS6.4 deploy OpenStack's Single Flat Network, encountered
some problems, hoping to have a friend help me. Part of the network
configuration on I refer to the official documentation
bk-quantum-admin-guide-grizzly.pdf, but the virtual machine is created, no
address. Please help me, thank you.


On Wed, Sep 4, 2013 at 8:00 PM, <
openstack-operators-request at lists.openstack.org> wrote:

> Send OpenStack-operators mailing list submissions to
>         openstack-operators at lists.openstack.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
> or, via email, send a message with subject or body 'help' to
>         openstack-operators-request at lists.openstack.org
>
> You can reach the person managing the list at
>         openstack-operators-owner at lists.openstack.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenStack-operators digest..."
>
>
> Today's Topics:
>
>    1. Re: OpenStack-operators Digest, Vol 35,   Issue 1 (Darragh O'Reilly)
>    2. Getting all the DHCP/L3 agent adresses    without admin right
>       (Robert van Leeuwen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 3 Sep 2013 14:33:09 +0100 (BST)
> From: Darragh O'Reilly <dara2002-openstack at yahoo.com>
> To: yungho <yungho5054 at gmail.com>
> Cc: "openstack-operators at lists.openstack.org"
>         <openstack-operators at lists.openstack.org>
> Subject: Re: [Openstack-operators] OpenStack-operators Digest, Vol 35,
>         Issue 1
> Message-ID:
>         <1378215189.67447.YahooMailNeo at web172401.mail.ir2.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> Yungho,
>
> 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.
>
>
> 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.
>
>
> With vlan mode instances can access real networks and routers without need
> for floating IPs.
>
>
> Re,
> Darragh.
>
>
> >________________________________
> > From: Lorin Hochstein <lorin at nimbisservices.com>
> >To: yungho <yungho5054 at gmail.com>
> >Cc: "openstack-operators at lists.openstack.org" <
> openstack-operators at lists.openstack.org>
> >Sent: Tuesday, 3 September 2013, 4:24
> >Subject: Re: [Openstack-operators] OpenStack-operators Digest, Vol
> 35,????Issue 1
> >
> >
> >
> >Youngho:
> >
> >
> >On Mon, Sep 2, 2013 at 10:51 PM, yungho <yungho5054 at gmail.com> wrote:
> >
> >Hello,
> >>? ? ? ?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.
> >>
> >>
> >>
> >
> >
> >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.
> >
> >
> >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.
> >
> >
> >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.
> >
> >
> >Take care,
> >
> >
> >Lorin
> >--?
> >
> >Lorin Hochstein
> >
> >Lead Architect - Cloud Services
> >Nimbis Services, Inc.
> >www.nimbisservices.com
> >_______________________________________________
> >OpenStack-operators mailing list
> >OpenStack-operators at lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >
> >
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 3 Sep 2013 13:36:52 +0000
> From: Robert van Leeuwen <Robert.vanLeeuwen at spilgames.com>
> To: "openstack-operators at lists.openstack.org"
>         <openstack-operators at lists.openstack.org>
> Subject: [Openstack-operators] Getting all the DHCP/L3 agent adresses
>         without admin right
> Message-ID:
>         <79E00D9220302D448C1D59B5224ED12D8D9C8225 at EchoDB02.spil.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> For monitoring purposes I would like to get all dhcp-agent addresses
> without being an admin.
> As an admin in the tenant where the services reside I can get a list of
> all dhcp agent (IP's)
>
> I've tried to create a new role to this without admin access.
> I've changed the quantum policy file to reflect this changes but I cannot
> get it to work without being  an admin.
> Even adding the role to admin_only/admin_or_network_owner/admin_or_owner
> in the quantum policy file does not work.
>
> Any suggestions?
> It is Grizzly
>
> Thx,
> Robert van Leeuwen
>
>
> ------------------------------
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
> End of OpenStack-operators Digest, Vol 35, Issue 4
> **************************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130906/01361bb2/attachment.html>


More information about the OpenStack-operators mailing list