...
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 |
|---|
| language | bash |
|---|
| title | Merge "v0.3.0" into skyhigh |
|---|
| firstline | 1 | linenumbers | true |
|---|
|
$ 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 |
|---|
language | bash |
|---|
| title | Track the correct repos |
|---|
| firstline | 1 | linenumbers | true |
|---|
|
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 |
|---|
| title | Deploy puppet modules using r10k |
|---|
| language | bash |
|---|
| title | Merge "v0.3.0" into skyhigh |
|---|
| firstline | 1 | linenumbers | true |
|---|
|
root@manager:~# r10k deploy environment skyhigh -vp |
...
