From: James Page <james.page@ubuntu.com>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Sage Weil <sage@inktank.com>,
"Laszlo Boszormenyi (GCS)" <gcs@debian.hu>,
Dan Mick <dan.mick@inktank.com>,
ceph-devel@vger.kernel.org
Subject: Re: deb/rpm package purge
Date: Wed, 20 Mar 2013 17:27:04 +0000 [thread overview]
Message-ID: <5149F168.8010802@ubuntu.com> (raw)
In-Reply-To: <5149CC4A.9030409@inktank.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 20/03/13 14:48, Mark Nelson wrote:
>>
>> We'll need to update teuthology ceph.py and nuke to clean up
>> /var/lib/ceph (for qa runs), and I think we should add a
>> ceph-deploy 'purgedata' command to clean out /var/lib/ceph on a
>> given host.
>
> It's not as important given that it won't outright destroy the
> cluster, but perhaps we should also leave /etc/ceph untouched on
> purge if a ceph.conf file has been placed in it (since that also
> was not installed by the package, but rather by a user?). I figure
> we should probably try to get it right now. The message about the
> directory not being empty sounds good.
>
> My thought here is:
>
> - remove anything created by the packages in /var/lib/ceph that has
> been untouched since package installation. - remove /var/lib/ceph
> if it has been untouched - remove /etc/ceph if it has been
> untouched
If those directories are created by dpkg rather than maintainer
scripts (i.e. in ceph.dirs rather than ceph.postinst) you should
should get that all for free; if the directories contain anything dpkg
does not know about it will just not removed them.
- --
James Page
Ubuntu Core Developer
Debian Maintainer
james.page@ubuntu.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBCAAGBQJRSfFoAAoJEL/srsug59jDJgsP/0zD4aKFtimFPh02/zdfJ3X0
BEY8Jmnmt3HcCxSPbGleZ+2p/38iLfLz8HdM1ZpOwGDVIv13N45vG0wW9zF/843R
8vKoGHJY7gAt/uY1fqa115m9txeNXAIZoaxwjrd6Zd31pgPvTBmfZhVsFKUnk7E5
9JmUs/K8gjjAZajhkUKgddp2ID70n/WGdHR+iu5cy72TyuvXVBQV1OmyYi9lMIxM
yHGnCM/X7x5DE1g61x532VP2D0gAegA2WWURoqQ6vAM3IZfVGVuvat+HdzZ8Ej8z
LfTk+8n2alTj6s1Xp3KGbb/D231MIi3VBaFMQx5pBlM29lAv8OYKidRQpZc9bZe2
5m5vhDutp4ZOZmqxDvDdayZgb/s8uVuodT2XK7qn4KbBRDEJN5aJKiUzXH0wTVTZ
Lg/A/criFuzRP+ZH/Sh1pfSnLkNrrLMbdTglUv4krM2L6ZPOmEU3fh+UIXkr2u9t
f6lnu4fVBwikDy/4hDztVL76IqB3wjnxYlJ1uHMHOrCugDeLRsGHdbCdFcoZonRW
rUhdrtqzuuSbPHkzs/dEMCm4vF439YdmuL4WGsfzxEu+djcESDtzuAw4D1LRO12V
JbEc9s8+L84oBJUv5dCSDG333jWc/8eihSs1ZG33NKZsWsNheppLR6aeXbg/nGi1
53R63uM1Lv7f1UaTxvH8
=6adU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-03-20 17:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 19:48 deb/rpm package purge Sage Weil
2013-03-19 19:59 ` Greg Farnum
2013-03-19 20:05 ` Mark Nelson
2013-03-19 20:46 ` Dan Mick
2013-03-19 20:51 ` Sage Weil
2013-03-19 22:27 ` Laszlo Boszormenyi (GCS)
2013-03-19 22:29 ` Sage Weil
2013-03-19 22:51 ` Laszlo Boszormenyi (GCS)
2013-03-19 22:59 ` Sage Weil
2013-03-20 6:29 ` Laszlo Boszormenyi (GCS)
2013-03-20 12:48 ` Sage Weil
2013-03-20 14:48 ` Mark Nelson
2013-03-20 17:27 ` James Page [this message]
2013-03-20 23:23 ` Laszlo Boszormenyi (GCS)
2013-03-21 1:08 ` Dan Mick
2013-03-19 23:01 ` Mark Nelson
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=5149F168.8010802@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@inktank.com \
--cc=gcs@debian.hu \
--cc=mark.nelson@inktank.com \
--cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.