It seems we have duplicated efforts here. DeWayne has separately created a
REST layer for the ONAP project.
DeWayne, could you provide more details?
On Wed, Nov 29, 2017 at 11:59 PM, D Jayachandran <
d.jayachand...@ericsson.com> wrote:
> Hi Tal,
>
> For our use case we have already built a REST
The extension repo was built based on Aria 0.1.1 base code. The dependency
is strictly set to 0.1.1 , which kinda make sense since 0.2.0 wasn't (and
still isn't) released. It probably uninstalls the 0.2.0 one and installs
0.1.1 instead, which sound to me as a wanted behavior.
On Thu, Nov 30,
Hi Tal,
For our use case we have already built a REST Layer on top of ARIA for
service-template, services and execution creation/start.
Now for this particular use-case we were looking if we could take the service
model object and create a service context object out of it, to be provided to
This was an explanation I had previously sent to another podling I mentor:
(Merit never expiring) is not a bug. As ASF sees it, this is a feature:
https://www.apache.org/dev/committers.html (search for Merit Never
Expires, an ASF axiom). As a volunteer organization, we cannot
require anyone
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 20 December 2017, 10:30 am PDT.
The report for your podling will
Ah, the dreaded multi-repo problems that I so detest, and am trying to
avoid by having it all in one repo...
The issue is that you are using a newer version of aria-extension-cloudify
than what is supported by aria on PyPI. I suggest keeping the two versions
matching to avoid problems.
On Wed,
I worked around this by installing the cloudify extention using the
--no-deps argument (to pip).
On Wed, Nov 29, 2017 at 2:32 PM, DeWayne Filppi wrote:
> OK. I guess I didn't provide enough context. I installed the ARIA-1
> branch of ARIA in order to pick up a bug fix I
There is one out. When a podling graduates, its customary to keep everyone
on. However, if there are people who are no longer interested in the
project and the project chooses to not include them, its not uncommon that
they be left off the graduation. They would still be open to be included
OK. I guess I didn't provide enough context. I installed the ARIA-1
branch of ARIA in order to pick up a bug fix I needed. When attempting to
install aria-extension-cloudify, it complains that ariatosca 0.2.0 is
installed, and it proceeds to remove it. So, the cloudify extension
deletes ARIA,
I think that is why we were having it - no one knew about Apache’s
rules around this.
That seems to settle the matter: once you are in, you are in.
—Tom
> On Nov 29, 2017, at 3:42 PM, Suneel Marthi wrote:
>
> Fyi... committership never expires in
Fyi... committership never expires in ASF, unless the committer chooses to
go Emeritus. So not sure if this discussion is needed.
On Wed, Nov 29, 2017 at 3:23 PM, Thomas Nadeau
wrote:
>
> One action I took from the last grooming meeting was to
> investigate with
One action I took from the last grooming meeting was to investigate
with the community, what process and policies we want to use around the
retirement and/or removal of Committers on the project. As our mentors have
told us before, the community here is empowered to decide the criteria
Sorry, hard to understand exactly what you're trying to do, what's
"failing" etc.
All I can gather from this is that you are installing something that
requires "apache-ariatosca" but that is already installed, so it's removing
it in order to upgrade. You stopped the log there.
On Wed, Nov 29,
13 matches
Mail list logo