netsec needs machine firewall for some providers
Bug #833064 reported by
William Reade
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Unassigned | ||
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
open_port, close_port, and get_opened_ports just log a warning and pretend to succeed; this is not good enough for production
Changed in juju: | |
milestone: | florence → honolulu |
summary: |
- non ec2 providers have no firewalls + non ec2/openstack providers have no firewalls |
Changed in juju: | |
milestone: | 0.6 → none |
Changed in juju: | |
milestone: | none → 0.8 |
Changed in juju-core: | |
importance: | Undecided → Medium |
Changed in juju-core: | |
importance: | Medium → Low |
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
importance: | Medium → Low |
tags: | added: firewall |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
This should probably delegate to the machine agent so we can implement once for all using machine level firewalling.. also gets rids of multi-second slowness for bootstrap/ addmachine/ remove- machine/ and destroy- environment.