filter-by-business-tag

Registered by XiaodongPan

In most production environments, we will have many vms with the same business type, but we are not allowed to be deployed on the same host, to avoid competition for resources, reduce maintenance costs, improve business availability, as follows:

1, before schedule:
+----------------------------------------------+
| ------ node01 ---- node02------- node03 --- |
| +-----------+ +-----------+ +-----------+ |
| | vm_nginx | | vm_nginx | | vm_nginx | |
| | vm_mysql | | vm_mongodb| |vm_mongodb | |
| | vm_redis | | vm_redis | | vm_redis | |
| +-----------+ +-----------+ +-----------+ |
+----------------------------------------------+
2, new instance of mysql, schedule like this:
+--------+
|vm_mysql|
+--+-----+
   |deploy
   |
+--+--------------------------------------------+
| ------ node01 ---- node02------- node03 ---- |
| +-----------+ +-----------+ +-----------+ |
| | vm_nginx | | vm_nginx | | vm_nginx | |
| | vm_mysql | | vm_mongodb| |vm_mongodb | |
| | vm_redis | | vm_redis | | vm_redis | |
| +-----------+ +-----------+ +-----------+ |
|---- not-allow ------ allow ------- allow ---- |
+-----------------------------------------------+

In order to avoid the same business type of virtual machines deployed on the same host, we need to scheduling vm by the business tag/type

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
XiaodongPan
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.