CTO Devrin Cakali has today confirmed this weekends Upgrade programme. He said:
"You will remember that we postponed our planned MR upgrade in October 2015 to allow many our partners avoid significant payment gateway issues at that time. We can now confirm two successive upgrades to return us to our normal position of using the most recent LTS (long term support) release of Porta.
The first step is to move to MR45-6 over the weekend of the 7th of May 2016 and this would be followed by a second move to MR50-4 three weeks later. The following reiterates our planned upgrade process for - weekend commencing - May 7th (first issued back in October):
All new features of MR45-6 - and all releases since the current build can be found at the links below:
- Maintenance Release 41
- Maintenance Release 42
- Maintenance Release 43
- Maintenance Release 44
- Maintenance Release 45
The upgrade will be completed in two parts, in order to reduce risk and limit downtime to off peak periods only. The first part of the upgrade procedure follows below, with details of the second part following that:
The first part involves the following steps:
(6th May 2100 GMT+1 - 7th May 0400 GMT+1)
update the Configuration Server and reboot to the new release
update the rest of the Servers and test reboot to the new partition and the reverse
This stage requires the minimum of downtime and will allow us to check that the update to the new release is successfully performed and to determine if there are any network issues. Each reboot instance can cause up to 10 minutes of downtime - though this will only occur between 0100 and 0400 on 10th October.
The second part includes following steps:
(8th May 0100 GMT+1 - 8th May 0600 GMT+1)
update the DB (during this period all services will be stopped)
permanently reboot to the new partition
apply the new configuration
The main downtime occurs during the DB update. The servers will be rebooted several times. During the DB update and server reboots, web and SIP services will be down. The downtime for this second part of the upgrade can take up to 4 hours. SIP servers will be prioritised to minimise down time on calling traffic.
Since the configuration server will be updated to new release during the 1st stage, the logging features (SIP log viewer and BE log viewer) will be affected. So, the new logs can be viewed only after the 2nd stage is complete.
The downtimes will be scheduled between 1am GMT+1 and 6am GMT+1.
If you have any concerns or questions about this upgrade, please do not hesitate to contact us via support.
We hope you enjoy all the new features and functionality"