Difference: CorosyncSinglePrimaryConfiguration (4 vs. 5)

Revision 52011-10-14 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="Computing"

Nevis particle-physics administrative cluster configuration

Line: 136 to 136
  configure colocation AdminWithMainIP inf: MainIPGroup Admin:Master
Added:
>
>
# We want to wait before assigning IPs to a node until we know that # Admin has been promoted to master on that node. configure order AdminBeforeMainIP inf: Admin:promote MainIPGroup
  # I like these commands, so commit them to the running configuration.

cib commit drbd

Line: 191 to 195
  # One more thing: It's important that we not try to mount the directory # until after Work has been promoted to master on the node.

Added:
>
>
# A score of "inf" means "infinity"; if the DRBD resource 'work' can't # be set up, then don't mount the /work partition.

  configure order WorkBeforeDirectory inf: Work:promote WorkDirectory:start

cib commit workdisk quit

Changed:
<
<
# We've made the relatively-unimportant work DRBD master function. Let's do it for real. # Prevously I created some LVM volumes on the admin DRBD master. We need to use a
>
>
# We've made the relatively-unimportant DRBD resource 'work' function. Let's do it for 'admin'. # Previously I created some LVM volumes on the admin DRBD master. We need to use a
 # resource to active them, but we can't activate them until after the Admin:Master # is loaded. crm
Line: 289 to 296
  # and demand that the cups service only start if /var/nevis (and the other # high-availability directories) have been mounted.

Deleted:
<
<
# A score of "inf" means "infinity"; if it can't be run on the # machine that mounted all the admin directories, it won't run at all.

  configure colocation CupsWithVar inf: Cups AdminDirectoriesGroup

# In order to prevent chaos, make sure that the high-availability directories

Line: 341 to 345
  configure colocation NfsStateWithVar inf: NfsStateDirectory AdminDirectoriesGroup configure order VarBeforeNfsState inf: AdminDirectoriesGroup NfsStateDirectory
Changed:
<
<
# Now that the NFS state directory is mounted, we can start the nfslockd. Note that
>
>
# Now that the NFS state directory is mounted, we can start nfslockd. Note that
  # that we're starting NFS lock on both the primary and secondary HA systems; # by default a "clone" resource is started on all systems in a cluster.
Added:
>
>
# (Placing nfslockd under the control of Pacemaker turned out to be key to # successful transfer of cluster services to another node. The nfslockd and # nfs daemon information stored in /var/lib/nfs have to be consistent.)
  configure primitive NfsLockInstance lsb:nfslock
Changed:
<
<
clone NfsLock NfsLockInstance
>
>
configure clone NfsLock NfsLockInstance
 
Changed:
<
<
# Once nfslockd has been set up, we can start NFS.
>
>
configure order NfsStateBeforeNfsLock inf: NfsStateDirectory NfsLock

# Once nfslockd has been set up, we can start NFS. (We say to colocate # NFS with 'NfsStateDirectory', instead of nfslockd, because nfslockd # is going to be started on both nodes.)

  configure primitive Nfs lsb:nfs configure colocation NfsWithNfsState inf: Nfs NfsStateDirectory
Changed:
<
<
configure order NfsStateBeforeNfs inf: NfsStateDirectory Nfs
>
>
configure order NfsLockBeforeNfs inf: NfsLock Nfs
  cib commit nfs quit
Line: 363 to 375
 # virtual machine. I previously created the hogwarts virtual machine and copied its # configuration to /xen/configs/hogwarts.cfg.
Added:
>
>
# I duplicated the same procedure for franklin (mail server), ada (web server), and # so on, but I don't know that here.
 crm cib new hogwarts

Line: 405 to 420
 # In general, there are many ways to implement a STONITH mechanism. At Nevis, the way # we do it is to shut-off the power on the UPS connected to the failed node.
Changed:
<
<
# (By the way, this is why you have to restart hypatia and orestes at the same time. # If you just restart one, the STONITH mechanism will cause the UPS on the restarting
>
>
# (By the way, this is why you have to be careful about restarting hypatia or orestes. # The STONITH mechanism may cause the UPS on the restarting
 # computer to turn off the power; it will never come back up.)

# At Nevis, the UPSes are monitored and controlled using the NUT package

Line: 466 to 481
 # For orestes to do this, it requires the condor service. It also requires that # library:/usr/nevis is mounted, the same as every other batch machine on the # Nevis condor cluster. We can't use the automount daemon (amd) to do this for
Changed:
<
<
# us, the way we do on the other batch nodes, so we have to make corosync do the
>
>
# us, the way we do on the other batch nodes; we have to make corosync do the
 # mounts.

crm cib new condor

Changed:
<
<
# Mount library:/usr/nevis
>
>
# Mount library:/usr/nevis. A bit of a name confusion here: there's a /work # partition on the primary node, but the name 'LibraryOnWork" means that # the nfs-mount of /usr/nevis is located on the secondary or "work" node.
  configure primitive LibraryOnWork ocf:heartbeat:Filesystem params device="library:/usr/nevis" directory="/usr/nevis"
Changed:
<
<
fstype="nfs" OCF_CHECK_LEVEL="20"
>
>
fstype="nfs"
 
Changed:
<
<
# Corosync must NOT mount library:/usr/nevis on the system has already
>
>
# Corosync must not NFS-mount library:/usr/nevis on the system has already
  # mounted /usr/nevis directly as part of AdminDirectoriesGroup # described above.

Line: 489 to 506
  configure colocation NoRemoteMountWithDirectories -inf: LibraryOnWork AdminDirectoriesGroup
Changed:
<
<
# Determine on which machine we mount library:/usr/nevis after we # figure out which machine is running AdminDirectoriesGroup.
>
>
# Determine on which machine we mount library:/usr/nevis after the NFS # export of /usr/nevis has been set up.
 
Changed:
<
<
configure order DirectoresBeforeLibrary inf: AdminDirectoriesGroup LibraryOnWork
>
>
configure order NfsBeforeLibrary inf: Nfs LibraryOnWork
  # Define the IPs associated with the backup system, and group them together. # This is a non-critical definition, and I don't want to assign it until the more important
Line: 515 to 532
  # If we're able mount library:/usr/nevis, then it's safe to start condor. # If we can't mount library:/usr/nevis, then condor will never be started.
Added:
>
>
# (We stated above that AssistantIPGroup won't start until after LibraryOnWork).
 
Changed:
<
<
configure colocation CondorWithLibrary inf: Condor LibraryOnWork

# library:/usr/nevis must be mounted before condor starts.

configure order LibraryBeforeCondor inf: LibraryOnWork Condor

>
>
configure colocation CondorWithAssistant inf: Condor AssistantIPGroup configure order AssistantBeforeCondor inf: AssistantIPGroup Condor
  cib commit condor quit
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback