stions)"
> , Ajay Kalambur
> Subject: Re: [openstack-dev] [nova] Compute Node restart
>
> On Apr 25, 2017 2:45 AM, "Ajay Kalambur (akalambu)"
> wrote:
>
> I see that when a host is gracefully rebooted nova-compute receives a
> lifecycle event to shutdown the ins
t;>,
Ajay Kalambur mailto:akala...@cisco.com>>
Subject: Re: [openstack-dev] [nova] Compute Node restart
On Apr 25, 2017 2:45 AM, "Ajay Kalambur (akalambu)"
mailto:akala...@cisco.com>> wrote:
I see that when a host is gracefully rebooted nova-compute receives a lifecycle
event
On Apr 25, 2017 2:45 AM, "Ajay Kalambur (akalambu)"
wrote:
I see that when a host is gracefully rebooted nova-compute receives a
lifecycle event to shutdown the instance and it updates the database with
the state set to SHUTOFF.
Now when compute node reboot and libvirt brings the VM back up nova
Hi
I see that when a host is gracefully rebooted nova-compute receives a lifecycle
event to shutdown the instance and it updates the database with the state set
to SHUTOFF.
Now when compute node reboot and libvirt brings the VM back up nova checks its
database and issues stop api and hence shuts
Hello,
I am trying to get Nova Compute create_instance hook to be called. However,
although the VM gets started from Horizon properly, the hook does not get
called and there is no reference in it to the logs. When I run the hook script
from the command line, it runs fine.
Please let me know
Hi all,
I'm glad to see much interest in this feature. I will prepare and submit
nova specs by the end of this week.
On Oct 23, 2015 5:47 PM, "Markus Zoeller" wrote:
> Mathieu Gagné wrote on 10/22/2015 08:08:07 PM:
> > > Could you maybe add a short explanation what the use case is? IOW,
> > > w
Mathieu Gagné wrote on 10/22/2015 08:08:07 PM:
> > Could you maybe add a short explanation what the use case is? IOW,
> > when and why do I (in whatever role) prefetch images?
> >
>
> This previous OpenStack Summit presentation at Paris is a great example
> of use case:
> https://www.openstack.
On 2015-10-21 10:23 AM, Markus Zoeller wrote:
> Lingxian Kong wrote on 10/21/2015 06:44:27 AM:
>
>> From: Lingxian Kong
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Date: 10/21/2015 06:44 AM
>> Subject: Re: [openstac
Lingxian Kong wrote on 10/21/2015 06:44:27 AM:
> From: Lingxian Kong
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 10/21/2015 06:44 AM
> Subject: Re: [openstack-dev] [nova-compute][nova][libvirt] Extending
> Nova-Compute for image
Hi, Alberto,
I'm really interested in your proposal, have you already submitted
your spec? or is there any topic for you to have a discussion with
Nova team in design summit?
I wonder what if the nova compute host use shared storage backend,
like NFS or Ceph?
I have another suggestion, we can co
On 10 October 2015 at 09:35, Alberto Geniola
wrote:
> Hi Michael,
>
> and thank you for your answer.
>
> Indeed, what I want to do is to add methods to the ImageCache.py module
> (listing, adding, deleting). So far, this module only takes care of image
> deletion: this represents the "cache" of i
Hi Michael,
and thank you for your answer.
Indeed, what I want to do is to add methods to the ImageCache.py module
(listing, adding, deleting). So far, this module only takes care of image
deletion: this represents the "cache" of images. Now, I want to populate
the cache with some images on the h
I think I'd rephrase your definition of pre-fetched to be honest --
something more like "images on this hypervisor node without a currently
running instance". So, your operations would become:
- trigger an image prefetching
- list unused base images (and perhaps when they were last used)
- dele
Hi all,
I'm considering to extend the Nova-Compute API in order to provide
image-prefetching capabilities to OS.
In order to allow image prefetching, I ended up with the need to add three
different APIs on the nova-compute nodes:
1. Trigger an image prefetching
2. List prefetched images
Hi all,
I have permission-related errors when creating instances.
In Kilo,
since my local disk is small, newly attaching a new disk, /data1 as
following.
root@cn2:/var/lib/nova# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 23G 1.7G 20G 8% /
...
/dev/mapper/vg_data-lv_data1 356G 7
On 8/17/2015 10:19 AM, Dan Smith wrote:
Is this documented somewhere?
I did a bit of digging and couldn't find anywhere that explicitly
required that for the J->K upgrade. Certainly it was documented for the
I->J upgrade.
It's our model, so I don't think we need to document it for each cycl
Dan Smith wrote on 08/17/2015 05:08:25 PM:
> From: Dan Smith
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 08/17/2015 05:15 PM
> Subject: Re: [openstack-dev] [nova] compute <-> conductor and version
> compatibility
>
&g
> Is this documented somewhere?
>
> I did a bit of digging and couldn't find anywhere that explicitly
> required that for the J->K upgrade. Certainly it was documented for the
> I->J upgrade.
It's our model, so I don't think we need to document it for each cycle
since we don't expect it to chang
On 08/17/2015 08:59 AM, Jay Pipes wrote:
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of
> No, that's not valid behaviour. You need to upgrade the controller
> infrastructure (conductor, API nodes, etc) before any compute nodes.
Yep.
--Dan
signature.asc
Description: OpenPGP digital signature
__
OpenStack Devel
bm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
From: Jay Pipes
To: openstack-dev@lists.openstack.org
Date: 08/17/2015 05:01 PM
Subject: Re: [openstack-dev] [nova] compute <-> conductor and version
On 08/17/2015 10:41 AM, Markus Zoeller wrote:
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a n
I have the impression that more and more people try to run OpenStack
in a "mixed-releases-mode" and face some troubles to understand how
the capabilities and limitations look like. For example, the reporter
of [1] runs a nova-conductor (Juno) with a nova-compute (Kilo). I tried
in comment #3 of [1]
+1, good idea!
2014-11-04 15:15 GMT+08:00 Eli Qiao :
> hello all:
> in current _init_instance function in compute manager,
> there's flood 'and' 'or' logic, to check the vm_state and task_state when
> initialize a instance during service list,
> this lead hard to read and hard to maintain, so I
,
From: Eli Qiao
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 11/04/2014 03:13 PM
Subject: [openstack-dev] [nova][compute] propose to use a table to
deal with the vm_state when _init_instance
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
From: Eli Qiao
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 11/04/2014 03:13 PM
Subject:[openstack-dev] [nov
hello all:
in current _init_instance function in compute manager,
there's flood 'and' 'or' logic, to check the vm_state and task_state
when initialize a instance during service list,
this lead hard to read and hard to maintain, so I propose a new way to
handle this.
we can create a vm_state_table,
Hi Rich
I'm trying to run VM from controller node onto compute node and it is
stucking at spawning state.I'm able to get the libvirt.xml in
/opt/stack/data/nova/instances/729482302900. on the compute node and
below is the libvirt.xml file..
domain type="kvm">
7210aa10-6c98-
Hi RIch
Thanks for the reply.The libguestfs is working fine here and there are no
issues regarding that on the ubuntu compute node.From the nova-compute logs
on the compute node,it appears that the tap interface is not coming up on
the compute node.
Also in the file driver.py at the path /opt/sta
On Fri, Jun 13, 2014 at 03:06:25PM +0530, abhishek jain wrote:
> Hi Rich
>
> Can you help me regarding the possible cause for VM stucking at spawning
> state on ubuntu powerpc compute node in openstack using devstack.
Did you solve this one? It's impossible to debug unless you collect
the full
Hi
I have installed openstack using devstack.I'm able to boot VM from
openstack cloud on the controller node.When I'm trying to boot VM on the
compute node,it is stucking at spawning state.The logs of the nova-compute
on the controller node is almost the same as that of of the nova-compute on
the
Hi Rich
Can you help me regarding the possible cause for VM stucking at spawning
state on ubuntu powerpc compute node in openstack using devstack.
Thanks
On Tue, Jun 10, 2014 at 10:29 PM, abhishek jain
wrote:
> Hi Rich
>
> I'm able to solve the problem regarding PAPR in libguestfs on my pow
Hi Rich
I'm able to solve the problem regarding PAPR in libguestfs on my powerpc
ubuntu.By default the libguestfs was configuring pseries machine and
afterwards I changed it to my original machine i.e ppce500 .The changes are
performed in ./src/guestfs-internal.h file.
However still my VM is stuc
On Tue, May 27, 2014 at 03:25:10PM +0530, abhishek jain wrote:
> Hi Daniel
>
> Thanks for the help.
> The end result of my setup is that the VM is stucking at Spawning state on
> my compute node whereas it is working fine on the controller node.
> Therefore I'm comparing nova-compute logs of both
On 6/3/2014 8:15 AM, abhishek jain wrote:
Hi Russell
Thanks
I'm able to solve it now by switching onto havana release on both the
controller node and compute node.
On Tue, Jun 3, 2014 at 10:56 AM, abhishek jain mailto:ashujain9...@gmail.com>> wrote:
Hi Russell
Below are the de
Hi Russell
Thanks
I'm able to solve it now by switching onto havana release on both the
controller node and compute node.
On Tue, Jun 3, 2014 at 10:56 AM, abhishek jain
wrote:
> Hi Russell
>
> Below are the details...
>
> controller node...
>
> nova --version
> 2.17.0.122
>
> nova-compute
Hi Russell
Below are the details...
controller node...
nova --version
2.17.0.122
nova-compute --version
2014.2
compute node.
nova --version
2.17.0.122
nova-compute --version
2013.2.4
Can you help me what i need to change in order to achieve the desired
functioonality.
Thaks
On Tue
On 06/02/2014 08:20 AM, abhishek jain wrote:
> |Hi
> |
>
> |
> I'm getting following error in nova-compute logs when trying to boot VM from
> controller node onto compute node ...
>
> Specified RPC version, 3.23, not supported
>
> Please help regarding this.
It sounds like you're using an ol
Hi
I'm getting following error in nova-compute logs when trying to boot
VM from controller node onto compute node ...
Specified RPC version, 3.23, not supported
Please help regarding this.
Thanks
Abhishek Jain
___
OpenStack-dev mailing list
OpenSta
Hi Daniel
Thanks for the help.
The end result of my setup is that the VM is stucking at Spawning state on
my compute node whereas it is working fine on the controller node.
Therefore I'm comparing nova-compute logs of both compute node as well as
controller node and trying to proceed step by step.
On Tue, May 27, 2014 at 12:04:23PM +0530, abhishek jain wrote:
> Hi
> Below is the code to which I'm going to reffer to..
>
> vim /opt/stack/nova/nova/virt/disk/vfs/api.py
>
> #
>
> try:
> LOG.debug(_("Trying to imp
Hi
Below is the code to which I'm going to reffer to..
vim /opt/stack/nova/nova/virt/disk/vfs/api.py
#
try:
LOG.debug(_("Trying to import guestfs"))
importutils.import_module("guestfs")
hasGu
Hi all
I'm trying to run VM on a compute node having ubuntu 13.10 with powerpc
arch.When I launch a VM from the controller node,it is stucking at
spawning state and below are the logs of nova-compute ...
/common/processutils.py:147^M
#Result is passed#^M
2014
Hi
I'm trying to boot VM from my controller node(openstack dashboard) onto
compute node but it is stucking at spawning state.
I'm able to see the VM interface onto the compute but the status is
spawning even after 10-15 minutes.
Below are the nova schedular logs..
ova/openstack/common/loopingcal
Hi
I'm getting foollowing error while booting VM on compute node in
nova-compute service using devstack due to which the VM is stuck at
spawning state..
ERROR nova.openstack.common.rpc.amqp
[req-da485913-0cb2-47c1-ac61-6657361286c3 nova service] Exception during
message handling
[16:18:23] Abhis
Hi Thierry
Thanks for help
On Wed, May 7, 2014 at 1:31 PM, Thierry Carrez wrote:
> sonia verma wrote:
> > Hi all
> >
> > I'm getting following error when booting VM onto compute node from
> > openstack dashboard...
> > [...]
>
> Hi!
>
> This list is for future development topics only, and your
Thanks Thierry for the help
On Wed, May 7, 2014 at 1:31 PM, Thierry Carrez wrote:
> sonia verma wrote:
> > Hi all
> >
> > I'm getting following error when booting VM onto compute node from
> > openstack dashboard...
> > [...]
>
> Hi!
>
> This list is for future development topics only, and your
sonia verma wrote:
> Hi all
>
> I'm getting following error when booting VM onto compute node from
> openstack dashboard...
> [...]
Hi!
This list is for future development topics only, and your question is
about debugging an issue you have using OpenStack. You shall get better
answers by asking
Hi all
I'm getting following error when booting VM onto compute node from
openstack dashboard...
014-05-06 12:47:22.393 DEBUG nova.openstack.common.processutils
[req-cc3cf4c6-160d-4dd4-b44d-d8f5c25fb55c admin admin] Result was 12
execute /opt/stack/nova/nova/openstack/common/processutils.py:172
2
Hi
I changed the ebtables version i.e ebtables_2.0.9.2-2ubuntu3_powerpc.deb
from version 2.0.10-4 and the error just reduced to one as below...
2014-05-03 11:26:42.052 12065 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
Hi all
I want to boot VM from controller node onto the compute node using
devstack.All my services such as nova,q-agt,nova-compute,neutron,etc are
running properly both on compute node as well on the controller node.I'm
also able to boot VMs on controller node from the openstack dashvoard
.However
Hi all
I'm trying too boot Vm from my controller node onto compute node and
getting following error in nova-compute service ...
2014-04-30 05:10:22.452 17049 TRACE nova.openstack.common.rpc.amqp if
ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
2014-04-30 05:10:
This is a development list, and your question sounds usage-related. I
suggest asking again on the users list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Thanks.
-Ben
On 04/29/2014 12:53 AM, abhishek jain wrote:
Hi all
I'm getting follwoing error when trying to run nova-c
Hi all
I'm getting follwoing error when trying to run nova-compute service..
if ret is None: raise libvirtError ('virNodeListDevices() failed',
conn=self)
2014-04-29 00:51:47.153 28127 TRACE nova.openstack.common.threadgroup
libvirtError: this function is not supported by the connection driver:
iled.
>>
>> Maybe you can try it manually and confirm whether it’s the reason.
>>
>>
>>
>> Best regards to you.
>>
>> Ricky
>>
>>
>>
>> *From:* abhishek jain [mailto:ashujain9...@gmail.com]
>> *Sent:* Saturday, April 26, 2014 3:
y it manually and confirm whether it’s the reason.
>
>
>
> Best regards to you.
>
> Ricky
>
>
>
> *From:* abhishek jain [mailto:ashujain9...@gmail.com]
> *Sent:* Saturday, April 26, 2014 3:25 PM
> *To:* OpenStack Development Mailing List (not for usage quest
: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] nova compute error
Hi all..
I'm getting following nova-compute error and thus not able to boot the VMs on
my compute node...
nova-ompute service stopped and started giving following error...
[02:06:44] Abhishek
Hi all..
I'm getting following nova-compute error and thus not able to boot the VMs
on my compute node...
nova-ompute service stopped and started giving following error...
[02:06:44] Abhishek Jain: 2014-04-25 15:32:00.112 6501 TRACE
nova.openstack.common.threadgroup cmd=' '.join(cmd))
2014-0
Hi,
Can anyone share the current deployment use case for compute Node Interfaces
configuration in Nova configuration file where hundreads of compute nodes [with
two or more physical interfaces] in DC network has to be configured with
IPAddress for Management Networks and Data Networks.
Is ther
59 matches
Mail list logo
