[Doc] update regarding rebranding (#643)

[Doc] update regarding rebranding

Rebrand doc, closes #637

Reviewed-by: Artem Lifshits

Author: anton-sidelnikov

CONTRIBUTING.rst

@@ -2,7 +2,7 @@ Contributing to OTC Extensions
 ==============================
 
 OTC Extension are developed as a community effort initiated by
-T-Systems International GmbH for the Open Telekom Cloud under an Open
+T-Systems International GmbH for the T Cloud Public (former Open Telekom Cloud) under an Open
 Source license. All code is licensed under the Apache 2.0 license.
 
 We are happily accepting pull requests. Please reach out to the

README.rst

@@ -9,7 +9,8 @@ OTC Extensions
     :alt: Documentation Status
 
 The OTC Extensions augment the OpenStack SDK of features and services
-provided by the Open Telekom Cloud. If installed as a Python package,
+provided by the T Cloud Public (former Open Telekom Cloud).
+If installed as a Python package,
 they add several extra commands to the OpenStack Client CLI. Therefore
 the project interacts closely with the
 
@@ -46,7 +47,7 @@ Configuration
 
 `Configuration Page <https://docs.otc.t-systems.com/python-otcextensions/install/configuration.html>`_
 
-Acessing the Open Telekom Cloud APIs requires authentication and
+Acessing the T Cloud Public APIs requires authentication and
 authorization. For both there are several options available:
 
 * **Configuration files** (recommended): A file called `clouds.yaml`

doc/source/index.rst

@@ -8,7 +8,7 @@ simplifies building applications to work with OpenStack clouds. The
 `OpenStack Client`_ is its equivalent on the command line.
 
 **This project, OTC Extensions,** adds extra functionality to the SDK
-and the CLI offered by the `Open Telekom Cloud`_. Technically, the OTC
+and the CLI offered by the `T Cloud Public`_. Technically, the OTC
 Extensions provide Python classes and methods to attach your own code
 to the cloud. They also integrate seamless into the OpenStack Client,
 providing many extra commands.
@@ -46,7 +46,7 @@ configured conveniently in a few files.
 Working with the CLI tool
 -------------------------
 
-Users who want to access Open Telekom Cloud specific services with
+Users who want to access T Cloud Public specific services with
 :doc:`command line tools <cli/index>` for a shell like Bash find
 documentation of all of their operations and properties in this
 section.
@@ -93,4 +93,4 @@ available:
 .. _OpenStack SDK: https://docs.openstack.org/openstacksdk/
 .. _OpenStack Client: https://docs.openstack.org/python-openstackclient/
 .. _Ansible modules: https://github.com/OpenTelekomCloud/ansible-collections/
-.. _Open Telekom Cloud: https://open-telekom-cloud.com/
+.. _T Cloud Public: https://public.t-cloud.com/

doc/source/install/configuration.rst

@@ -1,7 +1,7 @@
 Configuration
 =============
 
-You can connect to the Open Telekom Cloud and OpenStack clouds in general
+You can connect to the T Cloud Public and OpenStack clouds in general
 using two approaches. The first one uses a credential file called
 ``clouds.yaml`` and the other one is to use ``environment variables``.
 
@@ -17,7 +17,7 @@ locations with increasing precedence:
 2. Home directory / user space (~/.config/openstack/{clouds,secure}.yaml)
 3. Current directory (./{clouds,secure}.yaml)
 
-A sample clouds.yaml file is listed below to connect with Open Telekom Cloud:
+A sample clouds.yaml file is listed below to connect with T Cloud Public:
 
 **clouds.yaml**
 
@@ -139,7 +139,7 @@ secret which is left out from ``clouds.yaml``:
 Agency based authorization
 ^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Open Telekom Cloud supports a concept of agencies. One domain delegates access
+T Cloud Public supports a concept of agencies. One domain delegates access
 to resources to another domain. After trust relationship is established the
 following configuration can be used in ``clouds.yaml``:
 
@@ -167,9 +167,9 @@ Configuration of Environment Variables
 --------------------------------------
 
 Instead of using the clouds.yaml file, environmnt variables can be configured
-to connect to the Open Telekom Cloud. Create a simple file like ``.ostackrc``
+to connect to the T Cloud Public. Create a simple file like ``.ostackrc``
 in the home directory and source the file to make the variables available. On
-Open Telekom Cloud servers this file exists on bootup and needs to be changed
+T Cloud Public servers this file exists on bootup and needs to be changed
 according to your credentials.
 
 .. code-block:: bash

doc/source/install/index.rst

@@ -3,7 +3,7 @@ Installation
 
 There are several install options for OTC Extensions to enhance the
 native `OpenStack Client`_ and to extend the `OpenStack SDK`_. Once
-installed, they cover additional `Open Telekom Cloud`_ services and
+installed, they cover additional `T Cloud Public`_ services and
 provide extra functionality on top of the stock OpenStack SDK and CLI.
 
 .. toctree::
@@ -31,7 +31,7 @@ of OpenStack SDK and OTC Extensions into a CLI tool. If installed, it
 requires the SDK.
 
 **OTC Extensions:** An addition to OpenStack SDK with enhanced
-functionality that is specific for the Open Telekom Cloud. This is the
+functionality that is specific for the T Cloud Public. This is the
 package you are currently looking at. It requires the SDK since it
 extends its interfaces. If it is installed as a Python package it is
 detected and integrated automatically by the other two packages
@@ -84,5 +84,5 @@ https://build.opensuse.org/project/show/Cloud:OTC:Tools:OpenStack.
 
 .. _OpenStack SDK: https://docs.openstack.org/openstacksdk/
 .. _OpenStack Client: https://docs.openstack.org/python-openstackclient/
-.. _Open Telekom Cloud: https://open-telekom-cloud.com/
+.. _T Cloud Public: https://public.t-cloud.com/
 .. _Python Package Index (PyPI): https://pypi.org/

doc/source/sdk/getting_started.rst

@@ -76,8 +76,8 @@ the following command.
 The output represents all existent OpenStack servers in your Cloud
 environment.
 
-OTC Extensions specific Example for Open Telekom Cloud
-------------------------------------------------------
+OTC Extensions specific Example for T Cloud Public
+--------------------------------------------------
 
 The following script uses the OTC Extensions to list all existent CCE Clusters
 in your account.

doc/source/sdk/guides/ces.rst

@@ -1,8 +1,8 @@
 Cloud Eye Service (CES)
-=========================
+=======================
 
 Cloud Eye (CES) is a high-performance monitoring service with integrated
-alarm functions. Open Telekom Cloud users benefit from a dashboard with
+alarm functions. T Cloud Public users benefit from a dashboard with
 a basic overview of resources and their current status. Users can
 configure the alarm function in such a way that they receive
 notifications via SMS or email. Monitoring with the Cloud Eye Service

doc/source/sdk/guides/dcs.rst

@@ -14,7 +14,7 @@ The Distributed Cache Service is ideal for use as a cache server (e.g. in
 order to accelerate the loading times of websites), for real-time analyses,
 high-speed transactions, and message queuing. Clusters made up of individual
 DCS instances can be used for applications with extremely high performance
-requirements. Redis is available in the Open Telekom Cloud as the Distributed
+requirements. Redis is available in the T Cloud Public as the Distributed
 Cache Service. Via the console, the database can be defined in three variants:
 as a single-node database for temporary data storage, as a master/standby
 database for higher availability, and as a cluster for high performance.
@@ -25,7 +25,7 @@ Instances
 ---------
 
 A Distributed Cache Service Instance is a Redis instance on top of
-Open Telekom Cloud.
+T Cloud Public.
 
 List Instances
 ^^^^^^^^^^^^^^

doc/source/sdk/guides/dns.rst

@@ -12,10 +12,10 @@ work in public clouds. It enables users to integrate cloud resources in their
 own company networks with ease – they then see the services as part of their
 internal network. Moreover, using domain names instead of IP addresses also
 facilitates administrative tasks and makes clouds more user-friendly.
-The Open Telekom Cloud also offers a Domain Name Service (DNS). DNS is
-available via the Open Telekom Cloud console and features anti-DDoS
+The T Cloud Public also offers a Domain Name Service (DNS). DNS is
+available via the T Cloud Public console and features anti-DDoS
 protection. In addition to references to external IP addresses, the solution
-can also be used for services within the Open Telekom Cloud. Pricing of the
+can also be used for services within the T Cloud Public. Pricing of the
 Domain Name Service is based on scaled prices depending on the number of
 domains stored. If a domain is created and remains configured for more than
 24 hours, it is billed once for the entire month. A usage-based payment is

doc/source/sdk/guides/index.rst

@@ -1,8 +1,8 @@
 Guides for SDK
 ==============
 
-Open Telekom Cloud related User Guides
---------------------------------------
+T Cloud Public related User Guides
+----------------------------------
 
 .. toctree::
    :maxdepth: 1
@@ -42,9 +42,9 @@ Open Telekom Cloud related User Guides
 User Guides
 -----------
 
-The Open Telekom Cloud services are covering OpenStack native services and
+The T Cloud Public services are covering OpenStack native services and
 enhanced ones covering additional functionalities. All user guides related
-to Open Telekom Cloud are listed above. The links links to the most important
+to T Cloud Public are listed above. The links links to the most important
 OpenStack native services are listed below.
 
 OpenStack native User Guides