Re: [openstack-dev] [nova]can someone help me? when I use cmd nova migration-list error.

Perhaps a bug-maintainer should to update the status, the bug is not related to python-novaclient and it is not tried yet. Thanks a lot, s. - Original Message - From: li zheming lizhemin...@gmail.com To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] hugepage support

Hi Anil, I have checked on the code and it looks it is not possible to enable this feature for the guest. We are running kvm through libvirt and it support this option: http://libvirt.org/formatdomain.html It could be an interesting feature. may be by an option readed from the image

Re: [openstack-dev] [nova] hugepage support

I have started an implementation in review: https://review.openstack.org/#/c/69148/ - Original Message - From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Saturday, January 25, 2014 5:56

[openstack-dev] [nova] bp proposal: libvirt-resize-disk-down

Greetings, A blueprint is being discussed about the disk resize down feature of libvirt driver. https://blueprints.launchpad.net/nova/+spec/libvirt-resize-disk-down The current implementation does not handle disk resize down and just skips the step during a resize down of the instance. I'm

Re: [openstack-dev] [nova] bp proposal: libvirt-resize-disk-down

For metering/usage purposes, does the old size of ephemeral disk continue to be shown in usage records, or does the size of the disk in the newly-selected instance type (flavor) get used? If the former, then this would be an avenue for users to Get more disk space than they are paying for.

Re: [openstack-dev] [nova] bp proposal: libvirt-resize-disk-down

In case it hasn't been considered yet, shrinking a filesystem can result in terrible fragmentation. The block allocator in resize2fs does not do a great job of handling this case. The result will be a very non-optimal file layout and measurably worse performance, especially for drives with

Re: [openstack-dev] [nova] bp proposal: libvirt-resize-disk-down

, 2014 8:13:57 AM Subject: Re: [openstack-dev] [nova] bp proposal: libvirt-resize-disk-down On Thu, Jan 30, 2014 at 02:59:45PM +, sahid wrote: Greetings, A blueprint is being discussed about the disk resize down feature of libvirt driver. https://blueprints.launchpad.net/nova/+spec

[openstack-dev] [nova] about the bp cpu-entitlement

Greetings, I saw a really interesting blueprint about cpu entitlement, it will be targeted for icehouse-3 and I would like to get some details about the progress?. Does the developer need help? I can give a part of my time on it.

Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th February

+1 - Original Message - From: John Garbutt j...@johngarbutt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Friday, February 7, 2014 9:12:42 AM Subject: Re: [openstack-dev] [Nova] Bug Triage Day Proposal - Friday 7th

[openstack-dev] [Nova][Gate] qemu: linux kernel too old to load a ram disk

Hello, It looks since 12 hours the gate fails in 100% of case because an error with libvirt (logs/libvirtd.txt): qemu: linux kernel too old to load a ram disk Bug reported on openstack-ci: https://bugs.launchpad.net/openstack-ci/+bug/1280142 Fingerprint:

Re: [openstack-dev] [nova] Should we limit the disk IO bandwidth in copy_image while creating new instance?

It could be a good idea but as Sylvain said how to configure this? Then, what about using scp instead of rsync for a local copy? - Original Message - From: Wangpan hzwang...@corp.netease.com To: OpenStack Development Mailing List openstack-dev@lists.openstack.org Sent: Friday, February

[openstack-dev] [Nova] bp proposal: filter based on the load averages of the host

Greetings, I would like to add a new filter based on the load averages. This filter will use the command uptime and will provides an option to choice a period between 1, 5, and 15 minutes and an option to choice the max load average (a float between 0 and 1). Why: During a scheduling it could

Re: [openstack-dev] [Nova] bp proposal: filter based on the load averages of the host

To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Saturday, February 15, 2014 12:54:52 AM Subject: Re: [openstack-dev] [Nova] bp proposal: filter based on the load averages of the host On Fri, 2014-02-14 at 15:29 +, sahid wrote: Greetings

Re: [openstack-dev] [Nova] bp proposal: filter based on the load averages of the host

I have implemented a new monitor based on the system load averages https://review.openstack.org/#/c/74014/1 What do you think? s. - Original Message - From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [nova] bp proposal: New per-aggregate filters targeted for icehouse-3

://review.openstack.org/#/c/65474/ Thanks a lot, s. - Original Message - From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Tuesday, January 28, 2014 5:14:49 PM Subject: [openstack-dev] [nova] bp proposal

[openstack-dev] [nova] bugs that needs to be reviewed

Greetings, There are two fixes for bugs that need to be reviewed. One for the feature shelve instance and the other one for the API to get the list of migrations in progress. These two bugs are marked to high and medium because they broke feature. The code was push several months ago, if some

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

Sorry for the late of this response, I'm currently working on a project called Warm. https://wiki.openstack.org/wiki/Warm It is used as a standalone client and try to deploy small OpenStack environments from Yzml templates. You can find some samples here: https://github.com/sahid/warm

Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

be addressed by Heat using HOT templates? Regards, Thomas sahid sahid.ferdja...@cloudwatt.com wrote on 18/03/2014 12:56:47: From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: 18/03/2014 12:59 Subject

[openstack-dev] pep8 gating fails due to tools/config/check_uptodate.sh

Hello all, It looks 100% of the pep8 gate for nova is failing because of a bug reported, we probably need to mark this as Critical. https://bugs.launchpad.net/nova/+bug/1268614 Ivan Melnikov has pushed a patchset waiting for review: https://review.openstack.org/#/c/66346/

[openstack-dev] [nova] FFE request serial-ports

Hello, I would like to request a FFE for 4 changesets to complete the blueprint serial-ports. Topic on gerrit: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/serial-ports,n,z Blueprint on launchpad.net:

Re: [openstack-dev] [nova] How to connect to a serial port of an instance via websocket?

token that should be used with a websocket client to read/write on the stream. Considering the service nova-serialproxy is running and well configured you can use this simple test purpose client to connect yourself on the URL returned by the API: https://gist.github.com/sahid

Re: [openstack-dev] questions on result of diagnostics on libvirt

On Tue, Nov 11, 2014 at 01:59:12PM +0800, Chen CH Ji wrote: see the error value of diagnostics is huge , but I don't think my disk is that bad ... is this wrong info or wrong usage of libvirt? Also, all the disk has same error number curious me , any guide ? Considering you are using

Re: [openstack-dev] [nova] Proposal new hacking rules

On Thu, Nov 20, 2014 at 02:00:11PM -0800, Joe Gordon wrote: On Thu, Nov 20, 2014 at 9:49 AM, Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com wrote: This is something we can call nitpiking or low priority. This all seems like nitpicking for very little value. I think

Re: [openstack-dev] [nova] Proposal new hacking rules

accepted by Nova community first before to think about other projects ;) Jordan - Original Message - From: Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Sent: Friday

Re: [openstack-dev] [nova] Proposal new hacking rules

On Fri, Nov 21, 2014 at 05:23:28PM -0500, Matthew Treinish wrote: On Fri, Nov 21, 2014 at 04:15:07PM -0500, Sean Dague wrote: On 11/21/2014 01:52 PM, Matthew Treinish wrote: On Fri, Nov 21, 2014 at 07:15:49PM +0100, jordan pittier wrote: Hey, I am not a Nova developer but I still have

Re: [openstack-dev] [nova] Proposal new hacking rules

On Fri, Nov 21, 2014 at 10:30:59AM -0800, Joe Gordon wrote: On Fri, Nov 21, 2014 at 8:57 AM, Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com wrote: On Thu, Nov 20, 2014 at 02:00:11PM -0800, Joe Gordon wrote: On Thu, Nov 20, 2014 at 9:49 AM, Sahid Orentino Ferdjaoui sahid.ferdja

Re: [openstack-dev] [Nova] Spring cleaning nova-core

On Fri, Dec 05, 2014 at 01:41:59PM +, Daniel P. Berrange wrote: On Fri, Dec 05, 2014 at 11:05:28AM +1100, Michael Still wrote: One of the things that happens over time is that some of our core reviewers move on to other projects. This is a normal and healthy thing, especially as nova

Re: [openstack-dev] [hacking] proposed rules drop for 1.0

On Tue, Dec 09, 2014 at 06:39:43AM -0500, Sean Dague wrote: I'd like to propose that for hacking 1.0 we drop 2 groups of rules entirely. 1 - the entire H8* group. This doesn't function on python code, it functions on git commit message, which makes it tough to run locally. It also would be a

Re: [openstack-dev] [nova] Kilo specs review day

On Thu, Dec 11, 2014 at 08:41:49AM +1100, Michael Still wrote: Hi, at the design summit we said that we would not approve specifications after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve had a lot of specifications proposed this cycle (166 to my count), and haven’t kept

Re: [openstack-dev] anyway to pep8 check on a specified file

On Mon, Dec 15, 2014 at 09:37:23AM +, Daniel P. Berrange wrote: On Mon, Dec 15, 2014 at 05:04:59PM +0800, Chen CH Ji wrote: tox -e pep8 usually takes several minutes on my test server, actually I only changes one file and I knew something might wrong there anyway to only check that

Re: [openstack-dev] [nova] Volunteer for BP 'Improve Nova KVM IO support'

On Fri, Dec 19, 2014 at 11:36:03AM +0800, Rui Chen wrote: Hi, Is Anybody still working on this nova BP 'Improve Nova KVM IO support'? https://blueprints.launchpad.net/nova/+spec/improve-nova-kvm-io-support This feature is already in review, since it is only to add an option to libvirt I

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

On Wed, Feb 04, 2015 at 04:30:32PM +, Matthew Booth wrote: I've spent a few hours today reading about Galera, a clustering solution for MySQL. Galera provides multi-master 'virtually synchronous' replication between multiple mysql nodes. i.e. I can create a cluster of 3 mysql dbs and read

Re: [openstack-dev] problems with huge pages and libvirt

On Tue, Feb 03, 2015 at 03:05:24PM +0100, Sahid Orentino Ferdjaoui wrote: On Mon, Feb 02, 2015 at 11:44:37AM -0600, Chris Friesen wrote: On 02/02/2015 11:00 AM, Sahid Orentino Ferdjaoui wrote: On Mon, Feb 02, 2015 at 10:44:09AM -0600, Chris Friesen wrote: Hi, I'm trying to make use

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 10:44:09AM -0600, Chris Friesen wrote: Hi, I'm trying to make use of huge pages as described in http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/virt-driver-large-pages.html;. I'm running kilo as of Jan 27th. I've allocated 1 2MB pages on a

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 11:44:37AM -0600, Chris Friesen wrote: On 02/02/2015 11:00 AM, Sahid Orentino Ferdjaoui wrote: On Mon, Feb 02, 2015 at 10:44:09AM -0600, Chris Friesen wrote: Hi, I'm trying to make use of huge pages as described in http://specs.openstack.org/openstack/nova-specs

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

On Thu, Feb 05, 2015 at 09:56:21AM +, Matthew Booth wrote: On 04/02/15 19:04, Jay Pipes wrote: On 02/04/2015 12:05 PM, Sahid Orentino Ferdjaoui wrote: On Wed, Feb 04, 2015 at 04:30:32PM +, Matthew Booth wrote: I've spent a few hours today reading about Galera, a clustering solution

Re: [openstack-dev] [nova] memory reporting for huge pages

On Wed, Feb 04, 2015 at 05:35:55PM -0600, Chris Friesen wrote: As part of https://blueprints.launchpad.net/nova/+spec/virt-driver-large-pages; we have introduced the ability to specify based on flavor/image that we want to use huge pages. Yes, to add more information; When using image

Re: [openstack-dev] problems with huge pages and libvirt

On Mon, Feb 02, 2015 at 11:51:47AM -0500, Jay Pipes wrote: This is a bug that I discovered when fixing some of the NUMA related nova objects. I have a patch that should fix it up shortly. Never seen this issue, could be great to have a bug repported. This is what happens when we don't have

Re: [openstack-dev] How to debug test cases in Openstack

On Fri, Jan 16, 2015 at 11:07:07AM +0530, Abhishek Talwar/HYD/TCS wrote: Hi, I have been trying to debug the test cases in OpenStack, but I am not getting successful with it. So if someone can help me with that. The last response from the dev-list was to use $ ./run_tests.sh -d [test

Re: [openstack-dev] [nova] serial-console *replaces* console-log file?

On Fri, Jan 09, 2015 at 09:15:39AM +0800, Lingxian Kong wrote: There is an excellent post describing this, for your information: http://blog.oddbit.com/2014/12/22/accessing-the-serial-console-of-your-nova-servers/ Good reference, you can also get some information here:

Re: [openstack-dev] [nova] bp serial-ports *partly* implemented?

On Fri, Feb 20, 2015 at 06:03:46PM +0100, Markus Zoeller wrote: It seems to me that the blueprint serial-ports[1] didn't implement everything which was described in its spec. If one of you could have a look at the following examples and help me to understand if these observations are

Re: [openstack-dev] [nova] bp serial-ports *partly* implemented?

On Tue, Feb 24, 2015 at 04:19:39PM +0100, Markus Zoeller wrote: Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com wrote on 02/23/2015 11:13:12 AM: From: Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev

[openstack-dev] [stable] freeze exception

Hello, A request to get an exception for a fix related to PCI-Passthough. The backport seems to be reasonable and not invincible and the code is well covered by tests. The impact of this fix is to make compatible the config option 'pci_passthrough_whitelist' from icehouse to juno.

Re: [openstack-dev] [stable] freeze exception

On Fri, Apr 03, 2015 at 09:37:30AM +0200, Sahid Orentino Ferdjaoui wrote: Hello, A request to get an exception for a fix related to PCI-Passthough. The backport seems to be reasonable and not invincible and the code is well covered by tests. s/invincible/invasive/ The impact of this fix

[openstack-dev] [nova][oslo] RPC Asynchronous Communication

Hi, The primary point of this expected discussion around asynchronous communication is to optimize performance by reducing latency. For instance the design used in Nova and probably other projects let able to operate ascynchronous operations from two way. 1. When communicate between

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

On Wed, Jun 03, 2015 at 10:22:59AM +0200, Julien Danjou wrote: On Wed, Jun 03 2015, Robert Collins wrote: We *really* don't need a technical solution to a social problem. I totally agree. The trust issues is not going to be solve with a tool. +1 I can not believe people will commit

Re: [openstack-dev] Proposal of nova-hyper driver

On Sun, Jun 21, 2015 at 07:18:10PM +0300, Joe Gordon wrote: On Fri, Jun 19, 2015 at 12:55 PM, Peng Zhao p...@hyper.sh wrote: Hi, all, I would like to propose nova-hyper driver: https://blueprints.launchpad.net/nova/+spec/nova-hyper. - What is Hyper? Put simply, Hyper is a

Re: [openstack-dev] [Nova] The unbearable lightness of specs

On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote: Hey Nova, I'll cut to the chase and keep this email short for brevity and clarity: Specs don't work! They do nothing to facilitate good design happening, if anything they prevent it. The process layered on top with only a

Re: [openstack-dev] [nova][api] New micro-version needed for api bug fix or not?

On Fri, May 29, 2015 at 08:47:01AM +0200, Jens Rosenboom wrote: As the discussion in https://review.openstack.org/179569 still continues about whether this is just a bug fix, or an API change that will need a new micro version, maybe it makes sense to take this issue over here to the ML.

Re: [openstack-dev] [nova] correct API for getting image metadata for an instance ?

On Wed, May 27, 2015 at 02:59:10PM +0100, Daniel P. Berrange wrote: As part of the work to object-ify the image metadata dicts, I'm looking at the current way the libvirt driver fetches image metadata for an instance, in cases where the compute manager hasn't already passed it into the virt

Re: [openstack-dev] [Nova][libvirt] Understand why we lookup libvirt domains by instance name

On Thu, May 21, 2015 at 10:23:35AM +0100, Daniel P. Berrange wrote: On Wed, May 20, 2015 at 03:01:50PM -0700, Michael Still wrote: I note that we use instance.name to lookup the libvirt domain a bunch in the driver. I'm wondering why we don't just use instance.uuid all the time -- the code

Re: [openstack-dev] [nova][oslo] RPC Asynchronous Communication

On Fri, May 08, 2015 at 09:13:59AM -0400, Doug Hellmann wrote: Excerpts from Joe Gordon's message of 2015-05-07 17:43:06 -0700: On May 7, 2015 2:37 AM, Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com wrote: Hi, The primary point of this expected discussion around asynchronous

Re: [openstack-dev] [Nova][libvirt] Understand why we lookup libvirt domains by instance name

On Thu, May 21, 2015 at 09:11:57AM -0700, Michael Still wrote: On Thu, May 21, 2015 at 7:49 AM, Sahid Orentino Ferdjaoui sahid.ferdja...@redhat.com wrote: On Thu, May 21, 2015 at 10:23:35AM +0100, Daniel P. Berrange wrote: On Wed, May 20, 2015 at 03:01:50PM -0700, Michael Still wrote: I

Re: [openstack-dev] [nova] Thoughts on things that don't make freeze cutoffs

On Tue, Aug 04, 2015 at 12:54:34PM +0200, Thierry Carrez wrote: John Garbutt wrote: [...] Personally I find a mix of coding and reviewing good to keep a decent level of empathy and sanity. I don't have time for any coding this release (only a bit of documenting), and its not something I

Re: [openstack-dev] [nova] Create a network filter

On Thu, Jul 23, 2015 at 04:44:01PM +0200, Silvia Fichera wrote: Hi all, I'm using OpenStack together with OpenDaylight to add a network awareness feature to the scheduler. I have 3 compute nodes (one of these is also the Openstack Controller) connected by a openvswitch controlled by

Re: [openstack-dev] [nova][libvirt] Deprecating the live_migration_flag and block_migration_flag config options

On Mon, Jan 04, 2016 at 09:12:06PM +, Mark McLoughlin wrote: > Hi > > commit 8ecf93e[1] got me thinking - the live_migration_flag config > option unnecessarily allows operators choose arbitrary behavior of the > migrateToURI() libvirt call, to the extent that we allow the operator > to

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

.com > ><mailto:mrie...@linux.vnet.ibm.com>>> wrote: > > > > Nova has had some long-standing bugs that Sahid is trying > >to fix > > here [1]. > > > > You can create a network in neutron

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On Tue, Jul 12, 2016 at 06:45:03PM +0200, Markus Zoeller wrote: > On 12.07.2016 17:39, Sahid Orentino Ferdjaoui wrote: > > On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: > >> After closing the old (>18months) bug reports nobody is working on a few > &g

Re: [openstack-dev] [nova] focused review pipeline of bug fix changes?

On Tue, Jul 12, 2016 at 09:59:12AM +0200, Markus Zoeller wrote: > After closing the old (>18months) bug reports nobody is working on a few > days ago [1], it became clear that the "in progress" reports are the > majority [2]. After asking Gerrit how long it usually takes to get a fix > merged [3],

Re: [openstack-dev] [nova] Do we need a config option for use_usb_tablet/pointer_model?

On Fri, Jun 17, 2016 at 03:36:53PM -0500, Matt Riedemann wrote: > I was reviewing the last change in this blueprint series today: > > https://review.openstack.org/#/c/174854/ > > And started to question why we even have a config option for this anymore. > The blueprint didn't have a spec but

[openstack-dev] [Nova] FFE Request "libvirt-emulator-threads-policy"

I'm requesting a FFE for the libvirt driver blueprint/spec to isolate emulator threads [1]. The code is up and ready since Mid of November 2016. [1] https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/libvirt-emulator-threads-policy s.

Re: [openstack-dev] realtime kvm cpu affinities

On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote: > Am Tue, 27 Jun 2017 09:44:22 +0200 > schrieb Sahid Orentino Ferdjaoui <sferd...@redhat.com>: > > > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > > > Am Sun, 25 Jun 2017 10:0

[openstack-dev] [nova] allow vfs to be trusted

Hello Matt, There is a serie of patches pushed upstream [0] to configure virtual functions of a SRIOV device to be "trusted". That is to fix an issue when bonding two SRIOV nics in failover mode, basically without that capabability set to the VFs assigned, the guest would not have the privilege

Re: [openstack-dev] realtime kvm cpu affinities

On Wed, Jun 21, 2017 at 12:47:27PM +0200, Henning Schild wrote: > Am Tue, 20 Jun 2017 10:04:30 -0400 > schrieb Luiz Capitulino : > > > On Tue, 20 Jun 2017 09:48:23 +0200 > > Henning Schild wrote: > > > > > Hi, > > > > > > We are using

Re: [openstack-dev] realtime kvm cpu affinities

On Mon, Jun 26, 2017 at 12:12:49PM -0600, Chris Friesen wrote: > On 06/25/2017 02:09 AM, Sahid Orentino Ferdjaoui wrote: > > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: > > > On 06/23/2017 09:35 AM, Henning Schild wrote: > > > > Am Fri, 23 Jun 2017

Re: [openstack-dev] realtime kvm cpu affinities

On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > Am Sun, 25 Jun 2017 10:09:10 +0200 > schrieb Sahid Orentino Ferdjaoui <sferd...@redhat.com>: > > > On Fri, Jun 23, 2017 at 10:34:26AM -0600, Chris Friesen wrote: > > > On 06/23/2017 09:35 AM, Henning

Re: [openstack-dev] [nova] allow vfs to be trusted

On Wed, Jun 07, 2017 at 11:23:23AM -0500, Matt Riedemann wrote: > On 6/7/2017 8:28 AM, Sahid Orentino Ferdjaoui wrote: > > I still have a question do > > I need to provide a spec for this? > > There is a spec for it: > > https://review.openstack.org/#/c/397932/

Re: [openstack-dev] [nova] allow vfs to be trusted

On Fri, Apr 28, 2017 at 10:52:47AM +0200, Sahid Orentino Ferdjaoui wrote: > Hello Matt, > > There is a serie of patches pushed upstream [0] to configure virtual > functions of a SRIOV device to be "trusted". > > That is to fix an issue when bonding two SRIOV nics i

[openstack-dev] [nova] bug/1686116 - using more than 6 scsi disks with virtio-scsi

Hello, We have an issue in Nova which makes no possible to configure more than 6 SCSI disks with virtio-scsi where the controller could handle up to 256 disks. The fix has been reviewed by Stephen Finucane (thanks to him) and some other contributors (thanks to them), any chance to get one core

[openstack-dev] [nova] overhead_pin_set option

Some workloads require to have hypervisor overheads to be isolated from the set of pCPUs running guest vCPUs threads. For libvirt driver we have introduced the emulator threads placements which provides an option to reserve an additional host CPU per guest to pin the emulator threads on [0]. To

Re: [openstack-dev] vGPUs support for Nova

On Mon, Sep 25, 2017 at 09:29:25AM -0500, Matt Riedemann wrote: > On 9/25/2017 5:40 AM, Jay Pipes wrote: > > On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: > > > There is a desire to expose the vGPUs resources on top of Resource > > > Provider which is probably

[openstack-dev] vGPUs support for Nova - Implementation

Please consider the support of MDEV for the /pci framework which provides support for vGPUs [0]. Accordingly to the discussion [1] With this first implementation which could be used as a skeleton for implementing PCI Devices in Resource Tracker we provide support for attaching vGPUs to guests.

Re: [openstack-dev] vGPUs support for Nova

On Mon, Sep 25, 2017 at 04:59:04PM +, Jianghua Wang wrote: > Sahid, > > Just share some background. XenServer doesn't expose vGPUs as mdev > or pci devices. That does not make any sense. There is physical device (PCI) which provides functions (vGPUs). These functions are exposed

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

On Thu, Sep 28, 2017 at 05:06:16PM -0400, Jay Pipes wrote: > On 09/28/2017 11:37 AM, Sahid Orentino Ferdjaoui wrote: > > Please consider the support of MDEV for the /pci framework which > > provides support for vGPUs [0]. > > > > Accordingly to the discussion [

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On Thu, Sep 28, 2017 at 11:10:38PM +0200, Premysl Kouril wrote: > > > > Only the memory mapped for the guest is striclty allocated from the > > NUMA node selected. The QEMU overhead should float on the host NUMA > > nodes. So it seems that the "reserved_host_memory_mb" is enough. > > > > Even if

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

On Fri, Sep 29, 2017 at 11:16:43AM -0400, Jay Pipes wrote: > Hi Sahid, comments inline. :) > > On 09/29/2017 04:53 AM, Sahid Orentino Ferdjaoui wrote: > > On Thu, Sep 28, 2017 at 05:06:16PM -0400, Jay Pipes wrote: > > > On 09/28/2017 11:37 AM, Sahid Orentino Ferdjao

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

On Fri, Sep 29, 2017 at 04:51:10PM +, Bob Ball wrote: > Hi Sahid, > > > > a second device emulator along-side QEMU. There is no mdev > > > integration. I'm concerned about how much mdev-specific functionality > > > would have to be faked up in the X

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

On Fri, Sep 29, 2017 at 12:26:07PM +, Bob Ball wrote: > Hi Sahid, > > > Please consider the support of MDEV for the /pci framework which provides > > support for vGPUs [0]. > > From my understanding, this MDEV implementation for vGPU would be > entirely specific

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On Wed, Sep 27, 2017 at 11:10:40PM +0200, Premysl Kouril wrote: > > Lastly, qemu has overhead that varies depending on what you're doing in the > > guest. In particular, there are various IO queues that can consume > > significant amounts of memory. The company that I work for put in a good > >

[openstack-dev] vGPUs support for Nova

There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already made a decision about moving in that direction anyway. My personal feeling is that it is premature.

Re: [openstack-dev] [nova] Running large instances with CPU pinning and OOM

On Mon, Sep 25, 2017 at 05:36:44PM +0200, Jakub Jursa wrote: > Hello everyone, > > We're experiencing issues with running large instances (~60GB RAM) on > fairly large NUMA nodes (4 CPUs, 256GB RAM) while using cpu pinning. The > problem is that it seems that in some extreme cases qemu/KVM can

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

On Tue, Oct 24, 2017 at 03:32:15PM +0100, Stephen Finucane wrote: > Hey, > > I'm not actually sure what the protocol is for adding/removing cores to a > library project without a PTL, so I'm just going to put this out there: I'd > like to propose the following changes to the os-vif core team. >

[openstack-dev] [neutron][nova] live-migration broken after update of OVS/DPDK

We have an issue with live-migration if operators update OVS from a version that does not support dpdkvhostuserclient to a version that is supporting it. Basically from OVS2.6 to OVS2.7 or upper. The problem is that, for libvirt driver all the instances created that use vhu interfaces in server

Re: [openstack-dev] openstack-dev] [nova] Cannot live migrattion, because error:libvirtError: the CPU is incompatible with host CPU: Host CPU does not provide required features: cmt, mbm_total, mbm_lo

On Mon, May 14, 2018 at 11:23:51AM +0800, 何健乐 wrote: > Hi, all > When I did live-miration , I met the following error: result = > proxy_call(self._autowrap, f, *args, **kwargs)May 14 10:33:11 > nova-compute[981335]: File > "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 144, in

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On Fri, Jun 08, 2018 at 11:35:45AM +0200, Kashyap Chamarthy wrote: > On Thu, Jun 07, 2018 at 01:07:48PM -0500, Matt Riedemann wrote: > > On 6/7/2018 12:56 PM, melanie witt wrote: > > > Recently, we've received interest about increasing the maximum number of > > > allowed volumes to attach to a

Re: [openstack-dev] [nova] about filter the flavor

On Mon, Jul 02, 2018 at 11:08:51AM +0800, Rambo wrote: > Hi,all > > I have an idea.Now we can't filter the special flavor according to > the property.Can we achieve it?If we achieved this,we can filter the > flavor according the property's key and value to filter the > flavor. What do you think

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

On Mon, Jun 18, 2018 at 10:16:05AM -0400, Artom Lifshitz wrote: > Hey all, > > For Rocky I'm trying to get live migration to work properly for > instances that have a NUMA topology [1]. > > A question that came up on one of patches [2] is how to handle > resources claims on the destination, or

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

On Thu, Jun 21, 2018 at 09:36:58AM -0400, Jay Pipes wrote: > On 06/18/2018 10:16 AM, Artom Lifshitz wrote: > > Hey all, > > > > For Rocky I'm trying to get live migration to work properly for > > instances that have a NUMA topology [1]. > > > > A question that came up on one of patches [2] is

Re: [openstack-dev] [Openstack] [nova] [os-vif] [vif_plug_ovs] Support for OVS DB tcp socket communication.

On Wed, Jul 25, 2018 at 03:22:27PM +0530, pranab boruah wrote: > Hello folks, > > I have filed a bug in os-vif: > https://bugs.launchpad.net/os-vif/+bug/1778724 and > working on a patch. Any feedback/comments from you guys would be extremely > helpful. > > Bug details: > > OVS DB server has the