Etherpad: https://autotest.etherpad.mozilla.org/1?
Telephone bridge:
https://www.intercallonline.com/listNumbersByCode.action?confCode=9197544214
Highlights
More test grid work activity, and despite working hard on reviews, we
still have a large number of virt-test pull requests.
Commits on next - autotest
Updates to the cgroup testing utilities, bug fixes for the machine
recovery in autotest, more mechanisms to tell grid admin of potential
problems, and our highlight, Ruda's work updating the web interface to
provide static files, such as CSS through Django.
Lucas Meneghel Rodrigues (3):
server.hosts.remote: Introduce default install timeout
server.hosts.remote: Set value type for install_timeout
scheduler.monitor_db: Notify grid admin when a dead host is
reverified
Pavel Hrdina (2):
utils_cgroup: Strip the slash from cgroup path
utils_cgroup: Fix regexp for cgroup controllers
Peter Krempa (1):
utils_cgroup: Add option to check if cgconfig service exists
Rudá Moura (2):
install-autotest-server.sh: Add support to install on Debian.
web frontend: Use django.contrib.staticfiles to deliver static
content
Commits on next - virt-test
virt-test 2013.09.23 was released Tuesday, with a lot of interesting
changes, as well as bugfixes:
Fixes to git signed tag verification
New QEMU multi_disk_random_hotplug test
New Libvirt domiflist test
New svirt attach disk test
New libvirt_bench_domstate_switch_in_loop test
You can check a detailed list of changes here:
https://github.com/autotest/virt-test/compare/2013.09.17...2013.09.24
It seems that we're finally coming to a weekly release schedule basis. Yay!
Since the release, we had a new timedrift without network interface by
Jiri, support to SLES 11 SP3, and the usual bugfixes to the other tests.
Feng Yang (1):
virttest.remote: Update password and login prompt in
handle_prompts function
Jiří Župka (6):
virt: Fix OpenVSwitch configuration to be able to start with ./run
virt: Fix login operation with vm without network interface.
virt: Allow set network interface parameters none.
virt: Adds support for other get time methods.
virt: Adds support for kernel extra params
virt: Adds timedrift test without network interface.
Lucas Meneghel Rodrigues (2):
libvirt tests: PEP8 Fixes
virttest.qemu_devices: PEP8 Fixes
Lukáš Doktor (1):
Merge pull request #850 from humanux/kdump
Xiaoqing Wei (2):
guests: Added SLES 11 SP3
tests.unattended_install: should not generate autoyast.iso when
use floppy_ks
Xu Tian (4):
qemu.test: add support mirror image to nfs/iscsi
qemu.test: fix cdrom test failed on some latest guest
qemu.test: add step reboot guest when it resume from s3/s4
qemu.test: add scenario to eject non-removeable device force
Yang Feng (2):
Merge pull request #862 from ypu/cluster_size
Merge pull request #845 from humanux/transfer_file_over_ipv6
Yiqiao Pu (2):
cfg: Update cluster_size to image_cluster_size
test.stress_boot: Update the failed log for test
Yunping Zheng (3):
qemu.test.transfer_file_over_ipv6: some modification
virt.tests.kdump: Configuring the Core Collector for rhel5 guest
virttest.qemu_vm: Fix deactivate_nic functions.
Pull requests still in review
Autotest
No open pull requests at this time
Virt Test
50 open pull requests, basically at the same level as last week, meaning
we only managed to consume the extra pull requests produced during this
week. Some more work is needed to reduce the current amount.
One thing that we could consider to make the development process more
agile is to have sub maintainer trees, and follow a model similar to the
linux kernel:
* Submaintainers get patches from a given subsystem and take care of
them, test them
* They send large pull requests from time to time to the reference
tree maintainer, that pulls the patches and performs more testing.
Do you think that could work in our projects?
Proposal:
* Have one "scrum master"/project manager that rotates every week
going through the list of issues and assigning/asking people about the
current status of each issues
* People take a look at their list every week and try to work on the
reviews
* Formal RFC to the mailing list after this meeting
Autotest reporting work
Bugfixes to the host recovery functions, as well as new notifications
for hosts that can't be recovered by autotest. More work on
notifications is expected for next week.
Grid maintenance
Spent time setting up jobs for Michael Tirskin, that involve testing
QEMU from a signed tag, a feature recently introduced in virt-test
Libvirt updates
Excellent continuing great collaboration on reviews!
Healthy mix of core code updates + new or improved tests
Questions Corner
TODO
lmr
More work on test grid notifications
cevich
patch review
Improve libvirt testing SELinux support
Tinker on github reporting code + aexpect
documentation
cleber
Autotest 0.15.1 RPM in Fedora
Push the spec file to next (which tracks next)
Move "software installer" from virt-test back to autotest, adding
unittests and docs
This is necessary for the component isolation work v2, because
installing say qemu from koji will already register that software
component in the test database
Coming along nicely, expect pull request by next week
jzupka
same as last week
review pull-requests
bugs rtc, glusterfs
move not general test from general tests
rmoura
review pull-requests with lrmr's help
ldoktor
I was on teambuilding, so I'll work on last weeks items :-)
qemu_devices
PCI support for PCI switch/bridge/...
update virtio_console.interrupted_loopback test
unplug should work better on latest kernel
reviewing pull requests
fixing bugs
kvm-qe(BJ):
Keep on bugs fix and case development. And each of us will force on one
or two features in the following list:
And our National Day vacation will start from 10.1 to 10.7. We will not
work at that time.
ypu: whql cases
yunzheng: ipv6 related cases
xutian: timer device
fyang: device assignment
_______________________________________________
Virt-test-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/virt-test-devel
