|Apache Brooklyn V1 Adds Cloud Support|
|Written by Kay Ewbank|
|Monday, 09 March 2020|
Apache Brooklyn, an open source framework for modelling, monitoring, and managing applications, has reached version 1.0, and added facilities for public and private clouds.
Apache Brooklyn provides a single tool that includes a REST API and a GUI. It can be used for managing provisioning and application deployment; monitoring an application’s health and metrics; understanding the dependencies between components; and applying complex policies to manage the application. A basic blueprint might comprise a single process, such as a web-application server running a WAR file or a SQL database and its associated DDL scripts.
More complex blueprints encompass combinations of processes across multiple machines and services, such as a load-balancing HTTP server or SDN controller fronting a cluster of J2EE application servers, in turn connected to a resilient cluster of SQL database servers.
Brooklyn uses declarative YAML blueprints to describe an application and all its components, and the blueprints can be treated as an integral part of the application. They can also be used as modular components that can be composed and reused in many ways. Brooklyn blueprints include policies that can react to sensor data such as application health, and take actions such as replacing nodes or growing a cluster. Apache Brooklyn includes blueprints for applications and tools including ElasticSearch, clustered MySQL, and DNS management, as well as Apache projects such as Cassandra, CouchDB, Kafka, Solr, Storm, and ZooKeeper.
The headline improvement to the new version is its support for public and private clouds. This has largely been added by including integrated Apache jclouds, Apache's open source multi-cloud toolkit for the Java platform that can be used to create applications that are portable across clouds.
Another improvement to the new release is the inclusion of a drag-and-drop blueprint composer in in the web-based UI. New REST API and CLI tools have also been included that are described as suitable for power users, automation and scripting. The blueprint language and API has also been improved and is now stable. The final improvement is the inclusion of "batteries included” entities and policies covering clusters, auto-scaling, and replacing unhealthy components.
|Last Updated ( Monday, 09 March 2020 )|