Re: [openstack-dev] [nova] NUMA-aware live migration: easy but incomplete vs complete but hard

-IOV VFs would be helped by it. > > Best, > -jay > > [1 I know I'm only one person, but every workload I've seen that > requires pinned CPUs and/or huge pages is a VNF that has been > essentially an ASIC that a telco OEM/vendor has converted into software > and requires the s

Re: [openstack-dev] [placement][nova] Decision time on granular request groups for like resources

> land > > on *different* providers; > > - "any fit": make sure my instance lands *somewhere*. > > [Mooney, Sean K] for completeness we must also support explicit affinity also So the tree cases are "explicit anti-affinity": make s

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

same device. Does this imply that Cyborg can't reprogram the FPGA at all? [Mooney, Sean K] cyborg is intended to support fixed function acclerators also so it will not always be able to program the accelerator. In this case where an fpga is preprogramed with a multi function bitstream

Re: [openstack-dev] [openstack-ansible] Limiting pip wheel builds for OpenStack clients

sually > takes 8-12 minutes, so half the time is being spent there. > > More digging revealed that cassandra-driver is a dependency of python- > monascaclient, which is a dependency of heat. The requirements.txt for > heat drags in all of the clients: > > https://github.com/opens

Re: [openstack-dev] [kuryr][os-vif][nova] os-vif 1.8.0 breaks kuryr-kubernetes

ources > annotations, so to keep backwards compatibility we need > VIFBase.obj_make_compatible able to backport the data back into the > Subnet object. Or be able to load the older data to the newer object. > Anyone have an advice how we should proceed with that issue? [Mooney, Sean K] I belive

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

ine, it's just that you can't assume that anyone from neutron has anything to do with them or even knows what they do. [Mooney, Sean K] as paul said above this has been a requirement for stadium membership for some time. ocata was effectively the first release where this came in to effect https:

Re: [openstack-dev] [etsinfv][gap-04][blazar]: Clarification on the scope of the capacity query

. Everything else > is something that the MANO system user needs to be able to do. This is > why I've called NFV (and particularly MANO/NFVO) a "purpose-built telco > application" in the past. And I don't say that as some sort of put-down > of NFV. I'm just pointing out the real

Re: [openstack-dev] Removing internet access from unit test gates

proxy vars for the ensuing tests. > It might be easiest for you to work out the tox.ini modification on one > project (it'll be self-testing at least) and then once the pilot can be > shown working the conversation with the community becomes a little > easier. [Mooney, Sean K] I may be over

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

cts other than > nova, and I > >trust those not interested/knowledgeable in this area to stay away > > :) [Mooney, Sean K] in the future as we start integrating with neutron we may want to also extend this to neutron-cores with the same understanding that those not interested/kn

Re: [openstack-dev] [ironic] ironic and traits

y plan that uses traits for state information that we have a hangout or videoconference to discuss this? Unfortunately today and tomorrow I'm not able to do a hangout but I can do one on Wednesday any time of the day. [Mooney, Sean K] on the uefi boot topic I did bring up at the ptg that we

[openstack-dev] [nova][neutron] Use neutron's new port binding API

Hi matt You not only currently so I taught I would respond to your question regarding the workflow via email. http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2017-10-18.log.html#t2017-10-18T20:29:02 mriedem 1. conductor asks scheduler for a host20:29

Re: [openstack-dev] vGPUs support for Nova - Implementation

roblems, and more likely bound for > > failure. > > I feel the opposite. IMHO, Nova’s role in life is not to expose all the > quirks of the underlying platform, but rather to provide a useful > abstraction on top of those things. In spite of them. [Mooney, Sean K] I have to agree wi

Re: [openstack-dev] [devstack] zuulv3 gate status; LIBS_FROM_GIT failures

This also broke the legacy-tempest-dsvm-nova-os-vif gate job http://logs.openstack.org/98/508498/1/check/legacy-tempest-dsvm-nova-os-vif/8fdf055/logs/devstacklog.txt.gz#_2017-09-29_14_15_41_961 > -Original Message- > From: Mehdi Abaakouk [mailto:sil...@sileht.net] > Sent: Monday, October

Re: [openstack-dev] vGPUs support for Nova

t; > > > > anyway. My personal feeling is that it is premature. > > > > > > > > > > The nested Resource Provider work is not yet feature-complete > > > > > and requires more reviewer attention. If we continue in the > > > > > dir

Re: [openstack-dev] [os-vif] [passthrough] [VifHostDevice]

pe=direct and launched instances. > It gives the following error - Nova error : "No net device was found > for VF" > Am I missing some other config options? [Mooney, Sean K] no but as I mentioned above ovn is not currently supported. I belive you should have a log message in the neutron

Re: [openstack-dev] [ptg][nova][neutron] modelling network capabilities and capacity in placement and nova neutron port binding negociation.

ote: > > I'm interested in this. I get in to Denver this evening so if we can > > do this session tomorrow or later, that would be super. > > > > Best, > > -jay > > > > On 09/11/2017 01:11 PM, Mooney, Sean K wrote: > >> Hi everyone, > >> > >

[openstack-dev] [ptg][nova][neutron] modelling network capabilities and capacity in placement and nova neutron port binding negociation.

Hi everyone, I'm interested in set up a white boarding session at the ptg to discuss How to model network backend in placement and use that info as part of scheduling This work would also intersect on the nova neutron port binding negotiation Work that is also in flight so I think there is

Re: [openstack-dev] [nova] [neutron] Adding neutron VIF NUMA locality support

at.com>; Karthik Sundaravel > <ksund...@redhat.com>; Mooney, Sean K <sean.k.moo...@intel.com> > Subject: [nova] [neutron] Adding neutron VIF NUMA locality support > > Hey, > > NUMA locality matters as much for NICs used e.g for Open vSwitch as for > SR

Re: [openstack-dev] [nova][scheduling] Can VM placement consider the VM network traffic need?

ge questions) > <openstack-dev@lists.openstack.org> > Cc: Mooney, Sean K <sean.k.moo...@intel.com>; mosh...@mellanox.com > Subject: Re: [openstack-dev] [nova][scheduling] Can VM placement > consider the VM network traffic need? > > On Mon, Sep 4, 2017 at 9:11 PM, Jay Pipes <

Re: [openstack-dev] [nova] [placement] [api] cache headers in placement service

pairs > when we sent out responses, we could then have a conditional GET > handler which checked etags, returning 304 on a cache hit. > At _RC_CACHE changes we could flush the etag cache. [Mooney, Sean K] I agree this is likely needed if caching is used. One of the changes Intel would

Re: [openstack-dev] [neutron][infra] Functional job failure rate at 100%

deal with the > >> kernel bug? > > > > Making our images use non-current kernel packages isn't trivial, but [Mooney, Sean K] so on that it would bre quite trivial to have disk image builder install The linux-image-virtual-hwe-16.04 linux-image-virtual-hwe-1

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

] [vif_plug_ovs] Queries on > VIF_Type VIFHostDevice > > > > -----Original Message- > From: Mooney, Sean K [mailto:sean.k.moo...@intel.com] > Sent: Wednesday, August 9, 2017 6:36 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

= openvswitch to work with > Conntrack. > > So in your case if have SR-IOV nic which doesn't support hardware > offload (but has VF representors port) you will just fallback to the > ovs kernel datapath. [Mooney, Sean K] that is not what will happen with intel nics and I would

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

] [vif_plug_ovs] Queries on VIF_Type > VIFHostDevice > > Hi, > I am experimenting with the os-vif library and stumbled upon this new > VIF type called VIFHostDevice. I have few general queries. TIA. > > 1. How do I create ports with VIF_type as VIFHostDevice? Looking for > the

Re: [openstack-dev] [srv-apl-arch:7353] Re: [nova] Discussions for ivshmem support in OpenStack Nova

> -Original Message- > From: TETSURO NAKAMURA [mailto:nakamura.tets...@lab.ntt.co.jp] > Sent: Thursday, July 27, 2017 2:13 AM > To: Daniel P. Berrange <berra...@redhat.com>; Mooney, Sean K > <sean.k.moo...@intel.com> > Cc: Jay Pipes <jaypi...@gmail.co

Re: [openstack-dev] [nova] Discussions for ivshmem support in OpenStack Nova

ee if nova > > (or at first libvirt community) is acceptable for ivshmem > configuration. > > > > Your advice will be very helpful for our decision-making in our > project. > > I think this is a question that the libvirt community would first need > to weigh in on s

Re: [openstack-dev] [os-vif] 1.6.1 release for pike.

10:35 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [os-vif] 1.6.1 release for pike. > > On 7/18/2017 12:07 PM, Mooney, Sean K wrote: > > Resending with correct subject line > > The real correct subject line tag would be [nova] or [nova][n

[openstack-dev] [os-vif] 1.6.1 release for pike.

Resending with correct subject line From: Mooney, Sean K Sent: Tuesday, July 18, 2017 4:54 PM To: openstack-dev@lists.openstack.org Cc: Jay Pipes <jpi...@mirantis.com>; 'Stephen Finucane' <sfinu...@redhat.com>; Moshe Levi <mosh...@mellanox.com>; 'rbry...@redhat.com' &

[openstack-dev] os-vif 1.6.1 release for pike.

Hi We are approaching the non-client library freeze on Thursday. Below are a list of pending patches that I think will be good to review for inclusion in pike. Should have: Improve OVS Representor Lookup https://review.openstack.org/#/c/484051/ Add support for VIFPortProfileOVSRepresentor

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

above preference? > >> > >> Hi Kevin! > >> > >> I believe the benefit is so that the compute node prefers CPU > >> topologies that do not have hardware threads over CPU topologies > that > >> do include hardware threads. [Mooney, Sean K] if you have no

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

this confined to Nova? > > The Cyborg project (accelerators like FPGAs and some vGPUs) need nested > resource providers to model the relationship between a virtual resource > context against an accelerator and the compute node itself. [Mooney, Sean K] neutron will need to use nested r

Re: [openstack-dev] [nova-scheduler] Get scheduler hint

: > > Thank you a lot! :-). > > Actually, we are also working in parallel to implement the algorithm > with tacker, but for this project we will only use the basic modules in > OpenStack and Heat. [Mooney, Sean K] if you can use heat you can use the server anti affinity filter To cr

Re: [openstack-dev] [intel experimental ci] Is it actually checking anything?

pdk-nfv-networking-xenial/837e59d > >> : FAILURE in 47m 45s (non-voting) > > > > > > As you can see, it says the build succeeded, but all three jobs in > the > > pipeline failed. > > This would happen when CI is voting but all the jobs in a check are > no

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

d not get stuck in merge hell, Ansible will pick up the > Kolla base > templates and merge them with user provided overrides. [Mooney, Sean K] paul is correct here, I did not intend to suggest that kolla-ansible should not Be used to generate and manage config files. I simply

[openstack-dev] [neutron] vhost-user server mode and reconnect

Hi everyone I first proposed a series of patches to enable vhost-user with a Qemu server/ ovs client topology last july before the relevant changes To enable this configuration had been release in ovs with dpdk. Since then ovs 2.6 is out and shipping, (2.7 will be out soon) And all of the

Re: [openstack-dev] ovsdpdk mitaka

Hi In mitaka all support for ovs-dpdk was merged upstream into the standard neutron openvswitch agent and ml2 driver. The networking-ovs-dpdk-agent was removed in liberty and the ml2 driver was removed in mitaka. For mitaka+ networking-ovs-dpdk primarily provides a devstack plugin to compile

Re: [openstack-dev] [poll][kolla] Name of baremetal role/group

host that will run kolla-ansible as > the 'kolla host' or the 'deploy host'. So I worry this will be very > ambiguous (i.e.: "your next step is to run deploy-hosts on the > deployment host to deploy the hosts"). I'd lean more towards > terminology like "target-prep", &

Re: [openstack-dev] [poll][kolla] Name of baremetal role/group

ommend deploy-hosts (I assume this is the bootstrap renamed?) [Mooney, Sean K] hi steve this is not related to the command that is run (kolla-ansible bootstrap-servers) it is related to the name of the ansible role that Is invoked by the kolla-host playbook when you execute the “kolla-ansible boo

[openstack-dev] [poll][kolla] Name of baremetal role/group

Hi I recently introduced a new baremetal role/group which is used as part of the kolla-host playbook. https://github.com/openstack/kolla/tree/master/ansible/roles/baremetal This baremetal role is used to install all the dependencies required to deploy kolla containers on a "baremetal" host. The

Re: [openstack-dev] [kolla] Need clarify about baremetal host group and role in Ansible

nventory does not have any change, so I have some > questions after read through code base: > - Why all-in-one is treated differently. [Mooney, Sean K] in the all in one config the host is also the build host for the docker images. I have not written the code to deploy the build host yet hence why

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

gt; --oneline shows that the first one misses a handful of important > commits that the second one catches. This is the nature of merging to > master." > > What is meant by " tag the merge commit"? How do we tag a git commit on > our master branch? [Mooney, Sean K] cathy i

Re: [openstack-dev] [neutron][networking-ovs-dpdk][dvr] how to use dvr with networking-ovs-dpdk

You can enable dvr today with ovs-dpdk(e.g. netdev datapath) and it will function well enough to pass tempet test but no. Dvr with the netdev datapath has very poor performance. So much so that it is not useable in a production deployment. This is because dvr uses kernel namespace + tap

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

> -Original Message- > From: Assaf Muller [mailto:as...@redhat.com] > Sent: Monday, August 15, 2016 2:50 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Cc: Mooney, Sean K <sean.k.moo...@intel.com

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

policy-like things. > > My vote is the following: > > GET /capabilities <-- returns a set of *actions* or *abilities* that > the user is capable of performing > > GET /traits <-- returns a set of *adjectives* or *attributes* that may > describe a pr

Re: [openstack-dev] [nova] os-capabilities library created

es, and force users to > > upgrade openstack to be able to express requirements on those CPU > flags. > > I don't see how we would be able to expose a particular new CPU flag > *across disparate OpenStack clouds* unless we have some standardized > set of constants that has bee

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

> -Original Message- > From: kostiantyn.volenbovs...@swisscom.com > [mailto:kostiantyn.volenbovs...@swisscom.com] > Sent: Tuesday, August 9, 2016 12:58 PM > To: openstack-dev@lists.openstack.org; Mooney, Sean K > <sean.k.moo...@intel.com> > Subject: R

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

to attach to many networks via its single interface using VLAN tags. [Mooney, Sean K] In this case I take it that you want to create a scenario test that will cover teh vlan aware vms work is that correct? We would like this to be tested in a scenario test in the gate, but in order to do

[openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

Hi just a quick fyi, About 2 weeks ago I did some light testing with the conntrack security group driver and the newly Merged upserspace conntrack support in ovs. I can confirm that at least form my initial smoke tests where I Uses netcat ping and ssh to try and establish connections between two

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

t; provide > any information regarding which resource providers had any available inventory > for a consumer to use. > > Nova could then either have a proxy API call that would add the normal > end-user > interface to that information or completely hide it from end users v

Re: [openstack-dev] [devstack] libvirt/qemu source install plugin.

Kashyap Chamarthy <kcham...@redhat.com>; > mzoel...@linux.vnet.ibm.com; Mooney, Sean K <sean.k.moo...@intel.com> > Subject: Re: [openstack-dev] [devstack] libvirt/qemu source install > plugin. > > All, > > the purpose of the devstack-plugin-tar-installer[

[openstack-dev] [devstack] libvirt/qemu source install plugin.

Hi I recently had the need to test a feature (vhost-user reconnect) that was commit to the qemu source tree a few weeks ago. As there has been no release since then I needed to build from source so to that end I wrote a small devstack plugin to do just that. I was thinking of opening a review

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

indered by super-flexible > description of capabilities. I think having a set of "standard" > capabilities that can be counted on to be cross-OpenStack-cloud > compatible and a set of "dynamic" capabilities that are custom to a > deployment would be a good thing to do. [M

Re: [openstack-dev] [puppet][networking-ovs-dpdk] Request to add puppet-dpdk module

Is there a reason that you are starting a new project instead of contributing to The networking-ovs-dpdk puppet module? Networking-ovs-dpdk was created to host both the integration code with neutron and then deployment tool Support for deploying ovs with dpdk for differnet tools. Currently we

Re: [openstack-dev] [neutron][ovs] The way we deal with MTU

nt implementation with a single br-int (and thus datapath) makes that impossible to pull of with good performance. So there may be other reasons to consider introducing multiple isolated bridges: MTUs, datapath_types, etc. [Mooney, Sean K] I just noticed this now but I just wanted to share some of the

Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla + BiFrost integration

t currently support notifications, so, to learn the > >status of the deployments, you will need to poll the Ironic API (eg, > >"ironic node-list"). > > > > Great, > > Thanks for the feedback. I'll integrate your changes into the sequence >

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

d up with code like [1] that is looking for a particular end of a > > veth pair it just hopes is there so the rules have an effect. [Mooney, Sean K] I really would like to avoid encoding knowledge to Generate the names the same way in both neutron and os-vf/nova or having any Other sp

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

Well in terms of the ovs plugin change for strategy 2 that requires a single function call Here: https://github.com/openstack/os-vif/blob/master/vif_plug_ovs/ovs.py#L109 And here: https://github.com/openstack/os-vif/blob/master/vif_plug_ovs/ovs.py#L84 and one new function in

Re: [openstack-dev] [Neutron][os-vif] Expanding vif capability for wiring trunk ports

penstack.org>; Jay Pipes > <jaypi...@gmail.com>; Maxime Leroy <maxime.le...@6wind.com>; Moshe Levi > <mosh...@mellanox.com>; Russell Bryant <rbry...@redhat.com>; sahid > <sahid.ferdja...@redhat.com>; Mooney, Sean K <sean.k.moo...@intel.com> > Subject:

Re: [openstack-dev] [nova] [scheduler] New filter: AggregateInstanceAffinityFilter

you to review it: > https://review.openstack.org/#/c/314097/ > > Regards. > > PD: I know the non-priority feature spec freeze is today and that's why > I'm asking you to take a look at it. > [Mooney, Sean K] looks like you forgot to disable the automatic footer

[openstack-dev] [kolla] [bifrost] bifrost container poc update

Hi this is an update on where I am with my poc of creating a bifost container for kolla. As of Wednesday evening I have reached my v0 poc goal That goal was to demonstrate it was easy bifrost in a container with little to know changes. This is further broken down as follows. -Create

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

;> Subject: Re: [openstack-dev] [kolla] [bifrost] bifrost container. On Fri, May 6, 2016 at 10:56 AM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Sean, Thanks for taking this on :) I didn't know you had such an AR :) From: "Mooney, Sean K" &l

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

nd two, a management tool for getting machines deployed without needing nova using ironic. [Mooney, Sean K] yes this is correct, bifrost does provide both install playbooks for deploying ironic in standalone mode and a series of playbooks for dynamically enrolling node in ironic and dynamically

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

:) I didn't know you had such an AR :) [Mooney, Sean K] well if other want to do the work that ok with me too but I was planning on deploying bifrost At home again anyway so I taught I might as well try to automate the process while im at it. From: "Mooney, Sean K" <sean

[openstack-dev] [kolla] [bifrost] bifrost container.

Hi everyone. Following up on my AR from the kolla host repository session https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kolla-host-repo I started working on creating a kolla bifrost container. Are some initial success it have hit a roadblock with the current install playbook

[openstack-dev] [neutron] dvr with ovs-dpdk.

Hi If any of the dvr team are around I would love to Meet with ye to discuss how to make dvr work efficiently when using ovs with the dpdk datapath. Ill be around the Hilton all day and am currently in room 400 but if anyone wants to meetup to Discuss this let me know Regards Seán

Re: [openstack-dev] [devstack] openstack client slowness / client-as-a-service

7 PM, Monty Taylor wrote: > > Rather than ditching python for something like go, I'd rather put > > together a CLI with no plugins and that only depended on keystoneauth > > and os-client-config as libraries. No? [Mooney, Sean K] that is similar to how shade works correct.

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, March 23, 2016 8:01 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of > physical_device_mappings > > +tags for stable and nova > > Hi

[openstack-dev] [nova] stuck review, mtu incorrectly set on vhost-user port prevents vm booting.

Hi everyone I opened a bug back in January to correct an issue with vhost-user Related to setting the mtu on the interface. The recent changes in nova and neutron to change the default mtu value from 0 to 1500 Are a direct trigger for this bug resulting in an inability to boot vms that use

Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron

.com>; m...@mattfischer.com; Mooney, > Sean K <sean.k.moo...@intel.com> > Subject: Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron > > Hi MichalX, Sean, > > Building from sources is possible, but it will be more stable, if you > will use packaging system f

Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron

...@mattfischer.com > Cc: Mooney, Sean K <sean.k.moo...@intel.com>; Czesnowicz, Przemyslaw > <przemyslaw.czesnow...@intel.com> > Subject: Re: [openstack-dev] [puppet] adding ovs dpdk agent into neutron > > > > On 03/02/2016 02:48 PM, Ptacek, MichalX wrote: > &

Re: [openstack-dev] [nova] solving API case sensitivity issues

> -Original Message- > From: James Bottomley [mailto:james.bottom...@hansenpartnership.com] > Sent: Wednesday, February 24, 2016 5:46 PM > To: Sean Dague ; openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] solving API case sensitivity issues > > On

Re: [openstack-dev] Shovel (RackHD/OpenStack)

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, January 13, 2016 8:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Shovel (RackHD/OpenStack) > > On 01/13/2016 03:28 PM, Keedy, Andre wrote: > > Hi All, I'm pleased to

Re: [openstack-dev] [nova][neutron][os-vif] os-vif core review team membership

> -Original Message- > From: Moshe Levi [mailto:mosh...@mellanox.com] > Sent: Tuesday, January 12, 2016 4:23 PM > To: Russell Bryant; Daniel P. Berrange; openstack- > d...@lists.openstack.org > Cc: Jay Pipes; Mooney, Sean K; Sahid Orentino Ferdjaoui; Maxime Leroy &g

Re: [openstack-dev] [networking-ovs-dpdk] availability

Hi, it is possible to install and configure networking-ovs-dpdk without Using the devstack plugin however we currently do not have documentation for this process. The openstack configuration required to enable the ovs agent and ml2 driver provided by networking-ovs-dpdk Is minimal. The

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

. because if i exactly use the local.confs as in example the controller was vlan and compute is taking as vxlan for the ml2 config. And please find all the errors present in the compute and controller. Thanks Praveen On Thu, Nov 26, 2015 at 5:58 PM, Mooney, Sean K <sean.k.moo...@intel.

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

n.mank...@6wind.com>> wrote: Hi Sean, Thanks for the reply. Please find the logs attached. ovs-dpdk is correctly running in compute. Thanks Praveen On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote: Hi would you be able

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

t; > Thanks > Praveen > > On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K > <sean.k.moo...@intel.com> wrote: > Hi would you be able to attach the > > n-cpu log form the computenode and the > > n-sch and q-svc lo

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

Hi would you be able to attach the n-cpu log form the computenode and the n-sch and q-svc logs for the controller so we can see if there is a stack trace relating to the vm boot. Also can you confirm ovs-dpdk is running correctly on the compute node by running sudo service ovs-dpdk status

Re: [openstack-dev] [networking-ovs-dpdk]

.rst Regards Sean. From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com] Sent: Tuesday, November 24, 2015 12:42 PM To: Mooney, Sean K Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [networking-ovs-dpdk] Hi All, I also found another error wh

Re: [openstack-dev] [networking-ovs-dpdk]

Just wanted to confirm that my setup has ovs-dpdk running. Regards, Prathyusha On Wed, Nov 18, 2015 at 7:23 PM, James Page <james.p...@ubuntu.com<mailto:james.p...@ubuntu.com>> wrote: Hi Sean On Wed, Nov 18, 2015 at 12:30 PM, Mooney, Sean K <sean.k.moo...@intel.

Re: [openstack-dev] [networking-ovs-dpdk]

and it doesn't hang at creating external bridge anymore. All processes(nova-api, neutron, ovs-vswitchd, etc) did start. Thanks, Prathyusha On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote: We mainly test with 2M hugepages no

Re: [openstack-dev] [networking-ovs-dpdk]

conf.db and db.sock exist. So why ovs-vswitchd is failing to start??? Am I missing something??? Thanks, Prathyusha On Mon, Nov 16, 2015 at 4:39 PM, Mooney, Sean K <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote: Hi Yes sorry for the delay in responding to you and sa

Re: [openstack-dev] [networking-ovs-dpdk]

41 poll_s pts/3 03:42:31 ovs-vswitchd So now ovs-vswitchd runs unlike the last time. I really dont understand where am missing out.... On Tue, Nov 17, 2015 at 5:14 PM, Mooney, Sean K <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote: Can you provide the ovs-vswitchd

Re: [openstack-dev] [networking-ovs-dpdk]

ngare <samtarang...@gmail.com<mailto:samtarang...@gmail.com>> wrote: Hi Sean, Thanks for replying back, response inline. On Mon, Nov 9, 2015 at 8:24 PM, Mooney, Sean K <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote: > Hi > Can you provide some m

Re: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

To use the ovs-appctl application you have to specify the socket path to the ovs-vswitchd process. ovs-appctl -t /var/run/openvswitch/ list-commands e.g. ovs-appctl -t /var/run/openvswitch/ovs-vswitchd.10110.ctl list-commands From: Hui Xiang [mailto:hui.xi...@canonical.com] Sent: Monday,

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Can you provide some more information regarding your deployment? Can you check which kernel you are using. uname -a If you are using a 3.19 kernel changes to some locking code in the kennel broke synchronization dpdk2.0 and requires dpdk 2.1 to be used instead. In general it is not

Re: [openstack-dev] [Dpdk-ovs] [networking-ovs-dpdk]networking-ovs-dpdk configuration on devstack

Hi this mailing list if for OVDK the intel for ovs with the dpdk dpif datapath. The networking-ovs-dpdk repo support ovs from openvswitch.org with the dpdk netdev datapath. Issue and support should be directed to the openstack dev mailing list (openstack-dev@lists.openstack.org) with the

Re: [openstack-dev] [networking-ovs-dpdk]

Hello When set OVS_DPDK_MODE=controller_ovs You are disabling install of ovs-dpdk on the contoler node and only installing mechanism driver. If you want to install ovs-dpdk on the controller node you should set this value as follows OVS_DPDK_MODE=controller_ovs_dpdk See

Re: [openstack-dev] [networking-ovs-dpdk]

Integration with packsack is not currently supported. We currently have the first step( a puppet module to install ovs-dpdk) under review. At present we are not directly targeting packstack support but if anyone wants to add support It would be welcomed. At present devstack is the only fully

Re: [openstack-dev] [Neutron] revert default review branch to master

, 2015 at 5:58 PM, Jeremy Stanleyfu...@yuggoth.org wrote: On 2015-08-17 22:39:56 + (+), Mooney, Sean K wrote: [...] Assuming this was not intentional I have opened a bug and submitted a patch to revert this change. [...] Fix https://review.openstack.org/213843 is already winding

[openstack-dev] [Neutron] revert default review branch to master

Hi I just noticed the default review branch for neutron has been updated to the feature/qos branch Assuming this was not intentional I have opened a bug and submitted a patch to revert this change. https://bugs.launchpad.net/neutron/+bug/1485788 https://review.openstack.org/#/c/213908/

Re: [openstack-dev] [Neutron] service chaining feature development meeting at 10am pacific time June 11

Hi can anyone provide a link to today's irc meeting logs? Looking at http://eavesdrop.openstack.org/meetings/ I cannot see a Neutron_Service_Chaining_meeting directory Are the logs being stored in http://eavesdrop.openstack.org/meetings/service_chaining/2015/ ? If so the logs for today's

Re: [openstack-dev] [new][cloudpulse] Announcing a project to HealthCheck OpenStack deployments

Will cloudpulse be under the governance of the OpenStack Telemetry program Or will this be an independent StackFoge repository? I think there would be great value in having cloud monitoring or monitoring as a service In the telemetry program. Regards Sean. -Original Message- From:

Re: [openstack-dev] [nova] [libvirt] enabling per node filtering of mempage sizes

, Dec 02, 2014 at 07:44:23PM +, Mooney, Sean K wrote: Hi all I have submitted a small blueprint to allow filtering of available memory pages Reported by libvirt. Can you address this with aggregate? this will also avoid to do something specific in the driver libvirt. Which will have

Re: [openstack-dev] [nova] [libvirt] enabling per node filtering of mempage sizes

Selecting the host aggregate directly. Regards Sean. -Original Message- From: Daniel P. Berrange [mailto:berra...@redhat.com] Sent: Wednesday, December 03, 2014 1:38 PM To: Mooney, Sean K Cc: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova

[openstack-dev] [nova] [libvirt] enabling per node filtering of mempage sizes

Hi all I have submitted a small blueprint to allow filtering of available memory pages Reported by libvirt. https://blueprints.launchpad.net/nova/+spec/libvirt-allowed-mempage-sizes I believe that this change is small enough to not require a spec as per

Re: [openstack-dev] [all] The future of the integrated release

I would have to agree with Thomas. Many organizations have already worked out strategies and have processes in place to cover contributing to OpenStack which Cover all official project. Contributing to additional non-OpenStack projects may introduce additional barriers in large Organizations

Re: [openstack-dev] [nova][Spec Freeze Exception]Support dpdkvhost in ovs vif bindings

the issues raised. Regards Sean. From: Czesnowicz, Przemyslaw Sent: Friday, July 18, 2014 1:03 PM To: openstack-dev@lists.openstack.org Cc: Mooney, Sean K; Hoban, Adrian Subject: [openstack-dev][nova][Spec Freeze Exception]Support dpdkvhost in ovs vif bindings Hi Nova Cores, I would like

Re: [openstack-dev] [Neutron] [Spec freeze exception] ml2-use-dpdkvhost

-dev] [Neutron] [Spec freeze exception] ml2-use-dpdkvhost On Mon, Jul 21, 2014 at 10:04 AM, Mooney, Sean K sean.k.moo...@intel.com wrote: Hi I would like to propose https://review.openstack.org/#/c/107797/1/specs/juno/ml2-use-dpdkvhost .rst for a spec freeze exception. https

[openstack-dev] [Neutron] [Spec freeze exception] ml2-use-dpdkvhost

Hi I would like to propose https://review.openstack.org/#/c/107797/1/specs/juno/ml2-use-dpdkvhost.rst for a spec freeze exception. https://blueprints.launchpad.net/neutron/+spec/ml2-use-dpdkvhost This blueprint adds support for the Intel(R) DPDK Userspace vHost port binding to the Open

  1   2   >