Page History

Changes in puppet-sunet ( depracated)

...

We have created two separate branches in a branch https://github.com/SUNET/puppet-sunet:

...

/

...

tree/sa-

...

prod for the prod servers

...

In staging and Beta servers, we run

https://github.com/SUNET/puppet-sunet/tree/

...

Reference case: https://jira.sunet.se/browse/SA-72 (when we did for the first time)testing

NOTE: Stop cosmos on affected servers and after bump-tag, run cosmos as test in few servers with redudnancy, then reboot and check that the service is working, there's no error in cosmos logs and no alarms in nagios.

in puppet-sunet

git checkout stablesa-2023v1beta
git pull
git checkout sa-betaprod
git diff HEAD..stablesa-2023v1beta (checked the diffs)
git merge sa-beta
git status (check if there are conflicts)
git diff sa-beta:<file> HEAD:<file> (to check file with conflicts) 
fix conflicts locally or run git merge stable-2023v1
bump-tag --abort && git merge sa-beta -X theirs (to replace the conflicted files with those from sa-beta)
./bump-tag

OLD Branch

• sa-beta https://github.com/SUNET/puppet-sunet/tree/sa-beta
• Reference case: https://jira.sunet.se/browse/SA-72 (when we did for the first time)

Multiverse update

Reference case: https://jira.sunet.se/browse/SA-72 (when we did for the first time)
NOTE : Read the exceptions to know what may have happened in the last update.

...

git remote add multiverse git@github.com:SUNET/multiverse.git
git fetch --all
git checkout -b multiverse-<year>-<month>-<day>
git merge multiverse/main
git checkout master
git pull
git diff HEAD.. multiverse-<year>-<month>-<day>
git merge -X theirs  multiverse-<year>-<month>-<day>
git status
(Fix the conflicts, add and commit)
./bump-tag

OLD Method

git remote add multiverse git@github.com:SUNET/multiverse.git (If you don't already have it in your .git/config)
git fetch --all
git checkout multiverse (we already have a multiverse branch in remote, but in next update, we will create a new one)
git merge multiverse/main (meged the local multiverse branch with upstream multivers's main branch)
git push

Now

...

we

...

can

...

check

...

the

...

diffs

...

here

...

https://github.com/TheIdentitySelector/thiss-ops/compare/master...multiverse 

If there ar no conflicts

• create a Pull Request in Github
• double check the commits going in the merge
• confirm the merge
• run bump-tag from CLI

If there are conflicts, do not open a PR, use CLI to fix the conflicts by below manner

git checkout master
git pull
Fix conflicts locally or run git merge -X theirs multiverse (to replace the conflicted files with those from multiverse)
If satisified, create a Pull Request and confirm the merge.
If there are conflicts, do not open a PR, use CLI to fix the conflicts. Double check the commits going in the merge. 
./bump-tag

Exceptions

 01.07.2024

...