ariatosca-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARIA-254) Support multiple nodes of a node template at service creation time
Date Sun, 04 Jun 2017 09:51:04 GMT


ASF GitHub Bot commented on ARIA-254:

Github user mxmrlv commented on a diff in the pull request:
    --- Diff: tests/end2end/ ---
    @@ -39,4 +39,4 @@ def _verify_deployed_service_in_storage(service_name, model_storage):
         service = service_templates[0].services[service_name]
         assert == service_name
         assert len(service.executions) == 0  # dry executions leave no traces
    -    assert len(service.nodes) == 10
    +    assert len(service.nodes) == 13
    --- End diff --
    why 13? I though you added just one other instance

> Support multiple nodes of a node template at service creation time
> ------------------------------------------------------------------
>                 Key: ARIA-254
>                 URL:
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Assignee: Tal Liron
>            Priority: Critical
> Currently each node template can only have a single node.
> We need to support having multiple nodes of a given node-template at service creation
time. The mechanism for this should take into consideration future stories which would require
allowing scaling the number of nodes of a node-template up or down.
> Note: the term {{default_instances}} appears in several places in the code ([1|],
- we could perhaps use this or an extension based on this idea to support this issue.
> One other thing that should be taken into consideration (but perhaps be moved to a separate
JIRA issue) is the implicit declaration of multiple instances via the capabilities&requirements
mechanism in TOSCA - We need to decide if to support this as well or not, and if we do, how
does this play together with the primary method of declaring multiple nodes (or perhaps would
this be the only method of doing so?)

This message was sent by Atlassian JIRA

View raw message