ariatosca-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tal Liron (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIA-388) ARIA allows ad hoc inputs but should require them to be declared a priori
Date Tue, 10 Oct 2017 22:01:00 GMT

     [ https://issues.apache.org/jira/browse/ARIA-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tal Liron updated ARIA-388:
---------------------------
    Description: As a user of ARIA, I would like ARIA to disallow ad hoc inputs and instead
require those inputs to be explicitly declared ahead of time.  (was: As a user of ARIA, I
would like ARIA to disallow ad hoc inputs and instead require those inputs to be explicitly
declared ahead of time.


On Tue, Oct 10, 2017 at 2:46 PM, DeWayne Filppi <dewayne@cloudify.co> wrote:

So you'd agree that it should have required an explicit definition of the
inputs?

On Tue, Oct 10, 2017 at 2:17 PM, Tal Liron <tal@cloudify.co> wrote:

Any help in debugging would be appreciated!

On Tue, Oct 10, 2017 at 2:02 PM, DeWayne Filppi <dewayne@cloudify.co>
wrote:

For reasons that somewhat mystify me, the template is installing with
no
errors now.  I fixed it by removing the inputs definition I had in the
terminal.yaml file, which is counter-intuitive.  I used to have, in the
node type definition:

   interfaces:
     Standard:
       create:
         implementation: cloudify-utilities-plugin >
cloudify_terminal.tasks.run
         inputs:
           calls:
             type: list
             entry_schema: call_type

I defined the inputs because I thought I had to.  This was the source
of
the error I mentioned in another thread (regarding yaml-1.1).  In any
case,
by commenting it out, I got no validation errors, and the terminal
calls
are made as expected.  In the node template, I still pass inputs:

     interfaces:
       Standard:
         create:
           inputs:
             calls:
               - action: exit

This doesn't seem as though it should be possible.  In any case, the
latest
has been pushed to the repo:
https://github.com/dfilppi/fortigate-tosca-example

DeWayne

On Tue, Oct 10, 2017 at 10:37 AM, DeWayne Filppi <dewayne@cloudify.co>
wrote:

For those interested, I'm in the process of implementing a TOSCA
template
for the initial deployment and configuration of a Fortigate VNF in
Openstack.  It uses a couple of borrowed Cloudify plugins: one for
Openstack itself (https://github.com/cloudify-
cosmo/cloudify-openstack-
plugin), and one for the terminal plugin (part of the Cloudify
incubator
"utilities" project (https://github.com/cloudify-
incubator/cloudify-utilities-plugin).

The basic idea is that a network and router is created with public
access,
and a private network with no direct public access.  In between is
the
Fortigate firewall VNF that controls access to instances running on
the
private network.  The initial template just sets up the VNF and
networks.
The next template (TBD) will deploy a service on the private network
and
reconfigure the firewall to allow access via port forwarding.   This
is
very much a work in progress (the VNF configuration isn't quite
working
yet):

https://github.com/dfilppi/fortigate-tosca-example)

> ARIA allows ad hoc inputs but should require them to be declared a priori
> -------------------------------------------------------------------------
>
>                 Key: ARIA-388
>                 URL: https://issues.apache.org/jira/browse/ARIA-388
>             Project: AriaTosca
>          Issue Type: Story
>    Affects Versions: 0.1.1
>            Reporter: Thomas Nadeau
>            Priority: Minor
>
> As a user of ARIA, I would like ARIA to disallow ad hoc inputs and instead require those
inputs to be explicitly declared ahead of time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message