M3 Aggregator - Capabilities and Limitations
Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
Last updated July 13, 2022
This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 aggregator offer.
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.
The Public Cloud Databases offer is available in the following regions:
BHS
(Beauharnois, Canada)DE
(Frankfurt, Germany)GRA
(Gravelines, France)SBG
(Strasbourg, France)UK
(London, United Kingdom)WAW
(Warsaw, Poland)The entire database instances must be in the same region. Multi-AZ is currently not supported.
The Public Cloud Databases offer supports the following M3 aggregator versions:
Two plans are available:
Here is an overview of the various plans' capabilities:
Plan | Number of nodes by default | Additional nodes | Network |
---|---|---|---|
Business | 3 | No | Public & Private vRack |
Enterprise | 6 | No | Public & Private vRack |
Your choice of plan affects the number of nodes your cluster can run.
Each cluster is provided with the M3 Aggregator Community (GPL) license.
Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
Here are the node types you can choose from:
Business plans
Name | Disk (GB) | Cores | Memory (GB) |
---|---|---|---|
db1-7 | N/A | 2 | 7 |
db1-15 | N/A | 4 | 15 |
db1-30 | N/A | 8 | 30 |
db1-60 | N/A | 16 | 60 |
db1-120 | N/A | 32 | 120 |
Enterprise plans
Name | Disk (GB) | Cores | Memory (GB) |
---|---|---|---|
db1-15 | N/A | 4 | 15 |
db1-30 | N/A | 8 | 30 |
db1-60 | N/A | 16 | 60 |
db1-120 | N/A | 32 | 120 |
Right now, all nodes in a given cluster must be of the same type and located in the same region.
Public networking can be used for all the offers.
Private networking (vRack) is available for Business and Enterprise.
When using private networking, some network ports get created in the private network of your choice. Thus, further operations on that network might suffer from some restrictions - e.g. you won't be able to delete the network if you didn't stop the Public Cloud Databases services first.
Ingress and Egress traffic are included in the service plans and unmetered.
Logs and metrics are available via the OVHcloud Public Cloud Control Panel. As of today, you can't export logs and metrics, nor plug them into a remote tool.
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
We would love to help answer questions and appreciate any feedback you may have.
Are you on Discord? Connect to our channel at https://discord.gg/PwPqWUpN8G and interact directly with the team that builds our databases service!
Prima di inviare la valutazione, proponici dei suggerimenti per migliorare la documentazione.
Immagini, contenuti, struttura... Spiegaci perché, così possiamo migliorarla insieme!
Le richieste di assistenza non sono gestite con questo form. Se ti serve supporto, utilizza il form "Crea un ticket" .
Grazie per averci inviato il tuo feedback.
Accedi al tuo spazio nella Community Fai domande, cerca informazioni, pubblica contenuti e interagisci con gli altri membri della Community OVHcloud
Discuss with the OVHcloud community