Tracking shared storage in scheduler

Registered by Alex Xu

We should tracking the shared storage. There are some benefit for this:

1. we needn't specified 'on_shared_storage' parameter when evacuate. Also needn't specified 'block_migration' when live-migration.

2. We also can implement rescheduler when start stopped instance. Currently the start/stop instance won't release the instance resource on the compute node, also won't reschedule after start the stopped instance.

3. And when live-migrate and evacuate, scheduler can choice host that have shared-storage with previous host.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Alex Xu
Direction:
Needs approval
Assignee:
Alex Xu
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.