Closed wninobla closed 8 years ago
Currently this wasn't even on the roadmap (i.e. I don't even know what's involved in implementing it), but I'll add an item to our backlog to investigate it.
Level of priority?
I would say since we tie SLA's to it we'll want to mark this at least as a minimum if not a high only because we don't necessarily do containers fully just yet. nothing is considered a throw away yet so we need to provide some fault tolerance here at the VM level.
Ok - duly noted, will put this near the top of the pile :)
On 27 Sep. 2016, at 2:41 am, wninobla notifications@github.com wrote:
I would say since we tie SLA's to it we'll want to mark this at least as a minimum if not a high only because we don't necessarily do containers fully just yet. nothing is considered a throw away yet so we need to provide some fault tolerance here at the VM level.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
It's one API to enable with the 2 server IDs, so should be pretty simple to add.
Work remaining:
Looks to be pretty simple, so hopefully I can knock this one off today.
Hi,
Looking to consume the server anti-affinity rules here. Let me know if this is in development or not. Thanks!