juju HA primary controller machine concept
Bug #1860291 reported by
Anastasia
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia |
Bug Description
Currently, Juju gives no indication which controller machine in HA is primary.
From Juju perspective the concept is not necessarily useful as any controller machine can accept request and correctly pass them to a primary mongo instance.
However, sometimes it's important for the users to know which controller machine has a local mongo instance which is primary in a replicaset.
We should surface it in a status.
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Anastasia (anastasia-macmood) |
Changed in juju: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.8-beta1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Should it be in status? HA status is in the show-controller output and I'd think that, for the most part, status of that doesn't need much attention unless you were looking for it. Maybe we can tack the primary indicator to the existing data?
juju show-controller
controller- machines:
"0":
instance-id: juju-b882a2-0
ha-status: ha-enabled
"1":
instance-id: juju-b882a2-1
ha-status: ha-enabled
"2":
instance-id: juju-b882a2-2
ha-status: ha-enabled