|2.15.0||2017-09-30||Added virtual region support, and multi-environment isolation support.|
|2.14.1||2017-08-29||Fixed and optimized a few application deployment and publishing issues.|
|2.14.0||2017-08-23||Added application deployment and publishing function with batch mode support.|
- Virtual region allows you to create virtual regions in existing Alibaba Cloud regions, so a single tenant can have multiple isolated environments (for example, development, testing, and production) in a single region.
- Component Center page allows you to view all the sub-services of the EDAS platform. Here, application diagnostic components have been linked to other modules in the system menu.
- New Overview page of the Console displays four metrics: application count, machine count, service count, and the number of applications published in the past seven days. In addition, it shows three recent alarms from all the applications under the current account, and the service call trendline.
- EDAS container version 3.3.2, the latest version, provides all the functions that previous versions support, such as traffic greyscale, JAR package deployment, and HSF RESTful service calls.
- Docker applications can be developed in Spring Cloud/Boot framework and packed and run as FatJar.
- The application publish change details page is optimized with health check and optimized HSF service disabling.
Monitoring & service governance
- Slow SQL statement parsing is added to service tracing. When slow database access is detected, you can view the executed SQL statements.
- Optimized rate limiting and service degradation provide improved performance and allow you to customize the redirect page for rate throttling.
- Application status change prompts shows a global message “This application is performing a XXX change. Click for more information.” at the top of each page in a changing application.
- The change details page automatically populates the current change type and the deployment package name and version.
- The change details page shows the application group. If the action does not apply to the entire group, then the specific machines are added to the “Change Target” field.
- Change records are color coded to indicate the status of the changes. Successful changes are green, failed red, terminated yellow, and running black.
- Fixed a bug that the WAR package download failure caused by a full machine disk goes undetected during application deployment.
- Fixed a bug that the “Description” field in the publishing list is truncated.
- Fixed a bug that the “conversion successful” message is displayed despite the 503 error during the conversion of a Docker cluster node.
- Fixed a bug that the JVM xms parameter can be set to be greater than 70% of the memory size for Tomcat in a Docker application.
Application publishing order is a new way to deploy and publish an application. In this way, you can view the success or failure status of each stage in the publishing process. You can also stop a publishing when necessary.
Application batch publishing deploys and publishes applications in batches. You can define the machines for each batch and suspend the publishing between batches, so you can decide whether to continue the publishing or stop it and roll back the process.