Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Load-balanced and file sharing #22

Closed
fhorlaville opened this issue Sep 12, 2016 · 3 comments
Closed

Load-balanced and file sharing #22

fhorlaville opened this issue Sep 12, 2016 · 3 comments

Comments

@fhorlaville
Copy link

Hi, if the config directory is on an NFS shared volume, can one still use files for storing config and certificates or will that not work?
Thanks!

@Eihrister
Copy link

Eihrister commented Sep 12, 2016

It's not built to be NFS-aware, so if there's any network-hickups, trying to access a certificate/key pair from the storage backend, will fail and possibly lead to weird timeout-related things. But with NFS, that's with a lot of things.

That being said, it should work just fine.:

  • Latency with requests shouldn't be an issue: They're cached inside a shared dict in nginx, as well.
  • Multiple instances trying to issue the same cert should also not be an issue: Locking-mechanisms are in place.

How things will react with NFS-locks remains to be seen, I'm guessing you'll just get an error in your log.

:edit: I'm currently doing something similar: Using 3 Linux-containers with OpenRest 1.11.2 + lua-resty-auto-ssl, and /etc/resty-auto-ssl is a bind-mount to a directory on the host. They all share the same dir and it works just wonderfully.

@fhorlaville
Copy link
Author

Thank you very much !!
I'm going to try it with our Gluster share and will report

@GUI
Copy link
Collaborator

GUI commented Oct 22, 2016

Thanks, @Eihrister, for the detailed response! I'm going to go ahead and close this, but feel free to chime in if there's still any other questions or comments about this.

@GUI GUI closed this as completed Oct 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants