On Mon 12 Sep 2011 09:48:51 AM IDT, Livnat Peer wrote:
As for connection management, I think that runtime management of connection information is the way forward. I am positively against VDSM reading the storage for additional connection or even understanding more metadata. I don't care if the mgmt pushes this as an object and uses it in it's own code.
As for how you can help, simplest thing would be to complete the missing functions in the current connection management code. public_validateStorageServerConnection public_getStorageConnectionsList
They are part of the current API and making them work will be a good start. The actual binding of connections to a domain is part of the new API and we are not sure how to go about implementing its support just yet. Also making iscsi.py. devicemapper.py multipath.py more feature complete and better separated is a good start for making sure we have the subsystems for advanced connection management features.
Hi Sagi,
One of the things we want to improve in RHEVM 3.1 is the storage connection management. Today it is RHEVM responsibility to connect and disconnect the host from the storage domains explicitly, is that going to change as part of the new API? Is it going to be encapsulated in other verbs? Is there any documentation of that?
Thanks, Livnat
vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
It is going to change. We are still discussing the best way to do it internally and there will be an email for peer review on the list once were done arguing.