ariatosca-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ran-z <>
Subject [GitHub] incubator-ariatosca pull request #152: ARIA-166 Update README file
Date Mon, 12 Jun 2017 14:24:56 GMT
Github user ran-z commented on a diff in the pull request:
    --- Diff: ---
    @@ -4,198 +4,111 @@ ARIA
     [![Build Status](](
     [![Appveyor Build Status](](
    +[![PyPI release](](
    +![Python Versions](
    +[![Open Pull Requests](](
    +[![Closed Pull Requests](](
    -[ARIA]( is a minimal TOSCA orchestrator, as well as a platform
for building
    -TOSCA-based products. Its features can be accessed via a well-documented Python API.
    +[ARIA]( is a an open-source, lightweight, library
and CLI for orchestration that open-source projects can consume to build TOSCA-based orchestration
solutions for resources and services orchestration. It supports NFV and hybrid Cloud scenarios.
    -On its own, ARIA provides built-in tools for blueprint validation and for creating ready-to-run
    -service instances. 
    +ARIA can be utilized by any organization that wants to implement TOSCA-based orchestration
in its solutions, whether a multi-cloud enterprise application, or an NFV or SDN solution
for multiple virtual infrastructure managers.
    -ARIA adheres strictly and meticulously to the
    -[TOSCA Simple Profile v1.0 cos01 specification](,
    -providing state-of-the-art validation at seven different levels:
    +With ARIA, you can utilize TOSCA's cloud portability out-of-the-box, to test and run
your applications, from template to deployment. 
    -<ol start="0">
    -<li>Platform errors. E.g. network, hardware, or even an internal bug in ARIA (let
us know,
    -	please!).</li>
    -<li>Syntax and format errors. E.g. non-compliant YAML, XML, JSON.</li>
    -<li>Field validation. E.g. assigning a string where an integer is expected, using
a list instead of
    -	a dict.</li>
    -<li>Relationships between fields within a type. This is "grammar" as it applies
to rules for
    -    setting the values of fields in relation to each other.</li>
    -<li>Relationships between types. E.g. referring to an unknown type, causing a type
    -    loop.</li>
    -<li>Topology. These errors happen if requirements and capabilities cannot be matched
in order to
    -	assemble a valid topology.</li>
    -<li>External dependencies. These errors happen if requirement/capability matching
fails due to
    -    external resources missing, e.g. the lack of a valid virtual machine, API credentials,
    -    </li> 
    -Validation errors include a plain English message and when relevant the exact location
(file, row,
    -column) of the data the caused the error.
    -The ARIA API documentation always links to the relevant section of the specification,
and likewise
    -we provide an annotated version of the specification that links back to the API documentation.
    +ARIA is [available on PyPI](    
    +ARIA requires Python 2.6/2.7. Python 3+ is not currently supported.
    -Quick Start
    +ARIA itself is in a `wheel` format compatible with all platforms. 
    +Some dependencies, however, might require compilation (based on a given platform), and
therefore possibly some system dependencies are required as well.
    --- End diff --

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