Description
One of the PuppetLabs guys is trying to enforce best practices on administering Puppet modules, by using base modules and build services and roles on top of them. That way we can re-use external / third-party modules from forge.puppetlabs.com, ideally without touching them at all. He names that "the Lego approach". Full article.
The goal of this Hack Week project is to gather a few third-party modules, and test them for SLE and openSUSE. That way we can have a number of base modules, that are ready for constructing services and roles on top of them. Most of the good modules are written by PuppetLabs or their operations team. The problem is that most of the modules on forge have minimal to no openSUSE support, due to the fact that PuppetLabs operations are using Debian in their boxes. The good part though is that PuppetLabs is very cooperative in accepting patches, so ideally we will need to work on those modules and submit our patches upstream.
List of Puppet modules for hacking:
- https://github.com/puppetlabs-operations/puppet-puppet: Module to deploy and manage the Puppet Master and the Puppet Agents. It should (in theory) support various installation scenarios for the master: standalone service, apache+passenger, nginx+unicorn.
- https://github.com/puppetlabs-operations/puppet-unicorn
- https://github.com/puppetlabs-operations/puppet-nginx
- (More to be added)
Related material
This project is part of:
Hack Week 10
Activity
Comments
Be the first to comment!
Similar Projects
Recipes catalog and calculator in Rails 8 by gfilippetti
My wife needs a website to catalog and sell the products of her upcoming bakery, and I need to learn and practice modern Rails. So I'm using this Hack Week to build a modern store using the latest Ruby on Rails best practices, ideally up to the deployment.
TO DO
- Index page
- Product page
- Admin area -- Supplies calculator based on orders -- Orders notification
- Authentication
- Payment
- Deployment
Day 1
As my Rails knowledge was pretty outdated and I had 0 experience with Turbo (wich I want to use in the app), I started following a turbo-rails course. I completed 5 of 11 chapters.
Day 2
Continued the course until chapter 8 and added live updates & an empty state to the app. I should finish the course on day 3 and start my own project with the knowledge from it.
Hackweek 24
For this Hackweek I'll continue this project, focusing on a Catalog/Calculator for my wife's recipes so she can use for her Café.
Day 1
Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse
Description
"LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102
However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.
The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.
Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.
Goals
Goals of this project:
- Modify the RSpec tests and run them against a real LDAP server
- Replace the
net-ldaprubygem with theruby-ldaprubygem
Achieving the above mentioned goals will:
- Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
- Make a step towards officially supporting LDAP in OBS.
Resources