openpaas.linagora.com platform update process

Home » Guidelines

Objectives

• allow continuous updates
• warn before action
• get action informations

Process

✈ General rules

• the update happens at 4am Europe/Paris or 12am Europe/Paris
• the update never happens on Friday

✈ Before starting the update

1/ get everything ready

• the updated component(s) artefact(s) (docker images, or packages) should be available
• the Changelog exists in .md format

2/ warn the team

Send a message to lgs-openpaas-dev@linagora.com and comex@linagora.com :

• before 5pm Europe/Paris the previous day if update happens at 4pm
• before 11am Europe/Paris if update happens at 12pm

The email template is available here.

At this step, the Comex, or other OpenPaaS members, can ask you to delay the update.

3/ ensure that your team DevOps is available

The update should not happen without your team DevOps, or another DevOps that has enough knowledge on your software scope.

✈ Update process

The technical update process can be found:

• here for ESN
• here for Sabre
• here for frontends (SPA)
• here for James

✈ After the update

1/ test the system

• look at the logs, ensure everything is normal
• connect to the applications, and ensure that everything is still working

2/ send update feedback

No problem

Well done team ! Reply All to the update email that you sent earlier, adding this at the beginning:

The update is complete.


Regards

There are problems, things that don’t work

Don’t worry, you’ll succeed next time !

• apply the rollback process
• test the system
• Reply All to the update email that you sent earlier, adding this at the beginning:

The update has been cancelled. This is due to [some details about what problems were encountered during the system tests].


Regards

Update email template

Subject: [openpaas.linagora.com] Software update (tomorrow at 4am|today at 12pm)

Hello team,

The software at openpaas.linagora.com will get an update (tomorrow at 4am|today at 12pm). The components being updated are:

- component 1 (example: "James server")
- component 2 (example: "Calendar web frontend")

# if a server system is to be restarted
We expect a short downtime during the update process.
# if no server is to be restarted
We do not expect any downtime during the update process.

Please find the Changelog attached to this email.

Regards,

[Signature]


Attachment: The changelog as a Changelog.md file.