Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Robbie Williamson]

On 03/15/2012 10:17 AM, Robbie Williamson wrote:
> On 03/14/2012 11:42 AM, David Kranz wrote:
>> In case any one runs into this, there is a bug in the Precise upstart
>> package that causes a reboot after installing essex to result in a
>> kernel panic. I don't know exactly what in the openstack install process
>> triggers it but there is a PPA mentioned in comment #11 of this bug
>> ticket that fixes the problem after upgrading the upstart package:
>>
>> https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/935585
>>
> Thanks David, I'll see about getting the fixed version properly into
> Precise.
> 
FYI, I checked with our upstart maintainer and the fix should arrive in
Precise by tomorrow, Monday at the latest.

-Robbie



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Robbie Williamson]

On 03/14/2012 11:42 AM, David Kranz wrote:
> In case any one runs into this, there is a bug in the Precise upstart
> package that causes a reboot after installing essex to result in a
> kernel panic. I don't know exactly what in the openstack install process
> triggers it but there is a PPA mentioned in comment #11 of this bug
> ticket that fixes the problem after upgrading the upstart package:
> 
> https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/935585
> 
Thanks David, I'll see about getting the fixed version properly into
Precise.

-Robbie

-- 
Robbie Williamson 
robbiew[irc.freenode.net]

"Don't make me angry...you wouldn't like me when I'm angry."
 -Bruce Banner

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Joseph Heck]

Yeah, one service tenant, and then service accounts for each of nova, glance, 
quantum, swift. I've got a review that's updating this detail in the keystone 
docs right now (https://review.openstack.org/#change,5348)

The catalog can be either the template (in which case, you don't use commands, 
you just edit the template) or the SQL based catalog (where you do use the 
commands)

-joe


On Mar 14, 2012, at 9: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
> 
> On Tue, Mar 13, 2012 at 8:59 PM, Justin Shepherd  
> 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 ) 
>>> - 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.  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 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
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Justin Shepherd]

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 
mailto:jshep...@rackspace.com>> 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 ) - 
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.  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 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
Post to : 
openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: 
https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Anne Gentle]

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

On Tue, Mar 13, 2012 at 8:59 PM, Justin Shepherd 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  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.  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.comare 
> *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
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[David Kranz]

In case any one runs into this, there is a bug in the Precise upstart 
package that causes a reboot after installing essex to result in a 
kernel panic. I don't know exactly what in the openstack install process 
triggers it but there is a PPA mentioned in comment #11 of this bug 
ticket that fixes the problem after upgrading the upstart package:


https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/935585

 -David

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Joseph Heck]

Those were great bugs too - sorry you hit them, but thanks to you and Jay for 
reporting them in! We're working on them now!

-joe

On Mar 14, 2012, at 1:45 AM, Kevin Jackson wrote:
> Shep,
> Those steps are great. I'll be running through them, the devstack and any 
> other info I've collated and update the bug I originally raised that caused 
> me the pain that tipped me over the edge 
> (https://bugs.launchpad.net/glance/+bug/953989)
> 
> Adam, the other bugs raised in the last day regarding my issues where raised 
> by jaypipes when helping me troubleshoot my install : 
> https://bugs.launchpad.net/keystone/+bug/954089 and 
> https://bugs.launchpad.net/keystone/+bug/954087
> 
> Regards,
> 
> Kev
> 
> On 14 March 2012 01:59, Justin Shepherd  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 ) 
>>> - 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.  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 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
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> Kevin Jackson
> @itarchitectkev
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Shep,
Those steps are great. I'll be running through them, the devstack and any
other info I've collated and update the bug I originally raised that caused
me the pain that tipped me over the edge (
https://bugs.launchpad.net/glance/+bug/953989)

Adam, the other bugs raised in the last day regarding my issues where
raised by jaypipes when helping me troubleshoot my install :
https://bugs.launchpad.net/keystone/+bug/954089 and
https://bugs.launchpad.net/keystone/+bug/954087

Regards,

Kev

On 14 March 2012 01:59, Justin Shepherd  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  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.  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.comare 
> *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
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>


-- 
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Yes, I raise all bugs I find. I want these fixed as much as the next guy.
I'm on my mob, so don't easily have nums to hand.

Regards,
Kev
On Mar 13, 2012 10: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  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.  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.comare 
> *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
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Justin Shepherd]

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 ) - 
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.  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 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
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Adam Gandelman]

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 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 .  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 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
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Joshua Harlow]

Just my 2 cents.

Shouldn't openstack be dependent only on a known set of package versions and 
not a distro?

It seems like it should be the job of openstack to define those versions and 
let the distro's match that as they choice.

If 12.04 matches these versions, then it should work, if something else matches 
these versions then that's fine also.

That would make me happy, and is sort of what devstackPY is doing right now 
(defining that concrete list).

That list seems like it should be maintained elsewhere though (and devstackPY 
should just reference it - ie the master list from a url or something).

On 3/13/12 1:53 PM, "Kevin Jackson"  wrote:

Adam (and others I've not instantly replied to),
Thanks for the reply.  I understand that OpenStack (moving target) on Ubuntu 
(moving target) is no mean feat, but I no doubt expect a lot of people are in 
the same boat as me.  Ubuntu (and other distros) have set a certain level of 
expectation for installation of applications.  Whilst OpenStack is being 
developed, a lot of people's entry into OpenStack is through deb packages (or 
) - 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  .  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).

Adam, your email is very beneficial and very much appreciated.  Ubuntu 12.04 
LTS still seems a logical installation choice and its a release we've been 
waiting for.  I'm going to say that from the little guy (who are numerous and 
less vocal).  Orchestra and Juju was always on the cards at some point for me.

This email thread has actually turned frustration into optimism again.  I might 
actually break out into a smile...  The support has been nothing short of 
exceptional.
The key thing though is that OpenStack does work and people (a lot of people) 
want to make it work.  Of course I'll be happier once I have a working 
installation again.
Today has seen a couple of bugs come out the woodwork, and bugs in my own 
methods.  Any positive to come out of this gets me (and, more importantly to 
the community, everyone else who has felt equally frustrated) come closer to an 
end product.

To everyone - thanks.  Think its going to be a large bar tab at this rate.

As an update, the crux of my issues seems to stem around the change to and in 
keystone-light.  Whether the bugs raised today hint at this (both code and user 
error), the difference between a working devstack deployment and Ubuntu's seem 
possibly related to the catalog driver method (template file vs sql).  
Hopefully having a working devstack vs a Ubuntu 12.04 install will clear this 
up.

Thanks once again.

Kev :)

On 13 March 2012 18:51, Adam Gandelman  wrote:

Hey Kevin-

Sorry to hear about your troubles.  I know I was similarly frustrated getting 
my feet wet with Openstack during the diablo / oneiric cycle.  Without knowing 
details of every problem you've hit in your Ubuntu testing, its difficult to 
give you simple answers to get you up and going.  I  can try to offer some 
assurances that I hope boost your perception of Openstack, specifically 
Openstack-on-Ubuntu.

We're doing *a lot* of testing around Openstack.  If you need some proof that 
this stuff *actually works*, please see our Jenkins dashboard [1].  Note that 
this testing takes place across a cluster of physical machines, not an 
all-in-one-virtual-machine.  There are several goals here:

  - ensure our packages correctly install the components onto the distro. [2]
  - ensure our Juju charms are kept up to date with the latest 
deployment-related configuration changes [3]
  - ensure Openstack still works [4]

Assuming all of the above is still true, we upload a weekly snapshot of Essex 
(all components) into the Ubuntu archive every Friday.  This upload contains a 
weeks worth of packaging updates, configuration changes and bug fixes.  The end 
goal here is to help make testing the development release of Openstack on the 
development release of Ubuntu a stable yet bleeding-edge experience.  That 
said, Openstack is still very much a moving target.  Lots of things change in a 
weeks time--as evidenced by the Keystone Lite migration, among other things.  
Unfortunately, documentation tends to lag behind (if it exists at all).

I'll be the first to admit that none of this stuff is easy.  Unless you or your 
CI robots are spending a good deal of the day tracking upstream development 
across all components, getting close-to-trunk Openstack running is an extremely 
daunting task.  Speaking for Ubuntu, I expect we'll have documentation added to 
the Server Guide or elsewhere as the Essex cycle draws to a close and we know 
*exactly* what we're shipping in Precise.  Until then, we certainly appr

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Adam (and others I've not instantly replied to),
Thanks for the reply.  I understand that OpenStack (moving target) on
Ubuntu (moving target) is no mean feat, but I no doubt expect a lot of
people are in the same boat as me.  Ubuntu (and other distros) have set a
certain level of expectation for installation of applications.  Whilst
OpenStack is being developed, a lot of people's entry into OpenStack is
through deb packages (or ) -
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.  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).

Adam, your email is very beneficial and very much appreciated.  Ubuntu
12.04 LTS still seems a logical installation choice and its a release we've
been waiting for.  I'm going to say that from the little guy (who are
numerous and less vocal).  Orchestra and Juju was always on the cards at
some point for me.

This email thread has actually turned frustration into optimism again.  I
might actually break out into a smile...  The support has been nothing
short of exceptional.
The key thing though is that OpenStack does work and people (a lot of
people) want to make it work.  Of course I'll be happier once I have a
working installation again.
Today has seen a couple of bugs come out the woodwork, and bugs in my own
methods.  Any positive to come out of this gets me (and, more importantly
to the community, everyone else who has felt equally frustrated) come
closer to an end product.

To everyone - thanks.  Think its going to be a large bar tab at this rate.

As an update, the crux of my issues seems to stem around the change to and
in keystone-light.  Whether the bugs raised today hint at this (both code
and user error), the difference between a working devstack deployment and
Ubuntu's seem possibly related to the catalog driver method (template file
vs sql).  Hopefully having a working devstack vs a Ubuntu 12.04 install
will clear this up.

Thanks once again.

Kev :)

On 13 March 2012 18:51, Adam Gandelman  wrote:

>
> Hey Kevin-
>
> Sorry to hear about your troubles.  I know I was similarly frustrated
> getting my feet wet with Openstack during the diablo / oneiric cycle.
>  Without knowing details of every problem you've hit in your Ubuntu
> testing, its difficult to give you simple answers to get you up and going.
>  I  can try to offer some assurances that I hope boost your perception of
> Openstack, specifically Openstack-on-Ubuntu.
>
> We're doing *a lot* of testing around Openstack.  If you need some proof
> that this stuff *actually works*, please see our Jenkins dashboard [1].
>  Note that this testing takes place across a cluster of physical machines,
> not an all-in-one-virtual-machine.  There are several goals here:
>
>  - ensure our packages correctly install the components onto the distro.
> [2]
>  - ensure our Juju charms are kept up to date with the latest
> deployment-related configuration changes [3]
>  - ensure Openstack still works [4]
>
> Assuming all of the above is still true, we upload a weekly snapshot of
> Essex (all components) into the Ubuntu archive every Friday.  This upload
> contains a weeks worth of packaging updates, configuration changes and bug
> fixes.  The end goal here is to help make testing the development release
> of Openstack on the development release of Ubuntu a stable yet
> bleeding-edge experience.  That said, Openstack is still very much a moving
> target.  Lots of things change in a weeks time--as evidenced by the
> Keystone Lite migration, among other things.  Unfortunately, documentation
> tends to lag behind (if it exists at all).
>
> I'll be the first to admit that none of this stuff is easy.  Unless you or
> your CI robots are spending a good deal of the day tracking upstream
> development across all components, getting close-to-trunk Openstack running
> is an extremely daunting task.  Speaking for Ubuntu, I expect we'll have
> documentation added to the Server Guide or elsewhere as the Essex cycle
> draws to a close and we know *exactly* what we're shipping in Precise.
>  Until then, we certainly appreciate your patience, testing and any bug
> reports can you supply.
>
> -Adam
>
> PS: If you're interested in Juju or how this is all deployed and
> orchestrated, please see the Juju stuff at the tail end of the deployment
> test run [3].
>
>
> Some links to automated builds, deploys and tests of Essex on Precise as
> of this morning:
> [1] 
> https://jenkins.qa.ubuntu.com/**view/Precise%20OpenStack%**20Testing/
> [2] https://jenkins.qa.ubuntu.com/**view/Precise%20OpenStack%**
> 20Testing/job/precise-**openstack-essex-glance-trunk/**118/console

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Adam Gandelman]

On 03/13/2012 02:28 AM, Kevin Jackson wrote:



I have tried the following package/scripted installations:

1) Ubuntu 11.10 with Diablo (Nova PPA) - some degree of success - 
failures around Keystone and EC2 API
2) Ubuntu 11.10 with Managedit PPA - better degree of success, but no 
EC2 compatibility and some bug fixes not back-ported
3) Ubuntu 12.04 (various releases) with Ubuntu packages - no success 
apart from getting Keystone to do some things, but failing to get 
services to use Keystone.
4) Ubuntu 11.10 with Devstack (tried yesterday - unfortunately failed 
[specific reason escapes me, I'll try another install today, but was 
around nova compute failing to start])


I nearly got 12.04 working with Essex but then Keystone changed to 
Keystone light.  This also raised concerns with us that between 
Essex-3 and Essex-4 something as fundamental as Keystone changed and 
ever since then has formed the crux of my problems.
It doesn't help that the documentation @ 
http://keystone.openstack.org/ differs from 
http://docs.openstack.org/trunk/openstack-compute/install/content/identity-configure-keystone.html. 
 I also see conflicting advice on where Keystone fits - not only is 
the documentation different depending on where you enter the 
websites/search but even the Forum has Keystone mentioned under 
"Futurestack".  Is Keystone pinnacle to an Essex release?


I even tried the devstack method of installation thinking this should 
be the safest option and this failed.  I'll try this again though to 
help here rather than just say it failed.  On looking at how Keystone 
is implemented, I see differences in configuration which I'm unsure 
what they are (e.g. the service catalog - devstack has a text based 
catalog and referenced directly in keystone.conf, Ubuntu's are SQL 
based - on trying the devstack config, Keystone fails to start under 
Ubuntu 12.04 for example).  I also noticed the nova.conf in devstack 
differs wildly in format to that of Ubuntu following the format for 
the rest of the configs - is this something nova is moving to?




Hey Kevin-

Sorry to hear about your troubles.  I know I was similarly frustrated 
getting my feet wet with Openstack during the diablo / oneiric cycle.  
Without knowing details of every problem you've hit in your Ubuntu 
testing, its difficult to give you simple answers to get you up and 
going.  I  can try to offer some assurances that I hope boost your 
perception of Openstack, specifically Openstack-on-Ubuntu.


We're doing *a lot* of testing around Openstack.  If you need some proof 
that this stuff *actually works*, please see our Jenkins dashboard [1].  
Note that this testing takes place across a cluster of physical 
machines, not an all-in-one-virtual-machine.  There are several goals here:


  - ensure our packages correctly install the components onto the 
distro. [2]
  - ensure our Juju charms are kept up to date with the latest 
deployment-related configuration changes [3]

  - ensure Openstack still works [4]

Assuming all of the above is still true, we upload a weekly snapshot of 
Essex (all components) into the Ubuntu archive every Friday.  This 
upload contains a weeks worth of packaging updates, configuration 
changes and bug fixes.  The end goal here is to help make testing the 
development release of Openstack on the development release of Ubuntu a 
stable yet bleeding-edge experience.  That said, Openstack is still very 
much a moving target.  Lots of things change in a weeks time--as 
evidenced by the Keystone Lite migration, among other things.  
Unfortunately, documentation tends to lag behind (if it exists at all).


I'll be the first to admit that none of this stuff is easy.  Unless you 
or your CI robots are spending a good deal of the day tracking upstream 
development across all components, getting close-to-trunk Openstack 
running is an extremely daunting task.  Speaking for Ubuntu, I expect 
we'll have documentation added to the Server Guide or elsewhere as the 
Essex cycle draws to a close and we know *exactly* what we're shipping 
in Precise.  Until then, we certainly appreciate your patience, testing 
and any bug reports can you supply.


-Adam

PS: If you're interested in Juju or how this is all deployed and 
orchestrated, please see the Juju stuff at the tail end of the 
deployment test run [3].



Some links to automated builds, deploys and tests of Essex on Precise as 
of this morning:

[1] https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/
[2] 
https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/job/precise-openstack-essex-glance-trunk/118/console
[3] 
https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/job/precise-openstack-essex-deploy/18232/console
[4] 
https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/job/precise-openstack-essex-test/473/



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Joshua Harlow]

If u feel like it.

https://github.com/yahoo/Openstack-DevstackPy/wiki

Try it out :-)

On 3/13/12 8:29 AM, "Kevin Jackson"  wrote:

Thanks Marton,
I'm just running through another devstack install now.  This failed for me when 
I followed the instructions yesterday.  Yours are in more detail so hopefully 
some quirk of my environment might've caused an issue (don't see why, but not 
ruling anything out).

My goal is a working example that I can then roll out into the datacenter.  So 
while devstack gets me an installation, it will just give the confidence that 
OpenStack is real.  I'd happily take that at the moment, though.
The current work I'm doing is having 2 machines in front of me: one running 
devstack on 11.10 and the other running E4 on 12.04 B1.  I can then start 
troubleshooting a reference set up to one that  is closer to my goal.

Cheers,

Kev

On 13 March 2012 15:20, Marton Kiss  wrote:
Hi Kevin,

I like suggest you to start with devstack first. It is the shortest
way if you like to deploy a working openstack on a single machine
(takes just a few minutes). Anyway if you like to see a different
deployment scenario, it requires a proper planning and more time. In
the last two days I've deployed Essex and Diablo using devstack, both
of them works well.

Essex on Ubuntu 12.04 Precise
requires a server deployment with openssh enabled

as root user:
adduser stack
apt-get install sudo -y
echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers

after that, login as stack user:

sudo apt-get install git -y
git clone git://github.com/cloudbuilders/devstack.git 

cd devstack

create localrc file:
LIBVIRT_TYPE=qemu
FLOATING_RANGE=192.168.122.224/28 
FIXED_RANGE=10.0.0.0/24 
FIXED_NETWORK_SIZE=256
FLAT_INTERFACE=eth0

You can comment out LIBVIRT_TYPE, I used this flag, because it was
deployed inside a kvm server.

I needed to modify the files/apts/glance file, and comment out the
python-argparse line, because it was provided by python himself, and
deployment stopped due an dependency issue.

python-eventlet
python-routes
python-greenlet
#python-argparse
python-sqlalchemy
python-wsgiref
python-pastedeploy
python-xattr
python-iso8601

After that, just start stack.sh:
FORCE=yes ./stack.sh

It will deploy the entire stack after a few minutes, and display
access accounts and urls for dashboard and api.

Diablo is the same process as above, with the following differences:
- deployed on oneiric server
- don't need to hack files/apt/glance
- requires an extra package if you like to use vncproxy, so don't
forget to apt-get install python-numpy.

My experience that success depends on proper OS environment and
openstack component configuration.

Regards,
  Márton Kiss, CTO
  Xemeti
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kiall Mac Innes]

On Tue, Mar 13, 2012 at 3:20 PM, Marton Kiss  wrote:

>
> My experience that success depends on proper OS environment and
> openstack component configuration.
>

Yup - I've also found from #openstack that anytime anybody attempts method
A, then method B without a complete operating system re-install, things go
haywire.

Don't get me wrong, its more than possible to switch methods without a
re-install.. But people often expect "apt-get purge nova" to remove
everything, forgetting about packages like "python-nova".

Or, they run "python setup.py install" and forget to clear everything out
of /usr/local before attempting a package install..

I'm hoping with the 12.04 and Essex releases, non-developers needing to use
DevStack or git clones will be a thing of the past.. An unscientific
estimate of mine is, over 50% of the people asking for help on #openstack
are due to having multiple copies, and often versions of the components
installed. Usually caused by using mix of devstack, random git-clones, and
native package installs.

0.02c...

Kiall
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Thanks Marton,
I'm just running through another devstack install now.  This failed for me
when I followed the instructions yesterday.  Yours are in more detail so
hopefully some quirk of my environment might've caused an issue (don't see
why, but not ruling anything out).

My goal is a working example that I can then roll out into the datacenter.
 So while devstack gets me an installation, it will just give the
confidence that OpenStack is real.  I'd happily take that at the moment,
though.
The current work I'm doing is having 2 machines in front of me: one running
devstack on 11.10 and the other running E4 on 12.04 B1.  I can then start
troubleshooting a reference set up to one that  is closer to my goal.

Cheers,

Kev

On 13 March 2012 15:20, Marton Kiss  wrote:

> Hi Kevin,
>
> I like suggest you to start with devstack first. It is the shortest
> way if you like to deploy a working openstack on a single machine
> (takes just a few minutes). Anyway if you like to see a different
> deployment scenario, it requires a proper planning and more time. In
> the last two days I've deployed Essex and Diablo using devstack, both
> of them works well.
>
> Essex on Ubuntu 12.04 Precise
> requires a server deployment with openssh enabled
>
> as root user:
> adduser stack
> apt-get install sudo -y
> echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
>
> after that, login as stack user:
>
> sudo apt-get install git -y
> git clone git://github.com/cloudbuilders/devstack.git
> cd devstack
>
> create localrc file:
> LIBVIRT_TYPE=qemu
> FLOATING_RANGE=192.168.122.224/28
> FIXED_RANGE=10.0.0.0/24
> FIXED_NETWORK_SIZE=256
> FLAT_INTERFACE=eth0
>
> You can comment out LIBVIRT_TYPE, I used this flag, because it was
> deployed inside a kvm server.
>
> I needed to modify the files/apts/glance file, and comment out the
> python-argparse line, because it was provided by python himself, and
> deployment stopped due an dependency issue.
>
> python-eventlet
> python-routes
> python-greenlet
> #python-argparse
> python-sqlalchemy
> python-wsgiref
> python-pastedeploy
> python-xattr
> python-iso8601
>
> After that, just start stack.sh:
> FORCE=yes ./stack.sh
>
> It will deploy the entire stack after a few minutes, and display
> access accounts and urls for dashboard and api.
>
> Diablo is the same process as above, with the following differences:
> - deployed on oneiric server
> - don't need to hack files/apt/glance
> - requires an extra package if you like to use vncproxy, so don't
> forget to apt-get install python-numpy.
>
> My experience that success depends on proper OS environment and
> openstack component configuration.
>
> Regards,
>  Márton Kiss, CTO
>  Xemeti
>
> --
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Marton Kiss]

Hi Kevin,

I like suggest you to start with devstack first. It is the shortest
way if you like to deploy a working openstack on a single machine
(takes just a few minutes). Anyway if you like to see a different
deployment scenario, it requires a proper planning and more time. In
the last two days I've deployed Essex and Diablo using devstack, both
of them works well.

Essex on Ubuntu 12.04 Precise
requires a server deployment with openssh enabled

as root user:
adduser stack
apt-get install sudo -y
echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers

after that, login as stack user:

sudo apt-get install git -y
git clone git://github.com/cloudbuilders/devstack.git
cd devstack

create localrc file:
LIBVIRT_TYPE=qemu
FLOATING_RANGE=192.168.122.224/28
FIXED_RANGE=10.0.0.0/24
FIXED_NETWORK_SIZE=256
FLAT_INTERFACE=eth0

You can comment out LIBVIRT_TYPE, I used this flag, because it was
deployed inside a kvm server.

I needed to modify the files/apts/glance file, and comment out the
python-argparse line, because it was provided by python himself, and
deployment stopped due an dependency issue.

python-eventlet
python-routes
python-greenlet
#python-argparse
python-sqlalchemy
python-wsgiref
python-pastedeploy
python-xattr
python-iso8601

After that, just start stack.sh:
FORCE=yes ./stack.sh

It will deploy the entire stack after a few minutes, and display
access accounts and urls for dashboard and api.

Diablo is the same process as above, with the following differences:
- deployed on oneiric server
- don't need to hack files/apt/glance
- requires an extra package if you like to use vncproxy, so don't
forget to apt-get install python-numpy.

My experience that success depends on proper OS environment and
openstack component configuration.

Regards,
  Márton Kiss, CTO
  Xemeti

2012/3/13 Justin Shepherd :
> Kevin.. would like to help you get this working.. and I understand the
> confusion as I recently got all or our chef recipes in shape for RC1 and had
> to work through the Keystone Light migration.
>
> 1. Where are you in the setup process?
>
> 2. Do you think you have a working Kesytone?
>
> 3. What services are you having issues with keystone integration (Nova,
> Glance, Swift)
>
> Thanks,
> Shep
>
> Kevin.. wanted to reach out to you off list for a sec.. I would be more than
> happy to help you get through this.. as I recently got all or our chef
> recipes in shape for RC1 and had to work through the Keystone Light
> migration.
>
> Couple of questions..
>
> 1. Where are you in the install process..
> - Do you think you have a working keystone?
> - Are you running into issues with Glance working with keystone?
>
> Let me know how i can hep
> On Mar 13, 2012, at 8:00 AM, Kevin Jackson wrote:
>
> Thanks a lot for the points Andi (and the links), but not to stray away from
> my original post: I don't want complexity at this stage - I want a single
> server that works.  I haven't even got that.
> I had a multi node set up working (to some degree of butchery) of an early
> Essex-1 release using Orchestra, PXE booting and doing appropriate
> post-configuration, if a little bit of a hack.  We're a modest size digital
> hosting environment - introducing alternative PXE booting and config
> management systems ontop of something that is already causing us pain isn't
> something we're looking at right now.  Given a fairly slick PXE boot
> environment already across multiple datacentres of the rest of our kit means
> we can move to using this for OpenStack.  That's an aside - I mentioned
> prod, but not confuse a way of rolling this out in our datacentres.
>
> The issues stem from a basic install.  I'd love to chat about bare-metal
> provisioning issues as it means I've got OpenStack running.  I haven't.
>  Yet.
> I've raised a bug just now (https://bugs.launchpad.net/glance/+bug/953989)
> which might shed light on my issues as it's possible its not a bug, but
> process/config issue.  This would be great to hear as it means there's an
> easy fix.
> Given that keystone underpins the rest of the environment means that my
> frustrations could be solved.
>
> Cheers,
>
> Kev
>
> On 13 March 2012 12:42, andi abes  wrote:
>>
>>
>> I first need to get to a world where a manual install works.
>> > I was getting desperate in having a demonstration available to those
>> > that
>> > pay my wages - the best candidate I had here were Kiall's managedit
>> > repo.
>> >  Great work (really), but it wouldn't have been anything to be
>> > considered
>> > for production for obvious reasons.
>
> --
> Kevin Jackson
> @itarchitectkev
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : http

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Justin Shepherd]

Kevin.. would like to help you get this working.. and I understand the 
confusion as I recently got all or our chef recipes in shape for RC1 and had to 
work through the Keystone Light migration.

1. Where are you in the setup process?

2. Do you think you have a working Kesytone?

3. What services are you having issues with keystone integration (Nova, Glance, 
Swift)

Thanks,
Shep

Kevin.. wanted to reach out to you off list for a sec.. I would be more than 
happy to help you get through this.. as I recently got all or our chef recipes 
in shape for RC1 and had to work through the Keystone Light migration.

Couple of questions..

1. Where are you in the install process..
- Do you think you have a working keystone?
- Are you running into issues with Glance working with keystone?

Let me know how i can hep
On Mar 13, 2012, at 8:00 AM, Kevin Jackson wrote:

Thanks a lot for the points Andi (and the links), but not to stray away from my 
original post: I don't want complexity at this stage - I want a single server 
that works.  I haven't even got that.
I had a multi node set up working (to some degree of butchery) of an early 
Essex-1 release using Orchestra, PXE booting and doing appropriate 
post-configuration, if a little bit of a hack.  We're a modest size digital 
hosting environment - introducing alternative PXE booting and config management 
systems ontop of something that is already causing us pain isn't something 
we're looking at right now.  Given a fairly slick PXE boot environment already 
across multiple datacentres of the rest of our kit means we can move to using 
this for OpenStack.  That's an aside - I mentioned prod, but not confuse a way 
of rolling this out in our datacentres.

The issues stem from a basic install.  I'd love to chat about bare-metal 
provisioning issues as it means I've got OpenStack running.  I haven't.  Yet.
I've raised a bug just now (https://bugs.launchpad.net/glance/+bug/953989) 
which might shed light on my issues as it's possible its not a bug, but 
process/config issue.  This would be great to hear as it means there's an easy 
fix.
Given that keystone underpins the rest of the environment means that my 
frustrations could be solved.

Cheers,

Kev

On 13 March 2012 12:42, andi abes 
mailto:andi.a...@gmail.com>> wrote:

I first need to get to a world where a manual install works.
> I was getting desperate in having a demonstration available to those that
> pay my wages - the best candidate I had here were Kiall's managedit repo.
>  Great work (really), but it wouldn't have been anything to be considered
> for production for obvious reasons.
--
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Jay Pipes]

On 03/13/2012 09:00 AM, Kevin Jackson wrote:

Thanks a lot for the points Andi (and the links), but not to stray away
from my original post: I don't want complexity at this stage - I want a
single server that works.  I haven't even got that.
I had a multi node set up working (to some degree of butchery) of an
early Essex-1 release using Orchestra, PXE booting and doing appropriate
post-configuration, if a little bit of a hack.  We're a modest size
digital hosting environment - introducing alternative PXE booting and
config management systems ontop of something that is already causing us
pain isn't something we're looking at right now.  Given a fairly slick
PXE boot environment already across multiple datacentres of the rest of
our kit means we can move to using this for OpenStack.  That's an aside
- I mentioned prod, but not confuse a way of rolling this out in our
datacentres.

The issues stem from a basic install.  I'd love to chat about bare-metal
provisioning issues as it means I've got OpenStack running.  I haven't.
  Yet.
I've raised a bug just now
(https://bugs.launchpad.net/glance/+bug/953989) which might shed light
on my issues as it's possible its not a bug, but process/config issue.
  This would be great to hear as it means there's an easy fix.
Given that keystone underpins the rest of the environment means that my
frustrations could be solved.


Sorry to hear about your install troubles, Kevin! I've added a reply to 
that bug report above that should get you in better shape.


-jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Thanks a lot for the points Andi (and the links), but not to stray away
from my original post: I don't want complexity at this stage - I want a
single server that works.  I haven't even got that.
I had a multi node set up working (to some degree of butchery) of an early
Essex-1 release using Orchestra, PXE booting and doing appropriate
post-configuration, if a little bit of a hack.  We're a modest size digital
hosting environment - introducing alternative PXE booting and config
management systems ontop of something that is already causing us pain isn't
something we're looking at right now.  Given a fairly slick PXE boot
environment already across multiple datacentres of the rest of our kit
means we can move to using this for OpenStack.  That's an aside - I
mentioned prod, but not confuse a way of rolling this out in our
datacentres.

The issues stem from a basic install.  I'd love to chat about bare-metal
provisioning issues as it means I've got OpenStack running.  I haven't.
 Yet.
I've raised a bug just now (https://bugs.launchpad.net/glance/+bug/953989)
which might shed light on my issues as it's possible its not a bug, but
process/config issue.  This would be great to hear as it means there's an
easy fix.
Given that keystone underpins the rest of the environment means that my
frustrations could be solved.

Cheers,

Kev

On 13 March 2012 12:42, andi abes  wrote:

>
> I first need to get to a world where a manual install works.
> > I was getting desperate in having a demonstration available to those that
> > pay my wages - the best candidate I had here were Kiall's managedit repo.
> >  Great work (really), but it wouldn't have been anything to be considered
> > for production for obvious reasons.
>
-- 
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[andi abes]

On Tue, Mar 13, 2012 at 7:43 AM, Kevin Jackson
 wrote:
> Hi Andi,
> Sure - the methods aren't meant for automated production installs, but to
> get to a world where I can automate using Orchestra or variations on PXE
> booting,

Well.. setting up a distributed system where all the pieces connect,
is a bit more complex than a sequence of PXE boots, as the reminder of
your post identifies ;)


I first need to get to a world where a manual install works.
> I was getting desperate in having a demonstration available to those that
> pay my wages - the best candidate I had here were Kiall's managedit repo.
>  Great work (really), but it wouldn't have been anything to be considered
> for production for obvious reasons.
>
> I looked at Crowbar a few months back and tried to persevere with it, but it
> was very very clunky and not very friendly to use.  I couldn't customise it
> to my network requirements - which aren't anything out of the ordinary, but
> I needed customisation like VLAN IDs, etc.  The docs pointed to editing
> Barclamps.

You can look at it as add complexity, but the layer that crowbar adds
on top of the core packages is meant to solve the set of problems that
go beyond installing a single node. Like ensuring that the right nodes
end up on the right vlan and use the right gateway for that logical
network.

I would be interested to hear privately more about what you found
confusing and complex. And I'd admit that we've made strides in
publishing more guides, videos and advice (and heard pretty good
feedback).

An added complexity which I don't believe is necessary in a
> world where PXE booting an OS is simple and package installation is even
> simpler.  The crux of the challenge I need to solve is just OpenStack
> configuration but documentation lags development (naturally - not
> criticising) and comparing like-for-like hasn't worked for me (e.g. devstack
> configs are completely different to what, say, Ubuntu deb packages expect).
>

exactly. One thing to note though is that your comparison is not quite
fair. Package managers do a great job in installing a single machine.
They're not meant, nor really capable to deploy clusters of machines
without some layer of orchestration. I think that's actually your
expectation from the top of the email.

>From personal experience - to develop crowbar, I find myself reading
more .py files than .html/txt files... that's the world of agile
software development. If you want to take on orchestrating an
openstack deployment - I can share some good python resources.


> Given Canonical's backing of OpenStack I thought I was in good company.
>  After I've a working setup of installing Ubuntu onto a few nodes the next
> natural step would be to use Orchestra (or Cobbler itself which we currently
> use).
>

To be fair, canonical has been working on JUJU as a layer on top of
packages, to... orchestrate deployments.

> The issue I have is that all the components are installed without out error.

package installed is not equal to cluster deployed... sorry, just had
to hammer than nail.

>  I come to use it and keystone doesn't want to play ball with the other
> components.
> This leads me to believe it can be two things: misconfiguration or bugs.
>
> If its misconfiguration - excellent - I can fix that today if someone shares
> a script or steps to configure Keystone Light to work with the rest of the
> environment.

Assuming you're chef savvy, this might be useful:
https://github.com/dellcloudedge/barclamp-keystone/tree/release/essex-hack/master/chef/cookbooks/keystone


> In the meantime I'm assuming bugs as I'm not getting anywhere fast with what
> I currently *think* are the correct steps.
>


> Cheers,
>
> Kev
>
> On 13 March 2012 11:27, andi abes  wrote:
>>
>> Hi Kevin, sorry for the hard time you're having.
>> However, most of the methods you described, are NOT meant for
>> production deployments (not saying all, because I haven't tried
>> them all).
>> You might want to look at projects which aim to automate production
>> deployments.
>> I can point you to the one I'm working on (The diablo release is in
>> production in many installations,  The essex series is abit nascent,
>> but pretty far along). It's here [1]
>> You can also download ISO's from [2]
>> (the crowbar mailing list is here [3], so you can see what folks have
>> said, and check the wiki here [4])
>>
>> hope you have a more successful experience.
>>
>>
>> [1] http://github.com/dellcloudedge/crowbar
>> [2] http://crowbar.zehicle.com
>> [3] https://lists.us.dell.com/mailman/listinfo/crowbar
>> [4] http://github.com/dellcloudedge/crowbar/wiki
>>
>>
>> On Tue, Mar 13, 2012 at 6:27 AM, Kevin Jackson
>>  wrote:
>> > Cheers Padraig - I'll grab a Fedora install and compare notes.
>> > I guess if Fedora has an installation candidate, the problem is probably
>> > Ubuntu packaging - at least I can direct my issues at Ubuntu rather than
>> > OpenStack as a whole...
>> >
>> > Kev
>> >
>> >
>> > 2012/3/13 

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kiall Mac Innes]

Hi Kevin,

As others have said, I can only speak to what I'm familiar with ( the
Managed I.T. packages).

They should be fairly up-to-date, there has been very few bugfixes to the
stable branch that I'm aware of since I last updated the packages.

Re EC2 compatibility, they are as compatible as the Diablo release is - ie
it works fine for the vast majority of API calls. Are there any specific
issues you were having?

Anyway, Essex might be approaching the RC phase, but that doesn't mean the
various packages are! The packages will always take longer..

For Essex, DevStack on 11.10 is going to be the most reliable *test*
install and Ubuntu 12.04 *will be* the most reliable  (Ubuntu based)
production install IMO.

(Sorry for the top post, on my mobile!)

Thanks,
Kiall

Sent from my phone.
On Mar 13, 2012 9:30 a.m., "Kevin Jackson" 
wrote:

> Dear all,
> I had my first sleepless night last night after a conversation I had in
> work regarding an OpenStack installation.  We are a planning an OpenStack
> install but I've failed to demonstrate OpenStack running in our environment
> and yet packages are now being tagged up with RC.  As big a supporter as I
> am, I'm struggling with the justifications when I have nothing tangible to
> show.  The real questions are being posed to me on why we're looking at
> OpenStack and not CloudStack or Eucalyptus - they have installations that
> we can turn to.  I was hoping Essex would help answer these questions
> relatively simply, but the opposite has happened - I am struggling to get
> OpenStack Essex working under Ubuntu - 11.10 and 12.04.  There are a few
> issues I am hoping the community can address:
>
> 1) What is the preferred/recommended version of OpenStack to install if
> we're looking at production (and lets say production involves a plan of
> running a number of instances of a low impact application somewhere in the
> next few months - if there are a few bugs, that's ok).
> 2) What is the preferred/recommended Linux Distribution to install this on?
>
> OpenStack is  fast approaching RC status.  Release Candidate to me means
> that its nearly ready, but there could be some bugs that haven't been
> raised yet.  I haven't had a working Essex since Essex-1 - it isn't a
> release candidate for me.
>
> I have tried the following package/scripted installations:
>
> 1) Ubuntu 11.10 with Diablo (Nova PPA) - some degree of success - failures
> around Keystone and EC2 API
> 2) Ubuntu 11.10 with Managedit PPA - better degree of success, but no
> EC2 compatibility and some bug fixes not back-ported
> 3) Ubuntu 12.04 (various releases) with Ubuntu packages - no success apart
> from getting Keystone to do some things, but failing to get services to use
> Keystone.
> 4) Ubuntu 11.10 with Devstack (tried yesterday - unfortunately failed
> [specific reason escapes me, I'll try another install today, but was around
> nova compute failing to start])
>
> I nearly got 12.04 working with Essex but then Keystone changed to
> Keystone light.  This also raised concerns with us that between Essex-3 and
> Essex-4 something as fundamental as Keystone changed and ever since then
> has formed the crux of my problems.
> It doesn't help that the documentation @ 
> http://keystone.openstack.org/differs from
> http://docs.openstack.org/trunk/openstack-compute/install/content/identity-configure-keystone.html.
>  I also see conflicting advice on where Keystone fits - not only is the
> documentation different depending on where you enter the websites/search
> but even the Forum has Keystone mentioned under "Futurestack".  Is Keystone
> pinnacle to an Essex release?
>
> I even tried the devstack method of installation thinking this should be
> the safest option and this failed.  I'll try this again though to help here
> rather than just say it failed.  On looking at how Keystone is implemented,
> I see differences in configuration which I'm unsure what they are (e.g. the
> service catalog - devstack has a text based catalog and referenced directly
> in keystone.conf, Ubuntu's are SQL based - on trying the devstack config,
> Keystone fails to start under Ubuntu 12.04 for example).  I also noticed
> the nova.conf in devstack differs wildly in format to that of Ubuntu
> following the format for the rest of the configs - is this something nova
> is moving to?
>
> Now I'm pretty sure that OpenStack hasn't got RC status without it running
> in other people's environments - so I'd just love for you to share your
> details on how you have done this.  Is it all pull from source, install
> from source?  If that's the case - that's great as it means I can use the
> software, but it wouldn't be something I'd be doing in production on a
> modest number of machines - so the installation must come from packages
> eventually, somehow.
>
> Are my problems OpenStack's or Ubuntu's packaging?  I would love to speak
> to someone who has this running and direct my questions to the right place.
>  My aim is simple: I want a 

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Hi Andi,
Sure - the methods aren't meant for automated production installs, but to
get to a world where I can automate using Orchestra or variations on PXE
booting, I first need to get to a world where a manual install works.
I was getting desperate in having a demonstration available to those that
pay my wages - the best candidate I had here were Kiall's managedit repo.
 Great work (really), but it wouldn't have been anything to be considered
for production for obvious reasons.

I looked at Crowbar a few months back and tried to persevere with it, but
it was very very clunky and not very friendly to use.  I couldn't customise
it to my network requirements - which aren't anything out of the ordinary,
but I needed customisation like VLAN IDs, etc.  The docs pointed to editing
Barclamps.  An added complexity which I don't believe is necessary in a
world where PXE booting an OS is simple and package installation is even
simpler.  The crux of the challenge I need to solve is just OpenStack
configuration but documentation lags development (naturally - not
criticising) and comparing like-for-like hasn't worked for me (e.g.
devstack configs are completely different to what, say, Ubuntu deb packages
expect).

Given Canonical's backing of OpenStack I thought I was in good company.
 After I've a working setup of installing Ubuntu onto a few nodes the next
natural step would be to use Orchestra (or Cobbler itself which we
currently use).

The issue I have is that all the components are installed without out
error.  I come to use it and keystone doesn't want to play ball with the
other components.
This leads me to believe it can be two things: misconfiguration or bugs.

If its misconfiguration - excellent - I can fix that today if someone
shares a script or steps to configure Keystone Light to work with the rest
of the environment.
In the meantime I'm assuming bugs as I'm not getting anywhere fast with
what I currently *think* are the correct steps.

Cheers,

Kev

On 13 March 2012 11:27, andi abes  wrote:

> Hi Kevin, sorry for the hard time you're having.
> However, most of the methods you described, are NOT meant for
> production deployments (not saying all, because I haven't tried
> them all).
> You might want to look at projects which aim to automate production
> deployments.
> I can point you to the one I'm working on (The diablo release is in
> production in many installations,  The essex series is abit nascent,
> but pretty far along). It's here [1]
> You can also download ISO's from [2]
> (the crowbar mailing list is here [3], so you can see what folks have
> said, and check the wiki here [4])
>
> hope you have a more successful experience.
>
>
> [1] http://github.com/dellcloudedge/crowbar
> [2] http://crowbar.zehicle.com
> [3] https://lists.us.dell.com/mailman/listinfo/crowbar
> [4] http://github.com/dellcloudedge/crowbar/wiki
>
>
> On Tue, Mar 13, 2012 at 6:27 AM, Kevin Jackson
>  wrote:
> > Cheers Padraig - I'll grab a Fedora install and compare notes.
> > I guess if Fedora has an installation candidate, the problem is probably
> > Ubuntu packaging - at least I can direct my issues at Ubuntu rather than
> > OpenStack as a whole...
> >
> > Kev
> >
> >
> > 2012/3/13 Pádraig Brady 
> >>
> >> On 03/13/2012 09:28 AM, Kevin Jackson wrote:
> >> > Dear all,
> >> > I had my first sleepless night last night after a conversation I had
> in
> >> > work regarding an OpenStack installation.
> >>
> >> > Are my problems OpenStack's or Ubuntu's packaging?  I would love to
> >> > speak to someone who has this running and direct my questions to the
> right
> >> > place.
> >> > My aim is simple: I want a running OpenStack environment.
> >>
> >> I'm not familiar with ubuntu's packaging, but to allay your
> >> fears about openstack itself, we've recently had a successful Fedora
> >> test day testing out various functionality of Essex milestone 4
> >> including the new keystone.  I'm not suggesting you switch or
> >> anything, but you might be able to copy some of the configuration
> >> etc. from the steps detailed at:
> >>
> >> http://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day
> >>
> >> cheers,
> >> Pádraig.
> >
> >
> > --
> > Kevin Jackson
> > @itarchitectkev
> >
> > ___
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
> >
>



-- 
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[andi abes]

Hi Kevin, sorry for the hard time you're having.
However, most of the methods you described, are NOT meant for
production deployments (not saying all, because I haven't tried
them all).
You might want to look at projects which aim to automate production deployments.
I can point you to the one I'm working on (The diablo release is in
production in many installations,  The essex series is abit nascent,
but pretty far along). It's here [1]
You can also download ISO's from [2]
(the crowbar mailing list is here [3], so you can see what folks have
said, and check the wiki here [4])

hope you have a more successful experience.


[1] http://github.com/dellcloudedge/crowbar
[2] http://crowbar.zehicle.com
[3] https://lists.us.dell.com/mailman/listinfo/crowbar
[4] http://github.com/dellcloudedge/crowbar/wiki


On Tue, Mar 13, 2012 at 6:27 AM, Kevin Jackson
 wrote:
> Cheers Padraig - I'll grab a Fedora install and compare notes.
> I guess if Fedora has an installation candidate, the problem is probably
> Ubuntu packaging - at least I can direct my issues at Ubuntu rather than
> OpenStack as a whole...
>
> Kev
>
>
> 2012/3/13 Pádraig Brady 
>>
>> On 03/13/2012 09:28 AM, Kevin Jackson wrote:
>> > Dear all,
>> > I had my first sleepless night last night after a conversation I had in
>> > work regarding an OpenStack installation.
>>
>> > Are my problems OpenStack's or Ubuntu's packaging?  I would love to
>> > speak to someone who has this running and direct my questions to the right
>> > place.
>> > My aim is simple: I want a running OpenStack environment.
>>
>> I'm not familiar with ubuntu's packaging, but to allay your
>> fears about openstack itself, we've recently had a successful Fedora
>> test day testing out various functionality of Essex milestone 4
>> including the new keystone.  I'm not suggesting you switch or
>> anything, but you might be able to copy some of the configuration
>> etc. from the steps detailed at:
>>
>> http://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day
>>
>> cheers,
>> Pádraig.
>
>
> --
> Kevin Jackson
> @itarchitectkev
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Cheers Padraig - I'll grab a Fedora install and compare notes.
I guess if Fedora has an installation candidate, the problem is probably
Ubuntu packaging - at least I can direct my issues at Ubuntu rather than
OpenStack as a whole...

Kev


2012/3/13 Pádraig Brady 

> On 03/13/2012 09:28 AM, Kevin Jackson wrote:
> > Dear all,
> > I had my first sleepless night last night after a conversation I had in
> work regarding an OpenStack installation.
>
> > Are my problems OpenStack's or Ubuntu's packaging?  I would love to
> speak to someone who has this running and direct my questions to the right
> place.
> > My aim is simple: I want a running OpenStack environment.
>
> I'm not familiar with ubuntu's packaging, but to allay your
> fears about openstack itself, we've recently had a successful Fedora
> test day testing out various functionality of Essex milestone 4
> including the new keystone.  I'm not suggesting you switch or
> anything, but you might be able to copy some of the configuration
> etc. from the steps detailed at:
>
> http://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day
>
> cheers,
> Pádraig.


-- 
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Pádraig Brady]

On 03/13/2012 09:28 AM, Kevin Jackson wrote:
> Dear all,
> I had my first sleepless night last night after a conversation I had in work 
> regarding an OpenStack installation.

> Are my problems OpenStack's or Ubuntu's packaging?  I would love to speak to 
> someone who has this running and direct my questions to the right place.
> My aim is simple: I want a running OpenStack environment.

I'm not familiar with ubuntu's packaging, but to allay your
fears about openstack itself, we've recently had a successful Fedora
test day testing out various functionality of Essex milestone 4
including the new keystone.  I'm not suggesting you switch or
anything, but you might be able to copy some of the configuration
etc. from the steps detailed at:

http://fedoraproject.org/wiki/Test_Day:2012-03-08_OpenStack_Test_Day

cheers,
Pádraig.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] OpenStack Installation Woes - Need re-assurance and help.

[Kevin Jackson]

Dear all,
I had my first sleepless night last night after a conversation I had in
work regarding an OpenStack installation.  We are a planning an OpenStack
install but I've failed to demonstrate OpenStack running in our environment
and yet packages are now being tagged up with RC.  As big a supporter as I
am, I'm struggling with the justifications when I have nothing tangible to
show.  The real questions are being posed to me on why we're looking at
OpenStack and not CloudStack or Eucalyptus - they have installations that
we can turn to.  I was hoping Essex would help answer these questions
relatively simply, but the opposite has happened - I am struggling to get
OpenStack Essex working under Ubuntu - 11.10 and 12.04.  There are a few
issues I am hoping the community can address:

1) What is the preferred/recommended version of OpenStack to install if
we're looking at production (and lets say production involves a plan of
running a number of instances of a low impact application somewhere in the
next few months - if there are a few bugs, that's ok).
2) What is the preferred/recommended Linux Distribution to install this on?

OpenStack is  fast approaching RC status.  Release Candidate to me means
that its nearly ready, but there could be some bugs that haven't been
raised yet.  I haven't had a working Essex since Essex-1 - it isn't a
release candidate for me.

I have tried the following package/scripted installations:

1) Ubuntu 11.10 with Diablo (Nova PPA) - some degree of success - failures
around Keystone and EC2 API
2) Ubuntu 11.10 with Managedit PPA - better degree of success, but no
EC2 compatibility and some bug fixes not back-ported
3) Ubuntu 12.04 (various releases) with Ubuntu packages - no success apart
from getting Keystone to do some things, but failing to get services to use
Keystone.
4) Ubuntu 11.10 with Devstack (tried yesterday - unfortunately failed
[specific reason escapes me, I'll try another install today, but was around
nova compute failing to start])

I nearly got 12.04 working with Essex but then Keystone changed to Keystone
light.  This also raised concerns with us that between Essex-3 and Essex-4
something as fundamental as Keystone changed and ever since then has formed
the crux of my problems.
It doesn't help that the documentation @
http://keystone.openstack.org/differs from
http://docs.openstack.org/trunk/openstack-compute/install/content/identity-configure-keystone.html.
 I also see conflicting advice on where Keystone fits - not only is the
documentation different depending on where you enter the websites/search
but even the Forum has Keystone mentioned under "Futurestack".  Is Keystone
pinnacle to an Essex release?

I even tried the devstack method of installation thinking this should be
the safest option and this failed.  I'll try this again though to help here
rather than just say it failed.  On looking at how Keystone is implemented,
I see differences in configuration which I'm unsure what they are (e.g. the
service catalog - devstack has a text based catalog and referenced directly
in keystone.conf, Ubuntu's are SQL based - on trying the devstack config,
Keystone fails to start under Ubuntu 12.04 for example).  I also noticed
the nova.conf in devstack differs wildly in format to that of Ubuntu
following the format for the rest of the configs - is this something nova
is moving to?

Now I'm pretty sure that OpenStack hasn't got RC status without it running
in other people's environments - so I'd just love for you to share your
details on how you have done this.  Is it all pull from source, install
from source?  If that's the case - that's great as it means I can use the
software, but it wouldn't be something I'd be doing in production on a
modest number of machines - so the installation must come from packages
eventually, somehow.

Are my problems OpenStack's or Ubuntu's packaging?  I would love to speak
to someone who has this running and direct my questions to the right place.
 My aim is simple: I want a running OpenStack environment.

I appreciate that my concerns are possibly more to do with Ubuntu packaging
- but given that I was led to believe that a target in production would be
Ubuntu 12.04 LTS + OpenStack suggests that I'm hoping I'm in the right area
at least - and as an end user, not developer, it seems the correct place to
be - but its that last bit I'm struggling with - how to get OpenStack
running in the best way in a target production environment.

Cheers,

Kev
-- 
Kevin Jackson
@itarchitectkev
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp