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
@@ -38,7 +38,7 @@ The Public Cloud Databases offer supports the following MySQL versions:
38
38
39
39
- MySQL 8.0
40
40
41
-
MySQL recommends always installing and using the latest stable version.
41
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/de/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. MySQL recommends always installing and using the latest stable version.
42
42
43
43
### MySQL connectors
44
44
@@ -62,6 +62,9 @@ Here is an overview of the various plans' capabilities:
62
62
63
63
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.
64
64
65
+
> [!primary]
66
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
67
+
65
68
#### Nodes and replicas
66
69
67
70
-**Essential**: the cluster can support at most one node.
@@ -78,16 +81,25 @@ If any, license cost is included inside the service plans. You can't bring your
Right now, all nodes of a given cluster should be of the same type and live in the same region.
90
94
95
+
#### Flexible storage
96
+
97
+
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/de/publiccloud/databases/resize-cluster-storage/) for more information.
98
+
99
+
#### Node template upgrade
100
+
101
+
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.
102
+
91
103
#### Disk type
92
104
93
105
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.
@@ -102,8 +114,11 @@ The disk size listed above is the total disk size of the underlying machine. How
102
114
103
115
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
104
116
105
-
1. When reaching 97% capacity, the customer will have his database instance moved in "DISK_FULL" state, and 'read-only" mode, meaning no more writes can be done.
106
-
2. You then have the ability to upgrade to a higher service plan with more storage.
117
+
1. When reaching a concerning level of disk usage, a warning email is sent.
118
+
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.
119
+
3. You then have the ability to upgrade to a higher service plan with more storage.
120
+
121
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/de/publiccloud/databases/handling-disk-full/) for more information.
107
122
108
123
### Features
109
124
@@ -120,7 +135,11 @@ Here are some considerations to take into account when using private network:
120
135
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
121
136
- 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.
122
137
138
+
##### Authorised IPs
139
+
140
+
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. ##### Authorised IPs
123
141
142
+
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.
124
143
125
144
#### Maximum simultaneous connections
126
145
@@ -132,7 +151,7 @@ Note that the MySQL max-connections setting is always set to one higher (e.g. 52
132
151
133
152
#### Advanced parameters
134
153
135
-
We do not currently support MySQL advanced parameters.
154
+
You can customize your MySQL further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/de/publiccloud/databases/mysql/advanced-parameters-references/) for more information about which ones are supported.
136
155
137
156
#### Backups
138
157
@@ -144,8 +163,7 @@ We do not currently support MySQL advanced parameters.
144
163
145
164
#### Logs and metrics
146
165
147
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
148
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
166
+
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 MySQL logs in Opensearch and metrics in Grafana (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](https://docs.ovh.com/de/publiccloud/databases/cross-service-integration/) for more information.
Copy file name to clipboardExpand all lines: pages/platform/databases/mysql_01_capabilities/guide.en-asia.md
+33-15Lines changed: 33 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ slug: mysql/capabilities
4
4
excerpt: Discover the capabilities and limitations of Public Cloud Databases for MySQL
5
5
section: MySQL - Guides
6
6
order: 010
7
-
updated: 2023-01-19
7
+
updated: 2023-04-14
8
8
---
9
9
10
-
**Last updated January 19th, 2023**
10
+
**Last updated April 14th, 2023**
11
11
12
12
## Objective
13
13
@@ -36,7 +36,7 @@ The Public Cloud Databases offer supports the following MySQL versions:
36
36
37
37
- MySQL 8.0
38
38
39
-
MySQL recommends always installing and using the latest stable version.
39
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/asia/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. MySQL recommends always installing and using the latest stable version.
40
40
41
41
### MySQL connectors
42
42
@@ -60,6 +60,9 @@ Here is an overview of the various plans' capabilities:
60
60
61
61
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.
62
62
63
+
> [!primary]
64
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
65
+
63
66
#### Nodes and replicas
64
67
65
68
-**Essential**: the cluster can support at most one node.
@@ -76,16 +79,25 @@ If any, license cost is included inside the service plans. You can't bring your
Right now, all nodes of a given cluster should be of the same type and live in the same region.
88
92
93
+
#### Flexible storage
94
+
95
+
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/asia/en/publiccloud/databases/resize-cluster-storage/) for more information.
96
+
97
+
#### Node template upgrade
98
+
99
+
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.
100
+
89
101
#### Disk type
90
102
91
103
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.
@@ -100,8 +112,11 @@ The disk size listed above is the total disk size of the underlying machine. How
100
112
101
113
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
102
114
103
-
1. When reaching 97% capacity, the customer will have his database instance moved in "DISK_FULL" state, and 'read-only" mode, meaning no more writes can be done.
104
-
2. You then have the ability to upgrade to a higher service plan with more storage.
115
+
1. When reaching a concerning level of disk usage, a warning email is sent.
116
+
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.
117
+
3. You then have the ability to upgrade to a higher service plan with more storage.
118
+
119
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/asia/en/publiccloud/databases/handling-disk-full/) for more information.
105
120
106
121
### Features
107
122
@@ -118,7 +133,11 @@ Here are some considerations to take into account when using private network:
118
133
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
119
134
- 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.
120
135
136
+
##### Authorised IPs
137
+
138
+
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. ##### Authorised IPs
121
139
140
+
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.
122
141
123
142
#### Maximum simultaneous connections
124
143
@@ -130,7 +149,7 @@ Note that the MySQL max-connections setting is always set to one higher (e.g. 52
130
149
131
150
#### Advanced parameters
132
151
133
-
We do not currently support MySQL advanced parameters.
152
+
You can customize your MySQL further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/asia/en/publiccloud/databases/mysql/advanced-parameters-references/) for more information about which ones are supported.
134
153
135
154
#### Backups
136
155
@@ -142,8 +161,7 @@ We do not currently support MySQL advanced parameters.
142
161
143
162
#### Logs and metrics
144
163
145
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
146
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
164
+
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 MySQL logs in Opensearch and metrics in Grafana (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](https://docs.ovh.com/asia/en/publiccloud/databases/cross-service-integration/) for more information.
Copy file name to clipboardExpand all lines: pages/platform/databases/mysql_01_capabilities/guide.en-au.md
+33-15Lines changed: 33 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,10 @@ slug: mysql/capabilities
4
4
excerpt: Discover the capabilities and limitations of Public Cloud Databases for MySQL
5
5
section: MySQL - Guides
6
6
order: 010
7
-
updated: 2023-01-19
7
+
updated: 2023-04-14
8
8
---
9
9
10
-
**Last updated January 19th, 2023**
10
+
**Last updated April 14th, 2023**
11
11
12
12
## Objective
13
13
@@ -36,7 +36,7 @@ The Public Cloud Databases offer supports the following MySQL versions:
36
36
37
37
- MySQL 8.0
38
38
39
-
MySQL recommends always installing and using the latest stable version.
39
+
Please refer to the [DBMS lifecycle policy guide](https://docs.ovh.com/au/en/publiccloud/databases/lifecycle-policy/) for recommendations on version upgrades and end of life announcements of major versions. MySQL recommends always installing and using the latest stable version.
40
40
41
41
### MySQL connectors
42
42
@@ -60,6 +60,9 @@ Here is an overview of the various plans' capabilities:
60
60
61
61
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.
62
62
63
+
> [!primary]
64
+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
65
+
63
66
#### Nodes and replicas
64
67
65
68
-**Essential**: the cluster can support at most one node.
@@ -76,16 +79,25 @@ If any, license cost is included inside the service plans. You can't bring your
Right now, all nodes of a given cluster should be of the same type and live in the same region.
88
92
93
+
#### Flexible storage
94
+
95
+
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/au/en/publiccloud/databases/resize-cluster-storage/) for more information.
96
+
97
+
#### Node template upgrade
98
+
99
+
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.
100
+
89
101
#### Disk type
90
102
91
103
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/en-au/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.
@@ -100,8 +112,11 @@ The disk size listed above is the total disk size of the underlying machine. How
100
112
101
113
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
102
114
103
-
1. When reaching 97% capacity, the customer will have his database instance moved in "DISK_FULL" state, and 'read-only" mode, meaning no more writes can be done.
104
-
2. You then have the ability to upgrade to a higher service plan with more storage.
115
+
1. When reaching a concerning level of disk usage, a warning email is sent.
116
+
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.
117
+
3. You then have the ability to upgrade to a higher service plan with more storage.
118
+
119
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/au/en/publiccloud/databases/handling-disk-full/) for more information.
105
120
106
121
### Features
107
122
@@ -118,7 +133,11 @@ Here are some considerations to take into account when using private network:
118
133
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
119
134
- 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.
120
135
136
+
##### Authorised IPs
137
+
138
+
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. ##### Authorised IPs
121
139
140
+
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.
122
141
123
142
#### Maximum simultaneous connections
124
143
@@ -130,7 +149,7 @@ Note that the MySQL max-connections setting is always set to one higher (e.g. 52
130
149
131
150
#### Advanced parameters
132
151
133
-
We do not currently support MySQL advanced parameters.
152
+
You can customize your MySQL further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/au/en/publiccloud/databases/mysql/advanced-parameters-references/) for more information about which ones are supported.
134
153
135
154
#### Backups
136
155
@@ -142,8 +161,7 @@ We do not currently support MySQL advanced parameters.
142
161
143
162
#### Logs and metrics
144
163
145
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
146
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
164
+
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 MySQL logs in Opensearch and metrics in Grafana (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](https://docs.ovh.com/au/en/publiccloud/databases/cross-service-integration/) for more information.
0 commit comments