cluster-create creates a security group per trove instance

Bug #1396808 reported by Steve McLellan
6
This bug affects 1 person
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_id=2,volume=1 --instance flavor_id=2,volume=1 --instance flavor_id=2,volume=1

and then list instances:
  trove cluster-instances 953e3c9b-4e3f-4912-8992-23f8d00b5ecf
+--------------------------------------+---------------------+-----------+------+--------+
| ID | Name | Flavor ID | Size | Status |
+--------------------------------------+---------------------+-----------+------+--------+
| 4a4c9e45-d8ec-4fcb-8ea8-cbf22504244b | mongo-cluster-rs1-2 | 2 | 1 | BUILD |
| 57a7b0df-93ea-46a1-afe2-10d368b7b45a | mongo-cluster-rs1-3 | 2 | 1 | BUILD |
| 63bdad38-f056-4875-ae8d-c96fc5eddc08 | mongo-cluster-rs1-1 | 2 | 1 | BUILD |
+--------------------------------------+---------------------+-----------+------+--------+

The nlist neutron sec groups:
  neutron security-group-list

--------------------------------------+-----------------------------------------------+---------------------------------------------------------+
| id | name | description |
+--------------------------------------+-----------------------------------------------+---------------------------------------------------------+
| 077ff9f3-9b23-453a-99e3-c263390f048e | SecGroup_57a7b0df-93ea-46a1-afe2-10d368b7b45a | Security Group for 57a7b0df-93ea-46a1-afe2-10d368b7b45a |
| 3f6b2a3f-7416-4b4b-a50a-e97726e07bb5 | SecGroup_4a4c9e45-d8ec-4fcb-8ea8-cbf22504244b | Security Group for 4a4c9e45-d8ec-4fcb-8ea8-cbf22504244b |
| 7692ca69-4dd4-429d-af6b-6dd0679ed13c | SecGroup_63bdad38-f056-4875-ae8d-c96fc5eddc08 | Security Group for 63bdad38-f056-4875-ae8d-c96fc5eddc08 |
+--------------------------------------+-----------------------------------------------+---------------------------------------------------------+

Denis M. (dmakogon)
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
Revision history for this message
Auston McReynolds (amcrn) wrote :

this should be a conf, because there are very valid reasons why you'd want separate security-groups for each instance.

Amrith Kumar (amrith)
Changed in trove:
status: Triaged → Confirmed
milestone: none → ongoing
zhanggang (gangzh)
Changed in trove:
assignee: nobody → zhanggang (gangzh)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.