From 81e96746682421ca3a230ea1c9cbecea37dbe626 Mon Sep 17 00:00:00 2001 From: OpenStack Proposal Bot Date: Wed, 12 Nov 2014 06:12:50 +0000 Subject: [PATCH] Imported Translations from Transifex For more information about this automatic import see: https://wiki.openstack.org/wiki/Translations/Infrastructure Change-Id: I643ef226c96ce2d9404725db1dbf5e8b63b36a0d --- doc/glossary/locale/ja.po | 30 +- doc/image-guide/locale/fr.po | 65 +- doc/image-guide/locale/image-guide.pot | 54 +- doc/image-guide/locale/ja.po | 67 +- doc/user-guide/locale/fr.po | 2146 ++++++++++++++++++++++- doc/user-guide/locale/ja.po | 2148 +++++++++++++++++++++++- doc/user-guide/locale/user-guide.pot | 1457 +++++++++++++++- 7 files changed, 5847 insertions(+), 120 deletions(-) diff --git a/doc/glossary/locale/ja.po b/doc/glossary/locale/ja.po index d641e68211..c682d60e07 100644 --- a/doc/glossary/locale/ja.po +++ b/doc/glossary/locale/ja.po @@ -6,8 +6,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-11-11 02:33+0000\n" -"PO-Revision-Date: 2014-11-11 02:01+0000\n" +"POT-Creation-Date: 2014-11-11 16:08+0000\n" +"PO-Revision-Date: 2014-11-12 05:13+0000\n" "Last-Translator: Tomoyuki KATO \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -3462,7 +3462,7 @@ msgstr "Graphic Interchange Format (GIF)" #: ./doc/glossary/glossary-terms.xml3617(para) msgid "" "A type of image file that is commonly used for animated images on web pages." -msgstr "" +msgstr "Web ページのアニメーション画像によく使用される画像ファイルの形式。" #: ./doc/glossary/glossary-terms.xml3623(glossterm) #: ./doc/glossary/glossary-terms.xml3625(primary) @@ -3473,7 +3473,7 @@ msgstr "Graphics Processing Unit (GPU)" msgid "" "Choosing a host based on the existence of a GPU is currently unsupported in " "OpenStack." -msgstr "" +msgstr "GPU の有無によりホストを選択することは、現在 OpenStack で未サポート。" #: ./doc/glossary/glossary-terms.xml3635(glossterm) #: ./doc/glossary/glossary-terms.xml3637(primary) @@ -3497,7 +3497,7 @@ msgid "" "The code name for the seventh release of OpenStack. The design summit took " "place in San Diego, California, US and Grizzly is an element of the state " "flag of California." -msgstr "" +msgstr "OpenStack の 7 番目のリリースのコード名。デザインサミットがアメリカ合衆国カリフォルニア州サンディエゴで開催された。Grizzly は、カリフォルニア州の州旗に使われている。" #: ./doc/glossary/glossary-terms.xml3662(glossterm) #: ./doc/glossary/glossary-terms.xml3664(primary) @@ -3533,7 +3533,7 @@ msgstr "handover" msgid "" "An object state in Object Storage where a new replica of the object is " "automatically created due to a drive failure." -msgstr "" +msgstr "ドライブ故障により、オブジェクトの新しい複製が自動的に作成された、Object Storage のオブジェクトの状態。" #: ./doc/glossary/glossary-terms.xml3704(glossterm) #: ./doc/glossary/glossary-terms.xml3706(primary) @@ -3556,7 +3556,7 @@ msgid "" "The code name for the eighth release of OpenStack. The design summit took " "place in Portland, Oregon, US and Havana is an unincorporated community in " "Oregon." -msgstr "" +msgstr "OpenStack の 8 番目のリリースのコード名。デザインサミットがアメリカ合衆国オレゴン州ポートランドで開催された。Havana は、オレゴン州の非法人コミュニティーである。" #: ./doc/glossary/glossary-terms.xml3730(glossterm) #: ./doc/glossary/glossary-terms.xml3732(primary) @@ -3577,7 +3577,7 @@ msgstr "Heat Orchestration Template (HOT)" #: ./doc/glossary/glossary-terms.xml3748(para) msgid "Heat input in the format native to OpenStack." -msgstr "" +msgstr "OpenStack 固有形式の Heat の入力データ。" #: ./doc/glossary/glossary-terms.xml3753(glossterm) #: ./doc/glossary/glossary-terms.xml3755(primary) @@ -4976,7 +4976,7 @@ msgstr "Nebula" #: ./doc/glossary/glossary-terms.xml5335(para) msgid "Released as open source by NASA in 2010 and is the basis for Compute." -msgstr "" +msgstr "2010 年に NASA によりオープンソースとしてリリースされた。Compute の基になった。" #: ./doc/glossary/glossary-terms.xml5341(glossterm) #: ./doc/glossary/glossary-terms.xml5343(primary) @@ -4988,7 +4988,7 @@ msgid "" "One of the default roles in the Compute RBAC system. Enables the user to " "allocate publicly accessible IP addresses to instances and change firewall " "rules." -msgstr "" +msgstr "Compute RBAC システムにおけるデフォルトのロールの 1 つ。ユーザーが、パブリックにアクセス可能な IP アドレスをインスタンスに割り当てられ、ファイアウォールルールを変更できるようになる。" #: ./doc/glossary/glossary-terms.xml5354(glossterm) #: ./doc/glossary/glossary-terms.xml5356(primary) @@ -5685,7 +5685,7 @@ msgstr "パーティションインデックス値" #: ./doc/glossary/glossary-terms.xml6130(para) msgid "" "Used by Object Storage to determine which partition data should reside on." -msgstr "" +msgstr "パーティションデータが配置されるべき場所を決めるために、Object Storage により使用される。" #: ./doc/glossary/glossary-terms.xml6136(glossterm) #: ./doc/glossary/glossary-terms.xml6138(primary) @@ -5696,7 +5696,7 @@ msgstr "path MTU discovery (PMTUD)" msgid "" "Mechanism in IP networks to detect end-to-end MTU and adjust packet size " "accordingly." -msgstr "" +msgstr "エンド間の MTU を検出し、パケットサイズを適切に調整するための IP ネットワークにおける機構。" #: ./doc/glossary/glossary-terms.xml6148(glossterm) #: ./doc/glossary/glossary-terms.xml6150(primary) @@ -7204,7 +7204,7 @@ msgstr "StaticWeb" msgid "" "WSGI middleware component of Object Storage that serves container data as a " "static web page." -msgstr "" +msgstr "コンテナーデータを静的 Web ページとして取り扱う Object Storage の WSGI ミドルウェアコンポーネント。" #: ./doc/glossary/glossary-terms.xml7808(glossterm) #: ./doc/glossary/glossary-terms.xml7810(primary) @@ -8217,13 +8217,13 @@ msgstr "XenServer ハイパーバイザー" #: ./doc/glossary/glossary-terms.xml9013(glossterm) #: ./doc/glossary/glossary-terms.xml9015(primary) msgid "XFS" -msgstr "" +msgstr "XFS" #: ./doc/glossary/glossary-terms.xml9018(para) msgid "" "High-performance 64-bit file system created by Silicon Graphics. Excels in " "parallel I/O operations and data consistency." -msgstr "" +msgstr "Silicon Graphics 社により作成された、高性能な 64 ビットファイルシステム。並列 I/O 処理とデータ一貫性に優れる。" #: ./doc/glossary/glossary-terms.xml9029(title) msgid "Y" diff --git a/doc/image-guide/locale/fr.po b/doc/image-guide/locale/fr.po index cee84633f9..9ef0191a72 100644 --- a/doc/image-guide/locale/fr.po +++ b/doc/image-guide/locale/fr.po @@ -5,8 +5,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-11-05 07:13+0000\n" -"PO-Revision-Date: 2014-11-05 06:17+0000\n" +"POT-Creation-Date: 2014-11-11 16:08+0000\n" +"PO-Revision-Date: 2014-11-11 16:22+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n" "MIME-Version: 1.0\n" @@ -1967,7 +1967,7 @@ msgstr "Il y a plusieurs outils qui sont conçus pour automatiser la création d msgid "Oz" msgstr "Oz" -#: ./doc/image-guide/ch_creating_images_automatically.xml23(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml21(para) msgid "" "As of this writing, there are no Oz packages for Ubuntu, so you will need to" " either install from source or build your own .deb file." @@ -1985,7 +1985,7 @@ msgid "" "yum:" msgstr "Oz est un outil en ligne de commande qui automatise le processus de création de fichier image de machine virtuelle. Oz est une application Python qui interagit avec KVM pour passer à travers les étapes d'installation d'une machine virtuelle. Il utilise un jeu de fichiers kickstart (systèmes basés sur Red Hat) et preseed (systèmes basés sur Debian) prédéfinis pour les systèmes d'exploitation qui les supportent, et il peut aussi être utilisé pour créer des images Microsoft Windows. Sur Fedora, installez Oz avec yum:" -#: ./doc/image-guide/ch_creating_images_automatically.xml27(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml25(para) msgid "" "A full treatment of Oz is beyond the scope of this document, but we will " "provide an example. You can find additional examples of Oz template files on" @@ -1994,57 +1994,58 @@ msgid "" "Here's how you would create a CentOS 6.4 image with Oz." msgstr "Un traitement complet de Oz dépasse la portée de ce document, mais nous allons fournir un exemple. Vous pouvez trouver des exemples supplémentaires des fichiers modèles Oz sur GitHub à at rackerjoe/oz-image-build/templates. Voici coment vous pourrez créer une image CentOs 6.4 avec Oz." -#: ./doc/image-guide/ch_creating_images_automatically.xml34(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml31(para) msgid "" "Create a template file (we'll call it centos64.tdl) " "with the following contents. The only entry you will need to change is the " "<rootpw> contents." msgstr "Créez un fichier modèle (que nous allons appeler centos64.tdl) avec le contenu suivant. La seule entrée que vous devrez changer est le contenu <rootpw>." -#: ./doc/image-guide/ch_creating_images_automatically.xml72(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml69(para) msgid "" "This Oz template specifies where to download the Centos 6.4 install ISO. Oz " "will use the version information to identify which kickstart file to use. In" " this case, it will be RHEL6.auto." -" It adds EPEL as a repository and installs the epel-" +" It adds EPEL as a repository and install the epel-" "release, cloud-utils, and cloud-" "init packages, as specified in the packages " "section of the file." +msgstr "Ce modèle Oz indique où télécharger l'ISO d'installation de CentOS 6.4. Oz utilisera les informations de version pour identifier quel fichier kickstart utiliser. Dans ce cas, il s'agira de RHEL6.auto. Cela ajoute EPEL en tant que dépôt et installe les packages epel-release, cloud-utils, et cloud-init, comme spécifié dans la section packages du fichier." + +#: ./doc/image-guide/ch_creating_images_automatically.xml77(para) +msgid "" +"After Oz does the initial OS install using the kickstart file, it updates " +"the image's install packages with . It also removes any " +"reference to the eth0 device that libvirt creates while Oz does the " +"customizing, as specified in the command section of the " +"XML file." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml83(para) -msgid "" -"After Oz does the initial OS install using the kickstart file, it customizes" -" the image by doing an update. It also removes any reference to the eth0 " -"device that libvirt creates while Oz does the customizing, as specified in " -"the command section of the XML file." -msgstr "Après que Oz ait réalisé l'installation du système d'exploitation initiale, il personnalise l'image en réalisant une mise à jour. Il enlève aussi toute référence au périphérique eth0 que libvirt crée pendant que Oz réalise la personnalisation, comme indiqué dans la section command du fichier XML." - -#: ./doc/image-guide/ch_creating_images_automatically.xml89(para) msgid "To run this, do, as root:" msgstr "Pour lancer ça, faites, en tant que root:" -#: ./doc/image-guide/ch_creating_images_automatically.xml92(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml86(para) msgid "" "The -d3 flag tells Oz to show status information as it " "runs." msgstr "Le drapeau -d3 indique à Oz de montrer les informations de status comme il fonctionne." -#: ./doc/image-guide/ch_creating_images_automatically.xml96(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml90(para) msgid "" "The -u tells Oz to do the customization (install extra " "packages, run the commands) once it does the initial install." msgstr "Le drapeau -u indique à Oz de réaliser la personnalisation (installation de packages supplémentaires, lancement de commandes) une fois qu'il a fait l'installation initiale." -#: ./doc/image-guide/ch_creating_images_automatically.xml102(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml95(para) msgid "" "The -x <filename> flag tells Oz what filename to " "use to write out a libvirt XML file (otherwise it will default to something " "like centos64Apr_03_2013-12:39:42)." msgstr "Le drapeau -x <filename> indique à Oz quel nom de fichier utiliser pour écrire un fichier XML libvirt (autrement le fichier par défaut serait sous la forme centos64Apr_03_2013-12:39:42)." -#: ./doc/image-guide/ch_creating_images_automatically.xml90(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml84(para) msgid "" "If you leave out the -u " "flag, or you want to edit the file to do additional customizations, you can " @@ -2054,11 +2055,11 @@ msgid "" "and perform the customizations." msgstr "Si vous omettez le drapeau -u, ou si vous souhaitez éditer le fichier pour faire des personnalisations supplémentaires, vous pouvez utiliser la commande , en utilisant le fichier XML libvirt que génère. Par exemple: Oz va invoquer libvirt pour booter l'image à l'intérieur de KVM, puis Oz va faire un ssh à l'intérieur de l'instance et réaliser les personnalisations." -#: ./doc/image-guide/ch_creating_images_automatically.xml120(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml109(title) msgid "VMBuilder" msgstr "VMBuilder" -#: ./doc/image-guide/ch_creating_images_automatically.xml121(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml110(para) msgid "" "VMBuilder (Virtual " "Machine Builder) is a command-line tool that creates virtual machine images " @@ -2067,18 +2068,18 @@ msgid "" " ships with Debian can create Ubuntu and Debian virtual machine guests." msgstr "VMBuilder (Constructeur de Machine Virtuelle) est un outil en ligne de commande qui génère des images de machine virtuelle pour différents hyperviseurs. La version de VMBuilder fournie avec Ubuntu peut seulement créer des invités de machine virtuelle Ubuntu. La version de VMBuilder fournie avec Debian peut créer des invités de machine virtuelle ubuntu et Debian." -#: ./doc/image-guide/ch_creating_images_automatically.xml128(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml117(para) msgid "" "The Ubuntu Server Guide has " "documentation on how to use VMBuilder to create an Ubuntu image." msgstr "Le Guide du Serveur Ubuntu comprend de la documentation sur la manière d'utiliser VMBuilder pour créer une image Ubuntu." -#: ./doc/image-guide/ch_creating_images_automatically.xml135(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml124(title) msgid "BoxGrinder" msgstr "BoxGrinder" -#: ./doc/image-guide/ch_creating_images_automatically.xml136(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml125(para) msgid "" "BoxGrinder is another tool for " "creating virtual machine images, which it calls appliances. BoxGrinder can " @@ -2086,32 +2087,32 @@ msgid "" "currently only supported on Fedora." msgstr "BoxGrinder est un autre outil pour créer des images de machine virtuelle, qu'il appelle appliances. BoxGrinder peut créer des images Fedora, Red Hat Enterprise Linux, ou CentOS. BoxGrinder est actuellement seulement supporté sur Fedora." -#: ./doc/image-guide/ch_creating_images_automatically.xml145(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml134(title) msgid "VeeWee" msgstr "VeeWee" -#: ./doc/image-guide/ch_creating_images_automatically.xml146(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml135(para) msgid "" " VeeWee is often " "used to build Vagrant boxes, but " "it can also be used to build KVM images." msgstr " VeeWee est souvent utilisé pour construire des boites Vagrant, mais il peut aussi être utilisé pour construire des images KVM." -#: ./doc/image-guide/ch_creating_images_automatically.xml152(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml141(title) msgid "Packer" msgstr "Packer" -#: ./doc/image-guide/ch_creating_images_automatically.xml153(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml142(para) msgid "" " Packer is a tool for creating " "machine images for multiple platforms from a single source configuration." msgstr " Packer est un outil pour créer des images de machine pour de multiples plateformes à partir d'une configuration source unique." -#: ./doc/image-guide/ch_creating_images_automatically.xml159(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml148(title) msgid "imagefactory" msgstr "imagefactory" -#: ./doc/image-guide/ch_creating_images_automatically.xml160(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml149(para) msgid "" "imagefactory is a newer tool " "designed to automate the building, converting, and uploading images to " @@ -2119,11 +2120,11 @@ msgid "" "for OpenStack-based clouds." msgstr "imagefactory est un nouvel outil conçu pour automatiser la construction, la conversion, et le téléchargement d'images à différents fournisseurs de cloud. Il utilise Oz en tant que backend et inclue le support pour les clouds basés sur OpenStack." -#: ./doc/image-guide/ch_creating_images_automatically.xml167(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml156(title) msgid "SUSE Studio" msgstr "SUSE Studio" -#: ./doc/image-guide/ch_creating_images_automatically.xml168(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml157(para) msgid "" "SUSE Studio is a web application" " for building and testing software applications in a web browser. It " diff --git a/doc/image-guide/locale/image-guide.pot b/doc/image-guide/locale/image-guide.pot index a341fe7915..821b16419f 100644 --- a/doc/image-guide/locale/image-guide.pot +++ b/doc/image-guide/locale/image-guide.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-11-05 06:11+0000\n" +"POT-Creation-Date: 2014-11-12 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1365,7 +1365,7 @@ msgstr "" msgid "Oz" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:23(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:21(para) msgid "As of this writing, there are no Oz packages for Ubuntu, so you will need to either install from source or build your own .deb file." msgstr "" @@ -1373,91 +1373,91 @@ msgstr "" msgid "Oz is a command-line tool that automates the process of creating a virtual machine image file. Oz is a Python app that interacts with KVM to step through the process of installing a virtual machine. It uses a predefined set of kickstart (Red Hat-based systems) and preseed files (Debian-based systems) for operating systems that it supports, and it can also be used to create Microsoft Windows images. On Fedora, install Oz with yum:" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:27(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:25(para) msgid "A full treatment of Oz is beyond the scope of this document, but we will provide an example. You can find additional examples of Oz template files on GitHub at rackerjoe/oz-image-build/templates. Here's how you would create a CentOS 6.4 image with Oz." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:34(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:31(para) msgid "Create a template file (we'll call it centos64.tdl) with the following contents. The only entry you will need to change is the <rootpw> contents." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:72(para) -msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be RHEL6.auto. It adds EPEL as a repository and installs the epel-release, cloud-utils, and cloud-init packages, as specified in the packages section of the file." +#: ./doc/image-guide/ch_creating_images_automatically.xml:69(para) +msgid "This Oz template specifies where to download the Centos 6.4 install ISO. Oz will use the version information to identify which kickstart file to use. In this case, it will be RHEL6.auto. It adds EPEL as a repository and install the epel-release, cloud-utils, and cloud-init packages, as specified in the packages section of the file." +msgstr "" + +#: ./doc/image-guide/ch_creating_images_automatically.xml:77(para) +msgid "After Oz does the initial OS install using the kickstart file, it updates the image's install packages with . It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the command section of the XML file." msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml:83(para) -msgid "After Oz does the initial OS install using the kickstart file, it customizes the image by doing an update. It also removes any reference to the eth0 device that libvirt creates while Oz does the customizing, as specified in the command section of the XML file." -msgstr "" - -#: ./doc/image-guide/ch_creating_images_automatically.xml:89(para) msgid "To run this, do, as root:" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:92(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:86(para) msgid "The -d3 flag tells Oz to show status information as it runs." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:96(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:90(para) msgid "The -u tells Oz to do the customization (install extra packages, run the commands) once it does the initial install." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:102(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:95(para) msgid "The -x <filename> flag tells Oz what filename to use to write out a libvirt XML file (otherwise it will default to something like centos64Apr_03_2013-12:39:42)." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:90(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:84(para) msgid "If you leave out the -u flag, or you want to edit the file to do additional customizations, you can use the command, using the libvirt XML file that creates. For example: Oz will invoke libvirt to boot the image inside of KVM, then Oz will ssh into the instance and perform the customizations." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:120(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:109(title) msgid "VMBuilder" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:121(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:110(para) msgid "VMBuilder (Virtual Machine Builder) is a command-line tool that creates virtual machine images for different hypervisors. The version of VMBuilder that ships with Ubuntu can only create Ubuntu virtual machine guests. The version of VMBuilder that ships with Debian can create Ubuntu and Debian virtual machine guests." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:128(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:117(para) msgid "The Ubuntu Server Guide has documentation on how to use VMBuilder to create an Ubuntu image." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:135(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:124(title) msgid "BoxGrinder" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:136(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:125(para) msgid "BoxGrinder is another tool for creating virtual machine images, which it calls appliances. BoxGrinder can create Fedora, Red Hat Enterprise Linux, or CentOS images. BoxGrinder is currently only supported on Fedora." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:145(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:134(title) msgid "VeeWee" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:146(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:135(para) msgid " VeeWee is often used to build Vagrant boxes, but it can also be used to build KVM images." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:152(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:141(title) msgid "Packer" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:153(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:142(para) msgid " Packer is a tool for creating machine images for multiple platforms from a single source configuration." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:159(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:148(title) msgid "imagefactory" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:160(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:149(para) msgid "imagefactory is a newer tool designed to automate the building, converting, and uploading images to different cloud providers. It uses Oz as its back-end and includes support for OpenStack-based clouds." msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:167(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml:156(title) msgid "SUSE Studio" msgstr "" -#: ./doc/image-guide/ch_creating_images_automatically.xml:168(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml:157(para) msgid "SUSE Studio is a web application for building and testing software applications in a web browser. It supports the creation of physical, virtual or cloud-based applications and includes support for building images for OpenStack based clouds using SUSE Linux Enterprise and openSUSE as distributions." msgstr "" diff --git a/doc/image-guide/locale/ja.po b/doc/image-guide/locale/ja.po index 33535a4ddb..90654a90b4 100644 --- a/doc/image-guide/locale/ja.po +++ b/doc/image-guide/locale/ja.po @@ -5,8 +5,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-11-05 07:13+0000\n" -"PO-Revision-Date: 2014-11-05 06:17+0000\n" +"POT-Creation-Date: 2014-11-11 16:08+0000\n" +"PO-Revision-Date: 2014-11-11 16:22+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" @@ -1967,7 +1967,7 @@ msgstr "イメージ作成を自動化するために設計されたツールが msgid "Oz" msgstr "Oz" -#: ./doc/image-guide/ch_creating_images_automatically.xml23(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml21(para) msgid "" "As of this writing, there are no Oz packages for Ubuntu, so you will need to" " either install from source or build your own .deb file." @@ -1985,7 +1985,7 @@ msgid "" "yum:" msgstr "Oz は、仮想マシンイメージファイルの作成プロセスを自動化するコマンドラインツールです。仮想マシンのインストールプロセス全体を KVM とやりとりする Python アプリケーションです。サポートするオペレーティングシステムの kickstart (Red Hat 系システム)、preseed ファイル (Debian 系システム) の事前定義を使用します。Microsoft Windows イメージを作成するためにも使用できます。Fedora の場合、yum を用いて Oz をインストールします。" -#: ./doc/image-guide/ch_creating_images_automatically.xml27(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml25(para) msgid "" "A full treatment of Oz is beyond the scope of this document, but we will " "provide an example. You can find additional examples of Oz template files on" @@ -1994,57 +1994,58 @@ msgid "" "Here's how you would create a CentOS 6.4 image with Oz." msgstr "Oz の詳細は、このドキュメントの範囲を超えていますが、例を示します。GitHub の rackerjoe/oz-image-build/templates に Oz テンプレートの別の例があります。これは、Oz を用いて CentOS 6.4 イメージを作成する方法です。" -#: ./doc/image-guide/ch_creating_images_automatically.xml34(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml31(para) msgid "" "Create a template file (we'll call it centos64.tdl) " "with the following contents. The only entry you will need to change is the " "<rootpw> contents." msgstr "以下の内容のテンプレートファイルを作成します。centos64.tdl という名前にします。変更する必要がある項目は、<rootpw> の内容だけです。" -#: ./doc/image-guide/ch_creating_images_automatically.xml72(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml69(para) msgid "" "This Oz template specifies where to download the Centos 6.4 install ISO. Oz " "will use the version information to identify which kickstart file to use. In" " this case, it will be RHEL6.auto." -" It adds EPEL as a repository and installs the epel-" +" It adds EPEL as a repository and install the epel-" "release, cloud-utils, and cloud-" "init packages, as specified in the packages " "section of the file." -msgstr "この Oz テンプレートは、CentOS 6.4 インストール ISO をダウンロードする場所を指定します。Oz は、使用するキックスタートファイルを識別するために、バージョン情報を使用します。今回の場合、RHEL6.auto になります。リポジトリーとして EPEL を追加し、このファイルの packages に指定されたとおり、epel-release、cloud-utils、cloud-init パッケージをインストールします。" +msgstr "この Oz テンプレートは、Centos 6.4 インストール ISO のダウンロード場所を指定します。Oz は、使用する kickstart ファイルを識別するために、バージョン情報を使用します。この場合、RHEL6.auto になります。リポジトリーとして EPEL を追加します。そして、このファイルの packages セクションに指定されている、epel-release、cloud-utils、cloud-init パッケージをインストールします。" + +#: ./doc/image-guide/ch_creating_images_automatically.xml77(para) +msgid "" +"After Oz does the initial OS install using the kickstart file, it updates " +"the image's install packages with . It also removes any " +"reference to the eth0 device that libvirt creates while Oz does the " +"customizing, as specified in the command section of the " +"XML file." +msgstr "" #: ./doc/image-guide/ch_creating_images_automatically.xml83(para) -msgid "" -"After Oz does the initial OS install using the kickstart file, it customizes" -" the image by doing an update. It also removes any reference to the eth0 " -"device that libvirt creates while Oz does the customizing, as specified in " -"the command section of the XML file." -msgstr "Oz が kickstart ファイルを使用して OS の初期インストールを完了した後、更新を実行してイメージをカスタマイズします。Oz によるカスタマイズ中、XML ファイルの command セクションに指定されているとおり、libvirt が作成する eth0 デバイスへの参照をすべて削除します。" - -#: ./doc/image-guide/ch_creating_images_automatically.xml89(para) msgid "To run this, do, as root:" msgstr "root として、このとおり実行します。" -#: ./doc/image-guide/ch_creating_images_automatically.xml92(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml86(para) msgid "" "The -d3 flag tells Oz to show status information as it " "runs." msgstr "-d3 フラグにより、Oz が実行中の状態を表示します。" -#: ./doc/image-guide/ch_creating_images_automatically.xml96(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml90(para) msgid "" "The -u tells Oz to do the customization (install extra " "packages, run the commands) once it does the initial install." msgstr "-u により、Oz が初期インストール完了後、カスタマイズ (追加パッケージのインストール、コマンドの実行) をします。" -#: ./doc/image-guide/ch_creating_images_automatically.xml102(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml95(para) msgid "" "The -x <filename> flag tells Oz what filename to " "use to write out a libvirt XML file (otherwise it will default to something " "like centos64Apr_03_2013-12:39:42)." msgstr "-x <filename> フラグにより、Oz が libvirt XML ファイル (指定しなければ、デフォルトで centos64Apr_03_2013-12:39:42 のようなものになります) を書き込むために使用するファイル名を指定します。" -#: ./doc/image-guide/ch_creating_images_automatically.xml90(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml84(para) msgid "" "If you leave out the -u " "flag, or you want to edit the file to do additional customizations, you can " @@ -2054,11 +2055,11 @@ msgid "" "and perform the customizations." msgstr "-u フラグを使用しない場合、またはファイルを編集して追加カスタマイズしたい場合、 が作成した libvirt XML ファイルを用いて、 コマンドを使用できます。例: Oz は、KVM 内でイメージを起動するために、libvirt を呼び出します。次に、Oz はインスタンスに SSH し、カスタマイズを実行します。" -#: ./doc/image-guide/ch_creating_images_automatically.xml120(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml109(title) msgid "VMBuilder" msgstr "VMBuilder" -#: ./doc/image-guide/ch_creating_images_automatically.xml121(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml110(para) msgid "" "VMBuilder (Virtual " "Machine Builder) is a command-line tool that creates virtual machine images " @@ -2067,18 +2068,18 @@ msgid "" " ships with Debian can create Ubuntu and Debian virtual machine guests." msgstr "VMBuilder (Virtual Machine Builder) は、さまざまなハイパーバイザー向けの仮想マシンイメージを作成するコマンドラインツールです。Ubuntu に同梱されている VMBuilder のバージョンは、Ubuntu 仮想マシンゲストのみを作成できます。Debian に同梱されている VMBuilder のバージョンは、Ubuntu と Debian の仮想マシンゲストを作成できます。" -#: ./doc/image-guide/ch_creating_images_automatically.xml128(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml117(para) msgid "" "The Ubuntu Server Guide has " "documentation on how to use VMBuilder to create an Ubuntu image." msgstr "Ubuntu Server Guide は、Ubuntu イメージを作成するために、VMBuilder を使用する方法がドキュメント化されています。" -#: ./doc/image-guide/ch_creating_images_automatically.xml135(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml124(title) msgid "BoxGrinder" msgstr "BoxGrinder" -#: ./doc/image-guide/ch_creating_images_automatically.xml136(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml125(para) msgid "" "BoxGrinder is another tool for " "creating virtual machine images, which it calls appliances. BoxGrinder can " @@ -2086,32 +2087,32 @@ msgid "" "currently only supported on Fedora." msgstr "BoxGrinder は、アプライアンスと呼ぶ仮想マシンイメージを作成するためのもう一つのツールです。BoxGrinder は Fedora、Red Hat Enterprise Linux、CentOS イメージを作成できます。BoxGrinder は現在 Fedora のみにおいてサポートされます。" -#: ./doc/image-guide/ch_creating_images_automatically.xml145(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml134(title) msgid "VeeWee" msgstr "VeeWee" -#: ./doc/image-guide/ch_creating_images_automatically.xml146(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml135(para) msgid "" " VeeWee is often " "used to build Vagrant boxes, but " "it can also be used to build KVM images." msgstr " VeeWee は、よく Vagrant ボックスを構築するために使用されますが、KVM イメージを構築するためにも使用されます。" -#: ./doc/image-guide/ch_creating_images_automatically.xml152(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml141(title) msgid "Packer" msgstr "Packer" -#: ./doc/image-guide/ch_creating_images_automatically.xml153(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml142(para) msgid "" " Packer is a tool for creating " "machine images for multiple platforms from a single source configuration." msgstr "Packer は、単一のソース設定から複数のプラットフォームに対して、マシンイメージを作成するためのツールです。" -#: ./doc/image-guide/ch_creating_images_automatically.xml159(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml148(title) msgid "imagefactory" msgstr "imagefactory" -#: ./doc/image-guide/ch_creating_images_automatically.xml160(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml149(para) msgid "" "imagefactory is a newer tool " "designed to automate the building, converting, and uploading images to " @@ -2119,11 +2120,11 @@ msgid "" "for OpenStack-based clouds." msgstr "imagefactory は、さまざまなクラウドプロバイダーへのイメージの構築、変換、アップロードを自動化するために設計された、比較的新しいツールです。バックエンドとして Oz を使用し、OpenStack ベースのクラウドを" -#: ./doc/image-guide/ch_creating_images_automatically.xml167(title) +#: ./doc/image-guide/ch_creating_images_automatically.xml156(title) msgid "SUSE Studio" msgstr "SUSE Studio" -#: ./doc/image-guide/ch_creating_images_automatically.xml168(para) +#: ./doc/image-guide/ch_creating_images_automatically.xml157(para) msgid "" "SUSE Studio is a web application" " for building and testing software applications in a web browser. It " diff --git a/doc/user-guide/locale/fr.po b/doc/user-guide/locale/fr.po index 1a4125800e..9e6c42f627 100644 --- a/doc/user-guide/locale/fr.po +++ b/doc/user-guide/locale/fr.po @@ -11,8 +11,8 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-11-02 09:33+0000\n" -"PO-Revision-Date: 2014-11-02 06:45+0000\n" +"POT-Creation-Date: 2014-11-11 16:08+0000\n" +"PO-Revision-Date: 2014-11-11 16:22+0000\n" "Last-Translator: openstackjenkins \n" "Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n" "MIME-Version: 1.0\n" @@ -1518,6 +1518,7 @@ msgstr "Si vous n'avez pas créer de groupe de sécurité, Vous ne pourrez pas a #: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml179(guilabel) #: ./doc/user-guide/section_sdk_neutron.xml7(title) +#: ./doc/user-guide/hot/section_advanced_topics.xml7(title) msgid "Networking" msgstr "Réseaux" @@ -3406,6 +3407,11 @@ msgid "FLOATING_IP_ADDRESS" msgstr "FLOATING_IP_ADDRESS" #: ./doc/user-guide/section_cli_nova_floating_ips.xml102(para) +#: ./doc/user-guide/hot/section_hot_spec.xml311(para) +#: ./doc/user-guide/hot/section_hot_spec.xml330(para) +#: ./doc/user-guide/hot/section_hot_spec.xml351(para) +#: ./doc/user-guide/hot/section_hot_spec.xml702(para) +#: ./doc/user-guide/hot/section_basic_resources.xml320(para) msgid "For example:" msgstr "Par exemple :" @@ -6660,6 +6666,7 @@ msgid "" msgstr "Les volumes sont des dispositifs de stockage de bloc que vous attachez à des instances pour permettre un stockage persistant. Vous pouvez attaché un volume à une instance en cours d'exécution ou détacher un volume et l'attacher à une autre instance à tout moment. Vous pouvez également créer un instantané de volume ou supprimer un volume. Seuls les administrateurs peuvent créer des types de volume." #: ./doc/user-guide/section_dashboard_manage_volumes.xml16(title) +#: ./doc/user-guide/hot/section_basic_resources.xml317(title) msgid "Create a volume" msgstr "Créer un volume" @@ -6780,6 +6787,7 @@ msgid "" msgstr "Le tableau de bord montre le volume dans l'onglet Volumes." #: ./doc/user-guide/section_dashboard_manage_volumes.xml132(title) +#: ./doc/user-guide/hot/section_basic_resources.xml347(title) msgid "Attach a volume to an instance" msgstr "Joindre un volume à l'instance" @@ -7037,7 +7045,2139 @@ msgid "" " method:" msgstr "Pour ajouter une règle à un groupe de sécurité, appeler la méthode novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create:" +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_software_deployment.xml4(title) +msgid "Software configuration" +msgstr "Configuration du logiciel" + +#: ./doc/user-guide/hot/section_software_deployment.xml5(para) +msgid "" +"There are a variety of options to configure the software which runs on the " +"servers in your stack. These can be broadly divided into the following:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml9(para) +msgid "Custom image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml12(para) +#: ./doc/user-guide/hot/section_software_deployment.xml59(title) +msgid "User-data boot scripts and cloud-init" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml15(para) +msgid "Software deployment resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml18(para) +msgid "" +"This section will describe each of these options and provide examples for " +"using them together in your stacks." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml22(title) +msgid "Image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml23(para) +msgid "" +"The first opportunity to influence what software is configured on your " +"servers is by booting them with a custom-built image. There are a number of " +"reasons you might want to do this, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml28(para) +msgid "" +" - since the required software is already on " +"the image there is no need to download and install anything at boot time." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml32(para) +msgid "" +" - software downloads can fail for a " +"number of reasons including transient network failures and inconsistent " +"software repositories." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml36(para) +msgid "" +" - custom built images can be verified" +" in test environments before being promoted to production." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml40(para) +msgid "" +" - post-boot configuration " +"may depend on agents already being installed and enabled" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml44(para) +msgid "A number of tools are available for building custom images, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml47(para) +msgid "" +"diskimage-" +"builder image building tools for OpenStack" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml50(para) +msgid "" +"imagefactory builds images for a " +"variety of operating system/cloud combinations" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml54(para) +msgid "" +"Examples in this guide which require custom images will use diskimage-" +"builder." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml60(para) +msgid "" +"When booting a server it is possible to specify the contents of the user-" +"data to be passed to that server. This user-data is made available either " +"from configured config-drive or from the Metadata service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml63(para) +msgid "" +"How this user-data is consumed depends on the image being booted, but the " +"most commonly used tool for default cloud images is Cloud-init." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml65(para) +msgid "" +"Whether the image is using Cloud-init or " +"not, it should be possible to specify a shell script in the user_data " +"property and have it be executed by the server during boot:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml80(para) +msgid "" +": debugging these scripts it is often useful to view" +" the boot log using nova console-log <server-id> to" +" view the progress of boot script execution." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml84(para) +msgid "" +"Often there is a need to set variable values based on parameters or " +"resources in the stack. This can be done with the " +"str_replace intrinsic function:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml106(para) +msgid "" +": If a stack-update is performed and there are " +"any changes at all to the content of user_data then the server will be " +"replaced (deleted and recreated) so that the modified boot configuration can" +" be run on a new server." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml111(para) +msgid "" +"When these scripts grow it can become difficult to maintain them inside the " +"template, so the get_file intrinsic function can be used " +"to maintain the script in a separate file:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml131(para) +msgid "" +": str_replace can replace any " +"strings, not just strings starting with $. However doing " +"this for the above example is useful because the script file can be executed" +" for testing by passing in environment variables." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml137(title) +msgid "Choosing the user_data_format" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml138(para) +msgid "" +"The OS::Nova::Server " +"user_data_format property determines how the user_data should be formatted " +"for the server. For the default value HEAT_CFNTOOLS, the " +"user_data is bundled as part of the heat-cfntools cloud-init boot " +"configuration data. While HEAT_CFNTOOLS is the default " +"for user_data_format, it is considered legacy and " +"RAW or SOFTWARE_CONFIG will generally " +"be more appropriate." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml144(para) +msgid "" +"For RAW the user_data is passed to Nova unmodified. For a" +" Cloud-" +"init enabled image, the following are both valid " +"RAW user-data:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml166(para) +msgid "" +"For SOFTWARE_CONFIG user_data is bundled as part of the " +"software config data, and metadata is derived from any associated software " +"deployment resources." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml171(title) +msgid "Signals and wait conditions" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml172(para) +msgid "" +"Often it is necessary to pause further creation of stack resources until the" +" boot configuration script has notified that it has reached a certain state." +" This is usually either to notify that a service is now active, or to pass " +"out some generated data which is needed by another resource. The resources " +"OS::Heat::WaitCondition" +" and OS::Heat::SwiftSignal" +" both perform this function using different techniques and tradeoffs." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml178(para) +msgid "" +"OS::Heat::WaitCondition" +" is implemented as a call to the Orchestration API resource signal. " +"The token is created using credentials for a user account which is scoped " +"only to the wait condition handle resource. This user is created when the " +"handle is created, and is associated to a project which belongs to the " +"stack, in an identity domain which is dedicated to the orchestration " +"service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml184(para) +#: ./doc/user-guide/hot/section_software_deployment.xml267(para) +msgid "" +"Sending the signal is a simple HTTP request, as with this example using " +"curl:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml188(para) +msgid "" +"The JSON containing the signal data is expected to be of the following " +"format:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml195(para) +msgid "" +"All of these values are optional, and if not specified will be set to the " +"following defaults:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml203(para) +msgid "" +"If status is set to FAILURE then the " +"resource (and the stack) will go into a FAILED state " +"using the reason as failure reason." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml205(para) +msgid "" +"The following template example uses the convenience attribute " +"curl_cli which builds a curl command with a valid token:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml263(para) +msgid "" +"OS::Heat::SwiftSignal" +" is implemented by creating an Object Storage API temporary URL which is " +"populated with signal data with an HTTP PUT. The orchestration service will " +"poll this object until the signal data is available. Object versioning is " +"used to store multiple signals." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml269(para) +msgid "" +"The above template example only needs to have the type " +"changed to the swift signal resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml281(para) +msgid "" +"The decision to use OS::Heat::WaitCondition" +" or OS::Heat::SwiftSignal" +" will depend on a few factors:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml285(para) +msgid "" +"OS::Heat::SwiftSignal" +" depends on the availability of an Object Storage API" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml289(para) +msgid "" +"OS::Heat::WaitCondition" +" depends on whether the orchestration service has been configured with a " +"dedicated stack domain (which may depend on the availability of an Identity " +"V3 API)." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml294(para) +msgid "" +"The preference to protect signal URLs with token authentication or a secret " +"webhook URL." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml300(title) +msgid "Software config resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml301(para) +msgid "" +"Boot configuration scripts can also be managed as their own resources. This " +"allows configuration to be defined once and run on multiple server " +"resources. These software-config resources are stored and retrieved via " +"dedicated calls to the Orchestration API. It is not possible to " +"modify the contents of an existing software-config resource, so a stack-" +"update which changes any existing software-config resource will result in " +"API calls to create a new config and delete the old one." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml308(para) +msgid "" +"The resource OS::Heat::SoftwareConfig" +" is used for storing configs represented by text scripts, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml326(para) +msgid "" +"The resource OS::Heat::CloudConfig" +" allows Cloud-" +"init cloud-config to be represented as template YAML rather than a " +"block string. This allows intrinsic functions to be included when building " +"the cloud-config. This also ensures that the cloud-config is valid YAML, " +"although no further checks for valid cloud-config are done." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml352(para) +msgid "" +"The resource OS::Heat::MultipartMime" +" allows multiple OS::Heat::SoftwareConfig" +" and OS::Heat::CloudConfig" +" resources to be combined into a single Cloud-init " +"multi-part message:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/index.xml10(title) +msgid "HOT guide" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_functions.xml4(title) +msgid "HOT functions" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml7(title) +msgid "Link between resources" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml10(para) +#: ./doc/user-guide/hot/section_hot_spec.xml627(title) +msgid "get_param" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml13(para) +#: ./doc/user-guide/hot/section_hot_spec.xml673(title) +msgid "get_resource" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml16(para) +msgid "Ref" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml19(para) +msgid "Fn::GetAtt / get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml25(title) +msgid "String manipulations" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml28(para) +#: ./doc/user-guide/hot/section_hot_spec.xml587(title) +msgid "get_file" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml31(para) +#: ./doc/user-guide/hot/section_hot_spec.xml696(title) +msgid "list_join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml34(para) +#: ./doc/user-guide/hot/section_hot_spec.xml717(title) +msgid "str_replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml37(para) +msgid "Fn::Base64" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml40(para) +msgid "Fn::Join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml43(para) +msgid "Fn::Split" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml46(para) +msgid "Fn::Replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml52(title) +msgid "Lookup structured data" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml55(para) +msgid "Fn::FindInMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml58(para) +msgid "Fn::MemberListToMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml61(para) +msgid "Fn::Select" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml67(title) +msgid "Misc" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml70(para) +msgid "Fn::ResourceFacade / resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml73(para) +msgid "Fn::GetAZs" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hot_spec.xml15(title) +msgid "Heat Orchestration Template (HOT) specification" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml18(title) +msgid "Template structure" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml19(para) +msgid "HOT templates are defined in YAML and use the following structure:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml38(term) +msgid "heat_template_version" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml40(para) +msgid "" +"This key with value 2013-05-23 (or a later date) " +"indicates that the YAML document is a HOT template of the specified version." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml45(term) +#: ./doc/user-guide/hot/section_hot_spec.xml111(term) +#: ./doc/user-guide/hot/section_hot_spec.xml173(term) +#: ./doc/user-guide/hot/section_hot_spec.xml247(term) +#: ./doc/user-guide/hot/section_hot_spec.xml507(term) +msgid "description" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml47(para) +msgid "" +"This optional key gives a description of the template, or the workload that " +"can be deployed using the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml52(term) +msgid "parameter_groups" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml54(para) +msgid "" +"This section specifies how the input parameters should be grouped and the " +"order to provide the parameters in." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml56(para) +#: ./doc/user-guide/hot/section_hot_spec.xml64(para) +#: ./doc/user-guide/hot/section_hot_spec.xml81(para) +#: ./doc/user-guide/hot/section_hot_spec.xml408(para) +#: ./doc/user-guide/hot/section_hot_spec.xml415(para) +msgid "This section is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml60(term) +#: ./doc/user-guide/hot/section_hot_spec.xml117(term) +#: ./doc/user-guide/hot/section_environment.xml17(literal) +msgid "parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml62(para) +msgid "" +"This section specifies input parameters that have to be provided when " +"instantiating the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml68(term) +msgid "resources" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml70(para) +msgid "" +"This section contains the declaration of the resources of the template. This" +" section with at least one resource must be defined in any HOT template, or " +"the template would not really do anything when being instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml77(term) +msgid "outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml79(para) +msgid "" +"This section specifies output parameters available to users once the " +"template has been instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml88(title) +msgid "Parameter groups section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml89(para) +msgid "" +"The parameter_groups section specifies how the input " +"parameters should be grouped and the order to provide the parameters in. " +"These groups are typically used to describe expected behavior for downstream" +" user interfaces." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml92(para) +msgid "" +"These groups are specified in a list with each group containing a list of " +"associated parameters. The lists are used to denote the expected order of " +"the parameters. A parameter can only be included in one group. Use the name " +"of the parameter to add it to a group. The parameters details are defined in" +" the parameters section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml105(term) +#: ./doc/user-guide/hot/section_hot_spec.xml166(term) +msgid "label" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml107(para) +msgid "" +"A human-readable label that defines the associated group of parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml113(para) +msgid "A human-readable description of the parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml119(para) +msgid "A list of parameters that belong with this parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml123(term) +#: ./doc/user-guide/hot/section_hot_spec.xml151(term) +msgid "param name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml125(para) +msgid "" +"The name of a parameter defined in the parameters " +"section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml132(title) +msgid "Parameters section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml133(para) +msgid "" +"The parameters section defines input parameters that have" +" to be provided when instantiating the template. Such parameters are " +"typically used to customize each deployment, or for binding to environment " +"specifics like certain images." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml137(para) +msgid "" +"Each parameter is specified in a separated nested block with the name of the" +" parameter defined in the first line and additional attributes such as a " +"type or a default value defined as nested elements:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml153(para) +msgid "The name of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml157(term) +#: ./doc/user-guide/hot/section_hot_spec.xml397(term) +msgid "type" +msgstr "type" + +#: ./doc/user-guide/hot/section_hot_spec.xml159(para) +msgid "" +"The type of the parameter. Supported types are string, " +"number, comma_delimited_list, " +"json and boolean." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml162(para) +#: ./doc/user-guide/hot/section_hot_spec.xml400(para) +#: ./doc/user-guide/hot/section_hot_spec.xml519(para) +msgid "This attribute is required." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml168(para) +msgid "A human readable name for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml169(para) +#: ./doc/user-guide/hot/section_hot_spec.xml176(para) +#: ./doc/user-guide/hot/section_hot_spec.xml184(para) +#: ./doc/user-guide/hot/section_hot_spec.xml202(para) +#: ./doc/user-guide/hot/section_hot_spec.xml252(para) +#: ./doc/user-guide/hot/section_hot_spec.xml423(para) +#: ./doc/user-guide/hot/section_hot_spec.xml432(para) +#: ./doc/user-guide/hot/section_hot_spec.xml440(para) +#: ./doc/user-guide/hot/section_hot_spec.xml510(para) +msgid "This attribute is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml175(para) +msgid "A human readable description for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml180(term) +msgid "default" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml182(para) +msgid "" +"A default value for the parameter. This value is used if the user doesn't " +"specify his own value during deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml188(term) +msgid "hidden" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml190(para) +msgid "" +"Defines whether the parameters should be hidden when a user requests " +"information about a stack created from the template. This attribute can be " +"used to hide passwords specified as parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml193(para) +msgid "This attribute is optional and defaults to false." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml197(term) +msgid "constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml199(para) +msgid "" +"A list of constraints to apply. The constraints are validated by the " +"Orchestration engine when a user deploys a stack. The stack creation fails " +"if the parameter value doesn't comply to the constraints." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml206(para) +msgid "" +"The following example shows a minimalistic definition of two parameters:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml217(para) +msgid "" +"The description and the label are optional, but defining these attributes is" +" good practice to provide useful information about the role of the parameter" +" to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml222(title) +msgid "Parameter constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml223(para) +msgid "" +"The constraints block of a parameter definition defines " +"additional validation constraints that apply to the value of the parameter. " +"The parameter values provided by a user are validated against the " +"contrainsts at instantiation time. The contrainsts are defined as a list " +"with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml233(term) +msgid "constraint type" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml235(para) +msgid "" +"Type of constraint to apply. The set of currently supported constraints is " +"given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml240(term) +msgid "constraint definition" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml242(para) +msgid "" +"The actual constraint, depending on the constraint type. The concrete syntax" +" for each constraint type is given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml249(para) +msgid "" +"A description of the constraint. The text is presented to the user when the " +"value he defines violates the constraint. If ommitted, a default validation " +"message is presented to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml256(para) +msgid "" +"The following example shows the definition of a string parameter with two " +"constraints. Note that while the descriptions for each constraint are " +"optional, it is good practice to provide concrete descriptions to present " +"useful messages to the user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml271(para) +msgid "" +"While the descriptions for each constraint are optional, it is good practice" +" to provide concrete descriptions so useful messages can be presented to the" +" user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml275(para) +msgid "" +"The following sections list the supported types of parameter constraints, " +"along with the syntax for each type." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml278(title) +msgid "length" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml279(para) +msgid "" +"The length constraint applies to parameters of type " +"string. It defines a lower and upper limit for the length" +" of the string value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml281(para) +msgid "The syntax of the length constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml283(para) +msgid "" +"It is possible to define a length constraint with only a lower limit or an " +"upper limit. However, at least one of min or " +"max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml287(title) +msgid "range" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml288(para) +msgid "" +"The range constraint applies to parameters of type " +"number. It defines a lower and upper limit for the " +"numeric value of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml290(para) +msgid "The syntax of the range constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml292(para) +msgid "" +"It is possible to define a range constraint with only a lower limit or an " +"upper limit. However, at least one of min or " +"max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml294(para) +msgid "" +"The minimum and maximum boundaries are included in the range. For example, " +"the following range constraint would allow for all numeric values between 0 " +"and 10:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml299(title) +msgid "allowed_values" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml300(para) +msgid "" +"The allowed_values constraint applies to parameters of " +"type string or number. It specifies a " +"set of possible values for a parameter. At deployment time, the user-" +"provided value for the respective parameter must match one of the elements " +"of the list." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml304(para) +msgid "The syntax of the allowed_values constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml306(para) +msgid "Alternatively, the following YAML list notation can be used:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml324(title) +msgid "allowed_pattern" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml325(para) +msgid "" +"The allowed_pattern constraint applies to parameters of " +"type string. It specifies a regular expression against " +"which a user-provided parameter value must evaluate at deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml328(para) +msgid "The syntax of the allowed_pattern constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml341(title) +msgid "custom_constraint" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml342(para) +msgid "" +"The custom_constraint constraint adds an extra step of " +"validation, generally to check that the specified resource exists in the " +"backend. Custom constraints get implemented by plug-ins and can provide any " +"kind of advanced constraint validation logic." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml346(para) +msgid "The syntax of the custom_constraint constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml348(para) +msgid "" +"The name attribute specifies the concrete type of custom " +"constraint. It corresponds to the name under which the respective validation" +" plugin has been registered in the Orchestration engine." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml361(title) +msgid "Pseudo Parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml362(para) +msgid "" +"In addition to parameters defined by a template author, the Orchestration " +"module also creates two parameters for every stack that allow referential " +"access to the stack's name and identifier. These parameters are named " +"OS::stack_name for the stack name and " +"OS::stack_id for the stack identifier. These values are " +"accessible via the get_param intrinsic function, just " +"like user-defined parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml372(title) +msgid "Resources section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml373(para) +msgid "" +"The resources section defines actual resources that make " +"up a stack deployed from the HOT template (for instance compute instances, " +"networks, storage volumes)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml376(para) +msgid "" +"Each resource is defined as a separate block in the " +"resources section with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml390(term) +#: ./doc/user-guide/hot/section_hot_spec.xml551(term) +msgid "resource ID" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml392(para) +msgid "" +"A resource ID which must be unique within the resources " +"section of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml399(para) +msgid "" +"The resource type, such as OS::Nova::Server or " +"OS::Neutron::Port." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml404(term) +msgid "properties" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml406(para) +msgid "" +"A list of resource-specific properties. The property value can be provided " +"in place, or via a function (see Intrinsic functions)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml412(term) +msgid "metadata" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml414(para) +msgid "Resource-specific metadata." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml419(term) +msgid "depends_on" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml421(para) +msgid "Dependencies of the resource on one or more resources of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml422(para) +msgid "" +"See Resource " +"dependencies for details." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml427(term) +msgid "update_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml429(para) +msgid "" +"Update policy for the resource, in the form of a nested dictionary. Whether " +"update policies are supported and what the exact semantics are depends on " +"the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml436(term) +msgid "deletion_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml438(para) +msgid "" +"Deletion policy for the resource. Which type of deletion policy is supported" +" depends on the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml444(para) +msgid "" +"Depending on the type of resource, the resource block might include more " +"resource specific data." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml446(para) +msgid "" +"All resource types that can be used in CFN templates can also be used in HOT" +" templates, adapted to the YAML structure as outlined above." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml448(para) +msgid "" +"The following example demonstrates the definition of a simple compute " +"resource with some fixed property values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml457(title) +msgid "Resource dependencies" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml458(para) +msgid "" +"The depends_on attribute of a resource defines a " +"dependency between this resource and one or more other resources." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml460(para) +msgid "" +"If a resource depends on just one other resource, the ID of the other " +"resource is specified as string of the depends_on " +"attribute, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml470(para) +msgid "" +"If a resource depends on more than one other resources, the value of the " +"depends_on attribute is specified as a list of resource " +"IDs, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml487(title) +msgid "Outputs section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml488(para) +msgid "" +"The outputs section defines output parameters that should" +" be available to the user once a stack has been created. This would be, for " +"example, parameters such as IP addresses of deployed instances, or URLs of " +"web applications deployed as part of a stack." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml492(para) +msgid "" +"Each output parameter is defined as a separate block within the outputs " +"section according to the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml500(term) +#: ./doc/user-guide/hot/section_hot_spec.xml638(term) +msgid "parameter name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml502(para) +msgid "" +"The output parameter name, which must be unique within the " +"outputs section of a template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml509(para) +msgid "A short description of the output parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml514(term) +msgid "parameter value" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml516(para) +msgid "" +"The value of the output parameter. This value is usually resolved by means " +"of a function. See Intrinsic functions for details " +"about the functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml523(para) +msgid "" +"The example below shows how the IP address of a compute resource can be " +"defined as an output parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml532(title) +msgid "Intrinsic functions" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml533(para) +msgid "" +"HOT provides a set of intrinsic functions that can be used inside templates " +"to perform specific tasks, such as getting the value of a resource attribute" +" at runtime. The following section describes the role and syntax of the " +"intrinsic functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml538(title) +msgid "get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml539(para) +msgid "" +"The get_attr function references an attribute of a " +"resource. The attribute value is resolved at runtime using the resource " +"instance created from the respective resource definition." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml542(para) +msgid "The syntax of the get_attr function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml553(para) +msgid "The resource ID for which the attribute needs to be resolved." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml554(para) +msgid "" +"The resource ID must exist in the resources section of " +"the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml558(term) +msgid "attribute name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml560(para) +msgid "" +"The attribute name to be resolved. If the attribute returns a complex data " +"structure such as a list or a map, then subsequent keys or indexes can be " +"specified. These additional parameters are used to navigate the data " +"structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml567(para) +msgid "" +"The following example demonstrates how to use the " +"get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml580(para) +msgid "" +"In this example, if the networks attribute contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml583(para) +msgid "" +"then the value of the get_attr function would resolve to " +"10.0.0.1 (first item of the private " +"entry in the networks map)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml588(para) +msgid "" +"The get_file function returns the content of a file into " +"the template. It is generally used as a file inclusion mechanism for files " +"containing scripts or configuration files." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml591(para) +msgid "The syntax of the get_file function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml593(para) +msgid "" +"The content key is used to look up the " +"files dictionary that is provided in the REST API call. " +"The Orchestration client command () is " +"get_file aware and will populate the " +"files dictionnary with the actual content of fetched " +"paths and URLs. The Orchestration client command supports relative paths and" +" will transform these to the absolute URLs required by the Orcestration API." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml600(para) +msgid "" +"The get_file argument must be a static path or URL and " +"not rely on intrinsic functions like get_param. the " +"Orchestration client does not process intrinsic functions (they are only " +"processed by the Orchestration engine)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml605(para) +msgid "" +"The example below demonstrates the get_file function " +"usage with both relative and absolute URLs:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml621(para) +msgid "" +"The files dictionary generated by the Orchestration " +"client during instantiation of the stack would contain the following keys: *" +" file:///path/to/my_instance_user_data.sh * " +"http://example.com/my_other_instance_user_data.sh*" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml628(para) +msgid "" +"The get_param function references an input parameter of a" +" template. It resolves to the value provided for this input parameter at " +"runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml630(para) +msgid "The syntax of the get_param function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml640(para) +msgid "" +"The parameter name to be resolved. If the parameters returns a complex data " +"structure such as a list or a map, then subsequent keys or indexes can be " +"specified. These additional parameters are used to navigate the data " +"structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml647(para) +msgid "" +"The following example demonstrates the use of the " +"get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml663(para) +msgid "" +"In this example, if the instance_type and " +"server_data parameters contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml668(para) +msgid "" +"then the value of the property flavor would resolve to " +"m1.tiny, metadata would resolve to " +"{\"foo\": \"bar\"} and key_name would " +"resolve to a_key." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml674(para) +msgid "" +"The get_resource function references another resource " +"within the same template. At runtime, it is resolved to reference the ID of " +"the referenced resource, which is resource type specific. For example, a " +"reference to a floating IP resource returns the respective IP address at " +"runtime. The syntax of the get_resource function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml680(para) +msgid "" +"The resource ID of the referenced resource is given as single parameter to " +"the get_resource function." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml682(para) +msgid "For exemple:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml697(para) +msgid "" +"The list_join function joins a list of strings with the " +"given delimiter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml698(para) +msgid "The syntax of the list_join function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml704(para) +msgid "This resolve to the string one, two, and three." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml707(title) +msgid "resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml708(para) +msgid "" +"The resource_facade function retrieves data in a parent " +"provider template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml709(para) +msgid "" +"A provider template provdes a custom definition of a resource, called its " +"facade. For more information about custom templates, see . The syntax of the " +"resource_facade function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml713(para) +msgid "" +"data type can be one of metadata, " +"deletion_policy or update_policy." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml718(para) +msgid "" +"The str_replace function dynamically constructs strings " +"by providing a template string with placeholders and a list of mappings to " +"assign values to those placeholders at runtime. The placeholders are " +"replaced with mapping values wherever a mapping key exactly matches a " +"placeholder." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml722(para) +msgid "The syntax of the str_replace function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml728(term) +msgid "template" +msgstr "Modèle" + +#: ./doc/user-guide/hot/section_hot_spec.xml730(para) +msgid "" +"Defines the template string that contains placeholders which will be " +"substituted at runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml735(term) +msgid "params" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml737(para) +msgid "" +"Provides parameter mappings in the form of dictionary. Each key refers to a " +"placeholder used in the template attribute." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml742(para) +msgid "" +"The following example shows a simple use of the " +"str_replace function in the outputs section of a template" +" to build a URL for logging into a deployed application:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml758(para) +msgid "" +"The following examples show the use of the str_replace " +"function to build an instance initialization script:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hello_world.xml15(title) +msgid "Writing a hello world HOT template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml16(para) +msgid "" +"HOT is a new template format meant to replace the CloudFormation-compatible " +"format (CFN) as the native format supported by the Orchestration module over" +" time. This guide is targeted towards template authors and explains how to " +"write HOT templates based on examples. A detailed specification of HOT can " +"be found at ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml22(para) +msgid "" +"This section gives an introduction on how to write HOT templates, starting " +"from very basic steps and then going into more and more detail by means of " +"examples." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml26(title) +msgid "A most basic template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml27(para) +msgid "" +"The most basic template you can think of contains only a single resource " +"definition using only predefined properties. For example, the template below" +" could be used to deploy a single compute instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml41(para) +msgid "" +"Each HOT template has to include the " +"heat_template_version key with value " +"2013-05-23, the current HOT version. While the " +"description key is optional, it is good practice to " +"include some useful text that describes what users can do with the template." +" In case you want to provide a longer description that does not fit on a " +"single line, you can provide multi-line text in YAML, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml50(para) +msgid "" +"The resources section is required and must contain at " +"least one resource definition. In the above example, a compute instance is " +"defined with fixed values for the key_name, " +"image and flavor properties." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml54(para) +msgid "" +"All the defined elements (key pair, image, flavor) have to exist in the " +"OpenStack environment where the template is used." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml60(title) +msgid "Input parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml61(para) +msgid "" +"Input parameters defined in the parameters section of a " +"template allow users to customize a template during deployment. For example," +" this allows for providing custom key pair names or image IDs to be used for" +" a deployment. From a template author's perspective, this helps to make a " +"template more easily reusable by avoiding hardcoded assumptions." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml66(para) +msgid "" +"The following example extends the previous template to provide parameters " +"for the key pair, image and flavor properties of the resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml93(para) +msgid "" +"Values for the three parameters must be defined by the template user during " +"the deployment of a stack. The get_param intrinsic " +"function retrieves a user-specified value for a given parameter and uses " +"this value for the associated resource property." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml97(para) +msgid "" +"For more information about intrinsic functions, see ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml100(title) +msgid "Providing default values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml101(para) +msgid "" +"You can provide default values for parameters. If a user doesn't define a " +"value for a parameter, the default value is used during the stack " +"deployment. The following example defines a default value " +"m1.small for the flavor property:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml112(para) +msgid "" +"If a template doesn't define a default value for a parameter, then the user " +"must define the value, otherwise the stack creation will fail." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml117(title) +msgid "Hidding parameters values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml118(para) +msgid "" +"The values that a user provides when deploying a stack are available in the " +"stack details and can be accessed by any user in the same tenant. To hide " +"the value of a parameter, use the hidden boolean " +"attribute of the parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml129(title) +msgid "Restricting user input" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml130(para) +msgid "" +"You can restrict the values of an input parameter to make sure that the user" +" defines valid data for this parameter. The constraints " +"property of an input parameter defines a list of constraints to apply for " +"the parameter. The following example restricts the flavor" +" parameter to a list of three possible values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml143(para) +msgid "" +"The following example defines multiple contraints for a password definition:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml157(para) +msgid "" +"The list of supported constraints is available in the section." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml160(para) +msgid "" +"You can define multiple constraints of the same type. Especially in the case" +" of allowed patterns this not only allows for keeping regular expressions " +"simple and maintainable, but also for keeping error messages to be presented" +" to users precise." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml169(title) +msgid "Template outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml170(para) +msgid "" +"In addition to template customization through input parameters, you can " +"provide information about the resources created during the stack deployment " +"to the users in the outputs section of a template. In the" +" following example the output section provides the IP address of the " +"my_instance resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml179(para) +msgid "" +"Output values are typically resolved using intrinsic function such as the " +"get_attr. See for more information about intrinsic functions.." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml183(para) +msgid "" +"See for more information about the " +"outputs section." +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_basic_resources.xml4(title) +msgid "Instances" +msgstr "Instances" + +#: ./doc/user-guide/hot/section_basic_resources.xml11(title) +msgid "Manage instances" +msgstr "Gérer les instances" + +#: ./doc/user-guide/hot/section_basic_resources.xml13(title) +msgid "Create an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml14(para) +msgid "" +"Use the OS::Nova::Server " +"resource to create a Compute instance. The flavor " +"property is the only mandatory one, but you need to define a boot source " +"using one of the image or " +"block_device_mapping properties." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml17(para) +msgid "" +"You also need to define the networks property to indicate" +" to which networks your instance must connect if multiple networks are " +"available in your tenant." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml19(para) +msgid "" +"The following example creates a simple instance, booted from an image, and " +"connecting to the private network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml31(title) +msgid "Connect an instance to a network" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml32(para) +msgid "" +"Use the networks property of an OS::Nova::Server " +"resource to define which networks an instance should connect to. Define each" +" network as a YAML map, containing one of the following keys:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml38(literal) +msgid "port" +msgstr "port" + +#: ./doc/user-guide/hot/section_basic_resources.xml41(para) +msgid "" +"The ID of an existing Networking port. You usually create this port in the " +"same template using an OS::Neutron::Port" +" resource. You will be able to associate a floating IP to this port, and the" +" port to your Compute instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml49(literal) +msgid "network" +msgstr "network" + +#: ./doc/user-guide/hot/section_basic_resources.xml52(para) +msgid "" +"The name or ID of an existing network. You don't need to create an " +"OS::Neutron::Port" +" resource if you use this property, but you will not be able to associate a " +"floating IP with the instance interface in the template." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml59(para) +msgid "" +"The following example demonstrates the use of the port " +"and network properties:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml86(title) +msgid "Create and associate security groups to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml87(para) +msgid "" +"Use the OS::Neutron::SecurityGroup" +" resource to create security groups." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml89(para) +msgid "" +"Define the security_groups property of the OS::Neutron::Port" +" resource to associate security groups to a port, then associate the port to" +" an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml92(para) +msgid "" +"The following example creates a security group allowing inbound connections " +"on ports 80 and 443 (web server) and associates this security group to an " +"instance port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml128(title) +msgid "Create and associate a floating IP to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml129(para) +msgid "" +"You can use two sets of resources to create and associate floating IPs to " +"instances." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml132(title) +msgid "OS::Nova resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml133(para) +msgid "" +"Use the OS::Nova::FloatingIP" +" resource to create a floating IP, and the OS::Nova::FloatingIPAssociation" +" resource to associate the floating IP to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml136(para) +msgid "" +"The following example creates an instance and a floating IP, and associate " +"the floating IP to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml159(title) +msgid "OS::Neutron resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml161(para) +msgid "" +"The Networking service (neutron) must be enabled on your OpenStack " +"deployment to use these resources." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml164(para) +msgid "" +"Use the OS::Neutron::FloatingIP" +" resource to create a floating IP, and the OS::Neutron::FloatingIPAssociation" +" resource to associate the floating IP to a port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml189(title) +msgid "Enable remote access to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml190(para) +msgid "" +"The key_name attribute of the OS::Nova::Server " +"resource defines the key pair to use to enable SSH remote access:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml200(para) +msgid "" +"For more information about key pairs, see the Configure access and security " +"for instances section of the OpenStack user guide." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml205(title) +msgid "Create a key pair" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml206(para) +msgid "" +"You can create new key pairs with the OS::Nova::KeyPair" +" resource. Key pairs can be imported or created during the stack creation." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml208(para) +msgid "" +"If the public_key property is not specified, the " +"Orchestration module creates a new key pair. If the " +"save_private_key property is set to " +"true, the private_key attribute of the" +" resource holds the private key." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml211(para) +msgid "" +"The following example creates a new key pair and uses it as authentication " +"key for an instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml234(title) +msgid "Manage networks" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml236(title) +msgid "Create a network and a subnet" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml238(para) +msgid "" +"The Networking service (neutron) must be enabled on your OpenStack " +"deployment to create and manage networks and subnets. Networks and subnets " +"cannot be created if your deployment uses legacy networking (nova-network)." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml242(para) +msgid "" +"Use the OS::Neutron::Net " +"resource to create a network, and the OS::Neutron::Subnet" +" resource to provide a subnet for this network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml257(title) +msgid "Create and manage a router" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml258(para) +msgid "" +"Use the OS::Neutron::Router" +" resource to create a router. You can define its gateway with the " +"external_gateway_info property:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml265(para) +msgid "" +"You can connect subnets to routers with the OS::Neutron::RouterInterface" +" resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml275(title) +msgid "Complete network example" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml276(para) +msgid "The following example creates a network stack:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml279(para) +msgid "A network and an associated subnet." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml282(para) +msgid "A router with an external gateway." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml285(para) +msgid "An interface to the new subnet for the new router." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml288(para) +msgid "" +"In this example, the public network is an existing shared" +" network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml315(title) +msgid "Manage volumes" +msgstr "Gérer des volumes" + +#: ./doc/user-guide/hot/section_basic_resources.xml318(para) +msgid "" +"Use the OS::Cinder::Volume" +" resource to create a new Block Storage volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml326(para) +msgid "" +"The volumes that you create are empty by default. Use the " +"image property to create a bootable volume from an " +"existing image:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml334(para) +msgid "" +"You can also create new volumes from another volume, a volume snapshot, or a" +" volume backup. Use the source_volid, " +"snapshot_id or backup_id properties to" +" create a new volume from an existing source." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml337(para) +msgid "For example, to create a new volume from a backup:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml343(para) +msgid "" +"In this example the size property is not defined because " +"the Block Storage service uses the size of the backup to define the size of " +"the new volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml348(para) +msgid "" +"Use the OS::Cinder::VolumeAttachment" +" resource to attach a volume to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml350(para) +msgid "" +"The following example creates a volume and an instance, and attaches the " +"volume to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml371(title) +msgid "Boot an instance from a volume" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml372(para) +msgid "" +"Use the block_device_mapping property of the " +"OS::Nova::Server " +"resource to define a volume used to boot the instance. This property is a " +"list of volumes to attach to the instance before its boot." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml375(para) +msgid "" +"The following example creates a bootable volume from an image, and uses it " +"to boot an instance:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_composition.xml4(title) +msgid "Template composition" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml5(para) +msgid "" +"When writing complex templates you are encouraged to break up your template " +"into separate smaller templates. These can then be brought together using " +"template resources. This is a mechanism to define a resource using a " +"template, thus composing one logical stack with multiple templates." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml9(para) +msgid "" +"Template resources provide a feature similar to the AWS::CloudFormation::Stack" +" resource, but also provide a way to:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml13(para) +msgid "Define new resource types and build your own resource library." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml16(para) +msgid "Override the default behaviour of existing resource types." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml19(para) +msgid "To achieve this:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml22(para) +msgid "" +"The Orchestration client gets the associated template files and passes them " +"along in the files section of the POST " +"stacks/ API request." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml26(para) +msgid "" +"The environment in the Orchestration engine manages the mapping of resource " +"type to template creation." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml30(para) +msgid "" +"The Orchestration engine translates template parameters into resource " +"properties." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml34(para) +msgid "" +"The following examples illustrate how you can use a custom template to " +"define new types of resources. These examples use a custom template stored " +"in a my_nova.yml file:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml53(title) +msgid "Use the template filename as type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml54(para) +msgid "" +"The following template defines the my_nova.yaml file as " +"value for the type property of a resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml62(para) +msgid "" +"The key_name argument of the " +"my_nova.yaml template gets its value from the " +"key_name property of the new template." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml65(para) +msgid "" +"The above reference to my_nova.yaml assumes it is in the " +"same directory. You can use any of the following forms:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml69(para) +msgid "Relative path (my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml72(para) +msgid "" +"Absolute path (file:///home/user/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml75(para) +msgid "" +"Http URL (http://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml78(para) +msgid "" +"Https URL (https://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml82(para) +#: ./doc/user-guide/hot/section_composition.xml105(para) +msgid "To create the stack run:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml87(title) +msgid "Define a new resource type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml88(para) +msgid "" +"You can associate a name to the my_noya.yaml template in " +"an environment file. If the name is already known by the Orchestration " +"module then your new resource will override the default one." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml91(para) +msgid "" +"In the following example a new OS::Nova::Server resource " +"overrides the default resource of the same name." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml93(para) +msgid "" +"An env.yaml environment file holds the definition of the " +"new resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml97(para) +msgid "" +"See for more detail about environment " +"files." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml99(para) +msgid "" +"You can now use the new OS::Nova::Server in your new " +"template:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_advanced_topics.xml4(title) +msgid "Advanced topics" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml9(title) +msgid "Load balancer" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml10(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml14(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml18(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml26(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml30(para) +msgid "TODO" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml13(title) +msgid "Firewall" +msgstr "Pare-feu" + +#: ./doc/user-guide/hot/section_advanced_topics.xml17(title) +msgid "VPN" +msgstr "VPN" + +#: ./doc/user-guide/hot/section_advanced_topics.xml23(title) +msgid "Auto scaling" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml25(title) +msgid "Alarming" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml29(title) +msgid "Up scaling and down scaling" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_environment.xml4(title) +msgid "Environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml5(para) +msgid "" +"The environment affects the runtime behaviour of a template. It provides a " +"way to override the resource implementations and a mechanism to place " +"parameters that the service needs." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml8(para) +msgid "" +"To fully understand the runtime behavior you have to consider what plug-ins " +"are installed on the cloud you're using." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml12(title) +msgid "Environment file format" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml13(para) +msgid "The environment is a yaml text file that contains two main sections:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml20(para) +msgid "A map of key/pair values." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml25(literal) +msgid "resource_registry" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml28(para) +msgid "Definition of custom resources." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml32(para) +msgid "" +"Use the -e option of the command to create a stack using " +"with the environment defined in such a file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml34(para) +msgid "" +"You can also provide environment parameters as a list of key/value pairs " +"using the -P option of the command." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml36(para) +msgid "" +"In the following example the environment is read from the " +"my_env.yaml file and an extra parameter is provided using" +" the -P option:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml42(title) +msgid "Global and effective environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml43(para) +msgid "" +"The environment used for a stack is the combination of the environment you " +"use with the template for the stack, and a global environment that is " +"determined by your cloud operator. An entry in the user environment takes " +"precedence over the global environment. OpenStack includes a default global " +"environment, but you cloud operator can add additional environment entries." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml69(title) +msgid "Define values for a template arguments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml70(para) +msgid "" +"You can define values for the template arguments in the " +"parameters section of an environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml79(title) +msgid "Create and override resources" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml80(para) +msgid "" +"You can create or override resources in the " +"resource_registry section of an environment file. The " +"resource you provide in this manner must have an identifier, and references " +"either other resources IDs or the URL of an existing template file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml84(para) +msgid "" +"The following example maps the new " +"OS::Networking::FloatingIP resource to the existing " +"OS::Nova::FloatingIP" +" resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml88(para) +msgid "You can use wilcards to map multiple resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml91(para) +msgid "" +"To create or override a resource with a custom resource, create a template " +"file to define this resource, and provide the URL to the template file in " +"the environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml96(para) +msgid "" +"The supported URL scheme are file, " +"http and https." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml98(para) +msgid "" +"The template file extension must be .yaml or " +".template, or it will not be treated as a custom template" +" resource." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml101(para) +msgid "" +"You can limit the usage of a custom resource to a specific resource of the " +"template:" +msgstr "" + #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./doc/user-guide/section_sdk_configure_instances.xml0(None) +#: ./doc/user-guide/hot/section_environment.xml0(None) msgid "translator-credits" msgstr "Olivier Buisson , 2012 | Cloudwatt Team , 2013" diff --git a/doc/user-guide/locale/ja.po b/doc/user-guide/locale/ja.po index cf0a12d892..73b36a3890 100644 --- a/doc/user-guide/locale/ja.po +++ b/doc/user-guide/locale/ja.po @@ -7,9 +7,9 @@ msgid "" msgstr "" "Project-Id-Version: OpenStack Manuals\n" -"POT-Creation-Date: 2014-11-02 09:33+0000\n" -"PO-Revision-Date: 2014-11-03 01:00+0000\n" -"Last-Translator: Tomoyuki KATO \n" +"POT-Creation-Date: 2014-11-11 16:08+0000\n" +"PO-Revision-Date: 2014-11-11 16:22+0000\n" +"Last-Translator: openstackjenkins \n" "Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -1514,6 +1514,7 @@ msgstr "セキュリティグループを何も作成していなければ、標 #: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml179(guilabel) #: ./doc/user-guide/section_sdk_neutron.xml7(title) +#: ./doc/user-guide/hot/section_advanced_topics.xml7(title) msgid "Networking" msgstr "ネットワーク" @@ -3402,6 +3403,11 @@ msgid "FLOATING_IP_ADDRESS" msgstr "FLOATING_IP_ADDRESS" #: ./doc/user-guide/section_cli_nova_floating_ips.xml102(para) +#: ./doc/user-guide/hot/section_hot_spec.xml311(para) +#: ./doc/user-guide/hot/section_hot_spec.xml330(para) +#: ./doc/user-guide/hot/section_hot_spec.xml351(para) +#: ./doc/user-guide/hot/section_hot_spec.xml702(para) +#: ./doc/user-guide/hot/section_basic_resources.xml320(para) msgid "For example:" msgstr "例えば" @@ -6656,6 +6662,7 @@ msgid "" msgstr "ボリュームは、永続ストレージを使用するためにインスタンスに接続するブロックストレージデバイスです。ボリュームを稼働中のインスタンスに接続したり切断したりできます。また、いつでも別のインスタンスに接続できます。ボリュームからスナップショットを作成したり、削除したりできます。管理ユーザーのみがボリューム種別を作成できます。" #: ./doc/user-guide/section_dashboard_manage_volumes.xml16(title) +#: ./doc/user-guide/hot/section_basic_resources.xml317(title) msgid "Create a volume" msgstr "ボリュームの作成" @@ -6776,6 +6783,7 @@ msgid "" msgstr "ダッシュボードのボリュームタブにボリュームが表示されます。" #: ./doc/user-guide/section_dashboard_manage_volumes.xml132(title) +#: ./doc/user-guide/hot/section_basic_resources.xml347(title) msgid "Attach a volume to an instance" msgstr "ボリュームのインスタンスへの接続" @@ -7033,7 +7041,2139 @@ msgid "" " method:" msgstr "セキュリティグループにルールを追加するために、novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create メソッドを呼び出します。" +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_software_deployment.xml4(title) +msgid "Software configuration" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml5(para) +msgid "" +"There are a variety of options to configure the software which runs on the " +"servers in your stack. These can be broadly divided into the following:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml9(para) +msgid "Custom image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml12(para) +#: ./doc/user-guide/hot/section_software_deployment.xml59(title) +msgid "User-data boot scripts and cloud-init" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml15(para) +msgid "Software deployment resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml18(para) +msgid "" +"This section will describe each of these options and provide examples for " +"using them together in your stacks." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml22(title) +msgid "Image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml23(para) +msgid "" +"The first opportunity to influence what software is configured on your " +"servers is by booting them with a custom-built image. There are a number of " +"reasons you might want to do this, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml28(para) +msgid "" +" - since the required software is already on " +"the image there is no need to download and install anything at boot time." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml32(para) +msgid "" +" - software downloads can fail for a " +"number of reasons including transient network failures and inconsistent " +"software repositories." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml36(para) +msgid "" +" - custom built images can be verified" +" in test environments before being promoted to production." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml40(para) +msgid "" +" - post-boot configuration " +"may depend on agents already being installed and enabled" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml44(para) +msgid "A number of tools are available for building custom images, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml47(para) +msgid "" +"diskimage-" +"builder image building tools for OpenStack" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml50(para) +msgid "" +"imagefactory builds images for a " +"variety of operating system/cloud combinations" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml54(para) +msgid "" +"Examples in this guide which require custom images will use diskimage-" +"builder." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml60(para) +msgid "" +"When booting a server it is possible to specify the contents of the user-" +"data to be passed to that server. This user-data is made available either " +"from configured config-drive or from the Metadata service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml63(para) +msgid "" +"How this user-data is consumed depends on the image being booted, but the " +"most commonly used tool for default cloud images is Cloud-init." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml65(para) +msgid "" +"Whether the image is using Cloud-init or " +"not, it should be possible to specify a shell script in the user_data " +"property and have it be executed by the server during boot:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml80(para) +msgid "" +": debugging these scripts it is often useful to view" +" the boot log using nova console-log <server-id> to" +" view the progress of boot script execution." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml84(para) +msgid "" +"Often there is a need to set variable values based on parameters or " +"resources in the stack. This can be done with the " +"str_replace intrinsic function:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml106(para) +msgid "" +": If a stack-update is performed and there are " +"any changes at all to the content of user_data then the server will be " +"replaced (deleted and recreated) so that the modified boot configuration can" +" be run on a new server." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml111(para) +msgid "" +"When these scripts grow it can become difficult to maintain them inside the " +"template, so the get_file intrinsic function can be used " +"to maintain the script in a separate file:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml131(para) +msgid "" +": str_replace can replace any " +"strings, not just strings starting with $. However doing " +"this for the above example is useful because the script file can be executed" +" for testing by passing in environment variables." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml137(title) +msgid "Choosing the user_data_format" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml138(para) +msgid "" +"The OS::Nova::Server " +"user_data_format property determines how the user_data should be formatted " +"for the server. For the default value HEAT_CFNTOOLS, the " +"user_data is bundled as part of the heat-cfntools cloud-init boot " +"configuration data. While HEAT_CFNTOOLS is the default " +"for user_data_format, it is considered legacy and " +"RAW or SOFTWARE_CONFIG will generally " +"be more appropriate." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml144(para) +msgid "" +"For RAW the user_data is passed to Nova unmodified. For a" +" Cloud-" +"init enabled image, the following are both valid " +"RAW user-data:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml166(para) +msgid "" +"For SOFTWARE_CONFIG user_data is bundled as part of the " +"software config data, and metadata is derived from any associated software " +"deployment resources." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml171(title) +msgid "Signals and wait conditions" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml172(para) +msgid "" +"Often it is necessary to pause further creation of stack resources until the" +" boot configuration script has notified that it has reached a certain state." +" This is usually either to notify that a service is now active, or to pass " +"out some generated data which is needed by another resource. The resources " +"OS::Heat::WaitCondition" +" and OS::Heat::SwiftSignal" +" both perform this function using different techniques and tradeoffs." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml178(para) +msgid "" +"OS::Heat::WaitCondition" +" is implemented as a call to the Orchestration API resource signal. " +"The token is created using credentials for a user account which is scoped " +"only to the wait condition handle resource. This user is created when the " +"handle is created, and is associated to a project which belongs to the " +"stack, in an identity domain which is dedicated to the orchestration " +"service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml184(para) +#: ./doc/user-guide/hot/section_software_deployment.xml267(para) +msgid "" +"Sending the signal is a simple HTTP request, as with this example using " +"curl:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml188(para) +msgid "" +"The JSON containing the signal data is expected to be of the following " +"format:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml195(para) +msgid "" +"All of these values are optional, and if not specified will be set to the " +"following defaults:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml203(para) +msgid "" +"If status is set to FAILURE then the " +"resource (and the stack) will go into a FAILED state " +"using the reason as failure reason." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml205(para) +msgid "" +"The following template example uses the convenience attribute " +"curl_cli which builds a curl command with a valid token:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml263(para) +msgid "" +"OS::Heat::SwiftSignal" +" is implemented by creating an Object Storage API temporary URL which is " +"populated with signal data with an HTTP PUT. The orchestration service will " +"poll this object until the signal data is available. Object versioning is " +"used to store multiple signals." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml269(para) +msgid "" +"The above template example only needs to have the type " +"changed to the swift signal resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml281(para) +msgid "" +"The decision to use OS::Heat::WaitCondition" +" or OS::Heat::SwiftSignal" +" will depend on a few factors:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml285(para) +msgid "" +"OS::Heat::SwiftSignal" +" depends on the availability of an Object Storage API" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml289(para) +msgid "" +"OS::Heat::WaitCondition" +" depends on whether the orchestration service has been configured with a " +"dedicated stack domain (which may depend on the availability of an Identity " +"V3 API)." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml294(para) +msgid "" +"The preference to protect signal URLs with token authentication or a secret " +"webhook URL." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml300(title) +msgid "Software config resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml301(para) +msgid "" +"Boot configuration scripts can also be managed as their own resources. This " +"allows configuration to be defined once and run on multiple server " +"resources. These software-config resources are stored and retrieved via " +"dedicated calls to the Orchestration API. It is not possible to " +"modify the contents of an existing software-config resource, so a stack-" +"update which changes any existing software-config resource will result in " +"API calls to create a new config and delete the old one." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml308(para) +msgid "" +"The resource OS::Heat::SoftwareConfig" +" is used for storing configs represented by text scripts, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml326(para) +msgid "" +"The resource OS::Heat::CloudConfig" +" allows Cloud-" +"init cloud-config to be represented as template YAML rather than a " +"block string. This allows intrinsic functions to be included when building " +"the cloud-config. This also ensures that the cloud-config is valid YAML, " +"although no further checks for valid cloud-config are done." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml352(para) +msgid "" +"The resource OS::Heat::MultipartMime" +" allows multiple OS::Heat::SoftwareConfig" +" and OS::Heat::CloudConfig" +" resources to be combined into a single Cloud-init " +"multi-part message:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/index.xml10(title) +msgid "HOT guide" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_functions.xml4(title) +msgid "HOT functions" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml7(title) +msgid "Link between resources" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml10(para) +#: ./doc/user-guide/hot/section_hot_spec.xml627(title) +msgid "get_param" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml13(para) +#: ./doc/user-guide/hot/section_hot_spec.xml673(title) +msgid "get_resource" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml16(para) +msgid "Ref" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml19(para) +msgid "Fn::GetAtt / get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml25(title) +msgid "String manipulations" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml28(para) +#: ./doc/user-guide/hot/section_hot_spec.xml587(title) +msgid "get_file" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml31(para) +#: ./doc/user-guide/hot/section_hot_spec.xml696(title) +msgid "list_join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml34(para) +#: ./doc/user-guide/hot/section_hot_spec.xml717(title) +msgid "str_replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml37(para) +msgid "Fn::Base64" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml40(para) +msgid "Fn::Join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml43(para) +msgid "Fn::Split" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml46(para) +msgid "Fn::Replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml52(title) +msgid "Lookup structured data" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml55(para) +msgid "Fn::FindInMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml58(para) +msgid "Fn::MemberListToMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml61(para) +msgid "Fn::Select" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml67(title) +msgid "Misc" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml70(para) +msgid "Fn::ResourceFacade / resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml73(para) +msgid "Fn::GetAZs" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hot_spec.xml15(title) +msgid "Heat Orchestration Template (HOT) specification" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml18(title) +msgid "Template structure" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml19(para) +msgid "HOT templates are defined in YAML and use the following structure:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml38(term) +msgid "heat_template_version" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml40(para) +msgid "" +"This key with value 2013-05-23 (or a later date) " +"indicates that the YAML document is a HOT template of the specified version." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml45(term) +#: ./doc/user-guide/hot/section_hot_spec.xml111(term) +#: ./doc/user-guide/hot/section_hot_spec.xml173(term) +#: ./doc/user-guide/hot/section_hot_spec.xml247(term) +#: ./doc/user-guide/hot/section_hot_spec.xml507(term) +msgid "description" +msgstr "description" + +#: ./doc/user-guide/hot/section_hot_spec.xml47(para) +msgid "" +"This optional key gives a description of the template, or the workload that " +"can be deployed using the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml52(term) +msgid "parameter_groups" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml54(para) +msgid "" +"This section specifies how the input parameters should be grouped and the " +"order to provide the parameters in." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml56(para) +#: ./doc/user-guide/hot/section_hot_spec.xml64(para) +#: ./doc/user-guide/hot/section_hot_spec.xml81(para) +#: ./doc/user-guide/hot/section_hot_spec.xml408(para) +#: ./doc/user-guide/hot/section_hot_spec.xml415(para) +msgid "This section is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml60(term) +#: ./doc/user-guide/hot/section_hot_spec.xml117(term) +#: ./doc/user-guide/hot/section_environment.xml17(literal) +msgid "parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml62(para) +msgid "" +"This section specifies input parameters that have to be provided when " +"instantiating the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml68(term) +msgid "resources" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml70(para) +msgid "" +"This section contains the declaration of the resources of the template. This" +" section with at least one resource must be defined in any HOT template, or " +"the template would not really do anything when being instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml77(term) +msgid "outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml79(para) +msgid "" +"This section specifies output parameters available to users once the " +"template has been instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml88(title) +msgid "Parameter groups section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml89(para) +msgid "" +"The parameter_groups section specifies how the input " +"parameters should be grouped and the order to provide the parameters in. " +"These groups are typically used to describe expected behavior for downstream" +" user interfaces." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml92(para) +msgid "" +"These groups are specified in a list with each group containing a list of " +"associated parameters. The lists are used to denote the expected order of " +"the parameters. A parameter can only be included in one group. Use the name " +"of the parameter to add it to a group. The parameters details are defined in" +" the parameters section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml105(term) +#: ./doc/user-guide/hot/section_hot_spec.xml166(term) +msgid "label" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml107(para) +msgid "" +"A human-readable label that defines the associated group of parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml113(para) +msgid "A human-readable description of the parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml119(para) +msgid "A list of parameters that belong with this parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml123(term) +#: ./doc/user-guide/hot/section_hot_spec.xml151(term) +msgid "param name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml125(para) +msgid "" +"The name of a parameter defined in the parameters " +"section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml132(title) +msgid "Parameters section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml133(para) +msgid "" +"The parameters section defines input parameters that have" +" to be provided when instantiating the template. Such parameters are " +"typically used to customize each deployment, or for binding to environment " +"specifics like certain images." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml137(para) +msgid "" +"Each parameter is specified in a separated nested block with the name of the" +" parameter defined in the first line and additional attributes such as a " +"type or a default value defined as nested elements:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml153(para) +msgid "The name of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml157(term) +#: ./doc/user-guide/hot/section_hot_spec.xml397(term) +msgid "type" +msgstr "type" + +#: ./doc/user-guide/hot/section_hot_spec.xml159(para) +msgid "" +"The type of the parameter. Supported types are string, " +"number, comma_delimited_list, " +"json and boolean." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml162(para) +#: ./doc/user-guide/hot/section_hot_spec.xml400(para) +#: ./doc/user-guide/hot/section_hot_spec.xml519(para) +msgid "This attribute is required." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml168(para) +msgid "A human readable name for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml169(para) +#: ./doc/user-guide/hot/section_hot_spec.xml176(para) +#: ./doc/user-guide/hot/section_hot_spec.xml184(para) +#: ./doc/user-guide/hot/section_hot_spec.xml202(para) +#: ./doc/user-guide/hot/section_hot_spec.xml252(para) +#: ./doc/user-guide/hot/section_hot_spec.xml423(para) +#: ./doc/user-guide/hot/section_hot_spec.xml432(para) +#: ./doc/user-guide/hot/section_hot_spec.xml440(para) +#: ./doc/user-guide/hot/section_hot_spec.xml510(para) +msgid "This attribute is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml175(para) +msgid "A human readable description for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml180(term) +msgid "default" +msgstr "default" + +#: ./doc/user-guide/hot/section_hot_spec.xml182(para) +msgid "" +"A default value for the parameter. This value is used if the user doesn't " +"specify his own value during deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml188(term) +msgid "hidden" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml190(para) +msgid "" +"Defines whether the parameters should be hidden when a user requests " +"information about a stack created from the template. This attribute can be " +"used to hide passwords specified as parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml193(para) +msgid "This attribute is optional and defaults to false." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml197(term) +msgid "constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml199(para) +msgid "" +"A list of constraints to apply. The constraints are validated by the " +"Orchestration engine when a user deploys a stack. The stack creation fails " +"if the parameter value doesn't comply to the constraints." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml206(para) +msgid "" +"The following example shows a minimalistic definition of two parameters:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml217(para) +msgid "" +"The description and the label are optional, but defining these attributes is" +" good practice to provide useful information about the role of the parameter" +" to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml222(title) +msgid "Parameter constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml223(para) +msgid "" +"The constraints block of a parameter definition defines " +"additional validation constraints that apply to the value of the parameter. " +"The parameter values provided by a user are validated against the " +"contrainsts at instantiation time. The contrainsts are defined as a list " +"with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml233(term) +msgid "constraint type" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml235(para) +msgid "" +"Type of constraint to apply. The set of currently supported constraints is " +"given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml240(term) +msgid "constraint definition" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml242(para) +msgid "" +"The actual constraint, depending on the constraint type. The concrete syntax" +" for each constraint type is given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml249(para) +msgid "" +"A description of the constraint. The text is presented to the user when the " +"value he defines violates the constraint. If ommitted, a default validation " +"message is presented to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml256(para) +msgid "" +"The following example shows the definition of a string parameter with two " +"constraints. Note that while the descriptions for each constraint are " +"optional, it is good practice to provide concrete descriptions to present " +"useful messages to the user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml271(para) +msgid "" +"While the descriptions for each constraint are optional, it is good practice" +" to provide concrete descriptions so useful messages can be presented to the" +" user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml275(para) +msgid "" +"The following sections list the supported types of parameter constraints, " +"along with the syntax for each type." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml278(title) +msgid "length" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml279(para) +msgid "" +"The length constraint applies to parameters of type " +"string. It defines a lower and upper limit for the length" +" of the string value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml281(para) +msgid "The syntax of the length constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml283(para) +msgid "" +"It is possible to define a length constraint with only a lower limit or an " +"upper limit. However, at least one of min or " +"max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml287(title) +msgid "range" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml288(para) +msgid "" +"The range constraint applies to parameters of type " +"number. It defines a lower and upper limit for the " +"numeric value of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml290(para) +msgid "The syntax of the range constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml292(para) +msgid "" +"It is possible to define a range constraint with only a lower limit or an " +"upper limit. However, at least one of min or " +"max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml294(para) +msgid "" +"The minimum and maximum boundaries are included in the range. For example, " +"the following range constraint would allow for all numeric values between 0 " +"and 10:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml299(title) +msgid "allowed_values" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml300(para) +msgid "" +"The allowed_values constraint applies to parameters of " +"type string or number. It specifies a " +"set of possible values for a parameter. At deployment time, the user-" +"provided value for the respective parameter must match one of the elements " +"of the list." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml304(para) +msgid "The syntax of the allowed_values constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml306(para) +msgid "Alternatively, the following YAML list notation can be used:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml324(title) +msgid "allowed_pattern" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml325(para) +msgid "" +"The allowed_pattern constraint applies to parameters of " +"type string. It specifies a regular expression against " +"which a user-provided parameter value must evaluate at deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml328(para) +msgid "The syntax of the allowed_pattern constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml341(title) +msgid "custom_constraint" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml342(para) +msgid "" +"The custom_constraint constraint adds an extra step of " +"validation, generally to check that the specified resource exists in the " +"backend. Custom constraints get implemented by plug-ins and can provide any " +"kind of advanced constraint validation logic." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml346(para) +msgid "The syntax of the custom_constraint constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml348(para) +msgid "" +"The name attribute specifies the concrete type of custom " +"constraint. It corresponds to the name under which the respective validation" +" plugin has been registered in the Orchestration engine." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml361(title) +msgid "Pseudo Parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml362(para) +msgid "" +"In addition to parameters defined by a template author, the Orchestration " +"module also creates two parameters for every stack that allow referential " +"access to the stack's name and identifier. These parameters are named " +"OS::stack_name for the stack name and " +"OS::stack_id for the stack identifier. These values are " +"accessible via the get_param intrinsic function, just " +"like user-defined parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml372(title) +msgid "Resources section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml373(para) +msgid "" +"The resources section defines actual resources that make " +"up a stack deployed from the HOT template (for instance compute instances, " +"networks, storage volumes)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml376(para) +msgid "" +"Each resource is defined as a separate block in the " +"resources section with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml390(term) +#: ./doc/user-guide/hot/section_hot_spec.xml551(term) +msgid "resource ID" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml392(para) +msgid "" +"A resource ID which must be unique within the resources " +"section of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml399(para) +msgid "" +"The resource type, such as OS::Nova::Server or " +"OS::Neutron::Port." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml404(term) +msgid "properties" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml406(para) +msgid "" +"A list of resource-specific properties. The property value can be provided " +"in place, or via a function (see Intrinsic functions)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml412(term) +msgid "metadata" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml414(para) +msgid "Resource-specific metadata." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml419(term) +msgid "depends_on" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml421(para) +msgid "Dependencies of the resource on one or more resources of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml422(para) +msgid "" +"See Resource " +"dependencies for details." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml427(term) +msgid "update_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml429(para) +msgid "" +"Update policy for the resource, in the form of a nested dictionary. Whether " +"update policies are supported and what the exact semantics are depends on " +"the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml436(term) +msgid "deletion_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml438(para) +msgid "" +"Deletion policy for the resource. Which type of deletion policy is supported" +" depends on the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml444(para) +msgid "" +"Depending on the type of resource, the resource block might include more " +"resource specific data." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml446(para) +msgid "" +"All resource types that can be used in CFN templates can also be used in HOT" +" templates, adapted to the YAML structure as outlined above." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml448(para) +msgid "" +"The following example demonstrates the definition of a simple compute " +"resource with some fixed property values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml457(title) +msgid "Resource dependencies" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml458(para) +msgid "" +"The depends_on attribute of a resource defines a " +"dependency between this resource and one or more other resources." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml460(para) +msgid "" +"If a resource depends on just one other resource, the ID of the other " +"resource is specified as string of the depends_on " +"attribute, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml470(para) +msgid "" +"If a resource depends on more than one other resources, the value of the " +"depends_on attribute is specified as a list of resource " +"IDs, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml487(title) +msgid "Outputs section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml488(para) +msgid "" +"The outputs section defines output parameters that should" +" be available to the user once a stack has been created. This would be, for " +"example, parameters such as IP addresses of deployed instances, or URLs of " +"web applications deployed as part of a stack." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml492(para) +msgid "" +"Each output parameter is defined as a separate block within the outputs " +"section according to the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml500(term) +#: ./doc/user-guide/hot/section_hot_spec.xml638(term) +msgid "parameter name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml502(para) +msgid "" +"The output parameter name, which must be unique within the " +"outputs section of a template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml509(para) +msgid "A short description of the output parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml514(term) +msgid "parameter value" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml516(para) +msgid "" +"The value of the output parameter. This value is usually resolved by means " +"of a function. See Intrinsic functions for details " +"about the functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml523(para) +msgid "" +"The example below shows how the IP address of a compute resource can be " +"defined as an output parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml532(title) +msgid "Intrinsic functions" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml533(para) +msgid "" +"HOT provides a set of intrinsic functions that can be used inside templates " +"to perform specific tasks, such as getting the value of a resource attribute" +" at runtime. The following section describes the role and syntax of the " +"intrinsic functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml538(title) +msgid "get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml539(para) +msgid "" +"The get_attr function references an attribute of a " +"resource. The attribute value is resolved at runtime using the resource " +"instance created from the respective resource definition." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml542(para) +msgid "The syntax of the get_attr function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml553(para) +msgid "The resource ID for which the attribute needs to be resolved." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml554(para) +msgid "" +"The resource ID must exist in the resources section of " +"the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml558(term) +msgid "attribute name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml560(para) +msgid "" +"The attribute name to be resolved. If the attribute returns a complex data " +"structure such as a list or a map, then subsequent keys or indexes can be " +"specified. These additional parameters are used to navigate the data " +"structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml567(para) +msgid "" +"The following example demonstrates how to use the " +"get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml580(para) +msgid "" +"In this example, if the networks attribute contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml583(para) +msgid "" +"then the value of the get_attr function would resolve to " +"10.0.0.1 (first item of the private " +"entry in the networks map)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml588(para) +msgid "" +"The get_file function returns the content of a file into " +"the template. It is generally used as a file inclusion mechanism for files " +"containing scripts or configuration files." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml591(para) +msgid "The syntax of the get_file function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml593(para) +msgid "" +"The content key is used to look up the " +"files dictionary that is provided in the REST API call. " +"The Orchestration client command () is " +"get_file aware and will populate the " +"files dictionnary with the actual content of fetched " +"paths and URLs. The Orchestration client command supports relative paths and" +" will transform these to the absolute URLs required by the Orcestration API." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml600(para) +msgid "" +"The get_file argument must be a static path or URL and " +"not rely on intrinsic functions like get_param. the " +"Orchestration client does not process intrinsic functions (they are only " +"processed by the Orchestration engine)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml605(para) +msgid "" +"The example below demonstrates the get_file function " +"usage with both relative and absolute URLs:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml621(para) +msgid "" +"The files dictionary generated by the Orchestration " +"client during instantiation of the stack would contain the following keys: *" +" file:///path/to/my_instance_user_data.sh * " +"http://example.com/my_other_instance_user_data.sh*" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml628(para) +msgid "" +"The get_param function references an input parameter of a" +" template. It resolves to the value provided for this input parameter at " +"runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml630(para) +msgid "The syntax of the get_param function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml640(para) +msgid "" +"The parameter name to be resolved. If the parameters returns a complex data " +"structure such as a list or a map, then subsequent keys or indexes can be " +"specified. These additional parameters are used to navigate the data " +"structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml647(para) +msgid "" +"The following example demonstrates the use of the " +"get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml663(para) +msgid "" +"In this example, if the instance_type and " +"server_data parameters contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml668(para) +msgid "" +"then the value of the property flavor would resolve to " +"m1.tiny, metadata would resolve to " +"{\"foo\": \"bar\"} and key_name would " +"resolve to a_key." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml674(para) +msgid "" +"The get_resource function references another resource " +"within the same template. At runtime, it is resolved to reference the ID of " +"the referenced resource, which is resource type specific. For example, a " +"reference to a floating IP resource returns the respective IP address at " +"runtime. The syntax of the get_resource function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml680(para) +msgid "" +"The resource ID of the referenced resource is given as single parameter to " +"the get_resource function." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml682(para) +msgid "For exemple:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml697(para) +msgid "" +"The list_join function joins a list of strings with the " +"given delimiter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml698(para) +msgid "The syntax of the list_join function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml704(para) +msgid "This resolve to the string one, two, and three." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml707(title) +msgid "resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml708(para) +msgid "" +"The resource_facade function retrieves data in a parent " +"provider template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml709(para) +msgid "" +"A provider template provdes a custom definition of a resource, called its " +"facade. For more information about custom templates, see . The syntax of the " +"resource_facade function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml713(para) +msgid "" +"data type can be one of metadata, " +"deletion_policy or update_policy." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml718(para) +msgid "" +"The str_replace function dynamically constructs strings " +"by providing a template string with placeholders and a list of mappings to " +"assign values to those placeholders at runtime. The placeholders are " +"replaced with mapping values wherever a mapping key exactly matches a " +"placeholder." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml722(para) +msgid "The syntax of the str_replace function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml728(term) +msgid "template" +msgstr "テンプレート" + +#: ./doc/user-guide/hot/section_hot_spec.xml730(para) +msgid "" +"Defines the template string that contains placeholders which will be " +"substituted at runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml735(term) +msgid "params" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml737(para) +msgid "" +"Provides parameter mappings in the form of dictionary. Each key refers to a " +"placeholder used in the template attribute." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml742(para) +msgid "" +"The following example shows a simple use of the " +"str_replace function in the outputs section of a template" +" to build a URL for logging into a deployed application:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml758(para) +msgid "" +"The following examples show the use of the str_replace " +"function to build an instance initialization script:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hello_world.xml15(title) +msgid "Writing a hello world HOT template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml16(para) +msgid "" +"HOT is a new template format meant to replace the CloudFormation-compatible " +"format (CFN) as the native format supported by the Orchestration module over" +" time. This guide is targeted towards template authors and explains how to " +"write HOT templates based on examples. A detailed specification of HOT can " +"be found at ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml22(para) +msgid "" +"This section gives an introduction on how to write HOT templates, starting " +"from very basic steps and then going into more and more detail by means of " +"examples." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml26(title) +msgid "A most basic template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml27(para) +msgid "" +"The most basic template you can think of contains only a single resource " +"definition using only predefined properties. For example, the template below" +" could be used to deploy a single compute instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml41(para) +msgid "" +"Each HOT template has to include the " +"heat_template_version key with value " +"2013-05-23, the current HOT version. While the " +"description key is optional, it is good practice to " +"include some useful text that describes what users can do with the template." +" In case you want to provide a longer description that does not fit on a " +"single line, you can provide multi-line text in YAML, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml50(para) +msgid "" +"The resources section is required and must contain at " +"least one resource definition. In the above example, a compute instance is " +"defined with fixed values for the key_name, " +"image and flavor properties." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml54(para) +msgid "" +"All the defined elements (key pair, image, flavor) have to exist in the " +"OpenStack environment where the template is used." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml60(title) +msgid "Input parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml61(para) +msgid "" +"Input parameters defined in the parameters section of a " +"template allow users to customize a template during deployment. For example," +" this allows for providing custom key pair names or image IDs to be used for" +" a deployment. From a template author's perspective, this helps to make a " +"template more easily reusable by avoiding hardcoded assumptions." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml66(para) +msgid "" +"The following example extends the previous template to provide parameters " +"for the key pair, image and flavor properties of the resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml93(para) +msgid "" +"Values for the three parameters must be defined by the template user during " +"the deployment of a stack. The get_param intrinsic " +"function retrieves a user-specified value for a given parameter and uses " +"this value for the associated resource property." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml97(para) +msgid "" +"For more information about intrinsic functions, see ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml100(title) +msgid "Providing default values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml101(para) +msgid "" +"You can provide default values for parameters. If a user doesn't define a " +"value for a parameter, the default value is used during the stack " +"deployment. The following example defines a default value " +"m1.small for the flavor property:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml112(para) +msgid "" +"If a template doesn't define a default value for a parameter, then the user " +"must define the value, otherwise the stack creation will fail." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml117(title) +msgid "Hidding parameters values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml118(para) +msgid "" +"The values that a user provides when deploying a stack are available in the " +"stack details and can be accessed by any user in the same tenant. To hide " +"the value of a parameter, use the hidden boolean " +"attribute of the parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml129(title) +msgid "Restricting user input" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml130(para) +msgid "" +"You can restrict the values of an input parameter to make sure that the user" +" defines valid data for this parameter. The constraints " +"property of an input parameter defines a list of constraints to apply for " +"the parameter. The following example restricts the flavor" +" parameter to a list of three possible values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml143(para) +msgid "" +"The following example defines multiple contraints for a password definition:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml157(para) +msgid "" +"The list of supported constraints is available in the section." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml160(para) +msgid "" +"You can define multiple constraints of the same type. Especially in the case" +" of allowed patterns this not only allows for keeping regular expressions " +"simple and maintainable, but also for keeping error messages to be presented" +" to users precise." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml169(title) +msgid "Template outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml170(para) +msgid "" +"In addition to template customization through input parameters, you can " +"provide information about the resources created during the stack deployment " +"to the users in the outputs section of a template. In the" +" following example the output section provides the IP address of the " +"my_instance resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml179(para) +msgid "" +"Output values are typically resolved using intrinsic function such as the " +"get_attr. See for more information about intrinsic functions.." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml183(para) +msgid "" +"See for more information about the " +"outputs section." +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_basic_resources.xml4(title) +msgid "Instances" +msgstr "インスタンス" + +#: ./doc/user-guide/hot/section_basic_resources.xml11(title) +msgid "Manage instances" +msgstr "インスタンスの管理" + +#: ./doc/user-guide/hot/section_basic_resources.xml13(title) +msgid "Create an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml14(para) +msgid "" +"Use the OS::Nova::Server " +"resource to create a Compute instance. The flavor " +"property is the only mandatory one, but you need to define a boot source " +"using one of the image or " +"block_device_mapping properties." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml17(para) +msgid "" +"You also need to define the networks property to indicate" +" to which networks your instance must connect if multiple networks are " +"available in your tenant." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml19(para) +msgid "" +"The following example creates a simple instance, booted from an image, and " +"connecting to the private network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml31(title) +msgid "Connect an instance to a network" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml32(para) +msgid "" +"Use the networks property of an OS::Nova::Server " +"resource to define which networks an instance should connect to. Define each" +" network as a YAML map, containing one of the following keys:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml38(literal) +msgid "port" +msgstr "ポート" + +#: ./doc/user-guide/hot/section_basic_resources.xml41(para) +msgid "" +"The ID of an existing Networking port. You usually create this port in the " +"same template using an OS::Neutron::Port" +" resource. You will be able to associate a floating IP to this port, and the" +" port to your Compute instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml49(literal) +msgid "network" +msgstr "Network" + +#: ./doc/user-guide/hot/section_basic_resources.xml52(para) +msgid "" +"The name or ID of an existing network. You don't need to create an " +"OS::Neutron::Port" +" resource if you use this property, but you will not be able to associate a " +"floating IP with the instance interface in the template." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml59(para) +msgid "" +"The following example demonstrates the use of the port " +"and network properties:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml86(title) +msgid "Create and associate security groups to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml87(para) +msgid "" +"Use the OS::Neutron::SecurityGroup" +" resource to create security groups." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml89(para) +msgid "" +"Define the security_groups property of the OS::Neutron::Port" +" resource to associate security groups to a port, then associate the port to" +" an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml92(para) +msgid "" +"The following example creates a security group allowing inbound connections " +"on ports 80 and 443 (web server) and associates this security group to an " +"instance port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml128(title) +msgid "Create and associate a floating IP to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml129(para) +msgid "" +"You can use two sets of resources to create and associate floating IPs to " +"instances." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml132(title) +msgid "OS::Nova resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml133(para) +msgid "" +"Use the OS::Nova::FloatingIP" +" resource to create a floating IP, and the OS::Nova::FloatingIPAssociation" +" resource to associate the floating IP to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml136(para) +msgid "" +"The following example creates an instance and a floating IP, and associate " +"the floating IP to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml159(title) +msgid "OS::Neutron resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml161(para) +msgid "" +"The Networking service (neutron) must be enabled on your OpenStack " +"deployment to use these resources." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml164(para) +msgid "" +"Use the OS::Neutron::FloatingIP" +" resource to create a floating IP, and the OS::Neutron::FloatingIPAssociation" +" resource to associate the floating IP to a port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml189(title) +msgid "Enable remote access to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml190(para) +msgid "" +"The key_name attribute of the OS::Nova::Server " +"resource defines the key pair to use to enable SSH remote access:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml200(para) +msgid "" +"For more information about key pairs, see the Configure access and security " +"for instances section of the OpenStack user guide." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml205(title) +msgid "Create a key pair" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml206(para) +msgid "" +"You can create new key pairs with the OS::Nova::KeyPair" +" resource. Key pairs can be imported or created during the stack creation." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml208(para) +msgid "" +"If the public_key property is not specified, the " +"Orchestration module creates a new key pair. If the " +"save_private_key property is set to " +"true, the private_key attribute of the" +" resource holds the private key." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml211(para) +msgid "" +"The following example creates a new key pair and uses it as authentication " +"key for an instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml234(title) +msgid "Manage networks" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml236(title) +msgid "Create a network and a subnet" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml238(para) +msgid "" +"The Networking service (neutron) must be enabled on your OpenStack " +"deployment to create and manage networks and subnets. Networks and subnets " +"cannot be created if your deployment uses legacy networking (nova-network)." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml242(para) +msgid "" +"Use the OS::Neutron::Net " +"resource to create a network, and the OS::Neutron::Subnet" +" resource to provide a subnet for this network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml257(title) +msgid "Create and manage a router" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml258(para) +msgid "" +"Use the OS::Neutron::Router" +" resource to create a router. You can define its gateway with the " +"external_gateway_info property:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml265(para) +msgid "" +"You can connect subnets to routers with the OS::Neutron::RouterInterface" +" resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml275(title) +msgid "Complete network example" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml276(para) +msgid "The following example creates a network stack:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml279(para) +msgid "A network and an associated subnet." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml282(para) +msgid "A router with an external gateway." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml285(para) +msgid "An interface to the new subnet for the new router." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml288(para) +msgid "" +"In this example, the public network is an existing shared" +" network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml315(title) +msgid "Manage volumes" +msgstr "ボリュームの管理" + +#: ./doc/user-guide/hot/section_basic_resources.xml318(para) +msgid "" +"Use the OS::Cinder::Volume" +" resource to create a new Block Storage volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml326(para) +msgid "" +"The volumes that you create are empty by default. Use the " +"image property to create a bootable volume from an " +"existing image:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml334(para) +msgid "" +"You can also create new volumes from another volume, a volume snapshot, or a" +" volume backup. Use the source_volid, " +"snapshot_id or backup_id properties to" +" create a new volume from an existing source." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml337(para) +msgid "For example, to create a new volume from a backup:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml343(para) +msgid "" +"In this example the size property is not defined because " +"the Block Storage service uses the size of the backup to define the size of " +"the new volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml348(para) +msgid "" +"Use the OS::Cinder::VolumeAttachment" +" resource to attach a volume to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml350(para) +msgid "" +"The following example creates a volume and an instance, and attaches the " +"volume to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml371(title) +msgid "Boot an instance from a volume" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml372(para) +msgid "" +"Use the block_device_mapping property of the " +"OS::Nova::Server " +"resource to define a volume used to boot the instance. This property is a " +"list of volumes to attach to the instance before its boot." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml375(para) +msgid "" +"The following example creates a bootable volume from an image, and uses it " +"to boot an instance:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_composition.xml4(title) +msgid "Template composition" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml5(para) +msgid "" +"When writing complex templates you are encouraged to break up your template " +"into separate smaller templates. These can then be brought together using " +"template resources. This is a mechanism to define a resource using a " +"template, thus composing one logical stack with multiple templates." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml9(para) +msgid "" +"Template resources provide a feature similar to the AWS::CloudFormation::Stack" +" resource, but also provide a way to:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml13(para) +msgid "Define new resource types and build your own resource library." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml16(para) +msgid "Override the default behaviour of existing resource types." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml19(para) +msgid "To achieve this:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml22(para) +msgid "" +"The Orchestration client gets the associated template files and passes them " +"along in the files section of the POST " +"stacks/ API request." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml26(para) +msgid "" +"The environment in the Orchestration engine manages the mapping of resource " +"type to template creation." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml30(para) +msgid "" +"The Orchestration engine translates template parameters into resource " +"properties." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml34(para) +msgid "" +"The following examples illustrate how you can use a custom template to " +"define new types of resources. These examples use a custom template stored " +"in a my_nova.yml file:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml53(title) +msgid "Use the template filename as type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml54(para) +msgid "" +"The following template defines the my_nova.yaml file as " +"value for the type property of a resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml62(para) +msgid "" +"The key_name argument of the " +"my_nova.yaml template gets its value from the " +"key_name property of the new template." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml65(para) +msgid "" +"The above reference to my_nova.yaml assumes it is in the " +"same directory. You can use any of the following forms:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml69(para) +msgid "Relative path (my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml72(para) +msgid "" +"Absolute path (file:///home/user/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml75(para) +msgid "" +"Http URL (http://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml78(para) +msgid "" +"Https URL (https://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml82(para) +#: ./doc/user-guide/hot/section_composition.xml105(para) +msgid "To create the stack run:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml87(title) +msgid "Define a new resource type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml88(para) +msgid "" +"You can associate a name to the my_noya.yaml template in " +"an environment file. If the name is already known by the Orchestration " +"module then your new resource will override the default one." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml91(para) +msgid "" +"In the following example a new OS::Nova::Server resource " +"overrides the default resource of the same name." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml93(para) +msgid "" +"An env.yaml environment file holds the definition of the " +"new resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml97(para) +msgid "" +"See for more detail about environment " +"files." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml99(para) +msgid "" +"You can now use the new OS::Nova::Server in your new " +"template:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_advanced_topics.xml4(title) +msgid "Advanced topics" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml9(title) +msgid "Load balancer" +msgstr "負荷分散装置" + +#: ./doc/user-guide/hot/section_advanced_topics.xml10(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml14(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml18(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml26(para) +#: ./doc/user-guide/hot/section_advanced_topics.xml30(para) +msgid "TODO" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml13(title) +msgid "Firewall" +msgstr "ファイアウォール" + +#: ./doc/user-guide/hot/section_advanced_topics.xml17(title) +msgid "VPN" +msgstr "VPN" + +#: ./doc/user-guide/hot/section_advanced_topics.xml23(title) +msgid "Auto scaling" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml25(title) +msgid "Alarming" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml29(title) +msgid "Up scaling and down scaling" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_environment.xml4(title) +msgid "Environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml5(para) +msgid "" +"The environment affects the runtime behaviour of a template. It provides a " +"way to override the resource implementations and a mechanism to place " +"parameters that the service needs." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml8(para) +msgid "" +"To fully understand the runtime behavior you have to consider what plug-ins " +"are installed on the cloud you're using." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml12(title) +msgid "Environment file format" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml13(para) +msgid "The environment is a yaml text file that contains two main sections:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml20(para) +msgid "A map of key/pair values." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml25(literal) +msgid "resource_registry" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml28(para) +msgid "Definition of custom resources." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml32(para) +msgid "" +"Use the -e option of the command to create a stack using " +"with the environment defined in such a file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml34(para) +msgid "" +"You can also provide environment parameters as a list of key/value pairs " +"using the -P option of the command." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml36(para) +msgid "" +"In the following example the environment is read from the " +"my_env.yaml file and an extra parameter is provided using" +" the -P option:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml42(title) +msgid "Global and effective environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml43(para) +msgid "" +"The environment used for a stack is the combination of the environment you " +"use with the template for the stack, and a global environment that is " +"determined by your cloud operator. An entry in the user environment takes " +"precedence over the global environment. OpenStack includes a default global " +"environment, but you cloud operator can add additional environment entries." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml69(title) +msgid "Define values for a template arguments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml70(para) +msgid "" +"You can define values for the template arguments in the " +"parameters section of an environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml79(title) +msgid "Create and override resources" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml80(para) +msgid "" +"You can create or override resources in the " +"resource_registry section of an environment file. The " +"resource you provide in this manner must have an identifier, and references " +"either other resources IDs or the URL of an existing template file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml84(para) +msgid "" +"The following example maps the new " +"OS::Networking::FloatingIP resource to the existing " +"OS::Nova::FloatingIP" +" resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml88(para) +msgid "You can use wilcards to map multiple resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml91(para) +msgid "" +"To create or override a resource with a custom resource, create a template " +"file to define this resource, and provide the URL to the template file in " +"the environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml96(para) +msgid "" +"The supported URL scheme are file, " +"http and https." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml98(para) +msgid "" +"The template file extension must be .yaml or " +".template, or it will not be treated as a custom template" +" resource." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml101(para) +msgid "" +"You can limit the usage of a custom resource to a specific resource of the " +"template:" +msgstr "" + #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./doc/user-guide/section_sdk_configure_instances.xml0(None) +#: ./doc/user-guide/hot/section_environment.xml0(None) msgid "translator-credits" msgstr "Tomoyuki KATO , 2013-2014\nmyamamot , 2014\nykatabam , 2014" diff --git a/doc/user-guide/locale/user-guide.pot b/doc/user-guide/locale/user-guide.pot index fac3f6f1e5..8b82aeda22 100644 --- a/doc/user-guide/locale/user-guide.pot +++ b/doc/user-guide/locale/user-guide.pot @@ -1,7 +1,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2014-11-03 06:11+0000\n" +"POT-Creation-Date: 2014-11-12 06:12+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1121,7 +1121,7 @@ msgstr "" msgid "If you have not created any security groups, you can assign only the default security group to the instance." msgstr "" -#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:179(guilabel) ./doc/user-guide/section_sdk_neutron.xml:7(title) +#: ./doc/user-guide/section_dashboard_launch_instances_from_image.xml:179(guilabel) ./doc/user-guide/section_sdk_neutron.xml:7(title) ./doc/user-guide/hot/section_advanced_topics.xml:7(title) msgid "Networking" msgstr "" @@ -2549,7 +2549,7 @@ msgstr "" msgid "FLOATING_IP_ADDRESS" msgstr "" -#: ./doc/user-guide/section_cli_nova_floating_ips.xml:102(para) +#: ./doc/user-guide/section_cli_nova_floating_ips.xml:102(para) ./doc/user-guide/hot/section_hot_spec.xml:311(para) ./doc/user-guide/hot/section_hot_spec.xml:330(para) ./doc/user-guide/hot/section_hot_spec.xml:351(para) ./doc/user-guide/hot/section_hot_spec.xml:702(para) ./doc/user-guide/hot/section_basic_resources.xml:320(para) msgid "For example:" msgstr "" @@ -5001,7 +5001,7 @@ msgstr "" msgid "Volumes are block storage devices that you attach to instances to enable persistent storage. You can attach a volume to a running instance or detach a volume and attach it to another instance at any time. You can also create a snapshot from or delete a volume. Only administrative users can create volume types." msgstr "" -#: ./doc/user-guide/section_dashboard_manage_volumes.xml:16(title) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:16(title) ./doc/user-guide/hot/section_basic_resources.xml:317(title) msgid "Create a volume" msgstr "" @@ -5101,7 +5101,7 @@ msgstr "" msgid "The dashboard shows the volume on the Volumes tab." msgstr "" -#: ./doc/user-guide/section_dashboard_manage_volumes.xml:132(title) +#: ./doc/user-guide/section_dashboard_manage_volumes.xml:132(title) ./doc/user-guide/hot/section_basic_resources.xml:347(title) msgid "Attach a volume to an instance" msgstr "" @@ -5281,8 +5281,1453 @@ msgstr "" msgid "To add a rule, to a security group, call the novaclient.v1_1.security_group_rules.SecurityGroupRuleManager.create method:" msgstr "" +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_software_deployment.xml:4(title) +msgid "Software configuration" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:5(para) +msgid "There are a variety of options to configure the software which runs on the servers in your stack. These can be broadly divided into the following:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:9(para) +msgid "Custom image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:12(para) ./doc/user-guide/hot/section_software_deployment.xml:59(title) +msgid "User-data boot scripts and cloud-init" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:15(para) +msgid "Software deployment resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:18(para) +msgid "This section will describe each of these options and provide examples for using them together in your stacks." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:22(title) +msgid "Image building" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:23(para) +msgid "The first opportunity to influence what software is configured on your servers is by booting them with a custom-built image. There are a number of reasons you might want to do this, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:28(para) +msgid " - since the required software is already on the image there is no need to download and install anything at boot time." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:32(para) +msgid " - software downloads can fail for a number of reasons including transient network failures and inconsistent software repositories." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:36(para) +msgid " - custom built images can be verified in test environments before being promoted to production." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:40(para) +msgid " - post-boot configuration may depend on agents already being installed and enabled" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:44(para) +msgid "A number of tools are available for building custom images, including:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:47(para) +msgid "diskimage-builder image building tools for OpenStack" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:50(para) +msgid "imagefactory builds images for a variety of operating system/cloud combinations" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:54(para) +msgid "Examples in this guide which require custom images will use diskimage-builder." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:60(para) +msgid "When booting a server it is possible to specify the contents of the user-data to be passed to that server. This user-data is made available either from configured config-drive or from the Metadata service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:63(para) +msgid "How this user-data is consumed depends on the image being booted, but the most commonly used tool for default cloud images is Cloud-init." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:65(para) +msgid "Whether the image is using Cloud-init or not, it should be possible to specify a shell script in the user_data property and have it be executed by the server during boot:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:80(para) +msgid ": debugging these scripts it is often useful to view the boot log using nova console-log <server-id> to view the progress of boot script execution." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:84(para) +msgid "Often there is a need to set variable values based on parameters or resources in the stack. This can be done with the str_replace intrinsic function:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:106(para) +msgid ": If a stack-update is performed and there are any changes at all to the content of user_data then the server will be replaced (deleted and recreated) so that the modified boot configuration can be run on a new server." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:111(para) +msgid "When these scripts grow it can become difficult to maintain them inside the template, so the get_file intrinsic function can be used to maintain the script in a separate file:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:131(para) +msgid ": str_replace can replace any strings, not just strings starting with $. However doing this for the above example is useful because the script file can be executed for testing by passing in environment variables." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:137(title) +msgid "Choosing the user_data_format" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:138(para) +msgid "The OS::Nova::Server user_data_format property determines how the user_data should be formatted for the server. For the default value HEAT_CFNTOOLS, the user_data is bundled as part of the heat-cfntools cloud-init boot configuration data. While HEAT_CFNTOOLS is the default for user_data_format, it is considered legacy and RAW or SOFTWARE_CONFIG will generally be more appropriate." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:144(para) +msgid "For RAW the user_data is passed to Nova unmodified. For a Cloud-init enabled image, the following are both valid RAW user-data:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:166(para) +msgid "For SOFTWARE_CONFIG user_data is bundled as part of the software config data, and metadata is derived from any associated software deployment resources." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:171(title) +msgid "Signals and wait conditions" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:172(para) +msgid "Often it is necessary to pause further creation of stack resources until the boot configuration script has notified that it has reached a certain state. This is usually either to notify that a service is now active, or to pass out some generated data which is needed by another resource. The resources OS::Heat::WaitCondition and OS::Heat::SwiftSignal both perform this function using different techniques and tradeoffs." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:178(para) +msgid "OS::Heat::WaitCondition is implemented as a call to the Orchestration API resource signal. The token is created using credentials for a user account which is scoped only to the wait condition handle resource. This user is created when the handle is created, and is associated to a project which belongs to the stack, in an identity domain which is dedicated to the orchestration service." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:184(para) ./doc/user-guide/hot/section_software_deployment.xml:267(para) +msgid "Sending the signal is a simple HTTP request, as with this example using curl:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:188(para) +msgid "The JSON containing the signal data is expected to be of the following format:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:195(para) +msgid "All of these values are optional, and if not specified will be set to the following defaults:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:203(para) +msgid "If status is set to FAILURE then the resource (and the stack) will go into a FAILED state using the reason as failure reason." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:205(para) +msgid "The following template example uses the convenience attribute curl_cli which builds a curl command with a valid token:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:263(para) +msgid "OS::Heat::SwiftSignal is implemented by creating an Object Storage API temporary URL which is populated with signal data with an HTTP PUT. The orchestration service will poll this object until the signal data is available. Object versioning is used to store multiple signals." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:269(para) +msgid "The above template example only needs to have the type changed to the swift signal resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:281(para) +msgid "The decision to use OS::Heat::WaitCondition or OS::Heat::SwiftSignal will depend on a few factors:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:285(para) +msgid "OS::Heat::SwiftSignal depends on the availability of an Object Storage API" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:289(para) +msgid "OS::Heat::WaitCondition depends on whether the orchestration service has been configured with a dedicated stack domain (which may depend on the availability of an Identity V3 API)." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:294(para) +msgid "The preference to protect signal URLs with token authentication or a secret webhook URL." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:300(title) +msgid "Software config resources" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:301(para) +msgid "Boot configuration scripts can also be managed as their own resources. This allows configuration to be defined once and run on multiple server resources. These software-config resources are stored and retrieved via dedicated calls to the Orchestration API. It is not possible to modify the contents of an existing software-config resource, so a stack-update which changes any existing software-config resource will result in API calls to create a new config and delete the old one." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:308(para) +msgid "The resource OS::Heat::SoftwareConfig is used for storing configs represented by text scripts, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:326(para) +msgid "The resource OS::Heat::CloudConfig allows Cloud-init cloud-config to be represented as template YAML rather than a block string. This allows intrinsic functions to be included when building the cloud-config. This also ensures that the cloud-config is valid YAML, although no further checks for valid cloud-config are done." +msgstr "" + +#: ./doc/user-guide/hot/section_software_deployment.xml:352(para) +msgid "The resource OS::Heat::MultipartMime allows multiple OS::Heat::SoftwareConfig and OS::Heat::CloudConfig resources to be combined into a single Cloud-init multi-part message:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/index.xml:10(title) +msgid "HOT guide" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_functions.xml:4(title) +msgid "HOT functions" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:7(title) +msgid "Link between resources" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:10(para) ./doc/user-guide/hot/section_hot_spec.xml:627(title) +msgid "get_param" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:13(para) ./doc/user-guide/hot/section_hot_spec.xml:673(title) +msgid "get_resource" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:16(para) +msgid "Ref" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:19(para) +msgid "Fn::GetAtt / get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:25(title) +msgid "String manipulations" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:28(para) ./doc/user-guide/hot/section_hot_spec.xml:587(title) +msgid "get_file" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:31(para) ./doc/user-guide/hot/section_hot_spec.xml:696(title) +msgid "list_join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:34(para) ./doc/user-guide/hot/section_hot_spec.xml:717(title) +msgid "str_replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:37(para) +msgid "Fn::Base64" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:40(para) +msgid "Fn::Join" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:43(para) +msgid "Fn::Split" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:46(para) +msgid "Fn::Replace" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:52(title) +msgid "Lookup structured data" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:55(para) +msgid "Fn::FindInMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:58(para) +msgid "Fn::MemberListToMap" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:61(para) +msgid "Fn::Select" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:67(title) +msgid "Misc" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:70(para) +msgid "Fn::ResourceFacade / resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_functions.xml:73(para) +msgid "Fn::GetAZs" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hot_spec.xml:15(title) +msgid "Heat Orchestration Template (HOT) specification" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:18(title) +msgid "Template structure" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:19(para) +msgid "HOT templates are defined in YAML and use the following structure:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:38(term) +msgid "heat_template_version" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:40(para) +msgid "This key with value 2013-05-23 (or a later date) indicates that the YAML document is a HOT template of the specified version." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:45(term) ./doc/user-guide/hot/section_hot_spec.xml:111(term) ./doc/user-guide/hot/section_hot_spec.xml:173(term) ./doc/user-guide/hot/section_hot_spec.xml:247(term) ./doc/user-guide/hot/section_hot_spec.xml:507(term) +msgid "description" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:47(para) +msgid "This optional key gives a description of the template, or the workload that can be deployed using the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:52(term) +msgid "parameter_groups" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:54(para) +msgid "This section specifies how the input parameters should be grouped and the order to provide the parameters in." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:56(para) ./doc/user-guide/hot/section_hot_spec.xml:64(para) ./doc/user-guide/hot/section_hot_spec.xml:81(para) ./doc/user-guide/hot/section_hot_spec.xml:408(para) ./doc/user-guide/hot/section_hot_spec.xml:415(para) +msgid "This section is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:60(term) ./doc/user-guide/hot/section_hot_spec.xml:117(term) ./doc/user-guide/hot/section_environment.xml:17(literal) +msgid "parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:62(para) +msgid "This section specifies input parameters that have to be provided when instantiating the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:68(term) +msgid "resources" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:70(para) +msgid "This section contains the declaration of the resources of the template. This section with at least one resource must be defined in any HOT template, or the template would not really do anything when being instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:77(term) +msgid "outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:79(para) +msgid "This section specifies output parameters available to users once the template has been instantiated." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:88(title) +msgid "Parameter groups section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:89(para) +msgid "The parameter_groups section specifies how the input parameters should be grouped and the order to provide the parameters in. These groups are typically used to describe expected behavior for downstream user interfaces." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:92(para) +msgid "These groups are specified in a list with each group containing a list of associated parameters. The lists are used to denote the expected order of the parameters. A parameter can only be included in one group. Use the name of the parameter to add it to a group. The parameters details are defined in the parameters section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:105(term) ./doc/user-guide/hot/section_hot_spec.xml:166(term) +msgid "label" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:107(para) +msgid "A human-readable label that defines the associated group of parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:113(para) +msgid "A human-readable description of the parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:119(para) +msgid "A list of parameters that belong with this parameter group." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:123(term) ./doc/user-guide/hot/section_hot_spec.xml:151(term) +msgid "param name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:125(para) +msgid "The name of a parameter defined in the parameters section." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:132(title) +msgid "Parameters section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:133(para) +msgid "The parameters section defines input parameters that have to be provided when instantiating the template. Such parameters are typically used to customize each deployment, or for binding to environment specifics like certain images." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:137(para) +msgid "Each parameter is specified in a separated nested block with the name of the parameter defined in the first line and additional attributes such as a type or a default value defined as nested elements:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:153(para) +msgid "The name of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:157(term) ./doc/user-guide/hot/section_hot_spec.xml:397(term) +msgid "type" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:159(para) +msgid "The type of the parameter. Supported types are string, number, comma_delimited_list, json and boolean." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:162(para) ./doc/user-guide/hot/section_hot_spec.xml:400(para) ./doc/user-guide/hot/section_hot_spec.xml:519(para) +msgid "This attribute is required." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:168(para) +msgid "A human readable name for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:169(para) ./doc/user-guide/hot/section_hot_spec.xml:176(para) ./doc/user-guide/hot/section_hot_spec.xml:184(para) ./doc/user-guide/hot/section_hot_spec.xml:202(para) ./doc/user-guide/hot/section_hot_spec.xml:252(para) ./doc/user-guide/hot/section_hot_spec.xml:423(para) ./doc/user-guide/hot/section_hot_spec.xml:432(para) ./doc/user-guide/hot/section_hot_spec.xml:440(para) ./doc/user-guide/hot/section_hot_spec.xml:510(para) +msgid "This attribute is optional." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:175(para) +msgid "A human readable description for the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:180(term) +msgid "default" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:182(para) +msgid "A default value for the parameter. This value is used if the user doesn't specify his own value during deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:188(term) +msgid "hidden" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:190(para) +msgid "Defines whether the parameters should be hidden when a user requests information about a stack created from the template. This attribute can be used to hide passwords specified as parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:193(para) +msgid "This attribute is optional and defaults to false." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:197(term) +msgid "constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:199(para) +msgid "A list of constraints to apply. The constraints are validated by the Orchestration engine when a user deploys a stack. The stack creation fails if the parameter value doesn't comply to the constraints." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:206(para) +msgid "The following example shows a minimalistic definition of two parameters:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:217(para) +msgid "The description and the label are optional, but defining these attributes is good practice to provide useful information about the role of the parameter to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:222(title) +msgid "Parameter constraints" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:223(para) +msgid "The constraints block of a parameter definition defines additional validation constraints that apply to the value of the parameter. The parameter values provided by a user are validated against the contrainsts at instantiation time. The contrainsts are defined as a list with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:233(term) +msgid "constraint type" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:235(para) +msgid "Type of constraint to apply. The set of currently supported constraints is given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:240(term) +msgid "constraint definition" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:242(para) +msgid "The actual constraint, depending on the constraint type. The concrete syntax for each constraint type is given below." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:249(para) +msgid "A description of the constraint. The text is presented to the user when the value he defines violates the constraint. If ommitted, a default validation message is presented to the user." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:256(para) +msgid "The following example shows the definition of a string parameter with two constraints. Note that while the descriptions for each constraint are optional, it is good practice to provide concrete descriptions to present useful messages to the user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:271(para) +msgid "While the descriptions for each constraint are optional, it is good practice to provide concrete descriptions so useful messages can be presented to the user at deployment time." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:275(para) +msgid "The following sections list the supported types of parameter constraints, along with the syntax for each type." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:278(title) +msgid "length" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:279(para) +msgid "The length constraint applies to parameters of type string. It defines a lower and upper limit for the length of the string value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:281(para) +msgid "The syntax of the length constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:283(para) +msgid "It is possible to define a length constraint with only a lower limit or an upper limit. However, at least one of min or max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:287(title) +msgid "range" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:288(para) +msgid "The range constraint applies to parameters of type number. It defines a lower and upper limit for the numeric value of the parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:290(para) +msgid "The syntax of the range constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:292(para) +msgid "It is possible to define a range constraint with only a lower limit or an upper limit. However, at least one of min or max must be specified." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:294(para) +msgid "The minimum and maximum boundaries are included in the range. For example, the following range constraint would allow for all numeric values between 0 and 10:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:299(title) +msgid "allowed_values" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:300(para) +msgid "The allowed_values constraint applies to parameters of type string or number. It specifies a set of possible values for a parameter. At deployment time, the user-provided value for the respective parameter must match one of the elements of the list." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:304(para) +msgid "The syntax of the allowed_values constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:306(para) +msgid "Alternatively, the following YAML list notation can be used:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:324(title) +msgid "allowed_pattern" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:325(para) +msgid "The allowed_pattern constraint applies to parameters of type string. It specifies a regular expression against which a user-provided parameter value must evaluate at deployment." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:328(para) +msgid "The syntax of the allowed_pattern constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:341(title) +msgid "custom_constraint" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:342(para) +msgid "The custom_constraint constraint adds an extra step of validation, generally to check that the specified resource exists in the backend. Custom constraints get implemented by plug-ins and can provide any kind of advanced constraint validation logic." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:346(para) +msgid "The syntax of the custom_constraint constraint is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:348(para) +msgid "The name attribute specifies the concrete type of custom constraint. It corresponds to the name under which the respective validation plugin has been registered in the Orchestration engine." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:361(title) +msgid "Pseudo Parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:362(para) +msgid "In addition to parameters defined by a template author, the Orchestration module also creates two parameters for every stack that allow referential access to the stack's name and identifier. These parameters are named OS::stack_name for the stack name and OS::stack_id for the stack identifier. These values are accessible via the get_param intrinsic function, just like user-defined parameters." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:372(title) +msgid "Resources section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:373(para) +msgid "The resources section defines actual resources that make up a stack deployed from the HOT template (for instance compute instances, networks, storage volumes)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:376(para) +msgid "Each resource is defined as a separate block in the resources section with the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:390(term) ./doc/user-guide/hot/section_hot_spec.xml:551(term) +msgid "resource ID" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:392(para) +msgid "A resource ID which must be unique within the resources section of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:399(para) +msgid "The resource type, such as OS::Nova::Server or OS::Neutron::Port." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:404(term) +msgid "properties" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:406(para) +msgid "A list of resource-specific properties. The property value can be provided in place, or via a function (see Intrinsic functions)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:412(term) +msgid "metadata" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:414(para) +msgid "Resource-specific metadata." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:419(term) +msgid "depends_on" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:421(para) +msgid "Dependencies of the resource on one or more resources of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:422(para) +msgid "See Resource dependencies for details." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:427(term) +msgid "update_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:429(para) +msgid "Update policy for the resource, in the form of a nested dictionary. Whether update policies are supported and what the exact semantics are depends on the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:436(term) +msgid "deletion_policy" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:438(para) +msgid "Deletion policy for the resource. Which type of deletion policy is supported depends on the type of the current resource." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:444(para) +msgid "Depending on the type of resource, the resource block might include more resource specific data." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:446(para) +msgid "All resource types that can be used in CFN templates can also be used in HOT templates, adapted to the YAML structure as outlined above." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:448(para) +msgid "The following example demonstrates the definition of a simple compute resource with some fixed property values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:457(title) +msgid "Resource dependencies" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:458(para) +msgid "The depends_on attribute of a resource defines a dependency between this resource and one or more other resources." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:460(para) +msgid "If a resource depends on just one other resource, the ID of the other resource is specified as string of the depends_on attribute, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:470(para) +msgid "If a resource depends on more than one other resources, the value of the depends_on attribute is specified as a list of resource IDs, as shown in the following example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:487(title) +msgid "Outputs section" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:488(para) +msgid "The outputs section defines output parameters that should be available to the user once a stack has been created. This would be, for example, parameters such as IP addresses of deployed instances, or URLs of web applications deployed as part of a stack." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:492(para) +msgid "Each output parameter is defined as a separate block within the outputs section according to the following syntax:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:500(term) ./doc/user-guide/hot/section_hot_spec.xml:638(term) +msgid "parameter name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:502(para) +msgid "The output parameter name, which must be unique within the outputs section of a template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:509(para) +msgid "A short description of the output parameter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:514(term) +msgid "parameter value" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:516(para) +msgid "The value of the output parameter. This value is usually resolved by means of a function. See Intrinsic functions for details about the functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:523(para) +msgid "The example below shows how the IP address of a compute resource can be defined as an output parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:532(title) +msgid "Intrinsic functions" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:533(para) +msgid "HOT provides a set of intrinsic functions that can be used inside templates to perform specific tasks, such as getting the value of a resource attribute at runtime. The following section describes the role and syntax of the intrinsic functions." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:538(title) +msgid "get_attr" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:539(para) +msgid "The get_attr function references an attribute of a resource. The attribute value is resolved at runtime using the resource instance created from the respective resource definition." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:542(para) +msgid "The syntax of the get_attr function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:553(para) +msgid "The resource ID for which the attribute needs to be resolved." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:554(para) +msgid "The resource ID must exist in the resources section of the template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:558(term) +msgid "attribute name" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:560(para) +msgid "The attribute name to be resolved. If the attribute returns a complex data structure such as a list or a map, then subsequent keys or indexes can be specified. These additional parameters are used to navigate the data structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:567(para) +msgid "The following example demonstrates how to use the get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:580(para) +msgid "In this example, if the networks attribute contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:583(para) +msgid "then the value of the get_attr function would resolve to 10.0.0.1 (first item of the private entry in the networks map)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:588(para) +msgid "The get_file function returns the content of a file into the template. It is generally used as a file inclusion mechanism for files containing scripts or configuration files." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:591(para) +msgid "The syntax of the get_file function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:593(para) +msgid "The content key is used to look up the files dictionary that is provided in the REST API call. The Orchestration client command () is get_file aware and will populate the files dictionnary with the actual content of fetched paths and URLs. The Orchestration client command supports relative paths and will transform these to the absolute URLs required by the Orcestration API." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:600(para) +msgid "The get_file argument must be a static path or URL and not rely on intrinsic functions like get_param. the Orchestration client does not process intrinsic functions (they are only processed by the Orchestration engine)." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:605(para) +msgid "The example below demonstrates the get_file function usage with both relative and absolute URLs:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:621(para) +msgid "The files dictionary generated by the Orchestration client during instantiation of the stack would contain the following keys: * file:///path/to/my_instance_user_data.sh * http://example.com/my_other_instance_user_data.sh*" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:628(para) +msgid "The get_param function references an input parameter of a template. It resolves to the value provided for this input parameter at runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:630(para) +msgid "The syntax of the get_param function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:640(para) +msgid "The parameter name to be resolved. If the parameters returns a complex data structure such as a list or a map, then subsequent keys or indexes can be specified. These additional parameters are used to navigate the data structure to return the desired value." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:647(para) +msgid "The following example demonstrates the use of the get_param function:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:663(para) +msgid "In this example, if the instance_type and server_data parameters contained the following data:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:668(para) +msgid "then the value of the property flavor would resolve to m1.tiny, metadata would resolve to {\"foo\": \"bar\"} and key_name would resolve to a_key." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:674(para) +msgid "The get_resource function references another resource within the same template. At runtime, it is resolved to reference the ID of the referenced resource, which is resource type specific. For example, a reference to a floating IP resource returns the respective IP address at runtime. The syntax of the get_resource function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:680(para) +msgid "The resource ID of the referenced resource is given as single parameter to the get_resource function." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:682(para) +msgid "For exemple:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:697(para) +msgid "The list_join function joins a list of strings with the given delimiter." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:698(para) +msgid "The syntax of the list_join function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:704(para) +msgid "This resolve to the string one, two, and three." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:707(title) +msgid "resource_facade" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:708(para) +msgid "The resource_facade function retrieves data in a parent provider template." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:709(para) +msgid "A provider template provdes a custom definition of a resource, called its facade. For more information about custom templates, see . The syntax of the resource_facade function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:713(para) +msgid "data type can be one of metadata, deletion_policy or update_policy." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:718(para) +msgid "The str_replace function dynamically constructs strings by providing a template string with placeholders and a list of mappings to assign values to those placeholders at runtime. The placeholders are replaced with mapping values wherever a mapping key exactly matches a placeholder." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:722(para) +msgid "The syntax of the str_replace function is:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:728(term) +msgid "template" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:730(para) +msgid "Defines the template string that contains placeholders which will be substituted at runtime." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:735(term) +msgid "params" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:737(para) +msgid "Provides parameter mappings in the form of dictionary. Each key refers to a placeholder used in the template attribute." +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:742(para) +msgid "The following example shows a simple use of the str_replace function in the outputs section of a template to build a URL for logging into a deployed application:" +msgstr "" + +#: ./doc/user-guide/hot/section_hot_spec.xml:758(para) +msgid "The following examples show the use of the str_replace function to build an instance initialization script:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_hello_world.xml:15(title) +msgid "Writing a hello world HOT template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:16(para) +msgid "HOT is a new template format meant to replace the CloudFormation-compatible format (CFN) as the native format supported by the Orchestration module over time. This guide is targeted towards template authors and explains how to write HOT templates based on examples. A detailed specification of HOT can be found at ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:22(para) +msgid "This section gives an introduction on how to write HOT templates, starting from very basic steps and then going into more and more detail by means of examples." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:26(title) +msgid "A most basic template" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:27(para) +msgid "The most basic template you can think of contains only a single resource definition using only predefined properties. For example, the template below could be used to deploy a single compute instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:41(para) +msgid "Each HOT template has to include the heat_template_version key with value 2013-05-23, the current HOT version. While the description key is optional, it is good practice to include some useful text that describes what users can do with the template. In case you want to provide a longer description that does not fit on a single line, you can provide multi-line text in YAML, for example:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:50(para) +msgid "The resources section is required and must contain at least one resource definition. In the above example, a compute instance is defined with fixed values for the key_name, image and flavor properties." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:54(para) +msgid "All the defined elements (key pair, image, flavor) have to exist in the OpenStack environment where the template is used." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:60(title) +msgid "Input parameters" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:61(para) +msgid "Input parameters defined in the parameters section of a template allow users to customize a template during deployment. For example, this allows for providing custom key pair names or image IDs to be used for a deployment. From a template author's perspective, this helps to make a template more easily reusable by avoiding hardcoded assumptions." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:66(para) +msgid "The following example extends the previous template to provide parameters for the key pair, image and flavor properties of the resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:93(para) +msgid "Values for the three parameters must be defined by the template user during the deployment of a stack. The get_param intrinsic function retrieves a user-specified value for a given parameter and uses this value for the associated resource property." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:97(para) +msgid "For more information about intrinsic functions, see ." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:100(title) +msgid "Providing default values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:101(para) +msgid "You can provide default values for parameters. If a user doesn't define a value for a parameter, the default value is used during the stack deployment. The following example defines a default value m1.small for the flavor property:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:112(para) +msgid "If a template doesn't define a default value for a parameter, then the user must define the value, otherwise the stack creation will fail." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:117(title) +msgid "Hidding parameters values" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:118(para) +msgid "The values that a user provides when deploying a stack are available in the stack details and can be accessed by any user in the same tenant. To hide the value of a parameter, use the hidden boolean attribute of the parameter:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:129(title) +msgid "Restricting user input" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:130(para) +msgid "You can restrict the values of an input parameter to make sure that the user defines valid data for this parameter. The constraints property of an input parameter defines a list of constraints to apply for the parameter. The following example restricts the flavor parameter to a list of three possible values:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:143(para) +msgid "The following example defines multiple contraints for a password definition:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:157(para) +msgid "The list of supported constraints is available in the section." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:160(para) +msgid "You can define multiple constraints of the same type. Especially in the case of allowed patterns this not only allows for keeping regular expressions simple and maintainable, but also for keeping error messages to be presented to users precise." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:169(title) +msgid "Template outputs" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:170(para) +msgid "In addition to template customization through input parameters, you can provide information about the resources created during the stack deployment to the users in the outputs section of a template. In the following example the output section provides the IP address of the my_instance resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:179(para) +msgid "Output values are typically resolved using intrinsic function such as the get_attr. See for more information about intrinsic functions.." +msgstr "" + +#: ./doc/user-guide/hot/section_hello_world.xml:183(para) +msgid "See for more information about the outputs section." +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_basic_resources.xml:4(title) +msgid "Instances" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:11(title) +msgid "Manage instances" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:13(title) +msgid "Create an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:14(para) +msgid "Use the OS::Nova::Server resource to create a Compute instance. The flavor property is the only mandatory one, but you need to define a boot source using one of the image or block_device_mapping properties." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:17(para) +msgid "You also need to define the networks property to indicate to which networks your instance must connect if multiple networks are available in your tenant." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:19(para) +msgid "The following example creates a simple instance, booted from an image, and connecting to the private network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:31(title) +msgid "Connect an instance to a network" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:32(para) +msgid "Use the networks property of an OS::Nova::Server resource to define which networks an instance should connect to. Define each network as a YAML map, containing one of the following keys:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:38(literal) +msgid "port" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:41(para) +msgid "The ID of an existing Networking port. You usually create this port in the same template using an OS::Neutron::Port resource. You will be able to associate a floating IP to this port, and the port to your Compute instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:49(literal) +msgid "network" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:52(para) +msgid "The name or ID of an existing network. You don't need to create an OS::Neutron::Port resource if you use this property, but you will not be able to associate a floating IP with the instance interface in the template." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:59(para) +msgid "The following example demonstrates the use of the port and network properties:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:86(title) +msgid "Create and associate security groups to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:87(para) +msgid "Use the OS::Neutron::SecurityGroup resource to create security groups." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:89(para) +msgid "Define the security_groups property of the OS::Neutron::Port resource to associate security groups to a port, then associate the port to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:92(para) +msgid "The following example creates a security group allowing inbound connections on ports 80 and 443 (web server) and associates this security group to an instance port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:128(title) +msgid "Create and associate a floating IP to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:129(para) +msgid "You can use two sets of resources to create and associate floating IPs to instances." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:132(title) +msgid "OS::Nova resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:133(para) +msgid "Use the OS::Nova::FloatingIP resource to create a floating IP, and the OS::Nova::FloatingIPAssociation resource to associate the floating IP to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:136(para) +msgid "The following example creates an instance and a floating IP, and associate the floating IP to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:159(title) +msgid "OS::Neutron resources" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:161(para) +msgid "The Networking service (neutron) must be enabled on your OpenStack deployment to use these resources." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:164(para) +msgid "Use the OS::Neutron::FloatingIP resource to create a floating IP, and the OS::Neutron::FloatingIPAssociation resource to associate the floating IP to a port:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:189(title) +msgid "Enable remote access to an instance" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:190(para) +msgid "The key_name attribute of the OS::Nova::Server resource defines the key pair to use to enable SSH remote access:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:200(para) +msgid "For more information about key pairs, see the Configure access and security for instances section of the OpenStack user guide." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:205(title) +msgid "Create a key pair" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:206(para) +msgid "You can create new key pairs with the OS::Nova::KeyPair resource. Key pairs can be imported or created during the stack creation." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:208(para) +msgid "If the public_key property is not specified, the Orchestration module creates a new key pair. If the save_private_key property is set to true, the private_key attribute of the resource holds the private key." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:211(para) +msgid "The following example creates a new key pair and uses it as authentication key for an instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:234(title) +msgid "Manage networks" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:236(title) +msgid "Create a network and a subnet" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:238(para) +msgid "The Networking service (neutron) must be enabled on your OpenStack deployment to create and manage networks and subnets. Networks and subnets cannot be created if your deployment uses legacy networking (nova-network)." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:242(para) +msgid "Use the OS::Neutron::Net resource to create a network, and the OS::Neutron::Subnet resource to provide a subnet for this network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:257(title) +msgid "Create and manage a router" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:258(para) +msgid "Use the OS::Neutron::Router resource to create a router. You can define its gateway with the external_gateway_info property:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:265(para) +msgid "You can connect subnets to routers with the OS::Neutron::RouterInterface resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:275(title) +msgid "Complete network example" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:276(para) +msgid "The following example creates a network stack:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:279(para) +msgid "A network and an associated subnet." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:282(para) +msgid "A router with an external gateway." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:285(para) +msgid "An interface to the new subnet for the new router." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:288(para) +msgid "In this example, the public network is an existing shared network:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:315(title) +msgid "Manage volumes" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:318(para) +msgid "Use the OS::Cinder::Volume resource to create a new Block Storage volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:326(para) +msgid "The volumes that you create are empty by default. Use the image property to create a bootable volume from an existing image:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:334(para) +msgid "You can also create new volumes from another volume, a volume snapshot, or a volume backup. Use the source_volid, snapshot_id or backup_id properties to create a new volume from an existing source." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:337(para) +msgid "For example, to create a new volume from a backup:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:343(para) +msgid "In this example the size property is not defined because the Block Storage service uses the size of the backup to define the size of the new volume." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:348(para) +msgid "Use the OS::Cinder::VolumeAttachment resource to attach a volume to an instance." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:350(para) +msgid "The following example creates a volume and an instance, and attaches the volume to the instance:" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:371(title) +msgid "Boot an instance from a volume" +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:372(para) +msgid "Use the block_device_mapping property of the OS::Nova::Server resource to define a volume used to boot the instance. This property is a list of volumes to attach to the instance before its boot." +msgstr "" + +#: ./doc/user-guide/hot/section_basic_resources.xml:375(para) +msgid "The following example creates a bootable volume from an image, and uses it to boot an instance:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_composition.xml:4(title) +msgid "Template composition" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:5(para) +msgid "When writing complex templates you are encouraged to break up your template into separate smaller templates. These can then be brought together using template resources. This is a mechanism to define a resource using a template, thus composing one logical stack with multiple templates." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:9(para) +msgid "Template resources provide a feature similar to the AWS::CloudFormation::Stack resource, but also provide a way to:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:13(para) +msgid "Define new resource types and build your own resource library." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:16(para) +msgid "Override the default behaviour of existing resource types." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:19(para) +msgid "To achieve this:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:22(para) +msgid "The Orchestration client gets the associated template files and passes them along in the files section of the POST stacks/ API request." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:26(para) +msgid "The environment in the Orchestration engine manages the mapping of resource type to template creation." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:30(para) +msgid "The Orchestration engine translates template parameters into resource properties." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:34(para) +msgid "The following examples illustrate how you can use a custom template to define new types of resources. These examples use a custom template stored in a my_nova.yml file:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:53(title) +msgid "Use the template filename as type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:54(para) +msgid "The following template defines the my_nova.yaml file as value for the type property of a resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:62(para) +msgid "The key_name argument of the my_nova.yaml template gets its value from the key_name property of the new template." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:65(para) +msgid "The above reference to my_nova.yaml assumes it is in the same directory. You can use any of the following forms:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:69(para) +msgid "Relative path (my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:72(para) +msgid "Absolute path (file:///home/user/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:75(para) +msgid "Http URL (http://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:78(para) +msgid "Https URL (https://example.com/templates/my_nova.yaml)" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:82(para) ./doc/user-guide/hot/section_composition.xml:105(para) +msgid "To create the stack run:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:87(title) +msgid "Define a new resource type" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:88(para) +msgid "You can associate a name to the my_noya.yaml template in an environment file. If the name is already known by the Orchestration module then your new resource will override the default one." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:91(para) +msgid "In the following example a new OS::Nova::Server resource overrides the default resource of the same name." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:93(para) +msgid "An env.yaml environment file holds the definition of the new resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:97(para) +msgid "See for more detail about environment files." +msgstr "" + +#: ./doc/user-guide/hot/section_composition.xml:99(para) +msgid "You can now use the new OS::Nova::Server in your new template:" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_advanced_topics.xml:4(title) +msgid "Advanced topics" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:9(title) +msgid "Load balancer" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:10(para) ./doc/user-guide/hot/section_advanced_topics.xml:14(para) ./doc/user-guide/hot/section_advanced_topics.xml:18(para) ./doc/user-guide/hot/section_advanced_topics.xml:26(para) ./doc/user-guide/hot/section_advanced_topics.xml:30(para) +msgid "TODO" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:13(title) +msgid "Firewall" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:17(title) +msgid "VPN" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:23(title) +msgid "Auto scaling" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:25(title) +msgid "Alarming" +msgstr "" + +#: ./doc/user-guide/hot/section_advanced_topics.xml:29(title) +msgid "Up scaling and down scaling" +msgstr "" + +#. WARNING: This file is automatically generated. Do not edit it. +#: ./doc/user-guide/hot/section_environment.xml:4(title) +msgid "Environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:5(para) +msgid "The environment affects the runtime behaviour of a template. It provides a way to override the resource implementations and a mechanism to place parameters that the service needs." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:8(para) +msgid "To fully understand the runtime behavior you have to consider what plug-ins are installed on the cloud you're using." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:12(title) +msgid "Environment file format" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:13(para) +msgid "The environment is a yaml text file that contains two main sections:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:20(para) +msgid "A map of key/pair values." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:25(literal) +msgid "resource_registry" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:28(para) +msgid "Definition of custom resources." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:32(para) +msgid "Use the -e option of the command to create a stack using with the environment defined in such a file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:34(para) +msgid "You can also provide environment parameters as a list of key/value pairs using the -P option of the command." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:36(para) +msgid "In the following example the environment is read from the my_env.yaml file and an extra parameter is provided using the -P option:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:42(title) +msgid "Global and effective environments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:43(para) +msgid "The environment used for a stack is the combination of the environment you use with the template for the stack, and a global environment that is determined by your cloud operator. An entry in the user environment takes precedence over the global environment. OpenStack includes a default global environment, but you cloud operator can add additional environment entries." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:69(title) +msgid "Define values for a template arguments" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:70(para) +msgid "You can define values for the template arguments in the parameters section of an environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:79(title) +msgid "Create and override resources" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:80(para) +msgid "You can create or override resources in the resource_registry section of an environment file. The resource you provide in this manner must have an identifier, and references either other resources IDs or the URL of an existing template file." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:84(para) +msgid "The following example maps the new OS::Networking::FloatingIP resource to the existing OS::Nova::FloatingIP resource:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:88(para) +msgid "You can use wilcards to map multiple resources:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:91(para) +msgid "To create or override a resource with a custom resource, create a template file to define this resource, and provide the URL to the template file in the environment file:" +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:96(para) +msgid "The supported URL scheme are file, http and https." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:98(para) +msgid "The template file extension must be .yaml or .template, or it will not be treated as a custom template resource." +msgstr "" + +#: ./doc/user-guide/hot/section_environment.xml:101(para) +msgid "You can limit the usage of a custom resource to a specific resource of the template:" +msgstr "" + #. Put one translator per line, in the form of NAME , YEAR1, YEAR2 -#: ./doc/user-guide/section_sdk_configure_instances.xml:0(None) +#: ./doc/user-guide/hot/section_environment.xml:0(None) msgid "translator-credits" msgstr ""