Re: ARIA-118 plugin.yaml importing

[Thomas Nadeau]

Nothing has changed for non-committers; use the canonical GitHub fork->push
patches->propose patch request method
on the same two GitHub repos:

https://github.com/apache/incubator-ariatosca-website

and

https://github.com/apache/incubator-ariatosca

I’ll be on slack from now too if you need additional help.

—Tom


On Dec 4, 2017, at 8:28 AM, D Jayachandran 
wrote:

Hi,

I need to contribute for this JIRA item. Previously I had made my
contribution by forking from the apache-ariatosca project.
Is the process changed now ? What is the process which I should follow now ?


Regards,
DJ

[GitHub] djay87 opened a new pull request #212: ARIA-118 plugin.yaml importing

[GitBox]

djay87 opened a new pull request #212: ARIA-118 plugin.yaml importing
URL: https://github.com/apache/incubator-ariatosca/pull/212
 
 
   This commit supports using the plugin.yaml present in a plugin wagon archive 
in a more simpler way as described below.
   
   imports:
 - file: -
   repository: plugins


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] asfgit commented on issue #212: ARIA-118 plugin.yaml importing

[GitBox]

asfgit commented on issue #212: ARIA-118 plugin.yaml importing
URL: 
https://github.com/apache/incubator-ariatosca/pull/212#issuecomment-348881562
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

ARIA-118 plugin.yaml importing

[D Jayachandran]

Hi,

I need to contribute for this JIRA item. Previously I had made my contribution 
by forking from the apache-ariatosca project.
Is the process changed now ? What is the process which I should follow now ?


Regards,
DJ

Re: Transition to Gitbox Complete

[Tal Liron]

It's semantics, John. Recommending one mechanism but not the other means
that the other mechanism is less recommended or, in other words,
discouraged. This might be a mild discouragement, but it is so. The impact
of this mild discouragement would be that our potential devs will likely be
using https.

Anyway, if you know what you're doing, use whatever is easiest and best for
you.

On Sun, Dec 3, 2017 at 5:23 PM, John D. Ament  wrote:

> On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau 
> wrote:
>
> > That still uses SSH, which then uses your pre-configured keys.  Github
> docs
> > discourage this use for some reason.
> >
>
> Err no, github docs "recommend" using HTTPS, they don't discourage the use
> of SSH.
>
> https://stackoverflow.com/questions/11041729/why-does-
> github-recommend-https-over-ssh
> provides
> some info about why HTTPS is the current recommendation.
>
>
> >
> > --Tom
> >
> > On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> > wrote:
> >
> > > Any reason you wouldn't just use the github direct URLs?
> > >
> > > g...@github.com:apache/incubator-ariatosca.git
> > > g...@github.com:apache/incubator-ariatosca-website.git
> > >
> > >
> > >
> > > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > > wrote:
> > >
> > > > The gitbox transition appears to have completed - thanks for setting
> > this
> > > > up Suneel.
> > > >
> > > > Committers please follow the instructions Suneel provided on Slack
> > > earlier
> > > > to synch your apache account with github so permissions work/etc...
> > > >
> > > > --Tom
> > > >
> > > >
> > > > From slack:
> > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca.git;a=summary
> > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca-website.git;a=
> > > summary
> > > >
> > > > Moved to both repos Gitbox.  You'll need to have your committers link
> > > their
> > > > Github IDs on id.apache.org and enable two factor authentication
> here:
> > > > https://gitbox.apache.org/setup/  This process can take up to 2
> hours
> > > for
> > > > Gitbox to see.
> > > >
> > >
> >
>

Re: Transition to Gitbox Complete

[Thomas Nadeau]

I just took "recommend" one way to discourage the other. FWIW I've used
both methods with similar success; seems like personal preference.

--Tom


On Sun, Dec 3, 2017 at 5:23 PM, John D. Ament  wrote:

> On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau 
> wrote:
>
> > That still uses SSH, which then uses your pre-configured keys.  Github
> docs
> > discourage this use for some reason.
> >
>
> Err no, github docs "recommend" using HTTPS, they don't discourage the use
> of SSH.
>
> https://stackoverflow.com/questions/11041729/why-does-
> github-recommend-https-over-ssh
> provides
> some info about why HTTPS is the current recommendation.
>
>
> >
> > --Tom
> >
> > On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> > wrote:
> >
> > > Any reason you wouldn't just use the github direct URLs?
> > >
> > > g...@github.com:apache/incubator-ariatosca.git
> > > g...@github.com:apache/incubator-ariatosca-website.git
> > >
> > >
> > >
> > > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > > wrote:
> > >
> > > > The gitbox transition appears to have completed - thanks for setting
> > this
> > > > up Suneel.
> > > >
> > > > Committers please follow the instructions Suneel provided on Slack
> > > earlier
> > > > to synch your apache account with github so permissions work/etc...
> > > >
> > > > --Tom
> > > >
> > > >
> > > > From slack:
> > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca.git;a=summary
> > > >
> > > >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca-website.git;a=
> > > summary
> > > >
> > > > Moved to both repos Gitbox.  You'll need to have your committers link
> > > their
> > > > Github IDs on id.apache.org and enable two factor authentication
> here:
> > > > https://gitbox.apache.org/setup/  This process can take up to 2
> hours
> > > for
> > > > Gitbox to see.
> > > >
> > >
> >
>

Re: Transition to Gitbox Complete

[Thomas Nadeau]

Those instructions are working.  I pushed a PR earlier as well as Maxim
pushed a few.

--Tom


On Sun, Dec 3, 2017 at 5:21 PM, Suneel Marthi  wrote:

> If it helps, here's what was done on OpenNLP - one of the first projects
> that transitioned to gitbox in July 2017 after gitbox was announced.
>
> http://opennlp.apache.org/using-git.html
>
>
>
> On Sun, Dec 3, 2017 at 10:11 AM, Thomas Nadeau 
> wrote:
>
> > That still uses SSH, which then uses your pre-configured keys.  Github
> docs
> > discourage this use for some reason.
> >
> > --Tom
> >
> > On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> > wrote:
> >
> > > Any reason you wouldn't just use the github direct URLs?
> > >
> > > g...@github.com:apache/incubator-ariatosca.git
> > > g...@github.com:apache/incubator-ariatosca-website.git
> > >
> > >
> > >
> > > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > > wrote:
> > >
> > > > The gitbox transition appears to have completed - thanks for setting
> > this
> > > > up Suneel.
> > > >
> > > > Committers please follow the instructions Suneel provided on Slack
> > > earlier
> > > > to synch your apache account with github so permissions work/etc...
> > > >
> > > > --Tom
> > > >
> > > >
> > > > From slack:
> > > >
> > > > https://gitbox.apache.org/repos/asf?p=incubator-
> > ariatosca.git;a=summary
> > > >
> > > > https://gitbox.apache.org/repos/asf?p=incubator-
> > ariatosca-website.git;a=
> > > summary
> > > >
> > > > Moved to both repos Gitbox.  You'll need to have your committers link
> > > their
> > > > Github IDs on id.apache.org and enable two factor authentication
> here:
> > > > https://gitbox.apache.org/setup/  This process can take up to 2
> hours
> > > for
> > > > Gitbox to see.
> > > >
> > >
> >
>

Re: Transition to Gitbox Complete

[John D. Ament]

On Sun, Dec 3, 2017 at 10:11 AM Thomas Nadeau  wrote:

> That still uses SSH, which then uses your pre-configured keys.  Github docs
> discourage this use for some reason.
>

Err no, github docs "recommend" using HTTPS, they don't discourage the use
of SSH.

https://stackoverflow.com/questions/11041729/why-does-github-recommend-https-over-ssh
provides
some info about why HTTPS is the current recommendation.


>
> --Tom
>
> On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> wrote:
>
> > Any reason you wouldn't just use the github direct URLs?
> >
> > g...@github.com:apache/incubator-ariatosca.git
> > g...@github.com:apache/incubator-ariatosca-website.git
> >
> >
> >
> > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > wrote:
> >
> > > The gitbox transition appears to have completed - thanks for setting
> this
> > > up Suneel.
> > >
> > > Committers please follow the instructions Suneel provided on Slack
> > earlier
> > > to synch your apache account with github so permissions work/etc...
> > >
> > > --Tom
> > >
> > >
> > > From slack:
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=incubator-ariatosca.git;a=summary
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=incubator-ariatosca-website.git;a=
> > summary
> > >
> > > Moved to both repos Gitbox.  You'll need to have your committers link
> > their
> > > Github IDs on id.apache.org and enable two factor authentication here:
> > > https://gitbox.apache.org/setup/  This process can take up to 2 hours
> > for
> > > Gitbox to see.
> > >
> >
>

Re: Transition to Gitbox Complete

[Suneel Marthi]

If it helps, here's what was done on OpenNLP - one of the first projects
that transitioned to gitbox in July 2017 after gitbox was announced.

http://opennlp.apache.org/using-git.html



On Sun, Dec 3, 2017 at 10:11 AM, Thomas Nadeau 
wrote:

> That still uses SSH, which then uses your pre-configured keys.  Github docs
> discourage this use for some reason.
>
> --Tom
>
> On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament 
> wrote:
>
> > Any reason you wouldn't just use the github direct URLs?
> >
> > g...@github.com:apache/incubator-ariatosca.git
> > g...@github.com:apache/incubator-ariatosca-website.git
> >
> >
> >
> > On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> > wrote:
> >
> > > The gitbox transition appears to have completed - thanks for setting
> this
> > > up Suneel.
> > >
> > > Committers please follow the instructions Suneel provided on Slack
> > earlier
> > > to synch your apache account with github so permissions work/etc...
> > >
> > > --Tom
> > >
> > >
> > > From slack:
> > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-
> ariatosca.git;a=summary
> > >
> > > https://gitbox.apache.org/repos/asf?p=incubator-
> ariatosca-website.git;a=
> > summary
> > >
> > > Moved to both repos Gitbox.  You'll need to have your committers link
> > their
> > > Github IDs on id.apache.org and enable two factor authentication here:
> > > https://gitbox.apache.org/setup/  This process can take up to 2 hours
> > for
> > > Gitbox to see.
> > >
> >
>

Re: Transition to Gitbox Complete

[Tal Liron]

You *could* use those -- they are ssh with ssh keys. However, GitHub
generally recommends using HTTPS.

On Sun, Dec 3, 2017 at 4:54 PM, John D. Ament  wrote:

> Any reason you wouldn't just use the github direct URLs?
>
> g...@github.com:apache/incubator-ariatosca.git
> g...@github.com:apache/incubator-ariatosca-website.git
>
>
>
> On Sun, Dec 3, 2017 at 4:45 AM Thomas Nadeau 
> wrote:
>
> > The gitbox transition appears to have completed - thanks for setting this
> > up Suneel.
> >
> > Committers please follow the instructions Suneel provided on Slack
> earlier
> > to synch your apache account with github so permissions work/etc...
> >
> > --Tom
> >
> >
> > From slack:
> >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca.git;a=summary
> >
> > https://gitbox.apache.org/repos/asf?p=incubator-ariatosca-website.git;a=
> summary
> >
> > Moved to both repos Gitbox.  You'll need to have your committers link
> their
> > Github IDs on id.apache.org and enable two factor authentication here:
> > https://gitbox.apache.org/setup/  This process can take up to 2 hours
> for
> > Gitbox to see.
> >
>

Use of github tokens

[Thomas Nadeau]

Just to reflect this bit of important information for those pushing PRs:

emblemparade [11:45 AM]
also note: switching to two-factor authentication on github will involve
some changes. if you want to use https URLs, you will need a personal
access token. more info here:
https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/
(edited)


new messages
emblemparade [11:53 AM]
to clarify, if you use ssh key pairs (git@ URLs) then you *do not* need an
access token. access tokens are *only* needed for TLS (https).


Thomas Nadeau [2:45 PM]
I confirmed this is definitely the case

The token is entered in your password field.

[GitHub] tnadeauaria opened a new pull request #5: ARIA-415 Add git installation instructions to GettingStarted Guide

[GitBox]

tnadeauaria opened a new pull request #5: ARIA-415 Add git installation 
instructions to GettingStarted Guide
URL: https://github.com/apache/incubator-ariatosca-website/pull/5
 
 
   Add git installation instructions to GettingStarted Guide, clean up some 
things making them consistent.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Making the usage of ARIA more generic

[Maxim Orlov]

I've been working on making the usage of ARIA more generic, and opened up a
few PRS:

   - https://github.com/apache/incubator-ariatosca/pull/209 - making the
   update of tasks triggered by events more generic.
   - https://github.com/apache/incubator-ariatosca/pull/211 - the current
   json encoding mechanism is too strict to the current implementation of ARIA
   - this PR makes it more generic.

In addition, the current logging handler context manager just adds handlers
instead of replacing it. This PR fixes it:
https://github.com/apache/incubator-ariatosca/pull/210.

These PRs are fairly short and simple, it'd be great if we could push those
to 0.2.0.

[GitHub] tnadeauaria closed pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide

[GitBox]

tnadeauaria closed pull request #4: ARIA-415: add git to source-based 
installation in Getting Started Guide
URL: https://github.com/apache/incubator-ariatosca-website/pull/4
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/gettingstarted.md b/gettingstarted.md
index 5a02dfb..a9c8c81 100644
--- a/gettingstarted.md
+++ b/gettingstarted.md
@@ -5,8 +5,8 @@ permalink: /getting-started/
 share: false
 ---
 
-Installation
-
+Package-Based Installation
+--
 
 ARIA is [available on PyPI](https://pypi.python.org/pypi/apache-ariatosca).
 
@@ -17,6 +17,10 @@ To install ARIA directly from PyPI (using a ``wheel``), use::
 pip install --upgrade pip setuptools
 pip install apache-ariatosca
 
+
+Source-based Installations
+--
+
 To install ARIA from source, download the source tarball from
 [PyPI](https://pypi.python.org/pypi/apache-ariatosca), extract and ``cd`` into 
the extract dir, and run::
 
@@ -34,12 +38,12 @@ To install ARIA from source, download the source tarball 
from
 
 **Ubuntu/Debian** (tested on Ubuntu14.04, Ubuntu16.04)::
 
-apt-get install -y python-dev gcc libffi-dev libssl-dev
+apt-get install -y python-dev gcc libffi-dev libssl-dev git
 pip install apache-ariatosca[ssh]
 
 **Centos** (tested on Centos6.6, Centos7)::
 
-yum install -y python-devel gcc libffi-devel openssl-devel
+yum install -y python-devel gcc libffi-devel openssl-devel git
 pip install apache-ariatosca[ssh]
 
 **Archlinux**::
@@ -65,8 +69,8 @@ To install ``pip``, either use your distro's package 
management system, or run::
 
 
 
-Getting Started

+"Hello World" Example
+-
 
 
 This section will describe how to run a simple "Hello World" example.


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] tnadeauaria opened a new pull request #4: ARIA-415: add git to source-based installation in Getting Started Guide

[GitBox]

tnadeauaria opened a new pull request #4: ARIA-415: add git to source-based 
installation in Getting Started Guide
URL: https://github.com/apache/incubator-ariatosca-website/pull/4
 
 
   Add git to source-based installation in Getting Started Guide. Updated main 
headers to reflect source or package-based installations.
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Podling Report Reminder - December 2017

[johndament]

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 form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, December 06).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might 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 does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/December2017

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

[GitHub] mxmrlv opened a new pull request #211: ARIA-417 Encoding models to json is too strict

[GitBox]

mxmrlv opened a new pull request #211: ARIA-417 Encoding models to json is too 
strict
URL: https://github.com/apache/incubator-ariatosca/pull/211
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] asfgit commented on issue #211: ARIA-417 Encoding models to json is too strict

[GitBox]

asfgit commented on issue #211: ARIA-417 Encoding models to json is too strict
URL: 
https://github.com/apache/incubator-ariatosca/pull/211#issuecomment-348758528
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] mxmrlv opened a new pull request #210: CFY-416 Providing handlers to logging_handlers only adds handles inst?

[GitBox]

mxmrlv opened a new pull request #210: CFY-416 Providing handlers to 
logging_handlers only adds handles inst?
URL: https://github.com/apache/incubator-ariatosca/pull/210
 
 
   ?ead of replacing


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] asfgit commented on issue #210: CFY-416 Providing handlers to logging_handlers only adds handles inst?

[GitBox]

asfgit commented on issue #210: CFY-416 Providing handlers to logging_handlers 
only adds handles inst?
URL: 
https://github.com/apache/incubator-ariatosca/pull/210#issuecomment-348758517
 
 
   Can one of the admins verify this patch?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Transition to Gitbox Complete

[Thomas Nadeau]

The gitbox transition appears to have completed - thanks for setting this
up Suneel.

Committers please follow the instructions Suneel provided on Slack earlier
to synch your apache account with github so permissions work/etc...

--Tom


>From slack:

https://gitbox.apache.org/repos/asf?p=incubator-ariatosca.git;a=summary
https://gitbox.apache.org/repos/asf?p=incubator-ariatosca-website.git;a=summary

Moved to both repos Gitbox.  You'll need to have your committers link their
Github IDs on id.apache.org and enable two factor authentication here:
https://gitbox.apache.org/setup/  This process can take up to 2 hours for
Gitbox to see.

Re: synchronize committers/devs/policies between code and web repos?

[Thomas Nadeau]

Sorry to reply to my own post, but I just wanted to update folks on this
thread.

We've transitioned the repos (https://github.com/apache/incubator-ariatosca
and https://github.com/apache/incubator-ariatosca-website)
with gitbox and as part of that it was clear that both repos are managed by
the same group of committers/etc... so that answered
the question referenced below.

--Tom


On Tue, Nov 28, 2017 at 6:01 PM, Thomas Nadeau 
wrote:

>
> During the grooming meeting the point came up and was discussed briefly,
> about
> the desire to synch up both areas, especially given the move to gitbox
> where github
> will contain the code of record for the project very soon.
>
> I am looking to our mentors for advice on this one. 8)
>
> There are a number of stable/mature projects that operate this way,
> including within
> Apache, so there is plenty of precedent to synchronize both the website
> and the dev
> areas.
>
> What would this entail?  It would include the following, but might not be
> limited to:
>
> 0) Officially recognize https://github.com/apache/incubator-ariatosca-
> website
> as the master of the AriaTosca website.  At present, there are Jenkins
> jobs triggered from commits
> to this that regenerate/post the website when changes are made, so some
> integration with Apache infra
> has already happened.   However, as far as I know, there is no official
> mirroring like we currently have
> with https://github.com/apache/incubator-ariatosca-website for the code
> base.
>
> 1) As part of 0, synchronize committers between the two.  As far as I can
> tell, the committers of the
> website are a subset of those on the main project, so there shouldn’t be
> much if anything
> that needs to be done here except add
>
> If I have missed anything, please chime in!
>
> Cheers,
> —Tom
>
>

Re: pip executable expected as part of plugin install.

[Thomas Nadeau]

 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 freeze in current environment and return the
> > output"""
> > > > bin_dir = 'Scripts' if os.name == 'nt' else 'bin'
> > > > pip_path = os.path.join(sys.prefix, bin_dir,
> > > > 'pip{0}'.format('.exe' if os.name ==
> > > 'nt'
> > > > else ''))
> > > > pip_freeze = subprocess.Popen([pip_path, 'freeze'],
> > > > stdout=subprocess.PIPE)
> > > > pip_freeze_output, _ = pip_freeze.communicate()
> > > > assert not pip_freeze.poll()
> > > > return pip_freeze_output
> > > >
> > > > Now the question is why are we executing a pip command directly and
> > > > not using pip as a library.
> > > >
> > > >
> > > > Regards,
> > > > DJ
> > > >
> > >
> >
>

Re: pip executable expected as part of plugin install.

[Tal Liron]

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 
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 freeze in current environment and return the
> output"""
> > > bin_dir = 'Scripts' if os.name == 'nt' else 'bin'
> > > pip_path = os.path.join(sys.prefix, bin_dir,
> > > 'pip{0}'.format('.exe' if os.name ==
> > 'nt'
> > > else ''))
> > > pip_freeze = subprocess.Popen([pip_path, 'freeze'],
> > > stdout=subprocess.PIPE)
> > > pip_freeze_output, _ = pip_freeze.communicate()
> > > assert not pip_freeze.poll()
> > > return pip_freeze_output
> > >
> > > Now the question is why are we executing a pip command directly and
> > > not using pip as a library.
> > >
> > >
> > > Regards,
> > > DJ
> > >
> >
>