...
Take help of the 'Description & Troubleshooting' section above to troubleshoot the alarms. Se also GeneralTroubleshooting.
Upgrade & Verification
We run docker.sunet.se/pyff as docker image. ci.sune.se (Jenkins) builds that image every day with newer versions of dependencies and push it to docker.sunet.se.
We should make sure to run an image that is manually tagged specially in production and has been tested beforehand either in SeamlessAcess beta environment or in other test environments in SUNET. We should not run an image with a tag that is automatically added by ci.sunet.se. By running a manual tag that has been tested, we do not risk running an image with dependencies that may not be compabile with underlying code for pyFF. Currently we are running a 'stable' tag that has been tested in EIDAS project.
- Both PyFF and
- Both PyFF and
sunet-md_publisherare upgraded by chaging the versions inthiss-ops/global/overlay/etc/puppet/cosmos-rules.yaml.The puppet manifests for production, beta and staging are separate.
| Code Block |
|---|
thiss::pyff_prod:
pyff_version: eidas-2.1.3-stable
output: /var/www/html/metadata.json
output_trust: /var/www/html/metadata_sp.json
thiss::md_publisher_prod:
watch: /var/www/html/metadata.json
watch_sp: /var/www/html/m |
...
By setting the version parameter in thiss-ops/global/overlay/etc/puppet/cosmos-rules.yaml or in the thiss-ops/global/overlay/etc/puppet/modules/thiss/manifests/demo_sp.pp.
Log
Server
| Name | Location | Env |
|---|---|---|
| log.seamlessaccess.org | STO1v2, Safespring | Prod |
Descripton
The servers runs a syslog application to collect logs from service.seamlessaccess.org. The server is specifically allowed in Fastly configuration, you can check that under Logging for the current version of service.seamlessacces.org configuration running in Fastly.
...