Mailing List Archive

----- Original Message -----
> Hi there,
>
> we are using exportfs for building datastores for VMWare.
>
> After migrating 1 NFS resource to another node (after sucessful fencing
> e.g.),
> VMWare doesn't see that datastore until I manually fire _exportfs -f_ on the
> new cluster node.
>
> I tried to modify the resource agent itself like:
>
> 247 restore_rmtab
> 248
> 249 ocf_log info "File system exported"
> 250
> 251 sleep 5 #added
> 252
> 253 ocf_run exportfs -f || exit $OCF_ERR_GENERIC #added
> 254
> 255 ocf_log info "kernel table flushed" #added
> 256
> 257 return $OCF_SUCCESS
>
> but this didn't do the trick.
>
> Does anyone has an idea how to resolve that issue?

HA NFS is tricky and requires a very specific resource startup/shutdown
order to work correctly.

Here's some information about use cases I test. At this point, the active/passive
use case is well understood. If you are able to, I would recommend modeling
deployments using the A/P use case guidelines.

HA NFS Active/Passive:
https://github.com/davidvossel/phd/blob/master/doc/presentations/nfs-ap-overview.pdf?raw=true
https://github.com/davidvossel/phd/blob/master/scenarios/nfs-active-passive.scenario

HA NFS Active/Active:
https://github.com/davidvossel/phd/blob/master/doc/presentations/nfs-aa-overview.pdf?raw=true
https://github.com/davidvossel/phd/blob/master/scenarios/nfs-active-active.scenario

-- Vossel

>
> Cheers,
> Hauke
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

of course I currently use an active/active setting for some load spreading
issues, but I will try to use an (more ordered) active/passive setting. I need
that for VMWare and afaik it is NFSv3 so far.

Thanks for pointing things out.

Cheers,
Hauke

---
original message
timestamp: Monday, November 17, 2014 11:53:09 AM
from: David Vossel <dvossel@redhat.com>
to: The Pacemaker cluster resource manager <pacemaker@oss.clusterlabs.org>
cc:
subject: Re: [Pacemaker] exportfs resource agent modifications
message id: <1005680886.61322.1416243189209.JavaMail.zimbra@redhat.com>

> ----- Original Message -----
>
> > Hi there,
> >
> > we are using exportfs for building datastores for VMWare.
> >
> > After migrating 1 NFS resource to another node (after sucessful fencing
> > e.g.),
> > VMWare doesn't see that datastore until I manually fire _exportfs -f_ on
> > the new cluster node.
> >
> > I tried to modify the resource agent itself like:
> >
> > 247 restore_rmtab
> > 248
> > 249 ocf_log info "File system exported"
> > 250
> > 251 sleep 5 #added
> > 252
> > 253 ocf_run exportfs -f || exit $OCF_ERR_GENERIC #added
> > 254
> > 255 ocf_log info "kernel table flushed" #added
> > 256
> > 257 return $OCF_SUCCESS
> >
> > but this didn't do the trick.
> >
> > Does anyone has an idea how to resolve that issue?
>
> HA NFS is tricky and requires a very specific resource startup/shutdown
> order to work correctly.
>
> Here's some information about use cases I test. At this point, the
> active/passive use case is well understood. If you are able to, I would
> recommend modeling deployments using the A/P use case guidelines.
>
> HA NFS Active/Passive:
> https://github.com/davidvossel/phd/blob/master/doc/presentations/nfs-ap-over
> view.pdf?raw=true
> https://github.com/davidvossel/phd/blob/master/scenarios/nfs-active-passive
> .scenario
>
> HA NFS Active/Active:
> https://github.com/davidvossel/phd/blob/master/doc/presentations/nfs-aa-over
> view.pdf?raw=true
> https://github.com/davidvossel/phd/blob/master/scenarios/nfs-active-active.
> scenario
>
> -- Vossel
>
> > Cheers,
> > Hauke
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> >
> > Project Home: http://www.clusterlabs.org
> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> > Bugs: http://bugs.clusterlabs.org
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
--
Hauke Bruno Wollentin
(Infrastructure Engineer Cloud)


iNNOVO Cloud GmbH

Düsseldorfer Straße 40a

65760 Eschborn (Taunus)

Tel. 069/ 24 747 18-26

Fax. 069/ 24 747 18-1022

Mail. hauke-bruno.wollentin@innovo-cloud.de



Geschäftsführung: Dr. Sebastian Ritz, Stefan
Sickenberger

Registergericht Frankfurt a.M., HRB 95751/USt.-IdNr.: DE2870 34448
Frankfurter Volksbank eG (Blz. 501 900 00) Konto 600 200 9917
IBAN DE94501900006002009917 BIC: FFVBDEFF



Informationen (einschließlich Pflichtangaben) zu einzelnen, innerhalb der
EU tätigen Gesellschaften und Zweigniederlassungen der iNNOVO Cloud gmbH
finden Sie unter http://www.innovo-cloud.de/pflichtangaben.htm. Diese
E-Mail enthält vertrauliche und/ oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten
Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser E-Mail ist nicht gestattet.

Please refer to http://www.innovo-cloud.de for information (including
mandatory corporate particulars) on selected iNNOVO Cloud in the European
Union. This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.