You need to use https://ask.openstack.org/en/questions/ to post such queries
Thanks
Divakar
On 21 Jun 2015 12:11, Swaroop Jayanthi wrote:
Hi All,
I am understanding HEAT architecture, I have few basic questions in this regard.
1) Who provides the templates to Cloud Admin?
2) Template will be
> Most stuff in OpenStack gets around this by doing synchronous calls across
> oslo.messaging, where there is an end-to-end ack. We don't want that here >
> >though. We'll probably have to make do with having ways to recover after a
> failure (kick off another update with the same data is always
Steve,
The problem with the support of live-migrate would still exist even if we
decide to manage only one cluster from a compute node, unless one is ok with
only live-migrate functionality between clusters. The main debate started with
supporting the live-migrate between the ESX Hosts in the s
gh :)
Best,
-jay
> I don't know why the decision to manage vCenter with Nova was made but
> based on the above I understand the reasoning.
>
>
> Best,
> ---
> Juan Manuel Rey
>
> @jreypo
>
>
> On Mon, Apr 7, 2014 at 7:20 AM, Jay Pipes wrote:
> On
>> Well, it seems to me that the problem is the above blueprint and the code it
>> introduced. This is an anti-feature IMO, and probably the best solution
>> would be to remove the above code and go back to having a single >>
>> nova-compute managing a single vCenter cluster, not multiple ones.
>>> Why reboot an instance? What is wrong with deleting it and create a new one?
You generally use non-persistent disk mode when you are testing new software or
experimenting with settings. If something goes wrong just reboot and you are
back to clean state and start over again.I feel it's
