Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5C439200CC1 for ; Mon, 10 Jul 2017 13:05:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 58D75160E2C; Mon, 10 Jul 2017 11:05:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9DCD4160E18 for ; Mon, 10 Jul 2017 13:05:13 +0200 (CEST) Received: (qmail 18652 invoked by uid 500); 10 Jul 2017 11:05:12 -0000 Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ariatosca.incubator.apache.org Delivered-To: mailing list issues@ariatosca.incubator.apache.org Received: (qmail 18642 invoked by uid 99); 10 Jul 2017 11:05:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2017 11:05:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4F9BD192B6B for ; Mon, 10 Jul 2017 11:05:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id u4Mp0UA1Rsur for ; Mon, 10 Jul 2017 11:05:11 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 32B73623EB for ; Mon, 10 Jul 2017 11:05:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8D6C1E0D9E for ; Mon, 10 Jul 2017 11:05:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 33FD92469E for ; Mon, 10 Jul 2017 11:05:00 +0000 (UTC) Date: Mon, 10 Jul 2017 11:05:00 +0000 (UTC) From: "Ran Ziv (JIRA)" To: issues@ariatosca.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (ARIA-254) Support multiple nodes of a node template at service creation time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 11:05:14 -0000 [ https://issues.apache.org/jira/browse/ARIA-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv resolved ARIA-254. -------------------------- Resolution: Fixed Fix Version/s: 0.2.0 > Support multiple nodes of a node template at service creation time > ------------------------------------------------------------------ > > Key: ARIA-254 > URL: https://issues.apache.org/jira/browse/ARIA-254 > Project: AriaTosca > Issue Type: Story > Reporter: Ran Ziv > Assignee: Tal Liron > Priority: Critical > Fix For: 0.2.0 > > > 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|https://github.com/apache/incubator-ariatosca/blob/1f3e7ff42fefcd5dc8191e3b0eeac0460db059b0/extensions/aria_extension_tosca/profiles/tosca-simple-1.0/capabilities.yaml#L151], [2|https://github.com/apache/incubator-ariatosca/blob/fdd57c47acfe63dc25c6f20bcb3785225b3f774d/aria/modeling/service_template.py#L310], [3|https://github.com/apache/incubator-ariatosca/blob/60ea3ebb21e762d36115db26563a93dd3cb72003/extensions/aria_extension_tosca/simple_v1_0/modeling/__init__.py#L163]) - 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 (v6.4.14#64029)