Skip to content

Commit fec0e7a

Browse files
committed
add screens
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
1 parent 682406e commit fec0e7a

6 files changed

Lines changed: 17 additions & 0 deletions

File tree

98.1 KB
Loading
17.8 KB
Loading
86.2 KB
Loading
154 KB
Loading
116 KB
Loading

source/adminguide/virtual_machines/instance_boot_groups.rst

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ web tier starts.
2424
An Instance Boot Group is owned by an account, just like an Instance, and is
2525
managed from **Compute > Instance Boot Groups** in the CloudStack UI.
2626

27+
|instance_boot_groups.png|
28+
2729
.. note:: An Instance Boot Group is a different concept from an Instance
2830
Group (**Compute > Instance Groups**), which is a simple, unordered label
2931
used to organize Instances. An Instance Group can itself be added as a
@@ -143,6 +145,8 @@ Creating an Instance Boot Group
143145
reboot-on-retry behaviour for this Instance Boot Group only.
144146
#. Click **OK**.
145147

148+
|instance_boot_group_add.png|
149+
146150
Using the API:
147151

148152
.. code:: bash
@@ -155,6 +159,8 @@ Adding and Managing Members
155159
Once an Instance Boot Group has been created, Instances or Instance Groups
156160
can be added to it as members, each with its own Boot Order.
157161

162+
|instance_boot_group_members.png|
163+
158164
Adding a Member
159165
~~~~~~~~~~~~~~~~
160166

@@ -165,6 +171,8 @@ Adding a Member
165171
#. Enter the Boot Order for the new member.
166172
#. Click **OK**.
167173

174+
|instance_boot_group_member_add.png|
175+
168176
Using the API:
169177

170178
.. code:: bash
@@ -231,6 +239,8 @@ Configuring Readiness Rules for a Member
231239
Rules inherited from an owning Instance Group are shown read-only, tagged
232240
**Inherited**; they must be removed from the Instance Group member instead.
233241

242+
|instance_boot_group_member_readiness_rules.png|
243+
234244
.. note:: When adding a ``GuestAgentLiveness`` rule, make sure the QEMU
235245
guest agent is installed, running, and responsive inside the guest
236246
Instance, the rule can only report Ready once the agent answers.
@@ -342,3 +352,10 @@ Limitations
342352
#. If starting an Instance Boot Group is halted because a tier fails to
343353
become ready, any Instances already started in earlier tiers are left
344354
running. The operation is not automatically rolled back.
355+
356+
357+
.. |instance_boot_groups.png| image:: /_static/images/instance_boot_groups.png
358+
.. |instance_boot_group_add.png| image:: /_static/images/instance_boot_group_add.png
359+
.. |instance_boot_group_members.png| image:: /_static/images/instance_boot_group_members.png
360+
.. |instance_boot_group_member_add.png| image:: /_static/images/instance_boot_group_member_add.png
361+
.. |instance_boot_group_member_readiness_rules.png| image:: /_static/images/instance_boot_group_member_readiness_rules.png

0 commit comments

Comments
 (0)