From 18efde342915f6923d25f0609b70555b6427c9dd Mon Sep 17 00:00:00 2001 From: trihoangvo Date: Fri, 10 Apr 2026 15:56:08 +0200 Subject: [PATCH] Update docs for rebranding to T-Cloud Public --- api-ref/source/auth.rst | 16 +++--- api-ref/source/conf.py | 2 +- api-ref/source/examples.rst | 12 ++--- api-ref/source/index.rst | 2 +- api-ref/source/v2.rst | 4 +- umn/source/components_overview.rst | 8 +-- umn/source/conf.py | 2 +- umn/source/getting_started/deploy_app.rst | 8 +-- .../getting_started/specify_image_flavor.rst | 8 +-- umn/source/getting_started/start_deploy.rst | 6 +-- umn/source/google/how_to_deploy.rst | 2 +- umn/source/index.rst | 14 ++--- umn/source/network/dns.rst | 6 +-- umn/source/network/ip_ranges.rst | 2 +- umn/source/orchestration_workflow.rst | 4 +- umn/source/register.rst | 2 +- umn/source/releases.rst | 10 ++-- umn/source/secrets.rst | 2 +- umn/source/security_group/auto_generate.rst | 4 +- umn/source/service_catalogs/apache.rst | 2 +- umn/source/service_catalogs/argocd.rst | 4 +- umn/source/service_catalogs/cce.rst | 2 +- umn/source/service_catalogs/index.rst | 2 +- umn/source/service_catalogs/nextcloud.rst | 6 +-- umn/source/service_catalogs/openshift.rst | 36 ++++++------- umn/source/service_catalogs/rds.rst | 8 +-- umn/source/storage/obs.rst | 8 +-- umn/source/swiss_otc.rst | 52 +++++++++---------- umn/source/tosca_tutorials/define.rst | 2 +- umn/source/tutorial_videos.rst | 10 ++-- 30 files changed, 123 insertions(+), 123 deletions(-) diff --git a/api-ref/source/auth.rst b/api-ref/source/auth.rst index 08fc0b6..8bf4b9c 100644 --- a/api-ref/source/auth.rst +++ b/api-ref/source/auth.rst @@ -18,10 +18,10 @@ Create the following file **openrc**: .. code-block:: bash - #For OTC, use this IAM endpoint: + #For T-Cloud Public, use this IAM endpoint: export OS_AUTH_URL=https://iam.eu-de.otc.t-systems.com:443/v3 - #For Swiss OTC, use this IAM endpoint: + #For Swiss T-Cloud Public, use this IAM endpoint: #export OS_AUTH_URL=https://iam-pub.eu-ch2.sc.otc.t-systems.com/v3 export OS_IDENTITY_API_VERSION=3 @@ -47,8 +47,8 @@ Get the OSTOKEN For all REST requests, set the `OSTOKEN` in the HTTP header `X-Auth-Token` to authenticate it. For examples: -2.1. Requests for OTC -^^^^^^^^^^^^^^^^^^^^^ +2.1. Requests for T-Cloud Public +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. code-block:: bash @@ -58,16 +58,16 @@ For all REST requests, set the `OSTOKEN` in the HTTP header `X-Auth-Token` to a --request GET \ https://designer.otc-service.com/api/v2/templates -2.2. Requests for Swiss OTC -^^^^^^^^^^^^^^^^^^^^^^^^^^^ +2.2. Requests for Swiss T-Cloud Public +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. code-block:: bash curl \ --header "X-Auth-Token: $OSTOKEN" \ - --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss OTC + --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss T-Cloud Public --request GET \ https://designer.otc-service.com/api/v2/templates .. important:: - **TTL token limit**: The OSTOKEN issued by Open Telekom Cloud has a default TTL of 24 hours. However, Cloud Create only accepts the OSTOKEN with the TTL of 30 minutes to limit a stolen token. After 30 minutes, you should get a new one. \ No newline at end of file + **TTL token limit**: The OSTOKEN issued by T-Cloud Public has a default TTL of 24 hours. However, Cloud Create only accepts the OSTOKEN with the TTL of 30 minutes to limit a stolen token. After 30 minutes, you should get a new one. \ No newline at end of file diff --git a/api-ref/source/conf.py b/api-ref/source/conf.py index 49bd407..7bf2d11 100755 --- a/api-ref/source/conf.py +++ b/api-ref/source/conf.py @@ -70,7 +70,7 @@ master_doc = 'index' # General information about the project. -copyright = u'2022-present, Open Telekom Cloud' +copyright = u'2022-present, T-Cloud Public' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/api-ref/source/examples.rst b/api-ref/source/examples.rst index 3717789..29ddc6d 100644 --- a/api-ref/source/examples.rst +++ b/api-ref/source/examples.rst @@ -2,8 +2,8 @@ Examples ******** -1. Example to quick deploy OpenShift on Swiss OTC -================================================= +1. Example to quick deploy OpenShift on Swiss T-Cloud Public +============================================================ Step 1. (Optional) Show the template ------------------------------------ @@ -15,7 +15,7 @@ Request curl \ --header "Accept: application/json" \ --header "X-Auth-Token: $OSTOKEN" \ - --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss OTC + --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss T-Cloud Public --request GET \ https://designer.otc-service.com/api/v2/templates/OpenShift:4.16.19 @@ -31,7 +31,7 @@ Response "template_author": "Dr. Tri Vo", "public_template": true, "documentation_link": "https://docs.otc.t-systems.com/cloud-create/umn/service_catalogs/openshift.html", - "description": "This template deploys a Self-managed OpenShift Container Platform on Open Telekom Cloud with worker nodes in one availability zone...", + "description": "This template deploys a Self-managed OpenShift Container Platform on T-Cloud Public with worker nodes in one availability zone...", "creation_date": "2024-11-27T14:56:00.353+00:00", "last_update_date": "2024-11-27T14:56:00.353+00:00", "inputs": { @@ -184,7 +184,7 @@ Request --header "Content-Type: application/JSON" \ --header "Accept: application/JSON" \ --header "X-Auth-Token: $OSTOKEN" \ - --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss OTC + --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss T-Cloud Public --request POST \ --data @payload.json \ https://designer.otc-service.com/api/v2/deployments @@ -213,7 +213,7 @@ Request curl \ --header "Accept: application/json" \ --header "X-Auth-Token: $OSTOKEN" \ - --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss OTC + --header "X-Auth-Location: OTC-EU-CH2" \ # Add this header for Swiss T-Cloud Public --request GET \ https://designer.otc-service.com/api/v2/deployments/c853667c-2901-4274-aaec-f747e6649cdd diff --git a/api-ref/source/index.rst b/api-ref/source/index.rst index 1dfa484..5d756aa 100644 --- a/api-ref/source/index.rst +++ b/api-ref/source/index.rst @@ -4,7 +4,7 @@ Cloud Create API .. note:: - APIv2 has been released. With the new API, you can quick-deploy applications from premade templates (e.g., OpenShift, CCE, ArgoCD, etc.). The API supports both Open Telekom Cloud and Swiss Open Telekom Cloud. + APIv2 has been released. With the new API, you can quick-deploy applications from premade templates (e.g., OpenShift, CCE, ArgoCD, etc.). The API supports both T-Cloud Public and Swiss T-Cloud Public. .. toctree:: :maxdepth: 1 diff --git a/api-ref/source/v2.rst b/api-ref/source/v2.rst index 3d7f626..9c86dd2 100644 --- a/api-ref/source/v2.rst +++ b/api-ref/source/v2.rst @@ -40,7 +40,7 @@ Sample responses "template_name": "OpenShift", "template_version": "4.16.19", "public_template": true, - "description": "This template deploys a Self-managed OpenShift Container Platform on Open Telekom Cloud with worker nodes in one availability zone..." + "description": "This template deploys a Self-managed OpenShift Container Platform on T-Cloud Public with worker nodes in one availability zone..." }, { "id": "08e591c9-d241-4334-be0a-dba4dee0b6a6", @@ -93,7 +93,7 @@ Sample responses "template_author": "Dr. Tri Vo", "public_template": true, "documentation_link": "https://docs.otc.t-systems.com/cloud-create/umn/service_catalogs/openshift.html", - "description": "This template deploys a Self-managed OpenShift Container Platform on Open Telekom Cloud with worker nodes in one availability zone...", + "description": "This template deploys a Self-managed OpenShift Container Platform on T-Cloud Public with worker nodes in one availability zone...", "creation_date": "2024-11-27T14:56:00.353+00:00", "last_update_date": "2024-11-27T14:56:00.353+00:00", "inputs": { diff --git a/umn/source/components_overview.rst b/umn/source/components_overview.rst index 319275f..594efea 100644 --- a/umn/source/components_overview.rst +++ b/umn/source/components_overview.rst @@ -6,13 +6,13 @@ Components overview This section shows an overview of all components that you can use to design your application. Some components are not yet supported but we can add more upon requests. -.. hint:: If you want to suggest a feature or ask a quick question, please `ask a question in the Open Telekom Cloud Community `_. Choose the forum **Orchestration and Automation** and select topic **Cloud Create** to ask a question. +.. hint:: If you want to suggest a feature or ask a quick question, please `ask a question in the T-Cloud Public Community `_. Choose the forum **Orchestration and Automation** and select topic **Cloud Create** to ask a question. Network ======= ====================== =========================================================================================== ==================== ============== -Components Scenarios Open Telekom Cloud Google Cloud +Components Scenarios T-Cloud Public Google Cloud ====================== =========================================================================================== ==================== ============== Public network :ref:`Connect a compute to a public network ` Yes Yes Public network Reuse an existing floating IP and assign to a compute Yes No @@ -33,7 +33,7 @@ Storage ======= ================ ===================================================================================================== ==================== ============== -Components Scenarios Open Telekom Cloud Google Cloud +Components Scenarios T-Cloud Public Google Cloud ================ ===================================================================================================== ==================== ============== Block storage :ref:`Create a block storage with given size ` Yes Yes Block storage :ref:`Mount and format a block storage ` Yes Yes @@ -45,7 +45,7 @@ PaaS ==== +-----------------------------+------------------------------------------+--------------------+--------------+ -| Components | Scenarios | Open Telekom Cloud | Google Cloud | +| Components | Scenarios | T-Cloud Public | Google Cloud | +=============================+==========================================+====================+==============+ | Relational Database Service | :ref:`Create a RDS with databases ` | Yes | No | +-----------------------------+------------------------------------------+--------------------+--------------+ diff --git a/umn/source/conf.py b/umn/source/conf.py index 9f82742..1fc5925 100755 --- a/umn/source/conf.py +++ b/umn/source/conf.py @@ -70,7 +70,7 @@ master_doc = 'index' # General information about the project. -copyright = u'2022-present, Open Telekom Cloud' +copyright = u'2022-present, T-Cloud Public' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/umn/source/getting_started/deploy_app.rst b/umn/source/getting_started/deploy_app.rst index 246fa22..2f5239f 100644 --- a/umn/source/getting_started/deploy_app.rst +++ b/umn/source/getting_started/deploy_app.rst @@ -13,15 +13,15 @@ How to choose a cloud provider to deploy .. tip:: You can create multiple environents (e.g., development, test, production). In each enviroment, you can deploy an application in a cloud provider. To create an additional environment, click on **Configure Environments**. -3. Choose **OTC**. This will deploy the application in the region :code:`eu-de` of Open Telekom Cloud. -4. (Optional) Click on **Configure cloud provider** if you wish to configure any properties of Open Telekom Cloud resources (e.g., keypair or flavor of a Compute etc.) +3. Choose **T-Cloud Public**. This will deploy the application in the region :code:`eu-de` of T-Cloud Public. +4. (Optional) Click on **Configure cloud provider** if you wish to configure any properties of T-Cloud Public resources (e.g., keypair or flavor of a Compute etc.) 5. Click **Deploy** to start. .. figure:: /_static/images/2-compute-deploy-otc.png :width: 800 - Figure 2. Deploy the application on OTC + Figure 2. Deploy the application on T-Cloud Public .. note:: - Cloud Create deploys your application on Open Telekom Cloud for free of charge (i.e., you only need to pay for the cloud resources you create on Open Telekom Cloud). + Cloud Create deploys your application on T-Cloud Public for free of charge (i.e., you only need to pay for the cloud resources you create on T-Cloud Public). To deploy your application on Google Cloud, refer to the :ref:`Google deploy`. \ No newline at end of file diff --git a/umn/source/getting_started/specify_image_flavor.rst b/umn/source/getting_started/specify_image_flavor.rst index ac893d6..c4f80c7 100644 --- a/umn/source/getting_started/specify_image_flavor.rst +++ b/umn/source/getting_started/specify_image_flavor.rst @@ -11,20 +11,20 @@ How to specify a flavor, image, keypair, and availability zone for a compute .. figure:: /_static/images/2-compute-deploy-matching.png :width: 800 - Figure 1. The matching phase proposes a matched flavor and image of OTC + Figure 1. The matching phase proposes a matched flavor and image of T-Cloud Public -When we designed our :code:`HelloWorld` application, we specified CPU, RAM, and the operating system for the compute component. However, we did not specify a flavor and image. In the above Figure, the designer shows all available flavors and images that Open Telekom Cloud offers. For examples: +When we designed our :code:`HelloWorld` application, we specified CPU, RAM, and the operating system for the compute component. However, we did not specify a flavor and image. In the above Figure, the designer shows all available flavors and images that T-Cloud Public offers. For examples: * If we input :code:`1CPU`, :code:`1GB RAM`, and the operating system :code:`ubuntu` for the compute, the designer shows the matching flavor :code:`s2.medium.1` and available ubuntu versions: :code:`18.04`, :code:`20.04`, and :code:`22.04`. -* If we input :code:`3GB RAM`, the designer will show the matching flavor :code:`s2.medium.4` with :code:`4GB RAM` (because Open Telekom Cloud does not offer a flavor with 3GB RAM). +* If we input :code:`3GB RAM`, the designer will show the matching flavor :code:`s2.medium.4` with :code:`4GB RAM` (because T-Cloud Public does not offer a flavor with 3GB RAM). 2. How to specify a keypair & availability zone =============================================== 1. Select a **Compute**, the popup shows the following optional properties to configure: 2. **availability_zone**: Choose an availability zone for the compute (e.g., :code:`eu-de-01`). -3. **key_pair**: Click on the drop box to show a list of key pairs of the current user. If no key pairs are shown, go to the `console of Open Telekom Cloud `_ and create one. Then go back to refresh the keypair list. +3. **key_pair**: Click on the drop box to show a list of key pairs of the current user. If no key pairs are shown, go to the `console of T-Cloud Public `_ and create one. Then go back to refresh the keypair list. .. figure:: /_static/images/2-compute-deploy-matching-keypair.png :width: 800 diff --git a/umn/source/getting_started/start_deploy.rst b/umn/source/getting_started/start_deploy.rst index 2805f25..9b622bc 100644 --- a/umn/source/getting_started/start_deploy.rst +++ b/umn/source/getting_started/start_deploy.rst @@ -5,7 +5,7 @@ How to deploy & debug 1. Deploy the app ================= -1. When the app is deployed, the **Review** tab shows which cloud resources are being created on Open Telekom Cloud. In this example, a virtual router, network, port, floating IP, and a Virtual Machine (VM) are created. +1. When the app is deployed, the **Review** tab shows which cloud resources are being created on T-Cloud Public. In this example, a virtual router, network, port, floating IP, and a Virtual Machine (VM) are created. 2. Click on a component (e.g., **Compute**) to show the deployment logs of it: @@ -16,12 +16,12 @@ How to deploy & debug 3. In the above example, the logs show that the Terraform configuration for the Compute is generated and being applied. -4. In the console of Open Telekom Cloud, you can see the VM :code:`ctd-Compute-0` is created as well: +4. In the console of T-Cloud Public, you can see the VM :code:`ctd-Compute-0` is created as well: .. figure:: /_static/images/2-compute-deploy-review-2.png :width: 800 - Figure 2. OTC Console shows the new VM ctd-Compute-0 + Figure 2. The Web console shows the new VM ctd-Compute-0 5. After the VM is created, the orchestration engine tests the SSH connection to the VM. After the test, the VM is ready to install a service catalog. diff --git a/umn/source/google/how_to_deploy.rst b/umn/source/google/how_to_deploy.rst index 8493330..efbbe95 100644 --- a/umn/source/google/how_to_deploy.rst +++ b/umn/source/google/how_to_deploy.rst @@ -106,7 +106,7 @@ Step 4. Choose an availability zone and keypair (optional) Figure 6. Choose a zone and keypair -.. tip:: If the keypair dropbox is empty, you can create a keypair from the Open Telekom Cloud console and refresh the page to display it. +.. tip:: If the keypair dropbox is empty, you can create a keypair from the T-Cloud Public console and refresh the page to display it. Step 5. Deploy -------------- diff --git a/umn/source/index.rst b/umn/source/index.rst index da72294..813af4c 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -35,7 +35,7 @@ Quick introduction Cloud Create is a free-to-use **visual cloud management platform** that helps you **reduce cloud engineering footprint**, **accelerate time-to-market**, and deploy everything **from infrastructure to applications** in just one click. -Unlike traditional cloud platforms that require deep infrastructure knowledge and manual setup, Cloud Create offers a visual designer with **a growing premade templates** that enables you to deploy complex environments such as OpenShift and Argo CD in minutes. Whether you're working on Open Telekom Cloud or Swiss Open Telekom Cloud, Cloud Create empowers you to go from idea to running applications with speed and simplicity. +Unlike traditional cloud platforms that require deep infrastructure knowledge and manual setup, Cloud Create offers a visual designer with **a growing premade templates** that enables you to deploy complex environments such as OpenShift and Argo CD in minutes. Whether you're working on T-Cloud Public or Swiss T-Cloud Public, Cloud Create empowers you to go from idea to running applications with speed and simplicity. Cloud Create is built on open standards and powered by open-source TOSCA templates. Every deployment is transparent - **no hidden scripts, no black boxes**. You can inspect, customize, and extend each template directly from `our public GitHub repository `_ for **full transparency and reproducibility**. @@ -63,7 +63,7 @@ Launch your app with a single click. Need to make changes later? Redeploy update **4. Save and share your work** -Turn your customized app into a private template for your team, or publish it publicly on Open Telekom Cloud so others can benefit from your expertise. +Turn your customized app into a private template for your team, or publish it publicly on T-Cloud Public so others can benefit from your expertise. .. figure:: /_static/images/features/overview.png :width: 1000 @@ -100,16 +100,16 @@ In the design, you can seamlessly combine **infrastructure components** (e.g., c 2.3. Deploy and update ---------------------- -When your design is ready, simply hit “Deploy” - and Cloud Create will provision everything for you on Open Telekom Cloud in just minutes. Deploying apps with Cloud Create is simple, controlled, and fully transparent: +When your design is ready, simply hit “Deploy” - and Cloud Create will provision everything for you on T-Cloud Public in just minutes. Deploying apps with Cloud Create is simple, controlled, and fully transparent: **1. Select, Configure, and Launch** -In the **Deploy** section, you choose the desired **application version**, fill in required **inputs**, and select a **cloud provider** - like Open Telekom Cloud. Before launching, they can easily **review the deployment workflow** to ensure everything is ready. +In the **Deploy** section, you choose the desired **application version**, fill in required **inputs**, and select a **cloud provider** - like T-Cloud Public. Before launching, they can easily **review the deployment workflow** to ensure everything is ready. .. figure:: /_static/images/features/overview-deploy.png :width: 800 - Figure 6. Administrators select Open Telekom Cloud to deploy + Figure 6. Administrators select T-Cloud Public to deploy **2. Interactive, Step-by-Step Execution** @@ -166,7 +166,7 @@ An overview of all supported components is available in Section :ref:`Components 3.3. Is Cloud Create opensource ------------------------------- -Cloud Create is based on two opensource projects Application Lifecycle Enablement for Cloud (Alien4cloud) and Ystia Orchestrator (Yorc). At Open Telekom Cloud, we further integrate it with OpenStack and Google Cloud, provide an easy-to-use UI, added features (e.g., secrets management, deployment update, the :ref:`openshift`, etc.), and enforce the strictest Privacy and Security Assessment (PSA) process of Deutsche Telekom. +Cloud Create is based on two opensource projects Application Lifecycle Enablement for Cloud (Alien4cloud) and Ystia Orchestrator (Yorc). At T-Cloud Public, we further integrate it with OpenStack and Google Cloud, provide an easy-to-use UI, added features (e.g., secrets management, deployment update, the :ref:`openshift`, etc.), and enforce the strictest Privacy and Security Assessment (PSA) process of Deutsche Telekom. All premade templates and service catalogs are `opensource and available on Github `_ for transparency and contributions. @@ -201,7 +201,7 @@ We currently support Ansible :code:`10.5.0` (i.e., Ansible core :code:`2.17.4`), 3.6. How can I suggest a feature or ask a quick question -------------------------------------------------------- -Please `ask a question in the Open Telekom Cloud Community `_. Choose the forum **Orchestration and Automation** and select topic **Cloud Create** to ask a question. +Please `ask a question in the T-Cloud Public Community `_. Choose the forum **Orchestration and Automation** and select topic **Cloud Create** to ask a question. .. figure:: /_static/images/ask-question.png :width: 800 diff --git a/umn/source/network/dns.rst b/umn/source/network/dns.rst index 5f8d3bf..d7d3022 100644 --- a/umn/source/network/dns.rst +++ b/umn/source/network/dns.rst @@ -26,7 +26,7 @@ You can create a Domain Name Service so that users can access your compute via t .. important:: - * The domain must be globally unique in the Domain Name Service of Open Telekom Cloud. + * The domain must be globally unique in the Domain Name Service of T-Cloud Public. .. note:: @@ -47,7 +47,7 @@ Expect result Test ---- -1. Update your domain name at the registration service to the nameservers of Open Telekom Cloud: :code:`ns1.open-telekom-cloud.com` and :code:`ns2.open-telekom-cloud.com`. Or to test on localhost, update the nameservers of your localhost to the nameservers of Open Telekom Cloud. +1. Update your domain name at the registration service to the nameservers of T-Cloud Public: :code:`ns1.open-telekom-cloud.com` and :code:`ns2.open-telekom-cloud.com`. Or to test on localhost, update the nameservers of your localhost to the nameservers of T-Cloud Public. 2. Test your domain is resolved to the floating IP: .. code-block:: bash @@ -66,7 +66,7 @@ Test .. important:: - **Swiss Open Telekom Cloud** does not support DNS public zone, but only DNS private zone. When you set a dns_name to a network port, a DNS private zone will be created instead. + **Swiss T-Cloud Public** does not support DNS public zone, but only DNS private zone. When you set a dns_name to a network port, a DNS private zone will be created instead. .. _DNS Private: diff --git a/umn/source/network/ip_ranges.rst b/umn/source/network/ip_ranges.rst index f1ed432..c7024ea 100644 --- a/umn/source/network/ip_ranges.rst +++ b/umn/source/network/ip_ranges.rst @@ -17,7 +17,7 @@ How to create or reuse a private network .. important:: - OTC allows the following network ranges: + T-Cloud Public allows the following network ranges: * 10.0.0.0/8-24 * 172.16.0.0/12-24 diff --git a/umn/source/orchestration_workflow.rst b/umn/source/orchestration_workflow.rst index b04c965..79d240a 100644 --- a/umn/source/orchestration_workflow.rst +++ b/umn/source/orchestration_workflow.rst @@ -34,7 +34,7 @@ Figure 2 shows an example: At the beginning of the workflow, the orchestrator cr 1.2 Key Management System supported ----------------------------------- -When users deploy their applications, the orchestration engine uses the user OpenStack token to work on behalf of them and provision resources on Open Telekom Cloud. It means, the orchestration engine itself cannot make any changes to the tenant without the user authentication. This is similar to the :code:`OpenStack Heat` orchestration engine, which also uses the OpenStack token to provision resource on behalf of the authenticated users. +When users deploy their applications, the orchestration engine uses the user OpenStack token to work on behalf of them and provision resources on T-Cloud Public. It means, the orchestration engine itself cannot make any changes to the tenant without the user authentication. This is similar to the :code:`OpenStack Heat` orchestration engine, which also uses the OpenStack token to provision resource on behalf of the authenticated users. Recall that the orchestrator uses ansible to deploy service catalogs on the computes via SSH. For this purpose, the orchestrator auto-generates an SSH key for each deployment. The public part of the SSH key (name :code:`yorc`) is installed on the VMs. The private part is encrypted in our Key Management System using the user OpenStack token. Without the user OpenStack token, the orchestrator itself cannot decrypt this private key. @@ -57,7 +57,7 @@ The orchestrator retries a workflow step when the following errors occur: The backend server is unreachable ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -* The backend server of Open Telekom Cloud is temporarily not available and the REST API responses an HTTP error message :code:`The backend server is unreachable`. +* The backend server of T-Cloud Public is temporarily not available and the REST API responses an HTTP error message :code:`The backend server is unreachable`. * Retry: 5 times. 2.3 Error during VM bootstrap diff --git a/umn/source/register.rst b/umn/source/register.rst index 0eb06f9..b04d51a 100644 --- a/umn/source/register.rst +++ b/umn/source/register.rst @@ -41,7 +41,7 @@ The following tutorial shows how to create an IAM user and assign the given user 2.1. Create a project (optional, if you don't have one) ------------------------------------------------------- -* Login to the Web console of `OTC `_ / `Swiss OTC `_. +* Login to the Web console of `T-Cloud Public `_ / `Swiss T-Cloud Public `_. * Go to: **Identity Management** .. figure:: /_static/images/register-iam-button.png diff --git a/umn/source/releases.rst b/umn/source/releases.rst index 729f1e9..25449e3 100644 --- a/umn/source/releases.rst +++ b/umn/source/releases.rst @@ -83,15 +83,15 @@ The deploy setup logs display messages in 3 categories: error, warning, and info v2.15 ===== -Swiss Open Telekom Cloud ------------------------- +Swiss T-Cloud Public +-------------------- -Users can now login with IAM accounts from Swiss Open Telekom Cloud as well. When you login with an IAM account from Open Telekom Cloud (or Swiss Open Telekom Cloud) and deploy a template, the template will be deployed on Open Telekom Cloud (or Swiss Open Telekom Cloud), respectively. +Users can now login with IAM accounts from Swiss T-Cloud Public as well. When you login with an IAM account from T-Cloud Public (or Swiss T-Cloud Public) and deploy a template, the template will be deployed on T-Cloud Public (or Swiss T-Cloud Public), respectively. .. figure:: /_static/images/features/v2.15-login-swiss-otc.png :width: 800 - Figure 6. Login with domain name from Swiss Open Telekom Cloud. + Figure 6. Login with domain name from Swiss T-Cloud Public. Read more about :ref:`Swiss OTC`. @@ -144,7 +144,7 @@ v2.13 OpenShift template ------------------ -Users can create a `Self-managed OpenShift Container Platform `_ on Open Telekom Cloud from the :ref:`OpenShift`. +Users can create a `Self-managed OpenShift Container Platform `_ on T-Cloud Public from the :ref:`OpenShift`. .. figure:: /_static/images/features/openshift.png :width: 800 diff --git a/umn/source/secrets.rst b/umn/source/secrets.rst index 7a9c118..f92cb12 100644 --- a/umn/source/secrets.rst +++ b/umn/source/secrets.rst @@ -36,7 +36,7 @@ Step 2. Input the secret value Figure 2. Create the root_password secret -.. important:: Only users from Open Telekom Cloud with the :code:`Tenant Administrator` role in the same project has the permission to view and edit the secret value. +.. important:: Only users from T-Cloud Public with the :code:`Tenant Administrator` role in the same project has the permission to view and edit the secret value. 3. Expected result ================== diff --git a/umn/source/security_group/auto_generate.rst b/umn/source/security_group/auto_generate.rst index 42efd16..189dfff 100644 --- a/umn/source/security_group/auto_generate.rst +++ b/umn/source/security_group/auto_generate.rst @@ -18,9 +18,9 @@ When two Bash components are in a connection relationship, the orchestration eng * Because :code:`Compute_1` is a public compute, a security group is generated for the :code:`Compute_1`, which allows the traffic from the public network (i.e., allow the :code:`TCP` protocol from the remote IP :code:`0.0.0.0/0` on port :code:`8080`). * Because :code:`Bash_1` connects to :code:`Bash_2` internally, a security group is generated for the :code:`Compute_2`, which allows the private traffic from the :code:`Compute_1` (i.e., allow the :code:`TCP` protocol from the remote security group of :code:`Compute_1` on port :code:`27017`). -* The Open Telekom Cloud console also shows the auto-generated security groups attached to the ports of the two compute nodes. The figure below shows an example that the security group is auto-generated for the :code:`Compute_2` accordingly. +* The Web console also shows the auto-generated security groups attached to the ports of the two compute nodes. The figure below shows an example that the security group is auto-generated for the :code:`Compute_2` accordingly. .. figure:: /_static/images/7-Bash-auto-secgroup-otc.png :width: 800 - Figure 2. Example of auto-generated security group on the OTC console \ No newline at end of file + Figure 2. Example of auto-generated security group on the Web console \ No newline at end of file diff --git a/umn/source/service_catalogs/apache.rst b/umn/source/service_catalogs/apache.rst index 6d802f5..08606fb 100644 --- a/umn/source/service_catalogs/apache.rst +++ b/umn/source/service_catalogs/apache.rst @@ -65,7 +65,7 @@ Expect result Expect result ^^^^^^^^^^^^^ -1. One DNS public zone :code:`myexample.com.` with 2 record sets type A :code:`myexample.com.` and :code:`www.myexample.com.` will be created on Open Telekom Cloud. +1. One DNS public zone :code:`myexample.com.` with 2 record sets type A :code:`myexample.com.` and :code:`www.myexample.com.` will be created on T-Cloud Public. 2. The record sets point to the floating IP of the public compute, which hosts the Apache Webserver (e.g., :code:`80.158.62.203`). .. figure:: /_static/images/service-catalogs/dns2.png diff --git a/umn/source/service_catalogs/argocd.rst b/umn/source/service_catalogs/argocd.rst index f664b94..580b3a0 100644 --- a/umn/source/service_catalogs/argocd.rst +++ b/umn/source/service_catalogs/argocd.rst @@ -33,7 +33,7 @@ Whether you’re a startup racing to launch or an enterprise bringing new servic If this is the first time you use CCE **in a project**, you have to authorize it first. -1. Login to the Web console of `OTC `_ / or `Swiss OTC `_. +1. Login to the Web console of `T-Cloud Public `_ / or `Swiss T-Cloud Public `_. 2. Switch to the project you want to deploy CCE / go to **Cloud Container Engine**. 3. The Web console shows an **Authorization Description** > Click OK. @@ -137,7 +137,7 @@ If you do not wish to expose Argo CD to public access, disable **access_with_elb You can access the example app with a public IP address from type Load Balancer as follows: -1. On the OTC Web console, you can see a new CCE cluster is up and running. +1. On the Web console, you can see a new CCE cluster is up and running. 2. Go to **Services** and copy the **ELB Public IP** of the service **front-end-elb**. This is the service from type Load Balancer of our example app, which is `defined on the Github repository `_. .. figure:: /_static/images/service-catalogs/argocd6.png diff --git a/umn/source/service_catalogs/cce.rst b/umn/source/service_catalogs/cce.rst index a6e7e89..e714fbc 100644 --- a/umn/source/service_catalogs/cce.rst +++ b/umn/source/service_catalogs/cce.rst @@ -32,7 +32,7 @@ Whether you're testing a new idea or deploying a production-grade environment, t If this is the first time you use CCE **in a project**, you have to authorize it first. -1. Login to the Web console of `OTC `_ / or `Swiss OTC `_. +1. Login to the Web console of `T-Cloud Public `_ / or `Swiss T-Cloud Public `_. 2. Switch to the project you want to deploy CCE / go to **Cloud Container Engine**. 3. The Web console shows an **Authorization Description** > Click OK. diff --git a/umn/source/service_catalogs/index.rst b/umn/source/service_catalogs/index.rst index 4220bb1..9ec1333 100644 --- a/umn/source/service_catalogs/index.rst +++ b/umn/source/service_catalogs/index.rst @@ -6,7 +6,7 @@ Service catalogs In addition to infrastructure components (e.g., compute, network, storage), Cloud Create provides most frequently used services on the application layer that are ready-to-deploy (e.g., Prometheus for monitoring). This section shows how to use these services in the editor. -The service catalogs are modelled using TOSCA (i.e., a YAML file definition of the service). They are open-source and available at `the service catalogs of Open Telekom Cloud `_. +The service catalogs are modelled using TOSCA (i.e., a YAML file definition of the service). They are open-source and available on `our Github `_. A part from the services provided by Cloud Create, users can also model their services using TOSCA, then import them in the designer and share with one another. For tutorials how to model the service using TOSCA, refer to :ref:`tosca define service catalog`. diff --git a/umn/source/service_catalogs/nextcloud.rst b/umn/source/service_catalogs/nextcloud.rst index 4021ed9..a964cf8 100644 --- a/umn/source/service_catalogs/nextcloud.rst +++ b/umn/source/service_catalogs/nextcloud.rst @@ -40,7 +40,7 @@ Nextcloud is deployed in two VM: Template v3.0.0 ^^^^^^^^^^^^^^^ -Nextcloud app uses the Open Telekom Cloud service :ref:`rds` offered by Open Telekom Cloud as the MySQL Server. +Nextcloud app uses the T-Cloud Public service :ref:`rds` offered by T-Cloud Public as the MySQL Server. .. figure:: /_static/images/service-catalogs/nextcloud2v3.png :width: 800 @@ -50,7 +50,7 @@ Nextcloud app uses the Open Telekom Cloud service :ref:`rds` offered by Open Tel Template v4.0.0 ^^^^^^^^^^^^^^^ -Nextcloud app uses the Open Telekom Cloud services :ref:`obs` and :ref:`rds` as the storage back-end and the MySQL Server, respectively. +Nextcloud app uses the T-Cloud Public services :ref:`obs` and :ref:`rds` as the storage back-end and the MySQL Server, respectively. .. figure:: /_static/images/service-catalogs/nextcloud2v4.png :width: 800 @@ -105,7 +105,7 @@ Nextcloud app uses the Open Telekom Cloud services :ref:`obs` and :ref:`rds` as 3. Access nextcloud using DNS: -If :code:`dns_name` is specified, one DNS public zone :code:`myexample.com.` with 2 record sets type A :code:`myexample.com.` and :code:`www.myexample.com.` will be created on Open Telekom Cloud. The record sets point to the floating IP (e.g., :code:`80.158.45.177`): +If :code:`dns_name` is specified, one DNS public zone :code:`myexample.com.` with 2 record sets type A :code:`myexample.com.` and :code:`www.myexample.com.` will be created on T-Cloud Public. The record sets point to the floating IP (e.g., :code:`80.158.45.177`): .. figure:: /_static/images/service-catalogs/nextcloud4b.png :width: 800 diff --git a/umn/source/service_catalogs/openshift.rst b/umn/source/service_catalogs/openshift.rst index d045743..195d530 100644 --- a/umn/source/service_catalogs/openshift.rst +++ b/umn/source/service_catalogs/openshift.rst @@ -10,7 +10,7 @@ OpenShift template The following tutorial shows you how to register a (trial) subscription key from Red Hat and uses it to create an OpenShift cluster using the OpenShift template. .. important:: - * This template deploys a `self-managed OpenShift Container Platform `_ on Open Telekom Cloud (OTC) with Bring Your Own Subscription (BYOS). OpenShift is installed following the `OpenShift on OpenStack (User-Provisioned Infrastructure) procedure defined by Red Hat `_. + * This template deploys a `self-managed OpenShift Container Platform `_ on T-Cloud Public with Bring Your Own Subscription (BYOS). OpenShift is installed following the `OpenShift on OpenStack (User-Provisioned Infrastructure) procedure defined by Red Hat `_. * The subscription covers support from Red Hat for the OpenShift product itself (e.g., OpenShift core components, Red Hat Enterprise Linux CoreOS, upgrades/patches within OpenShift) on the `third party infrastructure `_. * Versions available in the template: :code:`4.16.19` and :code:`4.18.30`. Please contact us if you need a specific version. @@ -34,7 +34,7 @@ The following tutorial shows you how to register a (trial) subscription key from a. Specify base_domain ^^^^^^^^^^^^^^^^^^^^^^ -Specify the **base_domain** (e.g., :code:`tri-test.com`). This is the domain name that you will use to access the OpenShift console after the deployment completes. You can specify any domain names you prefer. Your domain name will be registered on the nameservers of OTC. After the deployment completes, you can add the nameservers of OTC on your local machine, then the domain can be resolved (See Section :ref:`access_openshift_console`). Alternatively, you can register a public domain name (e.g., a free domain from ClouDNS) and input it here. In the later case, you do not need to add the nameservers of OTC. +Specify the **base_domain** (e.g., :code:`tri-test.com`). This is the domain name that you will use to access the OpenShift console after the deployment completes. You can specify any domain names you prefer. Your domain name will be registered on the nameservers of T-Cloud Public. After the deployment completes, you can add the nameservers of T-Cloud Public on your local machine, then the domain can be resolved (See Section :ref:`access_openshift_console`). Alternatively, you can register a public domain name (e.g., a free domain from ClouDNS) and input it here. In the later case, you do not need to add the nameservers of T-Cloud Public. .. figure:: /_static/images/service-catalogs/openshift_config1.png :width: 700 @@ -43,7 +43,7 @@ Specify the **base_domain** (e.g., :code:`tri-test.com`). This is the domain nam .. important:: - **Swiss OTC** does not support a DNS Public Zone. However, you can bring your own domain name and set it here. For example, you can register a free domain name on ClouDNS (e.g., tri-test.ddns-ip.net). Then you set it to the base_domain. After the deployment completes, you can use this domain name to access the OpenShift console. See instruction in :ref:`access with nameservers`. + **Swiss T-Cloud Public** does not support a DNS Public Zone. However, you can bring your own domain name and set it here. For example, you can register a free domain name on ClouDNS (e.g., tri-test.ddns-ip.net). Then you set it to the base_domain. After the deployment completes, you can use this domain name to access the OpenShift console. See instruction in :ref:`access with nameservers`. b. Specify pull_secret @@ -75,7 +75,7 @@ d. (Optional) Specify ssh_public_key ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * Specify the **ssh_public_key** with your SSH public key (e.g., :code:`ssh-ed25519 AAAAC3N...`). This public key will be injected in the bastion host, master and worker nodes so that you can SSH to them later on. -* If ssh_public_key is **not specified**, we will auto-select one of your **existing key pair** from the OTC console instead. +* If ssh_public_key is **not specified**, we will auto-select one of your **existing key pair** from the Web console instead. .. figure:: /_static/images/service-catalogs/openshift_config2.png :width: 700 @@ -97,7 +97,7 @@ e. (Optional) Specify other paramters 3. Expect result ================ -* It takes about 2 minutes to create all compute resources on OTC. Afterwards, the OpenShift bootstrap process continues to setup the master and worker nodes. +* It takes about 2 minutes to create all compute resources on T-Cloud Public. Afterwards, the OpenShift bootstrap process continues to setup the master and worker nodes. * After about 31 minutes, the **CheckOpenShiftStatus** job checks the OpenShift boostrap process and reports the status. .. figure:: /_static/images/service-catalogs/openshift_check_result.png @@ -135,17 +135,17 @@ Option 1. Add hostname in /etc/host Option 2. Add nameservers ^^^^^^^^^^^^^^^^^^^^^^^^^ -On OTC, a DNS public zone is created with the record sets type A pointing to the ingress VIP address of the OpenShift cluster as follows: +On T-Cloud Public, a DNS public zone is created with the record sets type A pointing to the ingress VIP address of the OpenShift cluster as follows: .. figure:: /_static/images/service-catalogs/openshift-dns.png :width: 900 - Figure 9. A DNS public zone is created on OTC + Figure 9. A DNS public zone is created on T-Cloud Public It means, if you add the nameservers :code:`ns1.open-telekom-cloud.com` (80.158.48.19) or :code:`ns2.open-telekom-cloud.com` (93.188.242.252) to your machine, you can access the OpenShift console URL. .. important:: - **Swiss OTC** does not support a DNS Public Zone. However, you can register a DNS somewhere else. For example, first you register a domain name on a free DNS like `ClouDNS `_ (e.g., :code:`tri-test.ddns-ip.net`). Then you set it to the input **base_domain** (in Step 2.2a). Finally, you set a record set type A on ClouDNS pointing to the ingress VIP of the OpenShift cluster: + **Swiss T-Cloud Public** does not support a DNS Public Zone. However, you can register a DNS somewhere else. For example, first you register a domain name on a free DNS like `ClouDNS `_ (e.g., :code:`tri-test.ddns-ip.net`). Then you set it to the input **base_domain** (in Step 2.2a). Finally, you set a record set type A on ClouDNS pointing to the ingress VIP of the OpenShift cluster: .. figure:: /_static/images/service-catalogs/openshift-dns2.png :width: 600 @@ -263,7 +263,7 @@ The **bootstrap** VM is only needed during the installation. After the installat 4.2. Update os_password ----------------------- -On OTC, an IAM user password is expired every 3 months (by default). After it is expired, OpenShift cannot authenticate to OTC to provision volumes so you may get the following error: +On T-Cloud Public, an IAM user password is expired every 3 months (by default). After it is expired, OpenShift cannot authenticate to T-Cloud Public to provision volumes so you may get the following error: .. code-block:: bash @@ -302,7 +302,7 @@ The Cloud Credential Operator (CCO) will `rotate the secret `_ in OpenShift, which connects to SFS via NFS protocol: +You can create a SFS on T-Cloud Public manually and create a `PersistentVolume using NFS `_ in OpenShift, which connects to SFS via NFS protocol: -1. Go to the `webconsole of OTC `_. +1. Go to the `Web console `_. 2. Go to **Scalable File Service** / **Create File System** * Choose the **VPC** and **subnet** so that the SFS is created in the same subnet of the OpenShift worker nodes. During the deployment, Cloud Create created a VPC with the prefix :code:`cc`, followed by the environement name :code:`enviroment` and the application name :code:`openshift00`. In our example, the VPC is :code:`cc-environment-openshift00`. The subnet of our OpenShift worker nodes is :code:`cc-environment-openshift00-private-subnet`. @@ -474,14 +474,14 @@ You can create a SFS on OTC manually and create a `PersistentVolume using NFS `_ is not fully compliant with the OpenStack API. Therefore, the Machine API of OpenShift fails to create network ports on OTC. Follow the **steps below** to apply the `patch `_ so that the Machine API can work with the REST API of OTC. When the compliant issues are fixed, this patch is not necessary. + The `REST API of T-Cloud Public to create a network port `_ is not fully compliant with the OpenStack API. Therefore, the Machine API of OpenShift fails to create network ports on T-Cloud Public. Follow the **steps below** to apply the `patch `_ so that the Machine API can work with the REST API of T-Cloud Public. When the compliant issues are fixed, this patch is not necessary. .. code-block:: bash @@ -554,7 +554,7 @@ You can use the MachineSet API from OpenShift to spawn worker nodes on OTC as fo cloudsSecret: name: openstack-cloud-credentials namespace: openshift-machine-api - flavor: s3.xlarge.4 # Choose a flavor from OTC with minimum 4 vCPU and 16GB RAM + flavor: s3.xlarge.4 # Choose a flavor from T-Cloud Public with minimum 4 vCPU and 16GB RAM image: "" kind: OpenstackProviderSpec networks: @@ -572,7 +572,7 @@ You can use the MachineSet API from OpenShift to spawn worker nodes on OTC as fo trunk: false userDataSecret: name: worker-user-data - availabilityZone: eu-de-01 # Choose 'eu-de-01', 'eu-de-02', and 'eu-de-03' (for OTC), 'eu-ch2a' and 'eu-ch2b' (for Swiss OTC). + availabilityZone: eu-de-01 # Choose 'eu-de-01', 'eu-de-02', and 'eu-de-03' (for T-Cloud Public), 'eu-ch2a' and 'eu-ch2b' (for Swiss T-Cloud Public). 4. and apply diff --git a/umn/source/service_catalogs/rds.rst b/umn/source/service_catalogs/rds.rst index 8c2f138..7227841 100644 --- a/umn/source/service_catalogs/rds.rst +++ b/umn/source/service_catalogs/rds.rst @@ -7,9 +7,9 @@ Relational Database Service 1. About ======== -* Use this component to deploy the Relational Database Service (RDS) on Open Telekom Cloud. With RDS, you can deploy a MySQL, PostgreSQL, or Microsoft SQL Server. -* RDS is a cloud service with auto-backup, auto-upgrade and high availability features, which are fully managed via Open Telekom Cloud console. -* Because the cloud service is fully managed by Open Telekom Cloud, users cannot SSH to the RDS Virtual Machine. If you wish to have a full control of the VM, use the :ref:`mysql` instead. +* Use this component to deploy the Relational Database Service (RDS) on T-Cloud Public. With RDS, you can deploy a MySQL, PostgreSQL, or Microsoft SQL Server. +* RDS is a cloud service with auto-backup, auto-upgrade and high availability features, which are fully managed via the Web console . +* Because the cloud service is fully managed by T-Cloud Public, users cannot SSH to the RDS Virtual Machine. If you wish to have a full control of the VM, use the :ref:`mysql` instead. 2. How to use ============= @@ -52,7 +52,7 @@ Relational Database Service Figure 2. Set output for RDS -The deployment will output the private IP of RDS. Alternatively, you can get the IP via the Open Telekom Cloud console. +The deployment will output the private IP of RDS. Alternatively, you can get the IP via the T-Cloud Public console. 2.4. How to create MySQL database and user ------------------------------------------ diff --git a/umn/source/storage/obs.rst b/umn/source/storage/obs.rst index 5e0c134..8e706de 100644 --- a/umn/source/storage/obs.rst +++ b/umn/source/storage/obs.rst @@ -7,7 +7,7 @@ How to create an Object Storage 1. About ======== -* Use this component to deploy an Object Storage (OBS) on Open Telekom Cloud. +* Use this component to deploy an Object Storage (OBS) on T-Cloud Public. * To create an OBS, an access key is required. Users can either create an access key manually or use the property **auto_create_access_key** of the component. 2. Requirements @@ -44,7 +44,7 @@ Users who deploy an application with OBS, they must have the permission :code:`O 4. Specify the **access_key** and **secret_key** (Step 4). If you do not want to expose the keys in plaintext, set it as a secret (Step 4b). .. tip:: - The access key is required for a user to create an Object Storage. You can create your access key in the Open Telekom Cloud Console in the :code:`My Credentials` section. + The access key is required for a user to create an Object Storage. You can create your access key in the T-Cloud Public Console in the :code:`My Credentials` section. .. figure:: /_static/images/obs1.png :width: 800 @@ -74,12 +74,12 @@ Before the deployment, an access key is auto-created for the user (who deploys t Figure 3. An access key is auto-created before the deployment starts -In the :code:`My Credentials` Section of the Open Telekom Cloud console, you can see the new access key is created: +In the :code:`My Credentials` Section of the T-Cloud Public console, you can see the new access key is created: .. figure:: /_static/images/obs4.png :width: 800 - Figure 4. View access key on the Open Telekom Cloud console + Figure 4. View access key on the T-Cloud Public console In the topology, you can reference to the access key by using the intrinsic function :code:`get_secret: access_key` and :code:`get_secret: secret_key`. diff --git a/umn/source/swiss_otc.rst b/umn/source/swiss_otc.rst index 3ba8f92..7334bf2 100644 --- a/umn/source/swiss_otc.rst +++ b/umn/source/swiss_otc.rst @@ -1,15 +1,15 @@ .. _Swiss OTC: -************************ -Swiss Open Telekom Cloud -************************ +******************** +Swiss T-Cloud Public +******************** -This section summarizes the differences between two locations Swiss Open Telekom Cloud (Swiss OTC) vs. Open Telekom Cloud (OTC) and how you **design a template that works for both locations**. +This section summarizes the differences between two locations Swiss T-Cloud Public vs. T-Cloud Public and how you **design a template that works for both locations**. 1. Flavors ========== -Swiss OTC has a different set of flavors than OTC. At the time of writing, it only has **s3 flavors** (e.g., :code:`s3.medium.1`, :code:`s3.medium.2`). +Swiss T-Cloud Public has a different set of flavors than T-Cloud Public. At the time of writing, it only has **s3 flavors** (e.g., :code:`s3.medium.1`, :code:`s3.medium.2`). In the following example, the Compute has 1CPU and 1GB Ram. We do not need to set a specific flavor for the Compute in the template. @@ -18,7 +18,7 @@ In the following example, the Compute has 1CPU and 1GB Ram. We do not need to se Figure 1. A Compute has 1 CPU and 1GB Ram -When you deploy the template on Swiss OTC, Cloud Create finds a matching flavor on Swiss OTC that has 1CPU and 1GB Ram (e.g., :code:`s3.medium.1`). +When you deploy the template on Swiss T-Cloud Public, Cloud Create finds a matching flavor on Swiss T-Cloud Public that has 1CPU and 1GB Ram (e.g., :code:`s3.medium.1`). .. figure:: /_static/images/swiss-otc-02.png :width: 800 @@ -28,25 +28,25 @@ When you deploy the template on Swiss OTC, Cloud Create finds a matching flavor 2. Availability Zones ===================== -OTC and Swiss OTC have different availability zones: +T-Cloud Public and Swiss T-Cloud Public have different availability zones: - +-----+------------------------------+------------------+ - | | OTC | Swiss OTC | - +=====+==============================+==================+ - | AZs | eu-de-01, eu-de-02, eu-de-03 | eu-ch2a, eu-ch2b | - +-----+------------------------------+------------------+ + +-----+------------------------------+----------------------+ + | | T-Cloud Public | Swiss T-Cloud Public | + +=====+==============================+======================+ + | AZs | eu-de-01, eu-de-02, eu-de-03 | eu-ch2a, eu-ch2b | + +-----+------------------------------+----------------------+ In the Design (Figure 1), you can set the **availability_zone** to :code:`az-01`, :code:`az-02`, or :code:`az-03`. When you deploy the template in a location, Cloud Create finds the availability zones in the given location and updates the compute accordingly: -+-----------+----------+----------+--------------------------------------+ -| AZ | az-01 | az-02 | az-03 | -+===========+==========+==========+======================================+ -| OTC | eu-de-01 | eu-de-02 | eu-de-03 | -+-----------+----------+----------+--------------------------------------+ -| Swiss OTC | eu-ch2a | eu-ch2b | eu-ch2b (Swiss OTC has only two AZs) | -+-----------+----------+----------+--------------------------------------+ ++----------------------+----------+----------+-------------------------------------------------+ +| AZ | az-01 | az-02 | az-03 | ++======================+==========+==========+=================================================+ +| T-Cloud Public | eu-de-01 | eu-de-02 | eu-de-03 | ++----------------------+----------+----------+-------------------------------------------------+ +| Swiss T-Cloud Public | eu-ch2a | eu-ch2b | eu-ch2b (Swiss T-Cloud Public has only two AZs) | ++----------------------+----------+----------+-------------------------------------------------+ .. figure:: /_static/images/swiss-otc-03.png :width: 800 @@ -60,7 +60,7 @@ When you deploy the template in a location, Cloud Create finds the availability 3. EVS ====== -Swiss OTC supports only SAS and SSD (`See documentation `_). Therefore, you can set either :code:`SAS` or :code:`SSD` in the :code:`volume_type` of a **BootVolume** or **BlockStorage**. +Swiss T-Cloud Public supports only SAS and SSD (`See documentation `_). Therefore, you can set either :code:`SAS` or :code:`SSD` in the :code:`volume_type` of a **BootVolume** or **BlockStorage**. .. figure:: /_static/images/swiss-otc-04.png :width: 800 @@ -70,29 +70,29 @@ Swiss OTC supports only SAS and SSD (`See documentation