> - Actually document %traceback like it's a real thing. While it was > mentioned on a list long ago that it was intended mainly for debugging and > not really mentioned anywhere else I think it's potentially quite useful for > recording tracebacks and sending them to a logging/build server. Yep, better documentation in general is on the list and %traceback in particular will be documented. There are other sections supported by kickstart, too, that aren't really documented. > - Better high-level logging of the overall kickstart process somewhere, > maybe to a separate log file (then we could tail/scribe_cat it). > Examples "starting pre, partitioning X,Y,Z, installing package X, packages > finished, installing bootloader" Syslog is too verbose and you'd have to > regex out the interesting bits. (this is exactly what cobbler's anamon does) I think this is entirely an anaconda thing, but sure. Logging improvements are always needed and seldom looked at. I think we do entirely too much logging of pointless stuff, and then the useful stuff is not very discoverable. > - Timing metrics would be handy, we fake this roughly in pre/post scripts. > e.g. "took X to install Y package" or "took Y to install all packages" If we were more formal with our logging and wrote out markers at specific points, you could at least calculate this by looking at the timestamps on those lines in the log. > Also as a data point for them, we use a ton of %pre scripts to setup > hardware RAIDs for various vendors, e.g. HP, LSI/MegaRaid, or Fusion IO > cards. > > Ideally I'd like to make all of that somebody else's problem so we just say > "give me X devices with Y config" without writing lots of copypasta bash, > but I don't have any ideas how to make this better. They probably don't want > to write a lot of vendor-specific tools. It's true we don't want to write a lot of vendor-specific stuff. But there's probably still a lot we could do for you. I think there's going to need to be a followup thread asking specifically what kinds of storage things people are doing. We're going to need examples to be able to spot patterns. > We have ipv6 everywhere internally and probably half of our clusters are > ipv6 only. It's not hard to setup ipv6 only environments with VM's, it > would be nice to see this stuff better tested between releases to make sure > the basic functionality is working, it would save us lots of time running > down regressions. This example did come up elsewhere too - briefly, I know we don't test ipv6-only on the installer team. The QA team might, but I do not know for sure. Any bug reports here would be helpful. Testing has been a major focus lately and has certainly improved, but any test system is only as good as its test cases. I know we do not have an ipv6-only one here. We probably don't have a lot of others that we could use. Suggestions welcome! - Chris _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
