From: Christine Caulfield <ccaulfie@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Status
Date: Tue, 01 Sep 2009 07:57:39 +0100 [thread overview]
Message-ID: <4A9CC5E3.7000505@redhat.com> (raw)
Sorry this is late, it was a bank holiday in the UK yesterday.
W/C 24th August
Monday:
- Looking into clvmd errors on Rawhide
Working with LVM team to resolve & test
- Tried filing errata again. it seemed to work :)
Now done 5.3.z and 5.4.z
Tuesday:
- Interviewing Angus Salkeld
- General mucking about with STABLE3
Wednesday:
- Failing to file expenses
- Setting up VMs so I can do cross-hosted clusters
(that's harder than it sounds)
Thursday:
- Ill overnight, feeling a bit wobbly this morning, not sure why. taking
it easy
- Patch testing
- writing a cman_tool for a cman-less world
Some odd problems, need to investigate
Friday:
- Working on quorumtool for corosync, a replacement for cman_tool
in master, but also generally helpful!
- This uncovered four bugs that I needed to fix to get it to work!
next reply other threads:[~2009-09-01 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 6:57 Christine Caulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-10 9:04 [Cluster-devel] Status Christine Caulfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9CC5E3.7000505@redhat.com \
--to=ccaulfie@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).