When all you have is a hammer.....

Introducing Ballista


Some time ago I created a few tools and a library to interface with the Satellite 6 installation at a client and made some posts about that.

While these tools got some use, we found that what we really wanted was a tool that was easily extended and consistent in its use to manipulate our Satellite 6/Katello installations. So, together with my colleague Joey Loman I set out to create a comprehensive tool and provide an infrastructure for future functionality and supplement the existing hammer-cli interface.

You can check it out at  https://github.com/RedHatSatellite/ballista

Comments

Post a Comment

Popular posts from this blog

Runing Saltstack in multi-master

Recently I ran into some problems when trying to use multiple saltmasters in combination with using the mine and thought I'd share my experiences. Background   Like puppet   The salt mine can be compared to the PuppetDB ; it's a place to store stuff like (custom) facts for use on other nodes/instances. The classic use-case for this is a monitoring setup like Nagios that need to be configured for each additional deployed service/instance with the particular info of that service/instance. So let's say you deploy a new MySQL instance and automatically slave it to an existing cluster, you want the ip address, database name and maybe some other stuff to be configured on the monitoring server. Puppet does this by something called " exported resources " which basically sends data to a central location (the PuppetDB) which can then be collected by other machines when puppet runs there. But different   Where Puppet uses a database (PostgreSQL by default)
Read more

Recursively update Composite Content Views in Satellite 6/Katello

The basic idea Satellite 6 (and Katello for that matter) have a new way of dealing with content, whether it being puppet modules, rpm's or docker images. Below I will focus on rpm's, which I think will be the use case for most people. A content view can contain one or more rpm repository's at a specific point in time but can consist of multiple versions. So let's say I create a content view named RHEL7_BASE on Monday containing 2 repositories I just synced:  rhel7_server and rhel7_epel.  Version 1 of that content view points to the packages as they are on that Monday. Now the next Friday I do a sync of my repositories so I get the latest versions and patches and whatnot, but note that version 1 of my RHEL7_BASE content view is unchanged, and any servers that are using this version will not have access to the new packages. In order to make these new packages available, I need to publish a new version of the view and promote this version to the environment that con
Read more

First!

Well, I finally bit the bullet and started a blog. In here I will try to share some problems and solutions I encountered/devised in my daily dealings with mainly Linux as a DevOps Linux Engineer.
Read more