Open Stack

Hello!

Getting the system setup to the point where you are able to run the unit tests is much less involved than a full deployment. We have written up (in-house) a pretty easy to follow set of instructions on how to do that for Quantum unit tests and it turns out to be quite straight forward, something you can just follow and 5 minutes later it's all done.

Not sure that it's worth it to re-factor the devstack scripts, since it is so much simpler.

Putting the necessary instructions on a wiki page would be a great start, for example.

Juergen


> -----Original Message-----
> From: Robert Collins [mailto:robertc at robertcollins.net]
> Sent: Wednesday, November 14, 2012 2:22 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] making the dev toolchain easier to bring
> together
> 
> At the moment its a bit of a black art getting setup so that
> ./run_tests.sh will work in e.g. nova.
> 
> (For instance, you need python-dev on Ubuntu, and there isn't, AFAICT,
> any documentation of that other than group-knowledge).
> 
> I'd like to encode this stuff in a repeatable form, so that one can
> run some hypothetical tool to get setup for developing on nova, or
> glance, or ...; with the knowledge about what is needed localised to
> the particular codebase (so that having pristine environments is
> easy).
> 
> As a strawman:
>  - pull the devstack code for interpreting operating system package
> dependencies out of devstack into an oslo tool
>  - create directories under tools/ in-tree that contain appropriate
> lists for the tree, split into three groups:
>    - build (enough to make an egg for redistribution, no more)
>    - test (needed to run tests)
>    - use (needed to use this)
> 
> The split of three is needed to deal with circular dependencies should
> they arise (you use build to build eggs for an arbitrary point in the
> cycle, then use test for everything else, and when you circle around,
> use the tested elements for the thing you just built to start with).
> 
> Then to get going on (say) nova, you would:
>  install the common oslo tool
>  clone nova
>  run oslo-os-deps install # or whatever we call it
>  ./run_tests.sh
>  $profit
> 
> This would also (if desired) allow shrinking this aspect out of
> devstack.
> 
> If this sounds good, I'll look closer at the devstack code to see if
> its sensible to factor it out, or do something similar but parallel.
> 
> -Rob
> 
> --
> Robert Collins <rbtcollins at hp.com>
> Distinguished Technologist
> HP Cloud Services
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev