nfs-charm:revert-6-avoid-duplicate-exports

Last commit made on 2018-12-19
Get this branch:
git clone -b revert-6-avoid-duplicate-exports https://git.launchpad.net/nfs-charm

Branch merges

Branch information

Name:
revert-6-avoid-duplicate-exports
Repository:
lp:nfs-charm

Recent commits

c117d73... by Mike Wilson <email address hidden>

Revert "Avoid duplicate exports"

40c7830... by Mike Wilson <email address hidden>

Merge pull request #6 from cjwatson/avoid-duplicate-exports

Avoid duplicate exports

f33facf... by Colin Watson

Avoid duplicate exports

https://github.com/juju-solutions/interface-mount/pull/4 allows for multiple
mount requests to share the same export name. This could previously have
caused this charm to write an exports file with duplicate lines, which in turn
caused `exportfs` to issue a "duplicated export entries" error message and exit
with status 1.

`nfs_relation_changed` now deduplicates the lines it writes to its exports
file. It still needs to send an appropriate response to each `mount` relation,
so it now keeps track of those responses separately.

4761b23... by Mike Wilson <email address hidden>

Merge pull request #5 from cjwatson/nrpe

Add minimal Nagios monitoring support

0a04df2... by Colin Watson

Add minimal Nagios monitoring support

There's no interesting service monitoring here as yet, but host
monitoring is better than nothing at all.

f433c7d... by Mike Wilson <email address hidden>

Adding repo to layer

424bd1a... by Mike Wilson <email address hidden>

Merge pull request #4 from cjwatson/layer-exclude

Exclude builds and deps from charm build

41c44a2... by Mike Wilson <email address hidden>

Merge pull request #3 from cjwatson/fix-refresh-flag

Fix refresh_nfs_mounts flag name

f6915dc... by Colin Watson

Fix refresh_nfs_mounts flag name

The idle_status used the wrong flag name for whether NFS mounts need to
be refreshed, so it would set the active status a little too early.

9907977... by Colin Watson

Exclude builds and deps from charm build

This makes it a bit easier to test changes to this charm via `charm
build .`.