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

Looking for hackers with the skills:

ansible website

This project is part of:

Hack Week 21 Hack Week 20

Activity

  • over 3 years ago: nicoladm joined this project.
  • over 3 years ago: ph03nix liked this project.
  • over 3 years ago: ph03nix added keyword "website" to this project.
  • over 3 years ago: ph03nix added keyword "ansible" to this project.
  • over 3 years ago: ph03nix started this project.
  • over 3 years ago: ph03nix originated this project.

  • Comments

    • ph03nix
      over 3 years ago by ph03nix | Reply

      Someone pointed last year out that https://github.com/gnuninu/kwinble might be considered as well as a project here.

    • nicoladm
      over 3 years ago by nicoladm | Reply

      Hi, thanks for linking my project! FYI i have also created this for this year if anyone interested! https://hackweek.opensuse.org/21/projects/extend-k3s-ansible-support-with-new-functionalities-or-fork-slash-create-new-one

    • ph03nix
      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.

    • ph03nix
      over 3 years ago by ph03nix | Reply

      I also updated the https://geekoops.github.io/ page to use the current hugo-geekdoc theme which also has a dark mode. Fancy!

    Similar Projects

    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:

    First meeting Hackweek catchup


    Ansible to Salt integration by vizhestkov

    Description

    We already have initial integration of Ansible in Salt with the possibility to run playbooks from the salt-master on the salt-minion used as an Ansible Control node.

    In this project I want to check if it possible to make Ansible working on the transport of Salt. Basically run playbooks with Ansible through existing established Salt (ZeroMQ) transport and not using ssh at all.

    Goals

    • [v] Prepare the testing environment with Salt and Ansible installed
    • [ ] Discover Ansible codebase to figure out possible ways of integration
    • [v] Create Salt/Uyuni inventory module
    • [ ] Make basic modules to work with no using separate ssh connection, but reusing existing Salt connection
    • [ ] Test some most common playbooks

    Resources

    TBD


    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


    Dynamic Ansible Inventory for Orthos 2 by SchoolGuy

    Description

    Ansible is used in the context of Orthos 2. To enhance the parallel execution of Ansible playbooks for Orthos 2 hosts (machine scanning), the Cobbler dynamic Inventory plugin should be evaluated.

    Goals

    Improve the parallelization of machine scanning in Orthos 2.

    Resources

    • https://github.com/openSUSE/orthos2/
    • https://docs.ansible.com/projects/ansible/latest/inventoryguide/introdynamic_inventory.html#inventory-script-example-cobbler


    Sim racing track database by avicenzi

    Description

    Do you wonder which tracks are available in each sim racing game? Wonder no more.

    Goals

    Create a simple website that includes details about sim racing games.

    The website should be static and built with Alpine.JS and TailwindCSS. Data should be consumed from JSON, easily done with Alpine.JS.

    The main goal is to gather track information, because tracks vary by game. Older games might have older layouts, and newer games might have up-to-date layouts. Some games include historical layouts, some are laser scanned. Many tracks are available as DLCs.

    Initially include official tracks from:

    • ACC
    • iRacing
    • PC2
    • LMU
    • Raceroom
    • Rennsport

    These games have a short list of tracks and DLCs.

    Resources

    The hardest part is collecting information about tracks in each game. Active games usually have information on their website or even on Steam. Older games might be on Fandom or a Wiki. Real track information can be extracted from Wikipedia or the track website.