Re: [openstack-dev] KVM Forum 2017: Call For Participation

A quick reminder that the deadline for submissions to the KVM Forum 2017 is just 10 days away now, June 15. On Tue, May 09, 2017 at 01:50:52PM +0100, Daniel P. Berrange wrote: > > KVM Forum 2017: Call For Participation > O

Re: [openstack-dev] [nova][cinder][barbican] Why is Cinder creating symmetric keys in Barbican for use with encrypted volumes?

On Thu, May 25, 2017 at 11:38:44AM +0100, Duncan Thomas wrote: > On 25 May 2017 at 11:00, Lee Yarwood wrote: > > This has also reminded me that the plain (dm-crypt) format really needs > > to be deprecated this cycle. I posted to the dev and ops ML [2] last > > year about

[openstack-dev] KVM Forum 2017: Call For Participation

KVM Forum 2017: Call For Participation October 25-27, 2017 - Hilton Prague - Prague, Czech Republic (All submissions must be received before midnight June 15, 2017) =

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

On Fri, Apr 28, 2017 at 09:38:38AM +0100, sfinu...@redhat.com wrote: > On Fri, 2017-04-28 at 13:23 +0900, TETSURO NAKAMURA wrote: > > Hi Nova team, > > > > I'm writing this e-mail because I'd like to have a discussion about > > DPDK support at OpenStack Summit in Boston. > > > > We have

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

On Tue, Apr 04, 2017 at 09:21:27AM -0700, Clark Boylan wrote: > On Tue, Apr 4, 2017, at 06:36 AM, Daniel P. Berrange wrote: > > On Mon, Apr 03, 2017 at 04:06:53PM -0700, Clark Boylan wrote: > > > I have pushed a change to devstack [3] to enable using UCA which pulls > > >

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

On Tue, Apr 04, 2017 at 07:16:51AM -0400, Sean Dague wrote: > This is definitely a trade off, I know the last time we tried UCA we had > such a high failure rate we had to revert. But, that was a much younger > libvirt that was only just starting to get heavy testing in OpenStack. > So it feels

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

On Mon, Apr 03, 2017 at 04:06:53PM -0700, Clark Boylan wrote: > Hello, > > One of the major sets of issues currently affecting gate testing is > Libvirt stability. Elastic-recheck is tracking Libvirt crashes for us > and they happen frequently [0][1][2]. These issues appear to only affect >

Re: [openstack-dev] [nova] Core team changes

On Thu, Mar 09, 2017 at 05:14:08PM -0600, Matt Riedemann wrote: > I wanted to let everyone know of some various core team changes within Nova. > > nova-core > - > > I've discussed it with and removed Daniel Berrange (danpb) and Michael Still > (mikal) from the nova-core team. Both are

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote: > Hey all, > > We have a set of old vanity redirect URLs from back when we made a URL > for each project: > > cinder.openstack.org > glance.openstack.org > horizon.openstack.org > keystone.openstack.org > nova.openstack.org >

Re: [openstack-dev] [third-party][ci] openstack CI VM template

On Tue, Feb 28, 2017 at 07:49:01AM -0600, Mikhail Medvedev wrote: > On Tue, Feb 28, 2017 at 2:52 AM, Guo, Ruijing wrote: > > Hi, CI Team, > > > > > > > > I’d like to know if openstack CI VM support nested virtualization. > > > > OpenStack CI infrastructure is using nested

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Mon, Feb 27, 2017 at 10:30:33AM -0500, Artom Lifshitz wrote: > > - virtio-vsock - think of this as UNIX domain sockets between the host and > >guest. This is to deal with the valid use case of people wanting to use > >a network protocol, but not wanting an real NIC exposed to the

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Mon, Feb 20, 2017 at 12:46:09PM -0500, Artom Lifshitz wrote: > > But before doing that though, I think it'd be worth understanding whether > > metadata-over-vsock support would be acceptable to people who refuse > > to deploy metadata-over-TCPIP today. > > Sure, although I'm still concerned

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Mon, Feb 20, 2017 at 05:07:53PM +, Tim Bell wrote: > Is there cloud-init support for this mode or do we still need to mount > as a config drive? I don't think it particularly makes sense to expose the config drive via NVDIMM - it wouldn't solve any of the problems that config drive has

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Mon, Feb 20, 2017 at 10:46:09AM -0500, Artom Lifshitz wrote: > I don't think we're trying to re-invent configuration management in > Nova. We have this problem where we want to communicate to the guest, > from the host, a bunch of dynamic metadata that can change throughout > the guest's

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Mon, Feb 20, 2017 at 02:24:12PM +, Jeremy Stanley wrote: > On 2017-02-20 13:38:31 + (+), Daniel P. Berrange wrote: > [...] > >Rather than mounting as a filesystem, you can also use NVDIMM directly > >as a raw memory block, in which case it can contain wh

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Sat, Feb 18, 2017 at 01:54:11PM -0500, Artom Lifshitz wrote: > A few good points were made: > > * the config drive could be VFAT, in which case we can't trust what's > on it because the guest has write access > * if the config drive is ISO9660, we can't selectively write to it, we > need to

Re: [openstack-dev] [nova] Device tagging: rebuild config drive upon instance reboot to refresh metadata on it

On Sat, Feb 18, 2017 at 08:11:10AM -0500, Artom Lifshitz wrote: > In reply to Michael: > > > We have had this discussion several times in the past for other reasons. The > > reality is that some people will never deploy the metadata API, so I feel > > like we need a better solution than what we

Re: [openstack-dev] [Openstack-operators] [nova] Next minimum libvirt version

On Thu, Feb 09, 2017 at 05:29:22PM -0600, Matt Riedemann wrote: > Since danpb hasn't been around I've sort of forgotten about this, but we > should talk about bumping the minimum required libvirt version in nova. > > Currently it's 1.2.1 and the next was set to 1.2.9. > > On master we're gating

Re: [openstack-dev] [Openstack-operators] [nova] Automatically disabling compute service on RBD EMFILE failures

On Sat, Jan 07, 2017 at 12:04:25PM -0600, Matt Riedemann wrote: > A few weeks ago someone in the operators channel was talking about issues > with ceph-backed nova-compute and OSErrors for too many open files causing > issues. > > We have a bug reported that's very similar sounding: > >

Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

On Fri, Dec 02, 2016 at 09:22:54AM -0600, Matt Riedemann wrote: > I'm proposing that we add Stephen Finucane to the nova-core team. Stephen > has been involved with nova for at least around a year now, maybe longer, my > ability to tell time in nova has gotten fuzzy over the years. Regardless, >

Re: [openstack-dev] [all] Creating a new IRC meeting room ?

On Fri, Dec 02, 2016 at 11:35:05AM +0100, Thierry Carrez wrote: > Hi everyone, > > There has been a bit of tension lately around creating IRC meetings. > I've been busy[1] cleaning up unused slots and defragmenting biweekly > ones to open up possibilities, but truth is, even with those changes >

[openstack-dev] [nova] away from Nova development for forseeable future

Hi Folks, I was recently tasked with spending some months working full time on another project unrelated to OpenStack Nova. As such I am not likely to be participating in any Nova related work for at least the Ocata development cycle. At this time, I don't know whether I'll be returning to Nova

Re: [openstack-dev] [nova] More file injection woes

On Fri, Nov 11, 2016 at 07:11:51PM -0600, Matt Riedemann wrote: > Chris Friesen reported a bug [1] where injected files on a server aren't in > the guest after it's evacuated to another compute host. This is because the > injected files aren't persisted in the nova database at all. Evacuate and >

Re: [openstack-dev] [nova] Live migrations: Post-Copy and Auto-Converge features research

On Mon, Nov 07, 2016 at 10:34:39PM +0200, Vlad Nykytiuk wrote: > Hi, > > As you may know, currently QEMU supports several features that help live > migrations to operate more predictively. These features are: auto-converge > and post-copy. > I made a research on performance characteristics of

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

On Wed, Nov 02, 2016 at 10:43:44AM +, Lee Yarwood wrote: > On 02-11-16 08:55:08, Carlton, Paul (Cloud Services) wrote: > > Lee > > > > I see this in a multiple node devstack without shared storage, although > > that shouldn't be relevant > > > > I do a live migration of an instance > > > >

Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes

On Tue, Nov 01, 2016 at 11:22:25AM +, Carlton, Paul (Cloud Services) wrote: > I'm working on a bug https://bugs.launchpad.net/nova/+bug/1633033 with the > live migration of > > instances with encrypted volumes. I've submitted a work in progress version > of a patch > >

Re: [openstack-dev] [nova] Cannot bind instance to generic vhostuser interface

On Fri, Oct 28, 2016 at 10:34:50AM +, Tomas Cechvala -X (tcechval - PANTHEON TECHNOLOGIES at Cisco) wrote: > Hi nova devs, > > I'm trying to bind nova instances to generic vhostuser interface (created by > VPP).Based on the log output it seems that vhostuser vif_type is not > recognized by

Re: [openstack-dev] [nova][cinder] Addressing mangled LUKS passphrases (bug#1633518)

On Fri, Oct 21, 2016 at 12:07:08PM +0100, Lee Yarwood wrote: > Hello, > > I documented bug#1633518 [1] last week in which volumes encrypted prior > to Ib563b0ea [2] used a slightly mangled passphrase instead of the > original passphrase provided by the configured key manager. > > My first

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Fri, Sep 30, 2016 at 04:36:31PM +, Murray, Paul (HP Cloud) wrote: > > We have a problem migrating rescued instances that has a fix in progress based > on regenerating the xml on unrescue, see: > > https://blueprints.launchpad.net/nova/+spec/live-migrate-rescued-instances > > That might

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Mon, Oct 03, 2016 at 10:11:34AM +0300, Timofei Durakov wrote: > Hi team, > > I agree that it's kind of strange thing that nova dumps xml definition to > the disk but doesn't use it(at least I do not aware of it). > How the proposed changed would be aligned with other drivers? The worst > case

[openstack-dev] RFC: "next" min libvirt/qemu requirement for Pike release

In the Newton release we increased the min required libvirt to 1.2.1 and min QEMU to 1.5.3 We did not set any "next" versions for Ocata, so Ocata will not be changing. I think we should consider increasing min versions in the Pike release though to let us cut out more back-compatibility code for

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Tue, Sep 27, 2016 at 10:40:34AM -0600, Chris Friesen wrote: > On 09/27/2016 10:17 AM, Matthew Booth wrote: > > > I think we should be able to create a domain, but once created we should > > never > > redefine a domain. We can do adding and removing devices dynamically using > > libvirt's

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Tue, Sep 27, 2016 at 05:17:29PM +0100, Matthew Booth wrote: > Currently the libvirt driver (mostly) considers the nova db canonical. That > is, we can throw away libvirt's domain XML at any time and recreate it from > Nova. Anywhere that doesn't assume this is a bug, because whatever >

Re: [openstack-dev] [nova] Can all virt drivers provide a disk 'id' for the diagnostics API?

On Mon, Sep 26, 2016 at 09:31:39PM +0800, Alex Xu wrote: > 2016-09-23 20:38 GMT+08:00 Daniel P. Berrange <berra...@redhat.com>: > > > On Fri, Sep 23, 2016 at 07:32:36AM -0500, Matt Riedemann wrote: > > > On 9/23/2016 3:54 AM, Daniel P. Berrange wrote: > > >

Re: [openstack-dev] [nova] Can all virt drivers provide a disk 'id' for the diagnostics API?

On Fri, Sep 23, 2016 at 07:32:36AM -0500, Matt Riedemann wrote: > On 9/23/2016 3:54 AM, Daniel P. Berrange wrote: > > On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote: > > > Sergey is working on a spec to use the standardized virt driver instance > >

Re: [openstack-dev] [nova] Can all virt drivers provide a disk 'id' for the diagnostics API?

On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote: > Sergey is working on a spec to use the standardized virt driver instance > diagnostics in the os-diagnostics API. A question came up during review of > the spec about how to define a disk 'id': > >

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 11:36:29AM -0400, Sean Dague wrote: > On 09/20/2016 11:20 AM, Daniel P. Berrange wrote: > > On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: > >> On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: > >>> On Tue, Sep 20, 2016 at 09:2

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: > On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: > > On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: > >> This is a bit delayed due to the release rush, finally getting back to > >> writing u

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: > This is a bit delayed due to the release rush, finally getting back to > writing up my experiences at the Ops Meetup. > > Nova Feedback Session > = > > We had a double session for Feedback for Nova from Operators,

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote: > The said patch in question fixes a CVE[x] in stable/liberty. > > We currently have two options, both of them have caused an impasse with > the Nova upstream / stable maintainers. We've had two-ish months to > mull over this.

Re: [openstack-dev] [cinder] moving driver to open source

On Thu, Sep 08, 2016 at 10:24:09AM +0200, Thierry Carrez wrote: > Avishay Traeger wrote: > > There are a number of drivers that require closed-source tools to > > communicate with the storage. 3 others that I've come across recently: > > > > * EMC VNX: requires Navisphere CLI v7.32 or higher >

Re: [openstack-dev] [Nova] Interface in PEER2PEER live migration

On Thu, Aug 25, 2016 at 12:01:40PM +0200, Alberto Planas Dominguez wrote: > On Wed, 2016-08-24 at 11:18 -0400, Daniel P. Berrange wrote: > > On Wed, Aug 24, 2016 at 05:07:50PM +0200, Alberto Planas Dominguez > > wrote: > > Daniel, thanks for the fast reply!! > > &

Re: [openstack-dev] [Nova] Interface in PEER2PEER live migration

On Wed, Aug 24, 2016 at 05:07:50PM +0200, Alberto Planas Dominguez wrote: > Unfortunately was closed as invalid, and the solution provided is > completely unrelated. The solution suggested is based on > `live_migration_inbound_addr`, that is related with the libvirtd URI, > not the qmeu one. I

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

On Wed, Aug 03, 2016 at 07:47:37PM -0400, Jay Pipes wrote: > Hi Novas and anyone interested in how to represent capabilities in a > consistent fashion. > > I spent an hour creating a new os-capabilities Python library this evening: > > http://github.com/jaypipes/os-capabilities > > Please see

Re: [openstack-dev] [nova] test strategy for the serial console feature

On Thu, Aug 11, 2016 at 04:46:02PM +0200, Markus Zoeller wrote: > On 11.08.2016 13:31, Daniel P. Berrange wrote: > > On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote: > >> On 08/11/2016 05:45 AM, Markus Zoeller wrote: > >>> On 26.07.2016 12:16, Jordan P

Re: [openstack-dev] [nova] test strategy for the serial console feature

On Thu, Aug 11, 2016 at 07:19:42AM -0400, Sean Dague wrote: > On 08/11/2016 05:45 AM, Markus Zoeller wrote: > > On 26.07.2016 12:16, Jordan Pittier wrote: > >> Hi Markus > >> You don"t really need a whole new job for this. Just turn that flag to True > >> on existing jobs. > >> > >> 30/40 seconds

Re: [openstack-dev] [nova] Nova mascot

On Tue, Aug 09, 2016 at 11:26:21AM -0500, Matt Riedemann wrote: > On 8/8/2016 4:10 PM, Clint Byrum wrote: > > Excerpts from Matt Riedemann's message of 2016-08-08 14:35:12 -0500: > > > Not to be a major curmudgeon but I think we'd basically decided at the > > > midcycle (actually weeks before)

Re: [openstack-dev] [nova] Removal of live_migration_flag and block_migration_flag config options

On Tue, Aug 02, 2016 at 02:36:32PM +, Koniszewski, Pawel wrote: > In Mitaka development cycle 'live_migration_flag' and 'block_migration_flag' > have been marked as deprecated for removal. I'm working on a patch [1] to > remove both of them and want to ask what we should do with >

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On Mon, Jul 25, 2016 at 08:22:52AM -0400, Sean Dague wrote: > On 07/25/2016 08:05 AM, Daniel P. Berrange wrote: > > On Mon, Jul 25, 2016 at 07:57:08AM -0400, Sean Dague wrote: > >> On 07/22/2016 11:30 AM, Daniel P. Berrange wrote: > >>> On Thu, Jul 21, 2016 at 07

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On Mon, Jul 25, 2016 at 07:57:08AM -0400, Sean Dague wrote: > On 07/22/2016 11:30 AM, Daniel P. Berrange wrote: > > On Thu, Jul 21, 2016 at 07:03:53AM -0700, Matt Riedemann wrote: > >> On 7/21/2016 2:03 AM, Bhor, Dinesh wrote: > >> > >> I agree that it's n

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On Thu, Jul 21, 2016 at 07:03:53AM -0700, Matt Riedemann wrote: > On 7/21/2016 2:03 AM, Bhor, Dinesh wrote: > > Hi Nova Devs, > > > > > > > > Many times, there are a number of data sets that we have to run the same > > tests on. > > > > And, to create a different test for each data set values

Re: [openstack-dev] FPGA as a dynamic nested resources

On Thu, Jul 21, 2016 at 07:54:48AM +0200, Roman Dobosz wrote: > On Wed, 20 Jul 2016 10:07:12 +0100 > "Daniel P. Berrange" <berra...@redhat.com> wrote: > > Hey Daniel, thanks for the feedback. > > > > Thoughts? > > > > I'd suggest you'

Re: [openstack-dev] FPGA as a dynamic nested resources

On Tue, Jul 19, 2016 at 08:03:28PM +0200, Roman Dobosz wrote: > Hi all, > > Some time ago Jay Pipes published etherpad[1] with ideas around > modelling nested resources, taking NUMA as an example. I was also > encouraged ;) to start this thread, on last Nova scheduler meeting. > > I was read

Re: [openstack-dev] [glance][nova] Globally disabling hw_qemu_guest_agent support

On Tue, Jul 19, 2016 at 12:51:07AM +, Daniel Russell wrote: > Hi Erno, > > For the size of team I am in I think it would work well but it feels like > I am putting the security of Nova in the hands of Glance. Yep, from an architectural pov it is not very good. Particularly in a

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

On Tue, Jul 12, 2016 at 05:40:07PM +0800, Monty Taylor wrote: > Hey all! > > The poll emails for the P and Q naming have started to go out - and > we're experiencing some difficulties. Not sure at the moment what's > going on ... but we'll keep working on the issues and get ballots to > everyone

Re: [openstack-dev] [Nova][SR-IOV][pci-passthrough] Reporting pci devices in hypervisor-show

On Fri, Jul 08, 2016 at 03:45:10PM -0400, Jay Pipes wrote: > On 07/08/2016 12:10 PM, Beliveau, Ludovic wrote: > > I see a lot of values in having something like this for inventory > > purposes and troubleshooting. > > > > IMHO the information should be provided in two ways. > > > > 1. Show PCI

Re: [openstack-dev] [all][oslo] Disable option value interpolation in oslo.config

On Fri, Jul 08, 2016 at 10:14:20PM +0800, ChangBo Guo wrote: > Hi ALL, > > I have been working a bug [1] about option value interpolation in > oslo.config[2], in short, option value interpolation can't handle password > containing special characters from environment variable and I proposed a >

Re: [openstack-dev] [nova][nova-docker] Retiring nova-docker project

On Fri, Jul 08, 2016 at 10:11:59AM +0200, Thierry Carrez wrote: > Matt Riedemann wrote: > > [...] > > Expand the numbers to 6 months and you'll see only 13 commits. > > > > It's surprisingly high in the user survey (page 39): > > > >

Re: [openstack-dev] [Openstack-operators] [nova] Fail build request if we can't inject files?

On Sun, Jul 03, 2016 at 10:08:04AM -0500, Matt Riedemann wrote: > I want to use the gate-tempest-dsvm-neutron-full-ssh in nova since it runs > ssh validation + neutron + config drive + metadata service, which will test > the virtual device tagging 2.32 microversion API (added last week). > > The

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On Fri, Jul 01, 2016 at 02:13:46PM +, Jeremy Stanley wrote: > Have you considered just writing a throwaway devstack-gate change > which overrides the gate_hook to run that one suspect Tempest test, > say, a thousand times in a loop? Would be far more efficient if you > don't need to be

Re: [openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

On Fri, Jul 01, 2016 at 02:35:34PM +, Jeremy Stanley wrote: > On 2016-07-01 15:39:10 +0200 (+0200), Kashyap Chamarthy wrote: > > [Snip description of some nice debugging.] > > > > > I'd really love it if there was > > > > > > 1. the ability to request checking of just specific jobs eg > > >

[openstack-dev] [nova][infra][ci] bulk repeating a test job on a single review in parallel ?

A bunch of people in Nova and upstream QEMU teams are trying to investigate a long standing bug in live migration[1]. Unfortuntely the bug is rather non-deterministic - eg on the multinode-live-migration tempest job it has hit 4 times in 7 days, while on multinode-full tempest job it has hit ~70

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Fri, Jun 24, 2016 at 08:05:38AM -0600, John Griffith wrote: > On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > > > > > volumes connected to QE

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Fri, Jun 24, 2016 at 11:12:27AM +0200, Thierry Carrez wrote: > Angus Lees wrote: > > [...] > > None of these are great, but: > > > > Possibility 1: Backdoor rootwrap > > > > However if we assume rootwrap already exists then we _could_ rollout a > > new version of oslo.rootwrap that contains

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On Fri, Jun 24, 2016 at 04:52:31PM +0800, Chen Fan wrote: > > > On 2016年06月24日 16:20, Daniel P. Berrange wrote: > > On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > > > hi all, > > > in openstack, we can use the pci passthrough featur

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > hi all, > in openstack, we can use the pci passthrough feature now, refer to > https://wiki.openstack.org/wiki/Pci_passthrough > but we can't definitely specify the host pci driver is LEGACY_KVM or > newer VFIO, > new

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > volumes connected to QEMU instances eventually become directly connected? > > > Our long term goal is that 100% of all network storage will be connected > > to directly by QEMU. We already have the ability to partially do

Re: [openstack-dev] [nova] libvirt driver: who should create the libvirt.xml file?

On Mon, Jun 20, 2016 at 05:47:57PM +0200, Markus Zoeller wrote: > White working on the change series to implement the virtlogd feature I > got feedback [1] to move code which creates parts of the libvirt.xml > file from the "driver" module into the "guest" module. I'm a bit > hesitant to do so as

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Wed, Jun 15, 2016 at 04:59:39PM -0700, Preston L. Bannister wrote: > QEMU has the ability to directly connect to iSCSI volumes. Running the > iSCSI connections through the nova-compute host *seems* somewhat > inefficient. > > There is a spec/blueprint and implementation that landed in Kilo: >

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: [snip] > The crux of the problem is that os-brick 1.4 and privsep can't be used > without a config file change during the upgrade. Which violates our > policy, because it breaks rolling upgrades. os-vif support is going to face exactly

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

On Tue, Jun 14, 2016 at 02:35:57AM -0700, Kevin Benton wrote: > In strategy 2 we just pass 1 bridge name to Nova. That's the one that is > ensures is created and plumbs the VM to. Since it's not responsible for > patch ports it doesn't need to know anything about the other bridge. Ok, so we're

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

2 also requires you to pass a second bridge name to nova/os-vif, unless I'm mis-understanding the description below. > On Tue, Jun 14, 2016 at 1:29 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Mon, Jun 13, 2016 at 11:35:17PM +, Peters, Rawlin wrote: >

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

On Mon, Jun 13, 2016 at 11:35:17PM +, Peters, Rawlin wrote: > That said, there are currently a couple of vif-plugging strategies > we could go with for wiring trunk ports for OVS, each of them > requiring varying levels of os-vif augmentation: > > Strategy 1) When Nova is plugging a trunk

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

On Fri, Jun 10, 2016 at 09:51:03AM +1000, Tony Breeds wrote: > On Fri, Jun 10, 2016 at 08:24:34AM +1000, Michael Still wrote: > > On Fri, Jun 10, 2016 at 7:18 AM, Tony Breeds > > wrote: > > > > > On Wed, Jun 08, 2016 at 08:10:47PM -0500, Matt Riedemann wrote: > > > > > >

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

On Mon, Jun 13, 2016 at 07:39:29AM -0400, Assaf Muller wrote: > On Mon, Jun 13, 2016 at 4:35 AM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > >> Hi, > >> > >> You may or may

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

On Mon, Jun 13, 2016 at 02:08:30PM +0200, Armando M. wrote: > On 13 June 2016 at 10:35, Daniel P. Berrange <berra...@redhat.com> wrote: > > > On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > > > Hi, > > > > > > You may or may

Re: [openstack-dev] Invitation to join Hangzhou Bug Smash

On Mon, Jun 13, 2016 at 08:06:50AM +, Wang, Shane wrote: > Hi, OpenStackers, > > As you know, Huawei, Intel and CESI are hosting the 4th China OpenStack Bug > Smash at Hangzhou, China. > The 1st China Bug Smash was at Shanghai, the 2nd was at Xi'an, and the 3rd > was at Chengdu. > > We are

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

On Thu, Jun 09, 2016 at 05:31:13PM -0600, Carl Baldwin wrote: > Hi, > > You may or may not be aware of the vlan-aware-vms effort [1] in > Neutron. If not, there is a spec and a fair number of patches in > progress for this. Essentially, the goal is to allow a VM to connect > to multiple Neutron

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On Thu, Jun 09, 2016 at 12:35:06PM -0600, Chris Friesen wrote: > On 06/09/2016 05:15 AM, Paul Michali wrote: > > 1) On the host, I was seeing 32768 huge pages, of 2MB size. > > Please check the number of huge pages _per host numa node_. > > > 2) I changed mem_page_size from 1024 to 2048 in the

Re: [openstack-dev] [nova] Using image metadata to sanity check supplied authentication data at nova 'create' or 'recreate' time?

On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote: > On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote: > > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote: > > > > > Hello all, > > > > > > At Rackspace we're running into an interesting problem:

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On Fri, Jun 03, 2016 at 12:32:17PM +, Paul Michali wrote: > Hi! > > I've been playing with Liberty code a bit and had some questions that I'm > hoping Nova folks may be able to provide guidance on... > > If I set up a flavor with hw:mem_page_size=2048, and I'm creating (Cirros) > VMs with

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 31, 2016 at 08:19:33AM -0400, Sean Dague wrote: > On 05/30/2016 06:25 AM, Kashyap Chamarthy wrote: > > On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: > >> On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: > >>> On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > The team working on live migration testing started with an experimental > job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + > qemu under the assumption that a set of issues we were seeing are > solved. The short

Re: [openstack-dev] [nova]Libvirt error code for failing volume in nova

On Wed, May 18, 2016 at 07:57:17PM +, Radhakrishnan, Siva wrote: > Hi All! > Currently I am working on this bug > https://bugs.launchpad.net/nova/+bug/1168011 which says we have to change > error message displayed when attaching a volume fails. Currently it catches > all operation errors

Re: [openstack-dev] [nova] Thoughts on deprecating the legacy bdm v1 API support

On Tue, May 17, 2016 at 09:48:02AM -0500, Matt Riedemann wrote: > In the live migration meeting today mdbooth and I were chatting about how > hard it is to follow the various BDM code through nova, because you have the > three block_device modules: > > * nova.block_device - dict that does some

Re: [openstack-dev] Wiki

On Tue, May 10, 2016 at 12:59:41PM -0400, Anita Kuno wrote: > On 05/10/2016 12:48 PM, Dan Smith wrote: > >>> Hmm... that's unfortunate, as we were trying to get some of our less > >>> ephemeral items out of random etherpads and into the wiki (which has the > >>> value of being google indexed). > >

Re: [openstack-dev] [tc] License for specs repo

On Thu, May 05, 2016 at 12:03:38PM -0400, Ben Swartzlander wrote: > It appears that many of the existing specs repos contain a confusing mixture > of Apache 2.0 licensed code and Creative Commons licensed docs. > > The official cookie-cutter for creating new specs repos [1] appears to also >

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

On Tue, May 03, 2016 at 04:16:43PM -0600, Chris Friesen wrote: > On 05/03/2016 03:14 AM, Daniel P. Berrange wrote: > > >There are currently many options for live migration with QEMU that can > >assist in completion > > > > >Given this I've spent the last week c

Re: [openstack-dev] [Nova] Libvirt version requirement

On Mon, May 02, 2016 at 11:27:01AM +0800, ZhiQiang Fan wrote: > Hi Nova cores, > > There is a spec[1] submitted to Telemetry project for Newton release, > mentioned that a new feature requires libvirt >= 1.3.4 , I'm not sure if > this will have bad impact to Nova service, so I open this thread

Re: [openstack-dev] [Nova] Live Migration: Austin summit update

On Fri, Apr 29, 2016 at 10:32:09PM +, Murray, Paul (HP Cloud) wrote: > The following summarizes status of the main topics relating to live migration > after the Newton design summit. Please feel free to correct any inaccuracies > or add additional information. > Post copy > > The spec to add

Re: [openstack-dev] [nova] next min libvirt?

On Sat, Apr 30, 2016 at 10:28:23AM -0500, Thomas Bechtold wrote: > Hi, > > On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > > probably a good time consider the appropriate bump for Otaca. > > > > By that

Re: [openstack-dev] [nova] next min libvirt?

On Fri, Apr 29, 2016 at 03:16:56PM -0500, Matt Riedemann wrote: > On 4/29/2016 10:28 AM, Daniel P. Berrange wrote: > >On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > >>We've just landed the libvirt min to bump us up to 1.2.1 required. It's > >>pr

Re: [openstack-dev] [nova] next min libvirt?

On Fri, Apr 29, 2016 at 10:13:42AM -0500, Sean Dague wrote: > We've just landed the libvirt min to bump us up to 1.2.1 required. It's > probably a good time consider the appropriate bump for Otaca. > > By that time our Ubuntu LTS will be 16.04 (libvirt 1.3.1), RHEL 7.1 > (1.2.8). Additionally

Re: [openstack-dev] KVM Forum 2016: Call For Participation

at 06:19:36PM +, Daniel P. Berrange wrote: > = > KVM Forum 2016: Call For Participation > August 24-26, 2016 - Westin Harbor Castle - Toronto, Canada > > (All submissions must be received before midni

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On Tue, Apr 26, 2016 at 04:24:52PM +0200, Jordan Pittier wrote: > On Tue, Apr 26, 2016 at 3:32 PM, Daniel P. Berrange <berra...@redhat.com> > wrote: > > > On Tue, Apr 26, 2016 at 08:19:23AM -0500, Doug Hellmann wrote: > > > Excerpts from Guangyu Suo's messag

Re: [openstack-dev] [oslo.config] Encrypt the sensitive options

On Tue, Apr 26, 2016 at 08:19:23AM -0500, Doug Hellmann wrote: > Excerpts from Guangyu Suo's message of 2016-04-26 07:28:42 -0500: > > Hello, oslo team > > > > For now, some sensitive options like password or token are configured as > > plaintext, anyone who has the priviledge to read the

Re: [openstack-dev] [nova] Encrypted Ephemeral Storage

On Mon, Apr 25, 2016 at 04:28:17PM +, Coffman, Joel M. wrote: > Based on the comments to the RBD encryption change [1], it looks > like there will be a new direction for ephemeral disk encryption > (embedding it in QEMU directly). I assume LVM will work the same > way when the time comes. Will

Re: [openstack-dev] [nova][neutron] os-vif status report

On Fri, Apr 22, 2016 at 04:25:54AM +, Angus Lees wrote: > In case it wasn't already assumed, anyone is welcome to contact me directly > (irc: gus, email, or in Austin) if they have questions or want help with > privsep integration work. It's early days still and the docs aren't > extensive

  1   2   3   4   5   6   7   8   >