Whole Host Allocation

Registered by Phil Day on 2013-05-06

Allow a tenant to allocate all of the capacity of a host for their exclusive use. The host remains part of the Nova configuration, i.e. this is different from bare metal provisioning in that the tenant is not getting access to the Host OS - just a dedicated pool of compute capacity. This gives the tenant guaranteed isolation for their instances, at the premium of paying for a whole host.

The blueprint achieve this by building on the existing host aggregates and filter scheduler.

Extending this further in the future could form the basis of hosted private clouds – i.e. schematics of having a private could without the operational overhead.

In effect what we are doing is to make host aggregates a user facing feature (with appropriate controls), and providing an anonymous host allocation mechanism

Blueprint information

Status:
Started
Approver:
Russell Bryant
Priority:
Undefined
Drafter:
Phil Day
Direction:
Needs approval
Assignee:
Phil Day
Definition:
Drafting
Series goal:
None
Implementation:
Slow progress
Milestone target:
None
Started by
Phil Day on 2013-07-24

Related branches

Sprints

Whiteboard

Resetting priority, we need to review what the next steps are, and then review that design -- johnthetubaguy

Gerrit topic: https://review.openstack.org/#q,topic:bp/whole-host-allocation,n,z

Addressed by: https://review.openstack.org/38156
    Whole Host Allocation - Pcloud framework

Addressed by: https://review.openstack.org/39055
    Add Pcloud Flavors

Addressed by: https://review.openstack.org/47091
    Add hosts to pcloud.

[jpretorius 2013/12/13]
Once the base code is done, please add something to Horizon to expose this via the UI. My thinking is:
 - During instance creation, allow the deployment to a pcloud that the end-user has access to
 - When listing instances, show the pclouds that instances are hosted in
 - When viewing the instance details, show the pcloud that an instance is hosted in
Also, please test that the scheduler allows an end-user to migrate/live-migrate an instance from one pcloud to another.

    This blueprint has been deferred from the icehouse-3 milestone to Juno because it missed the "feature proposal freeze" deadline. https://wiki.openstack.org/wiki/Icehouse_Release_Schedule --russellb

Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyResetting priority, we need to review what the next steps are, and then review that design -- johnthetubaguy

Gerrit topic: https://review.openstack.org/#q,topic:bp/whole-host-allocation,n,z

Addressed by: https://review.openstack.org/38156
    Whole Host Allocation - Pcloud framework

Addressed by: https://review.openstack.org/39055
    Add Pcloud Flavors

Addressed by: https://review.openstack.org/47091
    Add hosts to pcloud.

[jpretorius 2013/12/13]
Once the base code is done, please add something to Horizon to expose this via the UI. My thinking is:
 - During instance creation, allow the deployment to a pcloud that the end-user has access to
 - When listing instances, show the pclouds that instances are hosted in
 - When viewing the instance details, show the pcloud that an instance is hosted in
Also, please test that the scheduler allows an end-user to migrate/live-migrate an instance from one pcloud to another.

    This blueprint has been deferred from the icehouse-3 milestone to Juno because it missed the "feature proposal freeze" deadline. https://wiki.openstack.org/wiki/Icehouse_Release_Schedule --russellb

Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

Work items:
Add wrapper layer to aggregates, usign metadata to record owner. name, etc : INPROGRESS
Add quoats and per action autorization : INPROGRESS
Add Scheduler filter for aggregate uuid (tenant must own aggregate): TODO

Dependency tree

* Blueprints in grey have been implemented.