On Mon, Feb 25, 2008 at 10:07:48AM +0000, Richard W.M. Jones wrote:
On Sun, Feb 24, 2008 at 10:20:24PM +0000, Daniel P. Berrange wrote:
We can't change the semantics of these calls. virNetworkDefineXML() explicitly does not affect the current live config, saving the config to take effect next time the network is started. This is the same semantics as the virDomainDefineXML() call, and the virStoragePoolDefineXML() calls.
Understood.
To do live updates, we'd need API similar to the domain device hot attach and detach APIs
Well given that it sounds like the original implementation is just as good. Any further comments on that? (http://www.redhat.com/archives/libvir-list/2008-February/thread.html#00281)
I'm fine with your original proposal, or DV's suggestion to use 3 separate arrays instead of the struct. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|