Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Upgrade Recommendations

We are currently running Petasan Version 2.6.2 looking to upgrade to latest Petasan build and want to make sure there aren't any "gotchas" during the process.

Petasan cluster consists of 3 nodes providing iSCSI storage for a Hyper-V cluster (8 nodes)

PS Node Specs (in each):
= 5x 1.6 TB SAS HDD for OSDs (15x total OSDs 128 PGs in RBD pool)
= 64GB RAM
= 4x 10GB fiber NICs (2x bonded with VLANs for MGMT and BACKEND, other two NICs dedicated for iSCSI, jumbo enabled on all)
= Dual 6 core Intel Xeon CPU E5-2630L (12 total cores, HT disabled)
= 1x 250GB SATA SSD for OS drive

Have not had to do an upgrade to the cluster previously, are there any active recommendations on the process or is it just shell in as root and do apt update/upgrades (one node at a time)??

Ideally in a perfect world I would stop all iSCSI traffic to the cluster but best I can probably do is cut the IO down by about 70% on the weekend by downing a bunch of machines that are only being used Mon-Fri, so cluster needs to be upgraded "live"

Looking at the documentation I'm thinking the process should be:

  1. Use the iSCSI path assignment to move the iSCSI targets off of node being upgraded
  2. Go into cluster maintenance settings turn off fencing and set all items to OFF to prevent data from being rebalanced / drives being marked as failed
  3. Log into node using SSH/Console
  4. Perform apt update
  5. Perform apt upgrade
  6. Perform apt install petasan
  7. Verify latest version is installed (dpkg -s petasan | grep Version)
  8. Access web admin console and verify node is only and cluster status is OK
  9. Repeat 1-8 on remaining nodes
  10. Once all 3 nodes are done and status is OK change maintenance settings back to ON and re-enable fencing
  11. Use iSCSI path assignment to re-balance the iSCSI paths across all 3 nodes

Thanks for the input

 

make sue you read our online upgrade guide.

you can also test a test vm cluster running 2.6.2 and do an upgrade to see the ptocess.