openstack team mailing list archive

[Kevin Jackson <kevin@xxxxxxxxxxxxxxxxxxx>]

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 <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.  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 <adamg@xxxxxxxxxxxxx> 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/<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<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<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/<https://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/job/precise-openstack-essex-test/473/>
>
>


-- 
Kevin Jackson
@itarchitectkev