-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs for basic tier and link updates #18340
Conversation
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -819,6 +809,25 @@ | |||
- interleave-in-parent.md | |||
- stable/interleave-in-parent.md | |||
|
|||
# Cloud 2.0 updates (Serverless/Dedicated to Basic/Standard/Advanced) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: I'd remove this comment before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant it as a header to help us add and track redirects more easily for Cloud 2.0
@@ -1,4 +1,4 @@ | |||
{% assign tab_names_html = "CockroachDB Serverless;CockroachDB Dedicated" %} | |||
{% assign html_page_filenames = "serverless-cluster-management.html;cluster-management.html" %} | |||
{% assign tab_names_html = "CockroachDB Basic;CockroachDB Standard;CockroachDB Advanced" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are going back to capitals for the tiers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assumed we'd follow the convention for the current tiers. I don't remember a discussion about not capitalizing tier names (or I might have missed it)
@@ -1,3 +1,3 @@ | |||
{{site.data.alerts.callout_info}} | |||
Organizations without billing information on file can only create one CockroachDB {{ site.data.products.serverless }} cluster. | |||
Organizations without billing information on file can only create one CockroachDB {{ site.data.products.basic }} cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we say "Organizations without a payment method configured can create only one...."? Not loving "billing information on file" but I understand it could be a credit card or a contract.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah this goes away after the new free trial is implemented anyways I think
@@ -36,7 +36,7 @@ However, 'legacy service accounts' that were created before the updated authoriz | |||
|
|||
To learn more, refer to [Manage Service Accounts]({{ link_prefix }})managing-access.html#manage-service-accounts) | |||
|
|||
#### CockroachDB {{ site.data.products.serverless }} cluster | |||
#### CockroachDB {{ site.data.products.basic }} cluster | |||
|
|||
A CockroachDB {{ site.data.products.cloud }} cluster deployed on request for a specific customer in *shared* network and compute infrastructure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the right terminology? Might be an opportunity to say "A CockroachDB cluster deployed on {{ site.data.products.cloud }} for a specific customer...." I don't think we want to say the type of cluster is a Cloud one -- it's actually a Basic one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah it can be either standard or basic (+ not focusing on existing content in this PR)
"title": "CockroachDB Advanced", | ||
"items": [ | ||
{ | ||
"title": "Plan a CockroachDB Dedicated Cluster", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Update the title?
|
||
Organizations without billing information on file can only create one cluster. Once you [set up billing information]({% link cockroachcloud/billing-management.md %}), your organization can have up to 200 clusters. | ||
|
||
### What is a Request Unit? | ||
|
||
With CockroachDB {{ site.data.products.serverless }}, you are charged for the storage and activity of your cluster. All cluster activity, including SQL queries, bulk operations, and background jobs, is measured in [Request Units]({% link cockroachcloud/plan-your-cluster-serverless.md %}#request-units), or RUs. An RU is an abstracted metric that represent the size and complexity of requests made to your cluster. See [Plan your CockroachDB {{ site.data.products.serverless }} Cluster]({% link cockroachcloud/plan-your-cluster-serverless.md %}#request-units) for more information. | ||
With CockroachDB {{ site.data.products.serverless }}, you are charged for the storage and activity of your cluster. All cluster activity, including SQL queries, bulk operations, and background jobs, is measured in [Request Units]({% link cockroachcloud/plan-your-cluster-basic.md %}#request-units), or RUs. An RU is an abstracted metric that represent the size and complexity of requests made to your cluster. See [Plan your CockroachDB {{ site.data.products.serverless }} Cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}#request-units) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Update the variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I had to leave the variables as is since I'm not updating this file in this PR. Only updating the links for now so they don't make the build fail. I know it's messy, but I'd rather look at each file holistically than change them piecemeal in multiple PRs
@@ -73,7 +73,7 @@ To connect to a cluster, download the CA certificate, and then generate a connec | |||
|
|||
### I created a CockroachCloud Free (beta) cluster before CockroachDB {{ site.data.products.serverless }} was available. Can I still use my cluster? | |||
|
|||
Yes, your free cluster has been automatically migrated to CockroachDB {{ site.data.products.serverless }}. Your ability to use your cluster should not be affected, and you will now have the option to [add resource limits]({% link cockroachcloud/serverless-cluster-management.md %}#edit-cluster-capacity) for your cluster with no downtime. | |||
Yes, your free cluster has been automatically migrated to CockroachDB {{ site.data.products.serverless }}. Your ability to use your cluster should not be affected, and you will now have the option to [add resource limits]({% link cockroachcloud/basic-cluster-management.md %}#edit-cluster-capacity) for your cluster with no downtime. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Update the variable?
@@ -22,7 +22,7 @@ To follow along with this tutorial you will need the following: | |||
|
|||
- The CockroachDB CLI [installed locally](install-cockroachdb-mac.html). | |||
- The Vault CLI [installed locally](https://www.vaultproject.io/downloads). | |||
- Access to a CockroachDB cluster as [`admin` SQL user](security-reference/authorization.html#admin-role). This tutorial will use a CockroachDB {{ site.data.products.serverless }} cluster, but you may either [Create a CockroachDB {{ site.data.products.serverless }} cluster](../cockroachcloud/create-a-serverless-cluster.html) or [Start a Local Cluster (secure)](start-a-local-cluster.html) in order to follow along. In either case you must have the public CA certificate for your cluster, and a username/password combination for the `root` SQL user (or another SQL user with the [`admin` role](security-reference/authorization.html#admin-role). | |||
- Access to a CockroachDB cluster as [`admin` SQL user](security-reference/authorization.html#admin-role). This tutorial will use a CockroachDB {{ site.data.products.serverless }} cluster, but you may either [Create a CockroachDB {{ site.data.products.serverless }} cluster](../cockroachcloud/create-a-basic-cluster.html) or [Start a Local Cluster (secure)](start-a-local-cluster.html) in order to follow along. In either case you must have the public CA certificate for your cluster, and a username/password combination for the `root` SQL user (or another SQL user with the [`admin` role](security-reference/authorization.html#admin-role). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Update the variable?
@@ -62,7 +62,7 @@ Property | Description | |||
`network usage` | The amount of data transferred over the network while the statement was executed. If the value is 0 B, the statement was executed on a single node and didn't use the network. | |||
`regions` | The [regions](show-regions.html) where the affected nodes were located. | |||
`max sql temp disk usage` | ([`DISTSQL`](#distsql-option) option only) How much disk spilling occurs when executing a query. This property is displayed only when the disk usage is greater than zero. | |||
`estimated RUs consumed` | The estimated number of [Request Units (RUs)](../cockroachcloud/plan-your-cluster-serverless.html#request-units) consumed by the statement. This property is visible only on CockroachDB {{ site.data.products.serverless }} clusters. | |||
`estimated RUs consumed` | The estimated number of [Request Units (RUs)](../cockroachcloud/plan-your-cluster-basic.html#request-units) consumed by the statement. This property is visible only on CockroachDB {{ site.data.products.serverless }} clusters. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Update the variable?
The deploy preview failure is due to several broken links. Might be worth |
@@ -819,6 +809,25 @@ | |||
- interleave-in-parent.md | |||
- stable/interleave-in-parent.md | |||
|
|||
# Cloud 2.0 updates (Serverless/Dedicated to Basic/Standard/Advanced) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant it as a header to help us add and track redirects more easily for Cloud 2.0
@@ -1,4 +1,4 @@ | |||
{% assign tab_names_html = "CockroachDB Serverless;CockroachDB Dedicated" %} | |||
{% assign html_page_filenames = "serverless-cluster-management.html;cluster-management.html" %} | |||
{% assign tab_names_html = "CockroachDB Basic;CockroachDB Standard;CockroachDB Advanced" %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assumed we'd follow the convention for the current tiers. I don't remember a discussion about not capitalizing tier names (or I might have missed it)
@@ -1,3 +1,3 @@ | |||
{{site.data.alerts.callout_info}} | |||
Organizations without billing information on file can only create one CockroachDB {{ site.data.products.serverless }} cluster. | |||
Organizations without billing information on file can only create one CockroachDB {{ site.data.products.basic }} cluster. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah this goes away after the new free trial is implemented anyways I think
@@ -36,7 +36,7 @@ However, 'legacy service accounts' that were created before the updated authoriz | |||
|
|||
To learn more, refer to [Manage Service Accounts]({{ link_prefix }})managing-access.html#manage-service-accounts) | |||
|
|||
#### CockroachDB {{ site.data.products.serverless }} cluster | |||
#### CockroachDB {{ site.data.products.basic }} cluster | |||
|
|||
A CockroachDB {{ site.data.products.cloud }} cluster deployed on request for a specific customer in *shared* network and compute infrastructure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah it can be either standard or basic (+ not focusing on existing content in this PR)
@@ -95,7 +95,54 @@ | |||
] | |||
}, | |||
{ | |||
"title": "CockroachDB Dedicated on Azure", | |||
"title": "Migrate from Serverless to Dedicated", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope -- only updated the sidebar entries for docs updated in this PR
|
||
Click **Next: Capacity**. | ||
|
||
## Step 4. Configure cluster capacity | ||
|
||
Your cluster's capacity dictates its [resource limits](https://www.cockroachlabs.com/docs/{{site.current_cloud_version}}/architecture/glossary#resource-limits), which are the maximum amount of storage and RUs you can use in a month. If you reach your storage limit, your cluster will be throttled and you may only be able to delete data. If you reach your RU limit, your cluster will be disabled until the end of the billing cycle unless you raise the limit. | ||
|
||
All CockroachDB {{ site.data.products.cloud }} organizations get 50M RUs and 10 GiB of storage for free each month. Free resources can be spent across all CockroachDB {{ site.data.products.serverless }} clusters in an organization. You can set higher resource limits to maintain a high level of performance with larger workloads. You will only be charged for what you use. | ||
All CockroachDB {{ site.data.products.cloud }} organizations get 50M RUs and 10 GiB of storage for free each month. Free resources can be spent across all CockroachDB {{ site.data.products.basic }} clusters in an organization. You can set higher resource limits to maintain a high level of performance with larger workloads. You will only be charged for what you use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, -- will handle it in April when I work on content updates
|
||
Organizations without billing information on file can only create one cluster. Once you [set up billing information]({% link cockroachcloud/billing-management.md %}), your organization can have up to 200 clusters. | ||
|
||
### What is a Request Unit? | ||
|
||
With CockroachDB {{ site.data.products.serverless }}, you are charged for the storage and activity of your cluster. All cluster activity, including SQL queries, bulk operations, and background jobs, is measured in [Request Units]({% link cockroachcloud/plan-your-cluster-serverless.md %}#request-units), or RUs. An RU is an abstracted metric that represent the size and complexity of requests made to your cluster. See [Plan your CockroachDB {{ site.data.products.serverless }} Cluster]({% link cockroachcloud/plan-your-cluster-serverless.md %}#request-units) for more information. | ||
With CockroachDB {{ site.data.products.serverless }}, you are charged for the storage and activity of your cluster. All cluster activity, including SQL queries, bulk operations, and background jobs, is measured in [Request Units]({% link cockroachcloud/plan-your-cluster-basic.md %}#request-units), or RUs. An RU is an abstracted metric that represent the size and complexity of requests made to your cluster. See [Plan your CockroachDB {{ site.data.products.serverless }} Cluster]({% link cockroachcloud/plan-your-cluster-basic.md %}#request-units) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I had to leave the variables as is since I'm not updating this file in this PR. Only updating the links for now so they don't make the build fail. I know it's messy, but I'd rather look at each file holistically than change them piecemeal in multiple PRs
Co-authored-by: Matt Linville (he/him) <linville@cockroachlabs.com>
In this PR: