1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// SPDX-License-Identifier: Apache-2.0
//! Block storage Cluster commands
//!
use ;
use crate::;
use AsyncOpenStack;
/// Clusters (clusters)
///
/// Administrator only. Lists all Cinder clusters, show cluster detail, enable or disable a
/// cluster.
///
/// Each cinder service runs on a host computer (possibly multiple services on the same host; it
/// depends how you decide to deploy cinder). In order to support High Availability scenarios,
/// services can be grouped into clusters where the same type of service (for example,
/// cinder-volume) can run on different hosts so that if one host goes down the service is still
/// available on a different host. Since there’s no point having these services sitting around
/// doing nothing while waiting for some other host to go down (which is also known as
/// Active/Passive mode), grouping services into clusters also allows cinder to support
/// Active/Active mode in which all services in a cluster are doing work all the time.
///
///
/// **Note**: Currently the only service that can be grouped into clusters is cinder-volume.
///
/// Clusters are determined by the deployment configuration; that’s why there is no
/// ‘create-cluster’ API call listed below. Once your services are up and running, however, you can
/// use the following API requests to get information about your clusters and to update their
/// status.
/// Supported subcommands