cluster-create creates a security group per trove instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Confirmed
|
Medium
|
zhanggang |
Bug Description
create-cluster results in a security group per instance; it makes more sense to me to have a security group for the cluster; there seems little benefit at the cost of stretching quotas.
If I use the cluster API to create a cluster:
trove cluster-create mongo-cluster mongodb 2.6 --instance flavor_
and then list instances:
trove cluster-instances 953e3c9b-
+------
| ID | Name | Flavor ID | Size | Status |
+------
| 4a4c9e45-
| 57a7b0df-
| 63bdad38-
+------
The nlist neutron sec groups:
neutron security-group-list
-------
| id | name | description |
+------
| 077ff9f3-
| 3f6b2a3f-
| 7692ca69-
+------
Changed in trove: | |
assignee: | nobody → Oleksandr Kyrylchuk (okyrylchuk) |
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in trove: | |
assignee: | Oleksandr Kyrylchuk (okyrylchuk) → nobody |
Changed in trove: | |
status: | Triaged → Confirmed |
milestone: | none → ongoing |
Changed in trove: | |
assignee: | nobody → zhanggang (gangzh) |
this should be a conf, because there are very valid reasons why you'd want separate security-groups for each instance.