Hi-

Sure Anita. I have been attending meeting for ML2 at #openstack-meeting-alt.

Will also, attend the below mentioned meetings ..

Thanking you.

-
Trinaths
________________________________________
From: Anita Kuno <ante...@anteaya.info>
Sent: Tuesday, May 27, 2014 10:45 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1

On 05/27/2014 01:03 PM, trinath.soman...@freescale.com wrote:
> Hi-
>
>
> Thanks a lot Salvatore.
>
>
> I'm looking into that issue. I'm troubleshooting the same.
>
>
> Will update this mail chain when its accessible for review.
>
>
> Thanks a lot for the review Salvatore.
>
>
> --
>
> Trinath
Have you considered starting an irc client, navigating to freenode and
joining the #openstack-dev and #openstack-neutron channels? It would
increase the rate at which you learn how to amend your code to get it
merged. It also would help as you troubleshoot your CI system.

Give it some thought,
Anita.
>
>
> ________________________________
> From: Salvatore Orlando <sorla...@nicira.com>
> Sent: Tuesday, May 27, 2014 10:29 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
>
> Too late.
>
> I just approved the specification.
> I don't think there is any need for reverting the blueprint and just updating 
> the topic in the patch.
>
> Please have a look at Freescale CI - logs are not accessible at the moment.
>
> Salvatore
>
>
> On 27 May 2014 18:51, 
> trinath.soman...@freescale.com<mailto:trinath.soman...@freescale.com> 
> <trinath.soman...@freescale.com<mailto:trinath.soman...@freescale.com>> wrote:
> Hi-
>
> Sure!. Will change the topic and update you.
>
> Thanks a lot for the reply and review.
>
> Your review helps me a lot to proceed further with code.
>
> Thanking you ..
>
> -
> Trinath Somanchi
> ________________________________________
> From: Edgar Magana Perdomo (eperdomo) 
> <eperd...@cisco.com<mailto:eperd...@cisco.com>>
> Sent: Tuesday, May 27, 2014 10:18 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [neutron] BPs for Juno-1
>
> My only comment is that the name of the topic should be:
>
> bp/fsl-sdn-os-mech-driver
>
>
> Instead of:
> bp/https
>
>
> I guss we can pass this..
>
> Edgar
>
> On 5/27/14, 9:23 AM, 
> "trinath.soman...@freescale.com<mailto:trinath.soman...@freescale.com>"
> <trinath.soman...@freescale.com<mailto:trinath.soman...@freescale.com>> wrote:
>
>> Hi Kyle
>>
>> Kindly consider my BP spec (https://review.openstack.org/#/c/88190/)  too
>> for Juno1.
>>
>> I have been mailing the reviewer to kindly make some to to review the BP
>> spec.
>>
>> I have code too in place for review along with working CI.
>>
>> The Code for review : https://review.openstack.org/#/c/78092/
>>
>> Kindly please do the needful.
>>
>> --
>> Trinath Somanchi.
>>
>> ________________________________________
>> From: Kyle Mestery 
>> <mest...@noironetworks.com<mailto:mest...@noironetworks.com>>
>> Sent: Tuesday, May 27, 2014 7:44 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: [openstack-dev] [neutron] BPs for Juno-1
>>
>> Hi Neutron developers:
>>
>> I've spent some time cleaning up the BPs for Juno-1, and they are
>> documented at the link below [1]. There are a large number of BPs
>> currently under review right now in neutron-specs. If we land some of
>> those specs this week, it's possible some of these could make it into
>> Juno-1, pending review cycles and such. But I just wanted to highlight
>> that I removed a large number of BPs from targeting Juno-1 now which
>> did not have specifications linked to them nor specifications which
>> were actively under review in neutron-specs.
>>
>> Also, a gentle reminder that the process for submitting specifications
>> to Neutron is documented here [2].
>>
>> Thanks, and please reach out to me if you have any questions!
>>
>> Kyle
>>
>> [1] https://launchpad.net/neutron/+milestone/juno-1
>> [2] https://wiki.openstack.org/wiki/Blueprints#Neutron
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to