Re: [Gluster-devel] Checklist for QEMU integration for upstream release
On Tue, Sep 06, 2016 at 10:56:39AM +0200, Niels de Vos wrote: > On Tue, Sep 06, 2016 at 09:01:18AM +0530, Bharata B Rao wrote: > > On Mon, Sep 05, 2016 at 05:57:55PM +0200, Niels de Vos wrote: > > > On Sat, Sep 03, 2016 at 01:04:37AM +0530, Pranith Kumar Karampuri wrote: > > > > hi Bharata, > > > >What tests are run before the release of glusterfs so that we > > > > make > > > > sure this integration is stable? Could you add that information here so > > > > that I can update it at > > > > https://public.pad.fsfe.org/p/gluster-component-release-checklist > > > > > > I normally run some qemu-img commands to create/copy/... VM-images. When > > > I have sufficient time, I start a VM based on a gluster:// URL on the > > > commandline (through libvirt XML files), similar to this: > > > > > > http://blog.nixpanic.net/2013/11/initial-work-on-gluster-integration.html > > > > I did reply with the testcases I used to run normally. Guess the reply > > didn't make it to the list. > > Thanks, now it did. One of our admins accepted the challange ;-) > > > > In case Bharata is not actively working (or interested) in QEMU and it's > > > Gluster driver, Prasanna and I should probably replace or get added in > > > the MAINTAINERS file, both of us get requests from the QEMU maintainers > > > directly. > > > > Makes sense as Prasanna is actively contributing to Gluter driver now. > > Do you still want to be listed, or shall we move you to the 'thank you' > section? Please move to 'thank you' section. Regards, Bharata. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Checklist for QEMU integration for upstream release
On Sat, Sep 03, 2016 at 01:04:37AM +0530, Pranith Kumar Karampuri wrote: > hi Bharata, >What tests are run before the release of glusterfs so that we make > sure this integration is stable? Could you add that information here so > that I can update it at > https://public.pad.fsfe.org/p/gluster-component-release-checklist Not sure how to edit that, but this is what you should ensure minimally... - Create a VM image on gluster backend qemu-img create -f qcow2 gluster://... - Install a distro on the created image using qemu qemu ... gluster://... - May be run a few IO benchmarks/stress tests like dbench, fio etc on guest disk which is backed by gluster. Regards, Bharata. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Checklist for QEMU integration for upstream release
On Mon, Sep 05, 2016 at 05:57:55PM +0200, Niels de Vos wrote: > On Sat, Sep 03, 2016 at 01:04:37AM +0530, Pranith Kumar Karampuri wrote: > > hi Bharata, > >What tests are run before the release of glusterfs so that we make > > sure this integration is stable? Could you add that information here so > > that I can update it at > > https://public.pad.fsfe.org/p/gluster-component-release-checklist > > I normally run some qemu-img commands to create/copy/... VM-images. When > I have sufficient time, I start a VM based on a gluster:// URL on the > commandline (through libvirt XML files), similar to this: > http://blog.nixpanic.net/2013/11/initial-work-on-gluster-integration.html I did reply with the testcases I used to run normally. Guess the reply didn't make it to the list. > In case Bharata is not actively working (or interested) in QEMU and it's > Gluster driver, Prasanna and I should probably replace or get added in > the MAINTAINERS file, both of us get requests from the QEMU maintainers > directly. Makes sense as Prasanna is actively contributing to Gluter driver now. Regards, Bharata. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Spurious failure in tests/basic/bd.t [22, 23, 24, 25]
CC'ing to the correct ID of Mohan
On Fri, May 30, 2014 at 5:45 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
hi Mohan,
Could you please look into this:
Patch == http://review.gluster.com/#/c/7926/1
Author== Avra Sengupta aseng...@redhat.com
Build triggered by== amarts
Build-url ==
http://build.gluster.org/job/regression/4615/consoleFull
Download-log-at ==
http://build.gluster.org:443/logs/regression/glusterfs-logs-20140529:10:51:46.tgz
Test written by == Author: M. Mohan Kumar mo...@in.ibm.com
./tests/basic/bd.t [22, 23, 24, 25]
0 #!/bin/bash
1
2 . $(dirname $0)/../include.rc
3
4 function execute()
5 {
6 cmd=$1
7 shift
8 ${cmd} $@ /dev/null 21
9 }
10
11 function bd_cleanup()
12 {
13 execute vgremove -f ${V0}
14 execute pvremove ${ld}
15 execute losetup -d ${ld}
16 execute rm ${BD_DISK}
17 cleanup
18 }
19
20 function check()
21 {
22 if [ $? -ne 0 ]; then
23 echo prerequsite $@ failed
24 bd_cleanup
25 exit
26 fi
27 }
28
29 SIZE=256 #in MB
30
31 bd_cleanup;
32
33 ## Configure environment needed for BD backend volumes
34 ## Create a file with configured size and
35 ## set it as a temporary loop device to create
36 ## physical volume VG. These are basic things needed
37 ## for testing BD xlator if anyone of these steps fail,
38 ## test script exits
39 function configure()
40 {
41 GLDIR=`$CLI system:: getwd`
42 BD_DISK=${GLDIR}/bd_disk
43
44 execute truncate -s${SIZE}M ${BD_DISK}
45 check ${BD_DISK} creation
46
47 execute losetup -f
48 check losetup
49 ld=`losetup -f`
50
51 execute losetup ${ld} ${BD_DISK}
52 check losetup ${BD_DISK}
53 execute pvcreate -f ${ld}
54 check pvcreate ${ld}
55 execute vgcreate ${V0} ${ld}
56 check vgcreate ${V0}
57 execute lvcreate --thin ${V0}/pool --size 128M
58 }
59
60 function volinfo_field()
61 {
62 local vol=$1;
63 local field=$2;
64 $CLI volume info $vol | grep ^$field: | sed 's/.*: //';
65 }
66
67 function volume_type()
68 {
69 getfattr -n volume.type $M0/. --only-values --absolute-names
-e text
70 }
71
72 TEST glusterd
73 TEST pidof glusterd
74 configure
75
76 TEST $CLI volume create $V0 ${H0}:/$B0/$V0?${V0}
77 EXPECT $V0 volinfo_field $V0 'Volume Name';
78 EXPECT 'Created' volinfo_field $V0 'Status';
79
80 ## Start volume and verify
81 TEST $CLI volume start $V0;
82 EXPECT 'Started' volinfo_field $V0 'Status'
83
84 TEST glusterfs --volfile-id=/$V0 --volfile-server=$H0 $M0
85 EXPECT '1' volume_type
86
87 ## Create posix file
88 TEST touch $M0/posix
89
90 TEST touch $M0/lv
91 gfid=`getfattr -n glusterfs.gfid.string $M0/lv --only-values
--absolute-names`
92 TEST setfattr -n user.glusterfs.bd -v lv:4MB $M0/lv
93 # Check if LV is created
94 TEST stat /dev/$V0/${gfid}
95
96 ## Create filesystem
97 sleep 1
98 TEST mkfs.ext4 -qF $M0/lv
99 # Cloning
100 TEST touch $M0/lv_clone
101 gfid=`getfattr -n glusterfs.gfid.string $M0/lv_clone --only-values
--absolute-names`
102 TEST setfattr -n clone -v ${gfid} $M0/lv
103 TEST stat /dev/$V0/${gfid}
104
105 sleep 1
106 ## Check mounting
107 TEST mount -o loop $M0/lv $M1
108 umount $M1
109
110 # Snapshot
111 TEST touch $M0/lv_sn
112 gfid=`getfattr -n glusterfs.gfid.string $M0/lv_sn --only-values
--absolute-names`
113 TEST setfattr -n snapshot -v ${gfid} $M0/lv
114 TEST stat /dev/$V0/${gfid}
115
116 # Merge
117 sleep 1
**118 TEST setfattr -n merge -v $M0/lv_sn $M0/lv_sn
**119 TEST ! stat $M0/lv_sn
**120 TEST ! stat /dev/$V0/${gfid}
121
122
123 rm $M0/* -f
124
**125 TEST umount $M0
126 TEST $CLI volume stop ${V0}
127 EXPECT 'Stopped' volinfo_field $V0 'Status';
128 TEST $CLI volume delete ${V0}
129
130 bd_cleanup
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
--
http://raobharata.wordpress.com/
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
