Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] [ps] Re: pSConfig Web Admin

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] [ps] Re: pSConfig Web Admin


Chronological Thread 
  • From: Michael Johnson <>
  • To: Johann Hugo <>
  • Cc: ,
  • Subject: Re: [perfsonar-user] [ps] Re: pSConfig Web Admin
  • Date: Tue, 9 Apr 2019 10:11:26 -0400

Hi Johann,

Responses inline:

On Fri, Apr 05, 2019 at 03:43:25PM +0200, Johann Hugo wrote:
1) I'm running PWA on the same VM as Maddash, using ports 8000 + 8443 for
the Nginx container. The meshconfig URL, as shown in the documentation
below, points to http://my-server/pub/config/ , but gives an error when I
try to export my configs. If I open http://my-server/pub/config/ directly
in my browser I get nothing, but https://my-server:8443/pub/config/ seems
to be there. Is the URL as shown in the PWA web GUI still valid when the
Nginx container listens on port 8000 + 8433 ?
http://docs.perfsonar.net/pwa.html

You're right, PWA doesn't give you a way to override the port in the URL it
generates -- it just assumes 80/443. That's something we should add, I
created a ticket for it.


2) Inside this file /etc/pwa/nginx/conf.d/pwa.conf I've changes the ports
for http and https to 8000 and 8433. I'm just wondering if the redirect
from http:my-host:8000/ to https:myhost:8433/ will work correctly

a.) A redirect should work, just keep in mind that you need to create the
redirect on the parent host, in Apache.

b.) Another option would be a reverse proxy, something like this:

ProxyPass "/pub/" "https://localhost:8443/";

c.) Better still might be to have a reverse proxy directly to your pwa-pub instance,
cutting out the nginx middle man. Nginx is just acting as a reverse proxy anyway, so if
you do "b." above, you'll have two layers of proxying.

Assuming you haven't changed what port the publisher runs on, or the name of
the publisher, Apache on the parent host would look something like this:

ProxyPass "/pub/" "http://pwa-pub1:8080/";


3) If I change any of the configs in /etc/pwa, what procedure should I
follow to make the new changes applicable to the docker containers ? Should
I just systemctl restart docker ?

I *think* the PWA portions will automatically see a config change, but nginx
likely won't. 'systemctl restart docker' will restart all the containers,
which is fine if you don't mind the slight downtime. Or you can just restart
the one(s) of interest using docker, i.e.:

docker restart nginx

I hope this helps.

Thanks,
Michael


--
Michael Johnson
GlobalNOC DevOps Engineer

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page