DOC-691 | ArangoGraph: Adjust for deployment UI changes (#547)

Author: Simran-B

Diff for: site/content/3.10/arangograph/deployments/_index.md

@@ -5,118 +5,95 @@ weight: 20
 description: >-
    How to create and manage deployments in ArangoGraph
 ---
-Below projects in the ArangoGraph deployment hierarchy are deployments. A deployment
-contains an ArangoDB, configured as you choose. You can have any number of
-deployments under one project.
+An ArangoGraph deployment is an ArangoDB cluster or single server, configured
+as you choose.
 
-**Organizations → Projects → <u>Deployments</u>**
-
-Each deployment can also be backed up manually or automatically by schedules
-you can define.
+Each deployment belongs to a project, which belongs to an organization in turn.
+You can have any number of deployments under one project.
 
-In essence, you can create whatever structure fits you for a given organization,
-its projects and deployments.
+**Organizations → Projects → <u>Deployments</u>**
 
 ![ArangoGraph Deployments](../../../images/arangograph-deployments-page.png)
 
 ## How to create a new deployment
 
 1. If you do not have a project yet,
    [create a project](../projects.md#how-to-create-a-new-project) first.
-2. In the main navigation, in the __Projects__ section, click the project for
-   which you want to create a new deployment.
-3. In the __Deployments__ page, you will see an empty list or a list with
-   your project's existing deployments.
-4. Click the __New deployment__ button.
+2. In the main navigation, click __Deployments__.
+3. Click the __New deployment__ button.
+4. Select the project you want to create the deployment for.
 5. Set up your deployment. The configuration options are described below.
 
-![ArangoGraph New Deployment](../../../images/arangograph-new-deployment1.png)
-
 {{< info >}}
 Deployments contain exactly **one policy**. Within that policy, you can define
 role bindings to regulate access control on a deployment level.
 {{< /info >}}
 
 ### In the **General** section
 
-- Enter the name and optionally a short description for the deployment.
-
-### In the **Location** section
-
-1. Select the __Provider__ and __Region__ of the provider.
-   {{< warning >}}
-   Once a deployment has been created, it is not possible to change the
-   provider and region anymore.
-   {{< /warning >}}
-2. Select the __DB Version__.
-   **Note**: If you don't know which DB version to select, leave the version
-   selected by default.
-3. In the __CA Certificate__ field
-    - The default certificate created for your project will automatically be selected.
-    - If you have no default certificate, or want to use a new certificate
-      create a new certificate by typing the desired name for it and hitting
-      enter or clicking the name when done.
-    - Or, if you already have multiple certificates, select the desired one.
-4. _Optional but strongly recommended:_ In the __IP allowlist__ field, select the
-   desired one in case you want to limit access to your deployment to certain
-   IP ranges. To create a allowlist, navigate to your project and select the
-   __IP allowlists__ tab.
-
-{{< security >}}
-For any kind of production deployment we strongly advise to use an IP allowlist.
-{{< /security >}}
-
-### In the **Configuration** section
-
-Choose between a **OneShard**, **Sharded** or **Single Server** deployment.
-
-- OneShard deployments are suitable when your data set fits in a single node.
-  They are ideal for graph use cases.
-
-- Sharded deployments are suitable when your data set is larger than a single
-  node. The data will be sharded across multiple nodes.
-
-- Single Server deployments are suitable when you want to try out ArangoDB without
-  the need for high availability or scalability. The deployment will contain a
-  single server only. Your data will not be replicated and your deployment can
-  be restarted at any time.
-
-{{< info >}}
-Before you begin configuring your deployment, you first need to select the
-provider and region in the Location section.
-{{< /info >}}
-
-#### OneShard
+- Enter the __Name__ and optionally a __Short description__ for the deployment.
+- Select the __Provider__ and __Region__ of the provider.
+  {{< warning >}}
+  Once a deployment has been created, it is not possible to change the
+  provider and region anymore.
+  {{< /warning >}}
 
-- Select the memory size of your node. The disk size is automatically set for you
-  based on the selected memory size.
+![ArangoGraph New Deployment General](../../../images/arangograph-new-deployment-general.png)
 
-![ArangoGraph Deployment OneShard](../../../images/arangograph-new-deployment-oneshard.png)
+### In the **Sizing** section
 
-#### Sharded
+- Choose a __Model__ for the deployment:
 
-- In addition to the memory size as in the OneShard configuration, select
-  the number of nodes for your deployment. The more nodes you have, the higher
-  the replication factor can be. Same as in OneShard, the disk size is automatically
-  set for you.
+  - __OneShard__ deployments are suitable when your data set fits in a single node.
+    They are ideal for graph use cases. This model has a fixed number of 3 nodes.
 
-![ArangoGraph Deployment Sharded](../../../images/arangograph-new-deployment-sharded.png)
+  - __Sharded__ deployments are suitable when your data set is larger than a single
+    node. The data will be sharded across multiple nodes. You can select the
+    __Number of nodes__ for this deployment model. The more nodes you have, the
+    higher the replication factor can be.
 
-#### Single Server
+  - __Single Server__ deployments are suitable when you want to try out ArangoDB without
+    the need for high availability or scalability. The deployment will contain a
+    single server only. Your data will not be replicated and your deployment can
+    be restarted at any time.
 
-- Like with OneShard and Sharded deployments, you can choose the memory size.
-  Note, however, that the size you choose is for the entire deployment.
-  For OneShard and Sharded deployments the chosen sizes are per node.
+- Select a __NODE SIZE__ from the list of available options. Each option is a
+  combination of vCPUs, memory, and disk space per node.
 
-![ArangoGraph Deployment Single Server](../../../images/arangograph-new-deployment-singleserver.png)
+![ArangoGraph New Deployment Sizing](../../../images/arangograph-new-deployment-sizing.png)
 
-### In the **Summary** section
+### In the **Advanced** section
 
-1. Review the configuration, and if you're ok with the setup press the
-  __Create__ button.
-2. You will be taken to the deployment overview page.
-   **Note:** Your deployment is at that point being bootstrapped, this process
-   will take a few minutes. Once it is ready, you will receive a confirmation email.
+- Select the __DB Version__.
+  If you don't know which DB version to select, use the version selected by default.
+- Select the desired __Support Plan__. Click the link below the field to get
+  more information about the different support plans.
+- In the __Certificate__ field:
+    - The default certificate created for your project is selected automatically.
+    - If you have no default certificate, or want to use a new certificate,
+      create a new certificate by typing the desired name for it and hitting
+      enter or clicking __Create "\<name\>"__ when done.
+    - Or, if you already have multiple certificates, select the desired one.
+- _Optional but strongly recommended:_ In the __IP allowlist__ field, select the
+  desired one in case you want to limit access to your deployment to certain
+  IP ranges. To create a allowlist, navigate to your project and select the
+  __IP allowlists__ tab. See [How to manage IP allowlists](../projects.md#how-to-manage-ip-allowlists)
+  for details.
+  {{< security >}}
+  For any kind of production deployment it is strongly advise to use an IP allowlist.
+  {{< /security >}}
+- Select a __Deployment Profile__. Profile options are only available on request.
+
+![ArangoGraph New Deployment Advanced](../../../images/arangograph-new-deployment-advanced.png)
+
+### In the **Summary** panel
+
+1. Review the configuration, and if you're okay with the setup, press the
+  __Create deployment__ button.
+2. You are taken to the deployment overview page.
+   **Note:** Your deployment is being bootstrapped at that point. This process
+   takes a few minutes. Once the deployment is ready, you receive a confirmation
+   email.
 
 ## How to access your deployment
 
@@ -125,11 +102,12 @@ provider and region in the Location section.
    which you created a deployment earlier.
 3. Alternatively, you can access your deployment by clicking __Deployments__ in the
    dashboard navigation. This page shows all deployments from all projects.
+   Click the name of the deployment you want to view.
 4. For each deployment in your project, you see the status. While your new
-   deployment is being set up, it will display the __bootstrapping__ status.
+   deployment is being set up, it displays the __bootstrapping__ status.
 5. Press the __View__ button to show the deployment page.
 6. When a deployment displays a status of __OK__, you can access it.
-7. Click the __Open web console__ button or on the endpoint URL property to open
+7. Click the __Open database UI__ button or on the database UI link to open
    the dashboard of your new ArangoDB deployment.
 
 At this point your ArangoDB deployment is available for you to use — **Have fun!**
@@ -138,16 +116,14 @@ If you have disabled the [auto-login option](#auto-login-to-database-ui) to the
 database web interface, you need to follow the additional steps outlined below
 to access your deployment:
 
-1. Click the copy icon next to the root password. This will copy the deployment
+1. Click the copy icon next to the root password. This copies the deployment
    root password to your clipboard. You can also click the view icon to unmask
    the root password to see it.
-
    {{< security >}}
    Do not use the root username/password for everyday operations. It is recommended
    to use them only to create other user accounts with appropriate permissions.
    {{< /security >}}
-
-2. Click the __Open web console__ button or on the endpoint URL property to open
+2. Click the __Open database UI__ button or on the database UI link to open
    the dashboard of your new ArangoDB deployment.
 3. In the __username__ field type `root`, and in the __password__ field paste the
    password that you copied earlier.
@@ -242,7 +218,7 @@ This feature is available on `443` port only.
 
 ## How to edit a deployment
 
-You can modify a deployment’s configuration, including the ArangoDB version
+You can modify a deployment's configuration, including the ArangoDB version
 that is being used, change the memory size, or even switch from
 a OneShard deployment to a Sharded one if your data set no longer fits in a
 single node. 
@@ -252,34 +228,37 @@ To edit an existing deployment, you must have the necessary set of permissions
 attached to your role. Read more about [roles and permissions](../security-and-access-control/_index.md#roles).
 {{< /tip >}}
 
-1. Go to the **Projects** section and select an existing deployment from the list. 
-2. Open the deployment you want to change. 
-3. In the **Quick start** section, click the **Edit** button. 
-4. In the **Version and Security** section, you can do the following:
-   - Upgrade the ArangoDB version that is currently being used. See also
-     [Upgrades and Versioning](upgrades-and-versioning.md)
-   - Select a different CA certificate.
-   - Add or remove an IP allowlist.
-5. In the **Configuration** section, you can do the following:
-   - Scale up or down the memory size per node. The disk size is
-     automatically set for you.
-     {{< warning >}}
-     When scaling up or down the memory size in AWS deployments, the new
-     value gets locked and cannot be changed again until the cloud provider rate
-     limit is reset. 
-     {{< /warning >}}
+1. In the main navigation, click **Deployments** and select an existing
+   deployment from the list, or click **Projects**, select a project, and then
+   select a deployment.
+2. In the **Quick start** section, click the **Edit** button. 
+3. In the **General** section, you can do the following:
+   - Change the deployment name
+   - Change the deployment description
+4. In the **Sizing** section, you can do the following:
    - Change **OneShard** deployments into **Sharded** deployments. To do so,
-     click **Sharded**. In addition to the other configuration options, you can
-     select the number of nodes for your deployment. This can also be modified later on.
+     select **Sharded** in the **Model** dropdown list. You can select the
+     number of nodes for your deployment. This can also be modified later on.
      {{< warning >}}
      You cannot switch from **Sharded** back to **OneShard**.
      {{< /warning >}}
    - Change **Single Server** deployments into **OneShard** or **Sharded** deployments.
      {{< warning >}}
      You cannot switch from **Sharded** or **OneShard** back to **Single Server**.
      {{< /warning >}}
-6. All changes are reflected in the **Summary** section. Review the new
-   configuration and click **Save**.
+   - Scale up or down the node size.
+     {{< warning >}}
+     When scaling up or down the size in AWS deployments, the new value gets locked
+     and cannot be changed again until the cloud provider rate limit is reset.
+     {{< /warning >}}
+5. In the **Advanced** section, you can do the following:
+   - Upgrade the ArangoDB version that is currently being used. See also
+     [Upgrades and Versioning](upgrades-and-versioning.md)
+   - Select a different certificate.
+   - Add or remove an IP allowlist.
+   - Select a deployment profile.
+6. All changes are reflected in the **Summary** panel. Review the new
+   configuration and click **Save changes**.
 
 ## How to connect a driver to your deployment
 
@@ -305,7 +284,7 @@ application has to handle connection failures by retrying operations if needed.
 ## How to delete a deployment
 
 {{< danger >}}
-Deleting a deployment will delete all its data and backups.
+Deleting a deployment deletes all its data and backups.
 This operation is **irreversible**. Please proceed with caution.
 {{< /danger >}}
 

Diff for: site/content/3.10/arangograph/organizations/_index.md

@@ -5,14 +5,12 @@ weight: 10
 description: >-
    How to manage organizations and what type of packages ArangoGraph offers
 ---
-At the highest level of the ArangoGraph deployment hierarchy are organizations.
-Organizations are a container for projects.
+An ArangoGraph organizations is a container for projects. An organization
+typically represents a (commercial) entity such as a company, a company division,
+an institution, or a non-profit organization.
 
 **<u>Organizations</u> → Projects → Deployments**
 
-An organization typically represents a (commercial) entity such as a company,
-a company division, an institution or a non-profit organization.
-
 Users can be members of one or more organizations. However, you can only be a
 member of one _Free-to-try_ tier organization at a time.
 

Diff for: site/content/3.10/arangograph/projects.md

@@ -5,20 +5,16 @@ weight: 15
 description: >-
   How to manage projects and IP allowlists in ArangoGraph
 ---
-Below organizations in the ArangoGraph deployment hierarchy are projects. They can
-represent organizational units such as teams, product groups, environments
-(e.g. staging vs. production). You can have any number of projects under one
-organization.
+ArangoGraph projects can represent organizational units such as teams,
+product groups, environments (e.g. staging vs. production). You can have any
+number of projects under one organization.
 
 **Organizations → <u>Projects</u> → Deployments**
 
 Projects are a container for related deployments, certificates & IP allowlists.
 Projects also come with their own policy for access control. You can have any
 number of deployment under one project.
 
-In essence, you can create whatever structure fits you for a given organization,
-its projects and deployments.
-
 ![ArangoGraph Projects Overview](../../images/arangograph-projects-overview.png)
 
 ## How to create a new project

Diff for: site/content/3.10/arangograph/security-and-access-control/_index.md

@@ -65,12 +65,13 @@ viewed on the **Policy** page of an organization within the ArangoGraph dashboar
 Decide whether you want to edit the policy for an organization, a project,
 or a deployment:
 
-- **Organization**: In the main navigation menu, click **Access Control**, then
-  open the **Policy** tab.
-- **Project**: In the main navigation menu, click the name of the required project, then
-  open the **Policy** tab.
-- **Deployment**: In the main navigation menu, click the name of the required project, then click either 
-  the deployment name or the **View** button, and finally open the **Policy** tab.
+- **Organization**: In the main navigation, click the __Organization__ icon and
+  then click __Policy__.
+- **Project**: In the main navigation, click the __Dashboard__ icon, then click
+  __Projects__, click the name of the desired project, and finally click __Policy__.
+- **Deployment**: In the main navigation, click the __Dashboard__ icon, then
+  click __Deployments__, click the name of the desired deployment, and finally 
+  click __Policy__.
 
 To delete a role binding, click the **Recycle Bin** icon in the **Actions** column.
 

Diff for: site/content/3.10/get-started/set-up-a-cloud-instance.md

@@ -82,13 +82,12 @@ used for multiple accounts.
 
    {{< icon src="../../images/arangograph-deployment-ready-email.png" alt="ArangoGraph Deployment Ready Email" style="max-height: 50vh">}}
 
-3. Click the name or the **View** button of the deployment card (or the
-   __Open deployment details__ link in the email) to view the deployment
-   details.
+3. Click the name of the deployment (or the __Open deployment details__ link in
+   the email) to view the deployment details.
 
    ![ArangoGraph Deployment Ready](../../images/arangograph-deployment-ready.png)
 
-4. Click the __Open web console__ button to open the ArangoDB web interface.
+4. Click the __Open database UI__ button to open the ArangoDB web interface.
 
 5. You can install example datasets and follow the accompanying guides to get
    started with ArangoDB and its query language. In the ArangoGraph dashboard, click