Re: [openstack-dev] [nova] Hold off on pushing new patches for config option cleanup

2016-08-27 Thread Matt Riedemann
On 8/22/2016 5:52 PM, Michael Still wrote: Its a shame so many are -2'ed. There is a lot there I could have merged yesterday if it wasn't for that. Michael When I went through and -2'ed things I left those that had a +2 on them, so the -2 was really on the stuff that was not reviewed yet, or

Re: [openstack-dev] [kolla][oisc] scenario #5 running

2016-08-27 Thread Steven Dake (stdake)
Scenario #6 is running – should finish in 4-6 hours. Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Saturday, August 27, 2016 at 4:34 AM To: "OpenStack Developmen

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

2016-08-27 Thread HU, BIN
The challenge in OpenStack is how to enable the innovation built on top of OpenStack. So telco use cases is not only the innovation built on top of OpenStack. Instead, telco use cases, e.g. Gluon (NFV networking), vCPE Cloud, Mobile Cloud, Mobile Edge Cloud, brings the needed requirement for in

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

2016-08-27 Thread Edward Leafe
On Aug 27, 2016, at 12:18 PM, HU, BIN wrote: >> From telco perspective, those are the areas that allow innovation, and >> provide telco customers with new types of services. > > We need innovation, starting from not limiting ourselves from bringing new > idea and new use cases, and bringing th

Re: [openstack-dev] [OpenStack-docs] [cinder] [api] [doc] API status report

2016-08-27 Thread Andreas Jaeger
On 08/26/2016 11:33 PM, Anne Gentle wrote: > Hi cinder block storage peeps: > > I haven't heard from you on your comfort level with publishing so I went > ahead and made the publishing job myself with this review: > > https://review.openstack.org/361475 > > Please let me know your thoughts ther

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

2016-08-27 Thread HU, BIN
IMHO, I wouldn't limit ourselves. If we expand our sight to view vCPE in its entirety, not any standalone VNF, it could be a cloud of vCPEs. It could be an enterprise cloud on top of enterprise vCPEs, or a community cloud across several organizations including vCPEs within residential communiti

Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

2016-08-27 Thread Davanum Srinivas
LOL Thierry! On Sat, Aug 27, 2016 at 8:44 AM, Thierry Carrez wrote: > Jay Pipes wrote: >> [...] >> However, I have not heard vCPE described in that way. v[E]CPE is all >> about enabling a different kind of application delivery for Telco >> products/services. Instead of sending the customer new ha

Re: [openstack-dev] A daily life of a dev in ${name_your_fav_project}

2016-08-27 Thread Gregory Haynes
On Fri, Aug 26, 2016, at 11:03 AM, Joshua Harlow wrote: > Hi folks (dev and more!), > > I was having a conversation with some folks at godaddy around our future > plans for a developer lab (where we can have various setups of > networking, compute, storage...) for 'exploring' purposes (testing o

Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

2016-08-27 Thread Thierry Carrez
Jay Pipes wrote: > [...] > However, I have not heard vCPE described in that way. v[E]CPE is all > about enabling a different kind of application delivery for Telco > products/services. Instead of sending the customer new hardware -- or > installing a giant monolith application with feature toggles

[openstack-dev] [kolla][oisc] scenario #5 running

2016-08-27 Thread Steven Dake (stdake)
Hey folks, I didn't undo any of what Dave did to the cluster. I wrote a simple shell script to run time on all of the operations. We will be doing the same thing for liberty and mitaka. I expect the test of all operations will take about 40 minutes to 2 hours. Full instructions are on the t

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

2016-08-27 Thread Jay Pipes
On 08/25/2016 06:38 PM, joehuang wrote: Hello, Ed, Just as Peter mentioned, "BT's NFV use cases e.g. vCPE, vCDN, vEPC, vIMS, MEC, IoT, where we will have compute highly distributed around the network (from thousands to millions of sites) ". vCPE is only one use case, but not all. And the har

Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

2016-08-27 Thread Jay Pipes
On 08/25/2016 11:08 AM, Thierry Carrez wrote: Jay Pipes wrote: [...] How is vCPE a *cloud* use case? From what I understand, the v[E]CPE use case is essentially that Telcos want to have the set-top boxen/routers that are running cable television apps (i.e. AT&T U-verse or Verizon FiOS-like thin

Re: [openstack-dev] [Neutron][Nova] Neutron mid-cycle summary report

2016-08-27 Thread Miguel Angel Ajo Pelayo
Hi Armando, Thanks for the report, I'm adding some notes inline (OSC/SDK) On Sat, Aug 27, 2016 at 2:13 AM, Armando M. wrote: > Hi Neutrinos, > > For those of you who couldn't join in person, please find a few notes below > to capture some of the highlights of the event. > > I would like to thank