Re: [Openstack-operators] [scientific] Ironic Summit recap - ops experiences

On 12/05/16 06:22, "Stig Telfer" wrote: >Hi All - > >Jim Rollenhagen from the Ironic project has just posted a great summit report >of Ironic team activities on the openstack-devs mailing list[1], which >included this item which will be of interest to the

[Openstack-operators] [scientific] Ironic Summit recap - ops experiences

Hi All - Jim Rollenhagen from the Ironic project has just posted a great summit report of Ironic team activities on the openstack-devs mailing list[1], which included this item which will be of interest to the Scientific WG members who are looking to work on bare metal activities this cycle:

[Openstack-operators] [glance] glance-registry deprecation: Request for feedback

Greetings, The Glance team is evaluating the needs and usefulness of the Glance Registry service and this email is a request for feedback from the overall community before the team moves forward with anything. Historically, there have been reasons to create this service. Some deployments use it

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On Wed, May 11, 2016 at 07:30:45PM -0400, Emilien Macchi wrote: :On Tue, May 3, 2016 at 11:43 AM, Matt Riedemann : wrote: :> Another thought is that deployment tools are just copying what devstack :> does, or what shows up in the configs in our dsvm gate jobs, and

[Openstack-operators] [app-catalog] App Catalog IRC meeting Thursday May 12th

Join us Thursday for our weekly meeting, scheduled for May 12th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog It might be a short

[Openstack-operators] FW: [openstack-dev] Collecting our wiki use cases

FYI. If you don't comment, you can't complain when they don't address your needs. --Rocky -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: Wednesday, May 11, 2016 8:28 AM To: OpenStack Development Mailing List Subject: [openstack-dev] Collecting our wiki use

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On Tue, May 3, 2016 at 11:43 AM, Matt Riedemann wrote: > On 5/3/2016 10:01 AM, Daniel P. Berrange wrote: >> >> Hello Operators, >> >> One of the things that constantly puzzles me when reading the user >> survey results wrt hypervisor is the high number of respondants

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

I am +1 on this response as well. Seems like having live or cold migrations follow the same pattern/states would make sense. ___ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: David Medberry

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

So I'm a big ol' -0- don't care on this. We've never used that list before (but will now). Seems like it would be useful though to have it the same for l-m and cold migration. On Wed, May 11, 2016 at 9:27 AM, Andrew Laski wrote: > > > > On Wed, May 11, 2016, at 11:10 AM,

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On 11 May 2016 at 14:32, Maish Saidel-Keesing wrote: > > On 11/05/16 22:18, Chris Friesen wrote: > > On 05/11/2016 11:46 AM, Ronald Bradford wrote: > > I have been curious as to why as mentioned in the thread virt_type=kvm, > but > os-hypervisors API call states QEMU. > > >

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On 05/11/2016 01:29 PM, Robert Starmer wrote: I don't disagree, what we're really getting at is that any lookup (ask the system what it's using on a particular instance, look at the config, look at the output of a nova CLI request, querry via Horizon), should all return the same answer. So one

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On 11/05/16 22:18, Chris Friesen wrote: > On 05/11/2016 11:46 AM, Ronald Bradford wrote: >> I have been curious as to why as mentioned in the thread >> virt_type=kvm, but >> os-hypervisors API call states QEMU. > > Arguably in both cases the hypervisor is qemu. When virt_type=kvm we > simply

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

I don't disagree, what we're really getting at is that any lookup (ask the system what it's using on a particular instance, look at the config, look at the output of a nova CLI request, querry via Horizon), should all return the same answer. So one is a bug (Horizon), the other requires looking

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

Or we could just fix the problem within OpenStack to report the correct Hypervisor in the first place. This kind of reminds me of a story. Someone was trying to drive down a path on his bicycle, but there were some tacks on the path. So his wheel kept on getting full of holes. So they thought

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On 05/11/2016 11:46 AM, Ronald Bradford wrote: I have been curious as to why as mentioned in the thread virt_type=kvm, but os-hypervisors API call states QEMU. Arguably in both cases the hypervisor is qemu. When virt_type=kvm we simply enable some additional acceleration. So rather than

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

You could just ask for the value of virt_type parameter from a compute host (or the output of something like grep 'virt_type' /etc/nova/nova*) if you are using qemu or kvm. I believe that's how nova figures out what parameters to use when launching an instance. On Wed, May 11, 2016 at 8:39 AM,

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

In the next user survey - could we clarify that qemu == full software cpu emulation and kvm (qemu/kvm) = hardware accelerated virtualization or some similar phrasing. It's totally possible that people are like: I run both qemu and kvm (thinking that’s qemu/kvm) - when in fact they only run kvm

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

Does anyone see a good way to fix this to report KVM or QEMU/KVM ? I guess the worry is whether this would count as a bug fix or an incompatible change. Tim On 11/05/16 17:51, "Kashyap Chamarthy" wrote: >On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

I have been curious as to why as mentioned in the thread virt_type=kvm, but os-hypervisors API call states QEMU. Interestingly this command mentioned (which works on Ubuntu) gives me a FAIL and WARN on my home test setup that runs on physical H/W. $ virt-host-validate QEMU: Checking for

Re: [Openstack-operators] How are folks providing GPU instance types?

Just wanted to add a few notes (I apologize for the brevity): * The wiki page is indeed the best source of information to get started. * I found that I didn't have to use EFI-based images. I wonder why that is? * PCI devices and IDs can be found by running the following on a compute node: $

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

Which still brings me back to the original point. Is this a bug - and should it be reported as such? On 11/05/16 18:51, Kashyap Chamarthy wrote: > On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote: > > [...] > >> I'm confused too about the use of KVM or QEMU In the computes

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote: [...] > I'm confused too about the use of KVM or QEMU In the computes the > file​/etc/nova/nova-compute.conf has: > > virt_type=kvm > > The output of: > > nova hypervisor-show | grep hypervisor_type > > is: > >

[Openstack-operators] Collecting our wiki use cases

Hi everyone, At the beginning of OpenStack we have been using wiki.openstack.org as our default community lightweight information publication platform. There were/are lots of things in there, reference information that a couple people struggled to keep up to date (and non-vandalized), old

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

On Wed, May 11, 2016, at 11:10 AM, David Medberry wrote: > Kekane, > > Hi, > > This setting, how does it display in the "nova show $UUID" or in the > "openstack server show $UUID"? Ie, I don't want a VM showing ERROR > state if the VM itself is not in error. A failed migration doesn't >

[Openstack-operators] [ironic] Dropping legacy bash ramdisk support

Hi all! As you probably know, the old bash-based ramdisks for ironic [1] and ironic-inspector [2] are deprecated for some long time. The time has come: we are removing their support from our code base in the near future. Here is the draft plan: 1. Remove the gate-tempest-dsvm-ironic-pxe_ssh-dib

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

Hi Operators, Could you please provide your opinion on below mail. I need to discuss this in coming nova meeting (12 May, 2016). Thank you, Abhishek Kekane From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com] Sent: Monday, May 09, 2016 7:22 AM To: