<br><br><div class="gmail_quote">On Tue, Nov 13, 2012 at 8:22 PM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
At the moment its a bit of a black art getting setup so that<br>
./run_tests.sh will work in e.g. nova.<br>
<br>
(For instance, you need python-dev on Ubuntu, and there isn't, AFAICT,<br>
any documentation of that other than group-knowledge).<br></blockquote><div><br></div><div>Isn't devstack installing those packages?</div><div><br></div><div>Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I'd like to encode this stuff in a repeatable form, so that one can<br>
run some hypothetical tool to get setup for developing on nova, or<br>
glance, or ...; with the knowledge about what is needed localised to<br>
the particular codebase (so that having pristine environments is<br>
easy).<br>
<br>
As a strawman:<br>
- pull the devstack code for interpreting operating system package<br>
dependencies out of devstack into an oslo tool<br>
- create directories under tools/ in-tree that contain appropriate<br>
lists for the tree, split into three groups:<br>
- build (enough to make an egg for redistribution, no more)<br>
- test (needed to run tests)<br>
- use (needed to use this)<br>
<br>
The split of three is needed to deal with circular dependencies should<br>
they arise (you use build to build eggs for an arbitrary point in the<br>
cycle, then use test for everything else, and when you circle around,<br>
use the tested elements for the thing you just built to start with).<br>
<br>
Then to get going on (say) nova, you would:<br>
install the common oslo tool<br>
clone nova<br>
run oslo-os-deps install # or whatever we call it<br>
./run_tests.sh<br>
$profit<br>
<br>
This would also (if desired) allow shrinking this aspect out of devstack.<br>
<br>
If this sounds good, I'll look closer at the devstack code to see if<br>
its sensible to factor it out, or do something similar but parallel.<br>
<br>
-Rob<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Cloud Services<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br>