rsnt_translations
56,430
edits
Automating VM creation/fr: Difference between revisions
no edit summary
(Created page with "La configuration de cloud-init est spécifiée en texte brut en format [https://fr.wikipedia.org/wiki/YAML YAML]. Pour savoir comment créer des fichiers, voyez la [https://cl...") |
No edit summary |
||
| Line 35: | Line 35: | ||
Le rafraîchissement du journal se fait en cliquant sur le bouton ''Go'', en haut de la page. | Le rafraîchissement du journal se fait en cliquant sur le bouton ''Go'', en haut de la page. | ||
==Utilisation de gabarits Heat== | ==Utilisation de gabarits Heat== | ||
Les gabarits Heat sont encore plus puissants : ils peuvent être utilisés pour automatiser des tâches faites dans le tableau de bord OpenStack, par exemple créer simultanément plusieurs instances, configurer des groupes de sécurité, créer et configurer des réseaux ou créer des volumes et les attacher à des instances. Les gabarits Heat peuvent être utilisés avec des fichiers cloud-init; une fois que Heat a créé une instance, il peut passer un fichier cloud-init à cette instante pour exécuter des tâches de configuration ou même inclure dynamiquement de l'information sur d'autres ressources dans le fichier cloud-init (par exemple des IP flottantes d'autres instances) | |||
As with cloud-init the creation of [https://wiki.openstack.org/wiki/Heat Heat] Orchestration Template (HOT) files is not covered here, instead see the official [http://docs.openstack.org/developer/heat/template_guide/hot_guide.html documentation]. HOT files are also written in the [https://en.wikipedia.org/wiki/YAML YAML] format. Heat allows automation of operations performed in the OpenStack dashboard (Horizon) as well as the ability to pass information into the embedded CloudInit files, such as an IP of another server. Before using a Heat template there is usually no need to create any resources in advance. In fact it is often good practice to remove any resources you are not currently using before hand, as using a Heat template consumes resources towards your quota and will fail if it tries to exceed your quota. | As with cloud-init the creation of [https://wiki.openstack.org/wiki/Heat Heat] Orchestration Template (HOT) files is not covered here, instead see the official [http://docs.openstack.org/developer/heat/template_guide/hot_guide.html documentation]. HOT files are also written in the [https://en.wikipedia.org/wiki/YAML YAML] format. Heat allows automation of operations performed in the OpenStack dashboard (Horizon) as well as the ability to pass information into the embedded CloudInit files, such as an IP of another server. Before using a Heat template there is usually no need to create any resources in advance. In fact it is often good practice to remove any resources you are not currently using before hand, as using a Heat template consumes resources towards your quota and will fail if it tries to exceed your quota. | ||