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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
..
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.
.. _ref-bindings:
=======================
Cluster-Policy Bindings
=======================
Concept
~~~~~~~
A :term:`Policy` object can be attached to at least one :term:`Cluster` at the
same time. A cluster at any time can have more than one Policy objects
attached to it.
After a policy object is attached to a cluster, you can still enable or
disable it or update some properties of the policy object.
Listing Policies Attached to a Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The :program:`openstack cluster` command provides a sub-command
:command:`policy binding list` to list policy objects that are attached to a
cluster. You can provide the name, the ID or the "short ID" of a cluster as
the identifier to reference a cluster. For example, the command below lists
the policies attached to the cluster ``webservers``::
$ openstack cluster policy binding list webservers
Sorting the List
----------------
You can specify the sorting keys and sorting direction when list cluster
policies, using the option :option:`--sort`. The :option:`--sort` option
accepts a string of format ``key1[:dir1],key2[:dir2],key3[:dir3]``, where the
keys used are properties of the policy bound to a cluster and the dirs can be
one of ``asc`` and ``desc``. When omitted, Senlin sorts a given key using
``asc`` as the default direction.
For example, the following command line sorts the policy bindings using the
``enabled`` property in descending order::
$ openstack cluster policy binding list --sort enabled:desc c3
When sorting the list of policies, ``enabled`` is the only key you can specify
for sorting.
Filtering the List
------------------
The :program:`openstack cluster` command also supports options for filtering
the policy list at the server side. The option :option:`--filters` can be used
for this purpose. For example, the following command filters clusters by the
``is_enabled`` field::
$ openstack cluster policy binding list --filters enabled=True c3
+-----------+-------------+---------------------------+------------+
| policy_id | policy_name | policy_type | is_enabled |
+-----------+-------------+---------------------------+------------+
| 0705f0f4 | up01 | senlin.policy.scaling-1.0 | True |
+-----------+-------------+---------------------------+------------+
The option :option:`--filters` accepts a list of key-value pairs separated by
semicolon (``;``), where each key-value pair is expected to be of format
``<key>=<value>``. The only key that can be used for filtering as of today is
``enabled``.
Attaching a Policy to a Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Senlin permits policy objects to be attached to clusters and to be detached
from clusters dynamically. When attaching a policy object to a cluster, you
can customize the policy properties for the particular cluster. For example,
you can specify whether the policy should be enabled once attached.
The following options are supported for the command
:command:`openstack cluster policy attach`:
- :option:`--enabled`: a boolean indicating whether the policy to be enabled
once attached.
For example, the following command attaches a policy named ``up01`` to the
cluster ``c3``, When a policy is attached to a cluster, it is enabled by
default. To keep it disabled, the user can use the parameter ``--enabled False``.
For example::
$ openstack cluster policy attach --policy up01 --enabled False c3
Note that most of the time, Senlin doesn't allow more than one policy of the
same type to be attached to the same cluster. This restriction is relaxed for
some policy types. For example, when working with policies about scaling, you
can actually attach more than one policy instances to the same cluster, each of
which is about a specific scenario.
For the identifiers specified for the cluster and the policy, you can use the
name, the ID or the "short ID" of an object. The Senlin engine will try make a
guess on each case. If no entity matches the specified identifier or there are
more than one entity matching the identifier, you will get an error message.
Showing Policy Properties on a Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To examine the detailed properties of a policy object that has been attached
to a cluster, you can use the :command:`openstack cluster policy binding show`
command with the policy identifier and the cluster identifier specified. For
example::
$ openstack cluster policy binding show --policy dp01 c3
+--------------+--------------------------------------+
| Field | Value |
+--------------+--------------------------------------+
| cluster_name | c3 |
| data | None |
| id | 2b7e9294-b5cd-470f-b191-b18f7e672495 |
| is_enabled | True |
| location | None |
| name | None |
| policy_id | 239d7212-6196-4a89-9446-44d28717d7de |
| policy_name | dp01 |
| policy_type | senlin.policy.deletion-1.0 |
+--------------+--------------------------------------+
You can use the name, the ID or the "short ID" of a policy and/or a cluster to
name the objects.
Updating Policy Properties on a Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once a policy is attached to a cluster, you can request its property on this
cluster be changed by using the command
:command:`openstack cluster policy binding update`. Presently, you can only
specify the ``enabled`` property to be updated.
For example, the following command disables a policy on the specified cluster::
$ openstack cluster policy binding update \
--enabled False --policy dp01 \
mycluster
The Senlin engine will perform validation of the arguments in the same way as
that for the policy attach operation. You can use the name, the ID or the
"short ID" of an entity to reference it, as you do with the policy attach
operation as well.
Detach a Policy from a Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Finally, to remove the binding between a specified policy object from a
cluster, you can use the :command:`openstack cluster policy detach` command as
shown below::
$ openstack cluster policy detach --policy dp01 mycluster
This command will detach the specified policy from the specified cluster.
You will use the option :option:`--policy` to specify the policy.
|
