vsphere provider is missing firewaller, networking implementations
Bug #1450129 reported by
Eric Snow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
Eric Snow | ||
| 1.24 |
Fix Released
|
High
|
Eric Snow | ||
Bug Description
The new vsphere provider doesn't implement the firewaller interface (open/close ports) nor the networking interface. Relatedly, the provider does not ever set up external IP addresses for instances. So currently it is only useful on a private network. This drastically reduces the utility of the provider and should be resolved ASAP.
Matykevich Sergey (<email address hidden>), from Altoros, is working on this.
Revision history for this message
| Eric Snow (ericsnowcurrently) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Committed |
| status: | Fix Committed → In Progress |
| assignee: | nobody → Eric Snow (ericsnowcurrently) |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| tags: | added: tech-debt vsphere-provider |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
http://