From bfad245ef2d35f09ea62b5743af9e6eaa61172fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9C=B1=E6=99=93=E9=9D=92?= <86282370+izhuxiaoqing@users.noreply.github.com> Date: Wed, 29 Dec 2021 20:53:53 +0800 Subject: [PATCH 1/4] Update 3.how-to-set-solution.md --- .../nebula-cloud/3.how-to-set-solution.md | 49 +++++++++++++++++++ 1 file changed, 49 insertions(+) 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 e69de29bb2d..550d640f3a9 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 @@ -0,0 +1,49 @@ +# How to configure a Solution + +Solution refers to the Nebula Graph database running on Nebula Graph Cloud. After subscribing Nebula Graph Cloud on Azure, you need to configure your Solutions on the Cloud platform to complete the purchase. This topic describes how to configure a Solution. + +## Configuration workflow + +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. + + !!! 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. + + 2. Configure the type and the number of the query engine and the type, the number, and the disk size of the storage engine in the **Instance** section. + + !!! caution + + 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. + 4. Click `Next` 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 + +You may see the following status and corresponding description on the Solution page. + +|Status| Description | +|:---|:---| +| `creating` | The resources required by a Solution are ready and the Solution will be created automatically. At this time, the Solution is in the `creating` state, which may last from several minutes to over ten minutes. | +| `starting` | After you have restarted a Solution, it will be in the `starting` state for a while. | +| `stopping` | After you have clicked `Stop Solution`, the Solution will be in the `stopping` state for a while. | +| `deleting` | After you have clicked `Delete Solution`, the Solution will be in the `deleting` state for a while. | +| `running` | After you create a Solution, it will be in the `running` state for a long time. | +| `stopped` | After you stop a Solution, it will be in the `stopped` state for a long time. | +| `deleted` | After you delete a Solution, it will be in the `deleted` state for a long time. | +| `create_failed` | If you failed to create a Solution, the Solution will be in the `create_failed` state for a long time. | +| `stop_failed` | If you failed to stop a Solution, the Solution will be in the `stop_failed` state for a long time. | +| `start_failed` | If you failed to start a Solution, the Solution will be in the `start_failed` state for a long time. | + +!!! caution + + If a Solution stays in an intermediate state for a long time and the page remains unchanged after refreshing, it means that there is an exception and you need to submit an order to solve the problem. + +!!! caution + + If a Solution is in the state of `create_failed`, `stop_failed`, or `start_failed`, you can execute `CREATE`, `STOP`, or `START` again. From cdc74c1ff247f065a8345b21717fca3e3e8edc9d Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Fri, 31 Dec 2021 14:45:25 +0800 Subject: [PATCH 2/4] Update 3.how-to-set-solution.md --- docs-2.0/nebula-cloud/3.how-to-set-solution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 550d640f3a9..e6fc4e16378 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 @@ -1,4 +1,4 @@ -# How to configure a Solution +# Configure a Solution Solution refers to the Nebula Graph database running on Nebula Graph Cloud. After subscribing Nebula Graph Cloud on Azure, you need to configure your Solutions on the Cloud platform to complete the purchase. This topic describes how to configure a Solution. From d75c9550efe9f7cba11190a6b800ac284115d7a7 Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Fri, 31 Dec 2021 14:48:24 +0800 Subject: [PATCH 3/4] Update 3.how-to-set-solution.md --- docs-2.0/nebula-cloud/3.how-to-set-solution.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 e6fc4e16378..dc086fe095f 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 @@ -4,9 +4,9 @@ Solution refers to the Nebula Graph database running on Nebula Graph Cloud. Afte ## Configuration workflow -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. +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. + 1. Select a **region** in the **Provider** section. !!! caution From 5386cdb2f9937a4e72a245fb74d2d2e0289ee81e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9C=B1=E6=99=93=E9=9D=92?= <86282370+izhuxiaoqing@users.noreply.github.com> Date: Fri, 31 Dec 2021 14:53:56 +0800 Subject: [PATCH 4/4] Update 3.how-to-set-solution.md --- .../nebula-cloud/3.how-to-set-solution.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) 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 dc086fe095f..884beeb275b 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 @@ -19,9 +19,9 @@ 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. - 4. Click `Next` 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. + 4. Click **Next** 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 @@ -29,16 +29,16 @@ You may see the following status and corresponding description on the Solution p |Status| Description | |:---|:---| -| `creating` | The resources required by a Solution are ready and the Solution will be created automatically. At this time, the Solution is in the `creating` state, which may last from several minutes to over ten minutes. | -| `starting` | After you have restarted a Solution, it will be in the `starting` state for a while. | -| `stopping` | After you have clicked `Stop Solution`, the Solution will be in the `stopping` state for a while. | -| `deleting` | After you have clicked `Delete Solution`, the Solution will be in the `deleting` state for a while. | -| `running` | After you create a Solution, it will be in the `running` state for a long time. | -| `stopped` | After you stop a Solution, it will be in the `stopped` state for a long time. | -| `deleted` | After you delete a Solution, it will be in the `deleted` state for a long time. | -| `create_failed` | If you failed to create a Solution, the Solution will be in the `create_failed` state for a long time. | -| `stop_failed` | If you failed to stop a Solution, the Solution will be in the `stop_failed` state for a long time. | -| `start_failed` | If you failed to start a Solution, the Solution will be in the `start_failed` state for a long time. | +| **creating** | The resources required by a Solution are ready and the Solution will be created automatically. At this time, the Solution is in the **creating** state, which may last from several minutes to over ten minutes. | +| **starting** | After you have restarted a Solution, it will be in the **starting** state for a while. | +| **stopping** | After you have clicked **Stop Solution**, the Solution will be in the **stopping** state for a while. | +| **deleting** | After you have clicked **Delete Solution**, the Solution will be in the **deleting** state for a while. | +| **running** | After you create a Solution, it will be in the **running** state for a long time. | +| **stopped** | After you stop a Solution, it will be in the **stopped** state for a long time. | +| **deleted** | After you delete a Solution, it will be in the **deleted** state for a long time. | +| **create_failed** | If you failed to create a Solution, the Solution will be in the **create_failed** state for a long time. | +| **stop_failed** | If you failed to stop a Solution, the Solution will be in the **stop_failed** state for a long time. | +| **start_failed** | If you failed to start a Solution, the Solution will be in the **start_failed** state for a long time. | !!! caution @@ -46,4 +46,4 @@ You may see the following status and corresponding description on the Solution p !!! caution - If a Solution is in the state of `create_failed`, `stop_failed`, or `start_failed`, you can execute `CREATE`, `STOP`, or `START` again. + If a Solution is in the state of **create_failed**, **stop_failed**, or **start_failed**, you can execute `CREATE`, `STOP`, or `START` again.