Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

I'm still seeing the same problem after disabling AppArmor, so I think it must be some other root problem. On Wed, Oct 24, 2018 at 2:41 PM Neil Jerram wrote: > > Thanks so much for these hints, Erlon. I will look closer at AppArmor. > > Neil > > On Wed, Oct 24, 2018 at

Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

e 2018 às 09:40, Erlon Cruz escreveu: >> >> I think that there's a change that AppArmor is blocking the access. Have you >> checked the dmesg messages related with apparmor? >> >> Em sex, 19 de out de 2018 às 09:38, Neil Jerram escreveu: >>> >>>

[openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

Wracking my brains over this one, would appreciate any pointers... Setup: Small test deployment with just 3 compute nodes, Queens on Ubuntu Bionic. The first compute node is an NFS server for /var/lib/nova/instances, and the other compute nodes mount that as NFS clients. Problem: Sometimes, when

Re: [openstack-dev] [all] Naming the T release of OpenStack

On Thu, Oct 18, 2018 at 2:35 PM Jay S Bryant wrote: > > > > On 10/18/2018 8:29 AM, Neil Jerram wrote: > > FWIW, I've have no clue if this is serious or not, or what 'Train' refers > to... > > Neil, > > The two Project Team Gathering events in Denver were held at

Re: [openstack-dev] [all] Naming the T release of OpenStack

FWIW, I've have no clue if this is serious or not, or what 'Train' refers to... On Thu, Oct 18, 2018 at 2:25 PM Jay S Bryant wrote: > On 10/18/2018 1:35 AM, Tony Breeds wrote: > > Hello all, > As per [1] the nomination period for names for the T release have > now closed (actually 3 days

Re: [openstack-dev] [keystone][nova] Struggling with non-admin user on Queens install

it means that that user can then do, e.g. nova.images.list(); but at least I have a working system again. Regards, Neil On Thu, Aug 9, 2018 at 4:42 PM Neil Jerram wrote: > I'd like to create a non-admin project and user that are able to do > nova.images.list(), in a Queens install. IIU

[openstack-dev] [keystone][nova] Struggling with non-admin user on Queens install

I'd like to create a non-admin project and user that are able to do nova.images.list(), in a Queens install. IIUC, all users should be able to do that. I'm afraid I'm pretty lost and would appreciate any help. Define a function to test whether a particular set of credentials can do

Re: [openstack-dev] [neutron] Credentials for a Keystone DB lookup from Neutron

name=service, parent_id=default, tags=[]> # Identify which user is the "neutron" one: >>> users=keystone_client.users.list() >>> users[0] http://controller:35357/v3/users/113dc98e751d4720b4573044df6eb870'}, name=neutron, options={}, password_expires_at=None> # Grant

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

b.com/openstack/python-keystoneclient/blob/650716d0dd30a73ccabe3f0ec20eb722ca0d70d4/keystoneclient/v3/client.py#L102-L116 > On Tue, Jul 17, 2018 at 9:58 PM, Neil Jerram wrote: > > On Tue, Jul 17, 2018 at 3:55 PM Jay Pipes wrote: > >> On 07/17/2018 03:36 AM, Neil Jerram wrote: >> &g

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

On Tue, Jul 17, 2018 at 3:55 PM Jay Pipes wrote: > On 07/17/2018 03:36 AM, Neil Jerram wrote: > > Can someone help me with how to look up a project name (aka tenant name) > > for a known project/tenant ID, from code (specifically a mechanism > > driver) running in the Neut

[openstack-dev] [neutron] How to look up a project name from Neutron server code?

Can someone help me with how to look up a project name (aka tenant name) for a known project/tenant ID, from code (specifically a mechanism driver) running in the Neutron server? I believe that means I need to make a GET REST call as here:

Re: [openstack-dev] [tc] [summary] Organizational diversity tag

On Tue, Jun 12, 2018 at 1:07 PM Thierry Carrez wrote: > Neil Jerram wrote: > >> The issue is that the current method (which uses a formula to apply > >>single-vendor and diverse-affiliation tags) is not working so well > >>anymore, with lots of low-acti

Re: [openstack-dev] [tc] [summary] Organizational diversity tag

FWIW, as an outside observer of this conversation: On Tue, Jun 12, 2018 at 10:46 AM Thierry Carrez wrote: > > The issue is that the current method (which uses a formula to apply > single-vendor and diverse-affiliation tags) is not working so well > anymore, with lots of low-activity projects

Re: [openstack-dev] [tc][all] A culture change (nitpicking)

>From my point of view as someone who is still just an occasional contributor (in all OpenStack projects other than my own team's networking driver), and so I think still sensitive to the concerns being raised here: - Nits are not actually a problem, at all, if they are uncontroversial and quick

Re: [openstack-dev] [neutron][ml2 plugin] unit test errors

On Fri, May 11, 2018 at 10:09 AM Andreas Scheuring < scheu...@linux.vnet.ibm.com> wrote: > So what you need to do first is to make a patch for networking-onos that > does ONLY the following > > > replace all occurrences of > > * neutron.callbacks by neutron_lib.callbacks > *

Re: [openstack-dev] [Zun][k8s] AWS Fargate and OpenStack Zun

+1 This is beautifully clear and helpful. Thank you! Neil On Wed, 2 May 2018, 02:13 Shuai Zhao, wrote: > Thanks Hongbin, > > The article is really great! > > On Mon, Apr 30, 2018 at 2:40 PM, Kumari, Madhuri > wrote: > >> Thank you

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 3:50 PM Thierry Carrez wrote: > Removing the root cause would be a more radical move: stop offering > hosting to non-OpenStack projects on OpenStack infrastructure > altogether. [...] I think this is the right solution for OpenStack. In

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

Just an immediate reaction: to me "OpenStack-Hosted projects" is not very distinct from "OpenStack projects". So with that terminology I think there will still be confusion (perhaps more). (Or did I misunderstand your new proposal?) Regards - Neil On Thu, Jun 15, 2017 at 10:16 AM Thierry

Re: [openstack-dev] [api][neutron][nova][Openstack-operators][interop] Time for a bikeshed - help me name types of networking

On Sun, May 14, 2017 at 6:02 PM Monty Taylor wrote: > Are "internal" and "external" ok with folks as terms for those two ideas? > Yes, I think so. Slight worry that 'external' is also used in 'router:external' - but I think it will be clear that your proposed context is

Re: [openstack-dev] [tc][elections]questions about one platform vision

On Tue, Apr 18, 2017 at 3:45 PM Flavio Percoco <fla...@redhat.com> wrote: > On 16/04/17 09:03 +0100, Neil Jerram wrote: > >FWIW, I think the Lego analogy is not actually helpful for another > reason: it has vastly too many ways of combining, and (hence) no sense at &g

Re: [openstack-dev] [tc][elections]questions about one platform vision

FWIW, I think the Lego analogy is not actually helpful for another reason: it has vastly too many ways of combining, and (hence) no sense at all of consistency / interoperability between the different things that you can construct with it. Whereas for OpenStack I believe you are also aiming for

Re: [openstack-dev] Emails for OpenStack R Release Name voting going out - please be patient

Nor me. On Wed, Apr 12, 2017 at 1:55 PM Doug Hellmann wrote: > Excerpts from Dulko, Michal's message of 2017-04-12 12:09:30 +: > > On Wed, 2017-04-12 at 06:57 -0500, Monty Taylor wrote: > > > On 04/06/2017 07:34 AM, Monty Taylor wrote: > > > > > > > > Hey all! > > > >

Re: [openstack-dev] [neutron][ml2] - heads up for mechanism drivers that don't use in tree DHCP agent

Thanks for the heads up, Kevin! Is this still necessary if a deployment disables the Neutron server's DHCP scheduling, with self._supported_extension_aliases.remove("dhcp_agent_scheduler") ? Thanks, Neil On Fri, Mar 31, 2017 at 12:52 AM Kevin Benton

Re: [openstack-dev] Project Navigator Updates - Feedback Request

Thanks, Sebastian, it looks good now. On Fri, Mar 24, 2017 at 5:12 PM Sebastian Marcet <smar...@gmail.com> wrote: > Neil sorry about that, problem solved, please re test > regards > > 2017-03-24 14:02 GMT-03:00 Neil Jerram <n...@tigera.io>: > > If I start typing

Re: [openstack-dev] Project Navigator Updates - Feedback Request

If I start typing something in the search box, I get an "Authentication Required" popup that captures the remaining keystrokes that I intended to type into the search box. Then if I do manage to type a complete search term into the box, and press Enter, that "Authentication Required" popup pops

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Hi Sam, On Tue, Mar 7, 2017 at 8:05 AM Sam wrote: > Is this? > > https://pypi.python.org/pypi/neutron-lib > Yes, that is one of the ways that neutron-lib is packaged. The 'upstream' is at http://git.openstack.org/cgit/openstack/neutron-lib. Exactly how are you using the

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 5:26 AM Joshua Harlow wrote: > Radical idea, have each project (not libraries) contain a dockerfile > that builds the project into a deployable unit (or multiple dockerfiles > for projects with multiple components) and then it becomes the projects >

Re: [openstack-dev] New driver project status?

ernance+branch:master+topic:formal-vote+driver-teams > > -- Dims > > On Wed, Feb 1, 2017 at 9:21 AM, Neil Jerram <n...@tigera.io> wrote: > > I believe there was recently a discussion on one of the OpenStack MLs > about > > a possible new status for driver projects.

[openstack-dev] New driver project status?

I believe there was recently a discussion on one of the OpenStack MLs about a possible new status for driver projects. Unfortunately I'm not immediately managing to find it in the archives. Did that discussion reach a conclusion, and - if so - is that documented somewhere? Thanks, Neil

Re: [openstack-dev] Is the gate stuck?

Thanks for the explanation. I agree that it has indeed moved now! On Wed, Jan 25, 2017 at 8:18 PM Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2017-01-25 20:05:04 + (+0000), Neil Jerram wrote: > > I'm not experienced in reading these things, but it seems that nothing i

[openstack-dev] Is the gate stuck?

I'm not experienced in reading these things, but it seems that nothing is currently getting through the integrated gate, and from [1] it appears this is because the gate-tempest-dsvm-neutron-full-ubuntu-xenial job of [2] has hung. [1] http://status.openstack.org/zuul/ [2]

Re: [openstack-dev] [neutron] PTL candidacy

On Wed, Jan 25, 2017 at 10:20 AM Thierry Carrez wrote: > Kevin Benton wrote: > > [...] > > The Neutron API is already very extensible and that's problematic. Right > > now a vendor can write an out-of-tree service plugin or driver that adds > > arbitrary fields and

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

I very much agree with Nate's comment here, and have particularly appreciated our discussions in connection with networking-calico. I look forward to your continuing involvement and help, even if not as PTL. Thanks Armando! On Mon, Jan 9, 2017 at 4:02 PM Nate Johnston

Re: [openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

Hi Steve, On Tue, Jan 10, 2017 at 7:35 AM Steve Martinelli wrote: > In preparation for the next TC meeting, a survey was sent out to driver > maintainers, here is a summary of the feedback that was gathered. > Did you send that survey to me, for networking-calico? I'm

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 23, 2016 at 1:37 PM Steve Gordon <sgor...@redhat.com> wrote: > - Original Message - > > From: "Neil Jerram" <n...@tigera.io> > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 16, 2016 at 4:16 PM Neil Jerram <n...@tigera.io> wrote: > On Fri, Dec 16, 2016 at 4:08 PM Steve Gordon <sgor...@redhat.com> wrote: > > > If you haven't already I would suggest grabbing qemu-kvm-ev from the > CentOS > > > Virt SIG repos: > > &

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 16, 2016 at 4:08 PM Steve Gordon <sgor...@redhat.com> wrote: > - Original Message - > > From: "Neil Jerram" <n...@tigera.io> > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.ope

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

On Fri, Dec 16, 2016 at 3:35 PM Steve Gordon <sgor...@redhat.com> wrote: > > > - Original Message ----- > > From: "Neil Jerram" <n...@tigera.io> > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev

Re: [openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

using libvirt 1.2.7? Thanks - Neil On Fri, Dec 16, 2016 at 11:40 AM Neil Jerram <n...@tigera.io> wrote: I appreciate that even libvirt 2.0.0 will be ancient history by now, to its developers, but I am seeing further issues that look associated with the recent CentOS 7 transition from libvirt

[openstack-dev] Issues with libvirt transition 1.2.7 -> 2.0.0 (CentOS 7.3)

I appreciate that even libvirt 2.0.0 will be ancient history by now, to its developers, but I am seeing further issues that look associated with the recent CentOS 7 transition from libvirt 1.2.7 to libvirt 2.0.0, and would appreciate any comments on them that people may have. I believe these

Re: [openstack-dev] [neutron] Is it possible that creating a port and binding it with 2 IPs

Hi Vincent,Your initial observation is correct: each port is associated with a Neutron network, and will get one IPv4 and one IPv6 address from the subnets associated with that network.To add additional IPs to a

Re: [openstack-dev] [Neutron] Stepping down from core

Thanks for your help with recent neutron-lib transitions, and best wishes for your future work, Henry! Neil On Thu, Dec 1, 2016 at 11:06 PM Dariusz Śmigiel wrote: > Henry, > it's very sad to see you stepping down. > Thank you for all the time and help in

Re: [openstack-dev] [neutron] neutron-lib impact

t; On Nov 24, 2016 10:02, "Armando M." <arma...@gmail.com> wrote: > > > > On 24 November 2016 at 05:27, Neil Jerram <n...@tigera.io> wrote: > > But I think a periodic check for a Neutron/neutron-lib-using project (such > as networking-cali

Re: [openstack-dev] [neutron] neutron-lib impact

But I think a periodic check for a Neutron/neutron-lib-using project (such as networking-calico) would still be a decent way of catching such issues, wouldn't it? On Thu, Nov 24, 2016 at 12:58 AM Kevin Benton wrote: > The issue we had is different than breaking changes in

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Tue, Nov 22, 2016 at 2:00 PM Neil Jerram <n...@tigera.io> wrote: > After fixing those... I see that the reproduce.sh script appears to do > DevStack setup correctly, but not to run any Tempest tests. Is > reproduce.sh supposed to run the Tempest tests as well? > >

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Tue, Nov 22, 2016 at 11:41 AM Neil Jerram <n...@tigera.io> wrote: > On Tue, Nov 22, 2016 at 10:58 AM Neil Jerram <n...@tigera.io> wrote: > > On Mon, Nov 7, 2016 at 9:50 PM Clark Boylan <cboy...@sapwetik.org> wrote: > > [...] > > If you have jobs still run

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Tue, Nov 22, 2016 at 10:58 AM Neil Jerram <n...@tigera.io> wrote: > On Mon, Nov 7, 2016 at 9:50 PM Clark Boylan <cboy...@sapwetik.org> wrote: > > [...] > > If you have jobs still running on trusty the next step is to fire up a > Xenial instance locally and ru

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Mon, Nov 7, 2016 at 9:50 PM Clark Boylan wrote: > [...] If you have jobs still running on trusty the next step is to fire up a > Xenial instance locally and run that test to see if it works. Usually > this will mean running the appropriate tox target or if using >

Re: [openstack-dev] [Neutron] Stepping down from core

On Thu, Nov 17, 2016 at 6:44 PM Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such > that I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and drivers team member. My

[openstack-dev] [neutron][calico] networking-calico IRC meeting today

Hi all; just wanted to remind that there will be a networking-calico IRC meeting today [1]. Please feel free to add to the agenda at [2] (or ask me to do that if you prefer). Thanks! Neil [1] http://eavesdrop.openstack.org/#Networking_Calico_Meeting [2]

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On Mon, Nov 7, 2016 at 9:50 PM Clark Boylan wrote: > If you have jobs still running on trusty the next step is to fire up a > Xenial instance locally and run that test to see if it works. > Can you advise how big (RAM, CPU, disk) the Xenial instance should be, so as to be

Re: [openstack-dev] [neutron][routed-network] Host doesn't connected any segments when creating port

Hi Zhi Chang,I believe the answer is that the physical network (aka fabric) should provide routing between those two subnets. This routing between segments is implicit in the idea of a multi-segment network, and

[openstack-dev] [neutron][calico] networking-calico IRC meeting tomorrow

Hi all; just wanted to remind that there will be a networking-calico IRC meeting tomorrow [1]. Please feel free to add to the agenda at [2] (or ask me to do that if you prefer). Thanks! Neil [1] http://eavesdrop.openstack.org/#Networking_Calico_Meeting [2]

Re: [openstack-dev] [band] OpenStack Summit - Barcelona - musicians please raise your hands

/sax   Thanks,   -amrith   From: Neil Jerram [mailto:n...@tigera.io] Sent: Monday, September 19, 2016 2:36 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [band] OpenStack Summit - Barcelona - musicians

Re: [openstack-dev] [neutron][calico][tempest][gate] Help setting up DSVM gate job for networking-calico

e tempest disabled in your > devstack settings file. > > On Thu, Oct 20, 2016 at 4:34 AM, Neil Jerram <n...@tigera.io> wrote: > > I'm trying to set up a dsvm gate job for networking-calico [1] - which I > think means > - using DevStack to set up a single combined controller/co

Re: [openstack-dev] Project mascot logos - sneak peek

IMO these logos are all really wonderful. Great work Heidi et al.! Neil On Wed, Oct 19, 2016 at 8:14 PM Heidi Joy Tretheway wrote: > Hi Developers, > Thanks for waiting patiently for news on your project logos! Our team of > illustrators has been working hard

[openstack-dev] [neutron][calico][tempest][gate] Help setting up DSVM gate job for networking-calico

I'm trying to set up a dsvm gate job for networking-calico [1] - which I think means - using DevStack to set up a single combined controller/compute node, with networking-calico settings and plugin [2] - using Tempest to run some tests on that; ideally including some networking-related tests :-)

Re: [openstack-dev] [neutron][networking-vpp]Introducing networking-vpp

On Wed, Oct 19, 2016 at 4:30 AM Ian Wells wrote: > Sorry to waken an old thread, but I chose a perfect moment to go on > holiday... > > So yes: I don't entirely trust the way we use RabbitMQ, and that's largely > because what we're doing with it - distributing state, or

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

+1, looks lovely! On Fri, Oct 14, 2016 at 7:31 PM Miguel Lavalle wrote: > Dear Neutrinos, > > I am organizing a social event for the team on Thursday 27th at 19:30. > After doing some Google research, I am proposing Raco de la Vila, which is > located in Poblenou:

[openstack-dev] [neutron][calico] Disappearance of neutron-lib deprecation warnings?

Back in August, HenryG committed a useful change [1] to networking-calico (and I assume to other neutron projects) to show deprecation warnings for imports from neutron that should now be from neutron-lib. But then in late August / early September, those deprecation warnings disappeared again -

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Wed, Oct 5, 2016 at 4:09 PM Sean Dague wrote: > On 10/03/2016 12:46 PM, Edward Leafe wrote: > > > > > We are fortunate in that all of the candidates are exceptionally > well-qualified, and those elected have put in excellent service while on > the TC. But one thing I'm afraid

Re: [openstack-dev] [neutron][networking-vpp]Introducing networking-vpp

On Thu, Oct 6, 2016 at 3:44 PM Jay Pipes wrote: > On 10/06/2016 03:46 AM, Jerome Tollet (jtollet) wrote: > > Hey Kevin, > > > > Thanks for your interest in this project. > > > > We found etcd very convenient to store desired states as well as > > operational states. It made

Re: [openstack-dev] [band] OpenStack Summit - Barcelona - musicians please raise your hands

I will be happy to bring my clarinet. Neil On Sat, Sep 17, 2016 at 7:37 PM Colette Alexander < colettealexan...@gmail.com> wrote: > On Sat, Sep 17, 2016 at 1:35 PM, Amrith Kumar wrote: > > So, would y'all musicians who plan to bring your gear to Barcelona > please start

Re: [openstack-dev] Singing in Barcelona

Being reminded by the band thread, I thought I should remind about this too... On Mon, Jul 11, 2016 at 6:56 PM Neil Jerram <n...@tigera.io> wrote: > I know it's crazy, but I've talked with a few people in Vancouver, Tokyo > and Austin about the idea of getting a singing group tog

Re: [openstack-dev] [charms]Running two haproxy-using units on same machine?

Thanks James for this quick and clear answer! Neil On Tue, Sep 13, 2016 at 8:46 PM, James Page <james.p...@ubuntu.com> wrote: > Hi Neil > > On Tue, 13 Sep 2016 at 20:43 Neil Jerram <n...@tigera.io> wrote: > >> Should it be possible to run two OpenStack charm u

[openstack-dev] [charms]Running two haproxy-using units on same machine?

Should it be possible to run two OpenStack charm units, that both use haproxy to load balance their APIs, on the same machine? Or is there some doc somewhere that says that a case like that should use separate machines? (I'm asking in connection with the bug report at

Re: [openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

I've put my name against networking-calico, but I believe it's a no-op for me at this stage of the tenant->project transition. The occurrences of 'tenant' in networking-calico's code are: ./networking_calico/plugins/calico/plugin.py:45:LOG.info("Forcing ML2 tenant_network_types to

Re: [openstack-dev] [Openstack] Naming polls - and some issues

Not sure what the problem would be with 'Quay' or 'Street' - they both sound like good options to me. On Thu, Jul 14, 2016 at 11:29 AM Eoghan Glynn wrote: > > > > >> Hey all! > > >> > > >> The poll emails for the P and Q naming have started to go out - and > > >> we're

[openstack-dev] Singing in Barcelona

I know it's crazy, but I've talked with a few people in Vancouver, Tokyo and Austin about the idea of getting a singing group together during a summit, and they've all encouraged me to go for it - so I'll start to look silly if I don't even try this... :-)So this is a call for anyone who wants to

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

Hi all, Just a quick reminder: the first networking-calico IRC meeting will be tomorrow (12th July) at 1600 UTC. Neil On Fri, Jul 1, 2016 at 12:31 PM Neil Jerram <n...@tigera.io> wrote: > The first networking-calico IRC meeting was planned for 28th June, but I'm > afraid I was

Re: [openstack-dev] [Neutron] Neutron-lib and Stadium evolution

Cool - thanks for clarifying that! Neil On Fri, Jul 8, 2016 at 5:20 PM Armando M. <arma...@gmail.com> wrote: > On 8 July 2016 at 08:22, Neil Jerram <n...@tigera.io> wrote: > >> Hi Armando, >> >> Who exactly are you addressing here? AFAICS, [1] on its ow

Re: [openstack-dev] [Neutron] Neutron-lib and Stadium evolution

Hi Armando, Who exactly are you addressing here? AFAICS, [1] on its own doesn't give me (or anyone) any new rights for neutron-lib changes. It appears to be preparatory to a planned expansion of neutron-lib-core - but looking at [5], the membership doesn't include me, or folk from many stadium

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

The first networking-calico IRC meeting was planned for 28th June, but I'm afraid I was unwell - so it will now be 12th July. I've updated the agenda [2] accordingly. Neil On Mon, Jun 20, 2016 at 3:42 PM Neil Jerram <n...@tigera.io> wrote: > Calling everyone interested in networki

Re: [openstack-dev] [neutron][calico] New networking-calico IRC meeting

Thanks, Carl. I had the same observation, so would also be interested in the answer. Neil On Thu, Jun 30, 2016 at 9:15 PM Carl Baldwin <c...@ecbaldwin.net> wrote: > On Mon, Jun 20, 2016 at 8:42 AM, Neil Jerram <n...@tigera.io> wrote: > > Calling everyone interested

Re: [openstack-dev] [packaging-deb] Status of the project

Is there a higher-level overview somewhere of what packaging-deb does? Should it be useful to me as the packager of a Neutron driver project (networking-calico)? (Currently I've rolled my own processes for generating Debian packages for Ubuntu Trusty and Xenial.) Thanks, Neil On Wed, Jun

[openstack-dev] [neutron][calico] New networking-calico IRC meeting

Calling everyone interested in networking-calico ...! networking-calico has been around in the Neutron stadium for a while now, and it's way past time that we had a proper forum for discussing and evolving it - so I'm happy to be finally proposing a regular IRC meeting slot for it: [1]. A

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On Wed, Jun 15, 2016 at 9:52 AM Thierry Carrez wrote: > [...] > Those are good points. Note that I do not advocate for those projects to > be kept closed/private: I'm simply saying that those (open source) > projects should not be blessed as "official" and be put under the

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port isActive

right now. Would that be reasonable? > > Best, > > Mohammad > > [image: Inactive hide details for Neil Jerram ---06/10/2016 09:25:59 > AM---Hi Mohammad, Why is the blocking needed? Is it to report som]Neil > Jerram ---06/10/2016 09:25:59 AM---Hi Mohammad, Why is the blocki

Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port is Active

Hi Mohammad, Why is the blocking needed? Is it to report some kind of status back to Docker/Kubernetes, or to allow some follow-on action to happen? When using networking-calico as the driver, I think that only option (1) would work, out of the options you've suggested below. (3) doesn't work,

Re: [openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

Me too. On Fri, Jun 10, 2016 at 10:32 AM Cory Benfield wrote: > > > On 8 Jun 2016, at 11:20, James Page wrote: > > > > The majority of contributors are from Canonical (from whom I have > permission to make this switch) with a further 18 contributors

Re: [openstack-dev] [Fuel] Correct wrong nomenclature in the Networks section of Fuel-ui

As I just commented in the review, I think the wording was clearer as it was before. So would prefer if you do not use this as a model for further similar changes. Neil On Wed, Jun 1, 2016 at 2:06 PM Giuseppe Cossu wrote: > Hi folks, > I submitted a bug and

Re: [openstack-dev] [nova-lxd]Nova-lxd with Linuxbridge

FWIW, the networking-calico team plans soon to make nova-lxd work with Calico networking, i.e. where data from/to the veth is routed on the compute host. That should land in July or August. Neil On Fri, May 20, 2016 at 3:30 PM Chuck Short wrote: > Hi, > >

Re: [openstack-dev] [charms] Juju Charms for OpenStack

+1 from me (as an OpenStack contributor, and one of those 'developers at SDN and storage vendors' :-) ). Neil On Thu, May 19, 2016 at 11:38 AM James Page wrote: > Hi All > > tl;dr Juju is a great way of deploying OpenStack, and we'd like the > OpenStack Charms for

Re: [openstack-dev] Easing contributions to central documentation

On 09/05/16 22:57, Matt Kassawara wrote: > At each summit, I speak with a variety of developers from different > projects about the apparent lack of contributions to the central > documentation. At previous summits, the most common complaint involved > using DocBook. After converting most of the

[openstack-dev] [kuryr] Port binding query

I'm trying Kuryr with networking-calico and think I've hit an unhelpful inconsistency. A Neutron port has 'id' and 'device_id' fields that are usually different. When Nova does VIF binding for a Neutron port, it generates the Linux device name from 'tap' + port['id']. But when Kuryr does VIF

Re: [openstack-dev] Easing contributions to central documentation

On 09/05/16 22:57, Matt Kassawara wrote: > At each summit, I speak with a variety of developers from different > projects about the apparent lack of contributions to the central > documentation. At previous summits, the most common complaint involved > using DocBook. After converting most of the

Re: [openstack-dev] [neutron] Social at the summit

On 25/04/16 10:58, Kyle Mestery wrote: > Ihar, Henry and I were talking and we thought Thursday night makes sense for > a Neutron social in Austin. If others agree, reply on this thread and we'll > find a place. That sounds good to me - thanks for thinking of it! Neil

Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

On 19/04/16 16:52, Irina Povolotskaya wrote: > Hi to everyone, > > as you possibly know (at least, those dev. teams working on their Fuel > plugins) we have a fuel-plugins Launchpad project [1] which serves as > all-in-one entry point for filing bugs, related > to plugin-specific problems. > >

[openstack-dev] summit tools

A couple of questions about our Austin-related planning tools... - Can one's calendar at https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-25 be exported as .ics, or otherwise integrated into a wider calendaring system? - Is the app working for anyone else? All I get

Re: [openstack-dev] [all] [devstack] Adding example "local.conf" files for testing?

On 14/04/16 08:35, Markus Zoeller wrote: > Sometimes (especially when I try to reproduce bugs) I have the need > to set up a local environment with devstack. Everytime I have to look > at my notes to check which option in the "local.conf" have to be set > for my needs. I'd like to add a folder in

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

On 01/04/16 02:16, Assaf Muller wrote: > Have you been negatively impacted by slow development and review > velocity? Read on. > > OpenStack has had a slow review velocity for as long as I can > remember. This has a cascading effect where people take up multiple > tasks, so that they can work on

Re: [openstack-dev] [Nova] No rejoin-stack.sh script in my setup

On 31/03/16 12:10, Ouadï Belmokhtar wrote: > Hi everyone, > > Could you give any help to my question here, please. > > http://stackoverflow.com/questions/36268822/no-rejoin-stack-sh-script-in-my-setup > > I'm blocked with the same problem since 10 days. Any help is considered. I think the

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 30/03/16 16:08, Pavel Bondar wrote: > We are now in early Newton, so it is good time to discuss plan for > pluggable ipam for this release cycle. > > Kevin Benton commented on review page for current migration to pluggable > approach [1]: >> >> IMO this cannot be optional. It's going to be a

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 29/03/16 21:55, Carl Baldwin wrote: > > I thought of another type of grouping which could benefit pluggable > IPAM today. It occurred to me as I was refreshing my memory on how > pluggable IPAM works when there are multiple subnets on a network. > Currently, Neutron's backend pulls the subnets

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 29/03/16 19:16, Carl Baldwin wrote: > I've been playing with this a bit on this patch set [1]. I haven't > gotten very far yet but it has me thinking. > > Calico has a similar use case in mind as I do. Essentially, we both > want to group subnets to allow for aggregation of routes. (a) In >

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On 11/03/16 23:20, Carl Baldwin wrote: > Hi, Hi Carl, and sorry for the lateness of this reply. > I have started to get into coding [1] for the Neutron routed networks > specification [2]. > > This spec proposes a new association between network segments and > subnets. This affects how IPAM

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

On 29/03/16 20:42, Miguel Lavalle wrote: > Hi, Hi Miguel, > I am writing a patchset to build a mapping between hosts and network > segments. The goal of this mapping is to be able to say whether a host > has access to a given network segment. I am building this mapping > assuming that if a host

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 30/03/16 13:35, Igor Kalnitsky wrote: > Neil Jerram wrote: >> But isn't Ansible also over-complicated for just running commands over SSH? > > It may be not so "simple" to ignore that. Ansible has a lot of modules > which might be very helpful. For instance, Sho

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

FWIW, as a naive bystander: On 30/03/16 11:06, Igor Kalnitsky wrote: > Hey Fuelers, > > I know that you probably wouldn't like to hear that, but in my opinion > Fuel has to stop using Shotgun. It's nothing more but a command runner > over SSH. Besides, it has well known issues such as retrieving

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 29/03/16 15:17, Jay Pipes wrote: > Hi! > > Once Shotgun is pulled out of Fuel, may I suggest renaming it to > something different? I know in the past that Anita and a few others > thought the name was not something we should really be encouraging in > the OpenStack ecosystem. > > Just something

  1   2   3   >