Polish and improve ansible roles in GeekOops
a project by ph03nix
Updated almost 3 years ago. No love. 2 followers.

Project Description

Geeko-ops is a collection of community-driven Ansible roles for SLES/openSUSE based distributions.

Goal for this Hackweek

The project needs to be refreshed to SLES/Leap 15.4. In addition I like to review and improve some recent community contributions there.

Anybody willing to contribute in this project is welcome!

Resources

  • https://geekoops.github.io/

Join this project

Looking for hackers with the skills:

ansible devops

This project is part of:

Hack Week 22

Activity

  • almost 3 years ago: ph03nix added keyword "devops" to this project.
  • almost 3 years ago: ph03nix added keyword "ansible" to this project.
  • almost 3 years ago: ph03nix started this project.
  • almost 3 years ago: ph03nix originated this project.


    • Comments

    • ph03nix
      almost 3 years ago by ph03nix | Reply

      Yay, Kickoff! I started today in fixing the molecule tests for the nginx role and wrote a small note on how I did that on my openqa-bites blog.

    • ph03nix
      almost 3 years ago by ph03nix | Reply

      Was busy in the last days to refresh my current roles and contribute to another role from a community member.

    • ph03nix
      almost 3 years ago by ph03nix | Reply

      Ok, I refreshed all of my roles, wrote a guide on how to use molecule, updated the website and reviewed two other roles, for which I created PRs.

    • ph03nix
      almost 3 years ago by ph03nix | Reply

      Note to myself: Maintaining those roles is considerable work. I spend most of the week in just getting the old roles back to shape. Also I like that it's becoming more of a community project.

    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

    1. https://github.com/SUSE/qe-sap-deployment
    2. 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