Make importing of "local dependencies" consistent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned | ||
OpenStack Core Infrastructure |
New
|
Undecided
|
Unassigned |
Bug Description
This bug was spurred by a conversation resulting from questions arising from https:/
http://
There are a number of places in Nova where a submodule depends on an external library, but that external library is not (for various reasons) in the global requirements file. Examples of these kind of external "local dependencies" include:
* libvirt (used in nova.virt.libvirt)
* guestfs (used in nova.virt.
* evzookeeper, zookeeper, and evzookeeper.
* iboot (nova.virt.
We should develop some documentation (in HACKING?) that discusses the appropriate way to import these "local dependencies", and then ensure each one in above list is done consistently.
Changed in nova: | |
status: | Confirmed → Won't Fix |
I am adding this to the OpenStack CI project because what I think this is about is common infrastructure for optional dependencies. Which I think we're discussing now. This will become more important for functional testing down the road.