Update patch set 27

Patch Set 27:

(1 comment)

Patch-set: 27
This commit is contained in:
Gerrit User 8786 2016-11-02 10:11:47 +00:00 committed by Gerrit Code Review
parent 10f48069a4
commit d6f0ee2339
1 changed files with 24 additions and 0 deletions

View File

@ -22,6 +22,30 @@
"revId": "3f8648848d4309c3b840ac33a8ca15bb7a34a4b6",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "ba5da102_feb13502",
"filename": "specs/10.0/role-decomposition.rst",
"patchSetId": 27
},
"lineNbr": 40,
"author": {
"id": 8786
},
"writtenOn": "2016-11-02T10:11:47Z",
"side": 1,
"message": "Igor, first of all we have a concept that roles of the node cannot be changed.\n\nSecondly, the whole idea is that we want to make services composition dynamic by stripping some of the services off the predefined roles.\n\nSo the idea is the following:\n1. Role is a preset of tags\n2. The main use case is to do a slight change, e.g. unassign db/amqp services from the controller and assign it to another node. This means that majority of nodes will still have roles assigned, e.g. computes, and only some of the controllers will have a slight divergence from the originating role.\n3. Having everything as a role would not be efficient as there will be too much roles which will clutter the UI/CLI output and make the UX terrible. User will need to assign something like 10 roles onto each node instead of assigning only one of them, while the main use case is to unassign/reassign only a couple of them.\n\nSo the whole idea of tags is related to the fact that we need to have separation between the \u0027default preset\u0027 which is a role and actually serves for business logic or UI purpose and a service assignment entity which is a tag.",
"parentUuid": "ba5da102_8df73558",
"range": {
"startLine": 39,
"startChar": 0,
"endLine": 40,
"endChar": 28
},
"revId": "3f8648848d4309c3b840ac33a8ca15bb7a34a4b6",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
}
]
}