[Rdo-list] Quantum in Packstack

[Maru Newby]

On Jun 18, 2013, at 5:30 PM, Perry Myers <pmyers at redhat.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/18/2013 05:03 PM, Forrest Taylor wrote:
>> Perry,
>> 
>> I was playing with the 2013-06-18.1 puddle and I noticed when I
>> run packstack, OpenStack Networking is used by default.  However,
>> there are no routers, networks or subnets configured.  Are there
>> plans to enable a router, network and/or subnet in packstack?
> 
> That's a good question and one that we've been discussing a bit...
> 
> Packstack installs the services, and gets things set up so that an
> admin can then start creating tenants.
> 
> But, since Packstack doesn't know how many tenants you want to set up,
> or anything, it can't really know what networks and subnets you want
> created.
> 
> Typically the task of creating a tenant network/subnet/router would be
> done by a cloud administrator at the point at which they create a new
> tenant.  Right now, that would involve a sequence of manual steps.
> 
> It could be that an OpenStack management solution of some sort could
> help to automate those tasks (since they do span multiple components),
> or a simple script could help.
> 
> There has been talk about giving Packstack an option to create a
> single tenant, network, subnet by default.  This would be useful for
> both testing environments as well as allinone or demo installs.  I
> believe Maru (cc'd) has been working on changes to puppet modules to
> support this, and Terry/Ryan (cc'd) are working on integrating this
> into Packstack

I have submitted patches for all-in-one demo configuration to the stackforge puppet modules.  Once they are accepted the packstack integration can begin.

> 
> But this doesn't solve the more general issue of "after Packstack
> deployment, I create 10 new tenants... who/how does the network/subnet
> creation happen?"

>From my experience working for a service provider, provisioning was not as trivial as creating openstack resources.  Integration with a datacenter management tool and management of hardware resources such as switches and routers was also required.  Unless this is the exception rather than the norm - that provisioning is as much about integration as configuration - it will be a challenge to provide generally useful provisioning guidelines.


m.

> Right now, it's just documentation, but perhaps in the future there is
> a better solution.  Brent (cc'd) is helping to chase this down.
> 
> I've cc'd some folks that might be able to weigh in on this
> 
> Perry
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iEYEARECAAYFAlHA0WUACgkQxdKLkeZeTz0YDQCcCTg9I7CsWEvqi9M20/3ALhAW
> xIcAnRpa4qTDIB2SEN7XA0iuANJoIUoQ
> =7pcz
> -----END PGP SIGNATURE-----