[Users] migration of VM, which protocol actually works?
i wanted to learn about the modules so that i could understand how the engine POSTS and sends data to the backend sql database and other scripts to perform various options. for e.g i need to know which code actually collects the storage path for the ISO s during ISCSI storage domain setup. also how the hosts, clusters and data centers are made and stored at the backend. if i want to add a new UI that bypasses some of these complicated tasks (again for personal understanding), will I be able to do that. Also i would like to mention that am working on making a little changes to how the ISCSI protocol works.. My another doubt is: when are the NFS/ISCSI/FC protocols actually used in ovirt. like what part of the VM running state? are their purpose limited to just copying the ISO from the storage center to the path required by the Host. Are the protocols them self responsible for sending and getting data during VM execution on a node. The concept of node and migration has left me a little confused. since each node can run multiple VMs , so during the running/execution of the VM , do the network protocols actully work, if not , then how is that achieved. if yes, again my question arises, which module should i focus on regarding this issue. thanks -- -Aditya Mamidwar
----- Original Message -----
From: "aditya mamidwar" <aditya.mamidwar@gmail.com> To: users@ovirt.org, engine-devel@ovirt.org Sent: Sunday, March 16, 2014 10:59:53 PM Subject: [Engine-devel] migration of VM, which protocol actually works?
i wanted to learn about the modules so that i could understand how the engine POSTS and sends data to the backend sql database and other scripts to perform various options.
oVirt is a gigantic application. The web interface is written in GWT, so the "post" part happens in GWT. The database operations happen in the dal (data access layer) module, primarily using the DAO pattern. http://en.wikipedia.org/wiki/Data_access_object
for e.g i need to know which code actually collects the storage path for the ISO s during ISCSI storage domain setup. also how the hosts, clusters and data centers are made and stored at the backend.
Hosts, Clusters, and Data Centers are all "model" objects. They live in UICommonweb. For example, see ClusterModel.java. And they are ultimately persisted to the database using the DAO pattern I mentioned.
if i want to add a new UI that bypasses some of these complicated tasks (again for personal understanding), will I be able to do that.
This sounds very difficult to achieve. Honestly, if you don't need these "complicated tasks," perhaps oVirt is not the right tool for your use case. You might want to look at virt-manager or Kimchi. http://en.wikipedia.org/wiki/KIMCHI
Also i would like to mention that am working on making a little changes to how the ISCSI protocol works..
My another doubt is: when are the NFS/ISCSI/FC protocols actually used in ovirt. like what part of the VM running state? are their purpose limited to just copying the ISO from the storage center to the path required by the Host.
The VMs *live* on these storage types. They are integral to how oVirt works. See http://www.ovirt.org/Architecture
Are the protocols them self responsible for sending and getting data during VM execution on a node. The concept of node and migration has left me a little confused. since each node can run multiple VMs , so during the running/execution of the VM , do the network protocols actully work, if not , then how is that achieved.
I don't understand your question, sorry.
if yes, again my question arises, which module should i focus on regarding this issue.
thanks -- -Aditya Mamidwar
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (2)
-
aditya mamidwar -
Greg Sheremeta