diff --git a/umn/source/_static/images/en-us_image_0000002010217609.png b/umn/source/_static/images/en-us_image_0000001955571482.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217609.png rename to umn/source/_static/images/en-us_image_0000001955571482.png diff --git a/umn/source/_static/images/en-us_image_0000001973577908.png b/umn/source/_static/images/en-us_image_0000001955571490.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577908.png rename to umn/source/_static/images/en-us_image_0000001955571490.png diff --git a/umn/source/_static/images/en-us_image_0000001973737652.png b/umn/source/_static/images/en-us_image_0000001955571494.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737652.png rename to umn/source/_static/images/en-us_image_0000001955571494.png diff --git a/umn/source/_static/images/en-us_image_0000002010217621.png b/umn/source/_static/images/en-us_image_0000001955571498.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217621.png rename to umn/source/_static/images/en-us_image_0000001955571498.png diff --git a/umn/source/_static/images/en-us_image_0000001955571502.png b/umn/source/_static/images/en-us_image_0000001955571502.png new file mode 100644 index 0000000..0cae059 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001955571502.png differ diff --git a/umn/source/_static/images/en-us_image_0000001973577920.png b/umn/source/_static/images/en-us_image_0000001955571506.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577920.png rename to umn/source/_static/images/en-us_image_0000001955571506.png diff --git a/umn/source/_static/images/en-us_image_0000001955571510.png b/umn/source/_static/images/en-us_image_0000001955571510.png new file mode 100644 index 0000000..53393c8 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001955571510.png differ diff --git a/umn/source/_static/images/en-us_image_0000002010217637.png b/umn/source/_static/images/en-us_image_0000001955571514.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217637.png rename to umn/source/_static/images/en-us_image_0000001955571514.png diff --git a/umn/source/_static/images/en-us_image_0000002010098133.png b/umn/source/_static/images/en-us_image_0000001955571518.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098133.png rename to umn/source/_static/images/en-us_image_0000001955571518.png diff --git a/umn/source/_static/images/en-us_image_0000001955571522.png b/umn/source/_static/images/en-us_image_0000001955571522.png new file mode 100644 index 0000000..678a318 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001955571522.png differ diff --git a/umn/source/_static/images/en-us_image_0000001973737676.png b/umn/source/_static/images/en-us_image_0000001955571526.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737676.png rename to umn/source/_static/images/en-us_image_0000001955571526.png diff --git a/umn/source/_static/images/en-us_image_0000002010217649.png b/umn/source/_static/images/en-us_image_0000001955571530.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217649.png rename to umn/source/_static/images/en-us_image_0000001955571530.png diff --git a/umn/source/_static/images/en-us_image_0000002010098145.png b/umn/source/_static/images/en-us_image_0000001955571534.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098145.png rename to umn/source/_static/images/en-us_image_0000001955571534.png diff --git a/umn/source/_static/images/en-us_image_0000001973577932.png b/umn/source/_static/images/en-us_image_0000001973577932.png deleted file mode 100644 index 03eb286..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973577932.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001973577936.png b/umn/source/_static/images/en-us_image_0000001973577936.png deleted file mode 100644 index 004fe20..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973577936.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001973579160.png b/umn/source/_static/images/en-us_image_0000001973579160.png deleted file mode 100644 index 61207c0..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973579160.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001973737644.png b/umn/source/_static/images/en-us_image_0000001973737644.png deleted file mode 100644 index 32f66d8..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973737644.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001973737664.png b/umn/source/_static/images/en-us_image_0000001973737664.png deleted file mode 100644 index 36b7eed..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973737664.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001973737672.png b/umn/source/_static/images/en-us_image_0000001973737672.png deleted file mode 100644 index cf323f6..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001973737672.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010098105.png b/umn/source/_static/images/en-us_image_0000001991770637.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098105.png rename to umn/source/_static/images/en-us_image_0000001991770637.png diff --git a/umn/source/_static/images/en-us_image_0000001973577904.png b/umn/source/_static/images/en-us_image_0000001991770641.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577904.png rename to umn/source/_static/images/en-us_image_0000001991770641.png diff --git a/umn/source/_static/images/en-us_image_0000001973737648.png b/umn/source/_static/images/en-us_image_0000001991770645.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737648.png rename to umn/source/_static/images/en-us_image_0000001991770645.png diff --git a/umn/source/_static/images/en-us_image_0000002010217617.png b/umn/source/_static/images/en-us_image_0000001991770649.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217617.png rename to umn/source/_static/images/en-us_image_0000001991770649.png diff --git a/umn/source/_static/images/en-us_image_0000002010098117.png b/umn/source/_static/images/en-us_image_0000001991770653.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098117.png rename to umn/source/_static/images/en-us_image_0000001991770653.png diff --git a/umn/source/_static/images/en-us_image_0000001973577916.png b/umn/source/_static/images/en-us_image_0000001991770657.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577916.png rename to umn/source/_static/images/en-us_image_0000001991770657.png diff --git a/umn/source/_static/images/en-us_image_0000001973737660.png b/umn/source/_static/images/en-us_image_0000001991770661.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737660.png rename to umn/source/_static/images/en-us_image_0000001991770661.png diff --git a/umn/source/_static/images/en-us_image_0000001991770665.png b/umn/source/_static/images/en-us_image_0000001991770665.png new file mode 100644 index 0000000..898c9c6 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991770665.png differ diff --git a/umn/source/_static/images/en-us_image_0000002010098129.png b/umn/source/_static/images/en-us_image_0000001991770669.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098129.png rename to umn/source/_static/images/en-us_image_0000001991770669.png diff --git a/umn/source/_static/images/en-us_image_0000001973577928.png b/umn/source/_static/images/en-us_image_0000001991770673.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577928.png rename to umn/source/_static/images/en-us_image_0000001991770673.png diff --git a/umn/source/_static/images/en-us_image_0000001991770677.png b/umn/source/_static/images/en-us_image_0000001991770677.png new file mode 100644 index 0000000..061687e Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991770677.png differ diff --git a/umn/source/_static/images/en-us_image_0000001991770681.png b/umn/source/_static/images/en-us_image_0000001991770681.png new file mode 100644 index 0000000..2f9f786 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991770681.png differ diff --git a/umn/source/_static/images/en-us_image_0000002010098141.png b/umn/source/_static/images/en-us_image_0000001991770685.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010098141.png rename to umn/source/_static/images/en-us_image_0000001991770685.png diff --git a/umn/source/_static/images/en-us_image_0000001973577940.png b/umn/source/_static/images/en-us_image_0000001991770689.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577940.png rename to umn/source/_static/images/en-us_image_0000001991770689.png diff --git a/umn/source/_static/images/en-us_image_0000001973737684.png b/umn/source/_static/images/en-us_image_0000001991770693.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737684.png rename to umn/source/_static/images/en-us_image_0000001991770693.png diff --git a/umn/source/_static/images/en-us_image_0000001991890821.png b/umn/source/_static/images/en-us_image_0000001991890821.png new file mode 100644 index 0000000..8961d4c Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890821.png differ diff --git a/umn/source/_static/images/en-us_image_0000002010217613.png b/umn/source/_static/images/en-us_image_0000001991890825.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217613.png rename to umn/source/_static/images/en-us_image_0000001991890825.png diff --git a/umn/source/_static/images/en-us_image_0000001991890829.png b/umn/source/_static/images/en-us_image_0000001991890829.png new file mode 100644 index 0000000..d19d6dc Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890829.png differ diff --git a/umn/source/_static/images/en-us_image_0000001973577912.png b/umn/source/_static/images/en-us_image_0000001991890833.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577912.png rename to umn/source/_static/images/en-us_image_0000001991890833.png diff --git a/umn/source/_static/images/en-us_image_0000001991890837.png b/umn/source/_static/images/en-us_image_0000001991890837.png new file mode 100644 index 0000000..d19d6dc Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890837.png differ diff --git a/umn/source/_static/images/en-us_image_0000001991890841.png b/umn/source/_static/images/en-us_image_0000001991890841.png new file mode 100644 index 0000000..46a46e7 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890841.png differ diff --git a/umn/source/_static/images/en-us_image_0000001991890845.png b/umn/source/_static/images/en-us_image_0000001991890845.png new file mode 100644 index 0000000..fdf1c92 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890845.png differ diff --git a/umn/source/_static/images/en-us_image_0000001973577924.png b/umn/source/_static/images/en-us_image_0000001991890849.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973577924.png rename to umn/source/_static/images/en-us_image_0000001991890849.png diff --git a/umn/source/_static/images/en-us_image_0000001973737668.png b/umn/source/_static/images/en-us_image_0000001991890853.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737668.png rename to umn/source/_static/images/en-us_image_0000001991890853.png diff --git a/umn/source/_static/images/en-us_image_0000002010217641.png b/umn/source/_static/images/en-us_image_0000001991890857.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217641.png rename to umn/source/_static/images/en-us_image_0000001991890857.png diff --git a/umn/source/_static/images/en-us_image_0000001991890861.png b/umn/source/_static/images/en-us_image_0000001991890861.png new file mode 100644 index 0000000..a22e807 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890861.png differ diff --git a/umn/source/_static/images/en-us_image_0000001991890865.png b/umn/source/_static/images/en-us_image_0000001991890865.png new file mode 100644 index 0000000..aa6128f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001991890865.png differ diff --git a/umn/source/_static/images/en-us_image_0000001973737680.png b/umn/source/_static/images/en-us_image_0000001991890869.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001973737680.png rename to umn/source/_static/images/en-us_image_0000001991890869.png diff --git a/umn/source/_static/images/en-us_image_0000002010217653.png b/umn/source/_static/images/en-us_image_0000001991890873.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000002010217653.png rename to umn/source/_static/images/en-us_image_0000001991890873.png diff --git a/umn/source/_static/images/en-us_image_0000002010098109.png b/umn/source/_static/images/en-us_image_0000002010098109.png deleted file mode 100644 index 0ef3668..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010098109.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010098121.png b/umn/source/_static/images/en-us_image_0000002010098121.png deleted file mode 100644 index 1ae56c9..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010098121.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010098125.png b/umn/source/_static/images/en-us_image_0000002010098125.png deleted file mode 100644 index a039652..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010098125.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010098137.png b/umn/source/_static/images/en-us_image_0000002010098137.png deleted file mode 100644 index 47bc0b2..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010098137.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010217625.png b/umn/source/_static/images/en-us_image_0000002010217625.png deleted file mode 100644 index 92342a3..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010217625.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010217629.png b/umn/source/_static/images/en-us_image_0000002010217629.png deleted file mode 100644 index c301765..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010217629.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010217645.png b/umn/source/_static/images/en-us_image_0000002010217645.png deleted file mode 100644 index e6f78b4..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010217645.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002010219181.png b/umn/source/_static/images/en-us_image_0000002010219181.png deleted file mode 100644 index 61207c0..0000000 Binary files a/umn/source/_static/images/en-us_image_0000002010219181.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000002046583090.png b/umn/source/_static/images/en-us_image_0000002046583090.png new file mode 100644 index 0000000..f603de3 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002046583090.png differ diff --git a/umn/source/_static/images/en-us_image_0000002046741362.png b/umn/source/_static/images/en-us_image_0000002046741362.png new file mode 100644 index 0000000..76f69b6 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002046741362.png differ diff --git a/umn/source/_static/images/en-us_image_0000002046752570.png b/umn/source/_static/images/en-us_image_0000002046752570.png new file mode 100644 index 0000000..cece33a Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002046752570.png differ diff --git a/umn/source/_static/images/en-us_image_0000002046754798.png b/umn/source/_static/images/en-us_image_0000002046754798.png new file mode 100644 index 0000000..38aa3c3 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002046754798.png differ diff --git a/umn/source/_static/images/en-us_image_0000002047112604.png b/umn/source/_static/images/en-us_image_0000002047112604.png new file mode 100644 index 0000000..6319996 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002047112604.png differ diff --git a/umn/source/_static/images/en-us_image_0000002047151338.png b/umn/source/_static/images/en-us_image_0000002047151338.png new file mode 100644 index 0000000..f07bf6a Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002047151338.png differ diff --git a/umn/source/_static/images/en-us_image_0000002082662057.png b/umn/source/_static/images/en-us_image_0000002082662057.png new file mode 100644 index 0000000..6d5e31c Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002082662057.png differ diff --git a/umn/source/_static/images/en-us_image_0000002082672533.png b/umn/source/_static/images/en-us_image_0000002082672533.png new file mode 100644 index 0000000..28df12c Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002082672533.png differ diff --git a/umn/source/_static/images/en-us_image_0000002082673825.png b/umn/source/_static/images/en-us_image_0000002082673825.png new file mode 100644 index 0000000..43ea6fe Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002082673825.png differ diff --git a/umn/source/_static/images/en-us_image_0000002082820613.png b/umn/source/_static/images/en-us_image_0000002082820613.png new file mode 100644 index 0000000..e824e56 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002082820613.png differ diff --git a/umn/source/_static/images/en-us_image_0000002083156329.png b/umn/source/_static/images/en-us_image_0000002083156329.png new file mode 100644 index 0000000..e2b6aa9 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002083156329.png differ diff --git a/umn/source/_static/images/en-us_image_0000002083259861.png b/umn/source/_static/images/en-us_image_0000002083259861.png new file mode 100644 index 0000000..00ade0f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000002083259861.png differ diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst deleted file mode 100644 index 16f98fa..0000000 --- a/umn/source/change_history.rst +++ /dev/null @@ -1,12 +0,0 @@ -:original_name: en-us_topic_0000001980286018.html - -.. _en-us_topic_0000001980286018: - -Change History -============== - -========== ============== -Date Change History -========== ============== -2024-07-30 First release -========== ============== diff --git a/umn/source/conf.py b/umn/source/conf.py index 768dab8..e95a900 100644 --- a/umn/source/conf.py +++ b/umn/source/conf.py @@ -136,4 +136,4 @@ latex_elements = { \newcommand{{\servicetitle}}{{{otcdocs_service_title}}} ''', 'sphinxsetup': 'hmargin={15mm,15mm}, vmargin={20mm,30mm}, marginpar=10mm' -} \ No newline at end of file +} diff --git a/umn/source/index.rst b/umn/source/index.rst index 46f35c8..a671799 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -6,4 +6,3 @@ Resource Formation Service - User Guide :maxdepth: 1 resource_formation_service/index - change_history diff --git a/umn/source/resource_formation_service/auditing/index.rst b/umn/source/resource_formation_service/auditing/index.rst index e45886b..2e92271 100644 --- a/umn/source/resource_formation_service/auditing/index.rst +++ b/umn/source/resource_formation_service/auditing/index.rst @@ -1,12 +1,12 @@ -:original_name: en-us_topic_0000002010098101.html +:original_name: en-us_topic_0000001991890813.html -.. _en-us_topic_0000002010098101: +.. _en-us_topic_0000001991890813: Auditing ======== -- :ref:`RFS Operations Supported by CTS ` -- :ref:`Viewing RFS Logs in CTS ` +- :ref:`RFS Operations Supported by CTS ` +- :ref:`Viewing RFS Logs in CTS ` .. toctree:: :maxdepth: 1 diff --git a/umn/source/resource_formation_service/auditing/rfs_operations_supported_by_cts.rst b/umn/source/resource_formation_service/auditing/rfs_operations_supported_by_cts.rst index b8319eb..a85b3dd 100644 --- a/umn/source/resource_formation_service/auditing/rfs_operations_supported_by_cts.rst +++ b/umn/source/resource_formation_service/auditing/rfs_operations_supported_by_cts.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000002010217605.html +:original_name: en-us_topic_0000001991770633.html -.. _en-us_topic_0000002010217605: +.. _en-us_topic_0000001991770633: RFS Operations Supported by CTS =============================== diff --git a/umn/source/resource_formation_service/auditing/viewing_rfs_logs_in_cts.rst b/umn/source/resource_formation_service/auditing/viewing_rfs_logs_in_cts.rst index bf85d37..49b7e76 100644 --- a/umn/source/resource_formation_service/auditing/viewing_rfs_logs_in_cts.rst +++ b/umn/source/resource_formation_service/auditing/viewing_rfs_logs_in_cts.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973737640.html +:original_name: en-us_topic_0000001955571478.html -.. _en-us_topic_0000001973737640: +.. _en-us_topic_0000001955571478: Viewing RFS Logs in CTS ======================= @@ -66,4 +66,4 @@ Procedure "record_time": 1721141698198 } -.. |image1| image:: /_static/images/en-us_image_0000002010098141.png +.. |image1| image:: /_static/images/en-us_image_0000001991770685.png diff --git a/umn/source/resource_formation_service/getting_started/accessing_resource_formation_service_rfs.rst b/umn/source/resource_formation_service/getting_started/accessing_resource_formation_service_rfs.rst index 60fad66..bb762fa 100644 --- a/umn/source/resource_formation_service/getting_started/accessing_resource_formation_service_rfs.rst +++ b/umn/source/resource_formation_service/getting_started/accessing_resource_formation_service_rfs.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973577888.html +:original_name: en-us_topic_0000001991890801.html -.. _en-us_topic_0000001973577888: +.. _en-us_topic_0000001991890801: Accessing Resource Formation Service (RFS) ========================================== diff --git a/umn/source/resource_formation_service/getting_started/creating_a_stack.rst b/umn/source/resource_formation_service/getting_started/creating_a_stack.rst index 7076904..ac0ce10 100644 --- a/umn/source/resource_formation_service/getting_started/creating_a_stack.rst +++ b/umn/source/resource_formation_service/getting_started/creating_a_stack.rst @@ -1,139 +1,195 @@ -:original_name: en-us_topic_0000002010217597.html +:original_name: en-us_topic_0000001955571466.html -.. _en-us_topic_0000002010217597: +.. _en-us_topic_0000001955571466: Creating a Stack ================ -On the stack list page, click **Create Stack** in the upper right corner, as shown in :ref:`Figure 1 `. +On the stack list page, click **Create Stack** in the upper right corner, as shown in :ref:`Figure 1 `. -.. _en-us_topic_0000002010217597_____d0e536: +.. _en-us_topic_0000001955571466____d0e536: -.. figure:: /_static/images/en-us_image_0000002010098105.png +.. figure:: /_static/images/en-us_image_0000001991770637.png :alt: **Figure 1** Creating a stack **Figure 1** Creating a stack #. Select a template. - There are three ways to select a template, as shown in :ref:`Figure 2 `: (1). Enter a URL of an OBS template. (2). Upload a local template file. (3). Select a template from **My Templates**. + There are three ways to select a template, as shown in :ref:`Figure 2 `: (1). Enter a URL of an OBS template. (2). Upload a local template file. (3). Select a template from **My Templates**. -.. _en-us_topic_0000002010217597_____d0e557: + .. _en-us_topic_0000001955571466____d0e557: -.. figure:: /_static/images/en-us_image_0000002010217609.png - :alt: **Figure 2** Selecting a template + .. figure:: /_static/images/en-us_image_0000001955571482.png + :alt: **Figure 2** Selecting a template - **Figure 2** Selecting a template + **Figure 2** Selecting a template -The following is an example of uploading a local template file. In this example, the **vpc_test.tf.json** file is uploaded. The template content is as follows: + The following is an example of uploading a local template file. In this example, the **ecs_test.tf.json** file is uploaded. The template content is as follows: -{ + { -"terraform": { + "terraform": { -"required_providers": { + "required_providers": { -"opentelekomcloud": { + "opentelekomcloud": { -"source": "opentelekomcloud/provider/opentelekomcloud", + "source": "opentelekomcloud/provider/opentelekomcloud", -"version": "1.36.15" + "version": "1.35.13" -} + } -} + } -}, + }, -"provider": { + "provider": { -"opentelekomcloud": { + "opentelekomcloud": { -"region": "eu-de", + "cloud": "otc", -"insecure": true, + "insecure": true -"auth_url": "https://iam.eu-de.otctest.t-systems.com/v3", + } -"tenant_name": "eu-de", + }, -"domain_name": "{{domain name}}", + "variable": { -"user_name": "{{user name}}" + "vpc_name": { -} + "type": "string", -}, + "description": "vpc name", -"variable": { + "default": "rf_teststack_vpc", -"vpc_name": { + "sensitive": true, -"type": "string", + "nullable": false -"description": "vpc name", + }, -"default": "rf_teststack_vpc", + "subnet_name": { -"nullable": false + "type": "string", -}, + "description": "subnet name", -"subnet_name": { + "default": "rf_teststack_subnet" -"type": "string", + }, -"description": "subnet name", + "ecs_name": { -"default": "rf_teststack_subnet" + "type": "string", -} + "description": "ecs name", -}, + "default": "rf_teststack_ecs" -"resource": { + }, -"opentelekomcloud_vpc_v1": { + "ecs_admin_passwd": { -"rf_doc_vpc": { + "type": "string", -"name": "${var.vpc_name}", + "description": "ecs passwd" -"cidr": "192.168.0.0/16" + } -} + }, -}, + "resource": { -"opentelekomcloud_vpc_subnet_v1": { + "opentelekomcloud_vpc_v1": { -"rf_doc_subnet": { + "rf_doc_vpc": { -"name": "${var.subnet_name}", + "name": "${var.vpc_name}", -"vpc_id": "${opentelekomcloud_vpc_v1.rf_doc_vpc.id}", + "cidr": "192.168.0.0/16" -"cidr": "192.168.1.0/24", + } -"gateway_ip": "192.168.1.1" + }, -} + "opentelekomcloud_vpc_subnet_v1": { -} + "rf_doc_subnet": { -}, + "name": "${var.subnet_name}", -"output": { + "vpc_id": "${opentelekomcloud_vpc_v1.rf_doc_vpc.id}", -"vpc_id": { + "cidr": "192.168.1.0/24", -"value": "${opentelekomcloud_vpc_subnet_v1.rf_doc_vpc.id}" + "gateway_ip": "192.168.1.1" -} + } -} + }, -} + "opentelekomcloud_compute_instance_v2": { + + "rf_doc_ecs": { + + "name": "${var.ecs_name}", + + "flavor_id": "c7.large.2", + + "admin_pass": "${var.ecs_admin_passwd}", + + "image_id": "cecc4bcf-b055-4d35-bd5f-693d4412eaef", + + "network": { + + "uuid": "${opentelekomcloud_vpc_subnet_v1.rf_doc_subnet.id}" + + }, + + "system_disk_type": "SAS", + + "system_disk_size": 100, + + "stop_before_destroy": false, + + "delete_disks_on_termination": true, + + "charging_mode": "postPaid", + + "auto_renew": false + + } + + } + + }, + + "output": { + + "ecs_address": { + + "value": "${opentelekomcloud_compute_instance_v2.rf_doc_ecs.access_ip_v4}", + + "description": "The ecs private address." + + }, + + "ecs_id": { + + "value": "${opentelekomcloud_compute_instance_v2.rf_doc_ecs.id}", + + "description": "The ecs resource id." + + } + + } + + } .. caution:: @@ -145,13 +201,15 @@ The template consists of five parts: #. **opentelekomcloud_vpc_subnet_v1** in **resource** indicates information about a subnet defined in the VPC. A subnet is a segment within the IP address range of the VPC. +#. **opentelekomcloud_compute_instance_v2** in **resource** indicates information about an ECS defined in the template. + #. **variable** indicates variables defined by users in templates during stack creation and deployment. -#. **output** defines the outputs of templates. After a stack is created, its output is generated based on the definition and displayed on the :ref:`Outputs ` tab page. +#. **output** defines the outputs of templates. After a stack is created, its output is generated based on the definition and displayed on the :ref:`Outputs ` tab page. #. Configure parameters. - Click **Next** to go to the parameter configuration page, where you can modify the stack name and description, as shown in :ref:`Figure 3 `. + Click **Next** to go to the parameter configuration page, where you can modify the stack name and description, as shown in :ref:`Figure 3 `. .. caution:: @@ -159,20 +217,20 @@ The template consists of five parts: A stack description can contain a maximum of 1024 characters. -.. _en-us_topic_0000002010217597_____d0e626: +.. _en-us_topic_0000001955571466____d0e626: -.. figure:: /_static/images/en-us_image_0000001973737644.png +.. figure:: /_static/images/en-us_image_0000001991890821.png :alt: **Figure 3** Configuring parameters **Figure 3** Configuring parameters Parameters marked with a red asterisk (``*``) are mandatory. Set these parameters to valid values. -If a value is invalid, the corresponding text box will turn red (as shown in :ref:`Figure 4 `) and page redirection will not be triggered after you click **Next**. +If a value is invalid, the corresponding text box will turn red (as shown in :ref:`Figure 4 `) and page redirection will not be triggered after you click **Next**. -.. _en-us_topic_0000002010217597_____d0e644: +.. _en-us_topic_0000001955571466____d0e644: -.. figure:: /_static/images/en-us_image_0000001973577904.png +.. figure:: /_static/images/en-us_image_0000001991770641.png :alt: **Figure 4** Text box with an invalid value **Figure 4** Text box with an invalid value @@ -181,37 +239,30 @@ Click **Next**. The **Configure Stack** page is displayed. .. caution:: - If the stack name or description is imported using a URL and contains special characters, the characters must be encoded following the HTTP encoding rules first. For example, **test&123** must be converted to **test%26123**, as shown in :ref:`Figure 5 `. (The same verification rules are applied to imported and manually input stack names and descriptions.) + If the stack name or description is imported using a URL and contains special characters, the characters must be encoded following the HTTP encoding rules first. For example, **test&123** must be converted to **test%26123**. (The same verification rules are applied to imported and manually input stack names and descriptions.) -.. _en-us_topic_0000002010217597_____d0e668: - -.. figure:: /_static/images/en-us_image_0000002010098109.png - :alt: **Figure 5** Stack description imported using a URL - - **Figure 5** Stack description imported using a URL - -Check whether the default VPC, subnet names used on this page already exist on the corresponding consoles. If the names already exist, change them to unique ones to prevent creation failures. +Check whether the default VPC, subnet, and ECS names used on this page already exist on the corresponding consoles. If the names already exist, change them to unique ones to prevent creation failures. #. Configure the stack. - Click **Next** to go to the **Advanced Settings** page, as shown in :ref:`Figure 6 `. + Click **Next** to go to the **Advanced Settings** page, as shown in :ref:`Figure 5 `. -.. _en-us_topic_0000002010217597_____d0e688: + .. _en-us_topic_0000001955571466____d0e688: -.. figure:: /_static/images/en-us_image_0000002010217613.png - :alt: **Figure 6** Configuring the stack + .. figure:: /_static/images/en-us_image_0000001991890825.png + :alt: **Figure 5** Configuring the stack - **Figure 6** Configuring the stack + **Figure 5** Configuring the stack -Optional parameters: + Optional parameters: -**IAM Permission Agency**: An agency can clearly define operation permissions of RFS (such as creation, update, and deletion) on stack resources. If the agency permissions are insufficient, subsequent operations may fail. + **IAM Permission Agency**: An agency can clearly define operation permissions of RFS (such as creation, update, and deletion) on stack resources. If the agency permissions are insufficient, subsequent operations may fail. -**Deletion Protection**: prevents the stack from being deleted accidentally. After a stack is created, you can update this configuration by clicking **Update** in the **Operation** column. + **Deletion Protection**: prevents the stack from being deleted accidentally. After a stack is created, you can update this configuration by clicking **Update** in the **Operation** column. -**Auto-Rollback**: If auto-rollback is enabled, the stack automatically rolls back to the previous successful resource status when an operation fails. + **Auto-Rollback**: If auto-rollback is enabled, the stack automatically rolls back to the previous successful resource status when an operation fails. -Click **Next** to go to the **Confirm Configurations** page. + Click **Next** to go to the **Confirm Configurations** page. #. Confirm the configurations. @@ -220,115 +271,116 @@ Click **Next** to go to the **Confirm Configurations** page. a. If you click **Directly Deploy Stack**, a confirmation dialog box will be displayed. - .. figure:: /_static/images/en-us_image_0000001973737648.png - :alt: **Figure 7** Directly deploy stack + .. figure:: /_static/images/en-us_image_0000001991770645.png + :alt: **Figure 6** Directly deploy stack - **Figure 7** Directly deploy stack + **Figure 6** Directly deploy stack - Click **Yes**. A new stack is generated and its status is **Deployment In Progress**, as shown in :ref:`Figure 8 `. + Click **Yes**. A new stack is generated and its status is **Deployment In Progress**, as shown in :ref:`Figure 7 `. - .. _en-us_topic_0000002010217597_____d0e756: + .. _en-us_topic_0000001955571466____d0e756: - .. figure:: /_static/images/en-us_image_0000001973577908.png - :alt: **Figure 8** Deployment in progress + .. figure:: /_static/images/en-us_image_0000001955571490.png + :alt: **Figure 7** Deployment in progress - **Figure 8** Deployment in progress + **Figure 7** Deployment in progress - Then, the status changes to **Deployment Complete**, as shown in :ref:`Figure 9 `. + Then, the status changes to **Deployment Complete**, as shown in :ref:`Figure 8 `. - .. _en-us_topic_0000002010217597_____d0e768: + .. _en-us_topic_0000001955571466____d0e768: - **Figure 9** Deployment complete + .. figure:: /_static/images/en-us_image_0000001991890829.png + :alt: **Figure 8** Deployment complete - |image1| + **Figure 8** Deployment complete - b. If you click **Create Execution Plan**, a dialog box of creating execution plan will be displayed. In this dialog box, you can set the name and description of the execution plan, as shown in :ref:`Figure 10 `. + b. If you click **Create Execution Plan**, a dialog box of creating execution plan will be displayed. In this dialog box, you can set the name and description of the execution plan, as shown in :ref:`Figure 9 `. - .. _en-us_topic_0000002010217597_____d0e780: + .. _en-us_topic_0000001955571466____d0e780: - .. figure:: /_static/images/en-us_image_0000002010217617.png - :alt: **Figure 10** Create Execution Plan dialog box + .. figure:: /_static/images/en-us_image_0000001991770649.png + :alt: **Figure 9** Create Execution Plan dialog box - **Figure 10** Create Execution Plan dialog box + **Figure 9** Create Execution Plan dialog box - Click **OK**. The **Execution Plans** tab page is displayed. Wait until the execution plan is created and refresh the page. The execution plan status changes to **Available**, as shown in :ref:`Figure 11 `. + Click **OK**. The **Execution Plans** tab page is displayed. - .. _en-us_topic_0000002010217597_____d0e800: + Wait until the execution plan is created and refresh the page. The execution plan status changes to **Available**, as shown in :ref:`Figure 10 `. - .. figure:: /_static/images/en-us_image_0000001973737652.png - :alt: **Figure 11** Available + .. _en-us_topic_0000001955571466____d0e800: - **Figure 11** Available + .. figure:: /_static/images/en-us_image_0000001955571494.png + :alt: **Figure 10** Available - Return to the stack list page. The stack status is **Creation Complete**, as shown in :ref:`Figure 12 `. + **Figure 10** Available - .. _en-us_topic_0000002010217597_____d0e813: + Return to the stack list page. The stack status is **Creation Complete**, as shown in :ref:`Figure 11 `. - .. figure:: /_static/images/en-us_image_0000001973577912.png - :alt: **Figure 12** Stack list +.. _en-us_topic_0000001955571466____d0e813: - **Figure 12** Stack list +.. figure:: /_static/images/en-us_image_0000001991890833.png + :alt: **Figure 11** Stack list + + **Figure 11** Stack list .. caution:: **Creating an execution plan** can preview the resource attribute changes of the entire stack and evaluate the impact. If the execution plan meets your expectations, you can execute the plan. Creating an execution plan does not incur fees. The system changes your stack only when you execute the plan. -Click **Deploy** in the **Operation** column of the execution plan to deploy it, as shown in :ref:`Figure 13 `. +Click **Deploy** in the **Operation** column of the execution plan to deploy it, as shown in :ref:`Figure 12 `. -.. _en-us_topic_0000002010217597_____d0e835: +.. _en-us_topic_0000001955571466____d0e835: -.. figure:: /_static/images/en-us_image_0000002010098117.png - :alt: **Figure 13** Execution plan dialog box +.. figure:: /_static/images/en-us_image_0000001991770653.png + :alt: **Figure 12** Execution plan dialog box - **Figure 13** Execution plan dialog box + **Figure 12** Execution plan dialog box -In the **Execution Plan** dialog box, click **Execute**. A message indicating that the execution plan is being deployed is displayed in the upper right corner. Return to the stack list page. A new stack is generated and its status is **Deployment In Progress**, as shown in :ref:`Figure 14 `. +In the **Execution Plan** dialog box, click **Execute**. A message indicating that the execution plan is being deployed is displayed in the upper right corner. Return to the stack list page. A new stack is generated and its status is **Deployment In Progress**, as shown in :ref:`Figure 13 `. -.. _en-us_topic_0000002010217597_____d0e853: +.. _en-us_topic_0000001955571466____d0e853: -.. figure:: /_static/images/en-us_image_0000002010217621.png - :alt: **Figure 14** Deployment in progress +.. figure:: /_static/images/en-us_image_0000001955571498.png + :alt: **Figure 13** Deployment in progress - **Figure 14** Deployment in progress + **Figure 13** Deployment in progress -Then, the stack status changes to **Deployment Complete**, as shown in :ref:`Figure 15 `. +Then, the stack status changes to **Deployment Complete**, as shown in :ref:`Figure 14 `. -.. _en-us_topic_0000002010217597_____d0e866: +.. _en-us_topic_0000001955571466____d0e866: -**Figure 15** Deployment complete +.. figure:: /_static/images/en-us_image_0000001991890837.png + :alt: **Figure 14** Deployment complete -|image2| + **Figure 14** Deployment complete -On the **Execution Plans** tab page of the stack details page, the execution plan status is **Applied**, as shown in :ref:`Figure 16 `. +On the **Execution Plans** tab page of the stack details page, the execution plan status is **Applied**, as shown in :ref:`Figure 15 `. -.. _en-us_topic_0000002010217597_____d0e882: +.. _en-us_topic_0000001955571466____d0e882: -.. figure:: /_static/images/en-us_image_0000001973577916.png - :alt: **Figure 16** Applied +.. figure:: /_static/images/en-us_image_0000001991770657.png + :alt: **Figure 15** Applied - **Figure 16** Applied + **Figure 15** Applied -Click the **Events** tab. The event list shows that resources of the stack are deployed, as shown in :ref:`Figure 17 `. +Click the **Events** tab. The event list shows that resources of the stack are deployed, as shown in :ref:`Figure 16 `. -.. _en-us_topic_0000002010217597_____d0e895: +.. _en-us_topic_0000001955571466____d0e895: -.. figure:: /_static/images/en-us_image_0000002010098121.png - :alt: **Figure 17** Resources deployed +.. figure:: /_static/images/en-us_image_0000001955571502.png + :alt: **Figure 16** Resources deployed - **Figure 17** Resources deployed + **Figure 16** Resources deployed You can view details on the console of the corresponding cloud service. -#. In the service list, locate and click **Virtual Private Cloud**. On the displayed page, view the deployed VPC, as shown in :ref:`Figure 18 `. +#. In the service list, locate and click **Elastic Cloud Server**. On the displayed page, view the deployed ECS, as shown in :ref:`Figure 17 `. - .. _en-us_topic_0000002010217597_____d0e912: + .. _en-us_topic_0000001955571466____d0e912: - .. figure:: /_static/images/en-us_image_0000002010217625.png - :alt: **Figure 18** VPC + .. figure:: /_static/images/en-us_image_0000001991890841.png + :alt: **Figure 17** ECS - **Figure 18** VPC + **Figure 17** ECS Resources of the stack are deployed. - -.. |image1| image:: /_static/images/en-us_image_0000001973579160.png -.. |image2| image:: /_static/images/en-us_image_0000002010219181.png diff --git a/umn/source/resource_formation_service/getting_started/creating_an_execution_plan.rst b/umn/source/resource_formation_service/getting_started/creating_an_execution_plan.rst index 51f8bc0..b13c235 100644 --- a/umn/source/resource_formation_service/getting_started/creating_an_execution_plan.rst +++ b/umn/source/resource_formation_service/getting_started/creating_an_execution_plan.rst @@ -1,37 +1,37 @@ -:original_name: en-us_topic_0000002010098097.html +:original_name: en-us_topic_0000001955571470.html -.. _en-us_topic_0000002010098097: +.. _en-us_topic_0000001955571470: Creating an Execution Plan ========================== -On the stack list page, click the name of the stack to go to its details page. Click **Update Template/Parameter** in the upper right corner to go to the page for creating an execution plan, as shown in :ref:`Figure 1 `. +On the stack list page, click the name of the stack to go to its details page. Click **Update Template/Parameter** in the upper right corner to go to the page for creating an execution plan, as shown in :ref:`Figure 1 `. -.. _en-us_topic_0000002010098097_____d0e1116: +.. _en-us_topic_0000001955571470____d0e1116: -.. figure:: /_static/images/en-us_image_0000001973577924.png +.. figure:: /_static/images/en-us_image_0000001991890849.png :alt: **Figure 1** Page for creating an execution plan **Figure 1** Page for creating an execution plan The subsequent steps are the same as those for creating a stack, except for one difference that you need to click **Create Execution Plan** instead of **Directly Deploy Stack**. -Then, an execution plan is generated, but the stack is not directly deployed. If you create multiple execution plans, they will exist in the same stack, as shown in :ref:`Figure 2 `. +Then, an execution plan is generated, but the stack is not directly deployed. If you create multiple execution plans, they will exist in the same stack, as shown in :ref:`Figure 2 `. -.. _en-us_topic_0000002010098097_____d0e1136: +.. _en-us_topic_0000001955571470____d0e1136: -.. figure:: /_static/images/en-us_image_0000002010098129.png +.. figure:: /_static/images/en-us_image_0000001991770669.png :alt: **Figure 2** Execution plan list **Figure 2** Execution plan list Locate the row that contains the generated execution plan and click **Deploy** in the **Operation** column if you want to deploy tour execution plan. -If an execution plan is no longer used, click **Delete** in the **Operation** column. Click **OK** in the dialog box displayed, as shown in :ref:`Figure 3 `. +If an execution plan is no longer used, click **Delete** in the **Operation** column. Click **OK** in the dialog box displayed, as shown in :ref:`Figure 3 `. -.. _en-us_topic_0000002010098097_____d0e1163: +.. _en-us_topic_0000001955571470____d0e1163: -.. figure:: /_static/images/en-us_image_0000002010217637.png +.. figure:: /_static/images/en-us_image_0000001955571514.png :alt: **Figure 3** Deleting an execution plan **Figure 3** Deleting an execution plan diff --git a/umn/source/resource_formation_service/getting_started/deleting_a_stack.rst b/umn/source/resource_formation_service/getting_started/deleting_a_stack.rst index e3ce78b..0fa4691 100644 --- a/umn/source/resource_formation_service/getting_started/deleting_a_stack.rst +++ b/umn/source/resource_formation_service/getting_started/deleting_a_stack.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000002010217601.html +:original_name: en-us_topic_0000001991890809.html -.. _en-us_topic_0000002010217601: +.. _en-us_topic_0000001991890809: Deleting a Stack ================ @@ -9,31 +9,31 @@ Deleting a Stack On the stack list page, locate the created stack and click **Delete** in the **Operation** column. In the dialog box displayed, enter **Delete** in the text box and click **OK**. -Alternatively, go to the stack details page and click **Delete** in the upper right corner, as shown in :ref:`Figure 1 `. +Alternatively, go to the stack details page and click **Delete** in the upper right corner, as shown in :ref:`Figure 1 `. -.. _en-us_topic_0000002010217601_____d0e1485: +.. _en-us_topic_0000001991890809____d0e1485: -.. figure:: /_static/images/en-us_image_0000001973737668.png +.. figure:: /_static/images/en-us_image_0000001991890853.png :alt: **Figure 1** Dialog box for deleting a stack **Figure 1** Dialog box for deleting a stack 2. When **Deletion Protection** is enabled: -:ref:`Figure 2 ` shows that the **Enabled** status of **Deletion Protection**. +:ref:`Figure 2 ` shows that the **Enabled** status of **Deletion Protection**. -.. _en-us_topic_0000002010217601_____d0e1504: +.. _en-us_topic_0000001991890809____d0e1504: -.. figure:: /_static/images/en-us_image_0000001973577928.png +.. figure:: /_static/images/en-us_image_0000001991770673.png :alt: **Figure 2** Deletion protection **Figure 2** Deletion protection -If you delete a resource stack with deletion protection enabled, an error message will be displayed, as shown in :ref:`Figure 3 `. +If you delete a resource stack with deletion protection enabled, an error message will be displayed, as shown in :ref:`Figure 3 `. -.. _en-us_topic_0000002010217601_____d0e1513: +.. _en-us_topic_0000001991890809____d0e1513: -.. figure:: /_static/images/en-us_image_0000002010098133.png +.. figure:: /_static/images/en-us_image_0000001955571518.png :alt: **Figure 3** Deletion failed **Figure 3** Deletion failed diff --git a/umn/source/resource_formation_service/getting_started/index.rst b/umn/source/resource_formation_service/getting_started/index.rst index 8a95092..21c1b96 100644 --- a/umn/source/resource_formation_service/getting_started/index.rst +++ b/umn/source/resource_formation_service/getting_started/index.rst @@ -1,18 +1,18 @@ -:original_name: en-us_topic_0000001973737624.html +:original_name: en-us_topic_0000001955571462.html -.. _en-us_topic_0000001973737624: +.. _en-us_topic_0000001955571462: Getting Started =============== -- :ref:`Accessing Resource Formation Service (RFS) ` -- :ref:`Viewing the Stack Status ` -- :ref:`Creating a Stack ` -- :ref:`Querying a Stack ` -- :ref:`Updating a Template or Parameter ` -- :ref:`Creating an Execution Plan ` -- :ref:`Deleting a Stack ` -- :ref:`Viewing Stack Details ` +- :ref:`Accessing Resource Formation Service (RFS) ` +- :ref:`Viewing the Stack Status ` +- :ref:`Creating a Stack ` +- :ref:`Querying a Stack ` +- :ref:`Updating a Template or Parameter ` +- :ref:`Creating an Execution Plan ` +- :ref:`Deleting a Stack ` +- :ref:`Viewing Stack Details ` .. toctree:: :maxdepth: 1 diff --git a/umn/source/resource_formation_service/getting_started/querying_a_stack.rst b/umn/source/resource_formation_service/getting_started/querying_a_stack.rst index 6d6fee0..1684cd9 100644 --- a/umn/source/resource_formation_service/getting_started/querying_a_stack.rst +++ b/umn/source/resource_formation_service/getting_started/querying_a_stack.rst @@ -1,17 +1,17 @@ -:original_name: en-us_topic_0000001973737632.html +:original_name: en-us_topic_0000001991890805.html -.. _en-us_topic_0000001973737632: +.. _en-us_topic_0000001991890805: Querying a Stack ================ Log in to the RFS console and click **Stacks** in the navigation pane on the left. The stack list page is displayed. -In the search box above the stack list, enter the name of the target stack and click the search button, as shown in :ref:`Figure 1 `. +In the search box above the stack list, enter the name of the target stack and click the search button, as shown in :ref:`Figure 1 `. -.. _en-us_topic_0000001973737632_____d0e956: +.. _en-us_topic_0000001991890805____d0e956: -.. figure:: /_static/images/en-us_image_0000001973737660.png +.. figure:: /_static/images/en-us_image_0000001991770661.png :alt: **Figure 1** Querying a stack **Figure 1** Querying a stack diff --git a/umn/source/resource_formation_service/getting_started/updating_a_template_or_parameter.rst b/umn/source/resource_formation_service/getting_started/updating_a_template_or_parameter.rst index 8598145..001ca49 100644 --- a/umn/source/resource_formation_service/getting_started/updating_a_template_or_parameter.rst +++ b/umn/source/resource_formation_service/getting_started/updating_a_template_or_parameter.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973577892.html +:original_name: en-us_topic_0000001991770625.html -.. _en-us_topic_0000001973577892: +.. _en-us_topic_0000001991770625: Updating a Template or Parameter ================================ @@ -9,11 +9,11 @@ Updating a Template or Parameter Stack change records are not available. If you want to view change details, you are recommended to create an execution plan. -You can add cloud service resources or change resource specifications in either of the following ways: Go to the stack list page, locate the target stack, and click **Update** in the **Operation** column. Alternatively, go to the stack details page and click **Update Template/Parameter** in the upper right corner to enter the page for updating the resource stack, as shown in :ref:`Figure 1 `. +You can add cloud service resources or change resource specifications in either of the following ways: Go to the stack list page, locate the target stack, and click **Update** in the **Operation** column. Alternatively, go to the stack details page and click **Update Template/Parameter** in the upper right corner to enter the page for updating the resource stack, as shown in :ref:`Figure 1 `. -.. _en-us_topic_0000001973577892_____d0e1006: +.. _en-us_topic_0000001991770625____d0e1006: -.. figure:: /_static/images/en-us_image_0000001973577920.png +.. figure:: /_static/images/en-us_image_0000001955571506.png :alt: **Figure 1** Selecting a template **Figure 1** Selecting a template @@ -22,33 +22,33 @@ You can select **Current Template** or **Replace Current Template** (use a new t Solution 1: Using the current template -#. Click **Next** to go to the **Configure Parameters** page and modify parameters on it, as shown in :ref:`Figure 2 `. +#. Click **Next** to go to the **Configure Parameters** page and modify parameters on it, as shown in :ref:`Figure 2 `. -.. _en-us_topic_0000001973577892_____d0e1035: +.. _en-us_topic_0000001991770625____d0e1035: -.. figure:: /_static/images/en-us_image_0000002010098125.png +.. figure:: /_static/images/en-us_image_0000001991890845.png :alt: **Figure 2** Configuring parameters **Figure 2** Configuring parameters -#. Click **Next** to go to the **Confirm Configurations** page, as shown in :ref:`Figure 3 `. +#. Click **Next** to go to the **Confirm Configurations** page, as shown in :ref:`Figure 3 `. -.. _en-us_topic_0000001973577892_____d0e1051: +.. _en-us_topic_0000001991770625____d0e1051: -.. figure:: /_static/images/en-us_image_0000002010217629.png +.. figure:: /_static/images/en-us_image_0000001991770665.png :alt: **Figure 3** Confirming configurations **Figure 3** Confirming configurations #. Click **Directly Deploy Stack**. The **Events** page is displayed. - The status changes to **Update Complete**, as shown in :ref:`Figure 4 `. + The status changes to **Update Complete**, as shown in :ref:`Figure 4 `. - .. _en-us_topic_0000001973577892_____d0e1072: + .. _en-us_topic_0000001991770625____d0e1072: - .. figure:: /_static/images/en-us_image_0000001973737664.png + .. figure:: /_static/images/en-us_image_0000001955571510.png :alt: **Figure 4** Update complete **Figure 4** Update complete -Solution 2: Replacing the current template (see :ref:`Creating a Stack `) +Solution 2: Replacing the current template (see :ref:`Creating a Stack `) diff --git a/umn/source/resource_formation_service/getting_started/viewing_stack_details.rst b/umn/source/resource_formation_service/getting_started/viewing_stack_details.rst index 839f23e..733b6fa 100644 --- a/umn/source/resource_formation_service/getting_started/viewing_stack_details.rst +++ b/umn/source/resource_formation_service/getting_started/viewing_stack_details.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973737636.html +:original_name: en-us_topic_0000001991770629.html -.. _en-us_topic_0000001973737636: +.. _en-us_topic_0000001991770629: Viewing Stack Details ===================== @@ -9,67 +9,67 @@ Viewing Stack Details There are six function modules on the stack details page (The stack named **stack_20240428_1517_39wa** is an example here.): - a. **Basic Information**: displays basic information about the stack, as shown in :ref:`Figure 1 `. + a. **Basic Information**: displays basic information about the stack, as shown in :ref:`Figure 1 `. - .. _en-us_topic_0000001973737636_____d0e1560: +.. _en-us_topic_0000001991770629____d0e1560: - .. figure:: /_static/images/en-us_image_0000002010217641.png - :alt: **Figure 1** Basic information +.. figure:: /_static/images/en-us_image_0000001991890857.png + :alt: **Figure 1** Basic information - **Figure 1** Basic information + **Figure 1** Basic information - b. **Resources**: displays information about cloud services or resources generated during plan execution and stack deployment, as shown in :ref:`Figure 2 `. +#. **Resources**: displays information about cloud services or resources generated during plan execution and stack deployment, as shown in :ref:`Figure 2 `. - .. _en-us_topic_0000001973737636_____d0e1571: + .. _en-us_topic_0000001991770629____d0e1571: - .. figure:: /_static/images/en-us_image_0000001973737672.png - :alt: **Figure 2** Resources + .. figure:: /_static/images/en-us_image_0000001991770677.png + :alt: **Figure 2** Resources - **Figure 2** Resources + **Figure 2** Resources - c. **Events**: displays log information generated during plan execution and stack deployment. Events are updated in real time based on the stack status. For example, :ref:`Figure 3 ` shows that three resources are created. +#. **Events**: displays log information generated during plan execution and stack deployment. Events are updated in real time based on the stack status. For example, :ref:`Figure 3 ` shows that three resources are created. - .. _en-us_topic_0000001973737636_____d0e1583: + .. _en-us_topic_0000001991770629____d0e1583: - .. figure:: /_static/images/en-us_image_0000001973577932.png - :alt: **Figure 3** Events + .. figure:: /_static/images/en-us_image_0000001955571522.png + :alt: **Figure 3** Events - **Figure 3** Events + **Figure 3** Events - d. .. _en-us_topic_0000001973737636__d0e1588: +#. .. _en-us_topic_0000001991770629__d0e1588: - **Outputs**: displays output parameters in the template, as shown in :ref:`Figure 4 `: + **Outputs**: displays output parameters in the template, as shown in :ref:`Figure 4 `: - .. _en-us_topic_0000001973737636_____d0e1595: + .. _en-us_topic_0000001991770629____d0e1595: - .. figure:: /_static/images/en-us_image_0000002010098137.png - :alt: **Figure 4** Outputs + .. figure:: /_static/images/en-us_image_0000001991890861.png + :alt: **Figure 4** Outputs - **Figure 4** Outputs + **Figure 4** Outputs - e. **Template**: displays the template content used for creating a stack, as shown in :ref:`Figure 5 `. +#. **Template**: displays the template content used for creating a stack, as shown in :ref:`Figure 5 `. - .. _en-us_topic_0000001973737636_____d0e1606: + .. _en-us_topic_0000001991770629____d0e1606: - .. figure:: /_static/images/en-us_image_0000002010217645.png - :alt: **Figure 5** Template + .. figure:: /_static/images/en-us_image_0000001991770681.png + :alt: **Figure 5** Template - **Figure 5** Template + **Figure 5** Template - f. **Execution Plans**: displays different execution plans. After an execution plan is generated, you need to click **Deploy** to create resources in the template. After an execution plan is executed, its status changes from **Available** to **Applied** and the **Deploy** button disappears, as shown in :ref:`Figure 6 `. +#. **Execution Plans**: displays different execution plans. After an execution plan is generated, you need to click **Deploy** to create resources in the template. After an execution plan is executed, its status changes from **Available** to **Applied** and the **Deploy** button disappears, as shown in :ref:`Figure 6 `. - .. _en-us_topic_0000001973737636_____d0e1629: + .. _en-us_topic_0000001991770629____d0e1629: - .. figure:: /_static/images/en-us_image_0000001973737676.png - :alt: **Figure 6** Execution plans + .. figure:: /_static/images/en-us_image_0000001955571526.png + :alt: **Figure 6** Execution plans - **Figure 6** Execution plans + **Figure 6** Execution plans - Click the execution plan name. The execution plan details page is displayed, as shown in :ref:`Figure 7 `. + Click the execution plan name. The execution plan details page is displayed, as shown in :ref:`Figure 7 `. - .. _en-us_topic_0000001973737636_____d0e1639: + .. _en-us_topic_0000001991770629____d0e1639: - .. figure:: /_static/images/en-us_image_0000001973577936.png - :alt: **Figure 7** Execution plan details + .. figure:: /_static/images/en-us_image_0000001991890865.png + :alt: **Figure 7** Execution plan details - **Figure 7** Execution plan details + **Figure 7** Execution plan details diff --git a/umn/source/resource_formation_service/getting_started/viewing_the_stack_status.rst b/umn/source/resource_formation_service/getting_started/viewing_the_stack_status.rst index de38ace..7587668 100644 --- a/umn/source/resource_formation_service/getting_started/viewing_the_stack_status.rst +++ b/umn/source/resource_formation_service/getting_started/viewing_the_stack_status.rst @@ -1,17 +1,17 @@ -:original_name: en-us_topic_0000002010098093.html +:original_name: en-us_topic_0000001991770621.html -.. _en-us_topic_0000002010098093: +.. _en-us_topic_0000001991770621: Viewing the Stack Status ======================== You can manage stack lifecycle (such as creation, update, deletion, and query) and the lifecycle of execution plans of a stack (such as creation, deletion, and query). -:ref:`Table 1 ` describes stack statuses. +:ref:`Table 1 ` describes stack statuses. -:ref:`Table 2 ` describes execution plan statuses. +:ref:`Table 2 ` describes execution plan statuses. -.. _en-us_topic_0000002010098093_____d0e380: +.. _en-us_topic_0000001991770621____d0e380: .. table:: **Table 1** Stack statuses @@ -29,7 +29,7 @@ You can manage stack lifecycle (such as creation, update, deletion, and query) a Rollback Complete The stack has been rolled back. ====================== ============================================ -.. _en-us_topic_0000002010098093_____d0e458: +.. _en-us_topic_0000001991770621____d0e458: .. table:: **Table 2** Execution plan statuses diff --git a/umn/source/resource_formation_service/iam_agency.rst b/umn/source/resource_formation_service/iam_agency.rst index 0108388..340fbb2 100644 --- a/umn/source/resource_formation_service/iam_agency.rst +++ b/umn/source/resource_formation_service/iam_agency.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973577900.html +:original_name: en-us_topic_0000001991890817.html -.. _en-us_topic_0000001973577900: +.. _en-us_topic_0000001991890817: IAM Agency ========== @@ -17,15 +17,17 @@ RFS uses an agency only in resource operation requests, such as creating a stack #. On the IAM console, choose **Agencies** from the navigation pane on the left, and click **Create Agency** in the upper right corner. -.. figure:: /_static/images/en-us_image_0000002010217649.png +.. figure:: /_static/images/en-us_image_0000001955571530.png :alt: **Figure 1** Creating an agency **Figure 1** Creating an agency -#. Enter an agency name.Set **Cloud Service** to **RFS**. +#. Enter an agency name. + + Set **Cloud Service** to **RFS**. - .. figure:: /_static/images/en-us_image_0000001973737680.png + .. figure:: /_static/images/en-us_image_0000001991890869.png :alt: **Figure 2** Creating an agency **Figure 2** Creating an agency @@ -36,34 +38,34 @@ RFS uses an agency only in resource operation requests, such as creating a stack If **op_svc_iac** has been used for registration, you are advised to change it to **RFS**. -2. Click **Next**. The **Authorize Agency** page is displayed. You can grant permissions to the agency on this page. +#. Click **Next**. The **Authorize Agency** page is displayed. You can grant permissions to the agency on this page. -.. figure:: /_static/images/en-us_image_0000001973577940.png +.. figure:: /_static/images/en-us_image_0000001991770689.png :alt: **Figure 3** Agency authorization **Figure 3** Agency authorization -3. Filter specific permissions and grant them to the agency. +#. Filter specific permissions and grant them to the agency. -.. figure:: /_static/images/en-us_image_0000002010098145.png +.. figure:: /_static/images/en-us_image_0000001955571534.png :alt: **Figure 4** Selecting policies **Figure 4** Selecting policies You can determine the permissions to be granted to an agency. OpenTelekom cloud best practices do not advise you to automatically create agencies with the Tenant Administrator permission for users. The best practice is to grant management permissions (including read and write operations) to resources that may be used in a stack. -4. Set the authorization scope. You can select **All resources** or **Region-specific projects**. +#. Set the authorization scope. You can select **All resources** or **Region-specific projects**. -.. figure:: /_static/images/en-us_image_0000002010217653.png +.. figure:: /_static/images/en-us_image_0000001991890873.png :alt: **Figure 5** Authorization scope **Figure 5** Authorization scope -5. Click **OK**. The agency is created. +#. Click **OK**. The agency is created. -|image1| + |image1| -.. |image1| image:: /_static/images/en-us_image_0000001973737684.png +.. |image1| image:: /_static/images/en-us_image_0000001991770693.png diff --git a/umn/source/resource_formation_service/index.rst b/umn/source/resource_formation_service/index.rst index 8ff7ecd..f53fde8 100644 --- a/umn/source/resource_formation_service/index.rst +++ b/umn/source/resource_formation_service/index.rst @@ -1,40 +1,25 @@ -:original_name: en-us_topic_0000002010217593.html +:original_name: en-us_topic_0000001991770617.html -.. _en-us_topic_0000002010217593: +.. _en-us_topic_0000001991770617: Resource Formation Service ========================== -:ref:`Getting Started ` +:ref:`Getting Started ` -:ref:`Managing a Stack ` +:ref:`Managing a Stack ` -:ref:`Managing a Stack ` +:ref:`Managing a Template ` -:ref:`Auditing ` +:ref:`Auditing ` -:ref:`IAM Agency ` +:ref:`IAM Agency ` -:ref:`Getting Started ` - -:ref:`Managing a Stack ` - -:ref:`Auditing ` - -:ref:`IAM Agency ` - -:ref:`Getting Started ` - -:ref:`Managing a Stack ` - -:ref:`Auditing ` - -:ref:`IAM Agency ` - -- :ref:`Getting Started ` -- :ref:`Managing a Stack ` -- :ref:`Auditing ` -- :ref:`IAM Agency ` +- :ref:`Getting Started ` +- :ref:`Managing a Stack ` +- :ref:`Managing a Template ` +- :ref:`Auditing ` +- :ref:`IAM Agency ` .. toctree:: :maxdepth: 1 @@ -42,5 +27,6 @@ Resource Formation Service getting_started/index managing_a_stack + managing_a_template/index auditing/index iam_agency diff --git a/umn/source/resource_formation_service/managing_a_stack.rst b/umn/source/resource_formation_service/managing_a_stack.rst index 20d60eb..0bc99ac 100644 --- a/umn/source/resource_formation_service/managing_a_stack.rst +++ b/umn/source/resource_formation_service/managing_a_stack.rst @@ -1,6 +1,6 @@ -:original_name: en-us_topic_0000001973577896.html +:original_name: en-us_topic_0000001955571474.html -.. _en-us_topic_0000001973577896: +.. _en-us_topic_0000001955571474: Managing a Stack ================ diff --git a/umn/source/resource_formation_service/managing_a_template/creating_a_stack.rst b/umn/source/resource_formation_service/managing_a_template/creating_a_stack.rst new file mode 100644 index 0000000..fdf6053 --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/creating_a_stack.rst @@ -0,0 +1,27 @@ +:original_name: en-us_topic_0000002046584002.html + +.. _en-us_topic_0000002046584002: + +Creating a Stack +================ + +RFS supports linkage between the stack and the template in console. Users can directly select templates to create and deploy a stack. Click **Create Stack** under **Operation** column as shown in :ref:`Figure 1 `. + +.. _en-us_topic_0000002046584002____d0e1006: + +**Figure 1** Creating Stack + +|image1| + +Next, the console will then automatically jump to the creation stack and select the latest version of the current template by default as shown in :ref:`Figure 2 `. + +.. _en-us_topic_0000002046584002__fig14609152010154: + +**Figure 2** Selecting Template + +|image2| + +Next, click **Next** to continue to create stack. + +.. |image1| image:: /_static/images/en-us_image_0000002047112604.png +.. |image2| image:: /_static/images/en-us_image_0000002083156329.png diff --git a/umn/source/resource_formation_service/managing_a_template/creating_a_template.rst b/umn/source/resource_formation_service/managing_a_template/creating_a_template.rst new file mode 100644 index 0000000..7030a5e --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/creating_a_template.rst @@ -0,0 +1,229 @@ +:original_name: en-us_topic_0000002046740822.html + +.. _en-us_topic_0000002046740822: + +Creating a Template +=================== + +On the template page, click **Create Template** in the upper right corner, as shown in :ref:`Figure 1 `. + +.. _en-us_topic_0000002046740822____d0e536: + +.. figure:: /_static/images/en-us_image_0000002046583090.png + :alt: **Figure 1** Creating a template + + **Figure 1** Creating a template + +#. Select a template. + + There are three ways to select a template, as shown in :ref:`Figure 2 `: (1). Enter a URL of an OBS template. (2). Upload a local template file. (3). Input templatge. + + .. _en-us_topic_0000002046740822____d0e557: + + **Figure 2** Selecting a template + + |image1| + + The following is an example of uploading a local template file. In this example, the **ecs_test.tf.json** file is uploaded. The template content is as follows: + + { + + "terraform": { + + "required_providers": { + + "opentelekomcloud": { + + "source": "opentelekomcloud/provider/opentelekomcloud", + + "version": "1.35.13" + + } + + } + + }, + + "provider": { + + "opentelekomcloud": { + + "cloud": "otc", + + "insecure": true + + } + + }, + + "variable": { + + "vpc_name": { + + "type": "string", + + "description": "vpc name", + + "default": "rf_teststack_vpc", + + "sensitive": true, + + "nullable": false + + }, + + "subnet_name": { + + "type": "string", + + "description": "subnet name", + + "default": "rf_teststack_subnet" + + }, + + "ecs_name": { + + "type": "string", + + "description": "ecs name", + + "default": "rf_teststack_ecs" + + }, + + "ecs_admin_passwd": { + + "type": "string", + + "description": "ecs passwd" + + } + + }, + + "resource": { + + "opentelekomcloud_vpc_v1": { + + "rf_doc_vpc": { + + "name": "${var.vpc_name}", + + "cidr": "192.168.0.0/16" + + } + + }, + + "opentelekomcloud_vpc_subnet_v1": { + + "rf_doc_subnet": { + + "name": "${var.subnet_name}", + + "vpc_id": "${opentelekomcloud_vpc_v1.rf_doc_vpc.id}", + + "cidr": "192.168.1.0/24", + + "gateway_ip": "192.168.1.1" + + } + + }, + + "opentelekomcloud_compute_instance_v2": { + + "rf_doc_ecs": { + + "name": "${var.ecs_name}", + + "flavor_id": "c7.large.2", + + "admin_pass": "${var.ecs_admin_passwd}", + + "image_id": "cecc4bcf-b055-4d35-bd5f-693d4412eaef", + + "network": { + + "uuid": "${opentelekomcloud_vpc_subnet_v1.rf_doc_subnet.id}" + + }, + + "system_disk_type": "SAS", + + "system_disk_size": 100, + + "stop_before_destroy": false, + + "delete_disks_on_termination": true, + + "charging_mode": "postPaid", + + "auto_renew": false + + } + + } + + }, + + "output": { + + "ecs_address": { + + "value": "${opentelekomcloud_compute_instance_v2.rf_doc_ecs.access_ip_v4}", + + "description": "The ecs private address." + + }, + + "ecs_id": { + + "value": "${opentelekomcloud_compute_instance_v2.rf_doc_ecs.id}", + + "description": "The ecs resource id." + + } + + } + + } + + The template consists of five parts: + + a. **opentelekomcloud_vpc_v1** in **resource** indicates VPC information. + b. **opentelekomcloud_vpc_subnet_v1** in **resource** indicates information about a subnet defined in the VPC. A subnet is a segment within the IP address range of the VPC. + c. **opentelekomcloud_compute_instance_v2** in **resource** indicates information about an ECS defined in the template. + d. **variable** indicates variables defined by users in templates during stack creation and deployment. + e. **output** defines the outputs of templates. After a stack is created, its output is generated based on the definition and displayed on the :ref:`Outputs ` tab page. + + Next, you can modify the template name, description and version description, as shown in :ref:`Figure 3 `. + + .. _en-us_topic_0000002046740822__fig197685819172: + + **Figure 3** Configuring parameters + + |image2| + + .. caution:: + + The template name must start with a letter and can contain a maximum of 128 characters, including letters, digits, underscores (_), and hyphens (-). The name must be unique. + + The template name cannot be changed after the template is created. + + A template description can contain a maximum of 1024 characters. + + A template version description can contain a maximum of 1024 characters. + +Click **Create Now** to create a template, as shown in :ref:`Figure 4 `. + +.. _en-us_topic_0000002046740822__fig441630162416: + +**Figure 4** Template list + +|image3| + +.. |image1| image:: /_static/images/en-us_image_0000002046741362.png +.. |image2| image:: /_static/images/en-us_image_0000002082662057.png +.. |image3| image:: /_static/images/en-us_image_0000002082820613.png diff --git a/umn/source/resource_formation_service/managing_a_template/deleting_a_template.rst b/umn/source/resource_formation_service/managing_a_template/deleting_a_template.rst new file mode 100644 index 0000000..af6e1f1 --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/deleting_a_template.rst @@ -0,0 +1,25 @@ +:original_name: en-us_topic_0000002082821521.html + +.. _en-us_topic_0000002082821521: + +Deleting a Template +=================== + +On the template list page, locate the created template and click **More** in the right under **Operation** column and click **Delete**. In the dialog box displayed, click **Yes** in the text box as shown in :ref:`Figure 1 `. Template and all versions will be deleted. + +.. _en-us_topic_0000002082821521____d0e1006: + +**Figure 1** Dialog box for deleting a stack + +|image1| + +Alternatively, go to the template details page and click **More** in the right under **Operation** column and click **Delete**, as shown in :ref:`Figure 2 `. + +.. _en-us_topic_0000002082821521__fig15352192845520: + +**Figure 2** Template details for deleting a template + +|image2| + +.. |image1| image:: /_static/images/en-us_image_0000002047151338.png +.. |image2| image:: /_static/images/en-us_image_0000002083259861.png diff --git a/umn/source/resource_formation_service/managing_a_template/editing_a_template.rst b/umn/source/resource_formation_service/managing_a_template/editing_a_template.rst new file mode 100644 index 0000000..1208a65 --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/editing_a_template.rst @@ -0,0 +1,34 @@ +:original_name: en-us_topic_0000002046742302.html + +.. _en-us_topic_0000002046742302: + +Editing a Template +================== + +You can edit an existing template and update the template content. Click **Edit** in the right under operation list to enter the page for updating the template content, as shown in :ref:`Figure 1 `. + +.. _en-us_topic_0000002046742302____d0e1006: + +**Figure 1** Editing a template + +|image1| + +Next, you can edit the template content directly on the page, as shown in :ref:`Figure 2 `. + +.. _en-us_topic_0000002046742302__fig2416252550: + +**Figure 2** Updating template content + +|image2| + +Then, Click **Save Template** in the upper right corner to save this change, as shown in :ref:`Figure 3 `. + +.. _en-us_topic_0000002046742302__fig146836389569: + +**Figure 3** Saving Template + +|image3| + +.. |image1| image:: /_static/images/en-us_image_0000002082672533.png +.. |image2| image:: /_static/images/en-us_image_0000002046752570.png +.. |image3| image:: /_static/images/en-us_image_0000002082673825.png diff --git a/umn/source/resource_formation_service/managing_a_template/exporting_a_template.rst b/umn/source/resource_formation_service/managing_a_template/exporting_a_template.rst new file mode 100644 index 0000000..d84295b --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/exporting_a_template.rst @@ -0,0 +1,22 @@ +:original_name: en-us_topic_0000002082662957.html + +.. _en-us_topic_0000002082662957: + +Exporting a Template +==================== + +RFS support export an existing template to user local area. Click **More** in the right under **Operation** column and click **Export**, as shown in :ref:`Figure 1 `. + +.. _en-us_topic_0000002082662957____d0e1006: + +**Figure 1** Exporting a template + +|image1| + +Next, the template will be automatically downloaded to the user's local area. + +.. caution:: + + Only the latest version of the template will be exported by default + +.. |image1| image:: /_static/images/en-us_image_0000002046754798.png diff --git a/umn/source/resource_formation_service/managing_a_template/index.rst b/umn/source/resource_formation_service/managing_a_template/index.rst new file mode 100644 index 0000000..2df5b9c --- /dev/null +++ b/umn/source/resource_formation_service/managing_a_template/index.rst @@ -0,0 +1,22 @@ +:original_name: en-us_topic_0000002082819549.html + +.. _en-us_topic_0000002082819549: + +Managing a Template +=================== + +- :ref:`Creating a Template ` +- :ref:`Editing a Template ` +- :ref:`Exporting a Template ` +- :ref:`Deleting a Template ` +- :ref:`Creating a Stack ` + +.. toctree:: + :maxdepth: 1 + :hidden: + + creating_a_template + editing_a_template + exporting_a_template + deleting_a_template + creating_a_stack