Fifth Update of INDIGO-2

The Fifth Update of INDIGO-2 release contains:

Accounting (APEL) v. 1.5.0-1

What's new

Installation & Configuration

Upgrading an already deployed instance

Artefacts

Analytics Portlets v. 1.0.1

What's new

CDMI Server v. 1.2.1

What's new

  • Improved support for storage plugins

List of RfCs

Installation & Configuration

Artefacts

CDMI S3 QoS v. 2.0

What's new

  • support for data namespace browsing.

  • support for CDMI export attribute, it allows to expose to the client information about configured data access protocols, thanks to that end user is able to find the data-object with WebDav for example, but to be well understand: export attribute only informs about alternative protocols, it doesn't provide them, if by any chance the data object is available through WebDAV then export attribute will tell it

  • support for bunch of new QoS attributes including:

    • exposing information about data lifetime

    • exposing information about data retention policy

  • removed dependency on cdmi-s3-qos-ceph-provider module, the information which was earlier provided by

    cdmi-s3-qos-ceph-provider now is partially read from configuration file (in case of static things) and partially is obtained directly from backed server through S3 protocol

Installation & Configuration

Artefacts

Packages

CDMI STORM Plugin v. 0.1.0

What's new

Installation & Configuration

Artefacts

The CDMI StoRM plugin is currently released as a RHEL7 rpm:

CloudInfoProvider: cloud-info-provider-indigo, v 0.11.1 & cloud-info-provider: 0.9.1

What's new

  • This update provides

    • cloud-info-provider with GLUE 2.1 and Keystone V3 support

    • cloud-info-provider-indigo package containing JSON rendering templates and a script to interact with the CMDB using OpenID Connect

List of RfCs

  • #35 - cloud-info-provider: Add GLUE 2.1 support

  • #36 - cloud-info-provider: Add Keystone v3 auth support Splitting repositories/packages

  • #4 - cloud-info-provider-indigo: Integrate CMDB calls with IAM-based authentication

Installation & Configuration

  • No manual intervention should be needed, but in case there are existing cron tasks they will have to take into account the following changes:

  • RHEL</br> yum clean all && yum update cloud-info-provider-indigo

  • Ubuntu</br>

    apt-get update && apt-get install -V python-cloud-info-prov

Artefacts

CLUES v. 1.0.0

What's new

  • Several bugfixes

List of RfCs

Installation & Configuration

Artefacts

The supported platforms

Infrastructure Manager v. 1.6.1

What's new

  • Add Support OTC.

  • Support "DependsOn" TOSCA relationship.

  • Enable to specify a port range in endpoint ports.

  • Fix error loading an infrastructure from DB in case of invalid TOSCA.

  • Fix error getting IP info in OCCI conn.

  • Fix error in Azure conn creating a VM with only a public net attached.

  • Fix error in contextualization nodes with private leys.

  • More bugfixes and improvements...

List of RfCs

Installation & Configuration

  • The supported platforms

    • CentOS 7

    • Ubuntu 14.04

    • Ubuntu 16.04

Documentation

Artefacts

Infrastructure Manager Java API v. 0.4.10

What's new

  • Allow to set up custom ids for authN headers

List of RfCs

Installation & Configuration

  • The supported platforms

    • CentOS 6

    • CentOS 7

    • Ubuntu 14.04

    • Ubuntu 16.04

  • To know how install the im-java-api library please read the documentation available in:

  • To update the library you only need to substitute the im-java-api-X.X.X.jar

Artefacts

Tarballs:

INDIGO IAM v.1.1.0

What's new

This release provides fixes to some outstanding bugs and improvements:

  • New Features

    • The login button text can now be customized for local and SAML login

    • A privacy policy can now be linked to the IAM login page

    • Improved error pages rendering

    • SAML metadata can now be filtered according to certain conditions (e.g., SIRTFI compliance)

    • The organisation name is now included in the IAM dashboard top bar

    • IAM now implements a scope policy management API that allows to restrict the use of OAuth scopes only to selected users or group of users

  • Fixes

    • IAM now correctly enforces SAML metadata signature checks

    • The subject of IAM notification messages now includes the organization name

More details: https://github.com/indigo-iam/iam/releases/tag/v1.1.0

List of RfCs

Installation & Configuration

  • IAM Login Service can be deployed in two different ways:

    • as Docker container

    • as systemd daemon from precompiled packages

Also a Puppet module is provided to simplify the installation and setup. This module leveraging on the precompiled packages. https://github.com/indigo-iam/puppet-indigo-iam

  • the IAM service is provided on the following DockerHub repositories:

    • indigoiam/iam-login-service

    • indigodatacloud/iam-login-service

The IAM service is executed by starting the docker container with the following command:


$ docker run --name iam-login-service \
  --net=iam -p 8080:8080 \
  --env-file=/path/to/iam-login-service/env \
   -v /path/to/keystore.jks:/keystore.jks:ro \
  indigodatacloud/iam-login-service

See the gitbook admin guide https://indigo-dc.gitbooks.io/iam/content/doc/admin.html for all configuration variables description.

Deployment with precompiled packages

Since IAM 1.0.0, precompiled packages are available to install IAM Login services Supported platforms:

  • CentOS 7

  • Ubuntu 16.04

Packages and repo files are hosted on https://repo.cloud.cnaf.infn.it/repository/indigo-iam public repository.

Artefacts

Indigo-Kepler v 1.3

What's new

  • A CLI client built on top of existing library to communicate with FutureGateway. It allows to submit & monitor tasks, upload & download files and query for available applications

List of RfCs

  • A CLI client exposing basic FutureGateway functionality to the command line

  • Updated workflows and scripts to support ENES use case

  • Fixed a bug with incorrect handling of timezone offset when parsing timestamps

Installation & Configuration

How to update: use provided Docker images versioned equally to the main libraries.

Artefacts

LiferayPlugIns v. 2.2.1

What's new

  • The new version includes:

    • the autogeneration of the UI for TOSCA based application

    • the access to runtime data in the UI.

    • Improved token management reducing the communication with IAM endpoints.

    • several bug fixes.

List of RfCs

  • Issue-28 - Support Runtime Data of the tasks

  • Issue-30 - Ajax call should be async

  • Issue-31 - Default paramter file generation

  • Issue-32 - Javascript dependency error

  • Issue-34 - Remove or improve alert messages

  • Issue-36 - Caching keys for token validation

  • Issue-38 - Default values in TOSCA template should be selected in Customisable Application Portlet

  • Issue-40 - Float field in the UI should accept integer

  • Issue-42 - Admin portlet should list task for all users

  • Issue-43 - UserInfo endpoint called with expired token

  • Issue-49 - OneProvider dns only name

Installation \& Configuration

  • Provided details in the documentation. In short administrator should add the new modules from the Liferay control panel and disable/remove the previous.

  • More information can be found in the "Upgrade to a new release" section of the Administration Guide

Artefacts

OIDC-Agent v. 1.1.1

What's new

Synergy Service, v. 1.5.3 and Scheduler Manager, v. 2.6.0

What's new

This update brings many new features and bug fixes like

  • New Synergy service features:

    • added security support

  • New Synergy Scheduler Manager features:

    • Added improvement on queue management algorithm ( Synergy should scale up the oldest user requests from the queue)

    • Added a mechanism that performs user actions before Synergy deletes the VMs

List of RfCs

Installation & Configuration

Artefacts

  • Supported Operating Systems platforms:

    • CentOS 7

    • Ubuntu 16.04

  • Supported CMF (Cloud Management Framework) versions:

    • OpenStack v. Ocata

    • OpenStack v. Newton

    • OpenStack v. Mitaka (only CentOS 7)

    • OpenStack v. Liberty (only CentOS 7)

Packages:

SLAM v. 1.3.1

What's new

  • introducing SLA for storage resources

  • integration with ONEDATA to obtain user space

  • enable CMDB-based recognition of service provider

  • improved performance and UX

  • fixing reported bugs

List of RfCs

Installation & Configuration

Artefacts

Container:

CLUES v. 1.0.0

What's new

  • Several bugfixes

List of RfCs

Installation & Configuration

Artefacts

The supported platforms

OIDC-Agent v. 1.1.1

What's new

Orchent v. 1.2.0

What's new

  • Highlights of this update are:

    • interface to the newly release oidc-agent

List of RfCs

Installation & Configuration

  • Documentation is avalable at - Orchent GitBook chapter "Setting the Access Token"

Artefacts

Orchestrator v. 1.5.1-FINAL

What's new

  • The current update adds support for Azure, increased support for Openstack and better configuration experience

List of RfCs

  • Enable the users to retrieve the underlining IaaS IDs (#237)

  • Evaluation of the TOSCA Concat function (#239)

  • Retrieval of TOSCA attributes for Marathon Deployments (#243)

  • Deploy on Azure (#244)

  • Support for Openstack regions different from the default ones (#245)

  • Add support for local volumes for Mesos tasks (#246)

Installation & Configuration

Artefacts

TOSCA-parser v. 0.8.3

What's new

  • The updated version of TOSCA-parser addresses some minor bugfixes

List of RfCs

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7:

    yum clean all && yum update tosca-parser

  • For Ubuntu 14:04/16.04:

    apt-get update && apt-get install python-tosca-parser

Artefacts

TOSCA types v. 2.1.0

What's new

  • The updated version of TOSCA types contains various improvements and adds some use cases

List of RfCs

  • Add configuration parameters for Chronos and Marathon nodes

  • Update template for Long-Running Services

  • Improve Galaxy configuration.

  • Fixing properties types for Spark

  • Major improvements for Dariah use-case

  • Update tosca types for cms use-case

  • Added type for spark on mesos.

  • Update Mesos types

  • Updated Marathon app definition

Installation & Configuration

Artefacts

udocker v. 1.1.0

What's new

  • udocker 1.1.0 includes additional container execution engines based on fakechroot and runC

    which provide alternative methods to execute the containers based on different approaches.

    These new engines can also deliver additional performance for applications that make intensive

    use of system calls.

List of RfCs

  • Bug fixes and new features:

    • Support image names prefixed by registry similarly to docker

    • Add execution engine selection logic

    • Add fr execution engine based on shared library interception

    • Add rc execution engine based on rootless namespaces

    • Improve proot tmp files cleanup on non ext filesystems

    • Improve search returning on Docker repositories

    • Improve runC execution portability

    • Add environment variable UDOCKER_KEYSTORE

    • Prevent creation of .udocker when UDOCKER_KEYSTORE is used

Installation & Configuration

Artefacts

WaTTS v. 1.2.1

What's new

  • This update is just a bug fix release:

    • if caching is uses (which is done by default) access tokens are invalidated way to fast, this is now fixed

      a workaroung is to disable caching by setting: oidc.cache_duration = none (version 1.1.0 to 1.2.0)

List of RfCs

Installation & Configuration

Artefacts

WaTTSon v. 1.2.0

What's new

  • This update provides integration with oidc-agent, so it can be used instead of storing an access token in an environmental varible

Installation & Configuration

Artefacts

Monitoring - Zabbix-probes v. 1.1

What's new

  • Authentication for Onedata through IAM service and automatic process for refreshing token.

List of RfCs

  • Some connection errors broke up the process and were catched and fixed.

  • A null lenght of oneprovider metrics broke up the process and were validated and fixed.

  • Authentication for Onedata can be done with a valid IAM token. This token and a refresh token is requested by a script (Client application credentials are required) and passed to the monitoring agent as input parameters.

Installation and Configuration

Artefacts

Last updated