Make importing of "local dependencies" consistent

Bug #1293743 reported by Jay Pipes on 2014-03-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
OpenStack Core Infrastructure

Bug Description

This bug was spurred by a conversation resulting from questions arising from

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.disk.vfs.guestfs)
* evzookeeper, zookeeper, and evzookeeper.membership
* iboot (nova.virt.baremetal)

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.

Sean Dague (sdague) wrote :

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.

Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → Wishlist
Sean Dague (sdague) on 2016-02-20
Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers