Different default security groups depending on API used to launch instnaces
Bug #681416 reported by
Soren Hansen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned | ||
ec2-api |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Cloud servers from Rackspace have no firewall by default, while access to instances on EC2 are completely blocked from the outside. In order to mimick this behaviour, we should have two default security groups per user (or project, really): One for instances launched through the EC2 API and one for instances launched through the OpenStack API. The former should be closed by default, the latter should be open by default.
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: security-group |
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | Incomplete → Confirmed |
tags: | added: ec2 |
tags: |
added: security-groups removed: security-group |
Changed in nova: | |
status: | Incomplete → Confirmed |
Changed in nova: | |
status: | Incomplete → Won't Fix |
To post a comment you must log in.
Soren: can you revisit this and evaluate whether this bug report is still valid?