Monty Taylor
10372e7e9a
Loading install_requires with the contents of pip-requires isn't getting us any real beneift and is causing issues. a) It can conflict with installing nova into an environment where deps have been installed from packages (devstack) b) It breaks the ability to use -e git urls in pip-requires which we want to start using for python-novaclient and python-keystoneclient c) It causes spurious network traffic when we're trying to test things. At the same time, since we are not expecting anyone to install nova from setup.py for production, the normal benefit of the feature is not needed. Change-Id: I402f975c652dc1c2b54b0c362b8abbb6886f8844
The Choose Your Own Adventure README for Nova ============================================= You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs. To monitor it from a distance: follow `@openstack <http://twitter.com/openstack>`_ on twitter. To tame it for use in your own cloud: read http://docs.openstack.org To study its anatomy: read http://nova.openstack.org To dissect it in detail: visit http://github.com/openstack/nova To taunt it with its weaknesses: use http://bugs.launchpad.net/nova To watch it: http://jenkins.openstack.org To hack at it: read HACKING To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations