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] 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 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 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] [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 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] [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] [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] [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] 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 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][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] [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] 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] 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] 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][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][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

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] 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][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

[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] 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] 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] 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 >

[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] [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] [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] 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] [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 >

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] [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] [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] [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 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] [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 >

[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][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

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] 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

<    3   4   5   6   7   8