openstack team mailing list archive

[Chmouel Boudjnah <chmouel@xxxxxxxxxxx>]

Hi Thomas,

On Tue, Mar 20, 2012 at 4:40 PM, Thomas Goirand <thomas@xxxxxxxxxx> wrote:
> The same mess applies in the devstack not-for-XenServer. In some cases,
> some tools are apt-get installed. I can see for example 'apt-get install
> sudo'. But stack.sh assumes (god knows why) that "screen" is already

screen is installed via packages and devstack don't assume it's already
installed :

https://github.com/openstack-dev/devstack/blob/master/files/apts/general

> Frankly, this devstack stuff is just a big hack. Nothing is really
> structured with functions. It's not really possible to run the scripts
> twice either (it's not idempotent, AFAIC).

I haven't tested the xen support but for the default install, I have
quickly spawned a VM on my laptop, downloaded devstack and ran it twice
and except having to kill screen[1] between the two run it was actually
the right thing (ie: redone the configuration).

> I don't think anyway that if you are a developer, you will be working on
> absolutely all packages (nova, glance, keystone, swift, quantum...) that
> we have available in Openstack. In most cases, you'd be working on *one*
> of the Git checkout, and the rest of could well be downloaded and
> installed, either through the PPA, or from Ubuntu directly. So why using
> devstack which will checkout absolutely all components from Github? This
> doesn't make sense either. Also, if this continues, none of the
> developers will be testing the final result (eg: the packages).

we have the ENABLED_SERVICES= variable for that and we have lately
fixed a lot of those bugs.
(albeit it does indeed  check-in nova currently for all services which
is a bug that need to be
fixed).

Chmouel.

[1] Which devstack had kindly advised me to do.