Enable server-groups functionality to ensure affinity and anti-affinity can be used

Bug #1468359 reported by James Page
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Medium
Unassigned
nova-cloud-controller (Juju Charms Collection)
Fix Released
High
David Ames

Bug Description

By default, its possible that two units of a service deployed ontop of a Juju deployed OpenStack cloud can end up on the same physical host; The nova-cloud-controller charm does not currently enable the required filter to support anti-affinity via server-groups:

   http://docs.openstack.org/kilo/config-reference/content/section_compute-scheduler.html

This would provide a good fallback for Juju in the event that no AZ's are exposed by the OpenStack cloud.

tags: added: cloud-installer landscape
James Troup (elmo)
tags: added: canonical-is
Curtis Hovey (sinzui)
tags: added: feature
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
tags: added: canonical-bootstack
Revision history for this message
James Page (james-page) wrote :

Marking Triaged; this is something we should enable by default in the charm as well.

Changed in nova-cloud-controller (Juju Charms Collection):
status: New → Triaged
importance: Undecided → High
assignee: nobody → David Ames (thedac)
tags: added: openstack
David Britton (dpb)
tags: added: kanban-cross-team
tags: removed: kanban-cross-team
James Page (james-page)
Changed in nova-cloud-controller (Juju Charms Collection):
milestone: none → 15.10
status: Triaged → Fix Committed
James Page (james-page)
Changed in nova-cloud-controller (Juju Charms Collection):
status: Fix Committed → Fix Released
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.