openstack team mailing list archive

[Justin Shepherd <jshepher@xxxxxxxxxxxxx>]

On Mar 14, 2012, at 11:57 AM, Anne Gentle wrote:

Hi Shep and others -
A couple of questions to enhance my understanding while I walk through this for the install doc.

Service Tenant - do you create just one service tenant to enclose all the service users?

Glance Service User - do you create a Nova Service User and a Swift Service User also?

files/default_catalog.templates - are your commands updating the template or a database? It this is a point of confusion. I guess I have to also add:
[catalog]
driver = keystone.catalog.backends.sql.Catalog


to keystone.conf in order to use a database backend for my service catalog?

Thanks for improving my mind map.

Anne

Anne,

I based the service tenant off what is done in devstack.. and it creates one service tenant that encloses all the service users.

Yes, i also create a nova and swift user that is part of the service tenant (also based on what is being done in devstack). In the example i set the name and password the same, but i generate separate passwords for each in actual deployments.

As for the default_catalog.templates, I am not making use of that file in any way. I am creating endpoints from the command line/api which populates the service catalog.. To be honest I also find this file confusing, and do not understand why or how you use it.

--shep


On Tue, Mar 13, 2012 at 8:59 PM, Justin Shepherd <jshepher@xxxxxxxxxxxxx<mailto:jshepher@xxxxxxxxxxxxx>> wrote:
Sent this to kevin earlier, thought i would throw it out to the list.. here are the steps i take to get a working keystone and glance on Ubuntu-12.04 using the ubuntu packages.

http://paste.openstack.org/show/9101/

These steps produce a working keystone and glance.. not 100% sure they are the most efficient steps, would be curious to hear from others if there is a better way.

--shep


On Mar 13, 2012, at 5:41 PM, Adam Gandelman wrote:

On 03/13/2012 01:53 PM, Kevin Jackson wrote:
Whilst OpenStack is being developed, a lot of people's entry into OpenStack is through deb packages (or <insert your fave package management in here>) - therefore Ubuntu becomes unofficial (but vocal) PR to OpenStack.  If the Ubuntu debs don't install, it becomes Plan B to install from somewhere else - even if that somewhere else is openstack.org<http://openstack.org/>.  When we view the pages of http://www.ubuntu.com/cloud there is little doubt that OpenStack is a 1st class citizen (Best-of-breed cloud infrastructure is built into every copy of Ubuntu).

Kevin-

As someone who helps maintain the Ubuntu packages, I'm curious to know when/what/where the problems you've hit installing packages. Do/did bug #s exist?  Can you please file bugs when you hit them?  We've been making an extra effort to ensure that the Openstack packages on archive.ubuntu.com<http://archive.ubuntu.com/> are *at least* installable without error at any given time.  Packaging bugs have slipped through into our weekly uploads, but we've been either catching them early or responding to any new relevant bug reports, and doing point uploads with fixes ASAP so things are installable until the next weekly upload.

I ask  anyone that is running into packaging problems: Please file bugs against the Ubuntu packages if you find they are failing to install.  They *will* get fixed!


Adam

_______________________________________________
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp


_______________________________________________
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp