Verify the storage data integrity after some storage operations with test cases

Hi,

  To verify the storage data integrity after some storage operations 
like snapshot, merging by VDSM.  Here are the test cases I am pondering.
I would like to know your feedback about these thoughts.

1) An customized ISO image with the agent  required prepared for 
bringing up a VM in VDSM
2) The test case will inform VDSM to create a VM from the customized ISO 
image
3) The test case will install an IO application to the VM
3) The test case communicate with the VDSM to inform the IO application 
in the VM to write some data intentionally.
4) The test case sends the commands to VDSM do some storage operation 
like disk snapshot, volume merging, &etc.
      Say snapshot operation here for an example.
5) VDSM then tell the test case the result of the operation like the 
name of the snapshot.
6) Test case can read the  snapshot made to verify the snapshot with the 
data written in 3).
      Note: currently, there is no tool to read the snapshot image 
directly.  We can restart the VM with the snapshot as
      the active disk and tell the IO application in the VM to read the 
data writen before for test case.  And test case can compare
       the data read with the data it informs the application in 3).
7) If the two data matches, the storage operation succeed or it fails.

In order to write such a test case, these VDSM features will be required.

1) VDSM can create a VM from a specific ISO image  (Almost works)
2) Test case can install an IO application to the VM by VDSM (by 
ovirt-agent?)
3) Test case must have some protocols with the IO application in VM for 
passing the command to the VM and returning the result from the VM
      to the test case(by ovirt-agent?).
4) The IO application can be seen as an test agent.  We may extend the 
existing agent like ovirt-agent as the IO application.


-- 
Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
IBM China Systems and Technology Laboratory

Actually setting up isos and installing an OS is an overkill IMHO.
Using libguestfs seems simpler as it has python bindings.

What you could do is:
1. use libguest fs to format a file system on an image
2. Put files on said file system with libguestfs
3. Snapshot
4. run fsck with libguestfs
5. rinse
6. repeast

If you don't trust fsck to detect all issues you can use libguestfs to get an md5sum
of the raw drive and make sure that after a snapshot it stays the same.


----- Original Message -----
>  From: "Shu Ming" <shuming(a)linux.vnet.ibm.com&gt;
>  To: "VDSM Project Development" <vdsm-devel(a)lists.fedorahosted.org&gt;
>  Sent: Monday, July 16, 2012 10:28:25 PM
>  Subject: [vdsm] Verify the storage data integrity after some storage operations with test
> cases
>  
>  Hi,
>  
>    To verify the storage data integrity after some storage operations
>  like snapshot, merging by VDSM.  Here are the test cases I am
>  pondering.
>  I would like to know your feedback about these thoughts.
>  
>  1) An customized ISO image with the agent  required prepared for
>  bringing up a VM in VDSM
>  2) The test case will inform VDSM to create a VM from the customized
>  ISO
>  image
>  3) The test case will install an IO application to the VM
>  3) The test case communicate with the VDSM to inform the IO
>  application
>  in the VM to write some data intentionally.
>  4) The test case sends the commands to VDSM do some storage operation
>  like disk snapshot, volume merging, &etc.
>        Say snapshot operation here for an example.
>  5) VDSM then tell the test case the result of the operation like the
>  name of the snapshot.
>  6) Test case can read the  snapshot made to verify the snapshot with
>  the
>  data written in 3).
>        Note: currently, there is no tool to read the snapshot image
>  directly.  We can restart the VM with the snapshot as
>        the active disk and tell the IO application in the VM to read
>        the
>  data writen before for test case.  And test case can compare
>         the data read with the data it informs the application in 3).
>  7) If the two data matches, the storage operation succeed or it
>  fails.
>  
>  In order to write such a test case, these VDSM features will be
>  required.
>  
>  1) VDSM can create a VM from a specific ISO image  (Almost works)
>  2) Test case can install an IO application to the VM by VDSM (by
>  ovirt-agent?)
>  3) Test case must have some protocols with the IO application in VM
>  for
>  passing the command to the VM and returning the result from the VM
>        to the test case(by ovirt-agent?).
>  4) The IO application can be seen as an test agent.  We may extend
>  the
>  existing agent like ovirt-agent as the IO application.
>  
>  
>  --
>  Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
>  IBM China Systems and Technology Laboratory
>  
>  
>  _______________________________________________
>  vdsm-devel mailing list
>  vdsm-devel(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/vdsm-devel
>

On 2012-7-17 23:21, Saggi Mizrahi wrote:
>  Actually setting up isos and installing an OS is an overkill IMHO.
>  Using libguestfs seems simpler as it has python bindings.
>
>  What you could do is:
>  1. use libguest fs to format a file system on an image 
Do you mean the test case
use libguest fs to format a file without 
interaction with VM?

>  2. Put files on said file system with libguestfs 
Do you mean
the test case put files to the files system with libguestfs 
directly without interaction with VM?
Or even VM is not running?

>  3. Snapshot 
If we want to test online snapshot, we should have
a running VM now.

>  4. run fsck with libguestfs
>  5. rinse
>  6. repeast
>
>  If you don't trust fsck to detect all issues you can use libguestfs to get an md5sum
> of the raw drive and make sure that after a snapshot it stays the same.
>
>
>  ----- Original Message -----
> > From: "Shu Ming" <shuming(a)linux.vnet.ibm.com&gt;
> > To: "VDSM Project Development" <vdsm-devel(a)lists.fedorahosted.org&gt;
> > Sent: Monday, July 16, 2012 10:28:25 PM
> > Subject: [vdsm] Verify the storage data integrity after some storage operations with
> test cases
> >
> > Hi,
> >
> >    To verify the storage data integrity after some storage operations
> > like snapshot, merging by VDSM.  Here are the test cases I am
> > pondering.
> > I would like to know your feedback about these thoughts.
> >
> > 1) An customized ISO image with the agent  required prepared for
> > bringing up a VM in VDSM
> > 2) The test case will inform VDSM to create a VM from the customized
> > ISO
> > image
> > 3) The test case will install an IO application to the VM
> > 3) The test case communicate with the VDSM to inform the IO
> > application
> > in the VM to write some data intentionally.
> > 4) The test case sends the commands to VDSM do some storage operation
> > like disk snapshot, volume merging, &etc.
> >        Say snapshot operation here for an example.
> > 5) VDSM then tell the test case the result of the operation like the
> > name of the snapshot.
> > 6) Test case can read the  snapshot made to verify the snapshot with
> > the
> > data written in 3).
> >        Note: currently, there is no tool to read the snapshot image
> > directly.  We can restart the VM with the snapshot as
> >        the active disk and tell the IO application in the VM to read
> >        the
> > data writen before for test case.  And test case can compare
> >         the data read with the data it informs the application in 3).
> > 7) If the two data matches, the storage operation succeed or it
> > fails.
> >
> > In order to write such a test case, these VDSM features will be
> > required.
> >
> > 1) VDSM can create a VM from a specific ISO image  (Almost works)
> > 2) Test case can install an IO application to the VM by VDSM (by
> > ovirt-agent?)
> > 3) Test case must have some protocols with the IO application in VM
> > for
> > passing the command to the VM and returning the result from the VM
> >        to the test case(by ovirt-agent?).
> > 4) The IO application can be seen as an test agent.  We may extend
> > the
> > existing agent like ovirt-agent as the IO application.
> >
> >
> > --
> > Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
> > IBM China Systems and Technology Laboratory
> >
> >
> > _______________________________________________
> > vdsm-devel mailing list
> > vdsm-devel(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/vdsm-devel
> > 

-- 
Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
IBM China Systems and Technology Laboratory

Well libguestfs really uses a VM behind the scenes, so it's the same thing only less
work

For online snapshotting, I agree this is a problem, but online snapshotting is only 1
test.
I think most tests that can should use libguestfs, it means that they theoretically could
be done without a full blown VDSM running.

----- Original Message -----
>  From: "Shu Ming" <shuming(a)linux.vnet.ibm.com&gt;
>  To: "Saggi Mizrahi" <smizrahi(a)redhat.com&gt;
>  Cc: "VDSM Project Development" <vdsm-devel(a)lists.fedorahosted.org&gt;
>  Sent: Tuesday, July 17, 2012 11:48:39 AM
>  Subject: Re: [vdsm] Verify the storage data integrity after some storage operations with
> test cases
>  
>  On 2012-7-17 23:21, Saggi Mizrahi wrote:
>  > Actually setting up isos and installing an OS is an overkill IMHO.
>  > Using libguestfs seems simpler as it has python bindings.
>  >
>  > What you could do is:
>  > 1. use libguest fs to format a file system on an image
>  Do you mean the test case use libguest fs to format a file without
>  interaction with VM?
>  
>  > 2. Put files on said file system with libguestfs
>  Do you mean the test case put files to the files system with
>  libguestfs
>  directly without interaction with VM?
>  Or even VM is not running?
>  
>  > 3. Snapshot
>  If we want to test online snapshot, we should have a running VM now.
>  
>  > 4. run fsck with libguestfs
>  > 5. rinse
>  > 6. repeast
>  >
>  > If you don't trust fsck to detect all issues you can use libguestfs
>  > to get an md5sum of the raw drive and make sure that after a
>  > snapshot it stays the same.
>  >
>  >
>  > ----- Original Message -----
>  >> From: "Shu Ming" <shuming(a)linux.vnet.ibm.com&gt;
>  >> To: "VDSM Project Development"
> <vdsm-devel(a)lists.fedorahosted.org&gt;
>  >> Sent: Monday, July 16, 2012 10:28:25 PM
>  >> Subject: [vdsm] Verify the storage data integrity after some
>  >> storage operations with test cases
>  >>
>  >> Hi,
>  >>
>  >>    To verify the storage data integrity after some storage
>  >>    operations
>  >> like snapshot, merging by VDSM.  Here are the test cases I am
>  >> pondering.
>  >> I would like to know your feedback about these thoughts.
>  >>
>  >> 1) An customized ISO image with the agent  required prepared for
>  >> bringing up a VM in VDSM
>  >> 2) The test case will inform VDSM to create a VM from the
>  >> customized
>  >> ISO
>  >> image
>  >> 3) The test case will install an IO application to the VM
>  >> 3) The test case communicate with the VDSM to inform the IO
>  >> application
>  >> in the VM to write some data intentionally.
>  >> 4) The test case sends the commands to VDSM do some storage
>  >> operation
>  >> like disk snapshot, volume merging, &etc.
>  >>        Say snapshot operation here for an example.
>  >> 5) VDSM then tell the test case the result of the operation like
>  >> the
>  >> name of the snapshot.
>  >> 6) Test case can read the  snapshot made to verify the snapshot
>  >> with
>  >> the
>  >> data written in 3).
>  >>        Note: currently, there is no tool to read the snapshot
>  >>        image
>  >> directly.  We can restart the VM with the snapshot as
>  >>        the active disk and tell the IO application in the VM to
>  >>        read
>  >>        the
>  >> data writen before for test case.  And test case can compare
>  >>         the data read with the data it informs the application in
>  >>         3).
>  >> 7) If the two data matches, the storage operation succeed or it
>  >> fails.
>  >>
>  >> In order to write such a test case, these VDSM features will be
>  >> required.
>  >>
>  >> 1) VDSM can create a VM from a specific ISO image  (Almost works)
>  >> 2) Test case can install an IO application to the VM by VDSM (by
>  >> ovirt-agent?)
>  >> 3) Test case must have some protocols with the IO application in
>  >> VM
>  >> for
>  >> passing the command to the VM and returning the result from the VM
>  >>        to the test case(by ovirt-agent?).
>  >> 4) The IO application can be seen as an test agent.  We may extend
>  >> the
>  >> existing agent like ovirt-agent as the IO application.
>  >>
>  >>
>  >> --
>  >> Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
>  >> IBM China Systems and Technology Laboratory
>  >>
>  >>
>  >> _______________________________________________
>  >> vdsm-devel mailing list
>  >> vdsm-devel(a)lists.fedorahosted.org
>  >> https://fedorahosted.org/mailman/listinfo/vdsm-devel
>  >>
>  
>  
>  --
>  Shu Ming <shuming(a)linux.vnet.ibm.com&gt;
>  IBM China Systems and Technology Laboratory
>  
>  
>