yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #29197
[Bug 1430239] [NEW] Hyper-V: *DataRoot paths are not set for instances
Public bug reported:
The Nova Hyper-V Driver does not set the Data Root path locations for
the newly created instances to the same location as the instances. By
default. Hyper-V sets the location on C:\. This can cause issues for
small C:\ partitions, as some of these files can be large.
The path locations that needs to be set are: ConfigurationDataRoot,
LogDataRoot, SnapshotDataRoot, SuspendDataRoot, SwapFileDataRoot.
** Affects: nova
Importance: Undecided
Assignee: Dorin Paslaru (dpaslaru)
Status: New
** Description changed:
The Nova Hyper-V Driver does not set the Data Root path locations for
- the newly created instances to the same location as the instances. This
- can cause issues for small C:\ partitions, as some of these files can be
- large.
+ the newly created instances to the same location as the instances. By
+ default. Hyper-V sets the location on C:\. This can cause issues for
+ small C:\ partitions, as some of these files can be large.
The path locations that needs to be set are: ConfigurationDataRoot,
LogDataRoot, SnapshotDataRoot, SuspendDataRoot, SwapFileDataRoot.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1430239
Title:
Hyper-V: *DataRoot paths are not set for instances
Status in OpenStack Compute (Nova):
New
Bug description:
The Nova Hyper-V Driver does not set the Data Root path locations for
the newly created instances to the same location as the instances. By
default. Hyper-V sets the location on C:\. This can cause issues for
small C:\ partitions, as some of these files can be large.
The path locations that needs to be set are: ConfigurationDataRoot,
LogDataRoot, SnapshotDataRoot, SuspendDataRoot, SwapFileDataRoot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1430239/+subscriptions
Follow ups
References