Loadbalancing for instance storage paths
The default path of instance location is in /var/lib/
If you want LiveMigrations you are advised to have this directory on a centralized storage, for example on NFS - as explained here: http://
There might be good reasons for having more than 1 instance directory for VM deployments - for example:
- In a big lanscape you might want to have more than 1 central storage mounts, i.e. 2 NFS mounts
- In compute-nodes with multiple local raid arrays you want to distribute instances over all arrays
If you want to use more than 1 location you need:
- more directories below /var/lib/
- a patch for Openstack to deploy on the directory with the least utilization
Even better would be to have a modular scheduler integrated so that it would be flexible on which algorithm the scheduler chooses the instance directories - f.e. one target for high IO VMs etc ...
--> I already have a working implementation for scheduling instances over 2 directories based on utilization which I could commit.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Low
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Christian Baumann
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Not started
- Milestone target:
- None
- Started by
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
idea seems fine. Discussion of implementation can happen in the review.
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)idea seems fine. Discussion of implementation can happen in the review.
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
This blueprint is not complete after a good year or so, marking as Obsolete to tidy up the Nova backlog. --johnthetubaguy (20th April 2014)