diff --git a/docs-2.0/nebula-cloud/3.how-to-set-solution.md b/docs-2.0/nebula-cloud/3.how-to-set-solution.md index 884beeb275b..78b65bc44f8 100644 --- a/docs-2.0/nebula-cloud/3.how-to-set-solution.md +++ b/docs-2.0/nebula-cloud/3.how-to-set-solution.md @@ -6,7 +6,11 @@ Solution refers to the Nebula Graph database running on Nebula Graph Cloud. Afte 1. To complete your purchase after subscribing Nebula Graph Cloud on Azure, click **Configure account now** on the page and the system will jump to the Nebula Graph Cloud login page. 2. Log in to the Azure account that has subscribed the Solution service in Nebula Graph Cloud. + + 1. Select a **region** in the **Provider** section. + + ![cloud](../nebula-cloud/figs/cl-ug-015.png) !!! caution @@ -19,8 +23,12 @@ Solution refers to the Nebula Graph database running on Nebula Graph Cloud. Afte It is recommended to configure at least 2 query engines and 3 storage engines to ensure high service availability. 3. Enter the specified Azure account mailbox as the Root user in the **Nebula Graph** section. + + ![cloud](../nebula-cloud/figs/cl-ug-016.png) + 4. Click **Next** at the bottom of this page. - 5. After confirmation, click **Create** at the bottom of this page. + 5. After confirmation, click **Create** at the bottom of this page. + 3. For now, you have completed the configuration of the Solution. If the status of the Solution is **running** on the Cloud homepage, the Solution has been created successfully. ## Solution status diff --git a/docs-2.0/nebula-cloud/5.solution/5.0.introduce-solution.md b/docs-2.0/nebula-cloud/5.solution/5.0.introduce-solution.md index 0ac5558362c..ef8908eaa11 100644 --- a/docs-2.0/nebula-cloud/5.solution/5.0.introduce-solution.md +++ b/docs-2.0/nebula-cloud/5.solution/5.0.introduce-solution.md @@ -6,26 +6,40 @@ On the **Solution** page, the sidebars are different based on roles and privileg On the homepage of Cloud, click on the Solution's name to enter the **Solution Info** page. The Solution Info page consists of the following parts: Basic Info, Instance Info, Price Info, Getting Started. You can view the information on this page in detail. -## Application +![Solution info](../figs/cl-ug-001.png) + +## Applications In the sidebar, click **Applications** to enter the page of ecosystem tools(Dashboard/Studio/Explorer). Different roles see different ecosystem tools. For more information, see [Accessory applications](../5.solution/5.1.supporting-application.md). +![applications](../figs/cl-ug-002.png) + ## Connectivity In the sidebar, click **Connectivity** to enter Private Link page. On this page, you can create a Private Link endpoint that enables you to access Nebula Graph databases through a private IP address in a virtual network. For more information, see [Private Link](../5.solution/5.2.connection-configuration-and-use.md). +![connectivity](../figs/cl-ug-003.png) + ## Root Management In the sidebar, click **Root Management** to enter the root account management page. For more information, see [Role and User Management](../5.solution/5.3.role-and-authority-management.md). -## User Mangement +![root management](../figs/cl-ug-004.png) + +## User Management In the sidebar, click **User Management** to enter the user account management page. For more information, see [Role and User Management](../5.solution/5.3.role-and-authority-management.md). +![User Management](../figs/cl-ug-005.png) + ## Audit Log In the sidebar, click **Audit Log** to enter the operation history page. You can select the time period according to the operation information such as `Create Solution`, `Start Solution`, `Stop Solution`, and filter results by operator and operation record. +![Audit Log](../figs/cl-ug-006.png) + ## Settings In the sidebar, click **Settings** to enter the settings page, and you can `Stop Solution` or `Transfer Solution` in this page. + +![Settings](../figs/cl-ug-007.png) \ No newline at end of file diff --git a/docs-2.0/nebula-cloud/5.solution/5.2.connection-configuration-and-use.md b/docs-2.0/nebula-cloud/5.solution/5.2.connection-configuration-and-use.md index 01d002b723c..0a4ea1605dc 100644 --- a/docs-2.0/nebula-cloud/5.solution/5.2.connection-configuration-and-use.md +++ b/docs-2.0/nebula-cloud/5.solution/5.2.connection-configuration-and-use.md @@ -6,6 +6,8 @@ You can create a Private Link endpoint in **Connectivity** to allow users to acc 1. Enter your subscription ID, click **Create**. The creation time takes about 2 minutes. + ![connectivity](../figs/cl-ug-008.png) + !!! note The subscription ID on the **Subscription** page of Azure Portal. You can click on the [Subscriptions] (https://portal.azure.com/?l=en.en-us#blade/Microsoft_Azure_Billing/SubscriptionsBlade) page for quick access. @@ -14,61 +16,73 @@ You can create a Private Link endpoint in **Connectivity** to allow users to acc 1. Navigate to the Azure portal. Search for Private Link and click **Private endpoint**. 2. Click **+ add**. + + ![Private endpoint](../figs/cl-ug-009.png) + 3. In the **Basics** section, fill in the following plan details: - Project details - |Field|Description| - |:---|:---| - |Subscription|Select the subscription.| - |Resource group|Select an existing resource group or create a new resource group.| + |Field|Description| + |:---|:---| + |Subscription|Select the subscription.| + |Resource group|Select an existing resource group or create a new resource group.| - Instance details - |Field|Description| - |:---|:---| - |Name| Set the name of the private endpoint.| - |Region| Select the region. | + |Field|Description| + |:---|:---| + |Name| Set the name of the private endpoint.| + |Region| Select the region. | + + ![Basics](../figs/cl-ug-010.png) - !!! caution + !!! caution The region of the database you select should be in the same area as that of your business to avoid performance and speed problems. 4. At the bottom of the **Basics** page, click **Next: Resource**. 5. In the **Resource** section, fill in the following plan details: - |Field|Description| - |:----|:---| - |Connection method|Click **Connect to an Azure resource by resource ID or alias.**| - |Resource ID or alias|Set the alias.| - |Request message|Set the message, this message will be sent to the resource owner.| + |Field|Description| + |:----|:---| + |Connection method|Click **Connect to an Azure resource by resource ID or alias.**| + |Resource ID or alias|Set the alias.| + |Request message|Set the message, this message will be sent to the resource owner.| !!! note The alias is on the **Connectivity** page of Nebula Graph Cloud, click ![copy](../figs/copy.png) to copy it. + + ![resource](../figs/cl-ug-012.png) 6. At the bottom of the **Resource** page, click **Next: Configuration**. 7. In the **Configuration** section, select the following plan details: - Networking - |Field|Description| - |:---|:---| - |Virtual network|Set virtual networks.| - |Subnet|Set the subnet in the selected virtual network.| + |Field|Description| + |:---|:---| + |Virtual network|Set virtual networks.| + |Subnet|Set the subnet in the selected virtual network.| !!! note Private DNS integration is currently not supported. + ![configuration](../figs/cl-ug-013.png) + 8. At the bottom of the **Configuration** page, click **Next: Tags**. 9. (optional)In the **Tags** section, enter **Name:Values**. + + ![Tag](../figs/cl-ug-014.png) + 10. At the bottom of the **Tags** page, click **Next: Review + create**. 11. At the bottom of the **Review + create** page, click **Create**. 3. After creating the **private endpoint**, copy the **Private IP address** in **Network interface** to the **Connectivity** page in Cloud. Click the **Create**. -!!! note + !!! note Private Link Endpoint IP information is stored in the Cloud, and you can click ![edit](../figs/edit.png) to modify. diff --git a/docs-2.0/nebula-cloud/5.solution/5.3.role-and-authority-management.md b/docs-2.0/nebula-cloud/5.solution/5.3.role-and-authority-management.md index 5a4cdcdbd6d..816779bfd24 100644 --- a/docs-2.0/nebula-cloud/5.solution/5.3.role-and-authority-management.md +++ b/docs-2.0/nebula-cloud/5.solution/5.3.role-and-authority-management.md @@ -15,6 +15,7 @@ Only users with **OWNER** authority can manage **ROOT** users. On the **Root Management** page, **OWNER** can reset **ROOT** users. 1. Click **Reset**, enter the email address of the ROOT user to be updated, and click **Send Email** to send the email. + 2. After the **ROOT** user receives the confirmation email, click **Confirm**. ## User Management diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-001.png b/docs-2.0/nebula-cloud/figs/cl-ug-001.png new file mode 100644 index 00000000000..cec45e0e800 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-001.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-002.png b/docs-2.0/nebula-cloud/figs/cl-ug-002.png new file mode 100644 index 00000000000..e84824c1b55 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-002.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-003.png b/docs-2.0/nebula-cloud/figs/cl-ug-003.png new file mode 100644 index 00000000000..ebd1d47a391 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-003.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-004.png b/docs-2.0/nebula-cloud/figs/cl-ug-004.png new file mode 100644 index 00000000000..6f1e963fa18 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-004.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-005.png b/docs-2.0/nebula-cloud/figs/cl-ug-005.png new file mode 100644 index 00000000000..5a372d49396 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-005.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-006.png b/docs-2.0/nebula-cloud/figs/cl-ug-006.png new file mode 100644 index 00000000000..13868aa323e Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-006.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-007.png b/docs-2.0/nebula-cloud/figs/cl-ug-007.png new file mode 100644 index 00000000000..d21402c16ee Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-007.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-008.png b/docs-2.0/nebula-cloud/figs/cl-ug-008.png new file mode 100644 index 00000000000..25678e690b5 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-008.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-009.png b/docs-2.0/nebula-cloud/figs/cl-ug-009.png new file mode 100644 index 00000000000..d46a600a4d8 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-009.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-010.png b/docs-2.0/nebula-cloud/figs/cl-ug-010.png new file mode 100644 index 00000000000..afe6472cc84 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-010.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-011.png b/docs-2.0/nebula-cloud/figs/cl-ug-011.png new file mode 100644 index 00000000000..08a8b35952e Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-011.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-012.png b/docs-2.0/nebula-cloud/figs/cl-ug-012.png new file mode 100644 index 00000000000..59a1ecdccb7 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-012.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-013.png b/docs-2.0/nebula-cloud/figs/cl-ug-013.png new file mode 100644 index 00000000000..166c992dae0 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-013.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-014.png b/docs-2.0/nebula-cloud/figs/cl-ug-014.png new file mode 100644 index 00000000000..a3f5c0613f6 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-014.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-015.png b/docs-2.0/nebula-cloud/figs/cl-ug-015.png new file mode 100644 index 00000000000..af77a1c893b Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-015.png differ diff --git a/docs-2.0/nebula-cloud/figs/cl-ug-016.png b/docs-2.0/nebula-cloud/figs/cl-ug-016.png new file mode 100644 index 00000000000..0e290f720f5 Binary files /dev/null and b/docs-2.0/nebula-cloud/figs/cl-ug-016.png differ