openstack/openstack-manuals
Code Issues Proposed changes

Imported Translations from Transifex

Browse Source 
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure

Change-Id: Ic79eb783d2f9482064ee417a158ca2311d7a50ec
This commit is contained in:
OpenStack Proposal Bot 2014-12-31 06:14:23 +00:00
parent d4fdca3d6d
commit 886a689c25
10 changed files with 1863 additions and 1206 deletions
doc
glossary/locale
ko_KR.po
image-guide/locale
fr.poimage-guide.potja.po
install-guide/locale
install-guide.potja.popt_BR.po
user-guide/locale
fr.poja.pouser-guide.pot

46
doc/glossary/locale/ko_KR.po

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-23 02:43+0000\n"
"PO-Revision-Date: 2014-12-22 14:11+0000\n"
"POT-Creation-Date: 2014-12-31 05:36+0000\n"
"PO-Revision-Date: 2014-12-30 13:51+0000\n"
"Last-Translator: Sungjin Kang <potopro@gmail.com>\n"
"Language-Team: Korean (Korea) (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ko_KR/)\n"
"MIME-Version: 1.0\n"
@ -266,7 +266,7 @@ msgstr "주소 풀"
msgid ""
"A group of fixed and/or floating IP addresses that are assigned to a project"
" and can be used by or assigned to the VM instances in a project."
msgstr "프로젝트에 할당되어 있고 프로젝트 내 VM 인스턴스가 사용하거나 할당될 수 있는 Fixed 및/또는 Floating IP 주소 그룹"
msgstr "프로젝트에 할당되었거나, 프로젝트에 있는 VM 인스턴스에 할당되어 사용할 수 있는 고정 IP이거나 유동 IP 주소 그룹을 나타냅니다."
#: ./doc/glossary/glossary-terms.xml258(glossterm)
#: ./doc/glossary/glossary-terms.xml260(primary)
@ -317,11 +317,11 @@ msgstr "모바일과 임베디드 장치에서 사용하는 저전력 CPU입니
#: ./doc/glossary/glossary-terms.xml310(glossterm)
msgid "alert"
msgstr "alert"
msgstr "알림"
#: ./doc/glossary/glossary-terms.xml312(primary)
msgid "alerts"
msgstr "alerts"
msgstr "알림들"
#: ./doc/glossary/glossary-terms.xml314(secondary)
#: ./doc/glossary/glossary-terms.xml876(secondary)
@ -364,7 +364,7 @@ msgid ""
"The Compute service can send alerts through its notification system, which "
"includes a facility to create custom notification drivers. Alerts can be "
"sent to and displayed on the horizon dashboard."
msgstr "Compute 서비스는 사용자 정의 통지 드라이버를 생성할 수 있는 기능을 포함하는 통지 시스템을 통해 alert을 보낼 수 있습니다. Alert은 horizon 대시보드에서 보내거나 표시할 수 있습니다."
msgstr "Compute 서비스는 사용자 정의 통지 드라이버를 생성할 수 있는 기능을 포함하는 통지 시스템을 통해 알림을 보낼 수 있습니다. 알림은 horizon 대시보드에서 보내거나 표시할 수 있습니다."
#: ./doc/glossary/glossary-terms.xml326(glossterm)
msgid "allocate"
@ -411,7 +411,7 @@ msgstr "Anvil"
msgid ""
"A project that ports the shell script-based project named DevStack to "
"Python."
msgstr "DevStack이라는 이름의 쉘 스크립트 기반 프로젝트가 Python으로 포팅된 프로젝트"
msgstr "Python으로 구성되어있는 DevStack을 쉘 스크립트 기반 프로젝트의 이름입니다."
#: ./doc/glossary/glossary-terms.xml387(glossterm)
#: ./doc/glossary/glossary-terms.xml389(primary)
@ -457,7 +457,7 @@ msgstr "응용프로그램 프로그래밍 인터페이스"
#: ./doc/glossary/glossary-terms.xml436(secondary)
#: ./doc/glossary/glossary-terms.xml441(secondary)
msgid "API endpoint"
msgstr "API endpoint"
msgstr "API 엔드 포인트"
#: ./doc/glossary/glossary-terms.xml434(primary)
#: ./doc/glossary/glossary-terms.xml2910(primary)
@ -465,7 +465,7 @@ msgstr "API endpoint"
#: ./doc/glossary/glossary-terms.xml3572(primary)
#: ./doc/glossary/glossary-terms.xml8146(primary)
msgid "endpoints"
msgstr "endpoints"
msgstr "엔드 포인트들"
#: ./doc/glossary/glossary-terms.xml439(primary)
#: ./doc/glossary/glossary-terms.xml455(primary)
@ -493,7 +493,7 @@ msgstr "API 확장"
#: ./doc/glossary/glossary-terms.xml461(para)
msgid "Custom modules that extend some OpenStack core APIs."
msgstr "일부 OpenStack 코어 API를 확장하는 사용자 정의 모듈."
msgstr "일부 OpenStack 코어 API를 확장하는 사용자 정의 모듈을 말합니다."
#: ./doc/glossary/glossary-terms.xml466(glossterm)
#: ./doc/glossary/glossary-terms.xml470(secondary)
@ -502,7 +502,7 @@ msgstr "API 확장 플러그인"
#: ./doc/glossary/glossary-terms.xml474(para)
msgid "Alternative term for a Networking plug-in or Networking API extension."
msgstr "네트워킹 플러그인이나 네트워킹 API 확장에 대한 대체 용어."
msgstr "네트워킹 플러그인이나 네트워킹 API 확장에 대한 대체 용어입니다."
#: ./doc/glossary/glossary-terms.xml480(glossterm)
#: ./doc/glossary/glossary-terms.xml484(secondary)
@ -511,7 +511,7 @@ msgstr "API 키"
#: ./doc/glossary/glossary-terms.xml488(para)
msgid "Alternative term for an API token."
msgstr "API 토큰의 대체 용어."
msgstr "API 토큰의 대체 용어입니다."
#: ./doc/glossary/glossary-terms.xml493(glossterm)
#: ./doc/glossary/glossary-terms.xml497(secondary)
@ -685,7 +685,7 @@ msgstr "논리적 포트에 인터페이스 ID 모음. 포트에 인터페이스
#: ./doc/glossary/glossary-terms.xml678(glossterm)
#: ./doc/glossary/glossary-terms.xml680(primary)
msgid "auditing"
msgstr "감사"
msgstr "auditing"
#: ./doc/glossary/glossary-terms.xml684(para)
msgid "Provided in Compute through the system usage data facility."
@ -733,7 +733,7 @@ msgid ""
"The process that confirms that the user, process, or client is really who "
"they say they are through private key, secret token, password, fingerprint, "
"or similar method."
msgstr ""
msgstr "사용자, 프로세스 또는 클라인트 중 정말 누구가 말하는지를 개인 키, 암호화된 토큰, 암호, 지문과 비슷한 매소드들을 통해 확인하는 프로세스를 말합니다."
#: ./doc/glossary/glossary-terms.xml742(glossterm)
msgid "authentication token"
@ -741,13 +741,13 @@ msgstr "인증 토큰"
#: ./doc/glossary/glossary-terms.xml744(primary)
msgid "authentication tokens"
msgstr "인증 토큰"
msgstr "인증 토큰들"
#: ./doc/glossary/glossary-terms.xml748(para)
msgid ""
"A string of text provided to the client after authentication. Must be "
"provided by the user or process in subsequent requests to the API endpoint."
msgstr ""
msgstr "인증후 클라이언트에 제공하는 텍스트 문자열입니다. API 엔드 포인트에서 이후에 요청된 프로세스나 사용자에의해 제공되어야합니다."
#: ./doc/glossary/glossary-terms.xml755(glossterm)
#: ./doc/glossary/glossary-terms.xml757(primary)
@ -756,7 +756,7 @@ msgstr "AuthN"
#: ./doc/glossary/glossary-terms.xml761(para)
msgid "The Identity Service component that provides authentication services."
msgstr ""
msgstr "인증 서비스를 제공하는 Identity 서비스 컴포넌트를 말합니다."
#: ./doc/glossary/glossary-terms.xml767(glossterm)
#: ./doc/glossary/glossary-terms.xml769(primary)
@ -1057,7 +1057,7 @@ msgstr "BMC"
#: ./doc/glossary/glossary-terms.xml1083(primary)
msgid "BMC (Baseboard Management Controller)"
msgstr ""
msgstr "BMC (베이스보드 관리 컨트롤러)"
#: ./doc/glossary/glossary-terms.xml1087(para)
msgid ""
@ -8169,7 +8169,7 @@ msgid ""
"Xen is a hypervisor using a microkernel design, providing services that "
"allow multiple computer operating systems to execute on the same computer "
"hardware concurrently."
msgstr ""
msgstr "Xen은 여러 컴퓨터 운영체제가 동시에 동일한 컴퓨터 하드웨어상에서 실행할 수 있도록 서비스를 제공하고, 마이크로 커널로 설계된 하이퍼바이저입니다."
#: ./doc/glossary/glossary-terms.xml8953(glossterm)
#: ./doc/glossary/glossary-terms.xml8964(primary)
@ -8209,13 +8209,13 @@ msgstr "XenServer 하이퍼바이저"
#: ./doc/glossary/glossary-terms.xml9002(glossterm)
#: ./doc/glossary/glossary-terms.xml9004(primary)
msgid "XFS"
msgstr ""
msgstr "XFS"
#: ./doc/glossary/glossary-terms.xml9007(para)
msgid ""
"High-performance 64-bit file system created by Silicon Graphics. Excels in "
"parallel I/O operations and data consistency."
msgstr ""
msgstr "실리콘 그래픽스에서 만든 고성능 64-bit 파일 스스템입니다. 병렬 I/O 작업과 데이터 일관성 부분이 우수합니다."
#: ./doc/glossary/glossary-terms.xml9018(title)
msgid "Y"
@ -8234,7 +8234,7 @@ msgstr "ZeroMQ"
msgid ""
"Message queue software supported by OpenStack. An alternative to RabbitMQ. "
"Also spelled 0MQ."
msgstr ""
msgstr "OpenStack를 지원하는 메시지 큐 소프트웨어입니다. RabbitMQ를 대신할 수 있으며, 0MQ로도 불리웁니다."
#: ./doc/glossary/glossary-terms.xml9047(glossterm)
#: ./doc/glossary/glossary-terms.xml9049(primary)
@ -8245,7 +8245,7 @@ msgstr "Zuul"
msgid ""
"Tool used in OpenStack development to ensure correctly ordered testing of "
"changes in parallel."
msgstr ""
msgstr "병렬로 변경분을 테스트할 수 있도록 주문을 하는 OpenStack 개발에서 사용하는 툴을 가르킵니다."
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2
#: ./doc/glossary/glossary-terms.xml0(None)

8
doc/image-guide/locale/fr.po

@ -5,8 +5,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-22 02:28+0000\n"
"PO-Revision-Date: 2014-12-22 01:16+0000\n"
"POT-Creation-Date: 2014-12-31 05:36+0000\n"
"PO-Revision-Date: 2014-12-31 05:36+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
@ -45,8 +45,8 @@ msgid ""
msgstr "Télécharger l'ISO des pilotes signés de VirtIO depuis <link href=\"http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/\">Fedora website</link>. "
#: ./doc/image-guide/section_windows-example.xml31(para)
msgid "Create a 10GB qcow2 image:"
msgstr "Créer une image qcow2 de 10 Go : "
msgid "Create a 15GB qcow2 image:"
msgstr ""
#: ./doc/image-guide/section_windows-example.xml37(para)
msgid ""

4
doc/image-guide/locale/image-guide.pot

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-22 06:12+0000\n"
"POT-Creation-Date: 2014-12-31 06:13+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -30,7 +30,7 @@ msgid "Download the signed VirtIO drivers ISO from the <link href=\"http://alt.f
msgstr ""
#: ./doc/image-guide/section_windows-example.xml:31(para)
msgid "Create a 10GB qcow2 image:"
msgid "Create a 15GB qcow2 image:"
msgstr ""
#: ./doc/image-guide/section_windows-example.xml:37(para)

8
doc/image-guide/locale/ja.po

@ -5,8 +5,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-22 02:28+0000\n"
"PO-Revision-Date: 2014-12-22 01:16+0000\n"
"POT-Creation-Date: 2014-12-31 05:36+0000\n"
"PO-Revision-Date: 2014-12-31 05:36+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@ -45,8 +45,8 @@ msgid ""
msgstr "<link href=\"http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/\">Fedora の Web サイト</link>から署名付き VirtIO ドライバーの ISO をダウンロードします。"
#: ./doc/image-guide/section_windows-example.xml31(para)
msgid "Create a 10GB qcow2 image:"
msgstr "10GB qcow2 イメージを作成します。"
msgid "Create a 15GB qcow2 image:"
msgstr ""
#: ./doc/image-guide/section_windows-example.xml37(para)
msgid ""

446
doc/install-guide/locale/install-guide.pot

File diff suppressed because one or more lines are too long

804
doc/install-guide/locale/ja.po

File diff suppressed because it is too large Load Diff

919
doc/install-guide/locale/pt_BR.po

File diff suppressed because it is too large Load Diff

316
doc/user-guide/locale/fr.po

@ -11,8 +11,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-18 22:20+0000\n"
"PO-Revision-Date: 2014-12-18 22:21+0000\n"
"POT-Creation-Date: 2014-12-31 05:36+0000\n"
"PO-Revision-Date: 2014-12-30 15:53+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: French (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/fr/)\n"
"MIME-Version: 1.0\n"
@ -7791,11 +7791,12 @@ msgid "Custom image building"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml12(para)
#: ./doc/user-guide/hot/section_software_deployment.xml59(title)
#: ./doc/user-guide/hot/section_software_deployment.xml58(title)
msgid "User-data boot scripts and cloud-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml15(para)
#: ./doc/user-guide/hot/section_software_deployment.xml400(title)
msgid "Software deployment resources"
msgstr ""
@ -7864,7 +7865,7 @@ msgid ""
"builder</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml60(para)
#: ./doc/user-guide/hot/section_software_deployment.xml59(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 "
@ -7873,14 +7874,14 @@ msgid ""
"service.html\">Metadata service</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml63(para)
#: ./doc/user-guide/hot/section_software_deployment.xml62(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 <link "
"href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml65(para)
#: ./doc/user-guide/hot/section_software_deployment.xml64(para)
msgid ""
"Whether the image is using <link "
"href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> or "
@ -7888,21 +7889,21 @@ msgid ""
"property and have it be executed by the server during boot:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml80(para)
#: ./doc/user-guide/hot/section_software_deployment.xml79(para)
msgid ""
"<emphasis role=\"Tip\"/>: debugging these scripts it is often useful to view"
" the boot log using <literal>nova console-log &lt;server-id&gt;</literal> to"
" view the progress of boot script execution."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml84(para)
#: ./doc/user-guide/hot/section_software_deployment.xml83(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 "
"<literal>str_replace</literal> intrinsic function:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml106(para)
#: ./doc/user-guide/hot/section_software_deployment.xml105(para)
msgid ""
"<emphasis role=\"Warning\"/>: If a stack-update is performed and there are "
"any changes at all to the content of user_data then the server will be "
@ -7910,14 +7911,14 @@ msgid ""
" be run on a new server."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml111(para)
#: ./doc/user-guide/hot/section_software_deployment.xml110(para)
msgid ""
"When these scripts grow it can become difficult to maintain them inside the "
"template, so the <literal>get_file</literal> intrinsic function can be used "
"to maintain the script in a separate file:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml131(para)
#: ./doc/user-guide/hot/section_software_deployment.xml130(para)
msgid ""
"<emphasis role=\"Tip\"/>: <literal>str_replace</literal> can replace any "
"strings, not just strings starting with <literal>$</literal>. However doing "
@ -7925,11 +7926,11 @@ msgid ""
" for testing by passing in environment variables."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml137(title)
#: ./doc/user-guide/hot/section_software_deployment.xml136(title)
msgid "Choosing the user_data_format"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml138(para)
#: ./doc/user-guide/hot/section_software_deployment.xml137(para)
msgid ""
"The <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> "
@ -7942,7 +7943,7 @@ msgid ""
"be more appropriate."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml144(para)
#: ./doc/user-guide/hot/section_software_deployment.xml143(para)
msgid ""
"For <literal>RAW</literal> the user_data is passed to Nova unmodified. For a"
" <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-"
@ -7950,18 +7951,19 @@ msgid ""
"<literal>RAW</literal> user-data:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml166(para)
#: ./doc/user-guide/hot/section_software_deployment.xml165(para)
msgid ""
"For <literal>SOFTWARE_CONFIG</literal> user_data is bundled as part of the "
"software config data, and metadata is derived from any associated software "
"deployment resources."
"software config data, and metadata is derived from any associated <link "
"linkend=\"software-deployment-resources\">Software deployment "
"resources</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml171(title)
#: ./doc/user-guide/hot/section_software_deployment.xml170(title)
msgid "Signals and wait conditions"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml172(para)
#: ./doc/user-guide/hot/section_software_deployment.xml171(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."
@ -7974,7 +7976,7 @@ msgid ""
" both perform this function using different techniques and tradeoffs."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml178(para)
#: ./doc/user-guide/hot/section_software_deployment.xml177(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -7987,39 +7989,39 @@ msgid ""
"service."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml184(para)
#: ./doc/user-guide/hot/section_software_deployment.xml267(para)
#: ./doc/user-guide/hot/section_software_deployment.xml183(para)
#: ./doc/user-guide/hot/section_software_deployment.xml266(para)
msgid ""
"Sending the signal is a simple HTTP request, as with this example using "
"<link href=\"http://curl.haxx.se/\">curl</link>:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml188(para)
#: ./doc/user-guide/hot/section_software_deployment.xml187(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)
#: ./doc/user-guide/hot/section_software_deployment.xml194(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)
#: ./doc/user-guide/hot/section_software_deployment.xml202(para)
msgid ""
"If <literal>status</literal> is set to <literal>FAILURE</literal> then the "
"resource (and the stack) will go into a <literal>FAILED</literal> state "
"using the <literal>reason</literal> as failure reason."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml205(para)
#: ./doc/user-guide/hot/section_software_deployment.xml204(para)
msgid ""
"The following template example uses the convenience attribute "
"<literal>curl_cli</literal> which builds a curl command with a valid token:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml263(para)
#: ./doc/user-guide/hot/section_software_deployment.xml262(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal>"
@ -8029,13 +8031,13 @@ msgid ""
"used to store multiple signals."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml269(para)
#: ./doc/user-guide/hot/section_software_deployment.xml268(para)
msgid ""
"The above template example only needs to have the <literal>type</literal> "
"changed to the swift signal resources:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml281(para)
#: ./doc/user-guide/hot/section_software_deployment.xml280(para)
msgid ""
"The decision to use <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -8044,14 +8046,14 @@ msgid ""
" will depend on a few factors:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml285(para)
#: ./doc/user-guide/hot/section_software_deployment.xml284(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal>"
" depends on the availability of an Object Storage API"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml289(para)
#: ./doc/user-guide/hot/section_software_deployment.xml288(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -8060,17 +8062,17 @@ msgid ""
"V3 API)."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml294(para)
#: ./doc/user-guide/hot/section_software_deployment.xml293(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)
#: ./doc/user-guide/hot/section_software_deployment.xml299(title)
msgid "Software config resources"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml301(para)
#: ./doc/user-guide/hot/section_software_deployment.xml300(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 "
@ -8082,14 +8084,14 @@ msgid ""
"API calls to create a new config and delete the old one."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml308(para)
#: ./doc/user-guide/hot/section_software_deployment.xml307(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" is used for storing configs represented by text scripts, for example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml326(para)
#: ./doc/user-guide/hot/section_software_deployment.xml325(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal>"
@ -8100,7 +8102,7 @@ msgid ""
"although no further checks for valid cloud-config are done."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml352(para)
#: ./doc/user-guide/hot/section_software_deployment.xml351(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__MultipartMime.html\">OS::Heat::MultipartMime</link></literal>"
@ -8113,6 +8115,246 @@ msgid ""
"multi-part message:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml401(para)
msgid ""
"There are many situations where it is not desirable to replace the server "
"whenever there is a configuration change. The <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource allows any number of software configurations to be added or "
"removed from a server throughout its life-cycle."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml406(title)
msgid "Building custom image for software deployments"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml407(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" resources are used to store software configuration, and a <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource is used to associate a config resource with one server. The "
"<literal>group</literal> attribute on <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" specifies what tool will consume the config content."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml412(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" has the ability to define a schema of <literal>inputs</literal> and which "
"the configuration script supports. Inputs are mapped to whatever concept the"
" configuration tool has for assigning variables/parameters."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml416(para)
msgid ""
"Likewise, <literal>outputs</literal> are mapped to the tool's capability to "
"export structured data after configuration execution. For tools which do not"
" support this, outputs can always be written to a known file path for the "
"hook to read."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml419(para)
msgid ""
"The <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource allows values to be assigned to the config inputs, and the "
"resource remains in an <literal>IN_PROGRESS</literal> state until the server"
" signals to heat what (if any) output values were generated by the config "
"script."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml425(title)
msgid "Custom image script"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml426(para)
msgid ""
"Each of the following examples requires that the servers be booted with a "
"custom image. The following script uses diskimage-builder to create an image"
" required in later examples:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml471(title)
msgid "Configuring with scripts"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml472(para)
msgid ""
"The <link linkend=\"custom-image-script\">Custom image script</link> already"
" includes the <literal>heat-config-script</literal> element so the built "
"image will already have the ability to configure using shell scripts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml475(para)
msgid ""
"Config inputs are mapped to shell environment variables. The script can "
"communicate outputs to heat by writing to the file "
"<literal>$heat_outputs_path.&lt;output name&gt;</literal>. See the following"
" example for a script which expects inputs <literal>foo</literal>, "
"<literal>bar</literal> and generates an output <literal>result</literal>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml529(para)
msgid ""
"<emphasis role=\"Tip\"/>: A config resource can be associated with multiple "
"deployment resources, and each deployment can specify the same or different "
"values for the <literal>server</literal> and <literal>input_values</literal>"
" properties."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml533(para)
msgid ""
"As can be seen in the <literal>outputs</literal> section of the above "
"template, the <literal>result</literal> config output value is available as "
"an attribute on the <literal>deployment</literal> resource. Likewise the "
"captured stdout, stderr and status_code are also available as attributes."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml539(title)
msgid "Configuring with os-apply-config"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml540(para)
msgid ""
"The agent toolchain of <literal>os-collect-config</literal>, <literal>os-"
"refresh-config</literal> and <literal>os-apply-config</literal> can actually"
" be used on their own to inject heat stack configuration data into a server "
"running a custom image."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml543(para)
msgid "The custom image needs to have the following to use this approach:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml546(para)
msgid "All software dependencies installed"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml549(para)
msgid ""
"<link href=\"https://github.com/openstack/os-refresh-config\">os-refresh-"
"config</link> scripts to be executed on configuration changes"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml552(para)
msgid ""
"<link href=\"https://github.com/openstack/os-apply-config\">os-apply-"
"config</link> templates to transform the heat-provided config data into "
"service configuration files"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml556(para)
msgid ""
"The projects <link href=\"https://github.com/openstack/tripleo-image-"
"elements\">tripleo-image-elements</link> and <link "
"href=\"https://github.com/openstack/tripleo-heat-templates\">tripleo-heat-"
"templates</link> demonstrate this approach."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml560(title)
msgid "Configuring with cfn-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml561(para)
msgid ""
"Likely the only reason to use the <literal>cfn-init</literal> hook is to "
"migrate templates which contain <link "
"href=\"http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-"
"resource-init.html\">AWS::CloudFormation::Init</link> metadata without "
"needing a complete rewrite of the config metadata. It is included here as it"
" introduces a number of new concepts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml565(para)
msgid ""
"To use the <literal>cfn-init</literal> tool the <literal>heat-config-cfn-"
"init</literal> element is required to be on the built image, so <link "
"linkend=\"custom-image-script\">Custom image script</link> needs to be "
"modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml570(para)
msgid ""
"Configuration data which used to be included in the "
"<literal>AWS::CloudFormation::Init</literal> section of resource metadata is"
" instead moved to the <literal>config</literal> property of the config "
"resource, as in the following example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml622(para)
msgid "There are a number of things to note about this template example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml625(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__StructuredConfig.html\">OS::Heat::StructuredConfig</link></literal>"
" is like <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" except that the <literal>config</literal> property contains structured YAML"
" instead of text script. This is useful for a number of other configuration "
"tools including ansible, salt and os-apply-config."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml632(para)
msgid ""
"<literal>cfn-init</literal> has no concept of inputs, so "
"<literal>{get_input: bar}</literal> acts as a placeholder which gets "
"replaced with the <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__StructuredDeployment.html\">OS::Heat::StructuredDeployment</link></literal><literal>input_values</literal>"
" value when the deployment resource is created."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml638(para)
msgid ""
"<literal>cfn-init</literal> has no concept of outputs, so specifying "
"<literal>signal_transport: NO_SIGNAL</literal> will mean that the deployment"
" resource will immediately go into the <literal>CREATED</literal> state "
"instead of waiting for a completed signal from the server."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml644(para)
msgid ""
"The template has 2 deployment resources deploying the same config with "
"different <literal>input_values</literal>. The order these are deployed in "
"on the server is determined by sorting the values of the "
"<literal>name</literal> property for each resource (10_deployment, "
"20_other_deployment)"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml652(title)
msgid "Configuring with puppet"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml653(para)
msgid ""
"The <link href=\"http://puppetlabs.com/\">puppet</link> hook makes it "
"possible to write configuration as puppet manifests which are deployed and "
"run in a masterless environment."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml655(para)
msgid ""
"To specify configuration as puppet manifests the <literal>heat-config-"
"puppet</literal> element is required to be on the built image, so <link "
"linkend=\"custom-image-script\">Custom image script</link> needs to be "
"modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml701(para)
msgid ""
"This demonstrates the use of the <literal>get_file</literal> function, which"
" will attach the contents of the file <literal>example-puppet-"
"manifest.pp</literal>, containing:"
msgstr ""
#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/index.xml10(title)
msgid "HOT guide"

316
doc/user-guide/locale/ja.po

@ -7,8 +7,8 @@
msgid ""
msgstr ""
"Project-Id-Version: OpenStack Manuals\n"
"POT-Creation-Date: 2014-12-18 22:20+0000\n"
"PO-Revision-Date: 2014-12-18 22:21+0000\n"
"POT-Creation-Date: 2014-12-31 05:36+0000\n"
"PO-Revision-Date: 2014-12-30 15:53+0000\n"
"Last-Translator: openstackjenkins <jenkins@openstack.org>\n"
"Language-Team: Japanese (http://www.transifex.com/projects/p/openstack-manuals-i18n/language/ja/)\n"
"MIME-Version: 1.0\n"
@ -7787,11 +7787,12 @@ msgid "Custom image building"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml12(para)
#: ./doc/user-guide/hot/section_software_deployment.xml59(title)
#: ./doc/user-guide/hot/section_software_deployment.xml58(title)
msgid "User-data boot scripts and cloud-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml15(para)
#: ./doc/user-guide/hot/section_software_deployment.xml400(title)
msgid "Software deployment resources"
msgstr ""
@ -7860,7 +7861,7 @@ msgid ""
"builder</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml60(para)
#: ./doc/user-guide/hot/section_software_deployment.xml59(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 "
@ -7869,14 +7870,14 @@ msgid ""
"service.html\">Metadata service</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml63(para)
#: ./doc/user-guide/hot/section_software_deployment.xml62(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 <link "
"href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml65(para)
#: ./doc/user-guide/hot/section_software_deployment.xml64(para)
msgid ""
"Whether the image is using <link "
"href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> or "
@ -7884,21 +7885,21 @@ msgid ""
"property and have it be executed by the server during boot:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml80(para)
#: ./doc/user-guide/hot/section_software_deployment.xml79(para)
msgid ""
"<emphasis role=\"Tip\"/>: debugging these scripts it is often useful to view"
" the boot log using <literal>nova console-log &lt;server-id&gt;</literal> to"
" view the progress of boot script execution."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml84(para)
#: ./doc/user-guide/hot/section_software_deployment.xml83(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 "
"<literal>str_replace</literal> intrinsic function:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml106(para)
#: ./doc/user-guide/hot/section_software_deployment.xml105(para)
msgid ""
"<emphasis role=\"Warning\"/>: If a stack-update is performed and there are "
"any changes at all to the content of user_data then the server will be "
@ -7906,14 +7907,14 @@ msgid ""
" be run on a new server."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml111(para)
#: ./doc/user-guide/hot/section_software_deployment.xml110(para)
msgid ""
"When these scripts grow it can become difficult to maintain them inside the "
"template, so the <literal>get_file</literal> intrinsic function can be used "
"to maintain the script in a separate file:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml131(para)
#: ./doc/user-guide/hot/section_software_deployment.xml130(para)
msgid ""
"<emphasis role=\"Tip\"/>: <literal>str_replace</literal> can replace any "
"strings, not just strings starting with <literal>$</literal>. However doing "
@ -7921,11 +7922,11 @@ msgid ""
" for testing by passing in environment variables."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml137(title)
#: ./doc/user-guide/hot/section_software_deployment.xml136(title)
msgid "Choosing the user_data_format"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml138(para)
#: ./doc/user-guide/hot/section_software_deployment.xml137(para)
msgid ""
"The <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> "
@ -7938,7 +7939,7 @@ msgid ""
"be more appropriate."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml144(para)
#: ./doc/user-guide/hot/section_software_deployment.xml143(para)
msgid ""
"For <literal>RAW</literal> the user_data is passed to Nova unmodified. For a"
" <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-"
@ -7946,18 +7947,19 @@ msgid ""
"<literal>RAW</literal> user-data:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml166(para)
#: ./doc/user-guide/hot/section_software_deployment.xml165(para)
msgid ""
"For <literal>SOFTWARE_CONFIG</literal> user_data is bundled as part of the "
"software config data, and metadata is derived from any associated software "
"deployment resources."
"software config data, and metadata is derived from any associated <link "
"linkend=\"software-deployment-resources\">Software deployment "
"resources</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml171(title)
#: ./doc/user-guide/hot/section_software_deployment.xml170(title)
msgid "Signals and wait conditions"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml172(para)
#: ./doc/user-guide/hot/section_software_deployment.xml171(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."
@ -7970,7 +7972,7 @@ msgid ""
" both perform this function using different techniques and tradeoffs."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml178(para)
#: ./doc/user-guide/hot/section_software_deployment.xml177(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -7983,39 +7985,39 @@ msgid ""
"service."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml184(para)
#: ./doc/user-guide/hot/section_software_deployment.xml267(para)
#: ./doc/user-guide/hot/section_software_deployment.xml183(para)
#: ./doc/user-guide/hot/section_software_deployment.xml266(para)
msgid ""
"Sending the signal is a simple HTTP request, as with this example using "
"<link href=\"http://curl.haxx.se/\">curl</link>:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml188(para)
#: ./doc/user-guide/hot/section_software_deployment.xml187(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)
#: ./doc/user-guide/hot/section_software_deployment.xml194(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)
#: ./doc/user-guide/hot/section_software_deployment.xml202(para)
msgid ""
"If <literal>status</literal> is set to <literal>FAILURE</literal> then the "
"resource (and the stack) will go into a <literal>FAILED</literal> state "
"using the <literal>reason</literal> as failure reason."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml205(para)
#: ./doc/user-guide/hot/section_software_deployment.xml204(para)
msgid ""
"The following template example uses the convenience attribute "
"<literal>curl_cli</literal> which builds a curl command with a valid token:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml263(para)
#: ./doc/user-guide/hot/section_software_deployment.xml262(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal>"
@ -8025,13 +8027,13 @@ msgid ""
"used to store multiple signals."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml269(para)
#: ./doc/user-guide/hot/section_software_deployment.xml268(para)
msgid ""
"The above template example only needs to have the <literal>type</literal> "
"changed to the swift signal resources:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml281(para)
#: ./doc/user-guide/hot/section_software_deployment.xml280(para)
msgid ""
"The decision to use <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -8040,14 +8042,14 @@ msgid ""
" will depend on a few factors:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml285(para)
#: ./doc/user-guide/hot/section_software_deployment.xml284(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal>"
" depends on the availability of an Object Storage API"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml289(para)
#: ./doc/user-guide/hot/section_software_deployment.xml288(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal>"
@ -8056,17 +8058,17 @@ msgid ""
"V3 API)."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml294(para)
#: ./doc/user-guide/hot/section_software_deployment.xml293(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)
#: ./doc/user-guide/hot/section_software_deployment.xml299(title)
msgid "Software config resources"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml301(para)
#: ./doc/user-guide/hot/section_software_deployment.xml300(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 "
@ -8078,14 +8080,14 @@ msgid ""
"API calls to create a new config and delete the old one."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml308(para)
#: ./doc/user-guide/hot/section_software_deployment.xml307(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" is used for storing configs represented by text scripts, for example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml326(para)
#: ./doc/user-guide/hot/section_software_deployment.xml325(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal>"
@ -8096,7 +8098,7 @@ msgid ""
"although no further checks for valid cloud-config are done."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml352(para)
#: ./doc/user-guide/hot/section_software_deployment.xml351(para)
msgid ""
"The resource <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__MultipartMime.html\">OS::Heat::MultipartMime</link></literal>"
@ -8109,6 +8111,246 @@ msgid ""
"multi-part message:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml401(para)
msgid ""
"There are many situations where it is not desirable to replace the server "
"whenever there is a configuration change. The <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource allows any number of software configurations to be added or "
"removed from a server throughout its life-cycle."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml406(title)
msgid "Building custom image for software deployments"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml407(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" resources are used to store software configuration, and a <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource is used to associate a config resource with one server. The "
"<literal>group</literal> attribute on <literal><link "
"href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" specifies what tool will consume the config content."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml412(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" has the ability to define a schema of <literal>inputs</literal> and which "
"the configuration script supports. Inputs are mapped to whatever concept the"
" configuration tool has for assigning variables/parameters."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml416(para)
msgid ""
"Likewise, <literal>outputs</literal> are mapped to the tool's capability to "
"export structured data after configuration execution. For tools which do not"
" support this, outputs can always be written to a known file path for the "
"hook to read."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml419(para)
msgid ""
"The <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal>"
" resource allows values to be assigned to the config inputs, and the "
"resource remains in an <literal>IN_PROGRESS</literal> state until the server"
" signals to heat what (if any) output values were generated by the config "
"script."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml425(title)
msgid "Custom image script"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml426(para)
msgid ""
"Each of the following examples requires that the servers be booted with a "
"custom image. The following script uses diskimage-builder to create an image"
" required in later examples:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml471(title)
msgid "Configuring with scripts"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml472(para)
msgid ""
"The <link linkend=\"custom-image-script\">Custom image script</link> already"
" includes the <literal>heat-config-script</literal> element so the built "
"image will already have the ability to configure using shell scripts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml475(para)
msgid ""
"Config inputs are mapped to shell environment variables. The script can "
"communicate outputs to heat by writing to the file "
"<literal>$heat_outputs_path.&lt;output name&gt;</literal>. See the following"
" example for a script which expects inputs <literal>foo</literal>, "
"<literal>bar</literal> and generates an output <literal>result</literal>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml529(para)
msgid ""
"<emphasis role=\"Tip\"/>: A config resource can be associated with multiple "
"deployment resources, and each deployment can specify the same or different "
"values for the <literal>server</literal> and <literal>input_values</literal>"
" properties."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml533(para)
msgid ""
"As can be seen in the <literal>outputs</literal> section of the above "
"template, the <literal>result</literal> config output value is available as "
"an attribute on the <literal>deployment</literal> resource. Likewise the "
"captured stdout, stderr and status_code are also available as attributes."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml539(title)
msgid "Configuring with os-apply-config"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml540(para)
msgid ""
"The agent toolchain of <literal>os-collect-config</literal>, <literal>os-"
"refresh-config</literal> and <literal>os-apply-config</literal> can actually"
" be used on their own to inject heat stack configuration data into a server "
"running a custom image."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml543(para)
msgid "The custom image needs to have the following to use this approach:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml546(para)
msgid "All software dependencies installed"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml549(para)
msgid ""
"<link href=\"https://github.com/openstack/os-refresh-config\">os-refresh-"
"config</link> scripts to be executed on configuration changes"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml552(para)
msgid ""
"<link href=\"https://github.com/openstack/os-apply-config\">os-apply-"
"config</link> templates to transform the heat-provided config data into "
"service configuration files"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml556(para)
msgid ""
"The projects <link href=\"https://github.com/openstack/tripleo-image-"
"elements\">tripleo-image-elements</link> and <link "
"href=\"https://github.com/openstack/tripleo-heat-templates\">tripleo-heat-"
"templates</link> demonstrate this approach."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml560(title)
msgid "Configuring with cfn-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml561(para)
msgid ""
"Likely the only reason to use the <literal>cfn-init</literal> hook is to "
"migrate templates which contain <link "
"href=\"http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-"
"resource-init.html\">AWS::CloudFormation::Init</link> metadata without "
"needing a complete rewrite of the config metadata. It is included here as it"
" introduces a number of new concepts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml565(para)
msgid ""
"To use the <literal>cfn-init</literal> tool the <literal>heat-config-cfn-"
"init</literal> element is required to be on the built image, so <link "
"linkend=\"custom-image-script\">Custom image script</link> needs to be "
"modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml570(para)
msgid ""
"Configuration data which used to be included in the "
"<literal>AWS::CloudFormation::Init</literal> section of resource metadata is"
" instead moved to the <literal>config</literal> property of the config "
"resource, as in the following example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml622(para)
msgid "There are a number of things to note about this template example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml625(para)
msgid ""
"<literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__StructuredConfig.html\">OS::Heat::StructuredConfig</link></literal>"
" is like <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal>"
" except that the <literal>config</literal> property contains structured YAML"
" instead of text script. This is useful for a number of other configuration "
"tools including ansible, salt and os-apply-config."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml632(para)
msgid ""
"<literal>cfn-init</literal> has no concept of inputs, so "
"<literal>{get_input: bar}</literal> acts as a placeholder which gets "
"replaced with the <literal><link href=\"http://docs.openstack.org/hot-"
"reference/content/OS__Heat__StructuredDeployment.html\">OS::Heat::StructuredDeployment</link></literal><literal>input_values</literal>"
" value when the deployment resource is created."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml638(para)
msgid ""
"<literal>cfn-init</literal> has no concept of outputs, so specifying "
"<literal>signal_transport: NO_SIGNAL</literal> will mean that the deployment"
" resource will immediately go into the <literal>CREATED</literal> state "
"instead of waiting for a completed signal from the server."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml644(para)
msgid ""
"The template has 2 deployment resources deploying the same config with "
"different <literal>input_values</literal>. The order these are deployed in "
"on the server is determined by sorting the values of the "
"<literal>name</literal> property for each resource (10_deployment, "
"20_other_deployment)"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml652(title)
msgid "Configuring with puppet"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml653(para)
msgid ""
"The <link href=\"http://puppetlabs.com/\">puppet</link> hook makes it "
"possible to write configuration as puppet manifests which are deployed and "
"run in a masterless environment."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml655(para)
msgid ""
"To specify configuration as puppet manifests the <literal>heat-config-"
"puppet</literal> element is required to be on the built image, so <link "
"linkend=\"custom-image-script\">Custom image script</link> needs to be "
"modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml701(para)
msgid ""
"This demonstrates the use of the <literal>get_file</literal> function, which"
" will attach the contents of the file <literal>example-puppet-"
"manifest.pp</literal>, containing:"
msgstr ""
#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/index.xml10(title)
msgid "HOT guide"

202
doc/user-guide/locale/user-guide.pot

@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2014-12-19 06:14+0000\n"
"POT-Creation-Date: 2014-12-31 06:13+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -5770,11 +5770,11 @@ msgstr ""
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)
#: ./doc/user-guide/hot/section_software_deployment.xml:12(para) ./doc/user-guide/hot/section_software_deployment.xml:58(title)
msgid "User-data boot scripts and cloud-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:15(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:15(para) ./doc/user-guide/hot/section_software_deployment.xml:400(title)
msgid "Software deployment resources"
msgstr ""
@ -5822,130 +5822,262 @@ msgstr ""
msgid "Examples in this guide which require custom images will use <link href=\"https://github.com/openstack/diskimage-builder\">diskimage-builder</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:60(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:59(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 <link href=\"http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html\">Metadata service</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:63(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:62(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 <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:65(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:64(para)
msgid "Whether the image is using <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:79(para)
msgid "<emphasis role=\"Tip\"/>: debugging these scripts it is often useful to view the boot log using <literal>nova console-log &lt;server-id&gt;</literal> to view the progress of boot script execution."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:84(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:83(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 <literal>str_replace</literal> intrinsic function:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:106(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:105(para)
msgid "<emphasis role=\"Warning\"/>: 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:110(para)
msgid "When these scripts grow it can become difficult to maintain them inside the template, so the <literal>get_file</literal> intrinsic function can be used to maintain the script in a separate file:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:131(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:130(para)
msgid "<emphasis role=\"Tip\"/>: <literal>str_replace</literal> can replace any strings, not just strings starting with <literal>$</literal>. 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:136(title)
msgid "Choosing the user_data_format"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:138(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:137(para)
msgid "The <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Nova__Server.html\">OS::Nova::Server</link></literal> user_data_format property determines how the user_data should be formatted for the server. For the default value <literal>HEAT_CFNTOOLS</literal>, the user_data is bundled as part of the heat-cfntools cloud-init boot configuration data. While <literal>HEAT_CFNTOOLS</literal> is the default for <literal>user_data_format</literal>, it is considered legacy and <literal>RAW</literal> or <literal>SOFTWARE_CONFIG</literal> will generally be more appropriate."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:144(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:143(para)
msgid "For <literal>RAW</literal> the user_data is passed to Nova unmodified. For a <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> enabled image, the following are both valid <literal>RAW</literal> user-data:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:166(para)
msgid "For <literal>SOFTWARE_CONFIG</literal> user_data is bundled as part of the software config data, and metadata is derived from any associated software deployment resources."
#: ./doc/user-guide/hot/section_software_deployment.xml:165(para)
msgid "For <literal>SOFTWARE_CONFIG</literal> user_data is bundled as part of the software config data, and metadata is derived from any associated <link linkend=\"software-deployment-resources\">Software deployment resources</link>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:171(title)
#: ./doc/user-guide/hot/section_software_deployment.xml:170(title)
msgid "Signals and wait conditions"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:172(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:171(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 <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> and <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> both perform this function using different techniques and tradeoffs."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:178(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:177(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> is implemented as a call to the <link href=\"http://developer.openstack.org/api-ref-orchestration-v1.html\">Orchestration API</link> 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:183(para) ./doc/user-guide/hot/section_software_deployment.xml:266(para)
msgid "Sending the signal is a simple HTTP request, as with this example using <link href=\"http://curl.haxx.se/\">curl</link>:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:188(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:187(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)
#: ./doc/user-guide/hot/section_software_deployment.xml:194(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)
#: ./doc/user-guide/hot/section_software_deployment.xml:202(para)
msgid "If <literal>status</literal> is set to <literal>FAILURE</literal> then the resource (and the stack) will go into a <literal>FAILED</literal> state using the <literal>reason</literal> as failure reason."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:205(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:204(para)
msgid "The following template example uses the convenience attribute <literal>curl_cli</literal> which builds a curl command with a valid token:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:263(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:262(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:268(para)
msgid "The above template example only needs to have the <literal>type</literal> changed to the swift signal resources:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:281(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:280(para)
msgid "The decision to use <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> or <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> will depend on a few factors:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:285(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:284(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SwiftSignal.html\">OS::Heat::SwiftSignal</link></literal> depends on the availability of an Object Storage API"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:289(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:288(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__WaitCondition.html\">OS::Heat::WaitCondition</link></literal> 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:293(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)
#: ./doc/user-guide/hot/section_software_deployment.xml:299(title)
msgid "Software config resources"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:301(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:300(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 <link href=\"http://developer.openstack.org/api-ref-orchestration-v1.html\">Orchestration API</link>. 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:307(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> is used for storing configs represented by text scripts, for example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:326(para)
#: ./doc/user-guide/hot/section_software_deployment.xml:325(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal> allows <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> 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)
#: ./doc/user-guide/hot/section_software_deployment.xml:351(para)
msgid "The resource <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__MultipartMime.html\">OS::Heat::MultipartMime</link></literal> allows multiple <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> and <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__CloudConfig.html\">OS::Heat::CloudConfig</link></literal> resources to be combined into a single <link href=\"http://cloudinit.readthedocs.org/en/latest/\">Cloud-init</link> multi-part message:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:401(para)
msgid "There are many situations where it is not desirable to replace the server whenever there is a configuration change. The <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal> resource allows any number of software configurations to be added or removed from a server throughout its life-cycle."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:406(title)
msgid "Building custom image for software deployments"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:407(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> resources are used to store software configuration, and a <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal> resource is used to associate a config resource with one server. The <literal>group</literal> attribute on <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> specifies what tool will consume the config content."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:412(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> has the ability to define a schema of <literal>inputs</literal> and which the configuration script supports. Inputs are mapped to whatever concept the configuration tool has for assigning variables/parameters."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:416(para)
msgid "Likewise, <literal>outputs</literal> are mapped to the tool's capability to export structured data after configuration execution. For tools which do not support this, outputs can always be written to a known file path for the hook to read."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:419(para)
msgid "The <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareDeployment.html\">OS::Heat::SoftwareDeployment</link></literal> resource allows values to be assigned to the config inputs, and the resource remains in an <literal>IN_PROGRESS</literal> state until the server signals to heat what (if any) output values were generated by the config script."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:425(title)
msgid "Custom image script"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:426(para)
msgid "Each of the following examples requires that the servers be booted with a custom image. The following script uses diskimage-builder to create an image required in later examples:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:471(title)
msgid "Configuring with scripts"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:472(para)
msgid "The <link linkend=\"custom-image-script\">Custom image script</link> already includes the <literal>heat-config-script</literal> element so the built image will already have the ability to configure using shell scripts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:475(para)
msgid "Config inputs are mapped to shell environment variables. The script can communicate outputs to heat by writing to the file <literal>$heat_outputs_path.&lt;output name&gt;</literal>. See the following example for a script which expects inputs <literal>foo</literal>, <literal>bar</literal> and generates an output <literal>result</literal>."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:529(para)
msgid "<emphasis role=\"Tip\"/>: A config resource can be associated with multiple deployment resources, and each deployment can specify the same or different values for the <literal>server</literal> and <literal>input_values</literal> properties."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:533(para)
msgid "As can be seen in the <literal>outputs</literal> section of the above template, the <literal>result</literal> config output value is available as an attribute on the <literal>deployment</literal> resource. Likewise the captured stdout, stderr and status_code are also available as attributes."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:539(title)
msgid "Configuring with os-apply-config"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:540(para)
msgid "The agent toolchain of <literal>os-collect-config</literal>, <literal>os-refresh-config</literal> and <literal>os-apply-config</literal> can actually be used on their own to inject heat stack configuration data into a server running a custom image."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:543(para)
msgid "The custom image needs to have the following to use this approach:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:546(para)
msgid "All software dependencies installed"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:549(para)
msgid "<link href=\"https://github.com/openstack/os-refresh-config\">os-refresh-config</link> scripts to be executed on configuration changes"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:552(para)
msgid "<link href=\"https://github.com/openstack/os-apply-config\">os-apply-config</link> templates to transform the heat-provided config data into service configuration files"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:556(para)
msgid "The projects <link href=\"https://github.com/openstack/tripleo-image-elements\">tripleo-image-elements</link> and <link href=\"https://github.com/openstack/tripleo-heat-templates\">tripleo-heat-templates</link> demonstrate this approach."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:560(title)
msgid "Configuring with cfn-init"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:561(para)
msgid "Likely the only reason to use the <literal>cfn-init</literal> hook is to migrate templates which contain <link href=\"http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-init.html\">AWS::CloudFormation::Init</link> metadata without needing a complete rewrite of the config metadata. It is included here as it introduces a number of new concepts."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:565(para)
msgid "To use the <literal>cfn-init</literal> tool the <literal>heat-config-cfn-init</literal> element is required to be on the built image, so <link linkend=\"custom-image-script\">Custom image script</link> needs to be modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:570(para)
msgid "Configuration data which used to be included in the <literal>AWS::CloudFormation::Init</literal> section of resource metadata is instead moved to the <literal>config</literal> property of the config resource, as in the following example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:622(para)
msgid "There are a number of things to note about this template example:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:625(para)
msgid "<literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__StructuredConfig.html\">OS::Heat::StructuredConfig</link></literal> is like <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__SoftwareConfig.html\">OS::Heat::SoftwareConfig</link></literal> except that the <literal>config</literal> property contains structured YAML instead of text script. This is useful for a number of other configuration tools including ansible, salt and os-apply-config."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:632(para)
msgid "<literal>cfn-init</literal> has no concept of inputs, so <literal>{get_input: bar}</literal> acts as a placeholder which gets replaced with the <literal><link href=\"http://docs.openstack.org/hot-reference/content/OS__Heat__StructuredDeployment.html\">OS::Heat::StructuredDeployment</link></literal><literal>input_values</literal> value when the deployment resource is created."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:638(para)
msgid "<literal>cfn-init</literal> has no concept of outputs, so specifying <literal>signal_transport: NO_SIGNAL</literal> will mean that the deployment resource will immediately go into the <literal>CREATED</literal> state instead of waiting for a completed signal from the server."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:644(para)
msgid "The template has 2 deployment resources deploying the same config with different <literal>input_values</literal>. The order these are deployed in on the server is determined by sorting the values of the <literal>name</literal> property for each resource (10_deployment, 20_other_deployment)"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:652(title)
msgid "Configuring with puppet"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:653(para)
msgid "The <link href=\"http://puppetlabs.com/\">puppet</link> hook makes it possible to write configuration as puppet manifests which are deployed and run in a masterless environment."
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:655(para)
msgid "To specify configuration as puppet manifests the <literal>heat-config-puppet</literal> element is required to be on the built image, so <link linkend=\"custom-image-script\">Custom image script</link> needs to be modified with the following:"
msgstr ""
#: ./doc/user-guide/hot/section_software_deployment.xml:701(para)
msgid "This demonstrates the use of the <literal>get_file</literal> function, which will attach the contents of the file <literal>example-puppet-manifest.pp</literal>, containing:"
msgstr ""
#. WARNING: This file is automatically generated. Do not edit it.
#: ./doc/user-guide/hot/index.xml:10(title)
msgid "HOT guide"