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
Right now, all nodes of a given cluster should be of the same type and live in the same region.
108
109
110
+
#### Flexible storage
111
+
112
+
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.
113
+
114
+
#### Node template upgrade
115
+
116
+
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.
117
+
109
118
#### Disk type
110
119
111
120
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.
@@ -114,6 +123,17 @@ Also, the performance caracteristics of the various storage offerings may vary d
114
123
115
124
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
116
125
126
+
#### Effective storage
127
+
128
+
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
129
+
130
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
131
+
132
+
1. When reaching a concerning level of disk usage, a warning email is sent.
133
+
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.
134
+
135
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/de/publiccloud/databases/handling-disk-full/) for more information.
136
+
117
137
### Features
118
138
119
139
#### Network
@@ -127,10 +147,17 @@ Here are some considerations to take into account when using private network:
127
147
- 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.
128
148
- 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.
129
149
150
+
##### Authorised IPs
151
+
152
+
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.
153
+
154
+
#### Advanced parameters
155
+
156
+
You can customize your Cassandra further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/de/publiccloud/databases/cassandra/advanced-parameters-references/) for more information about which ones are supported.
157
+
130
158
#### Logs and metrics
131
159
132
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
133
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
160
+
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 Cassandra 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.
Right now, all nodes of a given cluster should be of the same type and live in the same region.
102
103
104
+
#### Flexible storage
105
+
106
+
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.
107
+
108
+
#### Node template upgrade
109
+
110
+
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.
111
+
103
112
#### Disk type
104
113
105
114
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.
@@ -108,6 +117,17 @@ Also, the performance caracteristics of the various storage offerings may vary d
108
117
109
118
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
110
119
120
+
#### Effective storage
121
+
122
+
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
123
+
124
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
125
+
126
+
1. When reaching a concerning level of disk usage, a warning email is sent.
127
+
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.
128
+
129
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/asia/en/publiccloud/databases/handling-disk-full/) for more information.
130
+
111
131
### Features
112
132
113
133
#### Network
@@ -121,10 +141,17 @@ Here are some considerations to take into account when using private network:
121
141
- 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.
122
142
- 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.
123
143
144
+
##### Authorised IPs
145
+
146
+
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.
147
+
148
+
#### Advanced parameters
149
+
150
+
You can customize your Cassandra further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/asia/en/publiccloud/databases/cassandra/advanced-parameters-references/) for more information about which ones are supported.
151
+
124
152
#### Logs and metrics
125
153
126
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
127
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
154
+
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 Cassandra 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.
Right now, all nodes of a given cluster should be of the same type and live in the same region.
102
103
104
+
#### Flexible storage
105
+
106
+
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.
107
+
108
+
#### Node template upgrade
109
+
110
+
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.
111
+
103
112
#### Disk type
104
113
105
114
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.
@@ -108,6 +117,17 @@ Also, the performance caracteristics of the various storage offerings may vary d
108
117
109
118
Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
110
119
120
+
#### Effective storage
121
+
122
+
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
123
+
124
+
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
125
+
126
+
1. When reaching a concerning level of disk usage, a warning email is sent.
127
+
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.
128
+
129
+
See the [Handling «Disk Full» situations documentation](https://docs.ovh.com/au/en/publiccloud/databases/handling-disk-full/) for more information.
130
+
111
131
### Features
112
132
113
133
#### Network
@@ -121,10 +141,17 @@ Here are some considerations to take into account when using private network:
121
141
- 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.
122
142
- 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.
123
143
144
+
##### Authorised IPs
145
+
146
+
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.
147
+
148
+
#### Advanced parameters
149
+
150
+
You can customize your Cassandra further through the use of advanced parameters. See the [Advanced parameters references documentation](https://docs.ovh.com/au/en/publiccloud/databases/cassandra/advanced-parameters-references/) for more information about which ones are supported.
151
+
124
152
#### Logs and metrics
125
153
126
-
Logs and metrics are available via the OVHcloud Public Cloud Control Panel.
127
-
As of today, you can't export logs and metrics, nor plug them into a remote tool.
154
+
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 Cassandra 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