You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -32,13 +32,15 @@ The Public Cloud Databases offer is available in the following regions:
32
32
33
33
Entire database instances have to be in the same region. Multi-AZ is currently not supported.
34
34
35
-
### M3db versions
35
+
### M3DB versions
36
36
37
37
The Public Cloud Databases offer supports the following m3db versions:
38
38
39
39
- m3db 1.1
40
+
- m3db 1.2
41
+
- m3db 1.5
40
42
41
-
m3db recommends always installing and using the latest stable version.
43
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/gb/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. M3DB recommends always installing and using the latest stable version.
42
44
43
45
44
46
### Plans
@@ -59,11 +61,14 @@ Here is an overview of the various plans' capabilities:
59
61
60
62
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
61
63
64
+
> [!primary]
65
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
66
+
62
67
#### Nodes and replicas
63
68
64
-
-**Essential**: The cluster can support at most one node.
65
-
-**Business**: The cluster is delivered with 2 nodes by default. Adding read replicas is planned.
66
-
-**Enterprise**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned.
69
+
-**Essential**: the cluster can support at most one node.
70
+
-**Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
71
+
-**Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
67
72
68
73
#### License type
69
74
@@ -77,35 +82,41 @@ Here are the node types you can choose from:
Right now, all nodes of a given cluster should be of the same type and live in the same region.
108
111
112
+
#### Flexible storage
113
+
114
+
You can increased the storage of your cluster up to the maximum allowed for a given reference. Please refer to the [Resize your cluster storage guide](https://docs.ovh.com/gb/en/publiccloud/databases/resize-cluster-storage/) for more information.
115
+
116
+
#### Node template upgrade
117
+
118
+
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
119
+
109
120
#### Disk type
110
121
111
122
The type of storage available may vary according to the region your cluster lives in: see [Availability of Public Cloud products](https://www.ovhcloud.com/de/public-cloud/regions-availability/) for more information about block storage type availability depending on region. Thus, your cluster may be backed by e.g. *High Speed* or *High Speed Gen2* block storage.
@@ -114,6 +125,18 @@ Also, the performance caracteristics of the various storage offerings may vary d
114
125
115
126
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
116
127
128
+
#### Effective storage
129
+
130
+
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
131
+
132
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
133
+
134
+
1. When reaching a concerning level of disk usage, a warning email is sent.
135
+
2. When reaching a concerning level of disk usage, the service is moved in the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
136
+
3. You then have the ability to upgrade to a higher service plan with more storage.
137
+
138
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/gb/en/publiccloud/databases/handling-disk-full/) for more information.
139
+
117
140
### Features
118
141
119
142
#### Network
@@ -128,10 +151,13 @@ Here are some considerations to take into account when using private network:
128
151
- When connecting from outside subnet, Openstack IP gateway must be enabled in the subnet use for the Database service. The customer is responsible for any other custom network setup.
129
152
130
153
154
+
##### Authorised IPs
155
+
156
+
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic, until then your service will be unreachable.
157
+
131
158
#### Logs and metrics
132
159
133
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
134
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
160
+
Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration could be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3DB logs in Opensearch and metrics in Grafana. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
Copy file name to clipboardExpand all lines: pages/platform/databases/m3db_01_capabilities/guide.en-asia.md
+56-30Lines changed: 56 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ slug: m3db/capabilities
4
4
excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
5
5
section: M3db - Guides
6
6
order: 010
7
-
updated: 2023-01-19
7
+
updated: 2023-04-22
8
8
---
9
9
10
-
**Last updated January 19th, 2023**
10
+
**Last updated April 22nd, 2023**
11
11
12
12
## Objective
13
13
@@ -30,13 +30,15 @@ The Public Cloud Databases offer is available in the following regions:
30
30
31
31
Entire database instances have to be in the same region. Multi-AZ is currently not supported.
32
32
33
-
### M3db versions
33
+
### M3DB versions
34
34
35
35
The Public Cloud Databases offer supports the following m3db versions:
36
36
37
37
- m3db 1.1
38
+
- m3db 1.2
39
+
- m3db 1.5
38
40
39
-
m3db recommends always installing and using the latest stable version.
41
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/gb/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. M3DB recommends always installing and using the latest stable version.
40
42
41
43
42
44
### Plans
@@ -57,11 +59,14 @@ Here is an overview of the various plans' capabilities:
57
59
58
60
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
59
61
62
+
> [!primary]
63
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
64
+
60
65
#### Nodes and replicas
61
66
62
-
-**Essential**: The cluster can support at most one node.
63
-
-**Business**: The cluster is delivered with 2 nodes by default. Adding read replicas is planned.
64
-
-**Enterprise**: The cluster is delivered with 3 nodes by default. Adding read replicas is planned.
67
+
-**Essential**: the cluster can support at most one node.
68
+
-**Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
69
+
-**Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
65
70
66
71
#### License type
67
72
@@ -75,35 +80,41 @@ Here are the node types you can choose from:
Right now, all nodes of a given cluster should be of the same type and live in the same region.
106
109
110
+
#### Flexible storage
111
+
112
+
You can increased the storage of your cluster up to the maximum allowed for a given reference. Please refer to the [Resize your cluster storage guide](https://docs.ovh.com/gb/en/publiccloud/databases/resize-cluster-storage/) for more information.
113
+
114
+
#### Node template upgrade
115
+
116
+
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
117
+
107
118
#### Disk type
108
119
109
120
The type of storage available may vary according to the region your cluster lives in: see [Availability of Public Cloud products](https://www.ovhcloud.com/asia/public-cloud/regions-availability/) for more information about block storage type availability depending on region. Thus, your cluster may be backed by e.g. *High Speed* or *High Speed Gen2* block storage.
@@ -112,6 +123,18 @@ Also, the performance caracteristics of the various storage offerings may vary d
112
123
113
124
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
114
125
126
+
#### Effective storage
127
+
128
+
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
129
+
130
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
131
+
132
+
1. When reaching a concerning level of disk usage, a warning email is sent.
133
+
2. When reaching a concerning level of disk usage, the service is moved in the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
134
+
3. You then have the ability to upgrade to a higher service plan with more storage.
135
+
136
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/gb/en/publiccloud/databases/handling-disk-full/) for more information.
137
+
115
138
### Features
116
139
117
140
#### Network
@@ -126,10 +149,13 @@ Here are some considerations to take into account when using private network:
126
149
- When connecting from outside subnet, Openstack IP gateway must be enabled in the subnet use for the Database service. The customer is responsible for any other custom network setup.
127
150
128
151
152
+
##### Authorised IPs
153
+
154
+
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic, until then your service will be unreachable.
155
+
129
156
#### Logs and metrics
130
157
131
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
132
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
158
+
Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration could be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3DB logs in Opensearch and metrics in Grafana. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
0 commit comments