4:35 p.m.
Hi...
I've been working with both RHEV and Ovirt and can see distinct changes
and improvements with regards to how Ovirt is emerging and changing.
One area that still disturbs me is in the area of recovery and cleanup,
specifically around the ovirt-engine (rhevm) node.
I've observed a few things about the project:
- backup of a engine db seems to be a fairly manual process
with many steps. There are many files listed that need to be backed
up manually as listed in the RHEVM admin manual. pg_dump seems to
automate the dumping of the db, but other config files are left up
to the admin.
- restoration appears to be equally complex
- engine-cleanup (rhevm-cleanup) doesn't always cleanup
- there appear to be instances where the only way to get a solid base
is reinstallation. I've removed and reinstalled components so many
times it is now second nature. ;)
I'm curious about:
- Are there technical issues (beyond the code not being written yet) that
prevent backup and restore procedures from working correctly to save
and restore an engine environment? I would expect that a test for
that operation would be to setup an environment, take a snapshot,
and restore the whole thing to another management node.
- Are all the config files properly identified? The RHEVM Admin
manual has an extensive list but is it exhaustive?
- What technically prevents engine-cleanup from really *cleaning*
a system? My expectation would be that I should be able to run
engine-cleanup and completely wipe out the setup. All databases,
certs, config files and the like returned to their original,
pristine state. Perhaps another script - engine-restore-defaults? -
needs to go beyond where engine-cleanup goes today?
As a support professional, these are areas that I think warrant
investment and I wonder what is gating the development here.
Thanks,
Rick
--
+----------------------------------------------------------------------+
| Rick Beldin | Hewlett-Packard Company |
| email: Rick.Beldin(a)hp.com | |
| TCE&Q - Linux ERT | 5555 Windward Parkway West |
| | Alpharetta, GA 30004 |
+----------------------------------------------------------------------+
1:55 p.m.
This is a multi-part message in MIME format.
--------------090506000406080604020709
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 02/14/2013 03:35 PM, Rick Beldin wrote:
Hi...
I've been working with both RHEV and Ovirt and can see distinct changes
and improvements with regards to how Ovirt is emerging and changing.
One area that still disturbs me is in the area of recovery and cleanup,
specifically around the ovirt-engine (rhevm) node.
I've observed a few things about the project:
- backup of a engine db seems to be a fairly manual process
with many steps. There are many files listed that need to be backed
up manually as listed in the RHEVM admin manual. pg_dump seems to
automate the dumping of the db, but other config files are left up
to the admin.
- restoration appears to be equally complex
- engine-cleanup (rhevm-cleanup) doesn't always cleanup
- there appear to be instances where the only way to get a solid base
is reinstallation. I've removed and reinstalled components so many
times it is now second nature. ;)
I'm curious about:
- Are there technical issues (beyond the code not being written yet) that
prevent backup and restore procedures from working correctly to save
and restore an engine environment? I would expect that a test for
that operation would be to setup an environment, take a snapshot,
and restore the whole thing to another management node.
- Are all the config files properly identified? The RHEVM Admin
manual has an extensive list but is it exhaustive?
- What technically prevents engine-cleanup from really *cleaning*
a system? My expectation would be that I should be able to run
engine-cleanup and completely wipe out the setup. All databases,
certs, config files and the like returned to their original,
pristine state. Perhaps another script - engine-restore-defaults? -
needs to go beyond where engine-cleanup goes today?
As a support professional, these are areas that I think warrant
investment and I wonder what is gating the development here.
Thanks,
Rick
Hey Rick!
Firstly, thanks for the time and effort you have put into this, it is
really appreciated.
Secondly, I created wiki page [1] with the set of requirements for such
utility/feature that you discussed here, this would help in developing
it. Please feel free to comment/provide feedback.
[1] http://www.ovirt.org/Backup_And_Restore_Engine
--
Best regards,
Alex Lourie
Software Developer in Integration
Red Hat
--------------090506000406080604020709
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 02/14/2013 03:35 PM, Rick Beldin
wrote:<br>
</div>
<blockquote cite="mid:511CE822.2070603@hp.com" type="cite">
<pre wrap="">Hi...
I've been working with both RHEV and Ovirt and can see distinct changes
and improvements with regards to how Ovirt is emerging and changing.
One area that still disturbs me is in the area of recovery and cleanup,
specifically around the ovirt-engine (rhevm) node.
I've observed a few things about the project:
- backup of a engine db seems to be a fairly manual process
with many steps. There are many files listed that need to be backed
up manually as listed in the RHEVM admin manual. pg_dump seems to
automate the dumping of the db, but other config files are left up
to the admin.
- restoration appears to be equally complex
- engine-cleanup (rhevm-cleanup) doesn't always cleanup
- there appear to be instances where the only way to get a solid base
is reinstallation. I've removed and reinstalled components so many
times it is now second nature. ;)
I'm curious about:
- Are there technical issues (beyond the code not being written yet) that
prevent backup and restore procedures from working correctly to save
and restore an engine environment? I would expect that a test for
that operation would be to setup an environment, take a snapshot,
and restore the whole thing to another management node.
- Are all the config files properly identified? The RHEVM Admin
manual has an extensive list but is it exhaustive?
- What technically prevents engine-cleanup from really *cleaning*
a system? My expectation would be that I should be able to run
engine-cleanup and completely wipe out the setup. All databases,
certs, config files and the like returned to their original,
pristine state. Perhaps another script - engine-restore-defaults? -
needs to go beyond where engine-cleanup goes today?
As a support professional, these are areas that I think warrant
investment and I wonder what is gating the development here.
Thanks,
Rick
</pre>
</blockquote>
<font face="Droid Sans">Hey Rick!<br>
<br>
Firstly, thanks for the time and effort you have put into this, it
is really appreciated.<br>
<br>
Secondly, I created wiki page [1] with the set of requirements for
such utility/feature that you discussed here, this would help in
developing it. Please feel free to comment/provide feedback.<br>
<br>
</font>[1]
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://www.ovirt.org/Backup_And_Restore_Engine">http:/...
<pre class="moz-signature" cols="72">--
Best regards,
Alex Lourie
Software Developer in Integration
Red Hat</pre>
</body>
</html>
--------------090506000406080604020709--
4294
days inactive
4299
days old
2 comments
3 participants
participants (3)
-
Alex Lourie -
Rick Beldin -
Sandro Bonazzola