Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are multiple moving parts in ths the SkyHiGh arcitecture, and it might thus be a complex task to upgrade it. The upgrade process is currently not as streamlined as it could be, and although it is possible to do a live upgrade of everything we currently brings down some services when the upgrade is running to be on the safe side.

Update the r10k repo to pull inn all the correct modules

As all our settings are controlled by puppet, and all our puppet modules are downloaded by r10k, the r10k repo is exellent to control the upgrade.

If all of the infrastructure is going to be upgraded to a tested configuration, it is a matter of merging the new configuration to the current branch of the r10k repo. For instance, to upgrade the whole skyhigh platform to the Liberty release a merge of the master-branch at tag "v0.3.0" is performed into the skyhigh branch by the following commands:

Code Block
titleMerge "v0.3.0" into skyhigh
firstline1
$ git checkout skyhigh
$ git merge "v0.3.0"

After the merge it can be smart to edit the Puppetfile to also download the same versions of the role and profile repos:

Code Block
titleTrack the correct repos
firstline1
  mod 'role',
   :git => 'https://github.com/ntnusky/role.git',
-  :tag => 'master'
+  :tag => 'v0.3.0'
 
 mod 'profile',
   :git => 'https://github.com/ntnusky/profile.git',
-  :tag => 'master'
+  :tag => 'v0.3.0'

When one is ready to start the upgrade, the modules of the environment skyhigh can be deployed on the manager like so:

Code Block
titleDeploy puppet modules using r10k
firstline1
root@manager:~# r10k deploy environment skyhigh -vp

At this point puppet will start to pull in the changes.

Upgrade the CEPH cluster

 

...

articles in this part of the wiki is intended to guide you through the upgrade-procedures for parts of the infrastructure:

Page Tree
root@self