incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "AriaProposal" by ArthurBerezin
Date Sun, 03 Jul 2016 16:40:40 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "AriaProposal" page has been changed by ArthurBerezin:
https://wiki.apache.org/incubator/AriaProposal?action=diff&rev1=5&rev2=6

  ARIA aims to implement several main use cases, and can be used as a command line tool to
orchestrate TOSCA based application templates serving as a lightweight tool to onboard and
orchestrate applications in a repeatable and robust manner. ARIA can be used by software vendors
and VNF providers as a development environment for creating TOSCA templates for onboarding
and managing the lifecycle of software products and Virtual Network Functions(VNFs). 
  Additionally ARIA can be used for building orchestration platforms and enabling TOSCA based
orchestration using the ARIA TOSCA orchestration engine as the kernel of the orchestrator.
  
- ‘’’ ARIA TOSCA Parser ‘’’
+ ''' ARIA TOSCA Parser '''
  ARIA includes a TOSCA DSL parser, the parser’s role is to interpret the TOSCA template,
create an in-memory graph of the application and validate templates’ correctness. TOSCA
provides a type system of normative node types to describe the possible building blocks for
constructing a service template, as well as relationship types to describe possible kinds
of relations. Both node and relationship types may define lifecycle operations to implement
the behavior an orchestration engine can invoke when instantiating a service template. The
template files are written in declarative YAML language using TOSCA normative types. Technology
specific types can be introduced via ARIA Plugins without any modifications of the parser
code. 
  
  TOSCA Templates include: 
@@ -21, +21 @@

  Workflows
  Resources such as scripts, etc’
  
- ‘’’ ARIA Plugins ’’’
+ ''' ARIA Plugins '''
  ARIA Plugins allow extending the TOSCA normative types dynamically by adding new technology
specific node types and relationship types with their implementation, without changing the
code of the ARIA TOSCA Parser. The plugin based types are isolated, allowing different versions
of the same plugin in a single blueprint - for example support OpenStack Kilo and OpenStack
Juno in the same template. It also allows combining types of different technologies - for
example OpenStack nodes with VMware, Amazon, or other types such as Router, Firewall, Kubernetes
and others. The work of interacting with IaaS APIs and running scripts, Configuration Management
tools, Monitoring tools and any other tools used when managing applications is done by the
ARIA Plugins. 
  Plugins can be included as part of the application template package and loaded dynamically.

  ARIA includes plugins that can be used as is or as reference for implementing for new plugins,

@@ -33, +33 @@

  Script Plugin: Bash, Python others 
  Fabric Plugin via SSH 
  Custom Plugin 
+ 
- ‘’’ ARIA Embedded Workflows ‘’’
+ ''' ARIA Embedded Workflows '''
  Workflows are automated process algorithms that allow to interact dynamically with the graph
described in the application topology template. Workflows describe the flow of the automation
by determining which tasks will be executed and when. A task may be an operation, optionally
implemented by a plugin, but it may also be other actions, including arbitrary code or scripts.
Workflows can be embedded within the TOSCA Template to be able to access the graph dynamically.
They are implemented as Python code using dedicated APIs and a framework to access the graph
context, the context provide access to the object graph described in the TOSCA template.
  ARIA comes with a number of built-in workflows - these are the workflows for install, uninstall,
scale and heal. Additionally it is possible to write custom workflows. Built-in workflows
are not special in any way - they use the same API and framework as any custom workflow is
able to use.  
  
@@ -55, +56 @@

  
  === Current Status ===
  TBD
+ 
  === Meritocracy ===
-  
  ARIA being a reference implementation of a vendor independent and neutral standard specification,
we strongly believes in meritocracy, where individual committers and companies can help drive
the implementation of the standard and take leading roles in steering the project. ARIA’s
started it’s life as the Kernel of Cloudify, an open source and open platform orchestration
product, we intend to bring our experience operating in open source communities to create
an open governance structure for project leadership to encourage individual and company involvement
and contributions. 
  
  === Community ===
  TBD
+ 
  ===  Core Developers ===
  TBD
+ 
  === Alignment ===
  TBD
+ 
  === Known Risks ===
  TBD
  
  === Documentation ===
  TBD
+ 
   === Initial Source ===
  TBD
+ 
  === Source and Intellectual Property Submission Plan ===
   TBD
+ 
  === External Dependencies ===
   TBD
+ 
  === Cryptography ===
  TBD
+ 
-  === Required Resources ===
+ === Required Resources ===
-  TBD
+ TBD
+ 
  === Mailing lists ===
  TBD
+ 
  === Subversion Directory ===
-  TBD
+ TBD
+ 
  === Git Repository ===
  https://github.com/aria-tosca 
+ 
  ===  Issue Tracking ===
  TBD
+ 
  === Initial Committers ===
  TBD
+ 
  === Affiliations ===
  TBD
+ 
  === Sponsors ===
  TBD
+ 
  === Champion ===
  TBD
+ 
  === Nominated Mentors ===
  TBD
+ 
  === Sponsoring Entity ===
  TBD
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message