No OneTemporary
Actions

Size

44 KB

Referenced Files

None

Subscribers

None

View Options

	diff --git a/.gitignore b/.gitignore
	index 985abf4..c78acdd 100644
	--- a/.gitignore
	+++ b/.gitignore
	@@ -1,37 +1,35 @@
	# generated by jekyll
	/html/*.html
	/html/*.txt
	/html/assets/
	/html/doc/
	/html/feed.xml
	/html/pacemaker/index.html
	/html/pacemaker/*/index.php
	/html/polls/index.html
	/src/.*-cache/
	/src/.jekyll-metadata

	# generated by pacemaker make targets
	/html/pacemaker/abi/*/
	/html/pacemaker/doc/*/
	/html/pacemaker/doc/acls.*
	/html/pacemaker/doc/build-[0-9].[0-9].txt
	/html/pacemaker/doc/crm_fencing.*
	/html/pacemaker/doxygen/*/
	/html/pacemaker/global/*/
	/html/pacemaker/man/*.[78].html

	-# bugzilla, mediawiki, and phabricator source
	+# bugzilla and phorge source
	/bugzilla
	/bugzilla*/
	-/mediawiki
	-/mediawiki*/
	/projects

	# not version-controlled
	*~
	*.swp
	/build.clusterlabs.org
	/ci.kronosnet.org/
	/html/doc/Two-Stacks.pdf
	/html/images/
	/include/wiki.clusterlabs.org/secrets.php
	diff --git a/include/wiki.clusterlabs.org/secrets.php.sample b/include/wiki.clusterlabs.org/secrets.php.sample
	deleted file mode 100644
	index 213e08a..0000000
	--- a/include/wiki.clusterlabs.org/secrets.php.sample
	+++ /dev/null
	@@ -1,14 +0,0 @@
	-<?php
	-# Database settings
	-$wgDBserver = "put-servername-here";
	-$wgDBname = "put-database-name-here";
	-$wgDBuser = "put-username-here";
	-$wgDBpassword = "put-password-here";
	-
	-# uncomment to run maintenance scripts that require higher privileges
	-#$wgDBadminuser = "put-username-here";
	-#$wgDBadminpassword = "put-password-here";
	-
	-# Entropy source of last resort for authentication cookies
	-$wgSecretKey = "put-64-random-hex-chars-here";
	-?>
	diff --git a/src/_includes/sidebar.html b/src/_includes/sidebar.html
	index 7e46fe9..63bce8f 100644
	--- a/src/_includes/sidebar.html
	+++ b/src/_includes/sidebar.html
	@@ -1,48 +1,45 @@
	<!-- Sidebar -->
	<div id="sidebar">
	<div class="inner">
	-
	- <!-- Search -->
	- <section id="search" class="alt">
	+ <!-- Search -->
	+ <section id="search" class="alt">
	<a href="/">
	{% image clusterlabs3.svg width:160px class:centered alt:'ClusterLabs - Home' %}
	</a>
	- </section>
	+ </section>

	- <!-- Menu -->
	- <nav id="menu">
	- <header class="major">
	- <h2>Menu</h2>
	- </header>
	+ <!-- Menu -->
	+ <nav id="menu">
	+ <header class="major">
	+ <h2>Menu</h2>
	+ </header>
	<ul>
	<li><a href="/doc/">Documentation</a></li>
	<li><a href="/faq.html">FAQ</a></li>
	<li><a href="/help.html">Help</a></li>
	<li><a href="/quickstart.html">Quickstart</a></li>
	<li><a href="/developers.html">Developers</a></li>
	<li><a href="/wiki/">Wiki</a></li>
	</ul>
	- </nav>
	+ </nav>

	- <!-- Section -->
	- <section>
	- <header class="major">
	- <h2>Contact</h2>
	- </header>
	+ <!-- Section -->
	+ <section>
	+ <header class="major">
	+ <h2>Contact</h2>
	+ </header>

	- <p>
	+ <p>
	Stay up to date with the ClusterLabs community by subscribing to our
	mailing lists or by following the project development on Github.
	</p>
	- <ul class="contact">
	- <li class="fab fa-github-alt"><a href="https://github.com/ClusterLabs">Github organization</a></li>
	- <li class="fas fa-envelope"><a href="https://wiki.clusterlabs.org/wiki/Mailing_lists">Mailing lists</a></li>
	- <li class="fas fa-rss"><a href="https://wiki.clusterlabs.org/wiki/Special:RecentChanges">Wiki Recent Changes</a></li>
	- </ul>
	- </section>
	-
	+ <ul class="contact">
	+ <li class="fab fa-github-alt"><a href="https://github.com/ClusterLabs">Github organization</a></li>
	+ <li class="fas fa-envelope"><a
	+ href="https://projects.clusterlabs.org/w/clusterlabs/clusterlabs_mailing_lists/">Mailing lists</a></li>
	+ </ul>
	+ </section>

	{% include footer.html %}
	</div>
	</div>
	-
	diff --git a/src/_layouts/home.html b/src/_layouts/home.html
	index 65f2917..7c071a2 100644
	--- a/src/_layouts/home.html
	+++ b/src/_layouts/home.html
	@@ -1,204 +1,205 @@
	---
	layout: clusterlabs
	---

	<!-- Banner -->
	<section id="banner">
	<div class="content">
	- <header>
	- <h1>ClusterLabs</h1>
	- <p>Open Source <strong>High Availability</strong> Cluster Stack</p>
	- </header>
	- <p>
	- The ClusterLabs stack unifies a large group of Open Source projects related to
	- <strong>High Availability</strong> into a cluster offering suitable
	- for both small and large deployments. Together,
	- <a href="/corosync.html">Corosync</a>,
	- <a href="/pacemaker/">Pacemaker</a>,
	- <a href="https://linbit.com/">DRBD</a>,
	- <a href="https://www.alteeve.com/w/ScanCore">ScanCore</a>,
	- and many other projects have been enabling detection and recovery of
	- machine and application-level failures in production clusters since
	- 1999. The ClusterLabs stack supports practically any redundancy
	- configuration imaginable.</p>
	- <ul class="actions">
	- <li><a href="#content" class="button big">Learn More</a></li>
	- </ul>
	+ <header>
	+ <h1>ClusterLabs</h1>
	+ <p>Open Source <strong>High Availability</strong> Cluster Stack</p>
	+ </header>
	+ <p>
	+ The ClusterLabs stack unifies a large group of Open Source projects related to
	+ <strong>High Availability</strong> into a cluster offering suitable
	+ for both small and large deployments. Together,
	+ <a href="/corosync.html">Corosync</a>,
	+ <a href="/pacemaker/">Pacemaker</a>,
	+ <a href="https://linbit.com/">DRBD</a>,
	+ <a href="https://www.alteeve.com/w/ScanCore">ScanCore</a>,
	+ and many other projects have been enabling detection and recovery of
	+ machine and application-level failures in production clusters since
	+ 1999. The ClusterLabs stack supports practically any redundancy
	+ configuration imaginable.</p>
	+ <ul class="actions">
	+ <li><a href="#content" class="button big">Learn More</a></li>
	+ </ul>
	</div>
	</section>

	<section>
	<header class="major">
	<h2>Quick Overview</h2>
	</header>
	<div class="boxes">
	<article>
	<a href="{% asset_path Deploy.png %}" class="image">{% image Deploy-small.png %}</a>
	<h3>Deploy</h3>
	<p>
	We support many deployment scenarios, from the simplest
	2-node standby cluster to a 32-node active/active
	configuration.

	We can also dramatically reduce hardware costs by allowing
	several active/passive clusters to be combined and share a common
	backup node.
	</p>
	</article>

	<article>
	<a href="{% asset_path Monitor.png %}" class="image">{% image Monitor-small.png %}</a>
	<h3>Monitor</h3>
	<p>
	We monitor the system for both hardware and software failures.

	In the event of a failure, we will automatically recover
	your application and make sure it is available from one
	of the remaning machines in the cluster.
	</p>
	</article>

	<article>
	<a href="{% asset_path Recover.png %}" class="image">{% image Recover-small.png %}</a>
	<h3>Recover</h3>
	<p>
	After a failure, we use advanced algorithms to quickly
	determine the optimum locations for services based on
	relative node preferences and/or requirements to run with
	other cluster services (we call these "constraints").
	</p>
	</article>
	</div>
	</section>

	<section>
	<header class="major">
	<h2 id="why">Why clusters</h2>
	</header>

	<p>
	At its core, a cluster is a distributed finite state
	machine capable of co-ordinating the startup and recovery
	of inter-related services across a set of machines.
	</p>
	<blockquote class="pullquote">
	System HA is possible without a cluster manager, but you save many headaches using one anyway
	</blockquote>
	<p>
	Even a distributed and/or replicated application that is
	able to survive the failure of one or more components can
	benefit from a higher level cluster:
	<ul>
	<li>awareness of other applications in the stack</li>
	<li>a shared <a href="https://en.wikipedia.org/wiki/Quorum_%28Distributed_Systems%29">quorum</a> implementation and calculation</li>
	<li>data integrity through fencing (a non-responsive process does not imply it is not doing anything)</li>
	<li>automated recovery of instances to ensure capacity</li>
	</ul>
	</p>
	<p>
	While SYS-V init replacements like systemd can provide
	deterministic recovery of a complex stack of services, the
	recovery is limited to one machine and lacks the context
	of what is happening on other machines - context that is
	crucial to determine the difference between a local
	failure, clean startup or recovery after a total site
	failure.
	</p>
	</section>

	<section>
	<header class="major">
	<h2 id="features">Features</h2>
	</header>

	<p>
	The ClusterLabs stack, incorporating <a href="/corosync.html">Corosync</a>
	and <a href="/pacemaker/">Pacemaker</a> defines
	an <a href="https://en.wikipedia.org/wiki/Open_source">Open Source</a>,
	<a href="https://en.wikipedia.org/wiki/High_availability">High Availability</a>
	<a href="https://en.wikipedia.org/wiki/Cluster_(computing)">cluster</a>
	offering suitable for both small and large deployments.
	</p>

	<ul>
	<li>Detection and recovery of machine and application-level failures</li>
	- <li>Supports practically any <a href="https://wiki.clusterlabs.org/wiki/ClusterTypes">redundancy configuration</a></li>
	+ <li>Supports practically any <a
	+ href="https://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations">redundancy configuration</a></li>
	<li>Supports both <a href="https://en.wikipedia.org/wiki/Quorum_%28Distributed_Systems%29">quorate</a> and <a href="https://web.archive.org/web/20110727185030/http://devresources.linux-foundation.org/dev/clusters/docs/ResourceDrivenClusters.pdf">resource-driven</a> clusters</li>
	<li>Configurable <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/options.html#cluster-options">strategies</a> for dealing with <a href="https://en.wikipedia.org/wiki/Quorum_%28Distributed_Systems%29">quorum</a> loss (when multiple machines fail)</li>
	<li>Supports application <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#specifying-the-order-in-which-resources-should-start-stop">startup/shutdown ordering</a>, without requiring the applications to run on the same node</li>
	<li>Supports applications that must or must not run on the <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#placing-resources-relative-to-other-resources">same node</a></li>
	<li>Supports applications which need to be active on <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#clones-resources-that-can-have-multiple-active-instances">multiple nodes</a></li>
	<li>Supports applications with dual roles (<a href="https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#promotable-clones">promoted and unpromoted</a>)<br/><br/></li>
	<li>Provably correct response to any failure or cluster state. The cluster's
	response to any stimuli can be tested offline <i>before</i> the condition exists
	</li>
	</ul>

	</section>

	<section>
	<header class="major">
	<h2 id="components">Components</h2>
	</header>

	<blockquote class="pullquote">
	"The definitive open-source high-availability stack for the Linux
	platform builds upon the Pacemaker cluster resource manager."<br />
	-- <cite>LINUX Journal</cite>,
	<a href="http://www.linuxjournal.com/content/ahead-pack-pacemaker-high-availability-stack">"Ahead
	of the Pack: the Pacemaker High-Availability Stack"</a>
	</blockquote>
	<p>A Pacemaker stack is built on five core components:
	<ul>
	<li>libQB - core services (logging, IPC, etc)</li>
	<li>Corosync - Membership, messaging and quorum</li>
	<li>Resource agents - A collection of scripts that interact with the underlying services managed by the cluster</li>
	<li>Fencing agents - A collection of scripts that interact with network power switches and SAN devices to isolate cluster members</li>
	<li>Pacemaker itself</li>
	</ul>
	</p>

	<p>
	We describe each of these in <a href="/components.html">more detail</a> as well as other optional components such as CLIs and GUIs.
	</p>

	</section>

	<section>
	<header class="major">
	<h2 id="background">Background</h2>
	</header>

	<p>
	Pacemaker has been around
	since <a href="https://www.openhub.net/p/pacemaker/analyses/latest/languages_summary">2004</a>
	and is primarily a collaborative effort
	between <a href="https://www.redhat.com/">Red Hat</a>
	and <a href="https://www.suse.com/">SUSE</a>, however we also
	receive considerable help and support from the folks
	at <a href="https://www.linbit.com/">LinBit</a> and the community in
	general.
	</p>
	<p>
	Corosync also began life in <a href="https://www.ohloh.net/p/corosync/analyses/latest/languages_summary">2004</a>
	but was then part of the <a href="https://www.ohloh.net/p/openAIS">OpenAIS project</a>.
	It is primarily a <a href="https://www.redhat.com/">Red Hat</a> initiative,
	with considerable help and support from the folks in the community.
	</p>
	<p>
	The core ClusterLabs team is made up of full-time
	developers from Australia, Austria, Canada, China, Czech
	Repulic, England, Germany, Sweden and the USA. Contributions to
	the code or documentation are always welcome.
	</p>
	<p>
	The ClusterLabs stack ships with most modern enterprise
	distributions and has been deployed in many critical
	environments including Deutsche Flugsicherung GmbH
	(<a href="http://www.dfs.de/dfs_homepage/en/">DFS</a>)
	which uses Pacemaker to ensure
	its <a href="http://www.novell.com/success/dfs.html">air
	traffic control systems</a> are always available.
	</p>
	</section>

	diff --git a/src/doc/index.html b/src/doc/index.html
	index fd5cf64..c9fbe7d 100644
	--- a/src/doc/index.html
	+++ b/src/doc/index.html
	@@ -1,25 +1,25 @@
	---
	layout: pacemaker
	title: Documentation
	---
	<section id="main">

	<header class="major">
	<h2>General</h2>
	</header>

	<p>
	- The <a href="https://wiki.clusterlabs.org/wiki">ClusterLabs wiki</a> has
	+ The <a href="https://projects.clusterlabs.org/w/">ClusterLabs wiki</a> has
	how-to's, tips, and other information that doesn't make it into the project
	manuals.
	</p>

	<header class="major">
	<h2>Project-specific</h2>
	</header>

	<ul>
	<li><a href="/pacemaker/doc/">Pacemaker</a></li>
	</ul>

	-</section>
	+</section>
	diff --git a/src/help.html b/src/help.html
	index 7b62f4d..a56b4e7 100644
	--- a/src/help.html
	+++ b/src/help.html
	@@ -1,132 +1,132 @@
	---
	layout: pacemaker
	title: Help
	---
	- <section>
	- <header class="main">
	- <h1>Getting Help</h1>
	- </header>
	+<section>
	+ <header class="main">
	+ <h1>Getting Help</h1>
	+ </header>
	+ <p>
	+ A good first step is always to check out
	+ the <a href="/faq.html">FAQ</a>
	+ and <a href="/pacemaker/doc/">documentation</a>. Otherwise, many
	+ members of the community hang out
	+ on <a href="irc://irc.libera.chat/#clusterlabs">IRC</a>
	+ and are happy to answer questions. We are spread out over
	+ many timezones though (and have day jobs), so you may need
	+ to be patient when waiting for a reply.
	+ </p>

	- <p>
	- A good first step is always to check out
	- the <a href="/faq.html">FAQ</a>
	- and <a href="/pacemaker/doc/">documentation</a>. Otherwise, many
	- members of the community hang out
	- on <a href="irc://irc.libera.chat/#clusterlabs">IRC</a>
	- and are happy to answer questions. We are spread out over
	- many timezones though (and have day jobs), so you may need
	- to be patient when waiting for a reply.
	- </p>
	+ <p>
	+ Extended or complex issues might be better sent to the
	+ relevant <a href="https://projects.clusterlabs.org/w/clusterlabs/clusterlabs_mailing_lists/">mailing list</a>
	+ (you'll need to subscribe in order to send messages).
	+ </p>

	- <p>
	- Extended or complex issues might be better sent to the
	- relevant <a href="https://wiki.clusterlabs.org/wiki/Mailing_lists">mailing list</a>
	- (you'll need to subscribe in order to send messages).
	- </p>
	+ <p>
	+ People new to the project, or Open Source generally, are
	+ encouraged to
	+ read <a href="http://www.mikeash.com/getting_answers.html">Getting
	+ Answers</a> by Mike Ash from Rogue Amoeba. It provides
	+ some very good tips on effective communication with groups
	+ such as this one. Following the advice it contains will
	+ greatly increase the chance of a quick and helpful reply.
	+ </p>

	- <p>
	- People new to the project, or Open Source generally, are
	- encouraged to
	- read <a href="http://www.mikeash.com/getting_answers.html">Getting
	- Answers</a> by Mike Ash from Rogue Amoeba. It provides
	- some very good tips on effective communication with groups
	- such as this one. Following the advice it contains will
	- greatly increase the chance of a quick and helpful reply.
	- </p>
	+ <p>
	+ Bugs and other problems can also be reported
	+ via <a href="https://bugs.clusterlabs.org/">Bugzilla</a>.
	+ </p>

	- <p>Bugs and other problems can also be reported
	- via <a href="https://bugs.clusterlabs.org/">Bugzilla</a>.
	- </p>
	- <p>
	- Or if you already know the
	- solution, <a href="https://help.github.com/articles/using-pull-requests">submit
	- a patch</a> against
	- our <a href="https://github.com/ClusterLabs/pacemaker">GitHub
	- repository</a>.
	- </p>
	+ <p>
	+ Or if you already know the
	+ solution, <a href="https://help.github.com/articles/using-pull-requests">submit
	+ a patch</a> against
	+ our <a href="https://github.com/ClusterLabs/pacemaker">GitHub
	+ repository</a>.
	+ </p>

	- <p>
	- The development of most of the ClusterLabs-related projects take place as part of
	- the <a href="https://github.com/ClusterLabs/">ClusterLabs</a> organization at Github,
	- and the source code and issue trackers for these projects can be found there.
	- </p>
	+ <p>
	+ The development of most of the ClusterLabs-related projects take place as part of
	+ the <a href="https://github.com/ClusterLabs/">ClusterLabs</a> organization at Github,
	+ and the source code and issue trackers for these projects can be found there.
	+ </p>

	- <h1>Providing Help</h1>
	- <p>
	- If you find this project useful, you may want to consider supporting its future development.
	- There are a number of ways to support the project (in no particular order):
	- </p>
	- <ul>
	- <li>Spread the word</li>
	- <li>Help others on the <a href="https://wiki.clusterlabs.org/wiki/Mailing_lists">mailing list</a></li>
	- <li><a href="https://wiki.clusterlabs.org/wiki/Contributing_Patches">Contribute patches</a></li>
	- <li>Contribute documentation and examples or <a href="https://wiki.clusterlabs.org/">update the wiki</a></li>
	- <li>
	- Use it on
	- <a href="https://www.redhat.com/en/resources/high-availability-add-datasheet">Red Hat Enterprise Linux</a>
	- or <a href="https://www.suse.com/products/highavailability/">SUSE Linux Enterprise Server</a>.
	- Red Hat and SuSE fund the majority of our work, using it on their products
	- helps ensure they continue to see it as a priority.
	- </li>
	- </ul>
	- <p>
	- Thank you for using Pacemaker
	- </p>
	+ <h1>Providing Help</h1>
	+ <p>
	+ If you find this project useful, you may want to consider supporting its future development.
	+ There are a number of ways to support the project (in no particular order):
	+ </p>
	+ <ul>
	+ <li>Spread the word</li>
	+ <li>Help others on the <a href="https://projects.clusterlabs.org/w/clusterlabs/clusterlabs_mailing_lists/">mailing list</a></li>
	+ <li><a href="https://github.com/ClusterLabs/pacemaker/blob/main/CONTRIBUTING.md">Contribute patches</a></li>
	+ <li>Contribute documentation and examples or <a href="https://projects.clusterlabs.org/w/">update the wiki</a></li>
	+ <li>Use it on <a
	+ href="https://www.redhat.com/en/resources/high-availability-add-datasheet">Red Hat Enterprise Linux</a>
	+ or <a href="https://www.suse.com/products/highavailability/">SUSE Linux Enterprise Server</a>.
	+ Red Hat and SuSE fund the majority of our work, using it on their products
	+ helps ensure they continue to see it as a priority.
	+ </li>
	+ </ul>
	+ <p>
	+ Thank you for using Pacemaker
	+ </p>

	- <h1>Professional Support</h1>
	- <ul>
	- <li>
	- <a href="https://www.suse.com/">SUSE</a> supports Pacemaker and DRBD as part of their
	- <a href="https://www.suse.com/products/highavailability/">High Availability Extension</a>
	- </li>
	- <li>
	- <a href="https://www.redhat.com">Red Hat</a> supports ClusterLabs
	- software as part of the RHEL
	- <a href="https://www.redhat.com/en/resources/high-availability-add-datasheet">High
	- Availability Add-on</a>
	- </li>
	- <li>
	- <a href="http://www.schwartzkopff.org/">Michael Schwartzkopff</a> (author of the book
	- <a href="https://www.oreilly.de/buecher/120147/9783868993585-clusterbau%3A-hochverf%C3%BCgbarkeit-mit-linux.html">"Clusterbau:
	- Hochverfuegbarkeit mit Pacemaker, OpenAIS, Heartbeat und LVS]"</a>)
	- offers consulting and support for Linux clusters (HA, LVS, DRBD, etc.), as well
	- as training through <a href="https://www.heinlein-support.de/">Heinlein Support</a>.
	- </li>
	- <li>
	- <a href="https://www.linbit.com/">LINBIT</a> provides global support
	- for DRBD, Linux-HA, Pacemaker and other HA-software
	- suites. Philipp Reisner and Lars Ellenberg, the authors
	- of <a href="https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device">DRBD</a>, oversee
	- LINBIT's Professional Services. In addition, they offer training services, certification,
	- consultancy, and turnkey solutions around DRBD and Pacemaker
	- </li>
	- <li>
	- <a href="https://www.alteeve.com/c/">Alteeve</a> is a software
	- and systems design company specializing in server uptime and
	- operational continuity. Their Anvil! product offers an all-in-one
	- supported clustering solution using ClusterLabs software.
	- </li>
	- <li>
	- <a href="https://www.b1-systems.de/">B1 Systems</a>
	- provides support (troubleshooting, maintenance,
	- debugging, ...), consulting and training for Linux
	- clusters, load balancing, storage clusters, virtual
	- system cluster and high availability. This includes
	- Pacemaker, Heartbeat and LVS as well as various cluster
	- filesystems (OCFS2, GPFS, GFS, ...)
	- </li>
	- <li>
	- <a href="https://www.gurulabs.com">Gurulabs</a> offers training
	- on many topics, including
	- <a href="https://www.gurulabs.com/linux-training/courses/GL645/">Linux
	- high availability (HA) clustering and HA storage administration.</a>
	- </li>
	- </ul>
	+ <h1>Professional Support</h1>
	+ <ul>
	+ <li>
	+ <a href="https://www.suse.com/">SUSE</a> supports Pacemaker and DRBD as part of their
	+ <a href="https://www.suse.com/products/highavailability/">High Availability Extension</a>
	+ </li>
	+ <li>
	+ <a href="https://www.redhat.com">Red Hat</a> supports ClusterLabs
	+ software as part of the RHEL
	+ <a href="https://www.redhat.com/en/resources/high-availability-add-datasheet">High
	+ Availability Add-on</a>
	+ </li>
	+ <li>
	+ <a href="http://www.schwartzkopff.org/">Michael Schwartzkopff</a> (author of the book
	+ <a href="https://www.oreilly.de/buecher/120147/9783868993585-clusterbau%3A-hochverf%C3%BCgbarkeit-mit-linux.html">"Clusterbau:
	+ Hochverfuegbarkeit mit Pacemaker, OpenAIS, Heartbeat und LVS]"</a>)
	+ offers consulting and support for Linux clusters (HA, LVS, DRBD, etc.), as well
	+ as training through <a href="https://www.heinlein-support.de/">Heinlein Support</a>.
	+ </li>
	+ <li>
	+ <a href="https://www.linbit.com/">LINBIT</a> provides global support
	+ for DRBD, Linux-HA, Pacemaker and other HA-software
	+ suites. Philipp Reisner and Lars Ellenberg, the authors
	+ of <a href="https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device">DRBD</a>, oversee
	+ LINBIT's Professional Services. In addition, they offer training services, certification,
	+ consultancy, and turnkey solutions around DRBD and Pacemaker
	+ </li>
	+ <li>
	+ <a href="https://www.alteeve.com/c/">Alteeve</a> is a software
	+ and systems design company specializing in server uptime and
	+ operational continuity. Their Anvil! product offers an all-in-one
	+ supported clustering solution using ClusterLabs software.
	+ </li>
	+ <li>
	+ <a href="https://www.b1-systems.de/">B1 Systems</a>
	+ provides support (troubleshooting, maintenance,
	+ debugging, ...), consulting and training for Linux
	+ clusters, load balancing, storage clusters, virtual
	+ system cluster and high availability. This includes
	+ Pacemaker, Heartbeat and LVS as well as various cluster
	+ filesystems (OCFS2, GPFS, GFS, ...)
	+ </li>
	+ <li>
	+ <a href="https://www.gurulabs.com">Gurulabs</a> offers training
	+ on many topics, including
	+ <a href="https://www.gurulabs.com/linux-training/courses/GL645/">Linux
	+ high availability (HA) clustering and HA storage administration.</a>
	+ </li>
	+ </ul>

	- <p>
	- Does your company provide Pacemaker training or
	- support? <a href="https://lists.clusterlabs.org/mailman/listinfo/users">Let
	- us know!</a>
	- </p>
	+ <p>
	+ Does your company provide Pacemaker training or
	+ support? <a href="https://lists.clusterlabs.org/mailman/listinfo/users">Let
	+ us know!</a>
	+ </p>

	- </section>
	+</section>
	diff --git a/src/pacemaker/doc/index.php b/src/pacemaker/doc/index.php
	index 1cd8d48..4c2aea5 100644
	--- a/src/pacemaker/doc/index.php
	+++ b/src/pacemaker/doc/index.php
	@@ -1,186 +1,178 @@
	---
	layout: pacemaker
	title: Pacemaker Documentation
	---
	<section id="main">

	<p>
	Most of the documentation listed here was generated from the Pacemaker
	sources.
	</p>

	<header class="major">
	<h2>Where to Start</h2>
	</header>
	<p>
	If you're new to Pacemaker or clustering in general, the best place to
	start is <b>Clusters from Scratch</b>, which walks you step-by-step through
	the installation and configuration of a high-availability cluster with
	Pacemaker. It even makes common configuration mistakes so that it can
	demonstrate how to fix them.
	</p>

	<p>
	On the other hand, if you're looking for an exhaustive reference of all
	of Pacemaker's options and features, try <b>Pacemaker Explained</b>. It's
	dry, but should have the answers you're looking for.
	</p>

	<p>
	- There is also a <a href="https://wiki.clusterlabs.org/wiki">project wiki</a>
	+ There is also a <a href="https://projects.clusterlabs.org/w/">project wiki</a>
	with examples, how-to guides, and other information that doesn't make it
	into the manuals.
	</p>

	<header class="major">
	<h2>Unversioned documentation</h2>
	</header>

	<section class="docset">
	<h3 class="docversion">Command-line tools</h3>
	<table class="publican-doc">
	<tr>
	<td>man(1) pages</td>
	<td>[<a class="doclink" href="/pacemaker/man/">html</a>]</td>
	</tr>
	</table>
	</section>

	<section class="docset">
	<h3 class="docversion">General Concepts (somewhat outdated)</h3>
	<table class="publican-doc">
	- <tr>
	- <td>Ordering Explained</td>
	- <td>[<a class="doclink" href="https://wiki.clusterlabs.org/w/images/a/ae/Ordering_Explained_-_White.pdf">pdf</a>]</td>
	- </tr>
	- <tr>
	- <td>Colocation Explained</td>
	- <td>[<a class="doclink" href="https://wiki.clusterlabs.org/w/images/8/8a/Colocation_Explained_-_White.pdf">pdf</a>]</td>
	- </tr>
	<tr>
	<td>Configuring Fencing with crmsh</td>
	<td>[<a class="doclink" href="crm_fencing.html">html</a>]</td>
	</tr>
	</table>
	</section>

	<?php

	function get_versions($pattern) {
	$versions = array();
	foreach (glob($pattern) as $item)
	if ($item != '.' && $item != '..' && is_dir($item) && !is_link($item))
	$versions[] = basename($item);

	return array_reverse(array_unique($versions));
	}

	function doc_version_heading($base, $version) {
	$title = file_get_contents("$base/title-$version.txt");
	if (empty($title)) {
	$title = $version;
	}
	echo " <h3 class='docversion'>$title </h3>\n";
	$desc = file_get_contents("$base/desc-$version.txt");
	if (!empty($desc)) {
	echo " <p>$desc </p>\n";
	}
	$build = file_get_contents("$base/build-$version.txt");
	if (!empty($build)) {
	echo " <p>$build </p>\n";
	}
	}

	function sphinx_docs_for_version($base, $version) {
	echo " <section class='docset'>\n";
	doc_version_heading($base, $version);

	/* poor choice of name for style ... */
	echo " <table class=\"publican-doc\">\n";
	foreach (glob("$base/$version/*") as $filename) {
	$book = basename($filename);
	$formats = glob("$base/$version/$book/*");
	if (!empty($formats)) {
	echo " <tr>\n";
	echo " <td>" . str_replace("_", " ", $book) . "</td>\n";
	echo " <td>";

	foreach ($formats as $format) {
	$format_name = basename($format);
	if (strncmp($format_name, "build-", 6) !== 0) {
	if ($format_name == "pdf") {
	$link = "$format/$book.pdf";
	} else {
	$link = "$format/";
	}
	echo " [<a class='doclink' href='$link'>" . $format_name . "</a>]";
	}
	}
	echo "</td>\n";
	echo " </tr>\n";
	}
	}
	echo " </table>\n";
	echo " </section>\n";
	}

	function publican_docs_for_version($base, $version, $langs) {
	echo " <section class='docset'>\n";
	doc_version_heading($base, $version);

	$books = array();
	foreach (glob("$base/en-US/Pacemaker/$version/pdf/*") as $filename) {
	$books[] = basename($filename);
	}

	echo '<table class="publican-doc">';
	foreach ($books as $b) {
	foreach ($langs as $lang) {
	if (glob("$base/$lang/Pacemaker/$version/pdf/$b/*-$lang.pdf")) {
	echo '<tr><td>'.str_replace("_", " ", $b)." ($lang)</td>";

	echo '<td>';
	foreach (glob("$base/$lang/Pacemaker/$version/epub/$b/*.epub") as $filename) {
	echo " [<a class='doclink' href=$filename>epub</a>]";
	}
	foreach (glob("$base/$lang/Pacemaker/$version/pdf/$b/*.pdf") as $filename) {
	echo " [<a class='doclink' href=$filename>pdf</a>]";
	}
	foreach (glob("$base/$lang/Pacemaker/$version/html/$b/index.html") as $filename) {
	echo " [<a class='doclink' href=$filename>html</a>]";
	}
	foreach (glob("$base/$lang/Pacemaker/$version/html-single/$b/index.html") as $filename) {
	echo " [<a class='doclink' href=$filename>html-single</a>]";
	}
	foreach (glob("$base/$lang/Pacemaker/$version/txt/$b/*.txt") as $filename) {
	echo " [<a class='doclink' href=$filename>txt</a>]";
	}
	echo "</td></tr>";
	}
	}
	}
	echo "</table>";
	echo "</section>";
	}

	echo "<header class='major'>\n<h2>Versioned documentation</h2>\n</header>";
	$langs = array();
	// for now, show only US English; other translations haven't been maintained
	$langs[] = "en-US";

	foreach (get_versions("./[0-9].") as $v) {
	sphinx_docs_for_version(".", $v);
	}

	echo "<header class='major'>\n<h2>Deprecated documentation</h2>\n</header>";
	foreach(get_versions("deprecated//Pacemaker/") as $v) {
	$langs = array();
	foreach (glob("deprecated/*/Pacemaker/$v") as $item) {
	$langs[] = basename(dirname(dirname($item)));
	}
	publican_docs_for_version("deprecated", $v, $langs);
	}

	?>

	</section>
	diff --git a/src/pacemaker/index.html b/src/pacemaker/index.html
	index 0926048..aafa99d 100644
	--- a/src/pacemaker/index.html
	+++ b/src/pacemaker/index.html
	@@ -1,82 +1,80 @@
	---
	layout: default
	title: Pacemaker
	---

	<!-- Banner -->
	<section id="banner">
	<div class="content">
	- <header>
	- <h1>Pacemaker</h1>
	- <p>Cluster Resource Manager</p>
	- </header>
	- <p>
	- <b>Pacemaker</b> is an <a href="https://en.wikipedia.org/wiki/Open-source_model">open source</a>,
	- <a href="https://en.wikipedia.org/wiki/High_availability">high availability</a>
	- resource manager suitable for both small and large
	- <a href="https://en.wikipedia.org/wiki/Computer_cluster">clusters</a>.
	- </p>
	- </div>
	+ <header>
	+ <h1>Pacemaker</h1>
	+ <p>Cluster Resource Manager</p>
	+ </header>
	+ <p>
	+ <b>Pacemaker</b> is an <a href="https://en.wikipedia.org/wiki/Open-source_model">open source</a>,
	+ <a href="https://en.wikipedia.org/wiki/High_availability">high availability</a>
	+ resource manager suitable for both small and large
	+ <a href="https://en.wikipedia.org/wiki/Computer_cluster">clusters</a>.
	+ </p>
	+ </div>
	<span class="image object">
	{% image pacemaker-notext.svg %}
	</span>
	</section>

	+<section id="main">
	+ <a id="info"> </a>
	+ <blockquote class="pullquote">
	+ "The definitive open-source high-availability stack for the Linux
	+ platform builds upon the Pacemaker cluster resource manager."
	+ -- <cite>LINUX Journal</cite>,
	+ <a href="http://www.linuxjournal.com/content/ahead-pack-pacemaker-high-availability-stack">"Ahead
	+ of the Pack: the Pacemaker High-Availability Stack"</a>
	+ </blockquote>

	- <section id="main">
	- <a id="info"> </a>
	-
	+ <a id="features"> </a>
	+ <h2>Features</h2>
	+ <ul>
	+ <li>Detection and recovery of machine and application-level failures</li>
	+ <li>Supports practically any <a
	+ href="https://en.wikipedia.org/wiki/High-availability_cluster#Node_configurations">redundancy configuration</a></li>
	+ <li>Supports both <a href="https://en.wikipedia.org/wiki/Quorum_%28distributed_computing%29">quorate</a> and <a href="https://web.archive.org/web/20110727185030/http://devresources.linux-foundation.org/dev/clusters/docs/ResourceDrivenClusters.pdf">resource-driven</a> clusters</li>
	+ <li>Configurable <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/options.html#cluster-options">strategies</a> for dealing with <a href="https://en.wikipedia.org/wiki/Quorum_%28Distributed_Systems%29">quorum</a> loss (when multiple nodes fail)</li>
	+ <li>Supports application <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#specifying-the-order-in-which-resources-should-start-stop">startup/shutdown ordering</a>, without requiring the applications to run on the same node</li>
	+ <li>Supports applications that must or must not run on the <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#placing-resources-relative-to-other-resources">same node</a></li>
	+ <li>Supports applications which need to be active on <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#clones-resources-that-can-have-multiple-active-instances">multiple nodes</a></li>
	+ <li>Supports applications with dual roles (<a href="https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#promotable-clones">promoted and unpromoted</a>)</li>
	+ <li>Provably correct response to any failure or cluster state. The cluster's
	+ response to any stimuli can be tested offline <i>before</i> the condition exists
	+ </li>
	+ </ul>

	- <blockquote class="pullquote">
	- "The definitive open-source high-availability stack for the Linux
	- platform builds upon the Pacemaker cluster resource manager."
	- -- <cite>LINUX Journal</cite>,
	- <a href="http://www.linuxjournal.com/content/ahead-pack-pacemaker-high-availability-stack">"Ahead
	- of the Pack: the Pacemaker High-Availability Stack"</a>
	- </blockquote>
	-
	- <a id="features"> </a>
	- <h2>Features</h2>
	- <ul>
	- <li>Detection and recovery of machine and application-level failures</li>
	- <li>Supports practically any <a href="https://wiki.clusterlabs.org/wiki/ClusterTypes">redundancy configuration</a></li>
	- <li>Supports both <a href="https://en.wikipedia.org/wiki/Quorum_%28distributed_computing%29">quorate</a> and <a href="https://web.archive.org/web/20110727185030/http://devresources.linux-foundation.org/dev/clusters/docs/ResourceDrivenClusters.pdf">resource-driven</a> clusters</li>
	- <li>Configurable <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/options.html#cluster-options">strategies</a> for dealing with <a href="https://en.wikipedia.org/wiki/Quorum_%28Distributed_Systems%29">quorum</a> loss (when multiple nodes fail)</li>
	- <li>Supports application <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#specifying-the-order-in-which-resources-should-start-stop">startup/shutdown ordering</a>, without requiring the applications to run on the same node</li>
	- <li>Supports applications that must or must not run on the <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/constraints.html#placing-resources-relative-to-other-resources">same node</a></li>
	- <li>Supports applications which need to be active on <a href="/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#clones-resources-that-can-have-multiple-active-instances">multiple nodes</a></li>
	- <li>Supports applications with dual roles (<a href="https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/advanced-resources.html#promotable-clones">promoted and unpromoted</a>)<br/><br/></li>
	- <li>Provably correct response to any failure or cluster state. The cluster's
	- response to any stimuli can be tested offline <i>before</i> the condition exists
	- </li>
	- </ul>
	-
	- <h2>Background</h2>
	- <a class="ohloh" href="https://www.openhub.net/p/pacemaker?ref=sample">
	- <img alt="Black Duck Open Hub project report for pacemaker"
	- border="0"
	- src="https://www.openhub.net/p/pacemaker/widgets/project_partner_badge.gif">
	- </a>
	- <p>
	- Pacemaker has been around since
	- <a href="https://www.openhub.net/p/pacemaker/analyses/latest/languages_summary">2004</a>
	- and is a collaborative effort by the ClusterLabs community, including
	- full-time developers with
	- <a href="https://www.redhat.com/">Red Hat</a>
	- and <a href="https://www.suse.com/">SuSE</a>.
	- </p>
	- <p>
	- Pacemaker ships with most modern Linux distributions and has been
	- deployed in many critical environments including Deutsche
	- Flugsicherung GmbH
	- (<a href="http://www.dfs.de/dfs_homepage/de/">DFS</a>)
	- which uses Pacemaker to ensure
	- its <a href="http://www.novell.com/success/dfs.html">air traffic
	- control systems</a> are always available.
	- </p>
	- <p>
	- <a href="mailto:andrew@beekhof.net">Andrew Beekhof</a> was
	- Pacemaker's original author and long-time project lead. The current
	- project lead is <a href="mailto:kgaillot@redhat.com">Ken Gaillot</a>.
	- </p>
	- </section>
	+ <h2>Background</h2>
	+ <a class="ohloh" href="https://www.openhub.net/p/pacemaker?ref=sample">
	+ <img alt="Black Duck Open Hub project report for pacemaker"
	+ border="0"
	+ src="https://www.openhub.net/p/pacemaker/widgets/project_partner_badge.gif">
	+ </a>
	+ <p>
	+ Pacemaker has been around since
	+ <a href="https://www.openhub.net/p/pacemaker/analyses/latest/languages_summary">2004</a>
	+ and is a collaborative effort by the ClusterLabs community, including
	+ full-time developers with
	+ <a href="https://www.redhat.com/">Red Hat</a>
	+ and <a href="https://www.suse.com/">SuSE</a>.
	+ </p>
	+ <p>
	+ Pacemaker ships with most modern Linux distributions and has been
	+ deployed in many critical environments including Deutsche
	+ Flugsicherung GmbH
	+ (<a href="http://www.dfs.de/dfs_homepage/de/">DFS</a>)
	+ which uses Pacemaker to ensure
	+ its <a href="http://www.novell.com/success/dfs.html">air traffic
	+ control systems</a> are always available.
	+ </p>
	+ <p>
	+ <a href="mailto:andrew@beekhof.net">Andrew Beekhof</a> was
	+ Pacemaker's original author and long-time project lead. The current
	+ project lead is <a href="mailto:kgaillot@redhat.com">Ken Gaillot</a>.
	+ </p>
	+</section>
	diff --git a/wiki.clusterlabs.org/htmlets/iuseit.html b/wiki.clusterlabs.org/htmlets/iuseit.html
	deleted file mode 100644
	index 08d6342..0000000
	--- a/wiki.clusterlabs.org/htmlets/iuseit.html
	+++ /dev/null
	@@ -1 +0,0 @@
	-<script type="text/javascript" src="http://www.ohloh.net/p/319420/widgets/project_users_logo.js"></script>
	diff --git a/wiki.clusterlabs.org/htmlets/lang.html b/wiki.clusterlabs.org/htmlets/lang.html
	deleted file mode 100644
	index 3183cd5..0000000
	--- a/wiki.clusterlabs.org/htmlets/lang.html
	+++ /dev/null
	@@ -1 +0,0 @@
	-<script type="text/javascript" src="http://www.ohloh.net/p/319420/widgets/project_languages.js"></script>
	diff --git a/wiki.clusterlabs.org/htmlets/logopoll.html b/wiki.clusterlabs.org/htmlets/logopoll.html
	deleted file mode 100644
	index ee0c676..0000000
	--- a/wiki.clusterlabs.org/htmlets/logopoll.html
	+++ /dev/null
	@@ -1,4 +0,0 @@
	-<script type="text/javascript" charset="utf-8" src="http://static.polldaddy.com/p/4074769.js"></script>
	-<noscript>
	- <a href="http://polldaddy.com/poll/4074769/">Which Logo is Better?</a><span style="font-size:9px;"><a href="http://polldaddy.com/features-surveys/">online surveys</a></span>
	-</noscript>
	diff --git a/wiki.clusterlabs.org/htmlets/sizepoll.html b/wiki.clusterlabs.org/htmlets/sizepoll.html
	deleted file mode 100644
	index dd0fae0..0000000
	--- a/wiki.clusterlabs.org/htmlets/sizepoll.html
	+++ /dev/null
	@@ -1,4 +0,0 @@
	-<script type="text/javascript" charset="utf-8" src="http://static.polldaddy.com/p/1866622.js"></script>
	-<noscript>
	- <a href="http://polldaddy.com/poll/1866622/">What sized clusters do you have?</a><span style="font-size:9px;"><a href="http://polldaddy.com/features-surveys/">online surveys</a></span>
	-</noscript>
	diff --git a/wiki.clusterlabs.org/htmlets/stats.html b/wiki.clusterlabs.org/htmlets/stats.html
	deleted file mode 100644
	index 083c446..0000000
	--- a/wiki.clusterlabs.org/htmlets/stats.html
	+++ /dev/null
	@@ -1 +0,0 @@
	-<script type="text/javascript" src="http://www.ohloh.net/p/319420/widgets/project_partner_badge.js"></script>
	diff --git a/wiki.clusterlabs.org/htmlets/usagepoll.html b/wiki.clusterlabs.org/htmlets/usagepoll.html
	deleted file mode 100644
	index 471433b..0000000
	--- a/wiki.clusterlabs.org/htmlets/usagepoll.html
	+++ /dev/null
	@@ -1,4 +0,0 @@
	-<script type="text/javascript" charset="utf-8" src="http://static.polldaddy.com/p/4074807.js"></script>
	-<noscript>
	- <a href="http://polldaddy.com/poll/4074807/">Which Distribution do you use for Pacemaker?</a><span style="font-size:9px;"><a href="http://polldaddy.com/features-surveys/">survey software</a></span>
	-</noscript>
	diff --git a/wiki.clusterlabs.org/htmlets/versions.html b/wiki.clusterlabs.org/htmlets/versions.html
	deleted file mode 100644
	index 9e49e00..0000000
	--- a/wiki.clusterlabs.org/htmlets/versions.html
	+++ /dev/null
	@@ -1,2 +0,0 @@
	-<div id='history-graph'></div>
	-<script type="text/javascript" src="http://www.clusterlabs.org/js/pcmk_versions.js"></script>
	diff --git a/wiki.clusterlabs.org/logo.png b/wiki.clusterlabs.org/logo.png
	deleted file mode 100644
	index fa419ce..0000000
	Binary files a/wiki.clusterlabs.org/logo.png and /dev/null differ
	diff --git a/wiki.clusterlabs.org/robots.txt b/wiki.clusterlabs.org/robots.txt
	index b5da9a3..1f53798 100644
	--- a/wiki.clusterlabs.org/robots.txt
	+++ b/wiki.clusterlabs.org/robots.txt
	@@ -1,2 +1,2 @@
	User-agent: *
	-Disallow: /w/index.php?
	+Disallow: /
	diff --git a/wiki.clusterlabs.org/wiki-banner-blue.png b/wiki.clusterlabs.org/wiki-banner-blue.png
	deleted file mode 100644
	index 5867c98..0000000
	Binary files a/wiki.clusterlabs.org/wiki-banner-blue.png and /dev/null differ

File Metadata

Mime Type: text/x-diff
Expires: Wed, Jun 25, 5:28 AM (1 d, 6 h)
Storage Engine: blob
Storage Format: Raw Data
Storage Handle: 1952292
Default Alt Text: (44 KB)

No OneTemporaryActions

View Options

File Metadata

Event Timeline

No OneTemporary
Actions