Block Device will be created by block-device-mappting option when vm created
it is a very simple logic.
This is a way.
Whenever you create an instance by options on demand , volume is created and attached at the same time.
This is different from Ephemeral of flavor.
Usage is as follows:
nova boot cosmos-0807_5 --image 394dd9fb-
(Format: <id>:[<
if If you do not have id. Volume will be created as input size and attached on created vm.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- inhye.park
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
- None
- Started by
- inhye.park
- Completed by
- Joe Gordon
Whiteboard
I am a little unclear on what you are proposing, are you saying that nova should be able to automatically create a cinder volume if you ask it to? We are trying to move away from having nova be a proxy to all services as much as possible and I this goes against that. I would rather see this implemented in the unified python-
I actually think that as far as nova is concerned, you should have to create the volume ahead of time and pass it in as a block device mapping when creating the instance. If you want to automate it, that's something outside of nova. It could be a client feature, I suppose. You could also look at this as a really simple orchestration (Heat) use case. --russellb
