Christian PERRIER wrote:
> Template: sheepdog/start
> Type: boolean
> Default: true
> _Description: Automatically start the sheepdog service?
> Please choose whether you want the shhepdog service to
> start automatically when the system is booted.
Typo: s/shhep/sheep/. And no need to phrase it as a decision about
what I want -
Please choose whether the sheepdog service should start automatically
when the system is booted.
> Template: sheepdog/daemon_args
> Type: string
> _Description: Arguments for the sheepdog daemon:
> If no argument is given, the sheepdog daemon is started with the corosync driver on
> port 7000.
Shouldn't this start with something like:
Please choose the commandline arguments that should be passed to the
sheepdog daemon. If no argument is given, the default behavior is to
start with the corosync driver on port 7000.
(Does that mean "with 7000 as the corosync driver port" or is it two
things, "start on port 7000, using the corosync driver"? Or will
sheepdog users find it obvious?)
> Addition arguments are:
As MES spotted, s/Addition/Additional/, but "additional" to what?
Available options include:
> -p, --port specify the TCP port to listen to
> -l, --loglevel specify the level of logging detail
> -d, --debug include debug messages in the log
> -D, --directio use direct I/O when accessing the object store
> -z, --zone specify the zone ID
> -c, --cluster specify the cluster driver
> More infomation can be found in the sheep(8) manual page.
s/fom/form/. I suppose it doesn't matter that we could do all this
with a one-column indent and less of a gap. I was surprised to learn
that the controlling daemon is called "sheep", though...
The package description is really quite good:
> -Description: Distributed storage system for KVM/QEMU
> +Description: distributed storage system for KVM/QEMU
> Sheepdog provides highly available block level storage volumes that can be
> attached to KVM/QEMU virtual machines. Sheepdog scales to several hundreds
> nodes, and supports advanced volume management features such as snapshot,
> cloning, and thin provisioning.
"Highly available" isn't something I'd naturally say, but people who
care about this topic seem to, so fair enough. It's possible this
use of "snapshot" to mean "snapshotting"/"snapshot capability" is a
similar piece of jargon, but I'd prefer to avoid it by recycling that
surplus S from the line before:
Sheepdog provides highly available block level storage volumes that can be
attached to KVM/QEMU virtual machines. Sheepdog scales to several hundred
nodes, and supports advanced volume management features such as snapshots,
cloning, and thin provisioning.
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Openstack-devel mailing list