----- Original Message ----- From: "Shiva Kumar Pathori" <[email protected]> To: <[email protected]> Sent: Tuesday, February 19, 2019 1:40 PM
> I think there is a need to extend the ietf-system.yang or have new model to > get the current system startup information(like current system software > name, configuration file name, paf file name and patch file name etc..) > from the device and also set the next startup information for upgrade. This > can help the device administrator during system upgrade scenario to operate > with the YANG model. So first step will be copying these files(image, > config file, paf file and patch file) to the device and then set the next > startup information. After this YANG RPC "/ietf-system/system-restart" > can be used to reboot the system to upgrade to the new version. > > I request the WG to provide the opinion on this. Shiva The IETF is good at protocols, what must go on between boxes of different origins else they do not work. The internals of those boxes have no such need to be standardised and while the IETF does delve into those areas, e.g. Host MIB module or, arguably, much of the routing YANG module, it is less successful because, well, there is no need for them to be standardised for the Internet to work. So, a YANG module for startup information would need find common ground between, say, iPhone, Juniper router, Windows 10, Linux distro and so on when those products work quite happily with radically different views of what is needed. I recall one discussion which failed to get agreement on what the order of precedence of the fields version, release, level; different manufacturers have different interpretations thereof while any one manufacturer will likely be consistent in their usage across a wide range of hardware and software products. Thus it seems more likely an area for proprietary extensions than for the IETF. Tom Petch > Regards, > Shiva > ------------------------------------------------------------------------ -------- > _______________________________________________ > netmod mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/netmod > _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
