Customer Service Team March 1st, 2019

Update: PHP 5.6 and PHP 7.0 end of life - provisioning until mid of 2019

php

As of December 3rd, 2018, PHP 7.0 has reached its end of life. This means it will no longer have security support and could be exposed to unpatched security vulnerabilities.
Additionally, as of December 31st, 2018, PHP 5.6 also reached its end of life. By the way, the first version 5.0 was launched 14 years ago.

5c792f8064e02_image.png

Source: http://php.net/supported-versi...

root360 continues to provision PHP 7.0 and PHP 5.6 until mid of 2019 at no extra costs. This enables all customers to plan and migrate to PHP 7.1 or higher and regain security support. During your upgrade phase and required testing, we recommend to first update your local development or staging installation.

Get back to us at https://support.root360.cloud if we can support you planning your upgrade to PHP 7.1+.


Customer Service Team February 6th, 2019

Update: Docker Deployment Return Code Fix

Today will implement a feature that many of our docker customers have requested.

Until now a failed deployment caused a rollback to a previous version and returned exitcode 0 to your CI/CD pipelines. This caused troubles since your initial deployment did fail and the failure couldn't automatically be recognized by your toolchain. Therefor we changed the behavior so that a rollback is no longer marked as "OK". The rollback will now return exitcode 3.

A docker deployment can now reach the following states:

  • Success: exitcode 0
  • undefined error: exitcode 1
  • Failed Deploy without Rollback: exitcode 2
  • Failed Deploy with Rollback: exitcode 3
  • unknown Cluster: exitcode 4

If you have further questions feel free to contact us at support.root360.cloud.

Steffen February 6th, 2019

Bugfix: Hotfix roll out for root360 central logging

root360 offers for all managed environment a central logging service [1] to support flexible cloud resources. 

The free logging service merges logs from all instances to one place at bastion host for each environment - this happens at real time for all registered log files of all roles and instances. Also the service automatically masks IP addresses in the compressed log files used for long-term logging. With this feature central logging service ensures compliance with GDPR (DSGVO) requirements and stores only masked IP addresses like 162.158.xxx.xxx

Starting today we will roll out a hotfix for the root360 central logging system which prevents mixed logs during masking process for some customers. The new process adds multiple validations which causes a slightly higher resource consumption at affected bastion hosts.
It might be required to reboot the bastion host which causes a very short downtime. 

This might break any persistent SSH connections (e.g. SSH tunnel/OpenVPN) to your bastion host so you will be required to reconnect your service.

We plan to finish the whole roll out until 15th of February.

If you have further questions, please get in touch with us at https://support.root360.cloud

[1] https://faq.root360.cloud/...

Moritz November 15th, 2018

Update: Global Deployment Failures - STATUS: resolved

We are currently experiencing failing deployments due to a broken Ubuntu package. At the moment all deployments will fail. This has no impact on your currently running releases, so no downtime or other issues are to be expected. Nether the less please do not run deployments until further notice.

We will keep you updated.


Updates

  • 18:02 We have successfully recovered package availability for all deployments and started internal measures to prevent further service disruptions caused by package maintainers.

Customer Service Team November 14th, 2018

Update: New default version for MySQL, Aurora MySQL and Redis

We are always working to provide best and most efficient services at AWS for all customers.

In order to provide most recent features, higher security and higher performance for your application, we have updated our default settings to the following:

  • RDS MySQL 5.7.23
  • RDS Aurora for MySQL 5.7.23
  • ElastiCache for Redis 5.0.0

This change will NOT affect already provisioned resources but will be automatically applied when new resources are created. 

When you have further questions, please get back to us at https://support.root360.cloud



Updates

  • 19.11.2018: Additionally we have increased default version for memcached to 1.5 with AWS support (https://aws.amazon.com/about-aws/whats-new/2018/11/memcached15nowavailableonamazonelasticache/)

Timo September 28th, 2018

Update: root360 Cloud Dashboard “Orbiter” gets new features

We released new features for our dashboard "Orbiter". The Orbiter now offers the possibilty to list all existing snapshots of a database instance. Further the public ip address of the bastion host is shown in the Orbiter.

RDS

By clicking the snapshots button all snapshots will be displayed in a separeted pop-up.

5ba3c47e96af2_image.png

The pop-up shows all available snapshots with additional information about them, including the important time of creation. By clicking the relevant snapshot identifier a new view will be displayed.

5ba3c4bf06cc0_image.png


This view provides the ability to copy the restore command for the specific snapshot. This command has to be run on the bastion host to create a new database beside the exisiting to access the restored data.

5ba3c509b4769_image.png

Public ip address

The Orbiter now shows the public ip address of the bastion host. There is a link to our knowledge base, which discribes how to connect via ssh to the environment, too.

5ba3c5a868cdd_image.png


Get in touch with our root360 Dashboard at https://my.root360.cloud/. 
If your not registered yet, please contact us at https://support.root360.cloud

Customer Service Team September 18th, 2018

Bugfix: Wrong return code for successful deployments

At the moment root360 code deploy https://root360.atlassian.net/... is returning code 10 in successful case instead of 0. 
This may break your existing CI/CD processes. 

We are working to fix this issue and keep you updated here.

 


Bugfixes

  • 14:11: released hotfix for return code

Timo September 12th, 2018

Update: Tidesways 5 now available on root360 cloud platform

With the release of Tideways 5, our customers now have the opportunity to use the new features of Tideways 5 to monitor the performance of their applications and to debug them on their server.

Tideways 5 now offers a more detailed view of the metrics:

5b98ea263c798_Tideways 1.png

Analyse traces to find long lasting querys and which component is involved:

5b98ed157389f_TIdeways 2.png


If you already use Tideways and would like to upgrade to version 5, then you can contact our support and upgrade them.

For questions about Tideways, please contact our customer service at https://support.root360.cloud

Find more information about Tideways 5 on https://tideways.com/profiler/...


New Features

  • capturing more data in monitoring mode

  • always capture the total performance of SQL, HTTP, Redis, Memcache, File I/O and other downstream services for monitoring purposes

  • Memory Profiling

  • simpler and better transaction naming

Steffen September 6th, 2018

Update: New features for root360 Cloud Dashboard “Orbiter”

On Monday we released new features for our dashboard “Orbiter”. Now, it offers even more details about your AWS infrastructure in one compressed view.

Integration of ECS (Elastic Container Service)

With the update “Orbiter” gives you more insights in your Docker containers. You can keep an eye on the workload of your containers run on ECS on our own. If you think limits should be adjusted, just let us know.

WcHLBm7SpkZVXDduKKS9lnrwvjUXovg9eSi8Cv2v86lPDxqhzTiH3zVhESDYcH2AVDNqqq6fqG7P_NRfm-NzX4TJLbtxufEDb5g_uJF7pBvPkU5fg6yIV5Fxq9MX4u8TM9rAgK3m

Integration of CDN (CloudFront) & Elastic Search

You can also monitor your CDN and Elastic Search in the “Orbiter”.

EleasticSearchService:

FPv_m9UQZXQkTh0oJxQ5L1KOtA0HCTOtJIC0QILr0-zlZNrlAK13K4u9hsRDwzvbcYRh3jwM2K6Y4eQX-9o256_p0S8kT2zXmJU212urU3v45l60Q7LYoyKVvhwS5B9wt_1TBJ5d

AWS CloudFront:

2X3rGido47X2qmHos6_X6fRluWOP4MsDtMrhkA_Jg_8QcyRxicmilhg6W4CMesJtwtOG1ZEJmO9LCxZC63ontjTxrJ2kloBHml95fWdxvO-QzNKYiTl90-zaDQK4wMfsWTn05Rf9

Our next steps:

Our work at the “Orbiter” is still not finished. In the next release we are planning to add ECS Log Files and an overview about backups and how to restore.

Get in touch with our root360 Dashboard at https://my.root360.cloud/.
If your not registered yet, please contact us at https://support.root360.cloud


New Features

  • Integration of ECS (Elastic Container Service)

  • Integration of CDN (CloudFront) & Elastic Search

  • Storage information for EC2 instances

Customer Service Team September 3rd, 2018

Update: improved default configuration on our servers

We got a lot of feature requests concerning the default configuration of our servers.
Today we'll release changes that implement most of those requests.

The new configuration includes:

  • GNU Screen has a new configuration which:
    • starts nmon on screen #1 at start
    • starts bash on screen #2 at start
    • activates bash completion
    • shows status line at the bottom with hostname, running screens, system load and datetime
  • Bash stores last 9M commands and entered datetime in history
  • the message shown at SSH-login now includes the links to our documentation and support websites
    • if you are patient enough you can see up to 14 different images (here is one)
5b8d0209bcdc1_motd-2018-09-03_10-00.png