Re: [openstack-dev] [neutron][L3][HA] 2 masters after reboot of node

th you. I will try to implement this suggestion. > > On Fri, May 26, 2017 at 7:01 PM, Kevin Benton <ke...@benton.pub> wrote: > >> Just triggering a status change should just be handled as a port update >> on the agent side which shouldn't interrupt any existing flows. So

Re: [openstack-dev] [neutron][L3][HA] 2 masters after reboot of node

26, 2017 at 6:14 PM, Kevin Benton <ke...@benton.pub> wrote: > >> Perhaps when the L3 agent starts up we can have it explicitly set the >> port status to DOWN for all of the HA ports on that node. Then we are >> guaranteed that when they go to ACTIVE it will be because the L

Re: [openstack-dev] [neutron][L3][HA] 2 masters after reboot of node

Perhaps when the L3 agent starts up we can have it explicitly set the port status to DOWN for all of the HA ports on that node. Then we are guaranteed that when they go to ACTIVE it will be because the L2 agent has wired the ports. On Fri, May 26, 2017 at 5:27 AM, Anil Venkata

Re: [Openstack] [openstack][neutron] multiple vlan provider and tenant networks?

Yep! On May 26, 2017 3:17 AM, <vladislav.belogru...@oracle.com> wrote: > Thanks Kevin! > > so I can mix and match tenant and provider vlans now. > > Vladislav > > On 05/26/2017 11:48 AM, Kevin Benton wrote: > > assuming 'vlan' is in tenant_

Re: [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

ss to host is restored, > but not to VMs > > > - restart neutron-openvswitch-agent -> access to VMs is restored > > Thank you! > > > > > On Fri, Apr 28, 2017 at 5:07 PM, Kevin Benton <ke...@benton.pub> wrote: > >> With the network down, does

Re: [Openstack-operators] [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

ss to host is restored, > but not to VMs > > > - restart neutron-openvswitch-agent -> access to VMs is restored > > Thank you! > > > > > On Fri, Apr 28, 2017 at 5:07 PM, Kevin Benton <ke...@benton.pub> wrote: > >> With the network down, does

Re: [Openstack] [openstack][neutron] multiple vlan provider and tenant networks?

assuming 'vlan' is in tenant_network_types, it will go through the network_vlan_ranges you have defined. Since you haven't provided a range for provider0 or provider1, it will not automatically allocate from those. It will only automatically allocate from the two you have provided ranges for

Re: [openstack-dev] [neutron]VM packet lost on qbr bridge

Is it being dropped by iptables? Check the following: * Your VM using the correct IPv6 address assigned to it by Neutron * The security group associated with the port allows outbound IPv6 traffic * ensure bridge-nf-call-ip6tables is set to 1 in the kernel of the compute node On Thu, May 25, 2017

Re: [Openstack] How to utilize Neutron independently with veths

name prefix or what? What can I do to let it happen? > > Regards, > Dastan > > -- Original -- > *From: * "Kevin Benton"<ke...@benton.pub>; > *Date: * Wed, May 24, 2017 05:21 AM > *To: * "duhongwei"<duhong...@qiniu.com>; > *Cc: *

Re: [openstack-dev] [neutron][heat] - making Neutron more friendly for orchestration

: > >> On Fri, May 19, 2017, at 02:03 PM, Kevin Benton wrote: >> > I split this conversation off of the "Is the pendulum swinging on PaaS >> > layers?" thread [1] to discuss some improvements we can make to Neutron >> > to >> > make orchestra

Re: [Openstack] Openstack Routed Provider Networks Question

ferent 'physical_network' values, but may have the same VLAN ID (segmentation_id). On Tue, May 23, 2017 at 6:31 AM, Chris Marino <ch...@romana.io> wrote: > Thanks Kevin, very helpfulother comments in line. > CM > > On Mon, May 22, 2017 at 9:15 PM, Kevin Benton <ke...@benton.pub&g

Re: [Openstack-operators] Routed provider networks...

> On Mon, May 22, 2017 at 9:12 PM, Kevin Benton <ke...@benton.pub> wrote: > >> The operators that were asking for the spec were using private IP space >> and that is probably going to be the most common use case for routed >> networks. Splitting a /21 up across the entir

Re: [Openstack] How to utilize Neutron independently with veths

t will be >> anti-spoofed. >> >> *qvo*'s attributes (external-ids) tell neutron which logical *port* *qvo* >> is connecting, so neutron knows how to add flows to ovs *br-int *and >> *br-tun*. >> >> Am I correct? >> >> Regards, >> Dastan >> >&

[openstack-dev] [neutron] - may 23rd team meeting cancelled

Hi, There will be no neutron team meeting today due to a conflict on my end. If you have any announcements, please direct them to the mailing list. Ask any questions about bugs or blueprints in the #openstack-neutron channel. Cheers, Kevin Benton

Re: [Openstack] Openstack Routed Provider Networks Question

On May 22, 2017 9:34 AM, "Chris Marino" wrote: I'm digging into how Routed Provider Networks work and have some questions as well. I will presenting at the OpenStack Meetup on Wed on this and want to make sure I have my facts

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

I think we just need someone to volunteer to do the work to expose it as metadata to the VM in Nova. On May 22, 2017 1:27 PM, "Robert Li (baoli)" wrote: > Hi Levi, > > > > Thanks for the info. I noticed that support in the nova code, but was > wondering why something similar is

Re: [Openstack] How to utilize Neutron independently with veths

gt; > Regards, > Dastan > > -- Original -- > *From: * "Kevin Benton"<ke...@benton.pub>; > *Date: * Sat, May 20, 2017 03:26 AM > *To: * "duhongwei"<duhong...@qiniu.com>; > *Cc: * "openstack"<openstac

Re: [openstack-dev] [puppet] [tempest] L2GW not standard Tempest Plugin. How to get tests into CI?

Can you file a patch to adjust tox.ini of l2gw to make it the same as the others? On May 22, 2017 7:35 AM, "Ricardo Noriega De Soto" wrote: > Hello guys, > > I'm trying to enable some tempest tests into puppet-openstack-integration > project. I basically did the same

Re: [openstack-dev] [neutron][heat] - making Neutron more friendly for orchestration

way to distinguish which floating IP to translate to is which router the traffic is being directed to by the instance, which requires router interfaces. Cheers On Fri, May 19, 2017 at 3:29 PM, Zane Bitter <zbit...@redhat.com> wrote: > On 19/05/17 17:03, Kevin Benton wrote: > >> I sp

[openstack-dev] [neutron] - Summit "The Future of VPN as a Service (VPNaaS)" summary and next steps

erspective available in etherpad 1. https://bugs.launchpad.net/neutron/+bug/1692126 2. https://bugs.launchpad.net/neutron/+bug/1692128 3. https://bugs.launchpad.net/neutron/+bug/1692130 4. https://bugs.launchpad.net/neutron/+bug/1692131 Cheers, Ke

[openstack-dev] [neutron] - Summit "Distributed SNAT with DVR" summary and next steps

. If this is a burning point for you as an operator, consider looking into Dragonflow, which now has support for distributed SNAT. Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

[openstack-dev] [neutron] - Summit "Neutron Pain points session" summary and next steps

out for the summary of the closely related session "Making Neutron easy for people who want basic Networking" from Sukhdev if your topics were covered that session. 1. https://bugs.launchpad.net/neutron/+bug/1692133 2. https://bugs.launchpad.net/neutron/+bug

Re: [openstack-dev] [neutron][heat] - making Neutron more friendly for orchestration

+IP? On Fri, May 19, 2017 at 2:13 PM, Monty Taylor <mord...@inaugust.com> wrote: > On 05/19/2017 04:03 PM, Kevin Benton wrote: > >> I split this conversation off of the "Is the pendulum swinging on PaaS >> layers?" thread [1] to discuss some improvements

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

Started a new Neutron-specific thread so we can get some stuff turned into improvements in Neutron from this: http://lists.openstack.org/pipermail/openstack-dev/2017-May/117112.html On Fri, May 19, 2017 at 1:05 PM, Zane Bitter <zbit...@redhat.com> wrote: > On 19/05/17 15:06, Kevin Ben

[openstack-dev] [neutron][heat] - making Neutron more friendly for orchestration

- These seems similar to 1626607. Can we just expose the interfaces/router a floating IP is depending on explicitly in the API for you to fix these? If not, what can we do to help here? 1. http://lists.openstack.org/pipermail/openstack-dev/2017-May/117106.html Cheers, Kevin Benton On Fri, May 19,

Re: [Openstack] How to utilize Neutron independently with veths

same as neutron *port*'s > mac address? > 2) after we plug *qvo* into ovs *br-int*, neutron just automatically add > flows into ovs bridge? > > Regards, > Dastan > > -- Original -- > *From: * "Kevin Benton"<ke...@bento

Re: [openstack-dev] Is the pendulum swinging on PaaS layers?

>Don't even get me started on Neutron.[2] It seems to me the conclusion to that thread was that the majority of your issues stemmed from the fact that we had poor documentation at the time. A major component of the complaints resulted from you misunderstanding the difference between

Re: [Openstack] How to utilize Neutron independently with veths

------ Original -- > *From: * "Kevin Benton"<ke...@benton.pub>; > *Date: * Fri, May 12, 2017 10:45 AM > *To: * "duhongwei"<duhong...@qiniu.com>; > *Cc: * "openstack"<openstack@lists.openstack.org>; "Va

Re: [Openstack] How to utilize Neutron independently with veths

You want to look in neutron.agent.linux.interface to see how things are plugged into OVS. That's the module used by the L3 agent to plug into OVS/linux bridge/etc. There is a well defined interface name format corresponding to the port ID and the port ID, Mac address, and a couple of other things

Re: [Openstack] Neutron MTU help

Unfortunately not at the moment. There is a request to enable it here: https://bugs.launchpad.net/neutron/+bug/1671634 If you can add your use case to that request for enhancement that will be useful to help prioritize it. On Wed, May 10, 2017 at 1:07 PM, Sterdnot Shaken

[openstack-dev] [neutron] - neutron social

See message below from Miguel for details on the neutron social. Dear Neutrinos, We have a plan for tomorrow night, Wednesday 10th at 7pm. We are going to meet at UNO Pizzeria and Grill, 731 Boylston Street Boston, MA 02116, phone number (617) 267-8554. This location is a very easy walk of less

Re: [openstack-dev] [neutron] - are you attending the Boston summit?

t; > Following our past tradition, we should have Neutron dinner while we are > all in Boston. > > Miguel has few places in mind. I would propose that we nominate him as the > dinner organizer lieutenant. > > > > Miguel, I hope you will take us to some cool place. >

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

Thanks for all of your contributions. Good luck in your new role! Cheers On Thu, May 4, 2017 at 9:52 AM, Rossella Sblendido wrote: > Hi all, > > I've moved to a new position recently and despite my best intentions I > was not able to devote to Neutron as much time and

[openstack-dev] [neutron] - no drivers meeting today or next week (May 4th and May 11th)

Hi all, I'm canceling the drivers meeting May 4th and 11th to avoid discussion of new features until after the summit when we have collected user/operator feedback. Cheers, Kevin Benton __ OpenStack Development Mailing List

Re: [Openstack-operators] Neutron Issues

Failed to allocate networks usually means that the port failed to bind on the neutron side. If you're using ML2 + (ovs or Linux bridge), that's usually caused by either the agent on the host being dead, or there being no agent running on that host at all. Do a 'neutron agent-list' and ensure

Re: [Openstack] Neutron unable to create VLAN network

That means vlan 1 is in use by one of the other networks. On May 2, 2017 14:59, "Timothy Geier" wrote: > I’m doing some testing/PoC on an RDO Ocata CentOS7 setup and everything > has gone well with the exception of configuring multiple VLANs. > > After following the

Re: [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

tag: 171 > Interface "vlan171" > type: internal > ... > > > On Fri, Apr 28, 2017 at 3:03 PM, Kevin Benton <ke...@benton.pub> wrote: > >> Ok, that's likely not the issue then. I assume the way you access each >> ho

Re: [Openstack-operators] [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

tag: 171 > Interface "vlan171" > type: internal > ... > > > On Fri, Apr 28, 2017 at 3:03 PM, Kevin Benton <ke...@benton.pub> wrote: > >> Ok, that's likely not the issue then. I assume the way you access each >> ho

Re: [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

r/run/openvswitch/ovsdb-server.pid --detach --monitor > > Thanks > > > > > On Fri, Apr 28, 2017 at 5:00 AM, Kevin Benton <ke...@benton.pub> wrote: > >> Are you using an of_listen_address value of an interface being brought >> down? >> >> On Apr 25, 20

Re: [openstack-dev] [neutron] stepping down from neutron core team

Thanks for all of your work. Come back soon. ;) On Apr 28, 2017 05:02, "Miguel Angel Ajo Pelayo" wrote: > > Hi everybody, > > Some of you already know, but I wanted to make it official. > > Recently I moved to work on the networking-ovn component, > and OVS/OVN

Re: [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

Are you using an of_listen_address value of an interface being brought down? On Apr 25, 2017 17:34, "Gustavo Randich" wrote: > (using Mitaka / Ubuntu 16 / Neutron DVR / OVS / VXLAN / l2_population) > > This sounds very strange (to me): recently, after a switch outage,

Re: [Openstack-operators] [Openstack] Strange: lost physical connectivity to compute hosts when using native (ryu) openflow interface

Are you using an of_listen_address value of an interface being brought down? On Apr 25, 2017 17:34, "Gustavo Randich" wrote: > (using Mitaka / Ubuntu 16 / Neutron DVR / OVS / VXLAN / l2_population) > > This sounds very strange (to me): recently, after a switch outage,

Re: [openstack-dev] [neutron] keeping on top of neutron reviews

ay showing patches that are fixes for high/critical bugs, approved > blueprints and RFE. You can find it here [1] under "Gerrit Dashboard links" > > cheers, > > Rossella > > [1] http://status.openstack.org/reviews/ > > On 04/18/2017 12:45 AM, Kevin Benton wrote:

[openstack-dev] [neutron] - are you attending the Boston summit?

Hi, If you are a Neutron developer attending the Boston summit, please add your name to the etherpad here so we can plan a Neutron social and easily coordinate in person meetings: https://etherpad.openstack.org/p/neutron-boston-summit-attendees Cheers, Kevin Benton

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

FWIW mine just came through yesterday. On Wed, Apr 19, 2017 at 12:13 PM, Jay S Bryant wrote: > All, > > For those of you haven't received an e-mail, check the inbox you use for > Gerrit. You can verify what that is by going to review.openstack.org , > click your name, go

Re: [openstack-dev] Development workflow for bunch of patches

Whenever you want to work on the second patch you would need to first checkout the latest version of the first patch and then cherry-pick the later patch on top of it. That way when you update the second one it won't affect the first patch. The -R flag can also be used to prevent unexpected

Re: [Openstack] HA Router, "I want you!"

You might be able to force it by removing it from the active node and then adding it back. On Tue, Apr 18, 2017 at 3:56 PM, Sterdnot Shaken wrote: > Let's say I have 3 network nodes but set max_l3_agents_per_router to 2 > (intentionally) and I want to move either the

[openstack-dev] [neutron] keeping on top of neutron reviews

. Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [Openstack] Neutron in Newton: host_id and device_owner?

te) may work - that validates it somewhat. > > And about the deferred allocation - where would I find more info on that? > > > > [image: --] > Gregory Golberg > [image: http://]about.me/gregorygolberg > <http://about.me/gregorygolberg?promo=email_sig> > >

Re: [Openstack] LinuxBridge Agent Error

I am on CentOS 7 and this is a manual Ocata installation as described >>>> on the deployment guide. >>>> >>>> My cloud seems to be operating normally even with these messages. The >>>> thing is that I don't like all these (there are a whole bunch

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

I haven't received one either. Perhaps Monty has simply embraced the 'cattle not pets' approach and we were the unlucky ones. :) On Apr 12, 2017 07:49, "Lance Bragstad" wrote: > > On Wed, Apr 12, 2017 at 9:42 AM, Amrith Kumar > wrote: > >> Hmm, all

Re: [Openstack] Neutron in Newton: host_id and device_owner?

[image: http://]about.me/gregorygolberg > <http://about.me/gregorygolberg?promo=email_sig> > > > On Mon, Apr 10, 2017 at 4:10 PM, Kevin Benton <ke...@benton.pub> wrote: > >> Nova may not have set them yet. The port is updated with the host ID and >> the device ID

Re: [Openstack] How to get all detail RPC message and detail context in neutron docs?

I would strongly recommend that you don't build anything based on these messages. The contents change from release to release since this is an internal API between the agents and the server. On Apr 6, 2017 00:48, "Sam" wrote: > Thank you, use debug option will also help us

Re: [openstack-dev] [Openstack] How to get all detail RPC message and detail context in neutron docs?

I would strongly recommend that you don't build anything based on these messages. The contents change from release to release since this is an internal API between the agents and the server. On Apr 6, 2017 00:48, "Sam" wrote: > Thank you, use debug option will also help us

Re: [openstack-dev] [neutron][sfc][fwaas][taas][horizon] where would we like to have horizon dashboard for neutron stadium projects?

I think 'a' is probably the way to go since we can mainly rely on existing horizon guides for creating new dashboard repos. On Apr 10, 2017 08:11, "Akihiro Motoki" wrote: > Hi neutrinos (and horizoners), > > As the title says, where would we like to have horizon dashboard for

Re: [Openstack] Neutron in Newton: host_id and device_owner?

Nova may not have set them yet. The port is updated with the host ID and the device ID separately from the port creation in later Nova versions IIRC. On Apr 10, 2017 10:03, "Gregory Golberg" wrote: > Sorry, that should read host AND instance ID (as the device_id was >

Re: [Openstack] LinuxBridge Agent Error

You may be missing whatever package in your distro provides the 'conntrack' util. On Apr 7, 2017 03:52, "Georgios Dimitrakakis" wrote: > Hello, > > I am having an Ocata installation and on my Compute Node the > "linuxbridge-agent.log" file is constantly filling out with

Re: [Openstack-operators] [Openstack] Slow internet speed - Instances with floating IP

I recommend filing an issue against that speedtest-cli script. I noticed the timer seems to be started before the DNS lookup occurs (before call to urlopen). This means any DNS issues impact the measurement of what is supposed to be network throughput. On Apr 4, 2017 13:19, "John Petrini"

Re: [openstack-dev] [neutron] Engine facade

t; about switching for new facade, does the master branch fails the same? > > > > On Mon, Apr 3, 2017 at 8:35 AM Gary Kotton <gkot...@vmware.com> wrote: > > Yes, sorry my bad for not adding it - http://logs.openstack.org/39/ > 452539/2/check/gate-vmware-nsx-python27-ubuntu-xenial/

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

oyment 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 <ke...@benton.pub>

Re: [Openstack] Metadata issue when using allowed address pairs

You won't be able to use the metadata service using an IP that isn't in the fixed_ips list for a port. The way the metadata service associates a request with an instance is only based on that field. So if you want an IP to work with metadata, you'll have to add it to the fixed_ips field for the

[openstack-dev] [neutron] - meeting reminder for today

Hello all, This is just a quick reminder that the team meeting will be at the old time today of 2100 UTC in openstack-meeting due to the revert if the alteration. Cheers __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron] Engine facade

Do you have a link to a traceback? On Apr 2, 2017 09:25, "Gary Kotton" wrote: > Hi, > > The change https://review.openstack.org/#/c/402750/ has broken the > vmware-nsx plugin. I am not sure if this has had effect on any other > decomposed plugins. > > One of the issues that

Re: [openstack-dev] [neutron]: floating IP not being set for L2 GRE packets

ked the network node and the > nf_conntrack_proto_gre kernel module is not loaded. Among the loaded kernel > modules the only ones bearing the ‘nf_conntrack’ prefix are the following: > > > > - nf_conntrack > > - nf_conntrack_ipv4 > > - nf_

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

, see [3]. 1. https://review.openstack.org/452009 2. https://github.com/openstack/neutron/blob/4ed53a880714fd33280064c58e6f91 b9ecd3823e/neutron/api/rpc/handlers/dhcp_rpc.py#L292-L294 3. https://docs.openstack.org/developer/neutron/devref/ provisioning_blocks.html Cheers, Kevin Benton

[openstack-dev] [neutron] - Adding Miguel Lavalle to neutron-drivers team

for deciding what features are feasible for the platform. 1. http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions

Re: [Openstack] Troubles with networking part of openstack

:00 AM, Bartłomiej Solarz-Niesłuchowski < bartlomiej.solarz-niesluchow...@wit.edu.pl> wrote: > W dniu 2017-03-28 o 16:08, Jay Pipes pisze: > >> +kevin benton >> >> On 03/28/2017 07:20 AM, Bartłomiej Solarz-Niesłuchowski wrote: >> >>> Dear

Re: [openstack-dev] [neutron]: floating IP not being set for L2 GRE packets

Do you have the nf_conntrack_proto_gre kernel module loaded on the network node? On Wed, Mar 29, 2017 at 4:37 PM, Anil Rao wrote: > Strangely enough, there is no problem when I make use of a VxLAN tunnel to > communicate between the VM (inside the cloud) and an external

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

ange API behaviour, and > proposal to deprecate the API since there isn't a clear use-case for this > API. > > 2017-03-29 8:59 GMT+08:00 Kevin Benton <ke...@benton.pub>: > >> +1. If there is a use case missing from the neutron API that this allows, >> we can also expand the AP

[openstack-dev] [neutron] drivers meeting back to old time for tomorrow

The drivers meeting will be back to the old time tomorrow while we find a new meeting time that works for everyone[1]. 1. https://review.openstack.org/#/c/448886/ __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

+1. If there is a use case missing from the neutron API that this allows, we can also expand the API to address it. On Mar 28, 2017 07:16, "Matt Riedemann" wrote: > On 3/27/2017 11:42 PM, Rui Chen wrote: > >> Thank you Matt, the background information is important. Seems

[openstack-dev] [neutron] - no drivers meeting today

Hi, Due to time conflicts with the new drivers meeting time, let's not meet this week while we try to find a time that works for everyone. Please take the same block of time to review the RFE's in the triaged state: bugs.launchpad.net/neutron/+bugs?field.status%3Alist=Triaged=rfe

Re: [openstack-dev] Is there some way to run specific unittest in neutron?

tox -epy27 test_ovs_neutron_agent On Mar 22, 2017 22:25, "Sam" wrote: > Hi all, > > I'm working on neutron, I add some code into ovs_neutron_agent.py, and I > extend test_ovs_neutron_agent.py. > > Is there some way to run test_ovs_neutron_agent.py or run related module >

Re: [openstack-dev] [neutron] - adjusting Monday IRC meeting time and drivers meeting time

I'm okay with the revert here that you proposed: https://review.openstack.org/#/c/448886/ On Wed, Mar 22, 2017 at 9:39 PM, Armando M. <arma...@gmail.com> wrote: > > > On 21 March 2017 at 02:00, Kevin Benton <ke...@benton.pub> wrote: > >> Hi everyone, >>

Re: [Openstack] Newton: not able to login via public key

ta to instance. like adding adding keys in new instance ? > > > Thanks and Regards > Amit Uniyal > > On Sun, Mar 5, 2017 at 8:18 PM, Kevin Benton <ke...@benton.pub> wrote: > >> The metadata agent in Neutron is just a proxy that relays metadata >> requests

Re: [openstack-dev] [Openstack] Newton: not able to login via public key

ta to instance. like adding adding keys in new instance ? > > > Thanks and Regards > Amit Uniyal > > On Sun, Mar 5, 2017 at 8:18 PM, Kevin Benton <ke...@benton.pub> wrote: > >> The metadata agent in Neutron is just a proxy that relays metadata >> requests

[openstack-dev] [neutron] - adjusting Monday IRC meeting time and drivers meeting time

be on openstack-meeting-4 to work around other conflicts! https://review.openstack.org/447961 Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [neutron][stadium] - abandoned patches and bug triage

are working on it. This is just an effort to clear out stale work to help prioritize active reviews. Please help triage the bugs that were flipped back to the new status with this query: https://bugs.launchpad.net/neutron/+bugs?field.tag=timeout-abandon Cheers, Kevin Benton

Re: [Openstack] [Neutron] Need L2 Connectivity between the extra two nics between the VMs created on OpensStack

> we plug an Ethernet wire between two hosts (Host1)nic---etherrnetwire--- > nic(Host2). > > > On 16-Mar-2017 4:40 PM, "Kevin Benton" <ke...@benton.pub> wrote: > >> What kind of cable? What protocol will be carried over it? >> >> Traffic between VMs

Re: [Openstack] [Neutron] Need L2 Connectivity between the extra two nics between the VMs created on OpensStack

n is like direct cable connection.​ > > On Wed, Mar 15, 2017 at 11:06 AM, Kevin Benton <ke...@benton.pub> wrote: > >> What type of L2 communication do they need to do? If it's ethernet, then >> just attaching two ports to a network using one of the reference ML2 >> driv

Re: [Openstack] [Neutron] Need L2 Connectivity between the extra two nics between the VMs created on OpensStack

What type of L2 communication do they need to do? If it's ethernet, then just attaching two ports to a network using one of the reference ML2 drivers (i.e. OVS or LinuxBridge) will give you L2 ethernet connectivity via virtual switches. If you want two VMs connected via a direct connect that

[openstack-dev] [neutron][ml2] - driver capability/feature verification framework

it appropriately? We have to decide if we are going to block features based on the enforcement by this framework. Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

hu, Mar 9, 2017 at 12:17 PM, Vikash Kumar < >> vikash.ku...@oneconvergence.com> wrote: >> >> Import path looks OK >> https://github.com/openstack/networking-sfc/blob/master/netw >> orking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L23 >> >>

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

That location was recently changed in the Neutron side.[1] It sounds like sfc has to be updated. 1. https://github.com/openstack/neutron/commit/4ec456d31501f09c68b5c23c488878da32dce75e On Tue, Mar 7, 2017 at 9:41 PM, Vikash Kumar < vikash.ku...@oneconvergence.com> wrote: > Hi Igor, > >This

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

Hi Nate, Thanks for all of your contributions and good luck in your future endeavors! You're always welcome back. :) On Mar 6, 2017 13:15, "Nate Johnston" wrote: All, I have been delaying this long enough... sadly, due to changes in direction I am no longer able to

Re: [Openstack] Newton: not able to login via public key

The metadata agent in Neutron is just a proxy that relays metadata requests to Nova after adding in HTTP headers that identify the instance. On Sun, Mar 5, 2017 at 5:44 AM, Amit Uniyal wrote: > Hi all, > > I have reconfigured everything, working fine but not sure where what

Re: [openstack-dev] [Openstack] Newton: not able to login via public key

The metadata agent in Neutron is just a proxy that relays metadata requests to Nova after adding in HTTP headers that identify the instance. On Sun, Mar 5, 2017 at 5:44 AM, Amit Uniyal wrote: > Hi all, > > I have reconfigured everything, working fine but not sure where what

[openstack-dev] [neutron] - no drivers meeting today and RFEs

Hi, I'm canceling the drivers meeting today due to a last minute conflict for me. If you have a feature you want for Pike, try to get the RFE filed soon otherwise you will risk the chance of us being over-committed for Pike if you submit it later in the cycle. Cheers, Kevin Benton

Re: [openstack-dev] [neutron][address-scope] Questions about l3 address scope

Address scopes allow traffic to go across a router without performing any NAT. The rules you see there ensure that traffic isn't routed directly if it crosses from one address scope to another. On Wed, Mar 1, 2017 at 7:21 AM, zhi wrote: > Hi, all. > > I have some

[openstack-dev] [neutron] - Added Gary and Russell Boden to release team

unblock stadium projects impacted by devstack changes, neutron deprecated item removals, etc. Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

Re: [openstack-dev] [Neutron] Security Worries about Network RBAC

in place to even see keystone alterations when they happen so it would require constant background polling. 1. https://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements Cheers, Kevin Benton On Tue, Feb 28, 2017 at 7:43 PM, Adrian Turjak <a

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

504 gateway timeout" error. > Every time we have to reimage the servers and redeploy from scratch to make > neutron CLI to work again. > > Thanks, > Satya.P > > On Tue, Feb 28, 2017 at 2:18 PM, Kevin Benton <ke...@benton.pub> wrote: >> >> That particul

[openstack-dev] [neutron] PTG Summary

t need to get the testing/documentation/etc fixed up to bring it back into the stadium. Cheers, Kevin Benton __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

12 workers >> for each). Increased rpc_connect_timeout to 180 and rpc_response_timeout >> to 600. As of now it seems these are fine. >> >> Let me know if you have any comments or suggestions about increasing >> those parameter values. >> >> Thanks, >>

Re: [Openstack-operators] [Large deployments] Neutron issues in Openstack Large deployment using DVR

Thanks for following up. Would you mind sharing the parameters you had to tune (db pool limits, etc) just in case someone comes across this same thread in a google search? Thanks, Kevin Benton On Sun, Feb 26, 2017 at 8:48 PM, Satyanarayana Patibandla < satya.patiban...@gmail.com> wrote:

Re: [openstack-dev] [neutron] - Neutron team social Pictures

minathan.smugmug.com/OpenStack-Neutron-PTG-Atlanta-2017/ > > > > Thanks > > Swami > > > > *From:* Kevin Benton [mailto:ke...@benton.pub] > *Sent:* Thursday, February 23, 2017 4:09 PM > *To:* OpenStack Development Mailing List (not for usage questions) < > open

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

k.org> > *Subject:* Re: [openstack-dev] [neutron] - Neutron team social in Atlanta > on Thursday > > > > Count me in. > > > > *From:* Kevin Benton [mailto:ke...@benton.pub <ke...@benton.pub>] > *Sent:* Friday, February 17, 2017 11:19 AM > *To:* openstack-

[openstack-dev] [ptg][neutron] - found micro SD card

Hi all, A micro SD card was found inside of a micro-to-normal size SD card adapter in the Neutron PTG meeting room. If it's yours you can come claim it from me in the Neutron room today or tomorrow. Cheers, Kevin Benton

Re: [Openstack-operators] [neutron] Questions about LinuxBridge Trunk-port implementation

ion ID for the subport. The only place you should see it is if you run tcpdump on the parent port itself. Let me know if any of that needs clarification. Cheers, Kevin Benton On Wed, Feb 22, 2017 at 7:14 AM, Charles 'Boyo <charlesb...@gmail.com> wrote: > Hello all. > > I recently se

Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes

Expanding on that, you get that binding error usually when Neutron thinks it can't wire up the ports on the compute nodes. So ensure that you started the appropriate Neutron agents on the new compute nodes and that they are alive by running 'neutron agent-list'. On Mon, Feb 20, 2017 at 8:14 AM,

<    1   2   3   4   5   6   7   8   9   10   >