It seems that the metadata field has been added in the v1.1 of the TOSCA YAML standard. As the properties field is already available in v1.0, couldn't we use that instead?

TOSCA YAML v1.0 policy definition
TOSCA YAML v1.1 policy definition

The SLA IDs used in the example https://github.com/indigo-dc/tosca-types/blob/master/examples/web_mysql_tosca_across_clouds.yaml are actually service IDs. These should be changed to these values:
service_id 4401ac5dc8cfbbb737b0a02575e6f4bc --> sla_id: 4401ac5dc8cfbbb737b0a02575ee53f6
service_id 7efc59c5db69ea67c5100de0f752b3de --> sla_id: 7efc59c5db69ea67c5100de0f752b3de

According to the information at: http://indigo.cloud.plgrid.pl/slam/preferences/indigo-dc

Hi,

I am deploying an infrastructure (using ORCHENT) described in https://raw.githubusercontent.com/indigo-dc/tosca-types/master/examples/eubiosteo_client.yml. It uses oneclient_install.yml, and I got an error on the operations done in this module:

...
TASK [Install Ubuntu oneclient package] ****************************************
ok: [158.42.105.6_22]

TASK [Add root user to fuse group] *********************************************
fatal: [158.42.105.6_22]: FAILED! => {"changed": false, "failed": true, "msg": "Group fuse does not exist"}

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
158.42.105.6_22 : ok=13 changed=0 unreachable=0 failed=1
158.42.105.6_22 : ok=13 changed=0 unreachable=0 failed=1

ERROR executing playbook (1/1)
ERROR executing task onedata_client_node_conf_onedata_client_node: (3/3)

...

It seems that the task:

• name: Add {{ansible_user}} user to fuse group
  user: name={{ansible_user}} append=yes groups=fuse
  when: ansible_distribution == "Ubuntu"

is not working as the fuse group is not created. It was created before when installing onedataclient.

Can you check?

Many thanks

Please, set consul_mode:"agent" at
https://github.com/indigo-dc/tosca-types/blob/master/artifacts/mesos/mesos_lb_install.yml#L9

In case of a Mesos Elastic cluster the user can select to use a secure version of Chronos and Marathon so we have to add the posibility to modify the curl options in the mesos clues plugin adding the corresponding parameters:

• protocol, port, username, password for Marathon and Chronos
  These values have to be propagated to the recipes.
  Proposed by @maricaantonacci .

Hello,

I am trying to understand some tosca templates from some projects. I see they use the indigo types:

imports:
- indigo_custom_types: https://raw.githubusercontent.com/indigo-dc/tosca-types/master/custom_types.yaml

However, I have not found any place with documentation for each type.
For example, where can I find a description for this type?
tosca.nodes.indigo.Container.Application.Docker.Marathon

Thank you.

Please, let zookeeper start only on the master nodes of the cluster, i.e. remove this section https://github.com/indigo-dc/tosca-types/blob/master/artifacts/mesos/mesos_slave_install.yml#L13-L15

Deploying the Cellar Web Application on Ubuntu 16.04 complains about the lack of the php5 package:

TASK [apt] *********************************************************************
fatal: [34.199.64.103_22]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'php5' is available"}

Remove line https://github.com/indigo-dc/tosca-types/blob/master/artifacts/mesos/mesos_master_install.yml#L15

E.g. https://github.com/indigo-dc/tosca-types/blob/master/examples/indigo_job_output_upload_swift.yaml#L75

mem:
      type: float # -> scalar-unit.size
      description: Amount of Memory (MB) for this job
      required: yes