I'd be happy to, but how/where do I do that?
Regards,
Logan
- On Jul 25, 2016, at 2:56 PM, Sandro Bonazzola
wrote:
| Il 22/Lug/2016 17:10, "Logan Kuhn" < log...@wolfram.com > ha scritto:
| > Thank you!
| > That does do some interesting things, but doesn't appear to work.
|> I've add
Il 22/Lug/2016 17:10, "Logan Kuhn" ha scritto:
>
> Thank you!
>
> That does do some interesting things, but doesn't appear to work.
>
> I've added a new storage domain, merged the differences in the metadata
file back to the old one and powered it up. When I start up the nodes they
endlessly repo
Thank you!
That does do some interesting things, but doesn't appear to work.
I've added a new storage domain, merged the differences in the metadata file
back to the old one and powered it up. When I start up the nodes they
endlessly report: VDSM ovirt-reqa1 command failed: (-226, 'Unable to r
Logan Kuhn writes:
> Am I correct in the assumption that importing a previously master data domain
> into a fresh engine without a current master domain is supported?
It's supported only in case the master domain was previously correctly
detached from the data center.
In case of an unexpected c
Am I correct in the assumption that importing a previously master data domain
into a fresh engine without a current master domain is supported?
Regards,
Logan
- On Jul 19, 2016, at 7:16 AM, Logan Kuhn wrote:
| We are currently evaluating ovirt for our new VM backend and part of that is
We are currently evaluating ovirt for our new VM backend and part of that is
moving the engine to a physical controller node. So I took the opportunity to
test a DR scenario where the engine fails and takes more than a reboot to bring
it back up. For the most part it was straight forward to get
6 matches
Mail list logo