OpenStack Compute (nova)

nova-volume support for physical volumes was removed

Bug #659571 reported by Ryan Lucio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Initially I discovered that the --storage_dev flag for nova-volume was not doing anything, and then after doing some research I saw that the whole support for physical volumes was removed during the ORM merge (revision 275 http://bazaar.launchpad.net/~hudson-openstack/nova/trunk/revision/275). This merge removed the nova/volume/service.py and attempted to move all of the functionality to the driver.py and manager.py. But the chunk of code that uses storage_dev and runs pvcreate and such was all lost. As best I can tell this was not intentional.

Revision history for this message
Jesse Andrews (anotherjesse) wrote :

It was intentional, but we should probably make it optional?

the thought was that a service shouldn't modify volumes, that it should be part of configuration of the system prior to installing nova-volume.

A reason for that: what happens if a machine has raid issues. nova-volume modifying the volume groups could cause further issues.

Revision history for this message
Jesse Andrews (anotherjesse) wrote :

It isn't that support for physical volumes was removed. It is that we don't automatically create the pv.

Ryan Lucio (rlucio)
Changed in nova:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.