M3 Aggregator - Capabilities and Limitations
Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
Last updated January 19th, 2023
Objective
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.
Capabilities and limitations
Supported regions and multi-AZ
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.
M3 Aggregator versions
The Public Cloud Databases offer supports the following M3 aggregator versions:
- m3 aggregator 1.1
- m3 aggregator 1.2
Plans
Two plans are available:
- Business
- Enterprise
Here is an overview of the various plans' capabilities:
| Plan | Number of nodes by default | Additional nodes |
|---|---|---|
| Business | 3 | No |
| Enterprise | 6 | No |
Your choice of plan affects the number of nodes your cluster can run.
Nodes and replicas
- Business: The cluster is delivered with 3 nodes by default.
- Enterprise: The cluster is delivered with 6 nodes by default.
License type
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.
Hardware resources
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.
Features
Network
Public as well as private networking (vRack) can be used for all the offers.
Ingress and Egress traffic are included in the service plans and unmetered.
Private network considerations
Here are some considerations to take into account when using private network:
- 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.
- 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.
Logs and metrics
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.
- Logs retention: 1000 lines of logs
- Metrics retention: 1 calendar month
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
We want your feedback!
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/ovhcloud and interact directly with the team that builds our databases service!
Did you find this guide useful?
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.