egi-federation/ansible-role-ui

Ansible role to deliver User Interfaces

ansible-role-ui's Issues

credentials ownership in the UI

Hi Bruce
thanks a lot for the amazing work!
i just tested the docker container and i would like to know if there is a way to mount the current credentials without changing their ownership within the container. just to better explain

imagine i run as root and i have my credentials there, if i run the container as suggested

docker run -u griduser -ti --rm --name ui -v $HOME/.globus:/home/griduser/.globus quay.io/egi/ui /bin/bash

the credentials available under the griduser home will be owned by root

is there a way in docker to mount a volume and give the ownership to the user specified via -u?

thanks
Andrea

Quay container should be rebuild due to security issues

Quay container should be rebuild due to security issues: https://quay.io/repository/egi/ui?tab=tags

Install by default or allow to install condor on demand

Install by default or allow to install condor on demand.
Required to interact with HTCondorCE CEs.

Create list of packages to be tested via repoquery

Short Description of the issue

When testing the quality criteria of the middleware which is installed with this role, we need a list of packages which are provided as dependencies of the UI metapackage. This should be passed to pytest as a fixture, and can easily be obtained by a subprocess call -

listfile = open("list.txt", "w")
subprocess.call(["repoquery", "--requires", "ui"], stdout=listfile)
packages = listfile.read().splitlines()

Summary of proposed changes

Find a way to generate the fixtures dynamically.

User Interface should have an ssh client

Short Description of the issue

The user interface should have an ssh client installed, at least to be able to use the RCAuth master portal.

Relevant task

None

Summary of proposed changes

I propose to add:

• openssh clients to the prerequisites list
• an openssh client configuration template to the templates dir
• a task to template the client configuration

Prerequisites

• Test coverage added
• no known vulnerabilities introduced by the package
• client template checked by SVG

Revive container building and deployment

Revive container building and deployment