Upgrade notes for Lab Management 2.7

Back up the Lab Management data. Before upgrading from Lab Management 2.6 to 2.7, we need to back up the data. It is assumed that /public/backup is a mounted backup volume.

Use the following commands to backup Lab Management related data if /u1/cubit/data folder is not on NetApp volume.

sudo mkdir /public/backup/mgr.$THEDOMAIN.
cd /usr/local/cubit-mgr/bin
sudo ./cubit_backup.py -d /public/backup/mgr.$THEDOMAIN -c /var/ops/site.conf

Use the following commands to backup Lab Management related data if /u1/cubit/data folder is on NetApp volume (on production).

sudo mkdir /public/backup/mgr.$THEDOMAIN.
cd /usr/local/cubit-mgr/bin
sudo ./cubit_backup.py -d /public/backup/mgr.$THEDOMAIN -c /var/ops/site.conf --skip-data

Prepare the physical or virtual host that will house the Lab Management manager.

Note:

Virtual Machine Version should be 8.The OS type should be 64-bit-capable - "Centos 6 (64-bit)".
It should have two NICs, one for standard network traffic,another for the ILO network Disk Provisioning as thin.
Use the latest SCSI Controller, LSI Logic SAS.

Install CENTOS 6.5 64-bit on the host. Once the virtual machine is created, install Centos 6.5 on the machine. For this, you need two images: floppy and DVDs.

The floppy image is located at /public/os/ks-Centos6.5-x86_64.flp.
The DVD image is located at /public/os/CentOS-6.5-x86_64-bin-DVD1.iso and /public/os/CentOS-6.5-x86_64-bin-DVD2.iso.
Connect the floppy image as VM's floppy drive. (Edit Virtual Machine > Floppy > Use Existing floppy image in datastore > Navigate and select ks-Centos6.5-x86_64.flp).
Connect the CentOS-6.5-x86_64-bin-DVD1.iso DVD image as VM's "CD/DVD drive". Edit Virtual Machine > CD ROM > datastore ISO file > Navigate and select CentOS-6.5-x86_64-bin-DVD1.iso. Both should be connected at boot.
Use the above images to boot the newly built machine. The system should boot from DVD.
Press the ESC key from the boot menu to get a prompt.
At the prompt, type linux ks=floppy. This will install CentOS 6.5 OS and necessary packages. During the kick-start once first DVD is completed we need to connect the 2nd DVD CentOS-6.5-x86_64-bin-DVD2.iso to complete the installation. Once installation is complete make sure it boots from local disk. For the root password, check with DEV Team

Set up the network.

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and ensure that it has correct information.
Edit /etc/sysconfig/network-scripts/ifcg-eth1 and ensure that it has correct information.
Edit /etc/sysconfig/network and ensure that it has correct information.
Edit /etc/hosts and add an entry for "mgr.$THEDOMAIN", mapped to the primary IP of the host.
Edit /etc/resolv.conf and ensure that it has correct information.

Reboot the new manager.

Fix /etc/fstab.
Mount the backup volume (see step 1) to /mnt/backup.

cd /mnt/backup/mgr.$THEDOMAIN/system_info
cat nfs_entries >> /etc/fstab

Heart Bleed Fix. The following substeps are to fix the Heart Bleed Bug reported in OpenSSL 1.0.1e-15.

SSH into your LM Manager.
Check the current version of openssl.
- rpm -q openssl
Example
- OpenSSL 1.0.1e-15.
Update your repos:
- yum check-update
Once that is finished, upgrade open SSL.
- yum update openssl
- openssl version -b
Once the upgrade is over, check the version again. It should now read “Apr 7″ or later. You can verify by typing rpm -q openssl and ensure that it’s specifically openssl-1.0.1e-16.el6_5.7 (or later) being installed.
Note: openssl-devel will also get updated during this process.

Reboot the system.

Copy site.conf (From Backup taken) to /var/ops/ and modify /var/ops/site.conf file to add new tokens. For example, the following new tokens are to be set.

-----------------------------------------------------------------------------------------------------------------
[DEFAULT]
#smb_strict_locking = yes
-----------------------------------------------------------------------------------------------------------------
If you are upgrading LM MGR with centos 6.5 . please change the below token 
[infrastructure:mgr]
profile_name = centos6.5_base_x86_64
*Make sure that mac_addr is correct you can verify it by Login to Vsphere console -> mgr ->Edit VM -->Network Adapter--> MAC Address
-----------------------------------------------------------------------------------------------------------------
# MONITORING SETTINGS
if cubit_monitor_action = page_poc 
Add below token and its specifications if not page_poc add this token and comment it out 
cubit_admin_notify_timeout = true
#false - do not send notifications if the status is timeout
#true - always send notifications 
----------------------------------------------------------------------------------------------------------------
[licenses]
Windows-8 = xxxxx-xxxxx-xxxxx--xxxxx-xxxxx
Windows-8.1 = xxxxx-xxxxx-xxxxx--xxxxx-xxxxx
Windows-2012 = xxxxx-xxxxx-xxxxx--xxxxx-xxxxx
Windows-2012R2 = xxxxx-xxxxx-xxxxx--xxxxx-xxxxx
# Replace xxxxx-xxxxx-xxxxx--xxxxx-xxxxx with appropriate license keys.
# Evaluation Key or a MSDN Key, or a KMS  keys can be applied
-----------------------------------------------------------------------------------------------------------------

Updating manager. Get a copy of the latest Lab Management build (on production this should be from release folder) either from FRS or PBL.

Download it using wget and copy it to /public/download. For example:

wget --no-check-certificate https://mgr.cloud.sp.collab.net/pbl/labmgmt/pub/cubit-mgr/releases/2.7/cubit-2.7.0-10683.dev.tgz
cp cubit-2.7.0-10683.dev.tgz /public/download

Install Lab Management using the following commands.

cd /var/ops
tar xzvf /public/download/cubit-2.7.0-10683.dev.tgz
cd /var/ops/cubit-2.7.0-10683
./install.py -f /var/ops/site.conf

Restore Lab Management-data.

mv /u1/cubit/data /u1/cubit.data.XXX
/usr/local/cubit-mgr/installation-support/scripts/stop-services.py
cd /public/backup/mgr.$THEDOMAIN/system_info
cat nfs_entries >> /etc/fstab
cd /public/download
./add_users
cd /var/ops/2.7.0-10683
./cubit_restore.py -d /public/backup/ mgr.$THEDOMAIN

Mount the Lab Management data folder to /u1/cubit/data.

Install VMware-ovftool on the new manager.

Install OVFTOOL 3.0.1.
- sudo sh /public/package/cubit/VMware-ovftool-3.0.1-801290-lin.x86_64.bundle
Use the following command to verify the installation.
- ovftool -v
VMware ovftool 3.0.1 (build-801290)

Install VMware-vSphere-CLI on new manager.

cd /tmp
sudo tar xzvf /public/package/cubit/VMware-vSphere-CLI-4.1.0-254719.x86_64.tar.gz
cd vmware-vsphere-cli-distrib
sudo ./vmware-install.pl # Choose install location as /usr/local/vmware-vicli/bin

Rejoin the manager node into the AD domain.

Delete the manager node from the AD server.
On the AD server, click Start > Administrative Tools > Active Directory Users and Computers .
Open CubitComputers OU.
Right-click the manager entry and select Delete.

On the MGR node, join the manager to the AD domain (assuming the AD domain j.sp.collab.net is being used for the Lab Management domain). Ensure that Date, Time, Time-zone between LM Manager should match with Active Directory server.

$ /usr/bin/sudo kinit Administrator@J.SP.COLLAB.NET  <<<---- domain name in all upper cases
Password:  (this is your own password for sudo)
Password for Administrator@J.SP.COLLAB.NET:  (type domain administrator password here)
$ /usr/bin/sudo net ads join -U Administrator
Administrator's password:  (type domain administrator password here)
Using short domain name -- SERVERS
Joined 'MGR' to realm 'J.SP.COLLAB.NET'
$ /usr/bin/sudo net ads testjoin
Join is OK

Restart the samba service on the manager.

Set up WDS. Th following points are for adding Windows 8, 8.1 and Windows 2012, Windows 2012R2 server images to the WDS server using GUI or WDSUTIL. See Add Windows install and boot images using the GUI and Add Windows install and boot images using WDSUTIL.

Once the boot and install images are added to WDS, follow the steps in the "Configure the WDS server to support more images" section to set the default boot program and images.