Re: wiki entry for Periodic Blogs/vBlogs Created

[DeWayne Filppi]

Setting aside the knowledge of confluence, who would go looking for a wiki
via an "issue tracker" link?  This seems so obvious to me that there must
be something wrong with me.  I don't care where it is, I'd have just
preferred it "disinterred" rather than hidden.  So if I must be specific,
on the community page right above the dev mailling list line.  Franky, even
the community page isn't the right place.  "Docs" should lead to wiki and
the API docs, perhaps on a pulldown.   But that's more work.

DeWayne

On Mon, Nov 13, 2017 at 2:48 PM, Thomas Nadeau 
wrote:

>
> Specifics please! Like where specifically would you like this?  *)
>
> There is a link, but its buried a little. If you click on “Issue
> Tracker” here:
>
> http://ariatosca.incubator.apache.org/community/ <
> http://ariatosca.incubator.apache.org/community/>
>
> I am happy to make functional improvements like this. Just let me
> know where.
>
> —Tom
>
>
> > On Nov 13, 2017, at 5:15 PM, DeWayne Filppi  wrote:
> >
> > Yeah, at least that's where I instinctively look for it.  Then I have to
> > remember to go to github to find the link.  Seems arduous for those of us
> > with poor memories, or anyone approaching Aria for the first time.
> >
> > On Mon, Nov 13, 2017 at 1:40 PM, Thomas Nadeau 
> > wrote:
> >
> >>
> >>Specifically here or somewhere else?
> >>
> >> http://ariatosca.incubator.apache.org/community/ <
> >> http://ariatosca.incubator.apache.org/community/>
> >>
> >>
> >>> On Nov 13, 2017, at 4:35 PM, DeWayne Filppi 
> wrote:
> >>>
> >>> It would be nice if there was a link to the wiki on the community page.
> >>>
> >>> On Mon, Nov 13, 2017 at 1:19 PM, Thomas Nadeau 
> >>> wrote:
> >>>
> 
>    Just a heads up that I have created a section on the wiki to
>  store/manage/coordinate amongst ourselves here around
>  future blogs/vblogs. There is a section for planned/scheduled
>  entries, as well as future ones or suggested ones. If you have ideas
>  for these, please go here and add them. Its a dynamic document, so
>  we will update here as we go forward too.
> 
>  https://cwiki.apache.org/confluence/display/ARIATOSCA/
>  Periodic+Blogs+and+Videos   confluence/display/ARIATOSCA/Periodic+Blogs+and+Videos>
> 
>    Thanks,
> 
>    —Tom
> 
> 
> 
> 
> >>
> >>
>
>

Re: wiki entry for Periodic Blogs/vBlogs Created

[Thomas Nadeau]

Specifics please! Like where specifically would you like this?  *)

There is a link, but its buried a little. If you click on “Issue 
Tracker” here:

http://ariatosca.incubator.apache.org/community/ 


I am happy to make functional improvements like this. Just let me know 
where.

—Tom


> On Nov 13, 2017, at 5:15 PM, DeWayne Filppi  wrote:
> 
> Yeah, at least that's where I instinctively look for it.  Then I have to
> remember to go to github to find the link.  Seems arduous for those of us
> with poor memories, or anyone approaching Aria for the first time.
> 
> On Mon, Nov 13, 2017 at 1:40 PM, Thomas Nadeau 
> wrote:
> 
>> 
>>Specifically here or somewhere else?
>> 
>> http://ariatosca.incubator.apache.org/community/ <
>> http://ariatosca.incubator.apache.org/community/>
>> 
>> 
>>> On Nov 13, 2017, at 4:35 PM, DeWayne Filppi  wrote:
>>> 
>>> It would be nice if there was a link to the wiki on the community page.
>>> 
>>> On Mon, Nov 13, 2017 at 1:19 PM, Thomas Nadeau 
>>> wrote:
>>> 
 
   Just a heads up that I have created a section on the wiki to
 store/manage/coordinate amongst ourselves here around
 future blogs/vblogs. There is a section for planned/scheduled
 entries, as well as future ones or suggested ones. If you have ideas
 for these, please go here and add them. Its a dynamic document, so
 we will update here as we go forward too.
 
 https://cwiki.apache.org/confluence/display/ARIATOSCA/
 Periodic+Blogs+and+Videos 
 
   Thanks,
 
   —Tom
 
 
 
 
>> 
>> 

Re: wiki entry for Periodic Blogs/vBlogs Created

[DeWayne Filppi]

Yeah, at least that's where I instinctively look for it.  Then I have to
remember to go to github to find the link.  Seems arduous for those of us
with poor memories, or anyone approaching Aria for the first time.

On Mon, Nov 13, 2017 at 1:40 PM, Thomas Nadeau 
wrote:

>
> Specifically here or somewhere else?
>
> http://ariatosca.incubator.apache.org/community/ <
> http://ariatosca.incubator.apache.org/community/>
>
>
> > On Nov 13, 2017, at 4:35 PM, DeWayne Filppi  wrote:
> >
> > It would be nice if there was a link to the wiki on the community page.
> >
> > On Mon, Nov 13, 2017 at 1:19 PM, Thomas Nadeau 
> > wrote:
> >
> >>
> >>Just a heads up that I have created a section on the wiki to
> >> store/manage/coordinate amongst ourselves here around
> >> future blogs/vblogs. There is a section for planned/scheduled
> >> entries, as well as future ones or suggested ones. If you have ideas
> >> for these, please go here and add them. Its a dynamic document, so
> >> we will update here as we go forward too.
> >>
> >> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >> Periodic+Blogs+and+Videos  >> confluence/display/ARIATOSCA/Periodic+Blogs+and+Videos>
> >>
> >>Thanks,
> >>
> >>—Tom
> >>
> >>
> >>
> >>
>
>

Re: wiki entry for Periodic Blogs/vBlogs Created

[Thomas Nadeau]

Specifically here or somewhere else?

http://ariatosca.incubator.apache.org/community/ 



> On Nov 13, 2017, at 4:35 PM, DeWayne Filppi  wrote:
> 
> It would be nice if there was a link to the wiki on the community page.
> 
> On Mon, Nov 13, 2017 at 1:19 PM, Thomas Nadeau 
> wrote:
> 
>> 
>>Just a heads up that I have created a section on the wiki to
>> store/manage/coordinate amongst ourselves here around
>> future blogs/vblogs. There is a section for planned/scheduled
>> entries, as well as future ones or suggested ones. If you have ideas
>> for these, please go here and add them. Its a dynamic document, so
>> we will update here as we go forward too.
>> 
>> https://cwiki.apache.org/confluence/display/ARIATOSCA/
>> Periodic+Blogs+and+Videos > confluence/display/ARIATOSCA/Periodic+Blogs+and+Videos>
>> 
>>Thanks,
>> 
>>—Tom
>> 
>> 
>> 
>> 

Re: wiki entry for Periodic Blogs/vBlogs Created

[DeWayne Filppi]

It would be nice if there was a link to the wiki on the community page.

On Mon, Nov 13, 2017 at 1:19 PM, Thomas Nadeau 
wrote:

>
> Just a heads up that I have created a section on the wiki to
> store/manage/coordinate amongst ourselves here around
> future blogs/vblogs. There is a section for planned/scheduled
> entries, as well as future ones or suggested ones. If you have ideas
> for these, please go here and add them. Its a dynamic document, so
> we will update here as we go forward too.
>
> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Periodic+Blogs+and+Videos  confluence/display/ARIATOSCA/Periodic+Blogs+and+Videos>
>
> Thanks,
>
> —Tom
>
>
>
>

Re: Podlings reports schedule?

[Thomas Nadeau]

> On Nov 13, 2017, at 3:41 PM, John D. Ament  wrote:
> 
> On Mon, Nov 13, 2017 at 2:58 PM Thomas Nadeau  wrote:
> 
>> 
>>Mentors:
>> 
>>I just realized that I overlooked submitting the podling report
>> for October, so I looked
> 
> 
> Errr, not sure why you believe you overlooked submitting a report.
> Podlings submit reports once per quarter.  The last report was due in
> September and was received.

OK cool. I thought they were monthly because of a) Arthur’s last 
(private) email and b) the fact that there are monthly podling reports on our 
wiki.

> On the flip side, you specifically don't owe anything.  The PPMC does.

That is good news.

> around for instructions for how to do this. I was looking for information
>> about when/what format the podling reports should be in and found this:
>> 
>> https://incubator.apache.org/guides/ppmc.html <
>> https://incubator.apache.org/guides/ppmc.html>
>> 
>> The following link there is broken, I’ve emailed  us...@infra.apache.org
>>  to resolve the issue but there is no
>> information from there I can get right now.
>> 
> 
> I have no idea why you emailed infra about this.  This is a discussion for
> general@incubator.

Well, because I just don’t know as much as you do about the Apache 
infrastructure
situation. Please understand that people that are new to the Apache 
organization are unfamiliar 
with issues like this and frankly, the web site is not really that intuitive. 
As for why I chose this list,
I will also refer you to the Apache Infrastructure’s Page on Instructions which 
seemed
to fit the bill, although why the "general discussion” is not referred to as 
“general@…” I do not
know.

users@infra ... the general discussion list is used by the Infrastructure team 
to discuss issues concerning the operation of the overall Apache Software 
Foundation systems, and for committers to report problems or issues. This is 
not the address for questions about any of the ASF or its projects. It is for 
communication between ASF committers only to support the infrastructure. Anyone 
may send mail to report problems with ASF systems (however see notes about 
service status  ). Previously 
known as infrastructure@


> https://incubator.apache.org/report-groups.txt <
>> https://incubator.apache.org/report-groups.txt>
>> 
>> I found this reference which said to do a PR on the incubator
>> site:
>> 
>> 
>> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
>> <
>> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
>>> 
>> 
> 
> That's your status page.  Status pages don't maintain reports.

I understand that. A pointer to how to maintain reports would have been 
appreciated. 
Again, reading what is there at face value, it says to do PRs for new entries. 
If that is 
not the case, changing that to a link with correct instructions would be 
awesome.

> 
>>However, I’ve found the previous podling reports here on Jira, so
>> should I just edit a page here instead?
>> 
>> 
>> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
>> <
>> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
>>> 
>> 
>> 
>>Is there a specific cadence at which these should be published?
>> 
>> 
> Quarterly.
> 
> 
>> 
>>Thx,
>> 
>>—Tom
>> 
>> 

wiki entry for Periodic Blogs/vBlogs Created

[Thomas Nadeau]

Just a heads up that I have created a section on the wiki to
store/manage/coordinate amongst ourselves here around
future blogs/vblogs. There is a section for planned/scheduled
entries, as well as future ones or suggested ones. If you have ideas
for these, please go here and add them. Its a dynamic document, so
we will update here as we go forward too.

https://cwiki.apache.org/confluence/display/ARIATOSCA/Periodic+Blogs+and+Videos 


Thanks,

—Tom

Re: Podlings reports schedule?

[John D. Ament]

On Mon, Nov 13, 2017 at 2:58 PM Thomas Nadeau  wrote:

>
> Mentors:
>
> I just realized that I overlooked submitting the podling report
> for October, so I looked


Errr, not sure why you believe you overlooked submitting a report.
Podlings submit reports once per quarter.  The last report was due in
September and was received.

On the flip side, you specifically don't owe anything.  The PPMC does.


> around for instructions for how to do this. I was looking for information
> about when/what format the podling reports should be in and found this:
>
> https://incubator.apache.org/guides/ppmc.html <
> https://incubator.apache.org/guides/ppmc.html>
>
> The following link there is broken, I’ve emailed  us...@infra.apache.org
>  to resolve the issue but there is no
> information from there I can get right now.
>

I have no idea why you emailed infra about this.  This is a discussion for
general@incubator.


>
> https://incubator.apache.org/report-groups.txt <
> https://incubator.apache.org/report-groups.txt>
>
>  I found this reference which said to do a PR on the incubator
> site:
>
>
> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
> <
> https://incubator.apache.org/guides/website.html#Edit+your+project+status+page
> >
>

That's your status page.  Status pages don't maintain reports.


>
> However, I’ve found the previous podling reports here on Jira, so
> should I just edit a page here instead?
>
>
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
> <
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09
> >
>
>
> Is there a specific cadence at which these should be published?
>
>
Quarterly.


>
> Thx,
>
> —Tom
>
>

Re: native plugins

[Tal Liron]

There is no spec for native plugins yet, but it's something that I'm
working on. More info to come.

On Mon, Nov 13, 2017 at 12:54 PM, DeWayne Filppi 
wrote:

> As opposed to using Cloudify plugins, is there an example of a native
> plugin?  Or should new plugins just be written for Cloudify and adapted.
> I'm talking user role plugins, not internal like execution.
>
> DeWayne
>

Podlings reports schedule?

[Thomas Nadeau]

Mentors:

I just realized that I overlooked submitting the podling report for 
October, so I looked around for instructions for how to do this. I was looking 
for information about when/what format the podling reports should be in and 
found this:

https://incubator.apache.org/guides/ppmc.html 


The following link there is broken, I’ve emailed  us...@infra.apache.org 
 to resolve the issue but there is no 
information from there I can get right now.

https://incubator.apache.org/report-groups.txt 


 I found this reference which said to do a PR on the incubator site:

https://incubator.apache.org/guides/website.html#Edit+your+project+status+page 


However, I’ve found the previous podling reports here on Jira, so 
should I just edit a page here instead? 

https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-09 



Is there a specific cadence at which these should be published?


Thx,

—Tom

native plugins

[DeWayne Filppi]

As opposed to using Cloudify plugins, is there an example of a native
plugin?  Or should new plugins just be written for Cloudify and adapted.
I'm talking user role plugins, not internal like execution.

DeWayne

AriaTosca website published

[Apache Jenkins Server]

The Apache Jenkins build system has built AriaTosca Website (build #35)

Status: Successful

Check console output at https://builds.apache.org/job/AriaTosca%20Website/35/ 
to view the results.

Backlog Grooming Meeting Minutes: Monday, November 13, 2017

[Thomas Nadeau]

backlog grooming
  
Sprint #2, week 2Nov 13, 2017

Attendees: Tal, Vish, Tom, Arthur, Maxim


ARIA-1: Status, need another week to merge PR.  This will delay our .2 release 
to not begin until Monday, November 20.

We will need to revisit the release plan next Monday, as Tom (and Vish) plan on 
taking PTO next week.

Closed Aria-397 - merged by Arthur

Need to add permissions for Vish


GitBox Transition: I haven't heard back details from Suneel yet as to when/what 
will happen.  He has taken the action with Jonathan to invoke the chagne via 
Apache IT.

Vish to look at ARIA-399: Arthur is working on resettting the Docker HUB 
Pwd/credentials.
Docker compose file into the examples dir, and push image to DockerHUB.
Those two things will satisfy the story.

We need two things: the docker compose file for Aria, and make the docker image 
on Dockerhub that is pushed via the Apache release process.

Groomed rest of top of the backlog.

Tal/Tom in Israel week after Thanksgiving.

Tom to create Sprint 3, which likely will contain .2 release.

Re: Implementation for get_operation_output

[Tal Liron]

No, it has not yet been implemented.

On Mon, Nov 13, 2017 at 2:03 AM, D Jayachandran  wrote:

> Hi Tal,
>
> Will the below work at this moment ?
>
> ctx return my_value = this is the value
> And then you could use get_operation_output on "my_value".
>
>
> Regards,
> DJ
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Thursday, November 09, 2017 10:14 PM
> To: dev@ariatosca.incubator.apache.org
> Cc: Paul Doyle ; Barry Downey <
> barry.dow...@ericsson.com>
> Subject: Re: Implementation for get_operation_output
>
> This function has not yet been implemented, so it's stored nowhere. But of
> course it will likely have to be stored per particular execution.
>
> The "ctx" tool is just a way to remotely access the context object, so
> yes, with plugins it's identical.
>
> On Thu, Nov 9, 2017 at 1:14 AM, D Jayachandran <
> d.jayachand...@ericsson.com>
> wrote:
>
> > Hi Tal,
> >
> > To understand a bit more, so where are these return values stored ?
> > Would they updated to services as we do with TOSCA attributes or do
> > they live only for a particular execution ?
> > Also when it comes to plugin, can I do the same with the context
> > object being passed rather than using the "ctx" tool ?
> >
> > Regards,
> > DJ
> > -Original Message-
> > From: Tal Liron [mailto:t...@cloudify.co]
> > Sent: Wednesday, November 08, 2017 8:06 PM
> > To: dev@ariatosca.incubator.apache.org
> > Cc: Paul Doyle ; Barry Downey <
> > barry.dow...@ericsson.com>
> > Subject: Re: Implementation for get_operation_output
> >
> > ARIA currently uses a special tool, called "ctx", to communicate with
> > implementation scripts. I imagine we will use the same tool to set
> > return values.
> >
> > My understanding is also that these return values are quite arbitrary,
> > and thus un-typed. They will likely be stored as strings. So, for
> > example, from within a bash script you would do something like this:
> >
> > ctx return my_value = this is the value
> >
> > And then you could use get_operation_output on "my_value".
> >
> >
> > On Tue, Nov 7, 2017 at 5:55 AM, D Jayachandran <
> > d.jayachand...@ericsson.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > We currently don't have an implementation for the intrinsic function
> > > "get_operation_output".
> > >
> > > As per the TOSCA Simple YAML 1.0, specification it indicates this
> > > function must be used to retrieve the values of variables exposed /
> > > exported from an interface operation.
> > > The variable which is referenced here seems to be an environmental
> > > variable exposed by the interface operation script/plugin. (2.14.3
> > Example:
> > > setting output variables to an attribute, 2.14.4 Example: passing
> > > output variables between operations )
> > >
> > > We would like if you have the same understanding on the variable
> > > which is referenced in "get_operation_output".
> > >
> > > FROM TOSCA SPEC
> > >
> > >  - The required name of the variable that is
> > > exposed / exported by the operation.
> > >
> > > Here it is just stated as a variable. In the example it is mentioned
> > > as "environmental" variable exposed. Do you see a difference here ?
> > > Are we considering as an environmental variable or as an attribute
> > variable ?.
> > >
> > > Please let us know your comments on this so that we can plan the
> > > implementation of this.
> > >
> > > Regards,
> > > DJ
> > >
> >
>

New Parser Test Suite Demo Reminder

[Thomas Nadeau]

Just a reminder that Tal is going to be doing a demo/explanation of the 
new
parser test suite at 10AM EST. All are welcome to attend. This is the Zoom URL:

https://cloudify.zoom.us/j/9979398111 

—Tom

Re: Official Project Vote: Moving to Gitbox

[Thomas Nadeau]

OK I think we’ve given it the mandatory 3 days and then some. I haven’t 
seen any other votes, so the tally below stands.

Question:  does this shift include the aria-tosca-website as well?  I 
was just
discussing offline with a few that this should be synchronized and operated in
the same manner as the main source code repository for the simple reason that
devs will need to make changes to both areas, and its just plain simpler if 
they’re
both the same process.

—Tom


> On Nov 10, 2017, at 6:57 AM, Thomas Nadeau  wrote:
> 
> 
>   No one mentioned that we needed to keep this open for 3 days.  Ill keep 
> that
> in mind for the future.
> 
>   The original call for votes was sent Wednesday at 11AM EST, so 
> technically speaking Saturday
> at 11AM EST will be 3 full days.  Give it one more day then.
> 
>   —Tom
> 
> 
>> On Nov 9, 2017, at 8:48 PM, Suneel Marthi  wrote:
>> 
>> Have we kept this vote open for 3 days ?
>> 
>> On Fri, Nov 10, 2017 at 2:28 AM, Thomas Nadeau 
>> wrote:
>> 
>>> 
>>>   The official voting tally is:
>>> 
>>>   Active committers:
>>> 
>>>   Suneel: +1
>>>   Tal: +1
>>>   Avia: +1
>>>   Maxim: +1
>>> 
>>>   Active Contributors:
>>> 
>>>   Tom: +1
>>>   Vish: +1
>>> 
>>> 
>>>   I am calling that we’ve met the threshold to make this change.
>>> John or Suneel, I think the next step here is for one of you guys
>>> to request to Apache Ops to make the switch.
>>> 
>>>   —Tom
>>> 
>>> 
>>> 
> 

RE: Implementation for get_operation_output

[D Jayachandran]

Hi Tal,

Will the below work at this moment ?

ctx return my_value = this is the value
And then you could use get_operation_output on "my_value".


Regards,
DJ
-Original Message-
From: Tal Liron [mailto:t...@cloudify.co] 
Sent: Thursday, November 09, 2017 10:14 PM
To: dev@ariatosca.incubator.apache.org
Cc: Paul Doyle ; Barry Downey 

Subject: Re: Implementation for get_operation_output

This function has not yet been implemented, so it's stored nowhere. But of 
course it will likely have to be stored per particular execution.

The "ctx" tool is just a way to remotely access the context object, so yes, 
with plugins it's identical.

On Thu, Nov 9, 2017 at 1:14 AM, D Jayachandran 
wrote:

> Hi Tal,
>
> To understand a bit more, so where are these return values stored ? 
> Would they updated to services as we do with TOSCA attributes or do 
> they live only for a particular execution ?
> Also when it comes to plugin, can I do the same with the context 
> object being passed rather than using the "ctx" tool ?
>
> Regards,
> DJ
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Wednesday, November 08, 2017 8:06 PM
> To: dev@ariatosca.incubator.apache.org
> Cc: Paul Doyle ; Barry Downey < 
> barry.dow...@ericsson.com>
> Subject: Re: Implementation for get_operation_output
>
> ARIA currently uses a special tool, called "ctx", to communicate with 
> implementation scripts. I imagine we will use the same tool to set 
> return values.
>
> My understanding is also that these return values are quite arbitrary, 
> and thus un-typed. They will likely be stored as strings. So, for 
> example, from within a bash script you would do something like this:
>
> ctx return my_value = this is the value
>
> And then you could use get_operation_output on "my_value".
>
>
> On Tue, Nov 7, 2017 at 5:55 AM, D Jayachandran < 
> d.jayachand...@ericsson.com>
> wrote:
>
> > Hi All,
> >
> > We currently don't have an implementation for the intrinsic function 
> > "get_operation_output".
> >
> > As per the TOSCA Simple YAML 1.0, specification it indicates this 
> > function must be used to retrieve the values of variables exposed / 
> > exported from an interface operation.
> > The variable which is referenced here seems to be an environmental 
> > variable exposed by the interface operation script/plugin. (2.14.3
> Example:
> > setting output variables to an attribute, 2.14.4 Example: passing 
> > output variables between operations )
> >
> > We would like if you have the same understanding on the variable 
> > which is referenced in "get_operation_output".
> >
> > FROM TOSCA SPEC
> >
> >  - The required name of the variable that is 
> > exposed / exported by the operation.
> >
> > Here it is just stated as a variable. In the example it is mentioned 
> > as "environmental" variable exposed. Do you see a difference here ?
> > Are we considering as an environmental variable or as an attribute
> variable ?.
> >
> > Please let us know your comments on this so that we can plan the 
> > implementation of this.
> >
> > Regards,
> > DJ
> >
>