Second Update of INDIGO-1

The Second Update of INDIGO-1 release contains:

CDMI v. 1.1

What's new

  • Redis-Db replaces the filesystem-backed storage of metadata

List of RfCs

  • Redis-DB as new metadata storage

  • Focus on QoS-management via CDMI

  • refactoring

Installation & Configuration

Artefacts

INDIGO IAM v.0.4.0

What's new

  • This release provides new functionality and some bug fixes

List of RfCs

  • Groups are now encoded in the JSON returned by the IAM /userinfo endpoint as an array of group names.

  • Group information is also exposed by the token introspection endpoint

  • External authentication information (i.e. when a user authenticates with Google or SAML instead of username/password) is now provided in the JSON returned by the /userinfo endpoint

  • The first incarnation of the administrative dashboard is now included in the service

  • The first incarnation of the registration service is now included. The registration service implements a "self-register with admin approval" registration flow

  • User passwords are now encoded in the database using the Bcrypt encoder

  • A password forgotten service is now provided

  • More information about bug fixes and other developments can be found on our JIRA release board

Installation & Configuration

  • If the installation was done following the the instructions available in the INDIGO-IAM Deployment and Administration Guide, please follow the following steps to upgrade:

    docker pull indigodatacloud/iam-login-service

    docker stop iam-login-service

    docker rm iam-login-service

    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:indigo_1

Artefacts

Infrastructure Manager v1.4.7

What's new

  • The updated version of the IM adddresses a number of issues like return 403 error when the user cannot access the infrastructure and add features like single site support

List of RfCs

  • Add single site support

  • Return 403 error in REST API when the user cannot access the infrastructure

  • Assure to kill ansible processes is case of ctxt timeout

  • Bugfix in some configuration cases

  • Bugfix not installing ansible roles defined in not master vm

  • Add im.service file add support to systemd

  • Enable to add a Storage to a running VM in the OCCI and OpenNebula connectors

  • Bugfix in OCCI not waiting the volumes on creation

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7:

    yum clean all && yum update IM

  • For Ubuntu 14:04:

    apt-get update && apt-get install python-im

  • For containers

    • Stop the old container:

      sudo docker stop im

    • Remove the old container:

      sudo docker rm im

    • Pull the new image version:

      sudo docker pull indigodatacloud/im

    • Start the new version:

      sudo docker run -d -p 8899:8899 -p 8800:8800 -e IM_DATA_DB=mysql://username:password@server/db_name --name im indigodatacloud/im

Artefacts

FutureGateway

fgAPIServer & APIServerDaemon v0.0.5, PortalSetup v. 0.0.4

What's new

  • This update contains only bug fixes

List of RfCs

  • Portal token validator: LiferayIAM does not uses error: field to invalidate tokens; this time valid tokens are the ones providing the subject

  • An internal 'state' has been exposes as an official state foreseen by API specifications

  • During installation on machines having jdk8 the checkstyle caused a failure due to an unsupported jar file

  • PortalSetup contains static references to the newest versions of fgAPIServer and APIServerDaemon for the installation script fgSetup.sh

Installation & Configuration

  1. Extract from Git, paying attention to do not overwrite the apps/ directory and existing .conf files

  2. Restart the service

    1. a) If fgAPIServer runs as an application (command line execution); just restart the service. In case the service has been started by the /etc/init.d/futuregateway script execute a restart

    2. b) The fgAPIServer runs as wsgi. Restart the service that provides the configured wsgi execution (In case of apache restart it).

  3. APIServerDaemon; this is a Java web application and its code must be extracted from Git and compiled executing 'ant all', once obtained the war file copy the file under $CATALINA_HOME/webapps, then control the file $CATALINA_HOME/logs/catalina.out file checking for its successful installation. The service is now ready and polling activity can be monitored by the log file $CATALINA_HOME/webapps/APIServerDaemon/WEB-INF/logs/APIServerDaemon.log

Artefacts

HEAT-Translator v. indigo-1.1

What's new

  • Fix network support : a map was wrongly used instead of a list which would create invalid hot templates.

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7 + Mitaka:

    yum clean all && yum update heat-translator

  • For Ubuntu 14:04:

    apt-get update && apt-get install python-heat-translator

Artefacts

LiferayIAM v. 1.1.1

What's new

  • This release improve updates groups management following the new IAM groups specification: From IAM >= v0.4.0.rc0 groups are provided as a simple list of name and not as maps with name and other properties. The new version can manage the group list. Additionally, documentation has been improved with instructions to upgrade from the previous version.

List of RfCs

Installation \& Configuration

  • In order to use the latest version, 1.1.1, it is requested:

    • to remove the old version from the Liferay portal configuration panel and remove the old jar

    • restart Liferay and deploy the new one

    • No post-installation configuration is requested.

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

Artefacts

Nova-Docker v. 12.0.0

What's new

Installation & Configuration

  • In order to perform an update please follow the following instructions:

  • For CentOS 7:

    yum -y remove python-nova-docker && yum clean all && yum -y update python-nova-docker

  • For Ubuntu 14:04:

    apt-get remove --purge python-nova-docker

    apt-get update && apt-get -y install python-nova-docker nova-compute-docker

Artefacts

ONEdock v. 1.0-2

What's new

  • The updated version of OneDock addresses a problem due to the change in the -f parameter in the Docker CLI with the updated versions of Docker

List of RfCs

  • Add ansible installation for onedock

  • Update config file installation

  • Create package generating scripts for debian-based systems

  • Create package generating scripts for rpm

  • Remove the -f flag for docker tag

  • Update scripts to comply with bashate style rules

  • Add wiki documentation to gitbook

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7:

    yum clean all && yum update onedock-master and

    yum clean all && yum update onedock-node

  • For Ubuntu 14:04:

    apt-get update && apt-get install onedock-masterand

    apt-get update && apt-get install onedock-node

Artefacts

OOI v. 0.3.2

What's new

  • The updated version provides only bug fixes, no new feature

List of RfCs

  • ooi fails with 500 when deleting a volume

  • ooi fails with error 500 when deleting a volume that is attached

  • More info at Milestone-0.3.2

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7:

    yum clean all && yum update python-ooi

  • For Ubuntu 14:04:

    apt-get update && apt-get install python-ooi

Artefacts

Orchestrator v. 1.1.0-FINAL

What's new

  • The compatibility with IAM has been improved

  • Now the resources obtained from the REST APIs are sorted by date

  • CLUES installed on board of the elastic clusters can receive the IAM token

List of RfCs

  • Issue #109 - Support iam_access_token property in tosca.nodes.indigo.ElasticCluster nodes

  • Issue #110 - Support multiple SLAs for the same cloud provider

  • Issue #101 - Deployments and resources must be sorted by date when retrieved from REST APIs

  • Issue #104 - Adapt user info data to the new IAM format

  • More details can be found in the CHANGELOG

Installation & Configuration

  • Before the upgrade it needs to be checked on IAM if the openid scope is selected for the Orchestrator protected resource server, otherwise the clients will not be able to make requests to it.

  • In order to update the container, please do:

    • Stop the old container:

      sudo docker stop orchestrator

    • Remove the old container:

      sudo docker rm orchestrator

    • Pull the new image version:

      sudo docker pull indigodatacloud/orchestrator:indigo_1

    • Start the new version, with the same command that you used before, just pay attention to use the right tag of the container, like:

      ```sudo docker run --name orchestrator --link databaseWorkflow:databaseWorkflow --link databaseOrchestrator:databaseOrchestrator \

      -p 80:8080 -e ORCHESTRATOR_URL="" -d indigodatacloud/orchestrator:indigo_1```

Artefacts

TOSCA-parser v. 0.6.1

What's new

  • The updated version of TOSCA-parser addresses minor bug fixes and integrates the changes made upstream (in openstack/tosca-parser v.0.6).

Installation & Configuration

In order to update the packages please use:

  • For CentOS 7:

    yum clean all && yum update tosca-parser

  • For Ubuntu 14:04:

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

Artefacts

PreviousThird Update of INDIGO-1NextFirst Update of INDIGO-1

Last updated