[OASIS Issue Tracker] (TOSCA-180) Support of secured repositories for artifacts

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50341#comment-50341 ] 

Matthew Rutkowski  commented on TOSCA-180:
------------------------------------------

After discussion at the TOSCA YAML WG we have the following pseudocode and evaluation rules:

tosca_definitions_version: tosca_simple_yaml_1_0

imports:
  - option1-repositories.yaml.ste
  - 2.ste

node_templates:
  my_db:
    type: tosca.nodes.Database.MySQLDatabase
    properties:
	  db_name: { get_input: database_name }
	  db_user: { get_input: database_user }
	  db_password: { get_input: database_password }
	  db_port: { get_input: database_port }
    artifacts:
	  - tomcat_tar_gz: files/tomcat.tar.gz
	  - mysql_installation: < file relative to CSAR | URL >
            artifact_name: files/mysql.rpm  # path (last seg)
            url: http://non-secure.com/files/
            repos: [ my_repo1, my_repo2, ... ]
	  - jre: jre7.rpm
           

repositories: 
    my_repo1:
       xxx
    my_repo2:
       yyy

  
1) look in CSAR (manifest)
   ("file:" protocol is redundant but implies it is in CSAR)
2) look in all (named) repos (sequential) whether imported or in service template
   2a) If fully qualified URL directly access artifact 
   2b) use repos keyword for explicit (named) repos to look up artifact name
   2c) if NO repos keyword search all repos for artifact name
3) if duplicate names for artifact (error)



> Support of secured repositories for artifacts
> ---------------------------------------------
>
>                 Key: TOSCA-180
>                 URL: https://issues.oasis-open.org/browse/TOSCA-180
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>            Reporter: Moshe Elisha
>            Assignee: Moshe Elisha
>
> Currently, the DSL supports two types of artifacts locations:
> 1. In the CSAR - the artifact URI is relative to the location in the CSAR file.
> 2. In an external repository - the artifact URI is a public URL to some file server.
> The file server can require credentials that can be supplied in the URL in the format "protocol://username:password@hostname/" but because we don't have concatenation functions in the DSL, we can't use get_input and the username and password will need to be "hard-coded" inside the template.
> There is a concrete need for an external repository as the size of the deployments artifacts can sometimes reach several GBs and there is a requirement from customers that the repository should be secured.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)