[Ovirt-devel] [PATCH server] remove reliance on ovirt-pxe and clean up one more q/a installer variable problem

[Joey Boggs]

We can certainly make a puppet recipe to resync, but there are 
drawbacks(when to trigger it, how to trigger it) Puppet is in the 
background for ace but the server doesn't use it directly. Is there an 
example on the node that mimics a similar process using puppet?

What if we add in the %post section to run the update if cobbler and 
ovirt-server are installed? There's still some uncertainty in that 
scenario but it won't "hurt" anything really by running

What's the best approach?


Scott Seago wrote:
> Joey Boggs wrote:
>> Well now that I've actually thought about it some more, nothing 
>> really changes when the ovirt-node-image is upgraded. The pxe config 
>> remains the same since there is no version number in the menu, the 
>> only thing that's different is the iso. In that case nothing really 
>> needs to be done. Maybe I'm overlooking something?
> I think the main thing that has to be done now when node-image is 
> updated is to re-sync cobbler. That's the one thing that upgrading the 
> node-image-pxe RPM seemed to accomplish on already-installed systems.
>
> Scott