Dear all,
The issue is that we want to create a virtual link between two VMs on
the same physical machine (regardless of their interfaces and network
already created by neutron that inter-connect them through br-int or
ovs). Let us consider the most simple scenario: same physical machine,
same pro
Thanks Jay. I am checking StackLight.
My intention was to leverage my existing monitoring infra to watch Fuel
nodes as well.
Regards,
Raja.
On 7 March 2017 at 21:23, Simon Pasquier wrote:
> Hello Raja,
> If you're using Fuel, I would recommend you to use the StackLight plugins
> for monitoring.
The way I have debugged this issue is enabling port 22 (+ssh keys) so
you can log into the guest instance and see why it has failed to get to
a running state. Once there it is usually obvious what has gone wrong
(but may require several retries to get working)!
Best wishes
Mark
On 09/03/17
I think you'd better file a bug in https://bugs.launchpad.net/nova/
and post details of logs there, then developers can help figure out the
root cause.
2017-03-10 16:22 GMT+08:00 Excalibur <243523...@qq.com>:
> hi guys,
>
> I followed the docs to install otaca version. But when I finished
> insta
This is the whole log:
2017-03-10 16:05:20.724 25061 INFO os_vif [-] Loaded VIF plugins: ovs,
linux_bridge
2017-03-10 16:05:20.724 25061 WARNING oslo_reports.guru_meditation_report [-]
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward
compatibility. SIGUSR1 will no longe
hi guys,
I followed the docs to install otaca version. But when I finished installing
and configuring a compute node, and came to verify operation. I found there are
only service components on the controller node are enabled, the service
component on the compute node is not appeared in the c
