[Openstack] [Nova] Instance creation problem

Hi. I'm setting up a Openstack system on the servers of my laboratory. While I try to create an instance, a problem has occurred! Instance creation was failed and it seems that libvirt failed to attaching the vif to the instance. When I create a virtual machine by using virsh tool (libvirt) manuall

Re: [Openstack] [openstack][nova|cinder] niscsiadm: Could not log into all portals || VolumeNotFound exception

You launch a volume-backed instance. The volume can't be attached, so the instance can't be launched. The volume can't be attached because iSCSI authentication fails. Either it's not set up correctly in cinder.conf on the controller, or you hit a bug. When you google for /iscsi authentication

[Openstack] [openstack][nova|cinder] niscsiadm: Could not log into all portals || VolumeNotFound exception

Hi, I have created a development setup with Devstack on 2 machines, where one is a controller + compute node (IP: 172.23.29.96) and other is a storage node(IP: 172.23.29.118). I am running all the services on the controller, except the c-vol service which runs on the storage node. Whenever I try

Re: [Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

ed to connect to neutron networks but > they should be able to use affinity > poileices. > > > > > > > > In short, our compute nodes have an SR-IOV Mellanox NIC (ConnectX-3) > > > > with 16 VFs configured. We wish to expose > > > > these VFs

Re: [Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

anox NIC (ConnectX-3) with 16 >> VFs configured. We wish to expose these VFs to VMs that schedule on the >> host. However, the NIC is in NUMA region 0 which means that only half of >> the compute node's CPU cores would be usable if we required VM affinity to >> the NI

Re: [Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

o VMs that schedule on the > host. However, the NIC is in NUMA region 0 which means that only half of the > compute node's CPU cores would be usable if we required VM affinity to the > NIC's NUMA region. But we don't need that, since we are okay with > cross-region a

[Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

only half of the compute node's CPU cores would be usable if we required VM affinity to the NIC's NUMA region. But we don't need that, since we are okay with cross-region access to the PCI device. However, we do need CPU pinning to work, in order to have efficient cache hits on our

[Openstack] [NOVA][KOLLA] not able to configure pci pass-through on gpu devices

Dear Openstack community, I am not able to configure PCI pass-through with GPUs successfully and was wondering if someone could give advice. physical machine: Dell C4140 DT-V and SR-IOV are enabled on BIOS # hosts names/role: openstack-deployment --> kolla deployment and openstack client cont

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

On Fri, 12 Oct 2018 20:06:04 -0700, Remo Mattei wrote: I do not have it handy now but you can verify that the image is indeed raw or qcow2 As soon as I get home I will dig the command and pass it on. I have seen where images have extensions thinking it is raw and it is not. You could try 'qe

Re: [Openstack] nova-api-os-compute slowdown

Hi, Finally, the issue solved. It is caused by the low number of connections set to memcached servers: 1024. I noticed too many files open and too many sockets errors in my logs. Changing the memcached max allowed connections to 2048 or higher solved my problem. You can check your memcached serve

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

Hi all I do not have it handy now but you can verify that the image is indeed raw or qcow2 As soon as I get home I will dig the command and pass it on. I have seen where images have extensions thinking it is raw and it is not. Remo >> Il giorno 12 ott 2018, alle ore 17:17, melanie witt ha

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

On Fri, 12 Oct 2018 21:50:27 +, Eugen Block wrote: I would consider this thread as closed. After I learned that nova imports flat images if the image's disk-format is not "raw" I tested some different scenarios to understand more about this topic. I still couldn't explain why nova did that in

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

Hi Melanie, thanks for your response. I would consider this thread as closed. After I learned that nova imports flat images if the image's disk-format is not "raw" I tested some different scenarios to understand more about this topic. I still couldn't explain why nova did that in the speci

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

On Tue, 09 Oct 2018 08:01:01 +, Eugen Block wrote: So it's still unclear why nova downloaded a raw glance image to the local filesystem during the previous attempt. I always knew that with Ceph as backend it's recommended to use raw images but I always assumed the "disk-format" was not more

Re: [Openstack] nova-api-os-compute slowdown

Hi, I found that my controller nodes were a bit overloaded with 16 uwsgi nova-api-os compute processes. I reduced the nova-api-os uwsgi processes to 10 and timeout and slowdowns were eliminated. My cloud went stable and the response times went lower. I have 20 vcpus on a Xeon(R) CPU E5-2630 v4 @ 2

Re: [Openstack] [nova][ceph] Libvirt Error when add ceph as nova backend

Hi, the keyrings and caps seem correct to me. yes both nodes, ceph & nova-compute node was on same network 192.168.26.xx/24 , does any special port need to allow at firewalld ? Yes, the firewall should allow the traffic between the nodes. If this is just a test environment you could try dis

Re: [Openstack] [nova][ceph] Libvirt Error when add ceph as nova backend

Hi, This is my ceph node ( using single node ceph) for test only > [cephdeploy@ceph2 ~]$ cat /etc/ceph/ceph.client.nova.keyring > [client.nova] > key = AQBLxr5bbhnGFxAAXAliVJwMU5w5YgFY6jGJIA== > [cephdeploy@ceph2 ~]$ ceph auth get client.nova > exported keyring for client.nova > [client.nova] > ke

Re: [Openstack] [nova][ceph] Libvirt Error when add ceph as nova backend

Hi, your nova.conf [libvirt] section seems fine. Can you paste the output of ceph auth get client.nova and does the keyring file exist in /etc/ceph/ (ceph.client.nova.keyring)? Is the ceph network reachable by your openstack nodes? Regards, Eugen Zitat von Adhi Priharmanto : Hi, Im runni

[Openstack] [nova][ceph] Libvirt Error when add ceph as nova backend

Hi, Im running my openstack environment with rocky release, and I want to integrate ceph as nova-compute backend, so I followed instruction here : http://superuser.openstack.org/articl... and this is my nova.conf at my comput

Re: [Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

Hi, I just wanted to follow up on this for documentation purpose. Although I still don't have all answers there's something I can explain. When I upload a new image (iso) to create a new base image for glance, and I use "--disk-format iso", this will lead to the described behavior, nova w

[Openstack] nova-api-os-compute slowdown

Hi, After a few tempest run I noticed slowdowns in the nova-api-os-compute uwsgi  processes. I check the processes with py-spy and found that a lot of process blocked on read(). Here is my py-spy output from one of my nova-api-os-compute uwsgi process: http://paste.openstack.org/show/731677/ And

[Openstack] [Nova][Glance] Nova imports flat images from base file despite ceph backend

Hi list, this week I noticed something strange in our cloud (Ocata). We use Ceph as backend for nova, glance and cinder, everything really works like a charm. But from time to time we've noticed that some instances take much longer to launch than others. So I wanted to take a look what's h

[Openstack] [Nova][Cyborg] Cyborg-Nova integration -- new submitted Cyborg implementation code

Hi, I have noticed there are more and more developers who are interested in Cyborg at PTG, and there are also some valuable outputs after this PTG. According to the summary at this PTG(https://etherpad.openstack.org/p/cyborg-nova-ptg-stein ), 4 possible solutions about how Nova interact with Cy

Re: [Openstack] [nova]Capacity discrepancy between command line and MySQL query

On Tue, Aug 28, 2018 at 5:12 PM Jay Pipes wrote: > > On 08/27/2018 09:40 AM, Risto Vaaraniemi wrote: > > Hi, > > > > I tried to migrate a guest to another host but it failed with a > > message saying there's not enough capacity on the target host even > > though the server should me nearly empty.

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On Tue, Sep 18, 2018 at 4:31 PM, Peter Penchev wrote: > On Tue, Sep 18, 2018 at 03:07:45PM +0200, Attila Fazekas wrote: > > On Tue, Sep 18, 2018 at 2:09 PM, Peter Penchev < > openstack-...@storpool.com> > > wrote: > > > > > On Tue, Sep 18, 2018 at 11:32:37AM +0200, Attila Fazekas wrote: > > > [fo

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On Tue, Sep 18, 2018 at 03:07:45PM +0200, Attila Fazekas wrote: > On Tue, Sep 18, 2018 at 2:09 PM, Peter Penchev > wrote: > > > On Tue, Sep 18, 2018 at 11:32:37AM +0200, Attila Fazekas wrote: > > [format recovered; top-posting after an inline reply looks confusing] > > > On Mon, Sep 17, 2018 at 1

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On Tue, Sep 18, 2018 at 3:07 PM, Attila Fazekas wrote: > > > On Tue, Sep 18, 2018 at 2:09 PM, Peter Penchev > wrote: > >> On Tue, Sep 18, 2018 at 11:32:37AM +0200, Attila Fazekas wrote: >> [format recovered; top-posting after an inline reply looks confusing] >> > On Mon, Sep 17, 2018 at 11:43 PM

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On Tue, Sep 18, 2018 at 2:09 PM, Peter Penchev wrote: > On Tue, Sep 18, 2018 at 11:32:37AM +0200, Attila Fazekas wrote: > [format recovered; top-posting after an inline reply looks confusing] > > On Mon, Sep 17, 2018 at 11:43 PM, Jay Pipes wrote: > > > > > On 09/17/2018 09:39 AM, Peter Penchev w

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On Tue, Sep 18, 2018 at 11:32:37AM +0200, Attila Fazekas wrote: [format recovered; top-posting after an inline reply looks confusing] > On Mon, Sep 17, 2018 at 11:43 PM, Jay Pipes wrote: > > > On 09/17/2018 09:39 AM, Peter Penchev wrote: > > > >> Hi, > >> > >> So here's a possibly stupid question

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

Create a volume transfer VM/machine in each region. attache the volume -> dd -> compress -> internet ->decompress -> new volume, attache(/boot with) to the volume to the final machine. In case you have frequent transfers you may keep up the machines for the next one.. In case the storage is jus

Re: [Openstack] [nova][cinder] Migrate instances between regions or between clusters?

On 09/17/2018 09:39 AM, Peter Penchev wrote: Hi, So here's a possibly stupid question - or rather, a series of such :) Let's say a company has two (or five, or a hundred) datacenters in geographically different locations and wants to deploy OpenStack in both. What would be a deployment scenario

[Openstack] [nova][cinder] Migrate instances between regions or between clusters?

Hi, So here's a possibly stupid question - or rather, a series of such :) Let's say a company has two (or five, or a hundred) datacenters in geographically different locations and wants to deploy OpenStack in both. What would be a deployment scenario that would allow relatively easy migration (col

[Openstack] [openstack][nova]Can I specify a unique certificate for every instance(spice connection)?

Hi, Opesntack can configure a global tls certificate for all instances with spice connection via /etc/libvert/qemu.conf, but can I configure a certificate for every instance seperately? BR Don ___ Mailing list: http://lists.openstack.org/cgi-bi

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

On Mon, Sep 3, 2018 at 1:27 PM, Eugen Block wrote: Hi, To echo what cfriesen said, if you set your allocation ratio to 1.0, the system will not overcommit memory. Shut down instances consume memory from an inventory management perspective. If you don't want any danger of an instance cau

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

Thanks, that is a very good explanation, I get it now. Thank you very much for your answers! Zitat von Balázs Gibizer : On Mon, Sep 3, 2018 at 1:27 PM, Eugen Block wrote: Hi, To echo what cfriesen said, if you set your allocation ratio to 1.0, the system will not overcommit memory. Shut

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

On 09/03/2018 07:27 AM, Eugen Block wrote: Hi, To echo what cfriesen said, if you set your allocation ratio to 1.0, the system will not overcommit memory. Shut down instances consume memory from an inventory management perspective. If you don't want any danger of an instance causing an OOM, y

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

Hi, To echo what cfriesen said, if you set your allocation ratio to 1.0, the system will not overcommit memory. Shut down instances consume memory from an inventory management perspective. If you don't want any danger of an instance causing an OOM, you must set you ram_allocation_ratio to

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

On 08/30/2018 10:54 AM, Eugen Block wrote: Hi Jay, You need to set your ram_allocation_ratio nova.CONF option to 1.0 if you're running into OOM issues. This will prevent overcommit of memory on your compute nodes. I understand that, the overcommitment works quite well most of the time. It j

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

On 08/30/2018 08:54 AM, Eugen Block wrote: Hi Jay, You need to set your ram_allocation_ratio nova.CONF option to 1.0 if you're running into OOM issues. This will prevent overcommit of memory on your compute nodes. I understand that, the overcommitment works quite well most of the time. It ju

Re: [Openstack] [nova] Nova-scheduler: when are filters applied?

Hi Jay, You need to set your ram_allocation_ratio nova.CONF option to 1.0 if you're running into OOM issues. This will prevent overcommit of memory on your compute nodes. I understand that, the overcommitment works quite well most of the time. It just has been an issue twice when I booted

[Openstack] [nova] Nova-scheduler: when are filters applied?

Sorry. I was to quick with the send button... Hi *, I posted my question in [1] a week ago, but no answer yet. When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown

Re: [Openstack] [nova]

On 08/30/2018 10:19 AM, Eugen Block wrote: When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown and in the meantime more instances on the same hypervisor have been

[Openstack] [nova]

Hi *, I posted my question in [1] a week ago, but no answer yet. When does Nova apply its filters (Ram, CPU, etc.)? Of course at instance creation and (live-)migration of existing instances. But what about existing instances that have been shutdown and in the meantime more instances on the s

Re: [Openstack] [nova]Capacity discrepancy between command line and MySQL query

On 08/27/2018 09:40 AM, Risto Vaaraniemi wrote: Hi, I tried to migrate a guest to another host but it failed with a message saying there's not enough capacity on the target host even though the server should me nearly empty. The guest I'm trying to move needs 4 cores, 4 GB of memory and 50 GB of

[Openstack] [nova]Capacity discrepancy between command line and MySQL query

Hi, I tried to migrate a guest to another host but it failed with a message saying there's not enough capacity on the target host even though the server should me nearly empty. The guest I'm trying to move needs 4 cores, 4 GB of memory and 50 GB of disk. Each compute node should have 20 cores, 128

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

Got it! Thank you, Jay! - Cody On Wed, Aug 8, 2018 at 11:36 AM Jay Pipes wrote: > > So, that is normal operation, actually. The conductor calls the > scheduler to find a place for your requested instances. The scheduler > responded to the conductor that, sorry, there were no hosts that were > abl

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

So, that is normal operation, actually. The conductor calls the scheduler to find a place for your requested instances. The scheduler responded to the conductor that, sorry, there were no hosts that were able to match the request (I don't know what the details of that request were). And so th

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

Hi Jay, Thank you for getting back. I attached the log in my previous reply, but I guess Gmail hided it from you as a quoted message. Here comes again: From nova-conductor.log ### BEGIN ### 2018-08-08 09:28:35.974 1648 ERROR nova.conductor.manager [req-ef0d8ea1-e801-483e-b913-9148a6ac5d90 2499343

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

On 08/08/2018 09:37 AM, Cody wrote: On 08/08/2018 07:19 AM, Bernd Bausch wrote: I would think you don't even reach the scheduling stage. Why bother looking for a suitable compute node if you exceeded your quota anyway? The message is in the conductor log because it's the conductor that does mos

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

> On 08/08/2018 07:19 AM, Bernd Bausch wrote: > > I would think you don't even reach the scheduling stage. Why bother > > looking for a suitable compute node if you exceeded your quota anyway? > > > > The message is in the conductor log because it's the conductor that does > > most of the work. The

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

On 08/08/2018 07:19 AM, Bernd Bausch wrote: I would think you don't even reach the scheduling stage. Why bother looking for a suitable compute node if you exceeded your quota anyway? The message is in the conductor log because it's the conductor that does most of the work. The others are just sl

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

I would think you don't even reach the scheduling stage. Why bother looking for a suitable compute node if you exceeded your quota anyway? The message is in the conductor log because it's the conductor that does most of the work. The others are just slackers (like nova-api) or wait for instruction

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

Hi Jay, Thank you for getting back to my question. I agree that it is not an error; only a preset limit is reached. I just wonder why this incident only got recorded in the nova-conductor.log, but not in other files such as nova-scheduler.log, which would make more sense to me. :-) By the way, I

Re: [Openstack] [nova] Log files on exceeding cpu allocation limit

On 08/07/2018 10:57 AM, Cody wrote: Hi everyone, I intentionally triggered an error by launching more instances than it is allowed by the 'cpu_allocation_ratio' set on a compute node. When it comes to logs, the only place contained a clue to explain the launch failure was in the nova-conducto

[Openstack] [nova] Log files on exceeding cpu allocation limit

Hi everyone, I intentionally triggered an error by launching more instances than it is allowed by the 'cpu_allocation_ratio' set on a compute node. When it comes to logs, the only place contained a clue to explain the launch failure was in the nova-conductor.log on a controller node. Why there is

Re: [Openstack] [nova][api] Novaclient redirect endpoint https into http

+openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6 (command: nova –insecure service list) First of all, it seems that the nova client is hitting /v2.1

Re: [Openstack] [Nova] Nova Instance Launches failing on stable/pike

stack@lists.openstack.org' Subject: [Openstack][Nova] Nova Instance Launches failing on stable/pike Hi Nova Team, With the latest cloned Pike repo (devstack based setup), nova instance launches always fail with the following error: >From Nova Conductor Logs [u'Traceback (most recent

Re: [Openstack] Nova VNC console broken

According to the command output that you posted, the first API that fails is this: GET http://controller:8774/v2.1/servers/zktubntu It's the equivalent of openstack server show zktubntu. I wonder if you run console url show as the owner of that instance, or as admin. As admin, you can't find an

Re: [Openstack] Nova VNC console broken

Could you describe your HA set up a little bit? I assume your controllers are behind a load balancer. Did you alter the novnc URL to point to the virtual ip? -Erik On Apr 20, 2018 3:43 PM, "Torin Woltjer" wrote: After setting up HA for my openstack cluster, the nova console no longer works. Not

[Openstack] Nova VNC console broken

After setting up HA for my openstack cluster, the nova console no longer works. Nothing of note appears in any of the logs at /var/log/nova on the controller or the compute node running the instance. I get a single line that looks relevant output to /var/log/apache2/errors.log on the controller

[Openstack] [nova] KVM internal error. Suberror: 3

dc -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=12.0.5,serial=d8eca30f-2e73-4dfb-9270-244084458637,uuid=d6bec617-7977-4fd6-a6ad-cd9757735fdc,family=Virtual Machine -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-00

Re: [Openstack] [nova] Enabling nested KVM (or injecting any CPU feature flags) with cpu_mode=custom

somewhere along the way — is there a contemporary way to do this? We discussed this in the #openstack-nova IRC channel today and I'm going to summarize here in case there are others interested in the topic. It sounds like the "Add ability to configure extra CPU flags for named CPU

[Openstack] [nova] Enabling nested KVM (or injecting any CPU feature flags) with cpu_mode=custom

Hi everyone! I have a question about enabling nested KVM, or for that matter passing in any required CPU features to an instance, in combination with using a "custom" cpu-mode. My compute nodes (Ocata) are configured to run with cpu_mode=custom, cpu_model=IvyBridge. They are also configured for ne

Re: [Openstack] nova live migration setup

Here is some detail on some work regarding live migration - http://superuser.openstack.org/wp-content/uploads/2017/06/ha-livemigrate-whitepaper.pdf Some information on that report in terms of setting up live migration was gleaned from - https://www.mirantis.com/blog/tutorial-openstack-live-migrati

Re: [Openstack] nova live migration setup

Medberry Sent: 3/21/18 5:08 PM To: torin.wolt...@granddial.com Cc: OpenStack General Subject: Re: [Openstack] nova live migration setup Best practice is to use shared storage and then the "copy" is really only the active memory. A few changes came about in about the newton? timefra

Re: [Openstack] nova live migration setup

Best practice is to use shared storage and then the "copy" is really only the active memory. A few changes came about in about the newton? timeframe that allows for some memory convergence. Take a look at the nova release notes from that time forward and you should see reference to the change(s).

[Openstack] nova live migration setup

I can't find any up to date official documentation on the topic, and only find documentation referring to the commands used. What is the best practice for setting up live migration for nova? I have used live migration over SSH in the past, but the documentation for how to do so is lost to me. Al

Re: [Openstack] Nova + LXD + Ceph?

he LXD project; I will try to track down a nova features > timeline or submit a request myself. > nova-lxd is still a separate team and project: https://github.com/openstack/nova-lxd so its a little different to main Nova development right now

Re: [Openstack] Nova + LXD + Ceph?

o seeing it. Thanks. From: James Page Sent: 3/13/18 5:33 AM To: torin.wolt...@granddial.com Cc: openstack@lists.openstack.org Subject: Re: [Openstack] Nova + LXD + Ceph? Hi Torin On Mon, 12 Mar 2018 at 21:52, Torin Woltjer wrote: Hello, I am looking to deploy an openstack cluster using LXD for

Re: [Openstack] Nova + LXD + Ceph?

Hi Torin On Mon, 12 Mar 2018 at 21:52, Torin Woltjer wrote: > Hello, > > I am looking to deploy an openstack cluster using LXD for compute and Ceph > for storage, and I was running into some doubt as to whether this was > possible; and doubt that nova-lxd was mature enough for production. If > a

[Openstack] Nova + LXD + Ceph?

Hello, I am looking to deploy an openstack cluster using LXD for compute and Ceph for storage, and I was running into some doubt as to whether this was possible; and doubt that nova-lxd was mature enough for production. If anyone is running nova-lxd in production, or knows anything about it, pl

[Openstack] [nova] using nova.scheduler.HostManager() (newbie question)

Hi all, I'm trying to get started with openstack code. I'm using the nova.tests examples as they seems simple. I tried it on a packstack newton (it works) and on some TripleO deployments (Pike) , but it doesn't work :( Below you can find the code and the error: ~~~ from oslo_config import cfg fro

Re: [Openstack] [nova] [nova-lxd] Query regarding LXC instantiation using nova

Hi Amit (re-titled thread with scoped topics) As Matt has already referenced, [0] is a good starting place for using the nova-lxd driver. On Tue, 20 Feb 2018 at 11:13 Amit Kumar wrote: > Hello, > > I have a running OpenStack Ocata setup on which I am able to launch VMs. > But I want to move to

[Openstack] [openstack][openstack-nova][openstack-operators] Query regarding LXC instantiation using nova

Hello, I have a running OpenStack Ocata setup on which I am able to launch VMs. But I want to move to LXC instantiation instead of VMs. So, for this, I installed nova-compute-lxd on my compute node (Ubuntu 16.04). */etc/nova/nova-compute.conf* on my compute nodes was changed to contain the follow

[Openstack] Fwd: Port Binding between OpenStack nova VM and ODL network port

-- Forwarded message -- From: Abdul Malik Date: 12 February 2018 at 14:51 Subject: Port Binding between OpenStack nova VM and ODL network port To: openstack@lists.openstack.org Hello all, I am working on SDN controllers with OpenStack and I want to connect a VM launched by Nova

[Openstack] [nova] Compute node in Pike does not register itself

I can not get my compute nodes to register themelves when using Pike. It works OK in Ocata. Is there some additional config, service or software package required in Pike ? If I monitor the IP traffic on the compute node the following can be seen when nova-compute is started: Ocata: Compute no

Re: [Openstack] [Nova]Update glance image contents

Hi Ondrej, the following spec tries to address the issue that you described. https://review.openstack.org/#/c/508133/ Let me know if you have comments/suggestions. cheers, Belmiro On Fri, Jan 12, 2018 at 2:31 PM, Ondrej Vaško wrote: > Hello guys, > > I am dealing with one issue and that is a q

[Openstack] [Nova]Update glance image contents

Hello guys, I am dealing with one issue and that is a question *What is the right approach for updating openstack glance images?* When new version of cloud image comes out, for example Ubuntu cloud images , I want to update old openstack glance ima

[Openstack] [openstack][nova] VRRP packets lost

Hello, After a manual failover from the master to the slave keepalived by shutting down keepalived service on the master, then restarting it again, the VRRP packets the master sends are "lost" or at least not visible from the slave during couple of secondes / minutes, leading to the IP being on th

Re: [Openstack] [nova]How to convince the RetryFilter that a host is recovered from a failure?

On Wed, Nov 15, 2017 at 9:59 AM, Song Sam wrote: Hi, forks: I have a openstack o version cluster with two compute nodes. The resources are almost used up. So, I add a new compute node to a running cluster and try to cold migrate a vm to the new compute node. At the first time, the migratio

[Openstack] [nova]How to convince the RetryFilter that a host is recovered from a failure?

Hi, forks: I have a openstack o version cluster with two compute nodes. The resources are almost used up. So, I add a new compute node to a running cluster and try to cold migrate a vm to the new compute node. At the first time, the migration failed with 'No valid host found' for my mistake. I for

[Openstack] Fwd: [openstack][nova] Default availability zone

Hello Openstack, I need a help with AZ in Nova. I think that this case wasn't discussed before, I tried hard to google it and I find only one solution (below) which I tried but doesn't work. I have 2 availability zones (2 host aggregates each with 1 hypervisor added). I try to create VM In Horizo

[Openstack] [Nova][Operators]

Hi All, I have installed Openstack Pike with Openstack Ansible. Earlier I was working with Newton release. But with Pike release, I am noticing that Nova schedule is in force even when I am providing availability zone with a specific compute node. For the initial set of VMs, it is honouring avail

[Openstack] Nova SSL API Endpoint Failure in Horizon - Pike

Hello everyone, In my pike lab setup I am having an issue with using an https endpoint for the compute service only through horizon. The python client works fine. Below is what I am seeing. If you think its a bug let me know and I will file a report. Any assistance would be appreciated. Nova

[Openstack] Nova user cannot connect to MYSQL DB

Dear all, I am deploying Openstack using MAAS-JUJU, I am trying to deploy each service one-by-one and build the relation between them, everything is ok except that the nova-controller cannot connect to MYSQL db, the DB and the controller are on the same host. I am getting this error from the

[Openstack] nova connecting to amqp on 127.0.0.1

Hi I tried to setup openstack following the instructions in the getting started guide. OS is Centos7 with all updates applied. openstack is working, i can spawn instances, create networks and volumes but for some reason there is this message popping up in /var/log/nova/nova-compute.log: 2017-

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

ee [1] and [2] >> >> >> >> There is a bug with the pci_devices in a scenario when we can delete >> allocated pci device e.g. if pci.passthrough_whitelist is changed >> commit [3] try to resolve. >> >> >> >> >> >> [1] - http

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

when we can delete > allocated pci device e.g. if pci.passthrough_whitelist is changed commit > [3] try to resolve. > > > > > > [1] - https://github.com/openstack/oslo.db/blob/master/oslo_db/ > sqlalchemy/models.py#L142-L150 > > [2] - https://github.com/op

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

the pci_devices in a scenario when we can delete allocated pci device e.g. if pci.passthrough_whitelist is changed commit [3] try to resolve. [1] - https://github.com/openstack/oslo.db/blob/master/oslo_db/sqlalchemy/models.py#L142-L150 [2] - https://github.com/openstack/nova/blob/master/nova

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

model >> of GPU card. >> >> And wrote these information into pci_alias >> and >> pci_passthrough_whitelist in nova.conf on >> Control

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

ved card still exist in pci_devices table. How can I do to fix this problem? So, when you removed the GPU from the compute node and restarted the nova-compute s

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

;>>>> >>>>> >>>>> Hi again, Eddie :) Answer inline... >>>>> >>>>> On 07/06/2017 08:14 PM, Eddie Yen wrote: >>>>> >>>>> Hi everyone, >>>>> >>>>> I'

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

I'm using OpenStack Mitaka version (deployed from Fuel 9.2) >>>> >>>> In present, I installed two different model of GPU card. >>>> >>>> And wrote these information into pci_alias and >>>> pci_passthrough_white

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

(the node which installed GPU). >>> Then restart nova-api, nova-scheduler,and nova-compute. >>> >>> When I check database, both of GPU info registered in >>> pci_devices table. >>> >>> Now I removed one of t

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

GPU and marked that PCI device as deleted. At least, according to this code in the PCI manager: https://github.com/openstack/nova/blob/master/nova/pci/manager.py#L168-L183 <https://github.com/openstack/nova/blob/master/nova/pci/manager.py#L168-L183> Question for you: what

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

pci_devices table. >> >> How can I do to fix this problem? >> >> >> So, when you removed the GPU from the compute node and restarted the >> nova-compute service, it *should* have noticed you had removed the >> GPU and marked that PCI devi

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

gt;> >> But I check database again, the information of the removed card still >> exist in pci_devices table. >> >> How can I do to fix this problem? >> > > So, when you removed the GPU from the compute node and restarted the > nova-compute service, it *should*

Re: [Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

arked that PCI device as deleted. At least, according to this code in the PCI manager: https://github.com/openstack/nova/blob/master/nova/pci/manager.py#L168-L183 Question for you: what is the value of the status field in the pci_devices table for the GPU that you removed? Best, -jay p.s. I

[Openstack] [nova] Database not delete PCI info after device is removed from host and nova.conf

Hi everyone, I'm using OpenStack Mitaka version (deployed from Fuel 9.2) In present, I installed two different model of GPU card. And wrote these information into pci_alias and pci_passthrough_whitelist in nova.conf on Controller and Compute (the node which installed GPU). Then restart nova-api,

Re: [Openstack] [OpenStack] [nova] How can I release PCI device resources without delete instance?

On 07/06/2017 02:17 AM, Eddie Yen wrote: Hi, now I got another problem. I have two models of GPU devices and I set both in pci_alias and pcli_passthrogh_whitelist on controller and compute node(with this two GPUs). Now I removed one of GPU and delete its data in nova.conf, then restart nova-a

  1   2   3   4   5   6   7   8   9   10   >