mirror of https://github.com/tLDP/LDP
747 lines
28 KiB
XML
747 lines
28 KiB
XML
<chapter id="clusterops"><title>Clustering operations</title>
|
|
<para>This chapter discusses how to configure cluster storage containers (referred to throughout
|
|
this chapter as "cluster containers"), a feature provided by the EVMS Cluster Segment
|
|
Manager (CSM).</para>
|
|
<para>Disks that are physically accessible from all of the nodes of the cluster can be
|
|
grouped together as a single manageable entity. EVMS storage objects can then be
|
|
created using storage from these containers.</para>
|
|
<para>Ownership is assigned to a container to make the container either private or shared.
|
|
A container that is owned by any one node of the cluster is called a private container.
|
|
EVMS storage objects and storage volumes created using space from a private
|
|
container are accessible from only the owning node.</para>
|
|
<para>A container that is owned by all the nodes in a cluster is called a shared container.
|
|
EVMS storage objects and storage volumes created using space from a shared
|
|
container are accessible from all nodes of the cluster simultaneously.</para>
|
|
<para>EVMS provides the tools to convert a private container to a shared container, and
|
|
a shared container to a private container. EVMS also provides the flexibility to
|
|
change the ownership of a private container from one cluster node to another
|
|
cluster node.</para>
|
|
<sect1><title>Rules and restrictions for creating cluster containers</title>
|
|
<para>Note the following rules and limitations for creating cluster containers:
|
|
</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>Do not assign non-shared disks to a cluster container.
|
|
</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>Storage objects and volumes created on a cluster container must not
|
|
span across multiple cluster containers.
|
|
The EVMS Engine enforces this rule by disallowing such configurations.
|
|
</para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>Do not assign RAID-1, RAID-5, BBR, or snapshotting
|
|
to storage objects on a shared cluster container. These plug-ins
|
|
can be used on private cluster containers.
|
|
</para>
|
|
</listitem>
|
|
|
|
</itemizedlist>
|
|
</sect1>
|
|
|
|
<sect1><title>Example: create a private cluster container</title>
|
|
<para>This section tells how to create a sample private
|
|
container and provides instructions for completing the following task:</para>
|
|
|
|
<blockquote><example><title>Create a private cluster container</title>
|
|
<para>Given a system with three available shared disks
|
|
(<filename>sdd</filename>, <filename>sde</filename>, and
|
|
<filename>sdf</filename>),
|
|
use the EVMS Cluster Segment Manager to combine these disk drives into a
|
|
container called <filename>Priv1</filename> owned by <filename>node1</filename>.
|
|
</para>
|
|
</example>
|
|
</blockquote>
|
|
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
<para>To create a container with the EVMS GUI, follow these steps:</para>
|
|
|
|
<orderedlist>
|
|
|
|
<listitem><para>Select
|
|
<menuchoice><guimenu>Actions</guimenu><guimenuitem>Create</guimenuitem>
|
|
<guimenuitem>Container</guimenuitem>
|
|
</menuchoice> to see a list of plug-ins that support container creation.
|
|
</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Select the <guimenuitem>Cluster Segment Manager</guimenuitem>.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Click <guibutton>Next</guibutton>.</para>
|
|
<para>The next dialog window contains a list of storage objects that
|
|
the CSM can use to create a container.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list.</para>
|
|
</listitem>
|
|
<listitem><para>Click <guibutton>Next</guibutton>.</para>
|
|
</listitem>
|
|
<listitem><para>In the first pull-down menu, select the "Node Id" of the cluster node that
|
|
owns this container (<guimenuitem>node1</guimenuitem>). Select "Storage Type" as
|
|
<guimenuitem>private</guimenuitem> from the second pull-down menu.</para>
|
|
</listitem>
|
|
<listitem><para>Enter the name <userinput>Priv1</userinput> for the Container Name.</para>
|
|
</listitem>
|
|
<listitem><para>Click <guibutton>Create</guibutton>.</para>
|
|
<para>A window opens that displays the outcome.</para>
|
|
</listitem>
|
|
<listitem><para>Commit the changes.</para>
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
<para>To create the private container with the Ncurses interface, follow these steps:
|
|
</para>
|
|
<orderedlist>
|
|
<listitem><para>Select <menuchoice><guimenu>Actions</guimenu>
|
|
<guimenuitem>Create</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list
|
|
of plug-ins that support container creation.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow and select Cluster Segment Manager by
|
|
pressing <keycap>spacebar</keycap>. The plug-in you selected is marked with an "x." </para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
<para>The next submenu contains a list of disks that the Cluster Segment Manager finds
|
|
acceptable to use for the creation of a container.</para>
|
|
</listitem>
|
|
<listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>,
|
|
and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>On the Create Storage Container - Configuration Options menu, press
|
|
<keycap>spacebar</keycap> on the Node Id, which will provide a list of nodes from
|
|
which to select.</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>spacebar</keycap> on the node <filename>node1</filename> and
|
|
then press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the
|
|
Storage Type. A list of storage types opens.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow to
|
|
<guimenuitem>private entry</guimenuitem> and press <keycap>spacebar</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow to
|
|
<guimenuitem>Container Name</guimenuitem> and press <keycap>spacebar</keycap>.</para>
|
|
<para>The Change Option Value menu opens and asks for the Container Name. Type
|
|
in the name of the container as <userinput>Priv1</userinput>, and press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap> to complete the operation.</para>
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
<sect2><title>Using the CLI</title>
|
|
<para>An operation to create a private cluster container with the CLI takes three parameters: the name
|
|
of the container, the type of the container, and the nodeid to which the container belongs.
|
|
</para>
|
|
<para>On the CLI, type the following command to create the private container
|
|
<filename>Priv1</filename>:</para>
|
|
<programlisting>create: container,CSM={name="Priv1",type="private",nodeid="node1"},sdd,sde,sdf</programlisting>
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
<sect1><title>Example: create a shared cluster container</title>
|
|
<para>This section tells how to create a sample shared container and provides
|
|
instructions to help you complete the following task:</para>
|
|
|
|
<blockquote><example><title>Create a shared cluster container</title>
|
|
<para>Given a system with three available shared disks
|
|
(<filename>sdd</filename>, <filename>sde</filename>, and
|
|
<filename>sdf</filename>),
|
|
use the EVMS Cluster Segment Manager to combine these disk drives into a shared
|
|
container called <filename>Shar1</filename>.
|
|
</para>
|
|
</example>
|
|
</blockquote>
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
<para>To create a shared cluster container with the EVMS GUI, follow these steps:</para>
|
|
|
|
<orderedlist>
|
|
|
|
<listitem><para>Select
|
|
<menuchoice><guimenu>Actions</guimenu><guimenuitem>Create</guimenuitem>
|
|
<guimenuitem>Container</guimenuitem>
|
|
</menuchoice> to see a list of plug-ins that support container creation.
|
|
</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Select the <guimenuitem>Cluster Segment Manager</guimenuitem>.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Click <guibutton>Next</guibutton>.</para>
|
|
<para>The next dialog window contains a list of storage objects that
|
|
the CSM can use to create a container.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Select <filename>sdd</filename>, <filename>sde</filename>, and <filename>sdf</filename> from the list.</para>
|
|
</listitem>
|
|
<listitem><para>Click <guibutton>Next</guibutton>.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>You do not need to change the "Node Id" field. Select
|
|
Storage Type as
|
|
<guimenuitem>shared</guimenuitem> from the second pull-down menu.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Enter the name <userinput>Shar1</userinput> for the Container Name.</para>
|
|
</listitem>
|
|
<listitem><para>Click <guibutton>Create</guibutton>. A window opens to display the outcome.</para>
|
|
</listitem>
|
|
<listitem><para>Commit the changes.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
<para>To create a shared cluster contained with the Ncurses interface, follow these steps:</para>
|
|
|
|
<orderedlist><listitem><para>Select <menuchoice><guimenu>Actions</guimenu>
|
|
<guimenuitem>Create</guimenuitem>
|
|
<guimenuitem>Container</guimenuitem>
|
|
</menuchoice> to see a list of plug-ins that support container creation.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow and select Cluster Segment Manager by
|
|
pressing <keycap>spacebar</keycap>. The plug-in you selected is marked with an "x." </para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
<para>The next submenu contains a list of disks that the Cluster Segment Manager finds
|
|
acceptable to use for the creation of a container.</para>
|
|
</listitem>
|
|
<listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>,
|
|
and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>The Create Storage Container - Configuration Options menu open;
|
|
ignore the "Node Id" menu.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the
|
|
Storage Type. A list of storage types opens.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow to
|
|
<guimenuitem>shared entry</guimenuitem> and press <keycap>spacebar</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow to
|
|
<guimenuitem>Container Name</guimenuitem> and press <keycap>spacebar</keycap>.</para>
|
|
<para>The Change Option Value menu opens and asks for the Container Name. Type
|
|
in the name of the container as <userinput>Shar1</userinput>, and press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap> to complete the operation.</para>
|
|
</listitem>
|
|
<listitem><para>Quit Ncurses and run <command>evms_activate</command> on each of the cluster
|
|
nodes. This process will be automated in future releases of EVMS.</para>
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
|
|
</sect2>
|
|
|
|
<sect2><title>Using the CLI</title>
|
|
<para>An operation to create a shared cluster container with the CLI takes two parameters:
|
|
the name of the container and the type of the container.</para>
|
|
<para>On the CLI, type the following command to create shared container <filename>Shar1</filename>:</para>
|
|
<programlisting>create: container,CSM={name="Shar1",type="shared"},sdd,sde,sdf</programlisting>
|
|
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
<sect1><title>Example: convert a private container to a shared container</title>
|
|
|
|
<para>This section tells how to convert a sample private container to a shared
|
|
container and provides instructions for completing the following task:</para>
|
|
|
|
<blockquote><example><title>Convert a private container to shared</title>
|
|
<para>Given a system with a private storage container <filename>Priv1</filename> owned
|
|
by <filename>evms1</filename>, convert
|
|
<filename>Priv1</filename> to a shared storage container with the same name.</para>
|
|
</example>
|
|
</blockquote>
|
|
|
|
<note><title>CAUTION</title>
|
|
<para>Ensure that no application
|
|
is using the volumes on the container on any node of the cluster.</para></note>
|
|
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
<para>Follow these steps to convert a private cluster container to a shared cluster
|
|
container with the EVMS GUI:</para>
|
|
<orderedlist>
|
|
<listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para>
|
|
</listitem>
|
|
<listitem><para>Select the container <guimenuitem>Priv1</guimenuitem> and press <keycap>Next</keycap>.</para>
|
|
<para>A Modify Properties dialog box opens.</para>
|
|
</listitem>
|
|
<listitem><para>Change "Type" to "shared" and click <keycap>Modify</keycap>.</para>
|
|
<para>A window opens that displays the outcome.</para>
|
|
</listitem>
|
|
<listitem><para>Commit the changes.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
<para>Follow these steps to convert a private cluster container to a shared cluster
|
|
container with the Ncurses interface:</para>
|
|
|
|
<orderedlist><listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>The Modify Container Properties dialog opens. Select the container
|
|
<filename>Priv1</filename> by
|
|
pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para>
|
|
<para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Use <keycap>spacebar</keycap> to select <filename>sdd</filename>, <filename>sde</filename>,
|
|
and <filename>sdf</filename> from the list. The disks you select are marked with an "x."</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on "Type".</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Press <keycap>spacebar</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>The Change Option Value dialog opens. Type <userinput>shared</userinput> and press <keycap>Enter</keycap>.</para>
|
|
<para>The changed value now displays in the Modify Container Properties -
|
|
Configuration Options dialog.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
<para>The outcome of the command is displayed at the bottom of the screen.</para>
|
|
</listitem>
|
|
<listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown menu.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
|
|
<sect2><title>Using the CLI</title>
|
|
<para>The <command>modify</command> command modifies the properties of a container. The first argument
|
|
of the command is the object to modify, followed by its new properties. The command
|
|
to convert the private container to a shared container in the example is:</para>
|
|
<programlisting>modify: Priv1,type=shared</programlisting>
|
|
|
|
</sect2>
|
|
</sect1>
|
|
|
|
|
|
|
|
<sect1><title>Example: convert a shared container to a private container</title>
|
|
<para>This section tells how to convert a sample shared container to a private
|
|
container and provides instructions for completing the following task:</para>
|
|
|
|
<blockquote><example><title>Convert a shared container to private</title>
|
|
<para>Given a system with a shared storage container <filename>Shar1</filename>, convert
|
|
<filename>Shar1</filename> to a private storage container owned by node <filename>node1</filename> (where
|
|
<filename>node1</filename> is the nodeid of one of the cluster nodes).</para>
|
|
</example>
|
|
</blockquote>
|
|
|
|
<note><title>CAUTION</title>
|
|
<para>Ensure that no application
|
|
is using the volumes on the container of any node in the cluster.</para></note>
|
|
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
<para>Follow these steps to convert a shared cluster container to a private cluster
|
|
container with the EVMS GUI:</para>
|
|
<orderedlist>
|
|
<listitem><para>Select <menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice> to see a list of containers.</para>
|
|
</listitem>
|
|
<listitem><para>Select the container <guimenuitem>Shar1</guimenuitem> and press <keycap>Next</keycap>.</para>
|
|
<para>A Modify Properties dialog opens.</para>
|
|
</listitem>
|
|
<listitem><para>Change "Type" to "private" and the "Node" field to <filename>node1</filename>. Click <keycap>Modify</keycap>.</para>
|
|
<para>A window opens that displays the outcome.</para>
|
|
</listitem>
|
|
<listitem><para>Commit the changes.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
<para>Follow these steps to convert a shared cluster container to a private cluster
|
|
container with the Ncurses interface:</para>
|
|
|
|
<orderedlist><listitem><para>Select <menuchoice><guimenu>Actions</guimenu>
|
|
<guimenuitem>Modify</guimenuitem>
|
|
<guimenuitem>Container</guimenuitem></menuchoice></para>
|
|
</listitem>
|
|
|
|
<listitem>
|
|
<para>The Modify Container Properties dialog opens. Select the container
|
|
<filename>Shar1</filename> by
|
|
pressing <keycap>spacebar</keycap>. The container you selected is marked with an "x."</para>
|
|
<para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
|
|
|
|
<listitem><para>The Modify Container Properties - Configuration Options" dialog opens. Scroll down with the <keycap>down</keycap> arrow and press <keycap>spacebar</keycap> on the "Type" field.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Press <keycap>spacebar</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>The Change Option Value dialog opens. Select <userinput>private</userinput> and press <keycap>Enter</keycap>.</para>
|
|
|
|
</listitem>
|
|
<listitem><para>The Modify Container Properties -
|
|
Configuration Options dialog opens. Scroll down the list to <guimenuitem>NodeId</guimenuitem>
|
|
with the <keycap>down</keycap> arrow
|
|
and press <keycap>spacebar</keycap>.</para></listitem>
|
|
|
|
<listitem><para>The Change Option Value dialog opens. Select <userinput>node1</userinput> and press <keycap>Enter</keycap>.</para></listitem>
|
|
|
|
<listitem><para>The changed values now display in the Modify Container Properties -
|
|
Configuration Options dialog. Press <keycap>Enter</keycap>. </para>
|
|
<para>The outcome of the command is displayed at the bottom of the screen.</para>
|
|
</listitem>
|
|
|
|
<listitem><para>Save the changes by clicking <keycap>Save</keycap> in the <guimenuitem>Actions</guimenuitem> pulldown.</para></listitem>
|
|
|
|
</orderedlist>
|
|
</sect2>
|
|
|
|
|
|
<sect2><title>Using the CLI</title>
|
|
<para>The <command>modify</command> command modifies the properties of a container. The first argument
|
|
of the command is the object to modify, followed by its new properties. The command
|
|
to convert the shared container to a private container in the example is:</para>
|
|
<programlisting>modify: Shar1,type=private,node=node1</programlisting>
|
|
</sect2>
|
|
|
|
</sect1>
|
|
|
|
<sect1><title>Example: deport a private or shared container</title>
|
|
<para>
|
|
When a container is deported, the node disowns the container and deletes
|
|
all the objects created in memory that belong to that container.
|
|
No node in
|
|
the cluster can discover objects residing on a deported container or
|
|
create objects for a deported container.
|
|
This section explains how to deport a private or shared container.
|
|
</para>
|
|
|
|
<blockquote><example><title>Deport a cluster container</title>
|
|
<para>Given a system with a private or shared storage container named
|
|
<filename>c1</filename>, deport <filename>c1</filename>.
|
|
</para>
|
|
</example>
|
|
</blockquote>
|
|
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
<para>
|
|
To deport a container with the EVMS GUI, follow these steps:
|
|
</para>
|
|
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Select
|
|
<menuchoice><guimenu>Actions</guimenu><guimenuitem>Modify</guimenuitem><guimenuitem>Container</guimenuitem></menuchoice>.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select the container <filename>c1</filename> and press
|
|
<keycap>Next</keycap>.
|
|
</para>
|
|
<para>
|
|
A Modify Properties dialog opens.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Change "Type" to "deported." Click <keycap>Modify</keycap>.
|
|
</para>
|
|
<para>
|
|
A window opens that displays the outcome.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Commit the changes.
|
|
</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
|
|
</sect2>
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
<para>
|
|
To deport a container with Ncurses, follow these steps:
|
|
</para>
|
|
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Scroll down the list with the <keycap>down</keycap> arrow to
|
|
<guimenuitem>Modify</guimenuitem>. Press <keycap>Enter</keycap>.
|
|
</para>
|
|
<para>
|
|
A submenu is displayed.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Scroll down until Container is highlighted. Press <keycap>Enter</keycap>.
|
|
</para>
|
|
<para>
|
|
The Modify Container Properties dialog opens.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Select the container <filename>csm/c1</filename> by pressing
|
|
<keycap>spacebar</keycap>. The container you selected is marked with an "x."
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Press <keycap>Enter</keycap>.
|
|
</para>
|
|
<para>
|
|
The Modify Container Properties - Configuration Options dialog opens.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Scroll down and press <keycap>spacebar</keycap> on the "Type" field.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
Press <keycap>spacebar</keycap>.
|
|
</para>
|
|
<para>
|
|
The Change Option Value dialog opens.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Type <userinput>deported</userinput> and press <keycap>Enter</keycap>.
|
|
</para>
|
|
<para>
|
|
The changed value is displayed in the Modify Container Properties -
|
|
Configuration Options dialog.
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Press <keycap>Enter</keycap>.
|
|
</para>
|
|
<para>
|
|
The outcome of the command is displayed at the bottom of the screen.
|
|
</para></listitem>
|
|
<listitem>
|
|
<para>Commit the changes by clicking <keycap>Save</keycap> in the
|
|
<guimenuitem>Actions</guimenuitem> pulldown.
|
|
</para>
|
|
</listitem>
|
|
|
|
</orderedlist>
|
|
|
|
</sect2>
|
|
|
|
<sect2><title>Using the CLI</title>
|
|
<para>
|
|
To deport a container from the CLI, execute the following command
|
|
at the CLI prompt:
|
|
</para>
|
|
<programlisting>
|
|
modify: c1,type=deported
|
|
</programlisting>
|
|
|
|
</sect2>
|
|
</sect1>
|
|
<sect1><title>Deleting a cluster container</title>
|
|
<para>
|
|
The procedure for deleting a cluster container is the same for deleting
|
|
any container. See <xref linkend="examdelrecur"></xref>
|
|
|
|
|
|
|
|
|
|
|
|
</para></sect1>
|
|
|
|
<sect1><title>Failover and Failback of a private container on Linux-HA</title>
|
|
|
|
<para>EVMS supports the Linux-HA cluster manager in EVMS V2.0 and later. Support for
|
|
the RSCT cluster
|
|
manager is also available as of EVMS V2.1, but is not as widely tested.</para>
|
|
<para><note><title>NOTE</title>
|
|
<para>Ensure that <command>evms_activate</command> is called in one of the startup scripts
|
|
before the <command>heartbeat</command> startup script is called. If <command>evms_activate</command> is not called, failover
|
|
might not work correctly. </para>
|
|
</note></para>
|
|
|
|
<para>Follow these steps to set up failover and failback of a private container:</para>
|
|
<orderedlist>
|
|
<listitem><para>Add an entry in <filename>/etc/ha.d/haresources</filename> for each
|
|
private container to be failed over. For example, if <filename>container1</filename> and
|
|
<filename>container2</filename> are to
|
|
be failed over together to the same node with <filename>node1</filename> as the owning node, add the
|
|
following entry to <filename>/etc/ha.d/haresources</filename>:</para>
|
|
<programlisting>node1 evms_failover::container1 evms_failover::container2</programlisting>
|
|
<para><filename>node1</filename> is the cluster node that owns this resource. The resource is failed over
|
|
to the other node when <filename>node1</filename> dies.</para>
|
|
<para>Similarly, if <filename>container3</filename> and <filename>container4</filename> are to be failed over together to the same
|
|
node with <filename>node2</filename> as the owning node, then add the following entry to
|
|
<filename>/etc/ha.d/haresources</filename>:</para>
|
|
<programlisting>node2 evms_failover::container3 evms_failover::container4</programlisting>
|
|
<para>Refer to
|
|
<ulink url="http://www.linux-ha.org/download/GettingStarted.html">http://www.linux-ha.org/download/GettingStarted.html</ulink> for more details on the
|
|
semantics of resource groups.</para>
|
|
</listitem>
|
|
<listitem><para>Validate that the <filename>/etc/ha.d</filename>, <filename>/etc/ha.cf</filename> and <filename>/etc/ha.d/haresources</filename> files are the same
|
|
on all the nodes of the cluster.</para>
|
|
</listitem>
|
|
<listitem><para>The heartbeat cluster manager must be restarted, as follows, after the
|
|
<filename>/etc/ha.d/haresources</filename> file has been changed:</para>
|
|
<programlisting>/etc/init.d/heartbeat restart</programlisting>
|
|
<note><title>NOTE</title>
|
|
<para>
|
|
Do not add shared containers to the list of failover resources; doing so causes
|
|
EVMS to respond unpredictably.</para>
|
|
</note>
|
|
</listitem>
|
|
</orderedlist>
|
|
</sect1>
|
|
|
|
|
|
<sect1><title>Remote configuration management</title>
|
|
<para>EVMS supports the administration of cluster nodes by any node in the cluster. For
|
|
example, storage on remote cluster node <filename>node1</filename> can be administered from cluster node
|
|
<filename>node2</filename>. The following sections show how to set up remote administration
|
|
through the various EVMS user interfaces.</para>
|
|
|
|
<sect2><title>Using the EVMS GUI</title>
|
|
|
|
<para>To designate <filename>node2</filename> as the node to administer from the GUI, follow these steps:</para>
|
|
|
|
<orderedlist>
|
|
<listitem><para>Select <menuchoice><guimenu>Settings</guimenu><guimenuitem>Node Administered...</guimenuitem></menuchoice></para>
|
|
</listitem>
|
|
<listitem><para>Select <filename>node2</filename>.</para>
|
|
</listitem>
|
|
<listitem><para>Click <keycap>Administer</keycap> to switch to the new node.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
<para>
|
|
The GUI gathers information about the objects, containers, and volumes on
|
|
the other node. The status
|
|
bar displays the message "Now administering node node2," which indicates
|
|
that the GUI is switched over to node node2.
|
|
</para>
|
|
|
|
</sect2>
|
|
|
|
<sect2><title>Using Ncurses</title>
|
|
|
|
<para>To designate <filename>node2</filename> as the node to administer from Ncurses, follow these steps:</para>
|
|
|
|
<orderedlist>
|
|
<listitem><para>Go to the <guimenuitem>Settings</guimenuitem> pulldown menu.</para>
|
|
</listitem>
|
|
<listitem><para>Scroll down with the <keycap>down</keycap> arrow to the "Node Administered" option and
|
|
press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>The Administer Remote Node dialog opens. Select <filename>node2</filename> and press
|
|
<keycap>spacebar</keycap>.</para>
|
|
<para>The node you selected is marked with an "x."</para>
|
|
</listitem>
|
|
<listitem><para>Press <keycap>Enter</keycap>.</para>
|
|
</listitem>
|
|
<listitem><para>After a while, you will be switched over to
|
|
the node <filename>node2</filename>.</para></listitem>
|
|
</orderedlist>
|
|
|
|
</sect2>
|
|
<sect2><title>Using the CLI</title>
|
|
<para>To designate <filename>node2</filename> as a node administrator from the CLI, issue this command:</para>
|
|
<programlisting>evms -n node2</programlisting>
|
|
|
|
</sect2>
|
|
</sect1>
|
|
|
|
<sect1><title>Forcing a cluster container to be imported</title>
|
|
<para>
|
|
A private container and its objects are made active on a node if:</para>
|
|
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para>
|
|
the private container is owned by the node
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
the container is not deported
|
|
</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>
|
|
the node currently has quorum
|
|
</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
|
|
<para>
|
|
Similarly, a shared container and its objects are made active on a node if
|
|
the node currently has quorum. However, the administrator can force the
|
|
importation of private and shared containers by overriding these rules.
|
|
</para>
|
|
|
|
<note><title>NOTE</title>
|
|
<para>
|
|
Use extreme caution when performing this operation by ensuring that the
|
|
node on which the cluster container resides is the only active node in the
|
|
cluster. Otherwise, the data in volumes on shared and private containers
|
|
on the node can get corrupted.
|
|
</para>
|
|
</note>
|
|
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>
|
|
Enabling maintenance mode in the <filename>/etc/evms.conf</filename> file.
|
|
The option to modify in the <filename>/etc/evms.conf</filename> file is the
|
|
following:
|
|
</para>
|
|
<programlisting>
|
|
# cluster segment manager section
|
|
csm {
|
|
# admin_mode=yes # values are: yes or no
|
|
# The default is no. Set this key to
|
|
# yes when you wish to force the CSM
|
|
# to discover objects from all cluster
|
|
# containers, allowing you to perform
|
|
# configuration and maintenance. Setting
|
|
# admin_mode to yes will cause the CSM
|
|
# to ignore container ownership, which
|
|
# will allow you to configure storage
|
|
# in a maintenance mode.
|
|
</programlisting>
|
|
<para>
|
|
</para></listitem>
|
|
<listitem>
|
|
<para>
|
|
Running <command>evms_activate</command> on the node.
|
|
</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
|
|
|
|
</sect1>
|
|
</chapter>
|
|
|