openstack team mailing list archive

[Adam Gandelman <adamg@xxxxxxxxxxxxx>]

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/