Difference between revisions of "Cloud public affinity rules"
(Created page with "This article has been created by an automatic translation software. You can view the article source here.<br /> <!-- Début de l'articl...") |
|||
| Line 1: | Line 1: | ||
| + | <span data-link_translate_fr_title="Cloud public regles d affinite" data-link_translate_fr_url="Cloud_public_regles_d_affinite"></span><br />[[:fr:Cloud public regles d affinite]][[fr:Cloud public regles d affinite]]<br /> | ||
| + | |||
This article has been created by an automatic translation software. You can view the article source [[:fr:Cloud public regles d affinite|here]].<br /> | This article has been created by an automatic translation software. You can view the article source [[:fr:Cloud public regles d affinite|here]].<br /> | ||
Revision as of 15:36, 22 September 2015
fr:Cloud public regles d affinite
This article has been created by an automatic translation software. You can view the article source here.
Introduction
How to allocate its vm on multiple physical servers ?
Context : I wish that my platform's three web servers are deployed on three different physical hosts.
We will see how to set up a mechanism of anti-affinite.
Definition : Rules for affinity and anti affnite tells cloustack hypervisor to keep the vm sets or separated as heard on multiple physical hosts.
Note : This type of mechanism is taking place before deployment of instances of your platform.
Place
Step 1 Go to the menu
Click on
Fill in the name field
You get :
Step 2 Deploy an instance using the wizard from the menu
Step [5] Affinity choose Group 1
Conclusion
After deployment instances are on different physical hosts.
This article seemed you to be useful ?
Enable comment auto-refresher