Hedvig: Install - Revision history

Shanal: /* Hedvig Storage Proxy */

2016-07-30T05:04:50Z

Hedvig Storage Proxy

Shanal: /* Prepare Storage node */

2016-07-30T05:01:31Z

Prepare Storage node

Shanal: /* Prepare Storage node */

2016-07-30T05:00:49Z

Prepare Storage node

Shanal: /* Hedvig cluster Install and config */

2016-07-26T07:01:52Z

Hedvig cluster Install and config

Shanal: /* Hedvig cluster Install and config */

2016-07-26T07:00:14Z

Hedvig cluster Install and config

Shanal: /* Install and config */

2016-07-26T06:58:22Z

Install and config

Shanal: /* Install and config */

2016-07-26T06:55:55Z

Install and config

Shanal: /* Hedvig Deployment server setup */

2016-07-26T06:10:16Z

Hedvig Deployment server setup

Shanal: /* Install and config */

2016-07-26T06:09:50Z

Install and config

Shanal: /* Install and config */

2016-07-26T06:09:20Z

Install and config

@@ Line 76: / Line 76: @@
 * Enable Jumbo frames.
 * /usr/local/hedvig/scripts/menu_hedvig.sh
 == Hedvig Deployment server setup ==

@@ Line 37: / Line 37: @@
 * All the drives should stay unformatted hedvig process take care of all formatting and setup.
 * Set the root password to hedvig.
-  <code>
+  <nowiki>
   sudo su -
 passwd
-</code>
+</nowiki>
 * Check all other nodes are accessible via SSH at port 22 .
 * Add host names of all the other storage nodes , proxy and deploy node.

@@ Line 37: / Line 37: @@
 * All the drives should stay unformatted hedvig process take care of all formatting and setup.
 * Set the root password to hedvig.
-<code>
+ <code>
-sudo su -
+ sudo su -
-passd
+passwd
 </code>
 * Check all other nodes are accessible via SSH at port 22 .

← Older revision		Revision as of 07:01, 26 July 2016
Line 240:		Line 240:

	</nowiki>		</nowiki>
		+
		+	* :wq save and exit
		+
		+	* The configuration tool will automatically configure and initialize the cluster and start the appropriate services.
		+	* There are 56 separate and unique steps that are grouped to check each area individually to assure that everything is working correctly. These steps will take approximately 20 minutes.

@@ Line 196: / Line 196: @@
 * :wq to save and exit and enter to continue
+  <nowiki>
 ----
 checking ips in file for validity..

← Older revision	Revision as of 06:58, 26 July 2016
(No difference)

@@ Line 135: / Line 135: @@
 </nowiki>
-== Install and config ==
+== Hedvig cluster Install and config ==
-* In deploy.ova VM
+* In deploy.ova VM , login as root with hedvig default password.
   <nowiki>
-* Enter the Cluster setup menu and change the Host name to fully qualified name.
+[root@head ~]# sudo su -
- <nowiki>
+---------------------
----------------------------------
+--- Cluster setup ---
----    Cluster setup          ---
+---------------------
 . Login to cluster
 . Setup a new cluster
-. Update this machine
+. Upadte this machine
 . Restart this machine
 . Set hostname
 . Configure network
-. Exit
+. Exit ---------------------- Enter choice [ 1 - 7 ]   2
---------------------------------- Enter choice [ 1 - 7 ]   5
+</nowiki>
 </nowiki>
-* setup the public network in our case 192.168.1.185 with option 5 (network can be set with syscong scripts as well).
+* Enter the hostname of the storage nodes
   <nowiki>
----------------------------------
----    Cluster setup          ---
+node1.bostonhpc.in
----------------------------------
+node2.bostonhpc.in
-. Login to cluster
+node3.bostonhpc.in
-. Setup a new cluster
-. Update this machine
+</nowiki>
-. Restart this machine
+* save :wq and exit , hedvig will check validity of hostnames ,are they resolvable and check connectivity.
-. Set hostname
-. Configure network
+* In tgt nodes add the proxy node. If proxy are set in HA mode check the HA proxy user guide for info.
-. Exit
---------------------------------- Enter choice [ 1 - 7 ]   5
+ <nowiki>
 </nowiki>

@@ Line 93: / Line 93: @@
 sudo ./rpm_extract.bin
 sudo ./hedvig_extract.bin
 </nowiki>