Releases involving Customer Service Team

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.

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.


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.

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.



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:

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


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.

Integration of CDN (CloudFront) & Elastic Search

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

EleasticSearchService:

AWS CloudFront:

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)
Customer Service Team August 30th, 2018

Update: Deprecation of old legacy deploy scripts deploy.py and update-ecs-service.py​

As we rolled out our cloud management CLI suite 'r3' [1] almost a year ago, we are deprecating the old legacy commands for deploying customer code into our infrastructure. 
This affects the following commands:

  • deploy.py
  • update-ecs-service.py

Starting today those commands will deploy the code and always return code 250 and a deprecation message when the deploy was successful.
You should switch to the r3-command to deploy your code [2] by 27th September 2018. After this date the mentioned commands will be removed.

[1] 
root360 Cloud Management CLI Suite r3

[2] 
Default Deployment: How deployment via CLI is working

Docker (ECS) Deployment: root360 Container Platform Deployment 


        Updates

        • Due to a security patch the deploy script deploy.py is deprecated since today. Please check your deployment processes.

        Customer Service Team August 22nd, 2018

        Update: Hipchat service cancellation by end of August 2018

        As already announced Atlassian will not continue their Hipchat cloud service. You may read the full story at https://www.atlassian.com/blog...

        Hipchat has been a great platform to support customers during migration phase to the AWS powered root360 platform. Today, we will announce the end of the hipchat service for all customer as well. We will discontinue the service by end of August 2018. 

        As we like to chat with you, we published a new chat service paired with our customer support portal. After you successful logged in to https://support.root360.cloud, you will see a small orange bubble on the bottom right.

        By clicking this chat icon you will be transferred immediately to a customer support agent. 

        We will answer as soon as possible to support you. 

        Please keep in mind, that we will only support chat during business hours. In the event of a fault, please call +49 (0) 341 39 280 907-7 or send us a ticket via https://support.root360.cloud


        Customer Service Team July 19th, 2018

        Bugfix: Today's AWS Network Connectivity Issues

        In the night between 1:39 AM UTC and 1:49 AM UTC AWS experienced network connectivity issues for some instances in a single Availability Zone in the EU-CENTRAL-1 Region. This may have affected your availability during this period. 

        We have reviewed the components and do not see any malfunction of currently running instances. The issues has been resolved by AWS at 2:34 AM UTC officially.

        If you have further issues which may be related to this outage, please get back to us at https://support.root360.cloud/

        Source: https://status.aws.amazon.com/


        Updates

        • 11:04 fixed time in post

        Customer Service Team June 11th, 2018

        Update: Amazon ElastiCache Mandatory Maintenance in next 2-3 weeks

        AWS reached out to us that they need to apply mandatory updates for ElastiCache service. This update will effect all regions and include mandatory patches to improve security, reliability and operational performance.

        In case of single instances there will be a short service interruption which may effect your project availability. You can read more about ElastiCache maintenance at [1].

        root360 will contact all customers which have ElastiCache service in place to find best suitable maintenance window. 
        For any question, feel free to get back to us at https://support.root360.cloud.

        [1] https://aws.amazon.com/elastic...


        Updates

        • ElastiCache patches to improve security, reliability and operational performance

        Bugfix: root360 central logging system - masking issue

        To comply with the new General Data Protection Regulation (DSGVO) we released an update of our central logging system last week.

        One of the new feature is masking of IPv4 and IPv6 addresses during logrotation.

        That way the current log files provide the IP addresses for log analysis but older compressed logfiles (e.g. from yesterday) are cleaned.


        Under some circumstances the masking of IPv6 addresses also masked timestamps and other strings that are not IPv6 addresses.

        We just released an update that fixes this issue.


        If you have questions concerning the root360 central logging system you can read our documentation.

        For issues with the root360 central logging system please contact our support team via ticket system or via mail at support@root360.de.

        Update: temporary disruption - limited accessibility of the root360 Customer Service

        Due to a regional disturbance of the Internet connection, we have currently limited access. The communication via our ticket system as well as the telephony is affected by the disruption. We are already in contact with all involved service providers to solve the problem as fast as possible.

        We will keep you updated via this channel.


        Updates

        • 12:10 disruption is solved by our service provider

        New Feature: root360 central logging system - improved log rotation and IP masking


        The root360 logging system is an overall collector for technical and custom logs. Logs will be transferred to a unique place and merge into a single log per instance role. This solutions provides the most sophisticated way to transfer and monitor logs of scaling instances even with a limited lifetime.

        See https://root360.atlassian.net/wiki/spaces/KB/pages/66196200/How+logs+are+aggregated+-+Central+logging+system

        As of 31st of May 2018 we will release a major update for root360 central logging system. Following changes will be applied for all managed logs in root360 central logging system:

        • Data retention will be 90 days of anonymized logs
        • Log rotation will take place on daily basis
        • IP masking will be applied after 1 day masking IPv4 and IPv6

        This will affect logs which are registered via "register-log" [1] and "check-log-registration" [2] as well. Besides that, all customers will still be able to debug, aggregate and analyze most recent log files without any masking. Masking for IPv4 and IPv6 will be applied to the logs at first rotation only.

        This action is required to fulfill latest requirements of DS-GVO (GDPR) for our customers. 

        In case you will need a different log solution besides the upcoming changes, please get in touch with us at https://support.root360.cloud

        We will be happy to support you.


        [1] https://root360.atlassian.net/...

        [2] https://root360.atlassian.net/...



        New Features

        • mask IPv4 and IPv6 for all managed logs

        • force a pre-defined data retention

        • save disc space and log processing overhead

        • fulfill DS-GVO (GDPR) requirements

        Timo May 23rd, 2018

        Update: We are currently not available via support@root360.de and our ticket system

        Currently we have no possibility to receive and send messages via support@root360.de and our ticket system. We are already in contact with the provider of our ticket system. We apologize for this circumstance and keep you up to date.


        Updates

        • 14:15 - problems are resolved