document best practices for securing communication between juju nodes
Bug #966605 reported by
Jamie Strandboge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
| Precise |
Won't Fix
|
High
|
Unassigned | ||
| Quantal |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
This is a tracking bug for a dependency of the juju MIR (bug #912861).
Document best practices for securing communication between juju nodes and in the case of Maas, also between juju and cobbler. Remove an hard-coded assumptions from juju (eg, http vs https) and ideally add some functionality to make this easier to deploy. Suggestions are stunnel4 or openvpn.
| Changed in juju (Ubuntu Precise): | |
| importance: | Undecided → High |
| tags: | removed: rls-p-tracking |
| Changed in juju (Ubuntu Quantal): | |
| status: | Triaged → Won't Fix |
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in juju (Ubuntu Precise): | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release