The "bootstrap node" needs high availability

Bug #803042 reported by Clint Byrum
94
This bug affects 18 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Roger Peppe
pyjuju
Triaged
Wishlist
Unassigned

Bug Description

Currently the bootstrap step spawns one machine with zookeeper and the provisioning agent on it. These should be spawned on more than one machine and linked together so that they are not a single point of failure.

Revision history for this message
Benjamin Saller (bcsaller) wrote :

I might go so far as to suggest that we model this as an LXC container on some percentage of all deployed nodes in the environment running along side the machine agent its its managed service units.

The EC2 providers notions around `machine 0` go away and this becomes a distributed concern. It moves us in the intended direction of using ensembles service model to deploy itself as well.

Changed in juju:
status: New → Confirmed
importance: Undecided → High
tags: added: production
Changed in juju:
milestone: none → florence
Changed in juju:
milestone: florence → honolulu
Changed in juju:
milestone: 0.6 → none
Changed in juju-core:
status: New → Confirmed
importance: Undecided → High
Changed in juju-core:
milestone: none → 2.0
assignee: nobody → Dave Cheney (dave-cheney)
tags: added: goju-resolved
Revision history for this message
Chris Christensen (christianchristensen) wrote :

(Putting some notes here from an IRC discussion...)
20:26:14 < chrischris> I'm actually curious if an additional zookeeper relation to the bootstrap node could be made as another charm config
23:31:25 < SpamapS> chrischris: negronjl has monkied with the zookeeper charm to allow it to be deployed as a 3-node quorum for the bootstrap machine
23:31:48 < SpamapS> chrischris: the HA problem is addressed in juju-core (rewrite in go with mongodb instead of zookeeper)

tags: removed: goju-resolved
Revision history for this message
Kapil Thangavelu (hazmat) wrote :

this isn't the case yet re juju-core, but it is an issue being looked at.

Changed in juju:
milestone: none → 0.8
Revision history for this message
Данило Шеган (danilo) wrote :

This is being addressed with https://blueprints.launchpad.net/juju-core/+spec/s-cloud-juju-ha for juju-core.

Changed in juju-core:
status: Confirmed → Triaged
importance: High → Wishlist
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Hi Danilo,

What's the reasoning behind lowering this from High to Wishlist? From my perspective, this is the most critical bug in all of juju-core. Perhaps it can be called a "High", since there's a workaround (juju export).

Thanks!
Dustin

Revision history for this message
John A Meinel (jameinel) wrote :

High generally denotes that it is actively on our todo map for this cycle. It turns out that someone is working on this (Gustavo is spiking on it). So I'm willing to put it back to High.

Changed in juju-core:
importance: Wishlist → High
Changed in juju-core:
assignee: Dave Cheney (dave-cheney) → nobody
Tim Penhey (thumper)
tags: added: story-ha
Curtis Hovey (sinzui)
tags: added: feature
removed: story-ha
Curtis Hovey (sinzui)
Changed in juju:
status: Confirmed → Triaged
Chris J Arges (arges)
tags: added: cts-cloud-review
Mark Ramm (mark-ramm)
Changed in juju:
importance: High → Wishlist
Changed in juju-core:
assignee: nobody → Roger Peppe (rogpeppe)
tags: added: canonical-is
Tim Penhey (thumper)
Changed in juju-core:
status: Triaged → In Progress
Nate Finch (natefinch)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0 → 1.19.1
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

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