brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdowner <>
Subject [GitHub] incubator-brooklyn pull request: Add a "quick overview of concepts...
Date Mon, 19 Oct 2015 16:37:41 GMT
Github user rdowner commented on a diff in the pull request:
    --- Diff: docs/guide/start/ ---
    @@ -0,0 +1,35 @@
    +title: Brooklyn Concepts Quickstart
    +layout: website-normal
    +The following section gives a quick summary of the main Brooklyn concepts you will encounter
in Getting Started.  For later investigation of these concepts see [The Theory Behind Brookln]({{}}/learnmore/theory.html),
and the detailed description in [Brooklyn Concepts]({{}}/concepts/).
    +Having examined the concepts below, get started by **[installing and launching](running.html)**
    +***Deployment and Management*** Brooklyn is built for agile deployment of applications
across cloud and other targets, and real-time autonomic management. "Autonomics" is the concept
of components looking after themselves where possible (self-healing, self-optimizing, etc).
    +***Blueprints***  A blueprint defines an application by specifying its components, such
as processes, or combinations of processes across multiple machines and services. The blueprint
also specifies the inter-relationships between the configurations of the components.
    +***Entities*** The central concept in a Brooklyn deployment is that of an entity. An
entity represents a resource under management (individual machines or software processes)
or logical collections of these. Entities are arranged hierarchically. They can have events,
operations, and processing logic associated with them, and it is through this mechanism that
the active management is delivered.
    +***Applications*** are the top level entities that are the parents of all other entities.
    +***Configuration*** Entities can have arbitrary configuration values, which get inherited
by their child entities. You can set global (Brooklyn-wide) properties in (``~/.brooklyn/``).
 Common configuration keys have convenient aliases called "flags".
    --- End diff --
    It must be possible then - it didn't use to be possible, and I *think* it was changed
to be possible, but I wasn't sure! I withdraw my comment.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message