point of clarity... it should figure out the vm is in a bad state
eventually and list it as not running.
On Mon, Aug 6, 2012 at 11:25 PM, Matt Joyce wrote:
> You are using virsh directly. Don't do that. Let openstack suspend
> nodes. Otherwise yes openstack will not know that you have decided
You are using virsh directly. Don't do that. Let openstack suspend
nodes. Otherwise yes openstack will not know that you have decided to play
with virsh.
On Mon, Aug 6, 2012 at 11:05 PM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:
> Hi-'
>
> I have been testing the openstack for past
Hi-'
I have been testing the openstack for past few days... and I have a doubt
here...
>From the Horizon in the CONTROLLER, VMs are created in the NODE machine.
Using the virsh console at the NODE machine, I have suspended the VM. But
the same VM-STATE is not populated in the HORIZON.
Does Nov
Guys-
Its my config problem... Its troubleshooted... Now VMs are up and running...
On Tue, Aug 7, 2012 at 10:19 AM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:
> Hi-
>
> I'm seeing these errors in the COMPUTE-NODE nova-compute.log while
> bringing up the virtual machines.
>
> 2012-08-
Hi-
I'm seeing these errors in the COMPUTE-NODE nova-compute.log while bringing
up the virtual machines.
2012-08-07 04:45:46 DEBUG nova.rpc.amqp
[req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8
a17de6f647b14739acb33f09d246f72e] Pool creating new connection from
(pid=2770
Hi Dan
Thank you for pointing this.
Yusuke updated design spec.
https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
2012/8/6 Dan Wendlandt :
> Hi Nachi,
>
> I've reviewed the code and added comments. I'd like to see at least a basic
> spec describing the proposed approach (nee
Hi Nachi,
I've reviewed the code and added comments. I'd like to see at least a
basic spec describing the proposed approach (need only be a couple
paragraphs, perhaps with a diagram) linked to the blueprint so we can have
a design discussion around it. Thanks,
Dan
On Fri, Aug 3, 2012 at 1:03
On Sat, Aug 4, 2012 at 3:46 PM, Bill Shetti wrote:
> Hi, catching up, and sorry for the request for history... but here it is.
You can see a short explanation of this on the FAQ here:
http://wiki.openstack.org/QuantumDevelopment . Longer explanation below.
>
> What compelled the original dec
Hi,
The interval can be managed via the periodic_interval flag in nova.conf,
which is by default 60 sec
Cheers!
On Mon, Aug 6, 2012 at 9:40 AM, Trinath Somanchi wrote:
> thanks a lot for the guidance...
>
>
>
> On Mon, Aug 6, 2012 at 12:57 PM, Michael Still <
> michael.st...@canonical.com> wr
On 06/08/12 16:47, Trinath Somanchi wrote:
> Hi-
>
> Can any one guide me on understanding the process that updates the
> compute_nodes table in nova database.
nova-compute on each compute node sends a regular message to the
nova-scheduler on the scheduler node with an update of its status. These
Hi folks
I report this bug recently.
device_id should not be updated twice
https://bugs.launchpad.net/quantum/+bug/1031473
Now, a user can update device_id which may cause problem.
This is related to port id spec for nova boot.
https://bugs.launchpad.net/nova/+bug/1031096
My question is how w
Hi folks
> Gary
Thank you for your comment. I wanna discuss your point on the mailing list.
Yusuke pushed Multi-host implementation for review.
https://review.openstack.org/#/c/10766/2
This patch changes only quantum-dhcp-agent side.
Gary's point is we should have host attribute on the port for
thanks a lot for the guidance...
On Mon, Aug 6, 2012 at 12:57 PM, Michael Still
wrote:
> On 06/08/12 16:47, Trinath Somanchi wrote:
> > Hi-
> >
> > Can any one guide me on understanding the process that updates the
> > compute_nodes table in nova database.
>
> nova-compute on each compute node s
13 matches
Mail list logo
