Some great discussion going on here folks but, in an attempt to prevent this 
turning into a full-on Painting the Bike Shed debate, here are the assumptions 
I'm proceeding with:

1. Eventually there will be a "super tool" to aggregate the various services. 
It will be built/named later by someone.
2. Consensus seems to prefer "nova" as the Compute tool name. Based on this I'm 
keeping the package as python-novatools (the cmdline tool will be nova). 
Someone high up can put their foot down if this is wrong.
3. I'm going to move it from github to LP under Nova, fix the headers and apply 
co-BSD/Apache license.
4. There are lots of good ideas about ways to expand this tool, but right now 
it is what it is and I need it in trunk to keep Zones moving ahead for Cactus. 
(2 weeks left till Feature Freeze!!)  If someone wants to change it after, 
merge-props are always welcome.

Thanks everyone for your input.

Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is 
If you receive this transmission in error, please notify us immediately by 
at, and delete the original message. 
Your cooperation is appreciated.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to