I was working on reimplementing the drbd configuration file(s) so that
they're a bit more comprehensible to the administrator.
Ie. One file would be nice.
One file which can be read pretty much all at once would be nice.
My first take was a fancy approach involving a parser written in bash.
It's far too slow so I'm throwing it away.
Before I start again, I'd like to know if this conflicts with other
efforts. At this point my idea of a file looks something like this:
---cut--here---
# comment
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
---cut--here---
It's a sort of drbdtab. The verbosity of comments in the current file are
nice for the first time working with the file, but very much in the way on
successive visits. Other things this format should feature are stub
hosts.. ie
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> [<port>]
As the local drbd software doesn't need anymore. Fully specified hosts
are nice for keeping one file across all machines.
I think commands which attempt to start up drbd services should work like
mount.. matching on groupname, either of the device names, etc.
In the case where two fully specified host lines are given the software
should be able to determine which one is approrpriate for local use based
on ip addresses, hostnames, etc. available locally.
Please flame gently.
-josh
they're a bit more comprehensible to the administrator.
Ie. One file would be nice.
One file which can be read pretty much all at once would be nice.
My first take was a fancy approach involving a parser written in bash.
It's far too slow so I'm throwing it away.
Before I start again, I'd like to know if this conflicts with other
efforts. At this point my idea of a file looks something like this:
---cut--here---
# comment
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
---cut--here---
It's a sort of drbdtab. The verbosity of comments in the current file are
nice for the first time working with the file, but very much in the way on
successive visits. Other things this format should feature are stub
hosts.. ie
group: <groupname> <protocol> <timeout> <anyother group thing>
<host> <port> <upper_dev> <lower_dev> <other_host_thing>
<host> [<port>]
As the local drbd software doesn't need anymore. Fully specified hosts
are nice for keeping one file across all machines.
I think commands which attempt to start up drbd services should work like
mount.. matching on groupname, either of the device names, etc.
In the case where two fully specified host lines are given the software
should be able to determine which one is approrpriate for local use based
on ip addresses, hostnames, etc. available locally.
Please flame gently.
-josh