Open Stack

Hi Kyle,

Pls. ignore my previous mail. I figured out the issue and how to give
permission to openstackci.

I have provided owner permission to 'openstackci' for the pypi package. It
is good to go now!..

Thanks,
Vad
--

[image: Inline image 1]

On Wed, Sep 30, 2015 at 4:50 PM, Vadivel Poonathan <
vadivel.openstack at gmail.com> wrote:

> Kyle,
>
> We referenced arista's setup/config files when we setup the pypi for our plugin. So if it is ok for Arista, then it would be ok for ale-omniswitch too, i believe. You said Arista was ok when you did in google, instead of pypi search, in another email. So can you pls. check again ale-omniswitch as well and confirm.
>
> If still it has an issue, can you pls. throw me some pointers on where to enable the openstackci owener permission?..
>
> Thanks,Vad--
>
> The following pypi registrations did not follow directions to enable openstackci has "Owner" permissions, which allow for the publishing of
>
> packages to pypi:
>
> networking-ale-omniswitch
> networking-arista
>
>
> On Wed, Sep 30, 2015 at 11:56 AM, Kyle Mestery <mestery at mestery.com>
> wrote:
>
>> On Tue, Sep 29, 2015 at 8:04 PM, Kyle Mestery <mestery at mestery.com>
>> wrote:
>>
>>> On Tue, Sep 29, 2015 at 2:36 PM, Vadivel Poonathan <
>>> vadivel.openstack at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> As per the Sub-Project Release process - i would like to tag and
>>>> release the following sub-project as part of upcoming Liberty release.
>>>> The process says talk to one of the member of 'neutron-release' group.
>>>> I couldn’t find a group mail-id for this group. Hence I am sending this
>>>> email to the dev list.
>>>>
>>>> I just have removed the version from setup.cfg and got the patch
>>>> merged, as specified in the release process. Can someone from the
>>>> neutron-release group makes this sub-project release.
>>>>
>>>>
>>>
>>> Vlad, I'll do this tomorrow. Find me on IRC (mestery) and ping me there
>>> so I can get your IRC NIC in case I have questions.
>>>
>>>
>> It turns out that the networking-ale-omniswitch pypi setup isn't correct,
>> see [1] for more info and how to correct. This turned out to be ok, because
>> it's forced me to re-examine the other networking sub-projects and their
>> pypi setup to ensure consistency, which the thread found here [1] will
>> resolve.
>>
>> Once you resolve this ping me on IRC and I'll release this for you.
>>
>> Thanks!
>> Kyle
>>
>> [1]
>> http://lists.openstack.org/pipermail/openstack-dev/2015-September/075880.html
>>
>>
>>> Thanks!
>>> Kyle
>>>
>>>
>>>>
>>>> ALE Omniswitch
>>>> Git: https://git.openstack.org/cgit/openstack/networking-ale-omniswitch
>>>> Launchpad: https://launchpad.net/networking-ale-omniswitch
>>>> Pypi: https://pypi.python.org/pypi/networking-ale-omniswitch
>>>>
>>>> Thanks,
>>>> Vad
>>>> --
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150930/0cc21b65/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 165584 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150930/0cc21b65/attachment.png>