[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] [kuryr] Spec and devref placement

+1 for (b) or (d). devrefs should should be where the related code is > On 12 Sep 2016, at 18:18, Irena Berezovsky wrote: > > I am fine with option (b) as well. > We can add option (d): > Specs in openstack/kuryr-specs but devrefs in each specific project, > i.e., the one

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

> On 16 May 2016, at 20:01, Michał Dulko wrote: > > It's not directly related, but this reminds me of tests done by geguileo > [1] some time ago that were comparing different methods of preventing DB > race conditions in concurrent environment. Maybe you'll also find

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

On 16 May 2016, at 18:18, Michał Dulko wrote: > In Cinder we're handling similar problems related to race conditions > between status check and status change with conditional updates. > Basically we're doing "UPDATE table SET status='abc' WHERE id=1 AND >

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

rds, > Artur > IRC: korzen > > [1] https://review.openstack.org/#/c/303966/11 > [2] https://review.openstack.org/#/c/225995 > [3] https://bugs.launchpad.net/neutron/+bug/1516195 > > -Original Message- > From: Ilya Chukhnakov [mailto:ichukhna...@mirantis.com

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

meone writes to another > server. > So the DB lock only provides the conflicting change guarantee in a > single-writer mysql setup. > > On Thu, May 12, 2016 at 11:26 AM, Ilya Chukhnakov <ichukhna...@mirantis.com > <mailto:ichukhna...@mirantis.com>> wrote: > Hi everyo

[openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

Hi everyone. I’ve recently found that straightforward use of NeutronDbObject is prone to concurrency-related problems. I’ve submitted a patch set [3] with some tests to show that without special treatment using NeutronDbObject could lead to unexpected results. Further patch sets will provide

Re: [openstack-dev] [Neutron] Newton blueprints call for action

Hello everyone! Count me in for the VLAN aware VMS. I already have a [seemingly working] proof-of-concept for the OVS driver case and expect to submit it for the review in a few days. > On 13 Apr 2016, at 12:51, Oleg Bondarev wrote: > > > -- Forwarded