Re: [libvirt] Google Summer of Code 2013 ideas wiki open

Not sure if you planned to request separate projects for these, but I don't think it's deserved for separate projects. They can be just one project, as the work need to do for them is similar.

And not restricted to storage stuffs, if renaming API makes sense for storage volume, it makes sense for all other objects too, e.g. domain/network/interface/ nwfilter/secret/pool. What I'm thinking about is, the renaming is easy to implement for inactive objects, but for active ones, it's hard, even not possible, such as for a active domain, the domain name is refered by various places, if you change that, it will produce a big mess.

> 4, Move volume from one pool to another. I will develop 'virsh vol-move > xxx' > option for virsh tool. Not sure it's deserved, the existing command create-vol-as/vol-clone can actually copy the volume from another pool. And after that, you can just remove the original volume. Perhaps having a virsh command to wrapper the the two APIs together is enough.