Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-26 Thread Logan Kuhn
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 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 read resource
| > owners', 'Sanlock exception')

|> I tried reinstalling one of them and the error message continues. At least 
for
| > now I've restored the old config and the error is gone.

| > Regards,
| > Logan


| Logan, do you mind to write a testcase in ovirt.org website for the disaster
| recovery test you are doing? Milan, if Logan write it, can you please review
| it?

| > - On Jul 22, 2016, at 3:06 AM, Milan Zamazal mzama...@redhat.com wrote:

| > | Logan Kuhn < log...@wolfram.com > 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 complete disaster, when a fresh engine is
| > | installed and used, it's still possible to recover the master domain in
| > | theory. You must find `metadata' file in the master domain and edit it
| > | for the new engine. It's completely unsupported and it may or may not
| > | work. We don't have guidelines how to do it, but you may try to create
| > | a new master domain, then detach it and compare the two metadata files.
| > ___
| > Users mailing list
| > Users@ovirt.org
| > http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-25 Thread Sandro Bonazzola
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 report: VDSM ovirt-reqa1 command failed: (-226, 'Unable to read
resource owners', 'Sanlock exception')
>
> I tried reinstalling one of them and the error message continues.  At
least for now I've restored the old config and the error is gone.
>
> Regards,
> Logan
>

Logan, do you mind to write a testcase in ovirt.org website for the
disaster recovery test you are doing? Milan, if Logan write it, can you
please review it?


> - On Jul 22, 2016, at 3:06 AM, Milan Zamazal mzama...@redhat.com
wrote:
>
> | 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 complete disaster, when a fresh engine is
> | installed and used, it's still possible to recover the master domain in
> | theory.  You must find `metadata' file in the master domain and edit it
> | for the new engine.  It's completely unsupported and it may or may not
> | work.  We don't have guidelines how to do it, but you may try to create
> | a new master domain, then detach it and compare the two metadata files.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-22 Thread Logan Kuhn
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 read 
resource owners', 'Sanlock exception')

I tried reinstalling one of them and the error message continues.  At least for 
now I've restored the old config and the error is gone.

Regards,
Logan

- On Jul 22, 2016, at 3:06 AM, Milan Zamazal mzama...@redhat.com wrote:

| 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 complete disaster, when a fresh engine is
| installed and used, it's still possible to recover the master domain in
| theory.  You must find `metadata' file in the master domain and edit it
| for the new engine.  It's completely unsupported and it may or may not
| work.  We don't have guidelines how to do it, but you may try to create
| a new master domain, then detach it and compare the two metadata files.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-22 Thread Milan Zamazal
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 complete disaster, when a fresh engine is
installed and used, it's still possible to recover the master domain in
theory.  You must find `metadata' file in the master domain and edit it
for the new engine.  It's completely unsupported and it may or may not
work.  We don't have guidelines how to do it, but you may try to create
a new master domain, then detach it and compare the two metadata files.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Unable to import pre-configured nfs data domain

2016-07-20 Thread Logan Kuhn
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
| 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 it up and going,
| but I'm having a hard time getting the previous master data domain to import
| into the new engine. I've attached relevant snippets of the engine and vdsm
| log.

| Engine: http://pastebin.com/xBZ7CBs7

| VDSM: http://pastebin.com/eksVyWBn

| Regards,
| Logan

| ___
| Users mailing list
| Users@ovirt.org
| http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Unable to import pre-configured nfs data domain

2016-07-19 Thread Logan Kuhn
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 it up and going, 
but I'm having a hard time getting the previous master data domain to import 
into the new engine. I've attached relevant snippets of the engine and vdsm 
log. 

Engine: http://pastebin.com/xBZ7CBs7 

VDSM: http://pastebin.com/eksVyWBn 


Regards, 
Logan 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users