Create AWX docsite with RST content (#14328)

Co-authored-by: Thanhnguyet Vo <tvo@ansible.com>
Co-authored-by: TVo <thavo@redhat.com>

docs/docsite/rst/common/add-token.rst

@@ -0,0 +1,32 @@
+
+
+2. Click the **Tokens** tab from your user's profile. 
+
+When no tokens are present, the Tokens screen prompts you to add them:
+
+.. image:: ../common/images/users-tokens-empty.png
+
+3. Click the **Add** button, which opens the Create Token window.
+
+4. Enter the following details in Create Token window:
+
+ - **Application**: enter the name of the application with which you want to associate your token. Alternatively, you can search for it by clicking the |search| button. This opens a separate window that allows you to choose from the available options. Use the Search bar to filter by name if the list is extensive. Leave this field blank if you want to create a Personal Access Token (PAT) that is not linked to any application.
+
+ - **Description**: optionally provide a short description for your token.
+ 
+ - **Scope** (required): specify the level of access you want this token to have.
+
+.. |search| image:: ../common/images/search-button.png
+
+5. When done, click **Save** or **Cancel** to abandon your changes.
+
+After the token is saved, the newly created token for the user displays with the token information and when it expires. 
+
+.. image:: ../common/images/users-token-information-example.png
+
+.. note:: This is the only time the token value and associated refresh token value will ever be shown.
+
+In the user's profile, the application for which it is assigned to and its expiration displays in the token list view. 
+
+.. image:: ../common/images/users-token-assignment-example.png
+

docs/docsite/rst/common/containergroup-sa.yml

@@ -0,0 +1,36 @@
+---
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: containergroup-service-account
+  namespace: containergroup-namespace
+---
+kind: Role
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: role-containergroup-service-account
+  namespace: containergroup-namespace
+rules:
+  - apiGroups: [""]
+    resources: ["pods"]
+    verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
+  - apiGroups: [""]
+    resources: ["pods/log"]
+    verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
+  - apiGroups: [""]
+    resources: ["pods/attach"]
+    verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
+---
+kind: RoleBinding
+apiVersion: rbac.authorization.k8s.io/v1
+metadata:
+  name: role-containergroup-service-account-binding
+  namespace: containergroup-namespace
+subjects:
+  - kind: ServiceAccount
+    name: containergroup-service-account
+    namespace: containergroup-namespace
+roleRef:
+  kind: Role
+  name: role-containergroup-service-account
+  apiGroup: rbac.authorization.k8s.io

docs/docsite/rst/common/copyright.rst

@@ -0,0 +1,28 @@
+Copyright © Red Hat, Inc. 
+===============================
+
+Ansible, |aap|, Red Hat, and |rhel| are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ 
+If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original version. 
+
+**Third Party Rights**
+
+Ubuntu and Canonical are registered trademarks of Canonical Ltd.
+
+The CentOS Project is copyright protected. The CentOS Marks are trademarks of Red Hat, Inc. (“Red Hat”).
+
+Microsoft, Windows, Windows Azure, and Internet Explore are trademarks of Microsoft, Inc.
+
+VMware is a registered trademark or trademark of VMware, Inc.
+
+Amazon Web Services", "AWS", "Amazon EC2", and "EC2”, are trademarks of Amazon Web Services, Inc. or its affiliates.
+
+OpenStack™ and OpenStack logo are trademarks of OpenStack, LLC. 
+
+Chrome™ and Google Compute Engine™ service registered trademarks of Google Inc.
+
+Safari® is a registered trademark of Apple, Inc.
+
+Firefox® is a registered trademark of the Mozilla Foundation.
+
+All other trademarks are the property of their respective owners. 

docs/docsite/rst/common/execution_environs.rst

@@ -0,0 +1,2 @@
+
+The ability to build and deploy Python virtual environments for automation has been replaced by Ansible execution environments. Unlike legacy virtual environments, execution environments are container images that make it possible to incorporate system-level dependencies and collection-based content. Each execution environment allows you to have a customized image to run jobs, and each of them contain only what you need when running the job, nothing more. 

docs/docsite/rst/common/get-creds-from-service-account.rst

@@ -0,0 +1,33 @@
+
+A ``ContainerGroup`` is a type of ``InstanceGroup`` that has an associated Credential that allows for connecting to an OpenShift cluster. To set up a container group, you must first have the following:
+
+- A namespace you can launch into (every cluster has a “default” namespace, but you may want to use a specific namespace)
+- A service account that has the roles that allow it to launch and manage Pods in this namespace
+- If you will be using |ees| in a private registry, and have a Container Registry credential associated to them in AWX, the service account also needs the roles to get, create, and delete secrets in the namespace. If you do not want to give these roles to the service account, you can pre-create the ``ImagePullSecrets`` and specify them on the pod spec for the ContainerGroup. In this case, the |ee| should NOT have a Container Registry credential associated, or AWX will attempt to create the secret for you in the namespace.
+- A token associated with that service account (OpenShift or Kubernetes Bearer Token)
+- A CA certificate associated with the cluster
+
+This section describes creating a Service Account in an Openshift cluster (or K8s) in order to be used to run jobs in a container group via AWX. After the Service Account is created, its credentials are provided to AWX in the form of an Openshift or Kubernetes API bearer token credential. Below describes how to create a service account and collect the needed information for configuring AWX. 
+
+To configure AWX:
+
+1. To create a service account, you may download and use this sample service account, :download:`containergroup sa <../common/containergroup-sa.yml>` and modify it as needed to obtain the above credentials.
+
+2. Apply the configuration from ``containergroup-sa.yml``::
+
+	oc apply -f containergroup-sa.yml
+
+
+3. Get the secret name associated with the service account::
+
+	export SA_SECRET=$(oc get sa containergroup-service-account -o json | jq '.secrets[0].name' | tr -d '"')
+
+4. Get the token from the secret::
+
+	oc get secret $(echo ${SA_SECRET}) -o json | jq '.data.token' | xargs | base64 --decode > containergroup-sa.token
+
+5. Get the CA cert::
+
+	oc get secret $SA_SECRET -o json | jq '.data["ca.crt"]' | xargs | base64 --decode > containergroup-ca.crt
+
+6. Use the contents of ``containergroup-sa.token`` and ``containergroup-ca.crt`` to provide the information for the :ref:`ug_credentials_ocp_k8s` required for the container group.