Hi guys, have any updates here?
On Sun, Jun 17, 2012 at 12:59 PM, Igor Laskovy wrote:
> John, Jason, can you please concretely clarify what this bad things? For
> example the worst-case.
>
> Yoshi, Kei, can you please clarify current status of Kemari. How far it is
> from production usage?
>
> On
*John, Jason*, can you please concretely clarify what this bad things? For
example the worst-case.
*Yoshi, Kei*, can you please clarify current status of Kemari. How far it
is from production usage?
On Fri, Jun 15, 2012 at 5:48 PM, Jason Hedden wrote:
> I'm running 2 full nova controllers behind
So, making cloud controller node highly available using Corosync/Pacemaker
does not really avoid potential issue which you have mentioned below
(recover from half completed tasks), correct?
Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine
On Jun 15, 2012 1:36 PM, "John Garbutt" wrote:
> I kn
I know there is some work in the XenAPI driver to make it resilient to these
kinds of failures (to allow frequent updates of the nova code), and I think
there were plans for the work to be reused in the Libvirt driver.
AFAIK, in Essex and lower, bad things can happen if you don't wait for all th
I am using OpenStack for my little lab for a short time too))
Ok, you are right of course, but I meant a some another design when told
about virtualization controller nodes.
It is can be only two dedicated hypetvisor with dedicated share/drbd
between them. This hypervisors will be standalone, and
Hey,
well, I said "I might be wrong" because I have no "clear" vision on how
OpenStack works in
its deepest detail, however, I would not like to depend on a controller
node that
is inside a virtual machine, controlled by compute nodes, that are
controlled by the controller
node. This sounds quite
Why? Can you please clarify.
Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine
On Jun 15, 2012 1:55 AM, "Christian Parpart" wrote:
> I don't think putting the controller node completely into a VM is a good
> advice,
> at least when speaking of nova-scheduler and nova-api (if central).
>
> I m
I don't think putting the controller node completely into a VM is a good
advice,
at least when speaking of nova-scheduler and nova-api (if central).
I may be wrong, and if so, please correct me.
Christian.
On Thu, Jun 14, 2012 at 7:20 PM, Igor Laskovy wrote:
> Hi, have any updates there?
> Can
Hi, have any updates there?
Can anybody clarify what happens if controller nodes just going hard shutdown?
I thinking about solution with two hypervisors and putting controller
node in VM shared storage, which can be relaunched when active
hypervisor will die.
Any ideas, advise?
On Tue, Jun 12,
9 matches
Mail list logo
