The controller node can not host vms. But an All-in-one node can, because
it is a combination of controller and compute.
On Thu, Nov 15, 2012 at 12:53 PM, Ahmed Al-Mehdi wrote:
> Hello,
>
> I am following the document "OpenStack Deploy and Install Guide" to bring
> up a OpenStack setup. Per t
I got it.
PJ
On Tue, Aug 28, 2012 at 10:47 AM, Sandy Walsh wrote:
> Not sure if an email like this gets sent automagically by LP anymore, so here
> goes ...
>
> I'd love to get some feedback on it.
>
> Thanks!
> -S
>
> The Blueprint
> https://blueprints.launchpad.net/nova/+spec/monitoring-servi
; From: openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net
> [openstack-bounces+shouhengzhang.xu=mail.utoronto...@lists.launchpad.net] on
> behalf of Heng Xu [shouhengzhang...@mail.utoronto.ca]
> Sent: Thursday, August 02, 2012 4:47 PM
> To: Pengjun Pan
> Cc: opensta
Any thoughts?
> thank you
>
> Heng
> ____________
> From: Pengjun Pan [panpeng...@gmail.com]
> Sent: Thursday, August 02, 2012 4:42 PM
> To: Heng Xu
> Cc: Joseph Suh; openstack@lists.launchpad.net
> Subject: Re: [Openstack] Cannot pass hint to Nova Sche
Hi Heng,
The log should be in /var/log/nova/nova-scheduler.log.
PJ
On Thu, Aug 2, 2012 at 10:44 AM, Heng Xu
wrote:
> Hello Joseph:
> I am not sure where to find the log, so I just used the screen to n-sch,
> and one of the error is
> TRACE nova.rpc.amqp ValueError: No JSON object could be decod
I never tried to stop a VM using api. But run a "nova help", it has
pause, reboot, resume, etc.
To bypass nova api, you can use virsh to stop instances. Do a "sudo
virsh list --all", it will list all the running instances even if nova
cannot see it for some reason. And then you can kill all the "g
6 matches
Mail list logo
