Skip to content

Commit 0ccb132

Browse files
thild42thild42
committed
Update M3 Aggregator capabilities guide
1 parent c959c37 commit 0ccb132

File tree

15 files changed

+465
-346
lines changed

15 files changed

+465
-346
lines changed

‎pages/platform/databases/m3aggregator_01_capabilities/guide.de-de.md

Lines changed: 31 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ section: M3 Aggregator - Guides
66
order: 010
77
routes:
88
canonical: 'https://docs.ovh.com/gb/en/publiccloud/databases/m3aggregator/capabilities/'
9-
updated: 2023-01-19
9+
updated: 2023-04-24
1010
---
1111

12-
**Last updated January 19th, 2023**
12+
**Last updated April 24th, 2023**
1313

1414
## Objective
1515

16-
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 aggregator offer.
16+
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
1717

1818
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/ovh/public-cloud-roadmap/projects/2>.
1919

@@ -34,11 +34,13 @@ The entire database instances must be in the same region. Multi-AZ is currently
3434

3535
### M3 Aggregator versions
3636

37-
The Public Cloud Databases offer supports the following M3 aggregator versions:
37+
The Public Cloud Databases offer supports the following M3 Aggregator versions:
3838

39-
- m3 aggregator 1.1
40-
- m3 aggregator 1.2
39+
- M3 Aggregator 1.1
40+
- M3 Aggregator 1.2
41+
- M3 Aggregator 1.5
4142

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.
4244

4345
### Plans
4446

@@ -56,10 +58,13 @@ Here is an overview of the various plans' capabilities:
5658

5759
Your choice of plan affects the number of nodes your cluster can run.
5860

61+
> [!primary]
62+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
63+
5964
#### Nodes and replicas
6065

61-
- **Business**: The cluster is delivered with 3 nodes by default.
62-
- **Enterprise**: The cluster is delivered with 6 nodes by default.
66+
- **Business**: the cluster is delivered with 3 nodes by default.
67+
- **Enterprise**: the cluster is delivered with 6 nodes by default.
6368

6469
#### License type
6570

@@ -73,23 +78,23 @@ Here are the node types you can choose from:
7378

7479
**Business plans**
7580

76-
| Name | Disk (GB) | Cores | Memory (GB) |
77-
| ------- | --------- | ----- | ----------- |
78-
| db1-7 | N/A | 2 | 7 |
79-
| db1-15 | N/A | 4 | 15 |
80-
| db1-30 | N/A | 8 | 30 |
81-
| db1-60 | N/A | 16 | 60 |
82-
| db1-120 | N/A | 32 | 120 |
81+
| Name | Storage | vCore | Memory (GB) |
82+
| ------- | ------- | ----- | ----------- |
83+
| db1-7 | N/A | 2 | 7 |
84+
| db1-15 | N/A | 4 | 15 |
85+
| db1-30 | N/A | 8 | 30 |
86+
| db1-60 | N/A | 16 | 60 |
87+
| db1-120 | N/A | 32 | 120 |
8388

8489

8590
**Enterprise plans**
8691

87-
| Name | Disk (GB) | Cores | Memory (GB) |
88-
| ------- | --------- | ----- | ----------- |
89-
| db1-15 | N/A | 4 | 15 |
90-
| db1-30 | N/A | 8 | 30 |
91-
| db1-60 | N/A | 16 | 60 |
92-
| db1-120 | N/A | 32 | 120 |
92+
| Name | Storage | vCore | Memory (GB) |
93+
| ------- | ------- | ----- | ----------- |
94+
| db1-15 | N/A | 4 | 15 |
95+
| db1-30 | N/A | 8 | 30 |
96+
| db1-60 | N/A | 16 | 60 |
97+
| db1-120 | N/A | 32 | 120 |
9398

9499
Right now, all nodes in a given cluster must be of the same type and located in the same region.
95100

@@ -107,10 +112,13 @@ Here are some considerations to take into account when using private network:
107112
- 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.
108113
- 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.
109114

115+
##### Authorised IPs
116+
117+
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.
118+
110119
#### Logs and metrics
111120

112-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
113-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
121+
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 M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
114122

115123
- **Logs retention**: 1000 lines of logs
116124
- **Metrics retention**: 1 calendar month

‎pages/platform/databases/m3aggregator_01_capabilities/guide.en-asia.md

Lines changed: 31 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@ slug: m3aggregator/capabilities
44
excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
55
section: M3 Aggregator - Guides
66
order: 010
7-
updated: 2023-01-19
7+
updated: 2023-04-24
88
---
99

10-
**Last updated January 19th, 2023**
10+
**Last updated April 24th, 2023**
1111

1212
## Objective
1313

14-
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 aggregator offer.
14+
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
1515

1616
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/ovh/public-cloud-roadmap/projects/2>.
1717

@@ -32,11 +32,13 @@ The entire database instances must be in the same region. Multi-AZ is currently
3232

3333
### M3 Aggregator versions
3434

35-
The Public Cloud Databases offer supports the following M3 aggregator versions:
35+
The Public Cloud Databases offer supports the following M3 Aggregator versions:
3636

37-
- m3 aggregator 1.1
38-
- m3 aggregator 1.2
37+
- M3 Aggregator 1.1
38+
- M3 Aggregator 1.2
39+
- M3 Aggregator 1.5
3940

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.
4042

4143
### Plans
4244

@@ -54,10 +56,13 @@ Here is an overview of the various plans' capabilities:
5456

5557
Your choice of plan affects the number of nodes your cluster can run.
5658

59+
> [!primary]
60+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
61+
5762
#### Nodes and replicas
5863

59-
- **Business**: The cluster is delivered with 3 nodes by default.
60-
- **Enterprise**: The cluster is delivered with 6 nodes by default.
64+
- **Business**: the cluster is delivered with 3 nodes by default.
65+
- **Enterprise**: the cluster is delivered with 6 nodes by default.
6166

6267
#### License type
6368

@@ -71,23 +76,23 @@ Here are the node types you can choose from:
7176

7277
**Business plans**
7378

74-
| Name | Disk (GB) | Cores | Memory (GB) |
75-
| ------- | --------- | ----- | ----------- |
76-
| db1-7 | N/A | 2 | 7 |
77-
| db1-15 | N/A | 4 | 15 |
78-
| db1-30 | N/A | 8 | 30 |
79-
| db1-60 | N/A | 16 | 60 |
80-
| db1-120 | N/A | 32 | 120 |
79+
| Name | Storage | vCore | Memory (GB) |
80+
| ------- | ------- | ----- | ----------- |
81+
| db1-7 | N/A | 2 | 7 |
82+
| db1-15 | N/A | 4 | 15 |
83+
| db1-30 | N/A | 8 | 30 |
84+
| db1-60 | N/A | 16 | 60 |
85+
| db1-120 | N/A | 32 | 120 |
8186

8287

8388
**Enterprise plans**
8489

85-
| Name | Disk (GB) | Cores | Memory (GB) |
86-
| ------- | --------- | ----- | ----------- |
87-
| db1-15 | N/A | 4 | 15 |
88-
| db1-30 | N/A | 8 | 30 |
89-
| db1-60 | N/A | 16 | 60 |
90-
| db1-120 | N/A | 32 | 120 |
90+
| Name | Storage | vCore | Memory (GB) |
91+
| ------- | ------- | ----- | ----------- |
92+
| db1-15 | N/A | 4 | 15 |
93+
| db1-30 | N/A | 8 | 30 |
94+
| db1-60 | N/A | 16 | 60 |
95+
| db1-120 | N/A | 32 | 120 |
9196

9297
Right now, all nodes in a given cluster must be of the same type and located in the same region.
9398

@@ -105,10 +110,13 @@ Here are some considerations to take into account when using private network:
105110
- 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.
106111
- 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.
107112

113+
##### Authorised IPs
114+
115+
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.
116+
108117
#### Logs and metrics
109118

110-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
111-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
119+
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 M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
112120

113121
- **Logs retention**: 1000 lines of logs
114122
- **Metrics retention**: 1 calendar month

‎pages/platform/databases/m3aggregator_01_capabilities/guide.en-au.md

Lines changed: 31 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@ slug: m3aggregator/capabilities
44
excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
55
section: M3 Aggregator - Guides
66
order: 010
7-
updated: 2023-01-19
7+
updated: 2023-04-24
88
---
99

10-
**Last updated January 19th, 2023**
10+
**Last updated April 24th, 2023**
1111

1212
## Objective
1313

14-
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 aggregator offer.
14+
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
1515

1616
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/ovh/public-cloud-roadmap/projects/2>.
1717

@@ -32,11 +32,13 @@ The entire database instances must be in the same region. Multi-AZ is currently
3232

3333
### M3 Aggregator versions
3434

35-
The Public Cloud Databases offer supports the following M3 aggregator versions:
35+
The Public Cloud Databases offer supports the following M3 Aggregator versions:
3636

37-
- m3 aggregator 1.1
38-
- m3 aggregator 1.2
37+
- M3 Aggregator 1.1
38+
- M3 Aggregator 1.2
39+
- M3 Aggregator 1.5
3940

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.
4042

4143
### Plans
4244

@@ -54,10 +56,13 @@ Here is an overview of the various plans' capabilities:
5456

5557
Your choice of plan affects the number of nodes your cluster can run.
5658

59+
> [!primary]
60+
> Be aware that you will be able to upgrade your plan but will not be able to downgrade it afterwards.
61+
5762
#### Nodes and replicas
5863

59-
- **Business**: The cluster is delivered with 3 nodes by default.
60-
- **Enterprise**: The cluster is delivered with 6 nodes by default.
64+
- **Business**: the cluster is delivered with 3 nodes by default.
65+
- **Enterprise**: the cluster is delivered with 6 nodes by default.
6166

6267
#### License type
6368

@@ -71,23 +76,23 @@ Here are the node types you can choose from:
7176

7277
**Business plans**
7378

74-
| Name | Disk (GB) | Cores | Memory (GB) |
75-
| ------- | --------- | ----- | ----------- |
76-
| db1-7 | N/A | 2 | 7 |
77-
| db1-15 | N/A | 4 | 15 |
78-
| db1-30 | N/A | 8 | 30 |
79-
| db1-60 | N/A | 16 | 60 |
80-
| db1-120 | N/A | 32 | 120 |
79+
| Name | Storage | vCore | Memory (GB) |
80+
| ------- | ------- | ----- | ----------- |
81+
| db1-7 | N/A | 2 | 7 |
82+
| db1-15 | N/A | 4 | 15 |
83+
| db1-30 | N/A | 8 | 30 |
84+
| db1-60 | N/A | 16 | 60 |
85+
| db1-120 | N/A | 32 | 120 |
8186

8287

8388
**Enterprise plans**
8489

85-
| Name | Disk (GB) | Cores | Memory (GB) |
86-
| ------- | --------- | ----- | ----------- |
87-
| db1-15 | N/A | 4 | 15 |
88-
| db1-30 | N/A | 8 | 30 |
89-
| db1-60 | N/A | 16 | 60 |
90-
| db1-120 | N/A | 32 | 120 |
90+
| Name | Storage | vCore | Memory (GB) |
91+
| ------- | ------- | ----- | ----------- |
92+
| db1-15 | N/A | 4 | 15 |
93+
| db1-30 | N/A | 8 | 30 |
94+
| db1-60 | N/A | 16 | 60 |
95+
| db1-120 | N/A | 32 | 120 |
9196

9297
Right now, all nodes in a given cluster must be of the same type and located in the same region.
9398

@@ -105,10 +110,13 @@ Here are some considerations to take into account when using private network:
105110
- 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.
106111
- 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.
107112

113+
##### Authorised IPs
114+
115+
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.
116+
108117
#### Logs and metrics
109118

110-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
111-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
119+
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 M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](https://docs.ovh.com/gb/en/publiccloud/databases/cross-service-integration/) for more information.
112120

113121
- **Logs retention**: 1000 lines of logs
114122
- **Metrics retention**: 1 calendar month

0 commit comments

Comments
 (0)