|
| 1 | + |
| 2 | +<script type="text/javascript"> |
| 3 | +(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ |
| 4 | + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), |
| 5 | + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) |
| 6 | +})(window,document,'script','//www.google-analytics.com/analytics.js','ga'); |
| 7 | + |
| 8 | +ga('create', 'UA-73216650-1', 'auto'); |
| 9 | +ga('set', { |
| 10 | + page: '/documentation/3.5.0/about.html', |
| 11 | + title: '3.5.0 About' |
| 12 | +}); |
| 13 | +ga('send', 'pageview'); |
| 14 | + |
| 15 | +</script> |
| 16 | + |
| 17 | +<div class="container-fluid"> |
| 18 | + <div class="row"> |
| 19 | + |
| 20 | + <div class="col-sm-4 col-md-3"> |
| 21 | + <div id="sidebar_menu" class="tree" role="complementary"></div> |
| 22 | + </div> |
| 23 | + <div id="content" class="col-sm-8 col-md-9"> |
| 24 | + |
| 25 | + <div style="height: 50px;"> |
| 26 | + <h1 class="pull-left" style="margin-top: 0px;">3.5.0 About</h1> |
| 27 | + <a class="btn btn-primary pull-right" href="http://prose.io/#alien4cloud/alien4cloud.github.io/edit/sources/documentation/3.5.0/about.markdown"><i class="fa fa-pencil-square-o"></i> Edit (pull request)</a> |
| 28 | + </div> |
| 29 | + <p>Alien4Cloud means Application LIfecycle ENablement for Cloud. It is a project started by FastConnect in order to help enterprises adopting the cloud for their new or even existing applications in an Open way meaning with Open-Source model and standardization support in mind.</p> |
| 30 | + |
| 31 | +<hr style="margin-top:5px; margin-bottom:5px;" /> |
| 32 | +<div class="row"><ul class="nav nav-pills" id="summarypanel"></ul></div> |
| 33 | +<hr style="margin-top:5px; margin-bottom:5px;" /> |
| 34 | + |
| 35 | +<h1 id="why">Why</h1> |
| 36 | +<p>Cloud Computing is becoming prime development and deployment model for a number of applications.</p> |
| 37 | + |
| 38 | +<p>New applications being developed want to benefit from the agility and sometimes cost reduction implied by usage of Cloud technologies. |
| 39 | +Existing applications want to benefit as well from this model to be able to allow development and operations teams, managing the applications, to accelerate new features or maintenance pace.</p> |
| 40 | + |
| 41 | +<p>This requires to implement agility principles and leverage proper tools, not only in development, but as well on the deployment phase along all the application lifecycle. |
| 42 | +As well agility is reached when proper collaboration between Dev and Ops teams, and their business sponsor, is achieved.</p> |
| 43 | + |
| 44 | +<p>Even if a large number of solutions exist in the Cloud ecosystem, the ecosystem is not consolidated. |
| 45 | +Architectures, APIs, technologies and infrastructures are still evolving a lot. |
| 46 | +It leaves a lot of choice to the one willing to develop and deploy applications in the Cloud, but very often, the will to reach agility creates a lock-in to the choosen provider at some level : SaaS, PaaS or IaaS.</p> |
| 47 | + |
| 48 | +<p>Knowing the investment term in the Applications from development to deployment (usually several years), and the legacy, it is important to protect the investment in the Application lifecycle, from moving parts, at any level possible.</p> |
| 49 | + |
| 50 | +<h1 id="what">What</h1> |
| 51 | +<p> |
| 52 | +<div class="note info"> |
| 53 | +<h5>Alien4Cloud aims at addressing some of these problems by providing the following capabilities :</h5> |
| 54 | +<ul> |
| 55 | + <li>Ease the design and portability of Applications by leveraging TOSCA (an emerging standard driven by OASIS foundation)</li> |
| 56 | + <li>Isolate the application evolution from deployment technologies and infrastructures, allowing to integrate with any deployment layer and infrastructure</li> |
| 57 | + <li>Accelerate Application Infrastructure Design and improve reusability by providing a Components and Blueprints catalog</li> |
| 58 | + <li>Ease collaboration between Development and Deployment teams across the Application lifecycle in creating the Components and Blueprints to fill the catalog</li> |
| 59 | + <li>Integrate with existing Enterprise systems (Dev and Ops) through REST API and pluggable strategies</li> |
| 60 | +</ul> |
| 61 | +</div> |
| 62 | +</p> |
| 63 | + |
| 64 | +<p>Check <a href="../../roadmap">current roadmap</a> for details on where we are and where we go.</p> |
| 65 | + |
| 66 | +<h1 id="standard-support">Standard support</h1> |
| 67 | +<p>Alien4Cloud supports <a href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca" target="_blank">OASIS TOSCA</a> an emerging standard addressing applications portability in the cloud.</p> |
| 68 | + |
| 69 | +<p>We believe that applications cloud enablement should be done in an open way, free of any lock-in. |
| 70 | +No lock-in meaning that the application should freely move from one environment to the other with smallest effort possible. Therefore, it needs to abstract itself from the underlying infrastructure technical adherence, and define its infrastructure requirements and architecture, independently from each Cloud Provider’s Infrastructure Catalog. |
| 71 | +If not done, even if, technical compability between vendors could exist in theory (yet to be confirmed by reality), Infrastructure Catalog alignment between providers is very unlikely to happen as each provider is focusing in delivering best value to its customers and does not spend time aligning with others, especially when they may be competitors. |
| 72 | +As an analogy, can you easily compare your Telecom providers offerings ? |
| 73 | +We bet that the same will happen with Cloud providers, and it has already started.</p> |
| 74 | + |
| 75 | +<p>TOSCA enables the expression of Application Requirements on the Infrastructure and its QOS/SLA, in an open way, opening the door to optimized placement of Applications in the Cloud Infrastructures based on customer choice at its heart.</p> |
| 76 | + |
| 77 | +<p>We know about Infrastructure As Code, with TOSCA, we enter in to the era of “Application Requirements as Code” easing Application lifecycle management across several Cloud infrastructures.</p> |
| 78 | + |
| 79 | +<p>By increasing service and application portability in a vendor-neutral ecosystem, TOSCA will enable :</p> |
| 80 | + |
| 81 | +<ul> |
| 82 | + <li> |
| 83 | + <p>Portable deployment to any compliant cloud</p> |
| 84 | + </li> |
| 85 | + <li> |
| 86 | + <p>Smoother migration of existing applications to the cloud</p> |
| 87 | + </li> |
| 88 | + <li> |
| 89 | + <p>Flexible bursting (consumer choice)</p> |
| 90 | + </li> |
| 91 | + <li> |
| 92 | + <p>Dynamic, multi-cloud provider applications</p> |
| 93 | + </li> |
| 94 | +</ul> |
| 95 | + |
| 96 | +<h1 id="open-source">Open-Source</h1> |
| 97 | +<p>We decided to build Alien4Cloud and give it to the community in order to allow Application Requirements modelling in a TOSCA format, in a collaborative way, between all participants involved in Application Infrastructure Requirements definition.</p> |
| 98 | + |
| 99 | +<p>It is provided with an <a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">Apache 2 license</a> in order to favour contributions from external teams or individuals. |
| 100 | +Please check our <a href="#/developer_guide/index.html">Contribute</a> page to see how you can help.</p> |
| 101 | + |
| 102 | +<h1 id="what-it-is-not">What it is not</h1> |
| 103 | +<p>Alien4Cloud focuses on Design, Collaboration, Application Lifecycle Management and later Governance, but leverages other existing open source projects that help orchestrating cloud applications and which focus on runtime aspects.</p> |
| 104 | + |
| 105 | +<div class="note warning"> |
| 106 | +<h5>Alien4Cloud does not aim to provide applications deployment runtime.</h5> |
| 107 | +</div> |
| 108 | + |
| 109 | +<p>We believe that there are already a number of viable options there (some of them not being TOSCA compliant, btw) and we want to integrate more than replace. |
| 110 | +We do it in an open way through <a href="../developer_guide/plugin.html" target="_blank">plug-in approach</a> to allow you to leverage your best tools or skills.</p> |
| 111 | + |
| 112 | +<h1 id="status">Status</h1> |
| 113 | + |
| 114 | +<div class="note info"> |
| 115 | +<h5>Which version to choose ?</h5> |
| 116 | +<p>Basically the question depends on your timeframe, on the features you are looking from and on the support level you need.</p> |
| 117 | + |
| 118 | +<ul> |
| 119 | + <li> |
| 120 | + <p><strong>2.2.0</strong> is now deprecated</p> |
| 121 | + </li> |
| 122 | + <li> |
| 123 | + <p><strong>3.0.0</strong> is now released</p> |
| 124 | + </li> |
| 125 | +</ul> |
| 126 | +</div> |
| 127 | + |
| 128 | +<div class="note warning"> |
| 129 | +<h5>Supported platforms</h5> |
| 130 | +<p>To get more informations about the supported platforms, please refer to <a href="#/documentation/3.0.0/admin_guide/supported_platforms.html">this section</a>.</p> |
| 131 | +</div> |
| 132 | + |
| 133 | +<h1 id="features">Features</h1> |
| 134 | + |
| 135 | +<p><a href="../../images/3.4.0/alien-features-1-1.png"><img src="../../images/3.4.0/alien-features-1-1.png" alt="Alien features" /></a></p> |
| 136 | + |
| 137 | + <a class="btn btn-primary pull-right" href="http://prose.io/#alien4cloud/alien4cloud.github.io/edit/sources/documentation/3.5.0/about.markdown"><i class="fa fa-pencil-square-o"></i> Edit (pull request)</a> |
| 138 | + </div> |
| 139 | + </div> |
| 140 | + </div> |
| 141 | +</div><!-- /container --> |
| 142 | + |
| 143 | +<script> |
| 144 | +var hash = location.hash.replace( /^#/, '' ); |
| 145 | +if(hash && hash!== null && hash.match(/html$/)) { |
| 146 | +} else { |
| 147 | + var newLocation = location.protocol+"//"+location.host+"#"+location.pathname; |
| 148 | + location.replace(newLocation); |
| 149 | +} |
| 150 | +</script> |
| 151 | +<script type="text/javascript" src="/js/post-layout.js"></script> |
| 152 | +<script> |
| 153 | +$(document).ready(function () { |
| 154 | + makeSideBar('DOCUMENTATION-3.5.0', 'documentation/3.5.0/about.markdown'); |
| 155 | +}); |
| 156 | +</script> |
| 157 | + |
| 158 | +<script> |
| 159 | +$("div[data-gist]").gist(); |
| 160 | +</script> |
0 commit comments