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
Copy file name to clipboardExpand all lines: pages/public_cloud/public_cloud_databases/mirrormaker_01_capabilities/guide.de-de.md
+11-14Lines changed: 11 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
2
title: Kafka MirrorMaker - Capabilities and Limitations
3
-
excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka MirrorMaker
4
-
updated: 2025-07-31
3
+
excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka MirrorMaker
4
+
updated: 2025-08-04
5
5
---
6
6
7
7
## Objective
8
8
9
-
This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka MirrorMaker offer.
9
+
This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka MirrorMaker offer.
10
10
11
11
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
12
12
13
13
## Capabilities and limitations
14
14
15
15
### Supported regions and multi-AZ
16
16
17
-
The Public Cloud Databases offer is available in the following regions:
17
+
The Public Cloud Analytics offer is available in the following regions:
18
18
19
19
-`BHS` (Beauharnois, Canada)
20
20
-`DE` (Frankfurt, Germany)
@@ -29,7 +29,7 @@ Kafka MirrorMaker nodes have to be in the same region. Multi-AZ is currently not
29
29
30
30
### Kafka versions
31
31
32
-
The Public Cloud Databases offer supports the following Kafka versions:
32
+
The Public Cloud Analytics offer supports the following Kafka versions:
33
33
34
34
- Kafka MirrorMaker 3.7
35
35
- Kafka MirrorMaker 3.8
@@ -60,9 +60,6 @@ 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 as well as the SLA.
62
62
63
-
> [!primary]
64
-
> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
65
-
66
63
#### Nodes
67
64
68
65
-**Essential**: the cluster is delivered with 1 node by default.
@@ -85,13 +82,13 @@ Public as well as private networking (vRack) can be used for all the offers.
85
82
86
83
Ingress and Egress traffic are included in the service plans and unmetered.
87
84
88
-
The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
85
+
The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
89
86
90
87
##### Private network considerations
91
88
Here are some considerations to take into account when using private network:
92
89
93
-
- 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.
94
-
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
90
+
- 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 Analytics services first.
91
+
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the analytics service. The customer is responsible for any other custom network setup.
95
92
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
96
93
- OpenStack subnets routes announcement will not be applied to your services.
97
94
- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -129,12 +126,12 @@ Kafka is a streaming tool. We don't backup Kafka data.
129
126
130
127
#### Logs and metrics
131
128
132
-
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Public Cloud Databases - How to setup logs forwarding guide](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer).
129
+
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Analytics - How to setup logs forwarding](/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer).
133
130
134
131
-**Logs retention**: 1000 lines of logs
135
132
-**Metrics retention**: 1 calendar month
136
133
137
-
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
134
+
Please note that if the analytics instance is deleted, logs and metrics are also automatically deleted.
138
135
139
136
#### Users and roles
140
137
@@ -148,4 +145,4 @@ We would love to help answer questions and appreciate any feedback you may have.
148
145
149
146
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
150
147
151
-
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
148
+
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!
Copy file name to clipboardExpand all lines: pages/public_cloud/public_cloud_databases/mirrormaker_01_capabilities/guide.en-asia.md
+11-14Lines changed: 11 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
2
title: Kafka MirrorMaker - Capabilities and Limitations
3
-
excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka MirrorMaker
4
-
updated: 2025-07-31
3
+
excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka MirrorMaker
4
+
updated: 2025-08-04
5
5
---
6
6
7
7
## Objective
8
8
9
-
This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka MirrorMaker offer.
9
+
This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka MirrorMaker offer.
10
10
11
11
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
12
12
13
13
## Capabilities and limitations
14
14
15
15
### Supported regions and multi-AZ
16
16
17
-
The Public Cloud Databases offer is available in the following regions:
17
+
The Public Cloud Analytics offer is available in the following regions:
18
18
19
19
-`BHS` (Beauharnois, Canada)
20
20
-`DE` (Frankfurt, Germany)
@@ -29,7 +29,7 @@ Kafka MirrorMaker nodes have to be in the same region. Multi-AZ is currently not
29
29
30
30
### Kafka versions
31
31
32
-
The Public Cloud Databases offer supports the following Kafka versions:
32
+
The Public Cloud Analytics offer supports the following Kafka versions:
33
33
34
34
- Kafka MirrorMaker 3.7
35
35
- Kafka MirrorMaker 3.8
@@ -60,9 +60,6 @@ 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 as well as the SLA.
62
62
63
-
> [!primary]
64
-
> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
65
-
66
63
#### Nodes
67
64
68
65
-**Essential**: the cluster is delivered with 1 node by default.
@@ -85,13 +82,13 @@ Public as well as private networking (vRack) can be used for all the offers.
85
82
86
83
Ingress and Egress traffic are included in the service plans and unmetered.
87
84
88
-
The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
85
+
The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
89
86
90
87
##### Private network considerations
91
88
Here are some considerations to take into account when using private network:
92
89
93
-
- 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.
94
-
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
90
+
- 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 Analytics services first.
91
+
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the analytics service. The customer is responsible for any other custom network setup.
95
92
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
96
93
- OpenStack subnets routes announcement will not be applied to your services.
97
94
- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -129,12 +126,12 @@ Kafka is a streaming tool. We don't backup Kafka data.
129
126
130
127
#### Logs and metrics
131
128
132
-
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Public Cloud Databases - How to setup logs forwarding guide](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer).
129
+
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Analytics - How to setup logs forwarding](/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer).
133
130
134
131
-**Logs retention**: 1000 lines of logs
135
132
-**Metrics retention**: 1 calendar month
136
133
137
-
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
134
+
Please note that if the analytics instance is deleted, logs and metrics are also automatically deleted.
138
135
139
136
#### Users and roles
140
137
@@ -148,4 +145,4 @@ We would love to help answer questions and appreciate any feedback you may have.
148
145
149
146
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
150
147
151
-
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
148
+
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!
Copy file name to clipboardExpand all lines: pages/public_cloud/public_cloud_databases/mirrormaker_01_capabilities/guide.en-au.md
+11-14Lines changed: 11 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
---
2
2
title: Kafka MirrorMaker - Capabilities and Limitations
3
-
excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka MirrorMaker
4
-
updated: 2025-07-31
3
+
excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka MirrorMaker
4
+
updated: 2025-08-04
5
5
---
6
6
7
7
## Objective
8
8
9
-
This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka MirrorMaker offer.
9
+
This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka MirrorMaker offer.
10
10
11
11
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
12
12
13
13
## Capabilities and limitations
14
14
15
15
### Supported regions and multi-AZ
16
16
17
-
The Public Cloud Databases offer is available in the following regions:
17
+
The Public Cloud Analytics offer is available in the following regions:
18
18
19
19
-`BHS` (Beauharnois, Canada)
20
20
-`DE` (Frankfurt, Germany)
@@ -29,7 +29,7 @@ Kafka MirrorMaker nodes have to be in the same region. Multi-AZ is currently not
29
29
30
30
### Kafka versions
31
31
32
-
The Public Cloud Databases offer supports the following Kafka versions:
32
+
The Public Cloud Analytics offer supports the following Kafka versions:
33
33
34
34
- Kafka MirrorMaker 3.7
35
35
- Kafka MirrorMaker 3.8
@@ -60,9 +60,6 @@ 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 as well as the SLA.
62
62
63
-
> [!primary]
64
-
> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
65
-
66
63
#### Nodes
67
64
68
65
-**Essential**: the cluster is delivered with 1 node by default.
@@ -85,13 +82,13 @@ Public as well as private networking (vRack) can be used for all the offers.
85
82
86
83
Ingress and Egress traffic are included in the service plans and unmetered.
87
84
88
-
The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
85
+
The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
89
86
90
87
##### Private network considerations
91
88
Here are some considerations to take into account when using private network:
92
89
93
-
- 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.
94
-
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
90
+
- 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 Analytics services first.
91
+
- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the analytics service. The customer is responsible for any other custom network setup.
95
92
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
96
93
- OpenStack subnets routes announcement will not be applied to your services.
97
94
- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -129,12 +126,12 @@ Kafka is a streaming tool. We don't backup Kafka data.
129
126
130
127
#### Logs and metrics
131
128
132
-
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Public Cloud Databases - How to setup logs forwarding guide](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer).
129
+
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the [Analytics - How to setup logs forwarding](/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer).
133
130
134
131
-**Logs retention**: 1000 lines of logs
135
132
-**Metrics retention**: 1 calendar month
136
133
137
-
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
134
+
Please note that if the analytics instance is deleted, logs and metrics are also automatically deleted.
138
135
139
136
#### Users and roles
140
137
@@ -148,4 +145,4 @@ We would love to help answer questions and appreciate any feedback you may have.
148
145
149
146
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
150
147
151
-
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
148
+
Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!
0 commit comments