Re: [Openstack] [OpenStack][Nova][virt][hyperv]

t;Send Time:2016年10月27日(星期四) 16:14To:openstack <openstack@lists.openstack.org>Subject:Re: [Openstack] [OpenStack][Nova][virt][hyperv] On 10/27/2016 8:38 AM, zhaolihuisky wrote: > Hi, all > I want to use hyperv. > How to install nova-compute with source code on window

Re: [Openstack] [OpenStack][Nova][virt][hyperv]

On 10/27/2016 8:38 AM, zhaolihuisky wrote: Hi, all I want to use hyperv. How to install nova-compute with source code on windows 2012 operation system? Best Regards. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post

[Openstack] [OpenStack][Nova][virt][hyperv]

Hi, all I want to use hyperv. How to install nova-compute with source code on windows 2012 operation system? Best Regards. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org

Re: [openstack-dev] [openstack][nova] Port unbound from active VM

ck.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [openstack][nova] Port unbound from active VM I suggest filing a bug against nova for this. On Thu, Oct 13, 2016 at 9:44 AM, Ajay Kalambur (akalambu) <akala...@cisco.com<mailto:akala...@cisco.com>>

Re: [openstack-dev] [openstack][nova] Port unbound from active VM

M > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Subject: [openstack][nova] Port unbound from active VM > > Hi > There seems to be a corner case bug in nova code. Steps to reproduce it are > &g

Re: [openstack-dev] [openstack][nova] Port unbound from active VM

ists.openstack.org>> Subject: [openstack][nova] Port unbound from active VM Hi There seems to be a corner case bug in nova code. Steps to reproduce it are 1. Create a neutron port 2. Create a VM and launch instance with this port 3. Shutdown nova compute and network agent on comp

[openstack-dev] [openstack][nova] Port unbound from active VM

Hi There seems to be a corner case bug in nova code. Steps to reproduce it are 1. Create a neutron port 2. Create a VM and launch instance with this port 3. Shutdown nova compute and network agent on compute node 4. Unbind port from VM and delete the VM (offline delete) 5. Now

[Openstack] Nova scheduler tries to assign an already-in-use SRIOV QAT VF to a new instance (openstack-mitaka)

Hi, Upon trying to create VM instance (Say A) with one QAT VF, it fails with the following error i.e., “Requested operation is not valid: PCI device :88:04.7 is in use by driver QEMU, domain instance-0081”. Please note that, PCI device :88:04.7 is already being assigned to another VM

Re: [Openstack] Nova-Glance Query

Hi, I found the Solution, so thought to share with all and Brian one of member here also confirmed, so i believe its correct. So while creating metadata what i was doing wrong is, metadata={key:value}, if my value is integer i was passing it as it is. while i need pass it as string. so,

Re: [Openstack] Nova-Glance Query

Amit, For Glance, all the user-specified image metadata must be String data type. You can see this in the image schema [0], where "additionalProperties": {"type": "string"} (The only image properties that are *not* strings are those assigned non-string types in the schema.) So for your

[Openstack] Nova-Glance Query

Hi, I am using python-openstackclient and os_client_config My requirement is, i want to update, my image metadata i made two objects, by which i think i may achieve it: nova = os_client_config.make_client('compute') glance = os_client_config.make_client('images') example: metadata =

[Openstack] nova-docker setup in devstack

Good Day, Hope everyone doing good, I am trying to configure nova-docker in the devstack. I am using Mitaka version. Tried following nova-docker documentation for setup. I am still facing the issue with the installation. Getting the error as follows: 2016-09-01 10:10:48.213 |

Re: [openstack-dev] [RDO] [TripleO] [Packstack] qemu-kvm >= 2.3 now explicitely required for OpenStack Nova >= Newton

; Hi, > > Until now, the openstack-nova package in RDO had a lax requirement on > qemu-kvm which potentially meant an older version of qemu-kvm (or > qemu-kvm-rhel) would be installed [1]. > > We have agreed at the RDO meeting this morning to go ahead and > formally require qemu-kvm

[openstack-dev] [RDO] [TripleO] [Packstack] qemu-kvm >= 2.3 now explicitely required for OpenStack Nova >= Newton

Hi, Until now, the openstack-nova package in RDO had a lax requirement on qemu-kvm which potentially meant an older version of qemu-kvm (or qemu-kvm-rhel) would be installed [1]. We have agreed at the RDO meeting this morning to go ahead and formally require qemu-kvm >= 2.3 from Newton onwa

Re: [Openstack] nova/neutron vs heat - run as regular user

: [Openstack] nova/neutron vs heat - run as regular user As 'joeuser' in tenant/project 'joetenant' I can create a 'direct' neutron port and boot a nova instance with the just created port. The neutron network is owned by 'joetenant' However, using the same user/tenant when I create another

[Openstack] nova/neutron vs heat - run as regular user

As 'joeuser' in tenant/project 'joetenant' I can create a 'direct' neutron port and boot a nova instance with the just created port. The neutron network is owned by 'joetenant' However, using the same user/tenant when I create another instance with the same resource types using heat, stack

Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

Thanks. You make it clear. > -Original Message- > From: Gary Kotton [mailto:gkot...@vmware.com] > Sent: Wednesday, August 10, 2016 8:50 PM > To: guoyong 03239 (CCPL); 'openstack@lists.openstack.org' > Subject: Re: [Openstack] [openstack][nova][vmware] why deprecate map

Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

: openstack@lists.openstack.org Subject: Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster? I believe the usecase is to manage multiple vcenter cluster with one nova-compute instance. And if we restricting this would not make any sense. Regards

[Openstack] [openstack][nova][vmware] why deprecate mapping one-compute to multi vcenter cluster?

Anybody knows reason? ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

Hi, This was breaking the code in many places, for example snapshots, rescue etc. For spinning up VM’s the very simple use case worked. So we derpracated it. If you want more than one cluster supported I suggest running an additional nova-compute. The trade off is a little extra resources for

Re: [Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

I believe the usecase is to manage multiple vcenter cluster with one nova-compute instance. And if we restricting this would not make any sense. Regards, Vaidyanath On Wed, Aug 10, 2016 at 3:27 PM, Guoyong wrote: > Anybody knows reason? >

[Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

Anybody knows reason? - 本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and

[Openstack] [openstack][nova][vmware] why deprecate mapping one nova-compute to multi vcenter cluster?

Anybody knows reason? - 本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and

Re: [Openstack] nova+vmware doesn't create the cached image in ipaddress_base folder

, Gary Kotton <gkot...@vmware.com> wrote: > >> Hi, >> >> I suggest that you make use of the variable cache_prefix. >> >> >> https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/vmops.py#L156 >> >> The IP address just creates havoc… &

Re: [Openstack] nova+vmware doesn't create the cached image in ipaddress_base folder

PM, Gary Kotton <gkot...@vmware.com> wrote: > Hi, > > I suggest that you make use of the variable cache_prefix. > > > https://github.com/openstack/nova/blob/master/nova/virt/vmwareapi/vmops.py#L156 > > The IP address just creates havoc… > > Thanks > >

[Openstack] nova+vmware doesn't create the cached image in ipaddress_base folder

nova boot fails as the image created with oslo_vmware/api.py is creating the vm outside the base folder. though the x.x.x.x_base folder is present it is not creating it inside the vm my cofiguration is as follows. 1. controller and compute node in one vcenter server 2. the compute manages a

Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

nstack@lists.openstack.org Subject: Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network yeah.. my notes do the same as what you suggest. 1. create your neutron ports 2. pass port attributes to user-data script or use cloud-config as per the below. https://cloudinit.readthedocs

Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

gt; > params: > > $IPADDR: { get_attr: [ myserver, addresses, no-dhcp-net, 0, > addr ] } > > > > For now, I am going back to creating port and pass in that information as > user data. > > > > > > -Kaustubh > > > > *From:*

Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

gt; > > For now, I am going back to creating port and pass in that information as > user data. > > > > > > -Kaustubh > > > > *From:* Brent Troge [mailto:brenttroge2...@gmail.com] > *Sent:* Wednesday, July 20, 2016 7:27 PM > *To:* Kaustubh Kelkar <kaust

Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

20, 2016 7:27 PM To: Kaustubh Kelkar <kaustubh.kel...@casa-systems.com> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network Isn't that exposed through outputs ? And then use the output combined with configdrive cloudinit to c

Re: [Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

Isn't that exposed through outputs ? And then use the output combined with configdrive cloudinit to configure your NICS outputs: instance_ip: description: The IP address of the deployed instance value: { get_attr: [my_instance, first_address] } On Jul 20, 2016 5:58 PM, "Kaustubh

[Openstack] [OpenStack][Nova] Configuring IP address on a DHCP disabled network

My use case involves booting up an instance attached to two networks - one having Neutron DHCP service running and one without. Looking within the documentation [1], I was hoping to use configuration drive to provide IP information for the second interface. But, if I understand correctly, one

Re: [Openstack] Nova scheduler - change server group name

On 07/20/2016 10:13 AM, Frank Ritchie wrote: Hi all Does anyone know if it is safe to change the name of a Nova Scheduler server group directly in the database? Yeah, should be safe to do this. instance_groups.name is a non-unique column that isn't used for indexes, lookups or really

[Openstack] Nova scheduler - change server group name

Hi all Does anyone know if it is safe to change the name of a Nova Scheduler server group directly in the database? Thx ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org

[Openstack] nova drop port after VMs was evacuated through host-evacuate and failed compute was started again

Hello. Recently my compute was failed and I run host-evacuate, the VMs was started properly, but after failed compute was started again, nova was dropped ports of VMs which was evacuated with next log in nova-compute.log: 2016-07-15 03:29:59.013 4617 INFO nova.network.neutronv2.api

[Openstack] [openstack][nova] snapshot image queued, saving, deleted.

Hi , I brought up vm on openstack lierty, trying to create a snapshot but getting BadstatusLine: '' error , tried two times but got same status. 2016-07-14 18:18:00.072 65462 ERROR nova.compute.manager [instance: 275426c5-2fdb-4a9c-9065-398700acf650] Traceback (most recent call last):

[Openstack] [Nova] InstanceNotFound: Instance "UUID" could not be found.

Hi all, Recently, I am getting this error message below suddenly. = ==> /var/log/nova/nova-compute.log <== 2016-06-30 09:49:04.051 23236 ERROR nova.compute.resource_tracker

Re: [Openstack] Reg: not able to start openstack-nova-compute.service in compute node

On Jun 27, 2016, at 12:32 PM, venkat boggarapu wrote: > Check login credentials Seems pretty straight forward to me. You're having the wrong username/password when connecting to RabbitMQ. Try this: rgrep -E '^rabbit_' /etc -- Choose a job you love, and you will never have to work a day

[Openstack] Reg: not able to start openstack-nova-compute.service in compute node

Hi All, we are installing mitaka openstack on centos 7.2 As per the document http://docs.openstack.org/mitaka/install-guide-rdo/nova-compute-install.html . We are trying to install the compute node,but we are getting the error while starting the openstack-nova-compute.service the services both

Re: [Openstack] nova service-list error

On Jun 24, 2016, at 3:06 PM, venkat boggarapu wrote: > When i am trying to run the command nova service-list i am getting the > below error If you run the following command, what do you get? env | grep ^OS | sort -- Imagine you're an idiot and then imagine you're in the government. Oh,

Re: [Openstack] nova service-list error

You need a domain in your environment variables, e.g. export OS_USER_DOMAIN_NAME= or export OS_USER_DOMAIN_ID= Your environment script should provide OS_PROJECT_DOMAIN_NAME OS_USER_DOMAIN_NAME OS_PROJECT_NAME OS_USERNAME OS_PASSWORD OS_AUTH_URL=http://controller:35357/v3 --> (or

[Openstack] nova service-list error

HI All, When i am trying to run the command nova service-list i am getting the below error ERROR (BadRequest): Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400)

Re: [Openstack] [Nova][Ironic] An issue of provision 3 ironic nodes using Heat

com> Cc: openstack@lists.openstack.org Subject: Re: [Openstack] [Nova][Ironic] An issue of provision 3 ironic nodes using Heat Hi Gary, this is a known limitation of current model of Nova/Ironic interaction, which should be solved with ongoing Resource Providers work [0]. In the meantime I

Re: [Openstack] nova "get-password " returns blank line

half Of *David > Medberry > *Sent:* mercredi 15 juin 2016 19:21 > *To:* Jean-Pierre Ribeauville <jpribeauvi...@axway.com> > *Cc:* openstack@lists.openstack.org > *Subject:* Re: [Openstack] nova "get-password " returns blank line > > > > It all depends on ho

Re: [Openstack] Nova and Magnum on the same host?

On Jun 16, 2016, at 1:51 PM, Tomas Vondra wrote: > You cannot have two drivers in one process. Bummer!! But thanx, I'll thing about how to solve this. -- Michael Jackson is not going to buried or cremated but recycled into shopping bags so he can remain white, plastic and dangerous for kids to

Re: [Openstack] Nova and Magnum on the same host?

Turbo Fredriksson writes: > > On Jun 9, 2016, at 11:55 AM, Ricardo Carrillo Cruz wrote: > > > https://wiki.openstack.org/wiki/Docker > > I'm trying this and although I know very little of OS (and I haven't > managed to boot up my first container yet because of other issues), I >

Re: [Openstack] nova "get-password " returns blank line

ck.org Subject: Re: [Openstack] nova "get-password " returns blank line It all depends on how you have setup your cloud. Most/many OpenStack clouds DO NOT inject into the instance and the password feature is null and void. Look at: enable_instance_password = True (BoolOpt) E

Re: [Openstack] nova "get-password " returns blank line

It all depends on how you have setup your cloud. Most/many OpenStack clouds DO NOT inject into the instance and the password feature is null and void. Look at: enable_instance_password = *True* (BoolOpt) Enables returning of the instance password by the relevant server API calls such as create,

[Openstack] nova "get-password " returns blank line

Hi, I'm trying to use nova get-password command. My centos-1 (using the "standard" CentOS OpenStack image) is running find and I'm able to log via ssh by using centos user and a key pair. But, the following command returns a blank line: [root@dhcp-10-128-11-58 tmp]# nova get-password

Re: [Openstack] Nova and Magnum on the same host?

On Jun 9, 2016, at 11:55 AM, Ricardo Carrillo Cruz wrote: > https://wiki.openstack.org/wiki/Docker I'm trying this and although I know very little of OS (and I haven't managed to boot up my first container yet because of other issues), I have the docker entry in the web GUI "Admin -> System ->

[Openstack] [Nova][Ironic] An issue of provision 3 ironic nodes using Heat

Hi, We are encountering a weird error when we try to use a heat template(resource group) to provision 3 baremetal machines. Only the first instance is provisioned successfully while other 2 instances failed because they are assigned to the same ironic node and they failed to bind a network

[openstack-dev] [stable] Re: [Openstack-stable-maint] Stable check of openstack/nova failed

penstack.org <openstack-stable-ma...@lists.openstack.org> Subject:  [Openstack-stable-maint] Stable check of openstack/nova failed > Build failed. > > - periodic-nova-docs-liberty > http://logs.openstack.org/periodic-stable/periodic-nova-docs-liberty/2ede148/ > : SUCCESS in 7m

Re: [Openstack] Nova and Magnum on the same host?

On Jun 9, 2016, at 11:55 AM, Ricardo Carrillo Cruz wrote: > If you just want to be able to run compute in containers and you don't need > fancy things like Kubernetes/Swarm etc No, that's what's Openstack is for :). Or at least why _I_ choose it.. > you can use a nova plugin: > >

Re: [Openstack] Nova and Magnum on the same host?

If you just want to be able to run compute in containers and you don't need fancy things like Kubernetes/Swarm etc, you can use a nova plugin: http://docs.openstack.org/liberty/config-reference/content/lxc.html https://wiki.openstack.org/wiki/Docker Ricky 2016-06-09 12:31 GMT+02:00 Turbo

Re: [Openstack] Nova and Magnum on the same host?

On Jun 9, 2016, at 10:03 AM, Tomas Vondra wrote: > AFAIK the Magnum service will run containers inside VMs. It is a > provisioning system for container orchestration services like Kubernetes. I see. It doesn't work very well for Kubernetes, but maybe Magnums is smarter.. :) > There are drivers

[Openstack] Nova and Magnum on the same host?

My use-case require me to have Containers for certain rings and real VMs for others. But I also want to utilize my hardware to max, while keeping the electricity bill (and cooling) as low as possible. This means that I need (want!) to run both the VMs and the Containers on the same host. I've

Re: [Openstack] [openstack][nova][neutron]How a vm is created?

You will find these two links very useful: 1. http://docs.openstack.org/icehouse/training-guides/ content/associate-computer-node.html#associate-vm-provisioning-indepth 2. https://ilearnstack.com/2013/04/26/request-flow-for-provisioning-instance-in-openstack/ On Thu, May 12, 2016

[Openstack] [openstack][nova][neutron]How a vm is created?

Hi, I wanted to know how a vm is created in openstack. There are so many components of each service that I am getting confused. I understand at a high level that nova-scheduler will find the compute host, nova-compute will create the vm and nova interacts with neutron for port allocation. But I

[Openstack] nova evactuate failed

Hi ALL I am currently testing openstack liberty in my centos 7 environment. I am planning to boot vm from volume using ceph backend. all the instances volumes are shared among all the compute nodes and I am able to do the nova migrate and nova live-migration. when I was testing the nova

[Openstack] [Nova][RabbitMQ] RabbitMQ beam.smp take high CPU usage issue with latest master code devstack environment

Hi All Last Wednesday I try to setup a devstack environment with latest openstack master code in one Ubuntu 14.04 LTS system, after devstack installation finished I have met RabbitMQ beam.smp take high CPU usage issue in the system, the RabbitMQ beam.smp process will take high CPU usage which

Re: [Openstack] nova backup

okay. I tested cinder backup to 2nd ceph cluster.  1. I created full backup 2. I created incremental backup But on 2nd ceph cluster I see two full size backup (each 20G) Do anybody know why? rbd --cluster bak -p backups du warning: fast-diff map is not enabled for

[Openstack] nova backup

Hello. When I try to create backup: nova backup testdeb testdeb_bak daily 2 nova-api said: ==> nova/nova-api.log <== 2016-04-21 16:40:14.828 2814 INFO nova.compute.api [req-e89878e7-9d26-4e6e-8922-8aa9bba56b72 8d384cc45d0c467eb46ef3f980cf314d 3029462986ac400ca2c2c6ac4c9af5a7 - - -] [instance:

Re: [Openstack] [nova] Hyperv devstack

) <paul.carlt...@hpe.com> Cc: openstack@lists.openstack.org Subject: RE: [Openstack] [nova] Hyperv devstack Hello, It sounds like the Hyper-V role / component is not working. You can check if it runs with: Get-Service vmms You can also check if it can properly run with: New-VM test |

Re: [Openstack] [nova] Hyperv devstack

failed to spawn 2016-04-12 13:51:57.980 2420 ERROR nova.compute.manager [instance: fe8f6dd6-f197-4fd5-9d8d-c0607f8219de] Traceback (most recent call last): 2016-04-12 13:51:57.980 2420 ERROR nova.compute.manager [instance: fe8f6dd6-f197-4fd5-9d8d-c0607f8219de] File "C:\OpenStack\Nova\Python2

Re: [Openstack] [nova] Hyperv devstack

5-95a1-0c78f0331a85 - - - - -] Acc essRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAI N. For details see the broker logfile. 2016-04-12 10:23:02.467 2148 ERROR nova Traceback (most recent call last): 2016-04-12 10:23:02.467 2148 ERROR nova File &

[Openstack] [nova] Hyperv devstack

Claudiu You may remember I've been trying to get the hyperv working with devstack. You shared with me the local.conf from your CI job but I still can't get it to work. It fails with 2016-04-07 10:56:40.612 | + lib/neutron-legacy:_move_neutron_addresses_route:881 : sudo ovs-vsctl

Re: [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Hello Remo, No, there is just one user "admin" and when I gave --all-tenants it returned the same output (without networks) BR, Varun On Wed, Mar 30, 2016 at 10:20 AM, Remo Mattei wrote: > Wrong user? > > Try --all-tenants and see what shows up as an admin > > Inviato da

Re: [openstack-dev] [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Hello Remo, No, there is just one user "admin" and when I gave --all-tenants it returned the same output (without networks) BR, Varun On Wed, Mar 30, 2016 at 10:20 AM, Remo Mattei wrote: > Wrong user? > > Try --all-tenants and see what shows up as an admin > > Inviato da

Re: [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Wrong user? Try --all-tenants and see what shows up as an admin Inviato da iPhone > Il giorno 30 mar 2016, alle ore 10:08, varun bhatnagar > ha scritto: > > Hi, > > I am using OpenStack Juno on a multinode setup. > When I did nova list I couldn't see any interfaces

Re: [openstack-dev] [Openstack] [OpenStack] "nova list" doesn't show networks for few instances

Wrong user? Try --all-tenants and see what shows up as an admin Inviato da iPhone > Il giorno 30 mar 2016, alle ore 10:08, varun bhatnagar > ha scritto: > > Hi, > > I am using OpenStack Juno on a multinode setup. > When I did nova list I couldn't see any interfaces

[openstack-dev] [OpenStack] "nova list" doesn't show networks for few instances

Hi, I am using OpenStack Juno on a multinode setup. When I did nova list I couldn't see any interfaces attached to few of my VMs although in Dashboard they are visible. -+ | ID | Name | Status | Task

Re: [Openstack] [Nova] [DPDK] [Liberty] Issues in booting VMs via Nova onto DPDK-enabled OVS

On 28 March 2016 at 05:21, N Vivekanandan <n.vivekanan...@ericsson.com> wrote: > Hi Openstack Team, > > > > We were trying to boot VMs via Openstack Nova (off Liberty release) into > DPDK-enabled OVS instances. > > Our OVS is version 2.5 + DPDK 2.2 + Qemu 2.

[Openstack] [Nova] [DPDK] [Liberty] Issues in booting VMs via Nova onto DPDK-enabled OVS

Hi Openstack Team, We were trying to boot VMs via Openstack Nova (off Liberty release) into DPDK-enabled OVS instances. Our OVS is version 2.5 + DPDK 2.2 + Qemu 2.3 + Libvirt 1.2.16. We followed the guidelines here for installation of OVS Datapath and enable them for DPDK: https://github.com

[Openstack] [Nova] Mitaka RC2 available

release candidate respin, this tarball will be formally released as final "Mitaka" versions on April 7th. You are therefore strongly encouraged to test and validate this tarball ! Alternatively, you can directly test the mitaka release branch at: http://git.openstack.org/cgit/openstack/n

[Openstack] [nova] how to recover instances with different hypervisor-id on the same compute node

Hi All, Due to a hostname change, we ended up having a new hypervisor-id for one of our compute nodes. It was already running two instances and then, we didn't catch the updated hypervisor-id. This ended up with new instances spawning up with new hypervisor-id. Now, the instances with older

[Openstack] [nova] Nova does not add ports to br-int after a neutron-ovs-cleanup

Hi. After running a neutron-ovs-cleanup and restarting openvswitch-agent and nova-compute with all the VMs running, nova does not add existing ports to br-int. All qvb@qvo exists but, after restarting nova-compute, only qvo from new machines are added correctly to the br-int. If I reboot the

Re: [Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

Mmm... I don't see any incompatibility issue. If there is any pointer regarding to unexpected behaviour of evacuate / migrate in Juno, it would be helpful. Cheers, S On Mon, Feb 29, 2016 at 7:43 PM, Shinobu Kinjo wrote: > On Mon, Feb 29, 2016 at 5:49 PM, Merlin Blom

[Openstack] liberty: openstack/nova client, flavor create/list results in errors - help please.

I have install Liberty under CentOS 7.2 using the CentOS-OpenStack-liberty repository. All verification procedures detailed in the installation guide run successfully. However, when I try to create flavors using either the openstack or nova clients, I get errors: [root@beaver beaver]#

Re: [Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

On Mon, Feb 29, 2016 at 5:49 PM, Merlin Blom wrote: > > > Am 29.02.2016 um 09:12 schrieb Shinobu Kinjo: >> >> Thanks for your reply. >> >> On Mon, Feb 29, 2016 at 4:58 PM, Merlin Blom >> wrote: Hello, When I do "nova evacuate

Re: [Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

Am 29.02.2016 um 09:12 schrieb Shinobu Kinjo: Thanks for your reply. On Mon, Feb 29, 2016 at 4:58 PM, Merlin Blom wrote: Hello, When I do "nova evacuate ${instance} ${host}", evacuate process ends up with being failed. Did you find any error messages in

Re: [Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

Hello, When I do "nova evacuate ${instance} ${host}", evacuate process ends up with being failed. Did you find any error messages in /var/log/nova/ I had the problem too. In my case the CPUs of the Hosts are not compatible. There is an information of that instance in nova.instances and

[Openstack] [Nova] Do nova evacuate / migrate, but it's failed.

Hello, When I do "nova evacuate ${instance} ${host}", evacuate process ends up with being failed. There is an information of that instance in nova.instances and "deleted_at" flag is set. "nova list" show nothing about that instance. But there is a still directory in

Re: [Openstack] nova service-disable

: [Openstack] nova service-disable On 02/22/2016 05:38 AM, Yngvi Páll Þorfinnsson wrote: > Hi > > I want to stop instances from beeing created on one of our compute > nodes, i.e. "*compute1*" > > But I want all current instances on *compute1* to be active and available. > &g

Re: [Openstack] nova service-disable

On 02/22/2016 05:38 AM, Yngvi Páll Þorfinnsson wrote: Hi I want to stop instances from beeing created on one of our compute nodes, i.e. „*compute1*“ But I want all current instances on *compute1* to be active and available. I thus disable the nova service for this node: # nova

[Openstack] nova service-disable

Hi I want to stop instances from beeing created on one of our compute nodes, i.e. "compute1" But I want all current instances on compute1 to be active and available. I thus disable the nova service for this node: # nova service-disable compute1 nova-compute Nova status of compute1 will then

Re: [Openstack] [Nova] [Cinder] Block device name / ordering

t; > > > > >Cheers, > > >Bruno > > > > It's not actually cinder that's picking the device name (mountpoint), > it's > > the libvirt driver (more specifically, the nova.virt.libvirt.blockinfo > > code). > > > > The change to ignore the u

Re: [Openstack] [Nova] [Cinder] Block device name / ordering

actually cinder that's picking the device name (mountpoint), it's > the libvirt driver (more specifically, the nova.virt.libvirt.blockinfo > code). > > The change to ignore the user-supplied device name for the libvirt driver > went into liberty [1]. I don't know all of the details

Re: [Openstack] [Nova] [Cinder] Block device name / ordering

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: 18 February 2016 03:11 > To: openstack@lists.openstack.org > Subject: Re: [Openstack] [Nova] [Cinder] Block device name / ordering > > > > On 2/17/2016 6:49 PM, Bru

Re: [Openstack] [Nova] [Cinder] Block device name / ordering

a specific device was not reliable with libvirt, so it's best to let libvirt pick the mountpoint for you. ndipanov and/or danpb in the #openstack-nova freenode channel would be able to give more information. As for figuring out which mountpoint the attachments are on, you have to wait for the volume

[Openstack] [Nova] [Cinder] Block device name / ordering

Hi everyone, Could not figure this one out based on docs, wiki, or previous posts on the mailing list. We use KVM as our hypervisor on the Catalyst Cloud in New Zealand. Unlike Xen, KVM does not support setting the device name (eg: /dev/vdc) of a cinder volume within the guest. If a user

[Openstack] Nova-api started misbehaving after most recent package upgrade

Hello Everyone, I was testing a new OpenStack deployment, and was unable to launch instances due to this bug: https://bugs.launchpad.net/nova/+bug/1508230 I did a sudo apt-get upgrade on my controller and compute nodes. After the upgrade, Horizon started returning "Error: Unable to retrieve

Re: [Openstack] Nova-api started misbehaving after most recent package upgrade

My bad, sorry everyone, please ignore my request. Apparently, the [neutron] group in nova.conf got accidentally deleted.Thanks.

[Openstack] Nova scheduler error notifications

Hi, In nova icehouse, when a 500 error happened, "scheduler.run_instance" event was generated. What is the event generated in nova kilo for a 500 error? The events have changed to "scheduler.select_destinations.start/end" . -- Best Regards, Ankita

Re: [Openstack] [NOVA] nova image-list error class 'glanceclient.exc.CommunicationError'> (HTTP 500)

openstack@lists.openstack.org> Subject: [Openstack] [NOVA] nova image-list error class 'glanceclient.exc.CommunicationError'> (HTTP 500) I am a new bee to the this list. After a lot of attempts to get this working wanted to try out the mailing list for ideas. Please review this email in detail be

Re: [Openstack] Nova DB sync Operational error

Link: https://openstack.nimeyo.com/31835/?show=68695#c68695 From: buptzhoutian The most likely reason : You configured your mysql connection in the [api_database] , not [database] ___ Mailing list:

Re: [openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Hi, I think for this kind of change you should register a Blueprint and submit a spec for discussion. Sounds like it will be a bit change. BR On Sun, Dec 13, 2015 at 2:18 AM, Alexandre Levine wrote: > Hi all, > > os-user-data extension implements server_create

Re: [openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Sorry, s/bit/big On Mon, Dec 14, 2015 at 10:46 AM, Zhenyu Zheng wrote: > Hi, I think for this kind of change you should register a Blueprint and > submit a spec for discussion. Sounds like it will be a bit change. > > BR > > On Sun, Dec 13, 2015 at 2:18 AM, Alexandre

[openstack-dev] [openstack][nova] Microversions support for extensions without Controller

Hi all, os-user-data extension implements server_create method to add user_data for server creation. No Controller is used for this, only "class UserData(extensions.V21APIExtensionBase)". I want to add server_update method allowing to update the user_data. Obviously I have to add it as a

Re: [Openstack] [Nova] Stable/liberty does not work with hybrid clouds

Ok, thanks! Missed that. Will resurrect that On 12/8/15, 11:39 AM, "Daniel P. Berrange" wrote: >On Tue, Dec 08, 2015 at 07:11:22AM +, Gary Kotton wrote: >> Hi, >> Yesterday we hit the following bug: https://launchpad.net/bugs/1523503. An >> initial patch was posted

Re: [Openstack] [Nova] Stable/liberty does not work with hybrid clouds

rge > https://github.com/openstack/nova/commit/e792d50efadb36437e82381f4c84d738cee25dfd. > The question is how are we going to back port this to stable/liberty. The > patch proposed is for a BP (which as we all know is not back port worthy). I see you abandoned your change, but that is not

<    1   2   3   4   5   6   7   8   9   10   >