Skip to content

Latest commit



249 lines (167 loc) · 9.04 KB


File metadata and controls

249 lines (167 loc) · 9.04 KB

DEEP-1 Genesis

The DEEP - HybridDataCloud project is pleased to announce the general availability of its first public software release, codenamed Genesis

Included components

a4c-deep cip-deep daas im orchent paas-orchestrator ttt udocker indigovr


Key technical highlights:

  • Alien4Cloud-DEEP plugin
    • Support for visual composition of TOSCA templates
    • PaaS orchestrator support
  • cloud-info-provider
    • Support for GPU and Infiniband resources
    • Support for training a machine learning application
    • Support for performing inferences/analisys/predictions
    • Support only for synchronous requests
    • OpenID Connect support
    • Support for standalone service & OpenWhisk action
  • Infrastructure Manager (IM)
    • Improved support for hybrid deployments
    • Support for additional TOSCA types
  • PaaS Orchestrator
    • Hybrid deployments on multiple sites
    • Support to specifying specialized computing hardware Improved support for deployment failures
  • uDocker
    • Improved support for GPUs and Infiniband
  • Visual application topology composition and deployment
    • Graphical composition of complex application topologies
    • Deployment through PaaS orchestrator
  • DEEP as a Service
    • Deployment of DEEP Open Catalog components as server-less functions
  • DEEP Open Catalog
    • Ready-to-use machine learning and deep learning applications, including:
      • Machine learning frameworks + JupyterLab
      • Machine learning ready to use models
      • Deep learning ready to use models
      • BigData analytic tools

Release Notes

The DEEP-1/Genesis release consists in 9 Products and a number of technical guides:

  • 17 OS packages, for CentOS 7 and Ubuntu 16.04
    • 8 RPMS & SRPMS
    • 6 binary & source DEBS
    • 3 tarballs
  • 5 Docker containers

You can find in the later sections the full list of products, with detailed release notes and instructions for their installation/configuration.

Installation Notes

All DEEP - HybridDataCloud products are distributed from standard Operating Systems (OS) repositories and DockerHub registry of the indigodatacloud organization.

The packages repositories have the following structure:

All packages in production and preview repositories are signed with the INDIGO - DataCloud gpg key. The public key can be downloaded from here, and the fingerprint from here.

Please import the key BEFORE starting!

* for CentOS7 save the key under /etc/pki/rpm-gpg/ .. code-block:: bash

# rpm --import

* for Ubuntu: .. code-block:: bash

# wget -q -O - | sudo apt-key add -

Configuring the use of DEEP-HDC repositories

YUM & APT configuration files are available at:

or use the deephdc-release package to install DEEP-HDC repositories:

* CentOS7: .. code-block:: bash

# wget # yum localinstall -y deephdc-release-1.0.0-1.el7.noarch.rpm

* Ubuntu 16.04: .. code-block:: bash

# wget # dpkg -i deephdc-release_1.0.0-1_amd64.deb

These packages will install required dependencies, the INDIGO - DataCloud public key and ensures the precedence of DEEP-HybridDataCloud repositories over EPEL and Ubuntu.

It is strongly recommended the use of the lastest version of the deephdc-release packages containing the public key and the YUM and APT repository files.

Enable the DEEP-HDC Containers repositories

On the DockerHub Registry, DEEP -HybridDataCloud uses the INDIGO - DataCloud and DEEP-HDC Organizations:

Containers present in those repositories and released in DEEP-1 major release are tagged with “DEEP-1” tag and signed, leveraging the Docker’s trust features so that users can pull trusted images.

Currently, content trust is disabled by default. You must enable it by setting the DOCKER_CONTENT_TRUST environment variable, like below:


For more details regarding the "Content Trust in Docker" please read Docker's Documentation

Content trust is associated with the TAG portion of an image. For DEEP-1 (Genesis) release the signed tag is DEEP-1. See example bellow if you want to ensure the correct use of DEEP-HDC images:


$ docker pull indigodatacloud/orchestrator:2.1.1-FINAL
No trust data for 2.1.1-FINAL

$ docker pull indigodatacloud/orchestrator:DEEP-1
Pull (1 of 1): indigodatacloud/orchestrator:DEEP-1@sha256:441c8b037684422ccdf2fdec322c9c09904ed3ce74d9fcc7d2862a9f53ad36be
sha256:441c8b037684422ccdf2fdec322c9c09904ed3ce74d9fcc7d2862a9f53ad36be: Pulling from indigodatacloud/orchestrator
93857f76ae30: Pull complete
e8c92b40b492: Pull complete
Digest: sha256:441c8b037684422ccdf2fdec322c9c09904ed3ce74d9fcc7d2862a9f53ad36be
Status: Downloaded newer image for indigodatacloud/orchestrator@sha256:441c8b037684422ccdf2fdec322c9c09904ed3ce74d9fcc7d2862a9f53ad36be
Tagging indigodatacloud/orchestrator@sha256:441c8b037684422ccdf2fdec322c9c09904ed3ce74d9fcc7d2862a9f53ad36be as indigodatacloud/orchestrator:indigo_2
$ docker images
REPOSITORY                     TAG                 IMAGE ID            CREATED             SIZE
indigodatacloud/orchestrator   DEEP-1            bdbe758d9f32        37 hours ago        843MB


Please find DEEP-1 services and components documentation at Included components.


Most complex software contains bugs, we are not an exception. One of the features of free and open source software is the ability to report bugs, helping to fix or improve the software you use.

DEEP - HybridDataCloud project uses the INDIGO Catch-All GGUS - Support Unit and the for general support requests. More details regarding each product support channels are provided in the respective products release pages.

Developers, researchers and IT enthusiasts: feel free to write to to ask for more information on how to use DEEP solutions for your work. For automatic notifications you can register to the DEEP - HybridDataCloud release RSS feed or subscribe to the DEEP -HybridDataCloud Announce Mailing list. You can also socialize with us via Twitter or by joining our LinkedIn group.