PWA RPM Installation¶
If you are installing with Docker, SKIP THIS PAGE
To install PWA using RPM packages, you will need a host or VM with RHEL 7/CentOS 7.
Minimum recommended resources:
4 CPU cores
RHEL 7/CentOS 7
You will need to have the main perfSONAR repo installed, if not already:
rpm -hUv http://software.internet2.edu/rpms/el7/x86_64/latest/packages/perfSONAR-repo-0.10-1.noarch.rpm
Installing PWA from RPMs¶
There are several packages relating to PWA:
The web UI, REST API, and cache service
The publisher (the component from which mesh nodes and maddash pull down the configs
The authentication module that is used for the web UI
Shared libraries for the PWA components (not useful by itself)
To install all of PWA at once. On CentOS7, run this as root (the other packages will be installed as dependencies):
yum install -y perfsonar-psconfig-web-admin-ui perfsonar-psconfig-web-admin-publisher
It is also possible to install only specific components; you could run just a publisher on one host, and the UI on a different host, for instance.
Installing just the UI:
yum install -y perfsonar-psconfig-web-admin-ui
Installing just the publisher:
yum install -y perfsonar-psconfig-web-admin-publisher
Before you start the docker engine, you might want to add any VM specific configuration. For example, your VM might be using /usr/local as a primary partition for your VM. If so, you should have something like following..
By default, your configuration files will be placed under:
PWA code and libraries will be stored under:
Data will be stored under:
The PWA services are managed by
systemd, as with any standard daemon. Upon installing the packages, the appropriate servies will be enabed and started.
Getting the status of the services, run this as root:
systemctl status perfsonar-psconfig-web-admin-*
Similarly, you can (re)start/enable/disable services using
Depending on which packages you installd, the following daemons are available: