Project Description
I started the geekoops project last year for hosting some generic ansible roles for openSUSE. This year I'm gonna continue to work on the roles.
The project is still very young and has not received much love but it has not been forgotten. Everyone is welcome to help out or contribute. If you know ansible a little bit or you are keen in learning it, you're good to join!
Goal for this Hackweek
I'd like to extend the project by adding some more roles and improve the website/documentation so that it becomes a useful resource for the openSUSE community.
Resources
Keywords: DevOps, ansible, automation, geekoops, openSUSE
This project is part of:
Hack Week 21 Hack Week 20
Activity
Comments
-
-
-
over 3 years ago by ph03nix | Reply
Oh boy, those were already almost three intensive days.
I revived all of the current roles (moved them to Leap 15.4), reduced the number of external dependencies for testing to zero and updated the main page.
Thanks to Teo for testing the Webserver example, which was horribly broken so I fixed and updated it this morning.
-
Similar Projects
Multimachine on-prem test with opentofu, ansible and Robot Framework by apappas
Description
A long time ago I explored using the Robot Framework for testing. A big deficiency over our openQA setup is that bringing up and configuring the connection to a test machine is out of scope.
Nowadays we have a way¹ to deploy SUTs outside openqa, but we only use if for cloud tests in conjuction with openqa. Using knowledge gained from that project I am going to try to create a test scenario that replicates an openqa test but this time including the deployment and setup of the SUT.
Goals
Create a simple multimachine test scenario with the support server and SUT all created by the robot framework.
Resources
- https://github.com/SUSE/qe-sap-deployment
- terraform-libvirt-provider
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/
First meeting Hackweek catchup
- Monday, December 1 · 11:00 – 12:00
- Time zone: Europe/Madrid
- Google Meet link: https://meet.google.com/rrc-kqch-hca