RE: Fortigate VNF template

2017-10-11 Thread DeWayne Filppi
essage- From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] Sent: Wednesday, October 11, 2017 10:08 AM To: dev@ariatosca.incubator.apache.org Subject: Re: Fortigate VNF template Perfect! Thx man. —Tom > On Oct 11, 2017, at 9:30 AM, DeWayne Filppi <dewa...@cloudify.co> wrote: > >

RE: Fortigate VNF template

2017-10-11 Thread Steve Baillargeon
Message- From: Thomas Nadeau [mailto:tnadeaua...@gmail.com] Sent: Wednesday, October 11, 2017 10:08 AM To: dev@ariatosca.incubator.apache.org Subject: Re: Fortigate VNF template Perfect! Thx man. —Tom > On Oct 11, 2017, at 9:30 AM, DeWayne Filppi <dewa...@cloudify.co> wrote: >

Re: Fortigate VNF template

2017-10-11 Thread Thomas Nadeau
Perfect! Thx man. —Tom > On Oct 11, 2017, at 9:30 AM, DeWayne Filppi wrote: > > I already provided more detail. I'll see if I can boil it down into a > focused example. > > On Tue, Oct 10, 2017 at 5:02 PM, Tal Liron wrote: > >> Thanks, Tom. I'm

Re: Fortigate VNF template

2017-10-11 Thread DeWayne Filppi
I already provided more detail. I'll see if I can boil it down into a focused example. On Tue, Oct 10, 2017 at 5:02 PM, Tal Liron wrote: > Thanks, Tom. I'm pretty sure there already is just a JIRA... anyway, I > edited yours just to remove the other things, because DeWayne is

Re: Fortigate VNF template

2017-10-11 Thread Thomas Nadeau
Cool. Thx. I just wanted to ensure this was captured. It can be duped later if it is. 8) —Tom > On Oct 10, 2017, at 6:02 PM, Tal Liron wrote: > > Thanks, Tom. I'm pretty sure there already is just a JIRA... anyway, I > edited yours just to remove the other

Re: Fortigate VNF template

2017-10-10 Thread Tal Liron
Thanks, Tom. I'm pretty sure there already is just a JIRA... anyway, I edited yours just to remove the other things, because DeWayne is reporting a different issue here. DeWayne, could you you pretty please provide us with something more than "blows a gasket"? What happens exactly and when, and

Re: Fortigate VNF template

2017-10-10 Thread Thomas Nadeau
I created https://issues.apache.org/jira/browse/ARIA-388 to capture this. —Tom > On Oct 10, 2017, at 4:09 PM, DeWayne Filppi wrote: > > Ok. The interesting thing is that not only does it allow you to have > ad-hoc inputs, it also blows a gasket when you

Re: Fortigate VNF template

2017-10-10 Thread DeWayne Filppi
Ok. The interesting thing is that not only does it allow you to have ad-hoc inputs, it also blows a gasket when you try to define them. On Tue, Oct 10, 2017 at 3:02 PM, Tal Liron wrote: > ARIA right now lets you throw in ad hoc inputs, but I consider this to be a > bug. So

Re: Fortigate VNF template

2017-10-10 Thread Tal Liron
ARIA right now lets you throw in ad hoc inputs, but I consider this to be a bug. So yes, I would say you absolutely need to declare your inputs. On Tue, Oct 10, 2017 at 2:46 PM, DeWayne Filppi wrote: > So you'd agree that it should have required an explicit definition of

Re: Fortigate VNF template

2017-10-10 Thread DeWayne Filppi
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 wrote: > Any help in debugging would be appreciated! > > On Tue, Oct 10, 2017 at 2:02 PM, DeWayne Filppi > wrote: > > > For

Re: Fortigate VNF template

2017-10-10 Thread Tal Liron
Any help in debugging would be appreciated! On Tue, Oct 10, 2017 at 2:02 PM, DeWayne Filppi 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

Re: Fortigate VNF template

2017-10-10 Thread DeWayne Filppi
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:

Re: Fortigate VNF template

2017-10-10 Thread Arthur Berezin
s/repo/directory/ My bad :) On Tue, Oct 10, 2017 at 7:12 PM Tal Liron wrote: > Just to clarify, there is no separate "examples repo". It is simply a > directory in the ARIA source repository. > > On Tue, Oct 10, 2017 at 10:56 AM, Thomas Nadeau > wrote:

Re: Fortigate VNF template

2017-10-10 Thread Tal Liron
Just to clarify, there is no separate "examples repo". It is simply a directory in the ARIA source repository. On Tue, Oct 10, 2017 at 10:56 AM, Thomas Nadeau wrote: > > Sweet. It would be a good idea to document the example too. > > —Tom > > > > On Oct

Re: Fortigate VNF template

2017-10-10 Thread Arthur Berezin
That's a good point, I think we can add this under the ARIA examples repo here: https://github.com/apache/incubator-ariatosca/tree/master/examples Arthur On Tue, Oct 10, 2017 at 6:52 PM DeWayne Filppi wrote: > Nope. > > On Oct 10, 2017 10:50 AM, "Tal Liron"

Re: Fortigate VNF template

2017-10-10 Thread Thomas Nadeau
Sweet. It would be a good idea to document the example too. —Tom > On Oct 10, 2017, at 11:55 AM, Arthur Berezin wrote: > > That's a good point, I think we can add this under the ARIA examples repo > here: >

Re: Fortigate VNF template

2017-10-10 Thread DeWayne Filppi
Nope. On Oct 10, 2017 10:50 AM, "Tal Liron" wrote: > Great! Is there anything stopping you from contributing this to the ARIA > project when done? > > On Tue, Oct 10, 2017 at 10:37 AM, DeWayne Filppi > wrote: > > > For those interested, I'm in the process

Re: Fortigate VNF template

2017-10-10 Thread Tal Liron
Great! Is there anything stopping you from contributing this to the ARIA project when done? On Tue, Oct 10, 2017 at 10:37 AM, DeWayne Filppi wrote: > For those interested, I'm in the process of implementing a TOSCA template > for the initial deployment and configuration of

Fortigate VNF template

2017-10-10 Thread DeWayne Filppi
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