Open Source Strategy

Open Source is a key framework to enable the prolonged development and delivery of ARTIST tools.

ARTIST tools are developed following open standards and in many cases reusing existing open source components. Therefore, all project results are delivered under an open source license, with the exception of a few consultancy tools whose source code is not provided, but which are nonetheless free to use (see Note at foot page for details).

All the available toolsets and tools can be found at, where a link to the source code, licensing information, supporting documentation and demonstration videos are included for each entry.

ARTIST open source strategy is a combined approach consisting in creating its own OS community maintained by the ARTIST consortium plus the necessary engagement of existing and related open source communities as third parties in the ARTIST ecosystem. The objective of the ARTIST community is to share maintenance and development costs, pooling both innovation and effort, whilst obtaining revenue from industrial exploitation of services on top of the source code, following a similar approach as established OS communities such as OpenStack or Eclipse.

Several open source communities have been identified so far as potentially interested on ARTIST results: Eclipse (ATL, Modisco), Apache JClouds, OW2, OCEAN Open Cloud Directory and SPEC (Standard Performance Evaluation Corporation) RG Cloud Working Group. Engagement of these communities in our process is being accomplished from two perspectives:

  • on one hand, related and relevant ARTIST results are being contributed to these communities (if accepted) leading to the enhancement of some of their components by ARTIST or providing new components completely developed by our project;
  • on the other hand, involvement of these communities in the ARTIST ecosystem is planned by clearly explaining the benefits of joining us, simply reusing some of our results, or contributing, if they wish, to our solution and becoming an ARTIST third party.

The commitment of ARTIST in fostering open source is led by:

  • the positive experience in actively collaborating with other EU projects including OCEAN and PROSE to promote the adoption of an open source approach;
  • the value brought by the ‘network effect’ as more providers adopt Artist tools in their services – increasing visibility, tool maturity and overall capabilities;
  • the value of crowdsourcing innovation as the components themselves are evolved and expanded in multiple contexts beyond that of the ARTIST consortium’s commercial plans;
  • the reuse to the maximum extent  possible of existing open source components in the development of ARTIST itself.

ARTIST contributions to Open Source projects

ARTIST is already contributing to some existing open source projects through the partners directly involved in such projects. The committed work has been properly labelled under ARTIST brand.

The list of currently accepted contributions is:

Apart from this consolidated contributions, there are further planned contributions:

  • Contribute with the created model discoverers  to Eclipse MoDisco
  • Integrate the implemented model transformations by using ATL with the components this community is actually using
  • Select and upload some tools to Eclipse marketplace
  • Delivery of 3ALib, our component for benchmarking the availability in cloud providers, in SPEC RG WG directory. This group is focused on cloud benchmarking, quantitative evaluation, and experimental analysis. Here is the ARTIST work presented so far in this working group NTUA_DKMS_SPEC_presentation.pdf.

Note about non open source tools: Only three of twenty nine ARTIST tools are not being delivered under an open source license but offered for free use. They are the Maturity Assessment Tool (MAT), the Certification Model and the Business Feasibility Tool (BFT). The three tools are addressed to business consultants, respectively for analyzing the gap between the non-cloud application/business and the desired cloud complaint application/business; for certifying the compliance with the cloud of the migrated application; and for simulating several potential business scenarios according to the desired migration business goals. The value of these tools lies in the logic behind them rather than in the code itself, and they can be integrated with the ARTIST methodology, so they do not prevent the overall exploitation and sustainability of the ARTIST ecosystem.