tosca-templates's Introduction

INDIGO-DataCloud tosca-templates

These are the TOSCA Templates Supporting the Use Cases for INDIGO-DataCloud. The applications currently supported are:

amber/ambertools.yaml: Deploy an instance that supports AmberTools.
amber/amber_job_*.yaml: Run the amber tool sander through a Chronos job.
disvis.yaml: Deploy an instance that supports DisVis.
docker-kepler.yaml: Deploy a container with the Kepler WF engine in the OneDock testbed.
galaxy.yaml: Deploy a Galaxy server configured to execute jobs locally.
galaxy_elastic_cluster.yaml: Deploy a Galaxy server configured with a SLURM elastic cluster as LRMS.
mesos_cluster.yaml: Deploy a mesos cluster. The cluster is composed by one master, three slaves and one load balancer.
powerfit.yaml: Deploy an instance that supports PowerFit.
dodas/*.yaml: Deploy an HTCondor cluster on Mesos (DODAS)
deep-oc: DEEP-Hybrid-DataCloud Open Catalog.

User guides:

tosca-templates's People

Contributors

Stargazers

Watchers

tosca-templates's Issues

Site-specific configuration value on custom_types.yaml

Hi,

By transforming TOSCA template to HOT template (mesos_cluster.yaml), on my new HOT code
site-specific configuration values appear.

I suggest to remove those site-specific configuration values present in the file
https://raw.githubusercontent.com/indigo-dc/tosca-types/master/custom_types.yaml
or make them parameterized (preferred).

Es. (zabbix server)
Row 262
default: indigo-paas.cloud.ba.infn.it

Regards,
Alessandro.

Template simple_node in deep-oc/vm_docker_deepaas.yml

I think that the node should be of type tosca.nodes.indigo.Compute instead of tosca.nodes.Compute. I couldn't find capabilities->os->properties->image in the Openstack's TOSCA basic types declaration (https://github.com/openstack/tosca-parser/blob/master/toscaparser/elements/TOSCA_definition_1_0.yaml). The Indigo data types contain an image property though, for tosca.capabilities.indigo.OperatingSystem which derives from tosca.capabilities.OperatingSystem.

Recommend Projects