-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 24/08/14 20:40, Maru Newby wrote:
>
> On Aug 24, 2014, at 5:14 PM, Henry Gessau
> wrote:
>
>> Ihar Hrachyshka wrote:
>>> Now, maybe putting the module into requirements.txt is an
>>> overkill (though I doubt it). In that case, we could be
>>>
On Aug 25, 2014, at 11:38 AM, Robert Collins wrote:
> Fwiw I would like to see such dependencies listed so that we can properly
> install trunk via automation.
Do you mean that you want the requirements for all plugins listed somewhere in
the tree? Or specifically in Neutron’s requirements.
Fwiw I would like to see such dependencies listed so that we can properly
install trunk via automation.
On 24 Aug 2014 10:43, "Maru Newby" wrote:
>
> On Aug 14, 2014, at 1:55 PM, Ihar Hrachyshka wrote:
>
> > Signed PGP part
> > FYI: I've uploaded a review for openstack/requirements to add the
>
On Aug 24, 2014, at 5:14 PM, Henry Gessau wrote:
> Ihar Hrachyshka wrote:
>> Now, maybe putting the module into requirements.txt is an overkill
>> (though I doubt it). In that case, we could be interested in getting
>> the info in some other centralized way.
>
> Maru is of the opinion that it
Ihar Hrachyshka wrote:
> Now, maybe putting the module into requirements.txt is an overkill
> (though I doubt it). In that case, we could be interested in getting
> the info in some other centralized way.
Maru is of the opinion that it is overkill. I feel the same way, but I am not
involved much
On Aug 14, 2014, at 1:55 PM, Ihar Hrachyshka wrote:
> Signed PGP part
> FYI: I've uploaded a review for openstack/requirements to add the
> upstream module into the list of potential dependencies [1]. Once it's
> merged, I'm going to introduce this new requirement for Neutron.
The only reason s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FYI: I've uploaded a review for openstack/requirements to add the
upstream module into the list of potential dependencies [1]. Once it's
merged, I'm going to introduce this new requirement for Neutron.
[1]: https://review.openstack.org/114213
/Ihar
On 8/12/2014 1:53 PM, Ihar Hrachyshka wrote:
> On 12/08/14 17:12, Henry Gessau wrote:
>> On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote:
>>> as per [1], Cisco Nexus ML2 plugin requires a patched version of
>>> ncclient from github. I wonder:
>>>
>>> - - whether this information is still current;
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/08/14 17:12, Henry Gessau wrote:
> On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote:
>> as per [1], Cisco Nexus ML2 plugin requires a patched version of
>> ncclient from github. I wonder:
>>
>> - - whether this information is still current;
>
>
On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote:
> as per [1], Cisco Nexus ML2 plugin requires a patched version of
> ncclient from github. I wonder:
>
> - - whether this information is still current;
Please see:
https://review.openstack.org/112175
But we need to do backports before updating the wi
10 matches
Mail list logo
