RE: Node Template Substitution

[D Jayachandran]

Hi Tal,

Could you point to the open items with respect to substitution mapping, so that 
we can see if we can contribute for those items.

Regards,
DJ

-Original Message-
From: Tal Liron [mailto:t...@cloudify.co] 
Sent: Tuesday, December 12, 2017 7:02 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Node Template Substitution

There is currently no clear timeline. I expect it would take several weeks, 
perhaps months, unless more contributors step up to assist the effort.

On Tue, Dec 12, 2017 at 5:00 AM, D Jayachandran  wrote:

> Hi,
>
> When can we expect the support for substitution mapping to be merged 
> to master branch ?
>
> Regards,
> DJ
> -Original Message-
> From: Steve Baillargeon [mailto:steve.baillarg...@ericsson.com]
> Sent: Friday, December 08, 2017 8:26 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Node Template Substitution
>
> Hi Avia
> I don't access to the design doc. Am I missing something?
>
> Will 0.2.0 support YAML Profile 1.0 or 1.2 topology substitution?
> Or is it postponed to later?
>
> -Steve
>
> -Original Message-
> From: Avia Efrat [mailto:a...@cloudify.co]
> Sent: Tuesday, October 17, 2017 4:44 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Node Template Substitution
>
> There are plans to extend substitution mappings support to TOSCA 1.2, 
> just as any other change/improvement in the 1.2 profile.
>
> A CSAR with one 'main' service template and other service templates 
> will be stored as one service template, and will have one unique name.
>
> The design doc:
> https://drive.google.com/open?id=19nPjSj6mJyXWd4KLxPqRNp_
> TPqLpvXjzj98NXrAmcjc
>
>
> Additional v1.2 issues (a non-exhaustive list):
> https://docs.google.com/document/d/18yZC8qIWMbWBeULOzmLTT_
> oVrZXQ3z4030U6JIXdJ84/edit
>
>
> On Sat, Oct 14, 2017 at 2:10 AM, Steve Baillargeon < 
> steve.baillarg...@ericsson.com> wrote:
>
> > Hi Avia
> > One more question.
> >
> > Say we have a CSAR that contains multiple TOSCA YAML files e.g. a 
> > top-level ST and a bunch of low-level STs.
> > I am assuming all those TOSCA service templates (all of them have a 
> > full topology section) will be stored as a single “service-template”
> > in ARIA and a single unique name is needed to represent such single
> “service-template”
> > composed of multiple topologies.
> > Is this correct?
> >
> > -Steve
> >
> > -Original Message-
> > From: Steve Baillargeon
> > Sent: Wednesday, October 11, 2017 11:29 AM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: RE: Node Template Substitution
> >
> > Hi Avia
> > Is it possible to review the design documentation for it?
> > Do you have a doc or a few notes describing how ARIA will perform 
> > "best matching" based on YAML 1.0/1.1 profile?
> >
> > The full support for NFV Profile 1.0 requires Node Template 
> > Substitution defined in YAML 1.2 profile.
> > Any future plans for ARIA to extend Node Template Substitution as 
> > defined in YAML 1.2 profile ?
> >
> > Regards
> > Steve B
> >
> > -Original Message-
> > From: Arthur Berezin [mailto:art...@cloudify.co]
> > Sent: Tuesday, October 10, 2017 12:20 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: Node Template Substitution
> >
> > Avia, can you please post a link to the design?  thanks
> >
> > On Mon, Oct 9, 2017 at 5:14 PM Avia Efrat  wrote:
> >
> > > Currently the design is finished, and it is on a small hold for now.
> > > The plan is to support the 1.0/1.1 profile.
> > >
> > > On Wed, Oct 4, 2017 at 7:50 PM, Steve Baillargeon < 
> > > steve.baillarg...@ericsson.com> wrote:
> > >
> > > > Hi
> > > > Can we have a status update on the availability of the Node 
> > > > Template Substitution feature (aka substitution mappings)?
> > > > Will it support the "capabilities" defined in YAML Profile 1.0 
> > > > or YAML Profile 1.2?
> > > >
> > > > Regards
> > > > Steve B
> > > >
> > > >
> > >
> >
>

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Thomas Nadeau]

Thanks for posting.

Can you elaborate on your concerns?  From my perspective, I do not think
there is any preference of grooming meetings over mailing list
interactions. Everyone is invited to an open meeting, which happens once at
week at a time that was discussed openly on the list to accommodate
everyone. Furthermore, it has been said many times that the date/time is
not set in stone and can be changed going forward. Meeting minutes are
captured and posted to the list where additional open discussion is
invited.  People are free to (and have) groomed their own stories
independently too, which is cool. The only thing that has been asked is
that they give a heads up to the community on the list.

--Tom


On Tue, Dec 12, 2017 at 4:07 PM, John D. Ament 
wrote:

> I went ahead and posted the report to the incubator wiki.  Please review:
> https://wiki.apache.org/incubator/December2017
>
> I did make a few changes and ommissions.  Most importantly, we don't
> predict graduation dates.  I'm also a bit concerned with the preference of
> the grooming meetings over on list communication.
>
> John
>
> On Tue, Dec 12, 2017 at 8:23 AM Suneel Marthi  wrote:
>
> > I have not had a chance to review the draft - given that we are late on
> the
> > report I would prefer filing an updated report next month.
> > Meanwhile can we get a release out before the holidays kick in.
> >
> > Suneel
> >
> > On Tue, Dec 12, 2017 at 6:24 AM, Thomas Nadeau 
> > wrote:
> >
> > >
> > > I am confused - and have asked about what the specific process
> is
> > > for this. All
> > > I was told by Suneel when I asked, was to post up a G doc for people to
> > > hack/review
> > > together.  I have no idea what happens post that, so that is all I’ve
> > done.
> > >
> > > So to answer your question, the doc on the wiki is the final
> one.
> > > No one has
> > > submitted any comments since I posted it there last Thursday.
> > >
> > > —Tom
> > >
> > >
> > > > On Dec 11, 2017, at 9:32 PM, John D. Ament 
> > > wrote:
> > > >
> > > > So, I'm a bit confused as far as next steps.
> > > >
> > > > Is the report posted at
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > Podling+Report+2017-DEC-12
> > > > the
> > > > report we are saying should be submitted for the podling?  And are
> you
> > > > looking for me to post it on the incubator wiki?
> > > >
> > > > John
> > > >
> > > > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> > > >
> > > >> There actually was some in-person conversation between committers
> > about
> > > the
> > > >> report. But it's a good criticism -- we should make it explicitly
> open
> > > and
> > > >> via the mailing list.
> > > >>
> > > >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau <
> tnadeaua...@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >>>
> > > >>>
> > >  On Dec 11, 2017, at 9:36 AM, John D. Ament  >
> > > >>> wrote:
> > > 
> > >  The typical steps a podling would take:
> > > 
> > >  - Post a report on a common ground (e.g. email, confluence, or
> > other)
> > >  - Let others know where it is
> > >  - Discuss it and get others to contribute into it
> > >  - When the report comes through, post it on the incubator wiki,
> e.g.
> > >  https://wiki.apache.org/incubator/December2017 (link changes each
> > > >> month)
> > > 
> > >  The report generally looks fine, but I would change it so that
> only
> > > >> "[X]
> > >  Community building" is checked.  My current comment from the wiki
> > > still
> > >  holds "Activity on list is picking up over the slack
> > conversations.  A
> > >  community member is planning to write a report, however it
> > indicates a
> > >  corporate hierarchy issue within the project that needs to get
> > > solved."
> > > 
> > >  Basically what that second sentence means is that we shouldn't be
> > > >> reliant
> > >  on one person to do the report.
> > > >>>
> > > >>>Trust me, I am fully willing to share in the “fun” for the
> > next
> > > >>> report. *)
> > > >>>
> > > >>>—Tom
> > > >>>
> > > >>>
> > > 
> > >  John
> > > 
> > >  On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <
> > tnadeaua...@gmail.com>
> > > >>> wrote:
> > > 
> > > >
> > > >
> > > >   The AriaTosca report was submitted last Thursday (at least
> > made
> > > > available) and is available here:
> > > >
> > > >
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > >>> Podling+Report+2017-DEC-12
> > > > <
> > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > >>> Podling+Report+2017-DEC-12
> > > >>
> > > >
> > > >   I was not made aware of any special process for submitting
> > this
> > > > other than letting everyone know on the
> > > > mailer that it was 

Re: [DRAFT] Incubator PMC Board Report - December 2017

[John D. Ament]

I went ahead and posted the report to the incubator wiki.  Please review:
https://wiki.apache.org/incubator/December2017

I did make a few changes and ommissions.  Most importantly, we don't
predict graduation dates.  I'm also a bit concerned with the preference of
the grooming meetings over on list communication.

John

On Tue, Dec 12, 2017 at 8:23 AM Suneel Marthi  wrote:

> I have not had a chance to review the draft - given that we are late on the
> report I would prefer filing an updated report next month.
> Meanwhile can we get a release out before the holidays kick in.
>
> Suneel
>
> On Tue, Dec 12, 2017 at 6:24 AM, Thomas Nadeau 
> wrote:
>
> >
> > I am confused - and have asked about what the specific process is
> > for this. All
> > I was told by Suneel when I asked, was to post up a G doc for people to
> > hack/review
> > together.  I have no idea what happens post that, so that is all I’ve
> done.
> >
> > So to answer your question, the doc on the wiki is the final one.
> > No one has
> > submitted any comments since I posted it there last Thursday.
> >
> > —Tom
> >
> >
> > > On Dec 11, 2017, at 9:32 PM, John D. Ament 
> > wrote:
> > >
> > > So, I'm a bit confused as far as next steps.
> > >
> > > Is the report posted at
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > Podling+Report+2017-DEC-12
> > > the
> > > report we are saying should be submitted for the podling?  And are you
> > > looking for me to post it on the incubator wiki?
> > >
> > > John
> > >
> > > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> > >
> > >> There actually was some in-person conversation between committers
> about
> > the
> > >> report. But it's a good criticism -- we should make it explicitly open
> > and
> > >> via the mailing list.
> > >>
> > >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau  >
> > >> wrote:
> > >>
> > >>>
> > >>>
> >  On Dec 11, 2017, at 9:36 AM, John D. Ament 
> > >>> wrote:
> > 
> >  The typical steps a podling would take:
> > 
> >  - Post a report on a common ground (e.g. email, confluence, or
> other)
> >  - Let others know where it is
> >  - Discuss it and get others to contribute into it
> >  - When the report comes through, post it on the incubator wiki, e.g.
> >  https://wiki.apache.org/incubator/December2017 (link changes each
> > >> month)
> > 
> >  The report generally looks fine, but I would change it so that only
> > >> "[X]
> >  Community building" is checked.  My current comment from the wiki
> > still
> >  holds "Activity on list is picking up over the slack
> conversations.  A
> >  community member is planning to write a report, however it
> indicates a
> >  corporate hierarchy issue within the project that needs to get
> > solved."
> > 
> >  Basically what that second sentence means is that we shouldn't be
> > >> reliant
> >  on one person to do the report.
> > >>>
> > >>>Trust me, I am fully willing to share in the “fun” for the
> next
> > >>> report. *)
> > >>>
> > >>>—Tom
> > >>>
> > >>>
> > 
> >  John
> > 
> >  On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <
> tnadeaua...@gmail.com>
> > >>> wrote:
> > 
> > >
> > >
> > >   The AriaTosca report was submitted last Thursday (at least
> made
> > > available) and is available here:
> > >
> > >
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > >>> Podling+Report+2017-DEC-12
> > > <
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > >>> Podling+Report+2017-DEC-12
> > >>
> > >
> > >   I was not made aware of any special process for submitting
> this
> > > other than letting everyone know on the
> > > mailer that it was being created and where it was in case folks
> > wanted
> > >>> to
> > > comment. If there is anything
> > > else needed for this let me know.
> > >
> > >   —Tom
> > >
> > >
> > >> On Dec 10, 2017, at 9:36 AM, John D. Ament  >
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Below is the current draft of our report.  As of now, we have 5
> > >> reports
> > >> missing and 4 reports not signed off on.  I hope we can get that
> > >>> resolved
> > >> in the next few days.  I have copied those podlings impacted.
> > >>
> > >> Incubator PMC report for December 2017
> > >>
> > >> The Apache Incubator is the entry path into the ASF for projects
> and
> > >> codebases wishing to become part of the Foundation's efforts.
> > >>
> > >> There are currently 53 podlings incubating.  In the month of
> > >> November,
> > >>> we
> > >> executed six releases, added one IPMC member and received the
> > >>> resignation
> > >> of another (which is in 

Re: Node Template Substitution

[Tal Liron]

There is currently no clear timeline. I expect it would take several weeks,
perhaps months, unless more contributors step up to assist the effort.

On Tue, Dec 12, 2017 at 5:00 AM, D Jayachandran  wrote:

> Hi,
>
> When can we expect the support for substitution mapping to be merged to
> master branch ?
>
> Regards,
> DJ
> -Original Message-
> From: Steve Baillargeon [mailto:steve.baillarg...@ericsson.com]
> Sent: Friday, December 08, 2017 8:26 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Node Template Substitution
>
> Hi Avia
> I don't access to the design doc. Am I missing something?
>
> Will 0.2.0 support YAML Profile 1.0 or 1.2 topology substitution?
> Or is it postponed to later?
>
> -Steve
>
> -Original Message-
> From: Avia Efrat [mailto:a...@cloudify.co]
> Sent: Tuesday, October 17, 2017 4:44 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Node Template Substitution
>
> There are plans to extend substitution mappings support to TOSCA 1.2, just
> as any other change/improvement in the 1.2 profile.
>
> A CSAR with one 'main' service template and other service templates will
> be stored as one service template, and will have one unique name.
>
> The design doc:
> https://drive.google.com/open?id=19nPjSj6mJyXWd4KLxPqRNp_
> TPqLpvXjzj98NXrAmcjc
>
>
> Additional v1.2 issues (a non-exhaustive list):
> https://docs.google.com/document/d/18yZC8qIWMbWBeULOzmLTT_
> oVrZXQ3z4030U6JIXdJ84/edit
>
>
> On Sat, Oct 14, 2017 at 2:10 AM, Steve Baillargeon <
> steve.baillarg...@ericsson.com> wrote:
>
> > Hi Avia
> > One more question.
> >
> > Say we have a CSAR that contains multiple TOSCA YAML files e.g. a
> > top-level ST and a bunch of low-level STs.
> > I am assuming all those TOSCA service templates (all of them have a
> > full topology section) will be stored as a single “service-template”
> > in ARIA and a single unique name is needed to represent such single
> “service-template”
> > composed of multiple topologies.
> > Is this correct?
> >
> > -Steve
> >
> > -Original Message-
> > From: Steve Baillargeon
> > Sent: Wednesday, October 11, 2017 11:29 AM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: RE: Node Template Substitution
> >
> > Hi Avia
> > Is it possible to review the design documentation for it?
> > Do you have a doc or a few notes describing how ARIA will perform
> > "best matching" based on YAML 1.0/1.1 profile?
> >
> > The full support for NFV Profile 1.0 requires Node Template
> > Substitution defined in YAML 1.2 profile.
> > Any future plans for ARIA to extend Node Template Substitution as
> > defined in YAML 1.2 profile ?
> >
> > Regards
> > Steve B
> >
> > -Original Message-
> > From: Arthur Berezin [mailto:art...@cloudify.co]
> > Sent: Tuesday, October 10, 2017 12:20 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: Node Template Substitution
> >
> > Avia, can you please post a link to the design?  thanks
> >
> > On Mon, Oct 9, 2017 at 5:14 PM Avia Efrat  wrote:
> >
> > > Currently the design is finished, and it is on a small hold for now.
> > > The plan is to support the 1.0/1.1 profile.
> > >
> > > On Wed, Oct 4, 2017 at 7:50 PM, Steve Baillargeon <
> > > steve.baillarg...@ericsson.com> wrote:
> > >
> > > > Hi
> > > > Can we have a status update on the availability of the Node
> > > > Template Substitution feature (aka substitution mappings)?
> > > > Will it support the "capabilities" defined in YAML Profile 1.0 or
> > > > YAML Profile 1.2?
> > > >
> > > > Regards
> > > > Steve B
> > > >
> > > >
> > >
> >
>

Re: Loading Custom Workflows from CSAR

[Tal Liron]

This is indeed the situation right now, but we're unhappy with it and it
may be improved soon.

On Fri, Dec 8, 2017 at 12:05 AM, Vaishnavi K.R 
wrote:

> Hi Tal,
>
>
> The loading of the python modules with python functions for workflows
> happens when the module is in PYTHONPATH.
>
> But I could also see that, the absolute path of the resource storage with
> the service template ID is added to sys.path to make it available for
> python.
>
> This facilitates the loading of modules from CSAR, provided the modules
> are present in the root directory of the CSAR.
>
> Am I right?
>
>
> Thanks,
>
> /Vaish
>
> 
> From: Tal Liron 
> Sent: Thursday, December 7, 2017 8:51:49 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Loading Custom Workflows from CSAR
>
> Actually, the current implementation does not use the CSAR: it expects that
> the Python function (decorated by @workflow) would be somewhere in the
> Python path, and we are currently missing a CSAR code-loading mechanism.
>
> We do not expect the @workflow function structure to change in any way, so
> I think you can feel confident about writing custom workflows in this
> matter. What might change slightly in the near future is how to package the
> .py file.
>
>
> On Thu, Dec 7, 2017 at 2:57 PM, Steve Baillargeon <
> steve.baillarg...@ericsson.com> wrote:
>
> > Hi
> > While the investigation is on-going, I need to double check what can be
> > done today.
> > But I guess how it is done today might change as well (?)
> > Based on our analysis of the latest code base, the loading of the custom
> > workflows today is from CSAR only.
> > Please advise.
> >
> > -Steve
> >
> > -Original Message-
> > From: Tal Liron [mailto:t...@cloudify.co]
> > Sent: Tuesday, November 28, 2017 2:06 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: Loading Custom Workflows from CSAR
> >
> > Thanks, Steve. We don't have a JIRA for this right now, but we do intend
> > to have a way to include "plugins" in a CSAR and have them automatically
> > installed. A "plugin" is basically a Python extension to ARIA that can be
> > loaded at runtime and contained per service.
> >
> > This is part of our current general work trying to find a good design for
> > plugins generally, and will likely result in a JIRA epic with several
> > issues. At this time, I don't think it's worth created this epic if we
> > don't have a plan.
> >
> > The design will likely be inspired by the plugin design in Cloudify, from
> > which we grabbed our seed code. However, there is room for some
> > re-imagination especially as pertains TOSCA-specific issues.
> >
> > On Tue, Nov 28, 2017 at 1:01 PM, Steve Baillargeon <
> > steve.baillarg...@ericsson.com> wrote:
> >
> > > Hi
> > > As far as I know the implementation string associated with the
> > > aria.Workflow type must call or execute a Python function (using the
> > > dot
> > > notation) that is stored in ARIA, like a plugin.
> > > When will it be possible to refer to  a .py file stored in the CSAR
> > > instead?
> > > Do you have any Jira for this enhancement?
> > >
> > > Regards
> > > Steve B
> > >
> >
>

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Suneel Marthi]

I have not had a chance to review the draft - given that we are late on the
report I would prefer filing an updated report next month.
Meanwhile can we get a release out before the holidays kick in.

Suneel

On Tue, Dec 12, 2017 at 6:24 AM, Thomas Nadeau 
wrote:

>
> I am confused - and have asked about what the specific process is
> for this. All
> I was told by Suneel when I asked, was to post up a G doc for people to
> hack/review
> together.  I have no idea what happens post that, so that is all I’ve done.
>
> So to answer your question, the doc on the wiki is the final one.
> No one has
> submitted any comments since I posted it there last Thursday.
>
> —Tom
>
>
> > On Dec 11, 2017, at 9:32 PM, John D. Ament 
> wrote:
> >
> > So, I'm a bit confused as far as next steps.
> >
> > Is the report posted at
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2017-DEC-12
> > the
> > report we are saying should be submitted for the podling?  And are you
> > looking for me to post it on the incubator wiki?
> >
> > John
> >
> > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> >
> >> There actually was some in-person conversation between committers about
> the
> >> report. But it's a good criticism -- we should make it explicitly open
> and
> >> via the mailing list.
> >>
> >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau 
> >> wrote:
> >>
> >>>
> >>>
>  On Dec 11, 2017, at 9:36 AM, John D. Ament 
> >>> wrote:
> 
>  The typical steps a podling would take:
> 
>  - Post a report on a common ground (e.g. email, confluence, or other)
>  - Let others know where it is
>  - Discuss it and get others to contribute into it
>  - When the report comes through, post it on the incubator wiki, e.g.
>  https://wiki.apache.org/incubator/December2017 (link changes each
> >> month)
> 
>  The report generally looks fine, but I would change it so that only
> >> "[X]
>  Community building" is checked.  My current comment from the wiki
> still
>  holds "Activity on list is picking up over the slack conversations.  A
>  community member is planning to write a report, however it indicates a
>  corporate hierarchy issue within the project that needs to get
> solved."
> 
>  Basically what that second sentence means is that we shouldn't be
> >> reliant
>  on one person to do the report.
> >>>
> >>>Trust me, I am fully willing to share in the “fun” for the next
> >>> report. *)
> >>>
> >>>—Tom
> >>>
> >>>
> 
>  John
> 
>  On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau 
> >>> wrote:
> 
> >
> >
> >   The AriaTosca report was submitted last Thursday (at least made
> > available) and is available here:
> >
> >
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> > <
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> >>
> >
> >   I was not made aware of any special process for submitting this
> > other than letting everyone know on the
> > mailer that it was being created and where it was in case folks
> wanted
> >>> to
> > comment. If there is anything
> > else needed for this let me know.
> >
> >   —Tom
> >
> >
> >> On Dec 10, 2017, at 9:36 AM, John D. Ament 
> > wrote:
> >>
> >> All,
> >>
> >> Below is the current draft of our report.  As of now, we have 5
> >> reports
> >> missing and 4 reports not signed off on.  I hope we can get that
> >>> resolved
> >> in the next few days.  I have copied those podlings impacted.
> >>
> >> Incubator PMC report for December 2017
> >>
> >> The Apache Incubator is the entry path into the ASF for projects and
> >> codebases wishing to become part of the Foundation's efforts.
> >>
> >> There are currently 53 podlings incubating.  In the month of
> >> November,
> >>> we
> >> executed six releases, added one IPMC member and received the
> >>> resignation
> >> of another (which is in flight until their sole podling retires).
> We
> > added
> >> two podlings to our roster, have a few more in the pipeline and have
> >>> one
> >> podling planning to graduate this month.
> >>
> >> * Community
> >>
> >> New IPMC members:
> >>
> >> - Michael Semb Wever
> >>
> >> People who left the IPMC:
> >>
> >> - Upayavira (not processed in LDAP yet)
> >>
> >> * New Podlings
> >>
> >> - Crail
> >> - Service Comb
> >>
> >> * Podlings that failed to report, expected next month
> >>
> >> - Amaterasu - Activity stopped late November
> >> - Aria Tosca
> >> - HTrace - 0 on list activity
> 

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Thomas Nadeau]

Yes, after a minor correction I made to BOTH versions just now, I think it
is fine to go.
Both are identical save some formatting.

--Tom


On Tue, Dec 12, 2017 at 2:30 PM, John D. Ament 
wrote:

> Thomas,
>
> We'll resolve the issues around how and where to draft the report later.
> Can you confirm that the contents of
> https://docs.google.com/document/d/1Yg9J-9WD81UjqvwFoc8wek8628RSLzIEZog
> tVT1HBWg/edit?usp=sharing
> match
> the contents of
> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2017-DEC-12
> and
> I'll get things posted.
>
> John
>
> On Tue, Dec 12, 2017 at 6:25 AM Thomas Nadeau 
> wrote:
>
> >
> > I am confused - and have asked about what the specific process is
> > for this. All
> > I was told by Suneel when I asked, was to post up a G doc for people to
> > hack/review
> > together.  I have no idea what happens post that, so that is all I’ve
> done.
> >
> > So to answer your question, the doc on the wiki is the final one.
> > No one has
> > submitted any comments since I posted it there last Thursday.
> >
> > —Tom
> >
> >
> > > On Dec 11, 2017, at 9:32 PM, John D. Ament 
> > wrote:
> > >
> > > So, I'm a bit confused as far as next steps.
> > >
> > > Is the report posted at
> > >
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2017-DEC-12
> > > the
> > > report we are saying should be submitted for the podling?  And are you
> > > looking for me to post it on the incubator wiki?
> > >
> > > John
> > >
> > > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> > >
> > >> There actually was some in-person conversation between committers
> about
> > the
> > >> report. But it's a good criticism -- we should make it explicitly open
> > and
> > >> via the mailing list.
> > >>
> > >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau  >
> > >> wrote:
> > >>
> > >>>
> > >>>
> >  On Dec 11, 2017, at 9:36 AM, John D. Ament 
> > >>> wrote:
> > 
> >  The typical steps a podling would take:
> > 
> >  - Post a report on a common ground (e.g. email, confluence, or
> other)
> >  - Let others know where it is
> >  - Discuss it and get others to contribute into it
> >  - When the report comes through, post it on the incubator wiki, e.g.
> >  https://wiki.apache.org/incubator/December2017 (link changes each
> > >> month)
> > 
> >  The report generally looks fine, but I would change it so that only
> > >> "[X]
> >  Community building" is checked.  My current comment from the wiki
> > still
> >  holds "Activity on list is picking up over the slack
> conversations.  A
> >  community member is planning to write a report, however it
> indicates a
> >  corporate hierarchy issue within the project that needs to get
> > solved."
> > 
> >  Basically what that second sentence means is that we shouldn't be
> > >> reliant
> >  on one person to do the report.
> > >>>
> > >>>Trust me, I am fully willing to share in the “fun” for the
> next
> > >>> report. *)
> > >>>
> > >>>—Tom
> > >>>
> > >>>
> > 
> >  John
> > 
> >  On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau <
> tnadeaua...@gmail.com>
> > >>> wrote:
> > 
> > >
> > >
> > >   The AriaTosca report was submitted last Thursday (at least
> made
> > > available) and is available here:
> > >
> > >
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > >>> Podling+Report+2017-DEC-12
> > > <
> > > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > >>> Podling+Report+2017-DEC-12
> > >>
> > >
> > >   I was not made aware of any special process for submitting
> this
> > > other than letting everyone know on the
> > > mailer that it was being created and where it was in case folks
> > wanted
> > >>> to
> > > comment. If there is anything
> > > else needed for this let me know.
> > >
> > >   —Tom
> > >
> > >
> > >> On Dec 10, 2017, at 9:36 AM, John D. Ament  >
> > > wrote:
> > >>
> > >> All,
> > >>
> > >> Below is the current draft of our report.  As of now, we have 5
> > >> reports
> > >> missing and 4 reports not signed off on.  I hope we can get that
> > >>> resolved
> > >> in the next few days.  I have copied those podlings impacted.
> > >>
> > >> Incubator PMC report for December 2017
> > >>
> > >> The Apache Incubator is the entry path into the ASF for projects
> and
> > >> codebases wishing to become part of the Foundation's efforts.
> > >>
> > >> There are currently 53 podlings incubating.  In the month of
> > >> November,
> > >>> we
> > >> executed six releases, added one IPMC member and received the
> > >>> resignation
> > >> of another (which is in flight until 

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Thomas Nadeau]

Yes, the version on the wiki is the final version. I just updated it a
little as I noticed I missed correcting the committers/PMC note at the end.

As far as posting on the incubator wiki, I have no idea. Is that where the
final version must reside and if so, am I allowed to push it there
or do I need one of the mentors to do so?  If I can do it, let me know and
I will push it there asap.

--Tom


On Tue, Dec 12, 2017 at 4:32 AM, John D. Ament 
wrote:

> So, I'm a bit confused as far as next steps.
>
> Is the report posted at
> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> Podling+Report+2017-DEC-12
> the
> report we are saying should be submitted for the podling?  And are you
> looking for me to post it on the incubator wiki?
>
> John
>
> On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
>
> > There actually was some in-person conversation between committers about
> the
> > report. But it's a good criticism -- we should make it explicitly open
> and
> > via the mailing list.
> >
> > On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau 
> > wrote:
> >
> > >
> > >
> > > > On Dec 11, 2017, at 9:36 AM, John D. Ament 
> > > wrote:
> > > >
> > > > The typical steps a podling would take:
> > > >
> > > > - Post a report on a common ground (e.g. email, confluence, or other)
> > > > - Let others know where it is
> > > > - Discuss it and get others to contribute into it
> > > > - When the report comes through, post it on the incubator wiki, e.g.
> > > > https://wiki.apache.org/incubator/December2017 (link changes each
> > month)
> > > >
> > > > The report generally looks fine, but I would change it so that only
> > "[X]
> > > > Community building" is checked.  My current comment from the wiki
> still
> > > > holds "Activity on list is picking up over the slack conversations.
> A
> > > > community member is planning to write a report, however it indicates
> a
> > > > corporate hierarchy issue within the project that needs to get
> solved."
> > > >
> > > > Basically what that second sentence means is that we shouldn't be
> > reliant
> > > > on one person to do the report.
> > >
> > > Trust me, I am fully willing to share in the “fun” for the next
> > > report. *)
> > >
> > > —Tom
> > >
> > >
> > > >
> > > > John
> > > >
> > > > On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau  >
> > > wrote:
> > > >
> > > >>
> > > >>
> > > >>The AriaTosca report was submitted last Thursday (at least
> made
> > > >> available) and is available here:
> > > >>
> > > >>
> > > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > Podling+Report+2017-DEC-12
> > > >> <
> > > >> https://cwiki.apache.org/confluence/display/ARIATOSCA/
> > > Podling+Report+2017-DEC-12
> > > >>>
> > > >>
> > > >>I was not made aware of any special process for submitting
> this
> > > >> other than letting everyone know on the
> > > >> mailer that it was being created and where it was in case folks
> wanted
> > > to
> > > >> comment. If there is anything
> > > >> else needed for this let me know.
> > > >>
> > > >>—Tom
> > > >>
> > > >>
> > > >>> On Dec 10, 2017, at 9:36 AM, John D. Ament 
> > > >> wrote:
> > > >>>
> > > >>> All,
> > > >>>
> > > >>> Below is the current draft of our report.  As of now, we have 5
> > reports
> > > >>> missing and 4 reports not signed off on.  I hope we can get that
> > > resolved
> > > >>> in the next few days.  I have copied those podlings impacted.
> > > >>>
> > > >>> Incubator PMC report for December 2017
> > > >>>
> > > >>> The Apache Incubator is the entry path into the ASF for projects
> and
> > > >>> codebases wishing to become part of the Foundation's efforts.
> > > >>>
> > > >>> There are currently 53 podlings incubating.  In the month of
> > November,
> > > we
> > > >>> executed six releases, added one IPMC member and received the
> > > resignation
> > > >>> of another (which is in flight until their sole podling retires).
> We
> > > >> added
> > > >>> two podlings to our roster, have a few more in the pipeline and
> have
> > > one
> > > >>> podling planning to graduate this month.
> > > >>>
> > > >>> * Community
> > > >>>
> > > >>> New IPMC members:
> > > >>>
> > > >>> - Michael Semb Wever
> > > >>>
> > > >>> People who left the IPMC:
> > > >>>
> > > >>> - Upayavira (not processed in LDAP yet)
> > > >>>
> > > >>> * New Podlings
> > > >>>
> > > >>> - Crail
> > > >>> - Service Comb
> > > >>>
> > > >>> * Podlings that failed to report, expected next month
> > > >>>
> > > >>> - Amaterasu - Activity stopped late November
> > > >>> - Aria Tosca
> > > >>> - HTrace - 0 on list activity
> > > >>> - Pony Mail - Low activity, suspect just missed.
> > > >>> - Wave - Retiring
> > > >>>
> > > >>> * Podlings Missing sign off
> > > >>>
> > > >>> - Griffin
> > > >>> - Myriad
> > > >>> - OpenWhisk
> > > >>> - Spot
> > > >>>
> > > >>> * Graduations
> > > >>>

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Thomas Nadeau]

> On Dec 11, 2017, at 9:36 AM, John D. Ament  wrote:
> 
> The typical steps a podling would take:
> 
> - Post a report on a common ground (e.g. email, confluence, or other)
> - Let others know where it is
> - Discuss it and get others to contribute into it
> - When the report comes through, post it on the incubator wiki, e.g.
> https://wiki.apache.org/incubator/December2017 (link changes each month)
> 
> The report generally looks fine, but I would change it so that only "[X]
> Community building" is checked.  My current comment from the wiki still
> holds "Activity on list is picking up over the slack conversations.  A
> community member is planning to write a report, however it indicates a
> corporate hierarchy issue within the project that needs to get solved."
> 
> Basically what that second sentence means is that we shouldn't be reliant
> on one person to do the report.

Understood. Ill definitely pass the release baton for the next release 
as well
as the podling report.

—Tom


> 
> John
> 
> On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau  wrote:
> 
>> 
>> 
>>The AriaTosca report was submitted last Thursday (at least made
>> available) and is available here:
>> 
>> 
>> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
>> <
>> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
>>> 
>> 
>>I was not made aware of any special process for submitting this
>> other than letting everyone know on the
>> mailer that it was being created and where it was in case folks wanted to
>> comment. If there is anything
>> else needed for this let me know.
>> 
>>—Tom
>> 
>> 
>>> On Dec 10, 2017, at 9:36 AM, John D. Ament 
>> wrote:
>>> 
>>> All,
>>> 
>>> Below is the current draft of our report.  As of now, we have 5 reports
>>> missing and 4 reports not signed off on.  I hope we can get that resolved
>>> in the next few days.  I have copied those podlings impacted.
>>> 
>>> Incubator PMC report for December 2017
>>> 
>>> The Apache Incubator is the entry path into the ASF for projects and
>>> codebases wishing to become part of the Foundation's efforts.
>>> 
>>> There are currently 53 podlings incubating.  In the month of November, we
>>> executed six releases, added one IPMC member and received the resignation
>>> of another (which is in flight until their sole podling retires).  We
>> added
>>> two podlings to our roster, have a few more in the pipeline and have one
>>> podling planning to graduate this month.
>>> 
>>> * Community
>>> 
>>> New IPMC members:
>>> 
>>> - Michael Semb Wever
>>> 
>>> People who left the IPMC:
>>> 
>>> - Upayavira (not processed in LDAP yet)
>>> 
>>> * New Podlings
>>> 
>>> - Crail
>>> - Service Comb
>>> 
>>> * Podlings that failed to report, expected next month
>>> 
>>> - Amaterasu - Activity stopped late November
>>> - Aria Tosca
>>> - HTrace - 0 on list activity
>>> - Pony Mail - Low activity, suspect just missed.
>>> - Wave - Retiring
>>> 
>>> * Podlings Missing sign off
>>> 
>>> - Griffin
>>> - Myriad
>>> - OpenWhisk
>>> - Spot
>>> 
>>> * Graduations
>>> 
>>> The board has motions for the following:
>>> 
>>> - Trafodion
>>> - Your podling here?
>>> - Your podling here?
>>> 
>>> * Releases
>>> 
>>> The following releases entered distribution during the month of
>>> November:
>>> 
>>> - 2017-11-01 Apache Freemarker  2.3.27
>>> - 2017-11-08 Apache Netbeans HTML4J 1.5
>>> - 2017-11-15 Apache Mnemonic0.10.0
>>> - 2017-11-15 Apache MXNet   0.12.1
>>> - 2017-11-18 Apache Netbeans HTML4J 1.5.1
>>> - 2017-11-28 Apache Griffin 0.1.6
>>> 
>>> * IP Clearance
>>> 
>>> 
>>> 
>>> * Legal / Trademarks
>>> 
>>> 
>>> 
>>> * Infrastructure
>>> 
>>> 
>>> 
>>> * Miscellaneous
>>> 
>>> 
>>> 
>>> * Credits
>>> 
>>> --
>>>  Table of Contents
>>> Amaterasu
>>> AriaTosca
>>> Crail
>>> Daffodil
>>> Gearpump
>>> Griffin
>>> Hivemall
>>> HTrace
>>> Myriad
>>> Omid
>>> OpenWhisk
>>> PageSpeed
>>> Pony Mail
>>> Pulsar
>>> Quickstep
>>> SAMOA
>>> SDAP
>>> SINGA
>>> Spot
>>> Superset
>>> Taverna
>>> Tephra
>>> Trafodion
>>> Wave
>>> 
>>> --
>>> 
>>> 
>>> Amaterasu
>>> 
>>> Apache Amaterasu is a framework providing continuous deployment for Big
>> Data
>>> pipelines.
>>> 
>>> Amaterasu has been incubating since 2017-09-07.
>>> 
>>> Three most important issues to address in the move towards graduation:
>>> 
>>> 1.
>>> 2.
>>> 3.
>>> 
>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>>> aware of?
>>> 
>>> 
>>> 
>>> How has the community developed since the last report?
>>> 
>>> 
>>> 
>>> How has the project developed since the last report?
>>> 
>>> 
>>> How would you assess the podling's maturity?
>>> Please feel free to add 

Re: [DRAFT] Incubator PMC Board Report - December 2017

[John D. Ament]

Thomas,

We'll resolve the issues around how and where to draft the report later.
Can you confirm that the contents of
https://docs.google.com/document/d/1Yg9J-9WD81UjqvwFoc8wek8628RSLzIEZogtVT1HBWg/edit?usp=sharing
match
the contents of
https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
and
I'll get things posted.

John

On Tue, Dec 12, 2017 at 6:25 AM Thomas Nadeau 
wrote:

>
> I am confused - and have asked about what the specific process is
> for this. All
> I was told by Suneel when I asked, was to post up a G doc for people to
> hack/review
> together.  I have no idea what happens post that, so that is all I’ve done.
>
> So to answer your question, the doc on the wiki is the final one.
> No one has
> submitted any comments since I posted it there last Thursday.
>
> —Tom
>
>
> > On Dec 11, 2017, at 9:32 PM, John D. Ament 
> wrote:
> >
> > So, I'm a bit confused as far as next steps.
> >
> > Is the report posted at
> >
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
> > the
> > report we are saying should be submitted for the podling?  And are you
> > looking for me to post it on the incubator wiki?
> >
> > John
> >
> > On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> >
> >> There actually was some in-person conversation between committers about
> the
> >> report. But it's a good criticism -- we should make it explicitly open
> and
> >> via the mailing list.
> >>
> >> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau 
> >> wrote:
> >>
> >>>
> >>>
>  On Dec 11, 2017, at 9:36 AM, John D. Ament 
> >>> wrote:
> 
>  The typical steps a podling would take:
> 
>  - Post a report on a common ground (e.g. email, confluence, or other)
>  - Let others know where it is
>  - Discuss it and get others to contribute into it
>  - When the report comes through, post it on the incubator wiki, e.g.
>  https://wiki.apache.org/incubator/December2017 (link changes each
> >> month)
> 
>  The report generally looks fine, but I would change it so that only
> >> "[X]
>  Community building" is checked.  My current comment from the wiki
> still
>  holds "Activity on list is picking up over the slack conversations.  A
>  community member is planning to write a report, however it indicates a
>  corporate hierarchy issue within the project that needs to get
> solved."
> 
>  Basically what that second sentence means is that we shouldn't be
> >> reliant
>  on one person to do the report.
> >>>
> >>>Trust me, I am fully willing to share in the “fun” for the next
> >>> report. *)
> >>>
> >>>—Tom
> >>>
> >>>
> 
>  John
> 
>  On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau 
> >>> wrote:
> 
> >
> >
> >   The AriaTosca report was submitted last Thursday (at least made
> > available) and is available here:
> >
> >
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> > <
> > https://cwiki.apache.org/confluence/display/ARIATOSCA/
> >>> Podling+Report+2017-DEC-12
> >>
> >
> >   I was not made aware of any special process for submitting this
> > other than letting everyone know on the
> > mailer that it was being created and where it was in case folks
> wanted
> >>> to
> > comment. If there is anything
> > else needed for this let me know.
> >
> >   —Tom
> >
> >
> >> On Dec 10, 2017, at 9:36 AM, John D. Ament 
> > wrote:
> >>
> >> All,
> >>
> >> Below is the current draft of our report.  As of now, we have 5
> >> reports
> >> missing and 4 reports not signed off on.  I hope we can get that
> >>> resolved
> >> in the next few days.  I have copied those podlings impacted.
> >>
> >> Incubator PMC report for December 2017
> >>
> >> The Apache Incubator is the entry path into the ASF for projects and
> >> codebases wishing to become part of the Foundation's efforts.
> >>
> >> There are currently 53 podlings incubating.  In the month of
> >> November,
> >>> we
> >> executed six releases, added one IPMC member and received the
> >>> resignation
> >> of another (which is in flight until their sole podling retires).
> We
> > added
> >> two podlings to our roster, have a few more in the pipeline and have
> >>> one
> >> podling planning to graduate this month.
> >>
> >> * Community
> >>
> >> New IPMC members:
> >>
> >> - Michael Semb Wever
> >>
> >> People who left the IPMC:
> >>
> >> - Upayavira (not processed in LDAP yet)
> >>
> >> * New Podlings
> >>
> >> - Crail
> >> - Service Comb
> >>
> >> * Podlings that failed to report, 

Re: [DRAFT] Incubator PMC Board Report - December 2017

[Thomas Nadeau]

I am confused - and have asked about what the specific process is for 
this. All
I was told by Suneel when I asked, was to post up a G doc for people to 
hack/review
together.  I have no idea what happens post that, so that is all I’ve done. 

So to answer your question, the doc on the wiki is the final one. No 
one has
submitted any comments since I posted it there last Thursday.

—Tom


> On Dec 11, 2017, at 9:32 PM, John D. Ament  wrote:
> 
> So, I'm a bit confused as far as next steps.
> 
> Is the report posted at
> https://cwiki.apache.org/confluence/display/ARIATOSCA/Podling+Report+2017-DEC-12
> the
> report we are saying should be submitted for the podling?  And are you
> looking for me to post it on the incubator wiki?
> 
> John
> 
> On Mon, Dec 11, 2017 at 9:43 AM Tal Liron  wrote:
> 
>> There actually was some in-person conversation between committers about the
>> report. But it's a good criticism -- we should make it explicitly open and
>> via the mailing list.
>> 
>> On Mon, Dec 11, 2017 at 8:39 AM, Thomas Nadeau 
>> wrote:
>> 
>>> 
>>> 
 On Dec 11, 2017, at 9:36 AM, John D. Ament 
>>> wrote:
 
 The typical steps a podling would take:
 
 - Post a report on a common ground (e.g. email, confluence, or other)
 - Let others know where it is
 - Discuss it and get others to contribute into it
 - When the report comes through, post it on the incubator wiki, e.g.
 https://wiki.apache.org/incubator/December2017 (link changes each
>> month)
 
 The report generally looks fine, but I would change it so that only
>> "[X]
 Community building" is checked.  My current comment from the wiki still
 holds "Activity on list is picking up over the slack conversations.  A
 community member is planning to write a report, however it indicates a
 corporate hierarchy issue within the project that needs to get solved."
 
 Basically what that second sentence means is that we shouldn't be
>> reliant
 on one person to do the report.
>>> 
>>>Trust me, I am fully willing to share in the “fun” for the next
>>> report. *)
>>> 
>>>—Tom
>>> 
>>> 
 
 John
 
 On Mon, Dec 11, 2017 at 9:05 AM Thomas Nadeau 
>>> wrote:
 
> 
> 
>   The AriaTosca report was submitted last Thursday (at least made
> available) and is available here:
> 
> 
> https://cwiki.apache.org/confluence/display/ARIATOSCA/
>>> Podling+Report+2017-DEC-12
> <
> https://cwiki.apache.org/confluence/display/ARIATOSCA/
>>> Podling+Report+2017-DEC-12
>> 
> 
>   I was not made aware of any special process for submitting this
> other than letting everyone know on the
> mailer that it was being created and where it was in case folks wanted
>>> to
> comment. If there is anything
> else needed for this let me know.
> 
>   —Tom
> 
> 
>> On Dec 10, 2017, at 9:36 AM, John D. Ament 
> wrote:
>> 
>> All,
>> 
>> Below is the current draft of our report.  As of now, we have 5
>> reports
>> missing and 4 reports not signed off on.  I hope we can get that
>>> resolved
>> in the next few days.  I have copied those podlings impacted.
>> 
>> Incubator PMC report for December 2017
>> 
>> The Apache Incubator is the entry path into the ASF for projects and
>> codebases wishing to become part of the Foundation's efforts.
>> 
>> There are currently 53 podlings incubating.  In the month of
>> November,
>>> we
>> executed six releases, added one IPMC member and received the
>>> resignation
>> of another (which is in flight until their sole podling retires).  We
> added
>> two podlings to our roster, have a few more in the pipeline and have
>>> one
>> podling planning to graduate this month.
>> 
>> * Community
>> 
>> New IPMC members:
>> 
>> - Michael Semb Wever
>> 
>> People who left the IPMC:
>> 
>> - Upayavira (not processed in LDAP yet)
>> 
>> * New Podlings
>> 
>> - Crail
>> - Service Comb
>> 
>> * Podlings that failed to report, expected next month
>> 
>> - Amaterasu - Activity stopped late November
>> - Aria Tosca
>> - HTrace - 0 on list activity
>> - Pony Mail - Low activity, suspect just missed.
>> - Wave - Retiring
>> 
>> * Podlings Missing sign off
>> 
>> - Griffin
>> - Myriad
>> - OpenWhisk
>> - Spot
>> 
>> * Graduations
>> 
>> The board has motions for the following:
>> 
>> - Trafodion
>> - Your podling here?
>> - Your podling here?
>> 
>> * Releases
>> 
>> The following releases entered distribution during the month of
>> November:
>> 
>> - 2017-11-01 Apache Freemarker  

Re: pip executable expected as part of plugin install.

[Vaishnavi K . R]

Hi,


In ARIA, the pip executable path is used to get the output of the 'pip freeze' 
command. This lists the installed packages in the local system. This list is 
written to a file and passed as a constraint to the 'pip install' command used 
by wagon.


At times, the installation directory changes and so the pip executable path. 
This creates problem in our systems and we need to handle the installation of 
pip exclusively. So it would be good to use the pip library instead of the 
executable path.


I tried using the pip library inplace of the 'pip executable path' to get the 
list of installed packages. The pip library for freeze does not return anything 
but rather prints the output to the 'stdout'. So the stdout needs to be 
redirected and stored in a variable.


Is redirecting stdout recommended?


With my current understanding on the utilities provided by pip, this is the 
available option to use the pip library instead of the pip executable.


Thanks,

/Vaish


From: Vaishnavi K.R 
Sent: Friday, December 8, 2017 11:47:21 AM
To: dev@ariatosca.incubator.apache.org
Subject: Re: pip executable expected as part of plugin install.

Hi,


There is no change with regards to this in the latest code base.

The following is the error that we get when the pip executable is not found.


Validating plugin /root/testplugin-1.0-py27-none-any.wgn...

Plugin validated successfully

Installing plugin /root/testplugin-1.0-py27-none-any.wgn...

Retrieving source...

Extracting zip /root/testplugin-1.0-py27-none-any.wgn to /tmp/tmp3Q0BL2...

Source is: /tmp/tmp3Q0BL2/testplugin

[Errno 2] No such file or directory



Thanks,

/Vaish


From: Thomas Nadeau 
Sent: Sunday, December 3, 2017 2:57:22 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: pip executable expected as part of plugin install.

DJ,

If when you take a look at this, you find that it fails, please send
detailed log/output
so we can figure this out.  I don’t see any of that from the thread below.

Thx,

—Tom


On Sun, Dec 3, 2017 at 11:22 AM, Tal Liron  wrote:

> Hi DJ,
>
> A lot has changed since August. :) I wonder if you can take a look at the
> current state of master and see if things have improved with wagon
> installs?
>
> On Fri, Dec 1, 2017 at 9:22 AM, D Jayachandran <
> d.jayachand...@ericsson.com>
> wrote:
>
> > Hi Ran,
> >
> > Sorry I had missed to answer this thread. Just to answer your question
> > wagon also expects pip as a binary "/usr/bin/pip".  The above path may
> not
> > be the same for al distros of linux and when the path varies we run into
> > the issue/
> > As I already told we could probably fix this issue by using pip as
> library
> > instead of a 3PP.
> > Please let me know if we can also apply the same fix with wagon as well.
> >
> > Regards,
> > DJ
> > -Original Message-
> > From: Ran Ziv [mailto:r...@cloudify.co]
> > Sent: Sunday, August 20, 2017 12:40 PM
> > To: dev@ariatosca.incubator.apache.org
> > Subject: Re: pip executable expected as part of plugin install.
> >
> > Can you try to explain again what's the issue you're seeing with the way
> > Wagon works right now?
> > We could create a pull request for Wagon as well, but I'm not sure I
> > understand the problem at the moment.
> >
> > On Wed, Aug 16, 2017 at 6:04 PM, D Jayachandran <
> > d.jayachand...@ericsson.com
> > > wrote:
> >
> > > Even if we fix the issue in ARIA. Wagon library still uses the same
> > > logic in finding the pip path and it is wrong.
> > > Am not sure how to fix this with wagon.
> > >
> > > Regards,
> > > DJ
> > > -Original Message-
> > > From: D Jayachandran [mailto:d.jayachand...@ericsson.com]
> > > Sent: Thursday, August 03, 2017 5:00 PM
> > > To: dev@ariatosca.incubator.apache.org
> > > Subject: RE: pip executable expected as part of plugin install.
> > >
> > > Thanks Avia, I will open an issue.
> > >
> > > Regards,
> > > DJ
> > >
> > > -Original Message-
> > > From: Avia Efrat [mailto:a...@cloudify.co]
> > > Sent: Thursday, August 03, 2017 4:01 PM
> > > To: dev@ariatosca.incubator.apache.org
> > > Subject: Re: pip executable expected as part of plugin install.
> > >
> > > Hi DJ,
> > > It seems you are correct, I don't see a reason for not using the pip
> > > library.
> > > Maybe it was that way since we didn't want to add pip as a dependency
> > > explicitly (this code is from the beginning of ARIA).
> > >
> > > Feel free to open an issue about that =)
> > >
> > > On Wed, Aug 2, 2017 at 10:19 AM, D Jayachandran <
> > > d.jayachand...@ericsson.com
> > > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Am using a Ubuntu version of linux for my development and ARIA does
> > > > not find the correct path of pip during the plugin install.
> > > > To be precise this happens when pip freeze is executed.
> > > >
> > > > @staticmethod
> > > > def _pip_freeze():
> > > > """Run pip 

RE: Node Template Substitution

[D Jayachandran]

Hi,

When can we expect the support for substitution mapping to be merged to master 
branch ?

Regards,
DJ
-Original Message-
From: Steve Baillargeon [mailto:steve.baillarg...@ericsson.com] 
Sent: Friday, December 08, 2017 8:26 AM
To: dev@ariatosca.incubator.apache.org
Subject: RE: Node Template Substitution

Hi Avia
I don't access to the design doc. Am I missing something?

Will 0.2.0 support YAML Profile 1.0 or 1.2 topology substitution?
Or is it postponed to later?

-Steve

-Original Message-
From: Avia Efrat [mailto:a...@cloudify.co]
Sent: Tuesday, October 17, 2017 4:44 AM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Node Template Substitution

There are plans to extend substitution mappings support to TOSCA 1.2, just as 
any other change/improvement in the 1.2 profile.

A CSAR with one 'main' service template and other service templates will be 
stored as one service template, and will have one unique name.

The design doc:
https://drive.google.com/open?id=19nPjSj6mJyXWd4KLxPqRNp_TPqLpvXjzj98NXrAmcjc


Additional v1.2 issues (a non-exhaustive list):
https://docs.google.com/document/d/18yZC8qIWMbWBeULOzmLTT_oVrZXQ3z4030U6JIXdJ84/edit


On Sat, Oct 14, 2017 at 2:10 AM, Steve Baillargeon < 
steve.baillarg...@ericsson.com> wrote:

> Hi Avia
> One more question.
>
> Say we have a CSAR that contains multiple TOSCA YAML files e.g. a 
> top-level ST and a bunch of low-level STs.
> I am assuming all those TOSCA service templates (all of them have a 
> full topology section) will be stored as a single “service-template”
> in ARIA and a single unique name is needed to represent such single 
> “service-template”
> composed of multiple topologies.
> Is this correct?
>
> -Steve
>
> -Original Message-
> From: Steve Baillargeon
> Sent: Wednesday, October 11, 2017 11:29 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: RE: Node Template Substitution
>
> Hi Avia
> Is it possible to review the design documentation for it?
> Do you have a doc or a few notes describing how ARIA will perform 
> "best matching" based on YAML 1.0/1.1 profile?
>
> The full support for NFV Profile 1.0 requires Node Template 
> Substitution defined in YAML 1.2 profile.
> Any future plans for ARIA to extend Node Template Substitution as 
> defined in YAML 1.2 profile ?
>
> Regards
> Steve B
>
> -Original Message-
> From: Arthur Berezin [mailto:art...@cloudify.co]
> Sent: Tuesday, October 10, 2017 12:20 PM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Node Template Substitution
>
> Avia, can you please post a link to the design?  thanks
>
> On Mon, Oct 9, 2017 at 5:14 PM Avia Efrat  wrote:
>
> > Currently the design is finished, and it is on a small hold for now.
> > The plan is to support the 1.0/1.1 profile.
> >
> > On Wed, Oct 4, 2017 at 7:50 PM, Steve Baillargeon < 
> > steve.baillarg...@ericsson.com> wrote:
> >
> > > Hi
> > > Can we have a status update on the availability of the Node 
> > > Template Substitution feature (aka substitution mappings)?
> > > Will it support the "capabilities" defined in YAML Profile 1.0 or 
> > > YAML Profile 1.2?
> > >
> > > Regards
> > > Steve B
> > >
> > >
> >
>

RE: Free PyCharm license for ARIA work?

[D Jayachandran]

Hi Tal,

Am still facing the issue even after a "make clean" and from a fresh clone. Am 
facing this error only when running the execution in debug mode.
The error is thrown by the pydev plugin, check below for the stack trace. 
Please let me know if you have any clue on this.


warning: Debugger speedups using cython not found. Run 
'"/proj/tosca-o/common/dev_tools/python/bin/python" 
"/proj/tosca-o/common/dev_tools/eclipse_neon_4.6/plugins/org.python.pydev_6.0.0.201709191431/pysrc/setup_cython.py"
 build_ext --inplace' to build.
pydev debugger: starting (pid: 86306)
Starting execution. Press Ctrl+C cancel
Starting 'install' workflow execution
warning: Debugger speedups using cython not found. Run 
'"/proj/tosca-o/common/dev_tools/python/bin/python" 
"/proj/tosca-o/common/dev_tools/eclipse_neon_4.6/plugins/org.python.pydev_6.0.0.201709191431/pysrc/setup_cython.py"
 build_ext --inplace' to build.
pydev debugger: starting (pid: 86343)
Traceback (most recent call last):
  File 
"/proj/tosca-o/common/dev_tools/eclipse_neon_4.6/plugins/org.python.pydev_6.0.0.201709191431/pysrc/pydevd.py",
 line 1621, in 
main()
  File 
"/proj/tosca-o/common/dev_tools/eclipse_neon_4.6/plugins/org.python.pydev_6.0.0.201709191431/pysrc/pydevd.py",
 line 1615, in main
globals = debugger.run(setup['file'], None, None, is_module)
  File 
"/proj/tosca-o/common/dev_tools/eclipse_neon_4.6/plugins/org.python.pydev_6.0.0.201709191431/pysrc/pydevd.py",
 line 1022, in run
pydev_imports.execfile(file, globals, locals)  # execute the script
  File 
"/workarea/tosca-o/evyzzae/incubator-ariatosca/aria/orchestrator/workflows/executor/process.pyc",
 line 1
SyntaxError: Non-ASCII character '\xf3' in file 
/workarea/tosca-o/evyzzae/incubator-ariatosca/aria/orchestrator/workflows/executor/process.pyc
 on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ 
for details

-Original Message-
From: Tal Liron [mailto:t...@cloudify.co] 
Sent: Friday, October 13, 2017 10:05 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Free PyCharm license for ARIA work?

Hm, I don't see any non-ASCII character in the source code. Perhaps try to 
delete all your *.pyc files so that they get regenerated. You can run "make 
clean" in the root directory to do that.

On Fri, Oct 13, 2017 at 3:55 AM, D Jayachandran  wrote:

> Hi Tal,
>
> Am facing an issue with PyDev when I trigger an execution in debug mode.
>
> SyntaxError: Non-ASCII character '\xf3' in file 
> /home/evyzzae/tosca-repo/ 
> apache-aria/aria/orchestrator/workflows/executor/process.pyc on line 
> 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ 
> for details
>
> Are you aware of this ?
>
>
> Regards,
> DJ
>
> -Original Message-
> From: Tal Liron [mailto:t...@cloudify.co]
> Sent: Thursday, October 12, 2017 12:05 AM
> To: dev@ariatosca.incubator.apache.org
> Subject: Re: Free PyCharm license for ARIA work?
>
> I just want to point out that I do all my development with the free 
> PyDev IDE (based on Eclipse) and am very satisfied with it.
>
> On Wed, Oct 11, 2017 at 1:21 PM, Thomas Nadeau 
> 
> wrote:
>
> >
> > Cool. Thanks. It looks like there is a special deal for 
> > Apache
> > projects:
> >
> > You should have @apache.org email to apply Your order will be 
> > processed automatically after the application is submitted
> >
> > The catch-22 is that Vish is not a committer (i.e.: he does 
> > not have an apache.org email), so we might be SOL here.
> >
> > —Tom
> >
> >
> >
> > > On Oct 11, 2017, at 2:17 PM, Jakob Homan  wrote:
> > >
> > > JetBrains kindly provides open source licenses for sustained
> > > contributors: https://www.jetbrains.com/buy/opensource/  They have 
> > > a separate set of Apache requirements.  This is a consideration 
> > > they provide, not something that ASF does.
> > >
> > > -Jakob
> > >
> > > On 11 October 2017 at 11:01, Vishwanath Jayaraman 
> > >  wrote:
> > >> Was curious if there is a free PyCharm license that Apache 
> > >> provides for
> > contributors that contribute to the ARIA project?
> > >>
> > >> When I was contributing to the OpenStack Tacker and Neutron 
> > >> projects, I
> > was able to request such a free license, hence the above question.
> > >>
> > >>
> > >> Vish
> >
> >
>

Re: Loading custom workflows

[Vaishnavi K . R]

Hi,


Do we have any update on the design of the loading mechanism?


Thanks,

/Vaish


From: Tal Liron 
Sent: Thursday, December 7, 2017 8:54:47 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Loading custom workflows

We had some good discussions are are just about ready to make them public
for soliciting feedback.

I will handle it next week and let the mailing list know!

On Thu, Dec 7, 2017 at 2:31 PM, Thomas Nadeau  wrote:

> Do you think it is a good idea to start a document and/or wiki entry for a
> thumbnail sketch of how we want to do this?
>
> --Tom
>
> On Thu, Dec 7, 2017 at 2:04 PM, Tal Liron  wrote:
>
> > Our current idea is to support multiple ways of installing extensions.
> One
> > of them will, of course, be by including them in the CSAR file (which can
> > be done in various ways: Python source code, wheels, wagons, etc.). We
> want
> > to standardize all extensions with a single well-defined entry point.
> >
> > On Wed, Dec 6, 2017 at 4:58 PM, Vaishnavi K.R <
> vaishnavi@ericsson.com>
> > wrote:
> >
> > > Hi Tal,
> > >
> > >
> > > Good that this has been considered.
> > >
> > > As all the three entities are mere python modules, it is good to have a
> > > common loading mechanism.
> > >
> > > But will there be any major change in the existing way of loading
> plugins
> > > and using the same in the service template?
> > >
> > >
> > > Thanks,
> > >
> > > /Vaish
> > >
> > > 
> > > From: Tal Liron 
> > > Sent: Wednesday, December 6, 2017 7:27:02 PM
> > > To: dev@ariatosca.incubator.apache.org
> > > Subject: Re: Loading custom workflows
> > >
> > > Great question, and it was asked very recently on this list ...
> > >
> > > There is a need for a unified way to dynamically load
> > > extensions/plugins/workflows from CSAR files as well as other places.
> We
> > > are trying to come with a good, forward-looking architectural design
> for
> > > this loading mechanism. I will provide an update on this in the next
> few
> > > days.
> > >
> > > On Wed, Dec 6, 2017 at 3:51 PM, Vaishnavi K.R <
> > vaishnavi@ericsson.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > >
> > > > I tried using the custom workflow support provided by ARIA.
> > > >
> > > > In the current ARIA, the custom workflows are directly imported as
> > python
> > > > modules.
> > > >
> > > > It looks like it is loading the python modules that are bundled along
> > > with
> > > > the service template in CSAR.
> > > >
> > > >
> > > > Also I could see that you have plans to load it as how the plugins
> are.
> > > >
> > > > Is anyone working on this?
> > > >
> > > > Will the workflows be packaged as wagon archives and installed?
> > > >
> > > > Will they be referred in the service template with the same
> convention
> > as
> > > > plugins?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > /Vaish
> > > >
> > >
> >
>