Thanks Salvatore,
This is the kind of feedback I need. Putting tests in their respective
packages makes sense, and should be trivial. As for your other proposals:
1) Sounds good. I wasn't sure what exactly to call it, so 'core' seemed
like a good temporary name. I'll change it to 'quantum-server'.
2) I'll move those. Similarly, I was thinking about moving run_tests.py
to bin/quantum_tests or something.
I'll update the blueprint and make the discussed changes. Before long I
should have the 'quantum-server' packing fully working, and I'll send
out an update, because at that point you should be able to completely
install Quantum by package (I'll build some rpm binaries and include
them in the repo).
-Tyler
On 8/12/2011 3:39 PM, Salvatore Orlando wrote:
Hi Tyler,
Thanks for taking on the packaging work. The list of packages in your proposal
sounds good, I'm just not 100% sure whether we want tests in their own packages
or spread across the various packages, but I wouldn't mind if we had a package
specific for tests.
I have two "additional" proposals:
1) Since client tools are going into their own package, why don't we rename core into
"server"?
2) Binaries: cli.py and batch_setup.py are client binaries IMHO. I'd rather
have them in a bin directory in the client package (they're currently in
/quantum).
Regards,
Salvatore
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
