[openstack-dev] [neutron][taas] TaaS IRC schedule

Hi, TaaS IRC meetings on 12/21, 12/28 and 1/4 being canceled because of Christmas and New Year holidays. We will resume TaaS IRC on 1/11/2017. Have a nice holiday! Sincerely, Soichi __ OpenStack Developme

Re: [openstack-dev] [all][infra] Python3 change in OpenStack CI

On 2016-12-13 08:29, Andreas Jaeger wrote: > As part of the move to run master and stable/newton on Xenial, we > disabled testing python 3.4 on these newer branches. > > Now, for testing we have: > * python3.4 on older branches (stable/liberty and stable/mitaka) - on a > trusty VM > * python3.5 on

Re: [openstack-dev] [kuryr] Kuryr Kubernetes Demo

Ilya, That's a great demo, thanks for sharing! - I'm quite interested in how we could potentially use this in collaboration with Kolla-Kubernetes to provide a unified Kubernetes-OpenStack environment, and will explore this over the next couple of weeks. Cheers Pete On Mon, Dec 19, 2016 at 2:11

Re: [openstack-dev] [swift] limit/marker/count behavior when limit not given

On Mon, Dec 19, 2016 at 11:54 AM, Monty Taylor wrote: > Hey all, > > In the docs for listing containers: > > http://developer.openstack.org/api-ref/object-storage/? > expanded=show-account-details-and-list-containers-detail > > it says that limit is optional. However, if you give it > full_listin

Re: [openstack-dev] [Horizon] Weekly wrap-up

Yep, Rob's correct, that's the intent. There's also plenty of non-WIP high priority patches in the starred list :-) On 16 December 2016 at 23:31, Rob Cresswell (rcresswe) wrote: > I think the intent is to get eyes on those patches, to prevent a 1000 line > rewrite only for a core to say “I think

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi, Nate, thanks for your reply. May I ask a little stupid question? What's the difference between fwaas and security group? In my opinion, fwaas and security group are both using linux iptables now. So, what's the differences between them? Thanks Zhi Chang ___

Re: [openstack-dev] [neutron] Where will Neutron go in future?

The neutron-fwaas team is an active and enthusiastic participant in the Neutron stadium, and is targeting FWaaS v2 to complete in the Ocala release. Once FWaaS v2 is complete, the neutron-fwaas team will start deprecating FWaaS v1 in the Pike cycle. --N. On Sun, Dec 18, 2016 at 9:56 PM zhi wrote

[openstack-dev] [neutron] Where will Neutron go in future?

Deal all. I have some questions about what will Neutron does in next releases. As far as I know, LBaaSv2 will be deprecated in next 2 releases, maybe P release, we will not see LBaaSv2 anymore, isn't it? Instead of LBaaSv2( HAProxy driver based ), Octavia will be the only LBaaS solution, isn't it

[openstack-dev] [kuryr] Kuryr Kubernetes Demo

Hello, fellow kuryrs! I'd like to share a demo [1] that shows how Kuryr enables OpenStack Neutron networking for Kubernetes and allows Pods to access Nova VMs and vice versa. [1] https://asciinema.org/a/51qn06lgz78gcbzascpl2du4w --- Regards,

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 On 2016/12/16 8:58, Armando M. wrote: Hi neutrinos, I would like to propose Ryan and Nate as the go-to fellows for service-related patches. Both are core in their repos of focus, namely neutron-dynamic-routing and neutron-fwaas, and have a good understanding of the service framework, th

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1 On 2016/12/16 8:14, Armando M. wrote: Hi neutrinos, Miguel Lavalle has been driving the project forward consistently and reliably. I would like to propose him to be entrusted with +2/+A rights in the areas he's been most prolific, which are L3 and DHCP. At the same time, I'd like to prop

[openstack-dev] [swift] limit/marker/count behavior when limit not given

Hey all, In the docs for listing containers: http://developer.openstack.org/api-ref/object-storage/?expanded=show-account-details-and-list-containers-detail it says that limit is optional. However, if you give it full_listing=True, swiftclient always sends at least a second query with a marker s

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

On Fri, Dec 16, 2016 at 04:52:30PM +, Jeremy Stanley wrote: > On 2016-12-16 13:58:58 +1100 (+1100), Tony Breeds wrote: > [...] > > Due to a failure in the release pipline [1] some of the release > > jobs haven't been done. > [...] > > [1] > > http://lists.openstack.org/pipermail/release-job-fa

Re: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

On Fri, Dec 16, 2016 at 05:41:31PM -0500, Emilien Macchi wrote: > Hey Tony, > > Could we also EOL tripleo-incubator and tripleo-image-elements > stable/icehouse please? Yup, No problem. Tony. signature.asc Description: PGP signature _

Re: [openstack-dev] [neutron] multinode CI jobs in the gate

On 18 December 2016 at 12:28, John Schwarz wrote: > Hey, > > There is already an experimental job called > "gate-tempest-dsvm-neutron-dvr-ha-multinode-full-ubuntu-xenial-nv" > (which was added by [1]). > > However, the job is currently a "one dvr_snat nodes, two dvr nodes" > deployment (instead o

Re: [openstack-dev] [meteos] Meteos Released !!

Denis, I believe it would make sense to use containers for all the benefits that containers bring. On the other hand, I believe that using Sahara brings an easy of configuration to Meteos, because deploying and configuring Spark automatically on Meteos would be a bit of rework. Nonetheless, It do

Re: [openstack-dev] [neutron] multinode CI jobs in the gate

Hey, There is already an experimental job called "gate-tempest-dsvm-neutron-dvr-ha-multinode-full-ubuntu-xenial-nv" (which was added by [1]). However, the job is currently a "one dvr_snat nodes, two dvr nodes" deployment (instead of the "two dvr_snat nodes, one dvr node" that it should be in orde

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 From: "Armando M." Reply-To: OpenStack List Date: Friday, December 16, 2016 at 1:58 AM To: OpenStack List Subject: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs Hi neutrinos, I would like to propose Ryan and Nate as the go-to fellows for service-related

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1 From: "Armando M." Reply-To: OpenStack List Date: Friday, December 16, 2016 at 1:14 AM To: OpenStack List Subject: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt Hi neutrinos, Miguel Lavalle has been driving the project forward consistently and