OpenStack DBaaS (Trove)

show mongodb configsvr and mongos for cluster-instances

Bug #1697394 reported by jian.song
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
In Progress
Wishlist
jian.song

Bug Description

I noticed that in all kinds of clusters, only mongodb cluster use cluster-instances show only member (in the case of other types of nodes). It seems that it would be useful to add mongos and configsvr to this display.

In the past, we seem to have mgmt to complete this, but I noticed that there was no mgmt related command.

The modification has been completed（product needs, in the client side to add the type of display）, waiting for discussion if it is necessary.

+--------------------------------------+----------------------------------+-----------+------+--------+---------------+
| ID | Name | Flavor ID | Size | Status | Type |
+--------------------------------------+----------------------------------+-----------+------+--------+---------------+
| 60f9c20f-564a-4594-800d-4b5db450312d | rs2a | 2 | 5 | ACTIVE | member |
| 76e3f22c-58fb-42b6-868a-9177109937f6 | test-mongodb-cluster-rs1-3 | 1 | 1 | ACTIVE | member |
| 9ba7a767-80b9-4487-84ec-84a0dd44c95e | rs2c | 2 | 5 | ACTIVE | member |
| a0baf4c4-53da-4a5f-9102-0dee2bcad793 | test-mongodb-cluster-rs1-1 | 1 | 1 | ACTIVE | member |
| aac99495-7dcc-461d-aaa3-af8b3d25caa6 | mongo-mongos-test | 2 | 5 | ACTIVE | query_router |
| c0403293-88a5-4f9c-9a9e-ccac8a55fd44 | test-mongodb-cluster-configsvr-1 | 1 | 1 | ACTIVE | config_server |
| ec57deb7-9a38-402f-9c07-0f0b39e60faf | test-mongodb-cluster-rs1-2 | 1 | 1 | ACTIVE | member |
| fd3e44ca-ee39-44bf-9f99-5a4c0b8513db | rs2b | 2 | 5 | ACTIVE | member |
+--------------------------------------+----------------------------------+-----------+------+--------+---------------+

jian.song (jiansong)
Changed in trove:
assignee: nobody → jian.song (jiansong)
Revision history for this message
jian.song (jiansong) wrote :

The vertica that also has other type nodes shows the 'master' and 'member'. The other only have 'member'.

Revision history for this message
zhanggang (gangzh) wrote :

*******************************************************************
class MongoDbClusterView(ClusterView):

    def build_instances(self):
        return self._build_instances(['query_router'], ['member'])

class MongoDbMgmtClusterView(MgmtClusterView):

    def build_instances(self):
        return self._build_instances(['query_router'],
                                     ['config_server',
                                      'member',
                                      'query_router'])
*****************************************************************

As common use, just show the ip of mongos(query_router) and data nodes(member) of cluster is fine.
And if you want more detail, use mgmt, it will show all nodes include config_node, data_node, and mongos.

The architecture of these database is different(cassandra, galera, redis, vertica, mongo...), which means instance nodes to be publish could be different.
So, I think it's not a bug.

Revision history for this message
jian.song (jiansong) wrote :

yes,this is not a bug, is only for improvement experience.
Is there a way to call mgmt through troveclient? I see this patch out of stagnation[1].

In fact, Do this in mind only for the product...Mainly want to discuss whether this makes sense for community.

[1]:https://review.openstack.org/#/c/196938/

Amrith Kumar (amrith)
Changed in trove:
importance: Undecided → Wishlist
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/530177

Changed in trove:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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