Recently AWS announced C5 and M5 support in eu-central-1 region  as well as other regions before. New C5 instances are offered with "25% price/performance improvement over the C4 instances" based on Intels "Skylake" processor and a more powerful Elastic Network Adapter (ENA) for higher instance bandwidth.
Root360 will support new C5 and M5 instance family for dedicated customer workloads in eu-central-1 and many other regions. We support C5 and M5 instances with Elastic Network Adapter (ENA) by using an optimized root360 image to boot from.
If you want us to upgrade your environment, please get in touch with us at email@example.com
The newly discovered ability to exploit publicly available memcaches for DDoS attacks is now even easier with ready-made tools. Nevertheless, it is not possible to misuse memcaches used in Root360 infrastructures because they are securely located in the application network and are not publicly accessible. Further information can be found in our Quickstart.
Between 23:41 CET and 23:56 CET some EC2 instances experienced elevated DNS resolution errors in the EU-CENTRAL-1 and EU-WEST-1 Region. As a result of this, some AWS services experienced elevated errors and increased latency. The issue has been resolved and the service is operating normally.
The latest Updates for r3 had been released to all customer environments. Besides providing prettier response to ease understanding we focused on supportive functions for the deployment process. From now on you can not only see, which roles you are able to deploy, you can also find out what are the actual sources configured per default for them (1).
Furthermore we updated and extended our Knowledge Base articles on the topic. Feel free to visit our Knowledge Base (2) or the handbook on r3 (3).
r3 [instance] deploy --list-sources [-r, --role ROLENAME]
r3 [instance] deploy --list-roles
r3 instance list
From today we support PHP version 7.2 with full compatibility to New Relic PHP and Tideways extension.
add PHP 7.2.support
We reduced the amount of error messages printed out by our deploy.py command. See https://root360.atlassian.net/wiki/spaces/KB/pages...
Error messages that are the result of other failing deployment steps are now skipped unless full debug mode (-dd) is used. This way real error messages can be found easily in the output.
If you are using webframeworks with different languages than PHP e.g. Django, nodejs-express or CherryPy we now have your covered too.
We implemented the process manager supervisord (see our documentation in our infrastructure. With this tool you can run and manage scripts running in daemon mode without worrying about the init script that starts it at system boot.
If you need this feature just contact us.
add supervisord support
We now support the installation of different PHP version (currently 5.6, 7.0, 7.1) for different roles on the same server within root360 infrastructure.
That means you can run 2 applications on one server while one uses PHP 5.6 and the other PHP 7.0.
add support different PHP version (currently 5.6, 7.0, 7.1) for different roles on the same server