launch multiple bootstrap nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
As progress towards lp:803042, we should have an environment parameter that controls how many [er: "master", or "bootstrap", or whatever we call them] nodes are launched when we bootstrap.
To avoid the work for this bug ballooning out of control, I propose that this should only be required to actually work properly in the single-node case; there are several things we need to handle before we have a fully-working solution, including:
* making sure all the zookeepers know about all the other zookeepers
* making sure provisioning agents work well together
* figuring out what to do when we lose a master node
* probably more
These bullet points are heavily reminiscent of what juju itself is meant to do, but thinking too much about how we'd make juju deploy itself is giving me a headache. Definitely worthy of further thought/
Changed in juju: | |
status: | New → In Progress |
assignee: | nobody → William Reade (fwereade) |
Changed in juju: | |
status: | In Progress → Confirmed |
assignee: | William Reade (fwereade) → nobody |
Changed in juju: | |
importance: | Undecided → Low |
status: | Confirmed → Triaged |
Excerpts from William Reade's message of Wed Oct 19 11:43:07 UTC 2011: discussion. ..
> Public bug reported:
>
> As progress towards lp:803042, we should have an environment parameter
> that controls how many [er: "master", or "bootstrap", or whatever we
> call them] nodes are launched when we bootstrap.
>
> To avoid the work for this bug ballooning out of control, I propose that
> this should only be required to actually work properly in the single-
> node case; there are several things we need to handle before we have a
> fully-working solution, including:
>
> * making sure all the zookeepers know about all the other zookeepers
> * making sure provisioning agents work well together
> * figuring out what to do when we lose a master node
> * probably more
>
> These bullet points are heavily reminiscent of what juju itself is meant
> to do, but thinking too much about how we'd make juju deploy itself is
> giving me a headache. Definitely worthy of further thought/
Hi william this would be pretty nice, but we should probably talk about this. We
need to refactor bootstrap to launch zk and the provisioning agent as a juju
service, so the management of the zk is the same as any other service.