[Openstack-operators] Nova

Hey everyone, do specific versions of OpenStack necessitate specific versions of guest os's? I.e. if I'm running a mitaka cloud platform, do the guest vm operating systems need to be a specific version of Linux? My understanding is the two are totally unrelated when the VM's are running Linux but I

[Openstack-operators] nova rescue

Hello, Without specifying a rescue image, Nova will use the image that the instance is based on when performing a rescue. I've noticed that this is problematic for "cloud-friendly" images such as the official Ubuntu images and the newer CentOS 7 images. I'm finding that /dev/vdb still ends up mou

[Openstack-operators] nova-docker

How to install nova-docker? Can anyone help me? Thanks___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Nova

Hi Adam - The OS of the guest is independent of the Openstack version. Your choice of hypervisor (KVM, VMWare, HyperV, etc) would just need to support the OS version that you want to run on your guests. Mike Smith Lead Cloud Systems Architect Overstock.com On Sep 2, 20

Re: [Openstack-operators] Nova

Mike that's just as I suspected. To be super clear, does KVM in particular know how to distinguish between Ubuntu v12 versus v16? In other words, do I need to be running a specific version of KVM hypervisor so it can host guests running the latest version of Ubuntu? Again, this was brought up as b

Re: [Openstack-operators] Nova

The specific concern is *udev* and whether the *udev* version on the guest should match the version of *udev* running on the host to ensure reliable volume handling... //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-N

Re: [Openstack-operators] Nova

On Fri, Sep 02, 2016 at 04:00:17PM -0700, Adam Lawson wrote: :Mike that's just as I suspected. To be super clear, does KVM in particular :know how to distinguish between Ubuntu v12 versus v16? In other words, do I :need to be running a specific version of KVM hypervisor so it can host :guests runni

Re: [Openstack-operators] Nova

Hi Jonathan, What is being reported is that a guest was running Ubuntu v12 with kernel 3.9.x-generic on a host that was running Ubuntu v14 with kernel 3.13.x-generic and the engineer had problems with reliably mounting/unmounting volumes and that problem was corrected by upgrading the gusts to ker

Re: [Openstack-operators] [nova]

Hi, I am trying to programmatically rebuild a nova instance that has a persistent volume for its root device. I am specifically trying to rebuild an instance that has multiple network interfaces and a floating ip. I have observed that the order in which the network interface are attached matte

Re: [Openstack-operators] [nova]

If you don't recreate Neutron ports (just destroying VM, creating it as new and attaching old ports), then you can distinguish between interfaces by MAC addresses and store this in udev rules. You can do this on first boot (e.g. in cloud-init's "startcmd" command), using information from /sys/c

Re: [Openstack-operators] nova rescue

On 03/29/2015 11:19 AM, Joe Topjian wrote: Hello, Without specifying a rescue image, Nova will use the image that the instance is based on when performing a rescue. I've noticed that this is problematic for "cloud-friendly" images such as the official Ubuntu images and the newer CentOS 7 imag

Re: [Openstack-operators] nova rescue

That's all very useful advise -- thank you. :) On Sun, Mar 29, 2015 at 8:39 PM, gustavo panizzo (gfa) wrote: > > > On 03/29/2015 11:19 AM, Joe Topjian wrote: > >> Hello, >> >> Without specifying a rescue image, Nova will use the image that the >> instance is based on when performing a rescue. >>

Re: [Openstack-operators] nova-docker

Hi, Have you checked https://wiki.openstack.org/wiki/Docker#Configure_an_existing_OpenStack_installation_to_enable_Docker ? regards Anshu Prateek On Thu, 24 Sep 2015 at 08:42 葛文堂 wrote: > How to install nova-docker? Can anyone help me? Thanks > > > > ___

[Openstack-operators] [Nova] Deprecating localfs?

Greetings from an ancient thread (but the most recent on to openstack-dev about localfs that I can find). In 2014, which were heady times, we decided that we couldn't deprecate nova.virt.disk.vfs.localfs because we theorised that FreeBSD and containers would soon need it. Oh, and xenapi uses it a

[Openstack-operators] Nova HTTPConnectionPool Error

Hi there, After successful installation of both keystone and glance, my Nova service didn't work. The following error was occured when I executed: 'nova list' -- ERROR: HTTPConnectionPool(host='localhost', port=8774): Max retries exceeded with url: /v2/19934884vr78as87437483bb1/servers/detail (

[Openstack-operators] Nova HTTPConnectionPool Error

I fixed it. But now in my nova-compute.log a new error meesage was shown: unexpected error while running command. command: sudo nova-rootwrap /etc/nova/rootwrap.conf iptables-restore -c exit code: 2 stdout: '' stderr: "iptables-restore v1.4.21: iptables-restore: unable to initialize table 'nat' Ho

[Openstack-operators] Nova hypervisor uuid

Hi All, Please anyone know where hypervisor uuid is retrived? Sometime updating kmv nodes with yum update it changes and in nova database 2 uuids are assigned to the same node. regards Ignazio ___ OpenStack-operators mailing list OpenStack-operators@list

[Openstack-operators] [nova] Deprecation of ComputeFilter

Hi, First, sorry for cross-posting on both dev and operator MLs but I also would like to get operators feedback. So, I was reviewing the scheduler ComputeFilter and I was wondering why the logic should be in a filter. We indeed already have a check on the service information each time that a

[Openstack-operators] nova-neutron with vsphere

Hi Folks,i would like to know if anybody has tried to implement a neutron solution with vsphere without using NSX-like solutions. I mean, my lab environment is composed of :  - 1 network node ( neutron )  - 1 controller node  - 2 compute node ( kvm)  - 1 compute node linked to a cluster vsphe

[Openstack-operators] Nova DB archiving script

I posted a patch against one of the Nova DB archiving scripts in the osops-tools-generic repo a few days ago to support additional tables: https://review.openstack.org/#/c/229013/2 We’d like a few more folks to review to make sure it looks good. Please take a few minutes and take a look. Than

[Openstack-operators] Nova-network -> Neutron Migration

Hey fellow oppers! I was wondering if anyone has any experience doing a migration from nova-network to neutron. We're looking at an in place swap, on an Icehouse deployment. I don't have parallel I came across a couple of things in my search: https://wiki.openstack.org/wiki/Neutron/MigrationF

[Openstack-operators] nova-conductor scale out

Hi, Simple question: can I deploy nova-conductor across several servers? (Icehouse) Because we are reaching a limit in our controller node ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bi

[Openstack-operators] [nova] Removing seeded flavors

Hi all, I just wanted to float this past the operators list for visibility: Historically Nova has seeded some default flavors in an initial install. The way it has done this is really atypical of anything else we do, as it's embedded in the initial database schema migration. Since we're moving wh

[Openstack-operators] [nova] Mutable config options

Hi, I'm working on being able to reload a service's config file. This may be useful for EG turning debug logging on/off*, tweaking live migration parameters and changing the number of workers. Operators, which options would you like to be mutable (reloadable)? I'm interested in Nova for now, if ot

[Openstack-operators] nova mitaka->newton online_data_migrations

Hello there, before doing the upgrade, when still in Mitaka (tag 13.1.3), I am running the folllwing command: nova-manage db online_data_migrations I get this output: Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future. Option "notif

[Openstack-operators] nova-api response time

Hello Ops. So I had a feeling that my Openstack API is running a bit slow, like it takes a couple of seconds to get a full list of all instances in Horizon for example, which is kind of a lot for a basic MySQL select-and-present job. This got me wondering to how can I measure execution times and f

[Openstack-operators] [nova] Cells v2 FAQs

FYI, I've started a series of changes to add FAQs to the nova devref about cells v2: https://review.openstack.org/#/q/topic:cells-v2-docs The first few questions are based on things that have come up in IRC. If you have other things you'd like to see here, please reply to this thread, or bett

Re: [Openstack-operators] [Nova] Deprecating localfs?

On 6/7/2017 10:20 PM, Michael Still wrote: Greetings from an ancient thread (but the most recent on to openstack-dev about localfs that I can find). In 2014, which were heady times, we decided that we couldn't deprecate nova.virt.disk.vfs.localfs because we theorised that FreeBSD and containe

Re: [Openstack-operators] [Nova] Deprecating localfs?

Those notes are helpful, thanks. Were the freebsd and container cases from this ancient thread discussed as well? Michael On 9 Jun 2017 2:25 PM, "Matt Riedemann" wrote: > On 6/7/2017 10:20 PM, Michael Still wrote: > >> Greetings from an ancient thread (but the most recent on to openstack-d

Re: [Openstack-operators] [Nova] Deprecating localfs?

On 6/8/2017 11:35 PM, Michael Still wrote: Were the freebsd and container cases from this ancient thread discussed as well? I don't remember talking about that at the PTG, no. -- Thanks, Matt ___ OpenStack-operators mailing list OpenStack-operator

[Openstack-operators] [nova] Queens review priorities

I should have done this shortly after the PTG in September, surely before the Summit in November, most certainly before the queens-2 milestone, but...I didn't. Anyway, better late than never. Here is the patch that documents the review priorities for Queens, per my recollection from the PTG:

[Openstack-operators] nova 17.0.1 released (queens)

I just wanted to give a heads up to anyone thinking about upgrading to queens that nova has released a 17.0.1 patch release [1]. There are some pretty important fixes in there that came up after the queens GA so if you haven't upgraded yet, I recommend going straight to that one instead of 17.

[Openstack-operators] nova-placement-api tuning

Looking for recommendations on tuning of nova-placement-api. I have a few moderately-sized deployments (~200 nodes, ~4k instances), currently on Ocata, and instance creation is getting very slow as they fill up. I discovered that calls to placement seem to be taking a long time, and even thi

Re: [Openstack-operators] Nova HTTPConnectionPool Error

Hi, look into /var/logs/nova/nova-compute.log to understand why the service isn’t started! On Sep 11, 2014, at 13:16, Hossein Zabolzadeh wrote: > Hi there, > After successful installation of both keystone and glance, my Nova > service didn't work. The following error was occured when I executed

Re: [Openstack-operators] Nova HTTPConnectionPool Error

Check your nova.conf to make sure: A- You are not using any credentials B- You are and they match the ones you are using for RabbitMQ On Sep 11, 2014, at 13:27, Hossein Zabolzadeh wrote: > My nova-compute.log contains: > Connecting to AMQP server on localhost:5672 > ERROR oslo.messaging._driver

Re: [Openstack-operators] Nova HTTPConnectionPool Error

My nova-compute.log contains: Connecting to AMQP server on localhost:5672 ERROR oslo.messaging._drivers.impl_rabbit [-] AMQP server localhost:6572 closed the connection. Check login credentials: Socket closed On 9/12/14, Razique Mahroua wrote: > Hi, look into /var/logs/nova/nova-compute.log to u

[Openstack-operators] nova-network manual installation

Hi all, I have an openstack IceHouse environment with 1 controller and 1 compute node with all the compute services including nova-network. The compute node is using Vmware as a hypervisor. I am able to boot instances with no problem, but my instances don't get any IP address. The only time I am

Re: [Openstack-operators] Nova HTTPConnectionPool Error

abolzadeh > Date: Fri, 12 Sep 2014 13:31:25 +0430 > Subject: Re: [Openstack-operators] Nova HTTPConnectionPool Error > To: Razique Mahroua > > I fixed it. But now in my nova-compute.log a new error meesage was shown: > unexpected error while running command. command: sudo nova-r

[Openstack-operators] [nova] StarlingX diff analysis

In case you haven't heard, there was this StarlingX thing announced at the last summit. I have gone through the enormous nova diff in their repo and the results are in a spreadsheet [1]. Given the enormous spreadsheet (see a pattern?), I have further refined that into a set of high-level charts

[Openstack-operators] [nova] Removing the CachingScheduler

It's been deprecated since Pike, and the time has come to remove it [1]. mgagne has been the most vocal CachingScheduler operator I know and he has tested out the "nova-manage placement heal_allocations" CLI, added in Rocky, and said it will work for migrating his deployment from the CachingSc

Re: [Openstack-operators] Nova hypervisor uuid

On 11/27/2018 11:32 AM, Ignazio Cassano wrote: Hi  All, Please anyone know where hypervisor uuid is retrived? Sometime updating kmv nodes with yum update it changes and in nova database 2 uuids are assigned to the same node. regards Ignazio ___ Op

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

On 03/06/2015 07:19 AM, Sylvain Bauza wrote: Hi, First, sorry for cross-posting on both dev and operator MLs but I also would like to get operators feedback. So, I was reviewing the scheduler ComputeFilter and I was wondering why the logic should be in a filter. We indeed already have a check o

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

On 3/6/15 10:27 AM, Jay Pipes wrote: As for adding another CONF option, I'm -1 on that. I see no valid reason to schedule workloads to disabled hosts. There may be a better way to skin this cat, but one scenario is we have a host that has alerted, we want to evacuate it and prevent any future

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

On 03/06/2015 10:43 AM, Jesse Keating wrote: On 3/6/15 10:27 AM, Jay Pipes wrote: As for adding another CONF option, I'm -1 on that. I see no valid reason to schedule workloads to disabled hosts. There may be a better way to skin this cat, but one scenario is we have a host that has alerted,

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

I was wondering if doing the target host deployment is effected by the status of the compute host? IE can you do: nova boot --availability-zone : on a server that is marked as disabled in nova? Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC.

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

On 3/6/15 10:48 AM, Jay Pipes wrote: Have you ever done this in practice? One way of doing this would be to enable the host after adding it to a host aggregate that only has your administrative tenant allowed. Then launch an instance specifying some host aggregate extra_spec tag and the launch

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

On 03/06/2015 10:54 AM, Jesse Keating wrote: On 3/6/15 10:48 AM, Jay Pipes wrote: Have you ever done this in practice? One way of doing this would be to enable the host after adding it to a host aggregate that only has your administrative tenant allowed. Then launch an instance specifying some

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

(Adding back the -dev ML as it was removed) Le 06/03/2015 20:25, Jay Pipes a écrit : On 03/06/2015 10:54 AM, Jesse Keating wrote: On 3/6/15 10:48 AM, Jay Pipes wrote: Have you ever done this in practice? One way of doing this would be to enable the host after adding it to a host aggregate t

Re: [Openstack-operators] [nova] Deprecation of ComputeFilter

Hi Kris, Yes. It should work with even disabled host. Thanks, Kazu -Original Message- From: Kris G. Lindgren [mailto:klindg...@godaddy.com] Sent: Saturday, March 07, 2015 3:54 AM To: Jesse Keating; Jay Pipes; openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators

[Openstack-operators] [nova-docker] Request for Volunteers

Dear Ops folks, I just sent this on openstack-dev list, in case anyone is interested in helping with nova-docker. http://markmail.org/message/geijiljch4yxfcvq thanks, dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org htt

[Openstack-operators] nova-no-nd-relfection error

Hi My setup was workign earlier but when I launch the instance i get the error No valid host found on UI. I checked the nova logs I foud the below error: ERROR nova.compute.manager [req-9067a648-b77b-47c9-baa5-e10d3352f81d 4ca4e46cf5564ce5b158bf2eef161618 6341291002db49b8ae6baa6e6c6455f3] [inst

[Openstack-operators] [nova] disk I/O perfomance

Hello, all. We have measured disk I/O performance on openstack virtual machines with aid of FIO tool. We've tested performance on root dist drive device, test consists of write operationby 4kb blocks to file with size 90Gb (prefilled in advance). We use qcow2 image for vm, ephemeral drive a

[Openstack-operators] nova api versions under kilo

This call curl -s -H "X-Auth-Token:${token}" http://hostname:8774/ Against this version of nova-api: Version: 1:2015.1.1+a40~g2864505+trusty-1 returns only a version with id of v2.0, Making that call against devstack returns versions with ids v2.0 and v2.1. Is there anything you need to do on

[Openstack-operators] nova api versions under kilo

Hi Andrew, In Kilo, nova v2.1 API is disabled as the default value in Nova code. And devstack changes the config to enabled. We(nova dev team) have fixed it in Liberty by changing the default value to enabled with https://review.openstack.org/#/c/202724 So if you need to enable v2.1 in Kilo, ple

Re: [Openstack-operators] nova-neutron with vsphere

Hi Miko, it is possible to develop a neutron extension for achieveing your goal. Indeed for a customer we developed a ML2 driver that creates the needed portgroups and connect them to the right vlan in vCenter and hence when VMware VMs are created connect them to the create portgroups. The solution

Re: [Openstack-operators] nova-neutron with vsphere

you may have a look also at this project which uses a vm inside vcenter: https://wiki.openstack.org/wiki/Neutron/Networking-vSphere Br, Federico -- Future Internet is closer than you think! http://www.fiware.org Official Mirantis partner for OpenStack Training https://www.create-net.org/communi

Re: [Openstack-operators] nova-neutron with vsphere

Hi Federico, the link you suggested is very interesting but I did not find a link to download the vm appliance for vmware. Regards Ignazio 2015-09-24 11:25 GMT+02:00 Federico Michele Facca < federico.fa...@create-net.org>: > you may have a look also at this project which uses a vm inside vcenter

Re: [Openstack-operators] nova-neutron with vsphere

Hi Ignazio, never tested it, I may suppose that during the installation the appliance is created or downloaded (but I may be totally wrong). As by documentation: For help using or hacking on OVSvApp solution, you can send an email to the OpenStack Development Mailing List

Re: [Openstack-operators] nova-neutron with vsphere

Thanks 2015-09-24 11:49 GMT+02:00 Federico Michele Facca < federico.fa...@create-net.org>: > Hi Ignazio, > never tested it, I may suppose that during the installation the appliance > is created or downloaded (but I may be totally wrong). As by documentation: > > For help using or hacking on OVSvA

Re: [Openstack-operators] nova-neutron with vsphere

Federico, I presume you speak italian. Your company is a Mirantis partner ? We are going to select an openstack distro and we need to speak about mirantis. Ignazio 2015-09-24 11:52 GMT+02:00 Ignazio Cassano : > Thanks > > 2015-09-24 11:49 GMT+02:00 Federico Michele Facca < > federico.fa...@create

Re: [Openstack-operators] nova-neutron with vsphere

Ciao Ignazio, As you evinced from my "itanglish", I am italian :) and, yees we are official partners with Mirantis for OpenStack training: https://training.mirantis.com/mirantis-training-partners Feel free to contact me directly for any inquiry. Regards, Federico Br, Federico -- Future Internet

Re: [Openstack-operators] nova-neutron with vsphere

Miko, There’s a VDS driver for Neutron in addition to the NSX one that you might want to have a look at if you haven’t already. Some notes on that here (these are from the admin guides for the VMware Integrated OpenStack distribution as it does a pretty good job of describing the requirements,

Re: [Openstack-operators] nova-neutron with vsphere

As early mentioned this week, Mark's option is a valid alternative (separate regions). @ Mark, I wonder if this excpert from your pointer is still valid: "VDS-based networking has limitations, including the inability of tenants to create their own private L2 networks, and the inability to deliver

Re: [Openstack-operators] nova-neutron with vsphere

Yes: as the document there notes, the VDS driver uses provider networks (which in Neutron are created by the admin rather than the tenant and basically map neutron networks to VLANs in the physical datacenter network) and therefore punt L3 operations to the datacenter network. At Your Service,

Re: [Openstack-operators] nova-neutron with vsphere

Thanks all for your contribution on my request. I already knew VIO ( previous version 1.0 ) but i just wanted to see what I could (or could not) do without NSX . Miko ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org

[Openstack-operators] Nova resource limits not working

Hello, I have set my images to limit to 10MB/s bandwidth but it dos not get limited. Do I have the wrong driver? cat /etc/nova/nova-compute.conf [DEFAULT] compute_driver=libvirt.LibvirtDriver neutron_ovs_bridge=br-int [libvirt] virt_type=kvm vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDri

[Openstack-operators] Nova Configure VG ephemeral-storage

Could someone point me in the right direction for documentation on configuring ephemeral-storage? through a VolumeGroup for nova compute hosts in Kilo? ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.or

Re: [Openstack-operators] Nova-network -> Neutron Migration

On 09/12/15 06:32, Kevin Bringard (kevinbri) wrote: Hey fellow oppers! I was wondering if anyone has any experience doing a migration from nova-network to neutron. We're looking at an in place swap, on an Icehouse deployment. I don't have parallel I came across a couple of things in my search

Re: [Openstack-operators] Nova-network -> Neutron Migration

> On 9 Dec 2015, at 2:16 PM, Tom Fifield wrote: > > NeCTAR used this script (https://github.com/NeCTAR-RC/novanet2neutron ) with > success to do a live nova-net to neutron using Juno. That’s correct except we were on Kilo. I’m not sure I would try to do this on Icehouse though, neutron was pr

Re: [Openstack-operators] Nova-network -> Neutron Migration

Awesome code! I just did a small testbed test and it worked nicely! Edgar On 12/8/15, 7:16 PM, "Tom Fifield" wrote: >On 09/12/15 06:32, Kevin Bringard (kevinbri) wrote: >> Hey fellow oppers! >> >> I was wondering if anyone has any experience doing a migration from >> nova-network to neutron

Re: [Openstack-operators] Nova-network -> Neutron Migration

Thanks, Tom, Sam, and Edgar, that's really good info. If nothing else it'll give me a good blueprint for what to look for and where to start. On 12/8/15, 10:37 PM, "Edgar Magana" wrote: >Awesome code! I just did a small testbed test and it worked nicely! > >Edgar > > > > >On 12/8/15, 7:16 PM,

Re: [Openstack-operators] Nova-network -> Neutron Migration

Anyone think we should make this script a bit more "official" ... perhaps in the networking guide? On Wed, Dec 9, 2015 at 9:01 AM, Kevin Bringard (kevinbri) < kevin...@cisco.com> wrote: > Thanks, Tom, Sam, and Edgar, that's really good info. If nothing else > it'll give me a good blueprint for wh

Re: [Openstack-operators] Nova-network -> Neutron Migration

Yea, I was considering updating the wiki (https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo) to at least make mention of it. If it works (and it sounds like it does, at least for Juno) then I'm all for adding it as a potential resource On 12/9/15, 9:52 AM, "Matt Kassawa

Re: [Openstack-operators] Nova-network -> Neutron Migration

ngard (kevinbri)" Cc: Edgar Magana, Tom Fifield, OpenStack Operators Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration Anyone think we should make this script a bit more "official" ... perhaps in the networking guide? On Wed, Dec 9, 2015 at 9:01 AM, Kevin Bringard (

Re: [Openstack-operators] Nova-network -> Neutron Migration

ators mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration Yes! We should but with a huge caveat that is not not supported officially by the OpenStack community. At least the author wants to make a move with the Neutro

Re: [Openstack-operators] Nova-network -> Neutron Migration

, maybe we could use this as a good step 0. Edgar From: "Kris G. Lindgren" Date: Wednesday, December 9, 2015 at 8:57 AM To: Edgar Magana, Matt Kassawara, "Kevin Bringard (kevinbri)" Cc: OpenStack Operators Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration D

Re: [Openstack-operators] Nova-network -> Neutron Migration

tep > 0. > > >Edgar > > > > > >From: "Kris G. Lindgren" >Date: Wednesday, December 9, 2015 at 8:57 AM >To: Edgar Magana, Matt Kassawara, "Kevin Bringard (kevinbri)" >Cc: OpenStack Operators >Subject: Re: [Openstack-operators] Nova-

[Openstack-operators] [nova] Live migration bug triage

Hi, I'm having a go at triaging live migration bugs in nova that hurt operators at https://etherpad.openstack.org/p/mitaka-nova-live-migration-bugs . This is building up to a bug triage day and an associated push to close live migration bugs. I'd be interested in feedback on if there are specific

Re: [Openstack-operators] Nova-network -> Neutron Migration

e migration in multiple steps, maybe we could use this as a good step >> 0. >> >> >>Edgar >> >> >> >> >> >>From: "Kris G. Lindgren" >>Date: Wednesday, December 9, 2015 at 8:57 AM >>To: Edgar Magana, Matt Kassawara, "K

Re: [Openstack-operators] Nova-network -> Neutron Migration

e recommending to > >> make the migration in multiple steps, maybe we could use this as a good > step 0. > >> > >> > >>Edgar > >> > >> > >> > >> > >> > >>From: "Kris G. Lindgren" > >>Da

Re: [Openstack-operators] Nova-network -> Neutron Migration

nly solve the case of going from flatdhcp networks in >>>nova-network to same dchp/provider networks in neutron. Did anyone test to >>>see if it also works for doing more advanced nova-network configs? >>> >>> >>>_

Re: [Openstack-operators] Nova-network -> Neutron Migration

ll as mandating OVS. Since your branch indicates you're using linuxbridge on Icehouse, are you provisioning network nodes as part of your migration, or are you avoiding needing to provision network nodes in a different fashion? From: kevin...@cisco.com Subject: Re: [Openstack-operators] No

Re: [Openstack-operators] Nova-network -> Neutron Migration

e at the summit one way or another so I'd love to find some time to meet up and chat about it in person if you'd like. -- Kevin > >From: kevin...@cisco.com >Subject: Re: [Openstack-operators] Nova-network -> Neutron Migration > > > >Definitely, I can work on that.

Re: [Openstack-operators] Nova-network -> Neutron Migration

did not but more advanced could mean a lot of things for Neutron. There >> >>are so many possible scenarios that expecting to have a “script” to cover >> >>all of them is a whole new project. Not sure we want to explore than. In >> >>the past we were recommending to >

Re: [Openstack-operators] Nova-network -> Neutron Migration

possible scenarios that expecting to have a “script” to cover >>>all of them is a whole new project. Not sure we want to explore than. In the >>>past we were recommending to >>> make the migration in multiple steps, maybe we could use this as a good >>> step

Re: [Openstack-operators] Nova-network -> Neutron Migration

gt;>I did not but more advanced could mean a lot of things for Neutron. > There are so many possible scenarios that expecting to have a “script” to > cover all of them is a whole new project. Not sure we want to explore than. > In the past we were recommending to > >>> make the migr

Re: [Openstack-operators] Nova-network -> Neutron Migration

fying it. If I manage to get it working properly I'll >>>commit my changes to my fork and send it out. >>> >>>-- Kevin >>> >>> >>> >>>On 12/9/15, 10:00 AM, "Edgar Magana" wrote: >>> >>>>I did not but more adv

Re: [Openstack-operators] Nova-network -> Neutron Migration

ions because, specifically, in the >>>>migrate-secgroups.py it inserts into >>> the default_security_group table, which was introduced in Kilo. >>>> >>>>I'm working on modifying it. If I manage to get it working properly I'll >>>&

Re: [Openstack-operators] nova-conductor scale out

How many compute nodes do you have (that is triggering your controller node limitations)? We run nova-conductor on multiple control nodes. Each control node runs "N" conductors where N is basically the HyperThreaded CPU count. On Tue, Mar 15, 2016 at 8:44 AM, Gustavo Randich wrote: > Hi, > > Si

Re: [Openstack-operators] nova-conductor scale out

@lists.openstack.org>" mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] nova-conductor scale out How many compute nodes do you have (that is triggering your controller node limitations)? We run nova-conductor on multiple control nodes. Each contr

Re: [Openstack-operators] nova-conductor scale out

x Systems Engineer >> GoDaddy >> >> From: David Medberry >> Date: Tuesday, March 15, 2016 at 8:54 AM >> To: Gustavo Randich >> Cc: "openstack-operators@lists.openstack.org" < >> openstack-operators@lists.openstack.org> >> Subject:

Re: [Openstack-operators] nova-conductor scale out

ck-operators@lists.openstack.org" < > openstack-operators@lists.openstack.org> > Subject: Re: [Openstack-operators] nova-conductor scale out > > How many compute nodes do you have (that is triggering your controller > node limitations)? > > We run nova-conductor on multi

Re: [Openstack-operators] nova-conductor scale out

gt; Cc: David Medberry mailto:openst...@medberry.net>>, "openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>" mailto:openstack-operators@lists.openstack.org>> Subject: Re: [Openstack-operators] nova-conductor scale out PD: 32 cores

Re: [Openstack-operators] [nova] Removing seeded flavors

I recall these being embedded being a real operational pain when my team wanted to replace the defaults. +1 on removal On Mar 31, 2016 2:27 PM, "Dan Smith" wrote: > Hi all, > > I just wanted to float this past the operators list for visibility: > > Historically Nova has seeded some default flavor

Re: [Openstack-operators] [nova] Removing seeded flavors

+1 from me. We always just remove them and add our own. Like Dan said, it’s consistent with populating your own images. Mike Smith Lead Cloud Systems Architect Overstock.com On Apr 2, 2016, at 8:33 PM, Eric Windisch mailto:e...@windisch.us>> wrote: I recall these bei

Re: [Openstack-operators] [nova] Removing seeded flavors

I'll add a vote for removal, given how varied private clouds tend to be, the flavors are often "wrong" for any one particular purpose. R On Sat, Apr 2, 2016 at 8:41 PM, Mike Smith wrote: > +1 from me. We always just remove them and add our own. Like Dan said, > it’s consistent with populating

Re: [Openstack-operators] [nova] Removing seeded flavors

While I think it's fine to remove this from the normal setup, I think there should be either a file or process that one could run to add these basic flavors. I think without you will have things such as DevStack and other beginners not being able to get up and going. I think having the migration

Re: [Openstack-operators] [nova] Removing seeded flavors

I agree, if the flavors are removed, there should be a python script etc that can easily define the flavors using the CLI etc. Their presence may have been a presumption, but there are likely a lot of tests out there that depend upon the default flavors, and we should avoid breaking them until p

Re: [Openstack-operators] [nova] Removing seeded flavors

On 4/4/2016 3:43 PM, Joseph Bajin wrote: While I think it's fine to remove this from the normal setup, I think there should be either a file or process that one could run to add these basic flavors. I think without you will have things such as DevStack and other beginners not being able to get

Re: [Openstack-operators] [nova] Removing seeded flavors

Another remove vote. The only people this may affect are people standing up test clouds or new to OpenStack. For those folks that use puppet, the puppet community will be adding a provider to setup flavors since it's a feature that's been missing. I'll add a vote for removal, given how varied priv

  1   2   3   4   5   6   7   8   >