Re: [libvirt] [RFC][PATCH 3/7] interface: implement the public APIs

> I think we also need to add comments to > > virInterfaceDefineXML > virInterfaceUndefine > virInterfaceCreate > virInterfaceDestroy > > about the difference in their behaviour if a transaction is open, vs > normal non-transactional usage. They will behave the same at the moment they are called, but it will be possible to later undo what was done, because "opening the transaction" is really just saving off the original config state. More importantly (and probably this is the part you were talking about) if virInterfaceChangeCommit() isn't called before the next time the system is rebooted, all the changes will be automatically reverted during the boot process. (I want to make sure that nobody thinks opening a transaction means that all the changes are saved into a staging area and then later committed to the live config all at once when the transaction is committed - doing it this way would eliminate the ability to test the new config prior to committing).