Re: [Openstack-operators] Neutron Issues

I think you probably need to say what ML2 mechanism driver(s) you are using. On Tue, May 2, 2017 at 10:29 PM Steve Powell wrote: > No OVS here. Thanks though! This one has me stumped! > > > > *From:* Chris Sarginson [mailto:csarg...@gmail.com] > *Sent:* Tuesday, May 2, 2017 5:24 PM > *To:* Stev

Re: [Openstack-operators] OpenStack Operators Milan - Neutron Session

On behalf of the Calico team and driver... I'm afraid there won't be anyone from our team in Milan, but I'm happy to provide a quick update here, in case it is useful: - networking-calico (the Calico driver for Neutron) is mature now, and Just Works (tm) for the use cases that it targets.

Re: [Openstack-operators] [openstack-community] User Survey - Deadline Feb 20th

I notice that at the end of the survey, when I click on the "SUBMIT YOUR SURVEY >" button, I just get the same page again, and so could click "SUBMIT YOUR SURVEY >" again, and so on... You might want to look at fixing that; and in the meantime, I hope that would not result in multiple copies of th

Re: [Openstack-operators] [User-committee] User Survey: Pre-launch check

Hi Heidi, In the Answers for "Which OpenStack Network (Neutron) drivers are you using?" (box E80), I think you should delete "Modular Layer 2 Plugin (ML2)". ML2 is an implementation option (and the strongly recommended one) for the vendors (including me) who provide networking drivers; it is not

Re: [Openstack-operators] Mitaka to Newton networking issues

I have also recently been seeing 'Could not load InterfaceDriver' warnings from the DHCP agent, and haven't yet understood that - although I'm pretty sure that my interface driver is being loaded really - or else none of my networking function would work at all. So it's possible that that part of

Re: [Openstack-operators] SDN for hybridcloud, does it *really* exist?

Hi Jonathan, There's also Calico [1,2], which in its simplest form (and as currently implemented): - uses just IP routing (v4 and/or v6)‎ to connect workloads (VMs / containers / pods / bare metal) - has a security model that works across workloads hosted in different clouds, and so can specify

Re: [Openstack-operators] Multiple DHCP Agents

https://bugs.launchpad.net/neutron/+bug/1468236 has some discussion about this. Please note, though, that that discussion is 8 months old, and many of the details discussed there may now have changed; in particular I think the scalability of the reference Neutron DHCP agent may have improved since

Re: [Openstack-operators] Neutron DHCP agent local routes

On 22/04/16 12:22, Dan Sneddon wrote: > Yes, there is an unfortunate possibility of confusion around the word > 'subnet'. To some, that means a network segment, or VLAN, and to some > that just means the specific IP subnet. Neutron takes the latter view, > and treats multiple subnets as multiple IP

Re: [Openstack-operators] Neutron DHCP agent local routes

On 22/04/16 12:03, Remco wrote: > Hi Neil, > > Thanks. > The ip route output is as following, i guess the 0.0.0.0 gateway is only > listed by cloud-init: > > debian@instance:/$ ip route > default via 192.168.10.1 dev eth0 > 192.168.10.0/24 dev eth0 scope link > 169.254.169

Re: [Openstack-operators] Neutron DHCP agent local routes

On 22/04/16 10:59, Remco wrote: > Hi, Hi Remco, > We are running Liberty, with provider networks. We use the Neutron DHCP > agent to configure IPv4 and IPv6 addresses for instances. This is all > working great, however we sometimes need to put multiple subnets on one > VLAN interface (for legacy

Re: [Openstack-operators] [neutron] Interesting networking issue - need help

On 31/03/16 18:40, Christopher Hull wrote: > Hi all; > Was originally DNS issue, but that was a downstream symptom. > > Instances on Private net can't access internet TCP, but CAN ICMP. ping all. > Details: > 1. Instances on Public net work perfectly. > 2. Instances on Private net can fully access

Re: [Openstack-operators] Anyone using Project Calico for tenant networking?

me to agree, and it isn't one of my own priorities at the moment. Hope that's useful. Best wishes, Neil > > - Original Message - > From: Neil Jerram <mailto:neil.jer...@metaswitch.com>> > To: EDMUND RHUDY, openstack-operators@lists.openstack.or

Re: [Openstack-operators] Anyone using Project Calico for tenant networking?

On 05/02/16 19:03, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote: > I meant in a general sense of the networking technology that you're > using for instance networking, not in the sense of per-tenant networks, > though my wording was ambiguous. Part of our larger question centers > around the viability of t

Re: [Openstack-operators] Anyone using Project Calico for tenant networking?

On 05/02/16 18:19, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote: > Hello operators, > > We're continuing to investigate different cloud networking technologies > as part of our project to migrate from nova-network to Neutron, and one > that's come up frequently is Project Calico > (http://www.projectcalico

Re: [Openstack-operators] [Neutron] public and private fixed IPs

For assigning a routable public IP to a VM, James and Kevin have described using an external network, but I think there might be a second possibility. Namely, a shared, non-external network, with a subnet with the routable IP range that you want to assign from, and connected via a Neutron router

Re: [Openstack-operators] Inconsistent neutron namespaces after downtime

Yes, that's the bug that occurred to me too, for your symptom. I think that including that patch will solve the problem. From: Miguel A Diaz Corchero Sent: Friday, 9 October 2015 09:08 To: openstack-operators@lists.openstack.org; Kevin Benton Subject: Re: [Openstack-operators] Inconsistent neutro

Re: [Openstack-operators] European Operators

On 18/09/15 09:13, gustavo panizzo (gfa) wrote: > On Fri, Sep 18, 2015 at 08:43:16 +0100, Matt Jarvis wrote: >> So judging from the responses so far, I'd say there is an appetite for >> doing this. There are also a lot of folks who don't seem to be on this list >> including most of the other Europe

Re: [Openstack-operators] European Operators

Are Europe-based developers/vendors welcome too? My project (Calico) is always keen to understand more about operator interests and requirements, so I'd be very happy to be there. Neil On 17/09/15 13:17, Matt Jarvis wrote: I'm thinking we'll let this thread run for a day or so and hopeful

Re: [Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

I think it should be a requirement for the client to provide back-compatibility; or else to use a standard deprecation pattern‎, i.e. to emit a deprecation warning message, for a cycle or two, before removing support for something.  (I was just caught out by the change from '--is-public=true' t

Re: [Openstack-operators] ssh inside instance

Hi Aishwarya, The basic requirement here is that anyone - which really means a combination of a computer or instance, plus a user on that computer/instance - needs to have the private key that matches the public key that is installed on the target instance. You've asked about logging in from y

Re: [Openstack-operators] [openstack-dev] [Openstack] Rescinding the M name decision

On 10/07/15 10:19, Thierry Carrez wrote: Part of the confusion here is that we are not naming "releases". We are naming release *cycles*. We are giving a name to a period of time, basically. In that period of time, various version numbers for various components will be released. Saying "Glance 1

Re: [Openstack-operators] [openstack-dev] [openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

ll be too crazy? Cheers, Dani On Wed, Jul 1, 2015 at 9:23 AM, Neil Jerram mailto:neil.jer...@metaswitch.com>> wrote: Well, the bug discussion seems to point specifically to this dnsmasq fix: http://thekelleys.org.uk/gitweb/?p=dnsmasq.git

Re: [Openstack-operators] Accessing outside network from instance

Hi Aishwarya, On 01/07/15 10:44, aishwarya.adyanth...@accenture.com wrote: Hi, I have created a three nodes architecture for my openstack setup with the Kilo version. I am able to create an instance from the dashboard but when I try to access the outside network for instance running an ‘apt-get

Re: [Openstack-operators] [openstack-dev] [openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

Well, the bug discussion seems to point specifically to this dnsmasq fix: http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=9380ba70d67db6b69f817d8e318de5ba1e990b12 Neil On 01/07/15 07:34, Daniel Comnea wrote: Hi, sorry for no feedback, i've been doing more and more test and

Re: [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

Thanks Kris and Sam for your replies! On 18/06/15 01:20, Kris G. Lindgren wrote: On 6/17/15, 10:59 AM, "Neil Jerram" wrote: On 17/06/15 16:17, Kris G. Lindgren wrote: See inline. Kris Lindgren Senior Linux Systems Engineer GoDaddy, LL

Re: [Openstack-operators] [Large Deployments Team] Updated Agenda for Later Today

I've also added the Calico use case to the etherpad. I hope it's useful; please could people take a look and let me know if anything about it is not clear? Unfortunately I can't be at the mid-cycle meeting in person, but I'm keen to participate as much as I can remotely, and have reserved tim

Re: [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

On 17/06/15 16:17, Kris G. Lindgren wrote: See inline. Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. On 6/17/15, 5:12 AM, "Neil Jerram" wrote: Hi Kris, Apologies in advance for questions that are probably really dumb -

Re: [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

Couple more dumb comments here - sorry that I'm processing this thread backwards! On 16/06/15 15:20, Jay Pipes wrote: Adding -dev because of the reference to the Neutron "Get me a network spec". Also adding [nova] and [neutron] subject markers. Comments inline, Kris. On 05/22/2015 09:28 PM, K

Re: [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

Hi Kris, Apologies in advance for questions that are probably really dumb - but there are several points here that I don't understand. On 17/06/15 03:44, Kris G. Lindgren wrote: We are doing pretty much the same thing - but in a slightly different way. We extended the nova scheduler to help

Re: [Openstack-operators] [openstack-dev] [nova] [neutron] Re: How do your end users use networking?

[Sorry - unintentionally dropped -operators below; adding it back in this copy.] On 17/06/15 11:35, Neil Jerram wrote: Hi Sam, On 17/06/15 01:31, Sam Morrison wrote: We at NeCTAR are starting the transition to neutron from nova-net and neutron almost does what we want. We have 10 “public

Re: [Openstack-operators] [openstack-dev] [openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

On 09/06/15 11:34, Neil Jerram wrote: On 09/06/15 01:15, Kevin Benton wrote: I'm having difficulty reproducing the issue. The bug that Neil referenced (https://bugs.launchpad.net/neutron/+bug/1192381) looks like it was in Icehouse well before the 2014.1.3 release that looks like Fuel 5.1

Re: [Openstack-operators] [openstack-dev] [openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

fwm/5.1.2/ubuntu/pool/main/ [3] https://ci.fuel-infra.org/ [4] https://bugs.launchpad.net/mos/+filebug On Mon, Jun 8, 2015 at 10:15 AM Neil Jerram mailto:neil.jer...@metaswitch.com>> wrote: Two further thoughts on this: 1. Another DHCP agent problem that m

Re: [Openstack-operators] [openstack-dev][openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

reading issues between the agent and the Neutron server. You might like to review that thread and see if it describes any problems analogous to your DHCP one. Regards, Neil On 08/06/15 17:53, Neil Jerram wrote: My team has seen a problem that could be related: in a churn test w

Re: [Openstack-operators] [openstack-dev][openstack-operators][neutron[dhcp][dnsmask]: duplicate entries in addn_hosts causing no IP allocation

My team has seen a problem that could be related: in a churn test where VMs are created and terminated at a constant rate - but so that the number of active VMs should remain roughly constant - the size of the host and addn_hosts files keeps increasing. In other words, it appears that the conf

Re: [Openstack-operators] [neutron] multiple external networks on the same host NIC

Hi Mike, On 27/04/15 16:49, Mike Spreitzer wrote: > My use case is that I have two behaviorally different external > subnets --- they are treated differently by stuff outside of > OpenStack, with consequences that are meaningful to tenants. Thus, > I have two categories of floating IP addr