December 2020 - systemroles - Fedora Mailing-Lists

roles are now using tox-lsr for tox instead of local .travis scripts

by Rich Megginson

Most of the roles have been converted to use https://github.com/linux-system-roles/tox-lsr, including the GitHub Actions CI jobs. The roles that haven't yet been converted are logging https://github.com/linux-system-roles/logging/pull/192 network https://github.com/linux-system-roles/network/pull/331 storage https://github.com/linux-system-roles/storage/pull/183 If you are currently doing role development, you will need to update first and rebase your work on your project main/master branch. Then, install the plugin like this: pip install --user git+https://github.com/linux-system-roles/tox-lsr@1.0.0 if this doesn't work for some reason, try this: git clone https://github.com/linux-system-roles/tox-lsr -b 1.0.0 cd tox-lsr python setup.py install --user I've tried to make it work as before, so that you can use e.g. `tox -l`, `tox -e flake8`, etc.

3 years, 4 months

1
0
0 / 0

Parameter for hostname or IP address?

by Rich Megginson

The VPN role allows for the user to specify a hostname or an IP address for the connection https://github.com/linux-system-roles/vpn/pull/2#pullrequestreview-538046482 I wanted to open this discussion up to a wider audience. We have some precedence in system roles for a field that can take a hostname or IP address. The logging role has a field `server_host` in the elasticsearch and relp outputs https://github.com/linux-system-roles/logging/blob/master/README.md#loggi... - The documentation says "Host name" but this can be an IP address. Also the `target` field for the forwards output - it says "Target host (fqdn)." but it can be an IP address. The metrics role has https://github.com/linux-system-roles/metrics/blob/master/README.md#role-... `metrics_monitored_hosts` which I believe takes IP addresses as well as hostnames. There may be other examples in some of the other roles Does it matter what is the name that the VPN role uses for this field? Is `host` ok?

3 years, 4 months

4
5
0 / 0

Switch to Github Actions from Travis CI?

by Rich Megginson

We are currently having a problem with Travis CI. You may have noticed that your recent PRs are not being tested with Travis, that they seem never to start. I think that is my fault for not signing up for the open-source plan for linux-system-roles earlier. I have done so, but I have no idea when they will respond. In the meantime, I have been investigating using Github Actions. https://github.com/linux-system-roles/ci-testing/pull/3 Here is the workflow definition file: https://github.com/linux-system-roles/ci-testing/blob/06d3f91151bcd7de1a5... There was a good bit of hackery to support py26 since Github Actions Workflows (actions/setup-python@v2) doesn't support it natively. The other missing piece is tox-travis, which allows you to have fine grained control of which tox tests are run for a specific version of python. So right now we run all of the default tox jobs for all of the python versions (e.g. we run black, flake8, etc. on all versions of python). If we wanted to do the same in GHA, we would have to define an explicit job for each version of python (instead of using the matrix feature) - AFAIK (I'm quite new to GA so if anyone has a better way to do this, let me know). IMO this is not a blocker to move to GHA. What do you think?

3 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

systemroles December 2020