OpenStack:Essex Multi Node HA - Revision history

Danehans: /* site manifest */

2012-11-16T23:04:29Z

site manifest

← Older revision		Revision as of 23:04, 16 November 2012
Line 251:		Line 251:
	** class { 'apt': } This module manages the initial configuration of apt.		** class { 'apt': } This module manages the initial configuration of apt.
	** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.		** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.
-	** [apt::pin] [~~Pins~~ https://help.ubuntu.com/community/PinningHowto] packages from the Cisco Edition software repositories.	+	** [apt::pin] [https://help.ubuntu.com/community/PinningHowto Pins] packages from the Cisco Edition software repositories.
	* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:		* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:
	** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]		** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]

Danehans: /* site manifest */

2012-11-16T23:03:54Z

site manifest

← Older revision		Revision as of 23:03, 16 November 2012
Line 251:		Line 251:
	** class { 'apt': } This module manages the initial configuration of apt.		** class { 'apt': } This module manages the initial configuration of apt.
	** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.		** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.
-	** [apt::pin] ~~Pins~~ [https://help.ubuntu.com/community/PinningHowto] packages from the Cisco Edition software repositories.	+	** [apt::pin] [Pins https://help.ubuntu.com/community/PinningHowto] packages from the Cisco Edition software repositories.
	* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:		* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:
	** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]		** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]

Danehans: /* site manifest */

2012-11-16T23:02:53Z

site manifest

← Older revision		Revision as of 23:02, 16 November 2012
Line 251:		Line 251:
	** class { 'apt': } This module manages the initial configuration of apt.		** class { 'apt': } This module manages the initial configuration of apt.
	** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.		** [apt::ppa] Adds the Cisco Edition ppa repository using <tt>add-apt-repository</tt>.
		+	** [apt::pin] Pins [https://help.ubuntu.com/community/PinningHowto] packages from the Cisco Edition software repositories.
	* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:		* Shared Variables: I will not address every shared variable, as many of them are self explanatory or include inline documentation. Here is a list of shared variables that can use additional explanation:
	** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]		** '''[$multi_host]''' Must be set to true. Establishes the [http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html#d6e7351 Nova multi-host networking model]

Danehans: /* Deploying Swift */

2012-11-08T21:29:30Z

Deploying Swift

← Older revision		Revision as of 21:29, 8 November 2012
Line 549:		Line 549:
	* Next, the storage nodes should be run again so that they can rsync the ring databases.		* Next, the storage nodes should be run again so that they can rsync the ring databases.
	* Add the 2nd Proxy Node.		* Add the 2nd Proxy Node.
-	* From a Proxy Node, ~~Verify~~ the contents of the ~~Rings~~:	+	* From a Proxy Node, verify the contents of the Swift rings:

	<pre>swift-ring-builder /etc/swift/account.builder		<pre>swift-ring-builder /etc/swift/account.builder

Danehans: /* Deploying Swift */

2012-11-08T21:28:49Z

Deploying Swift

← Older revision		Revision as of 21:28, 8 November 2012
Line 549:		Line 549:
	* Next, the storage nodes should be run again so that they can rsync the ring databases.		* Next, the storage nodes should be run again so that they can rsync the ring databases.
	* Add the 2nd Proxy Node.		* Add the 2nd Proxy Node.
		+	* From a Proxy Node, Verify the contents of the Rings:
		+
		+	<pre>swift-ring-builder /etc/swift/account.builder
		+
		+	swift-ring-builder /etc/swift/container.builder
		+
		+	swift-ring-builder /etc/swift/object.builder</pre>
		+

	The [https://github.com/danehans/puppet-openstack/blob/essex-ha/examples/swift-nodes.pp example configuration] creates five storage devices on every node. Make sure to increase/decrease the following swift-nodes.pp definitions based on the number of hard disks in your Storage Nodes:		The [https://github.com/danehans/puppet-openstack/blob/essex-ha/examples/swift-nodes.pp example configuration] creates five storage devices on every node. Make sure to increase/decrease the following swift-nodes.pp definitions based on the number of hard disks in your Storage Nodes:

Danehans: /* Deploying Swift */

2012-11-08T21:25:34Z

Deploying Swift

← Older revision		Revision as of 21:25, 8 November 2012
Line 539:		Line 539:

	* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder (Proxy Node) into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.		* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder (Proxy Node) into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.
-	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in the Proxy Node) collects the storage endpoints and ~~create~~ the ring database. It also creates an rsync server which is used to host the ring database. ~~Resources are exported that~~ are used to rsync the ring database from ~~this server~~.	+	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in the Proxy Node) collects the storage endpoints and creates the ring database. It also creates an rsync server which is used to host the ring database. The resources are used to rsync the ring database from the Swift Proxy.
	* If you like, you can verify the contents of the Swift storeconfigs in the Puppet Master database:		* If you like, you can verify the contents of the Swift storeconfigs in the Puppet Master database:
	<pre>mysql		<pre>mysql

Danehans: /* Deploying Swift */

2012-11-08T21:23:14Z

Deploying Swift

← Older revision		Revision as of 21:23, 8 November 2012
Line 538:		Line 538:
	The Swift Nodes must be configured in the following order:		The Swift Nodes must be configured in the following order:

-	* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.	+	* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder (Proxy Node) into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.
	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in the Proxy Node) collects the storage endpoints and create the ring database. It also creates an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.		* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in the Proxy Node) collects the storage endpoints and create the ring database. It also creates an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.
	* If you like, you can verify the contents of the Swift storeconfigs in the Puppet Master database:		* If you like, you can verify the contents of the Swift storeconfigs in the Puppet Master database:

Danehans: /* Deploying Swift */

2012-11-08T21:22:19Z

Deploying Swift

← Older revision		Revision as of 21:22, 8 November 2012
Line 539:		Line 539:

	* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.		* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.
-	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in Proxy Node) ~~needs to collect~~ the storage endpoints and create the ring database ~~before the proxy can be installed~~. It also ~~sets up~~ an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.	+	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in the Proxy Node) collects the storage endpoints and create the ring database. It also creates an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.
		+	* If you like, you can verify the contents of the Swift storeconfigs in the Puppet Master database:
		+	<pre>mysql
		+
		+	use puppet;
		+
		+	select * from resources;</pre>
		+
	* Next, the storage nodes should be run again so that they can rsync the ring databases.		* Next, the storage nodes should be run again so that they can rsync the ring databases.
-	* Next, [http://docs.openstack.org/essex/openstack-compute/install/apt/content/verify-swift-installation.html verify Swift] is operating properly.
	* Add the 2nd Proxy Node.		* Add the 2nd Proxy Node.

Danehans: /* Deploying Swift */

2012-11-08T21:15:41Z

Deploying Swift

← Older revision		Revision as of 21:15, 8 November 2012
Line 539:		Line 539:

	* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.		* First the storage nodes need to be configured. This creates the storage services (object, container, account) and exports all of the storage endpoints for the ring builder into storeconfigs. '''Note:''' It is expected that the account, object, and container replication service will fail to start during the initial puppet run. You are ready to move to the first Proxy Node when you have reached this state in your puppet runs for the Storage Nodes.
-	* Next, ~~the ringbuilder and~~ Swift Proxy 1 ~~must~~ be ~~configured~~. The ringbuilder needs to collect the storage endpoints and create the ring database before the proxy can be installed. It also sets up an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.	+	* Next, Swift Proxy 1 should be deployed. The ringbuilder (included in Proxy Node) needs to collect the storage endpoints and create the ring database before the proxy can be installed. It also sets up an rsync server which is used to host the ring database. Resources are exported that are used to rsync the ring database from this server.
	* Next, the storage nodes should be run again so that they can rsync the ring databases.		* Next, the storage nodes should be run again so that they can rsync the ring databases.
	* Next, [http://docs.openstack.org/essex/openstack-compute/install/apt/content/verify-swift-installation.html verify Swift] is operating properly.		* Next, [http://docs.openstack.org/essex/openstack-compute/install/apt/content/verify-swift-installation.html verify Swift] is operating properly.

Danehans: /* Installation Order */

2012-11-05T16:43:48Z

Installation Order

← Older revision		Revision as of 16:43, 5 November 2012
Line 98:		Line 98:
	<ul>		<ul>
	<li><p>'''HAProxy Nodes''': Make sure the haproxy/keepalived services are running before proceeding to the next node type.</p></li>		<li><p>'''HAProxy Nodes''': Make sure the haproxy/keepalived services are running before proceeding to the next node type.</p></li>
-	<li><p>'''Swift Storage Nodes''': If you are rebuilding Swift Storage Nodes, the hard disks should be zero'ed out. Use clean-disk~~.pp~~ from the Cisco repo or use the following command on each storage node:</p>	+	<li><p>'''Swift Storage Nodes''': If you are rebuilding Swift Storage Nodes, the hard disks should be zero'ed out. Use the [https://github.com/CiscoSystems/cisco-openstack-docs/blob/master/examples/clean_disk.sh clean-disk script] from the Cisco repo or use the following command on each storage node before starting the rebuild:</p>
	<pre>for i in b c d e f <add/subtract drive letters as needed>		<pre>for i in b c d e f <add/subtract drive letters as needed>
	do		do