.backup()/.restore() idea for modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I'm kind of a fan of the idea of modules supporting some common utility methods if applicable. The best
examples of this currently are the .inventory() and .info() methods.

I was thinking another good case would be a .backup() and .restore() methods. With the idea being that the results of .backup() could be stored, and restored with a call to the .restore() method. Simple idea, but I think it could useful, especially with the recent improvements in the async behavior making potentially
long running commands a bit more useful.

existing modules that seem like good candidates would include iptables (which more or less already has this cability), sysctl, services (aka, store chkconfig state), and maybe filetracker.


I think in most cases, .backup() and .inventory() are different uses, though some cases it can surely be the same (sysctl for example, is probably basically the same). But with the main idea that .backup()
would include enough info to restore from "scantily clad metal"[1] state.


[1] as opposed to "bare metal", "scantily clad metal" is a basic os that perhaps was just reprovisioned[2] [2] I think I may have just made that up. I like it. Way cooler than "Just enough OS"

Adrian

_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list

[Index of Archives]     [Fedora Users]     [Linux Networking]     [Fedora Legacy List]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux