Go (golang) plugin in Citellus

I wanted to practice a bit Go programing, so I divided that task in two parts, one, adding a golang extension for Citellus and a sample, but working plugin using it. If interested in the code it’s available at the review at https://review.gerrithub.io/c/citellusorg/citellus/+/495622. The final sample code for it has been: // Author: Pablo Iranzo Gómez ([email protected]) // Header for citellus metadata // long_name: Report detected number of CPU's // description: List the processors detected in the system // priority: 200 package main import ( "bufio" "io" "os" "runtime" "strconv" "strings" ) func main() { var OKAY, _ = strconv....

June 14, 2020 · 2 min · Pablo Iranzo Gómez

Katacoda scenario redirection

After my post about Katacoda, I did split my initial scenarios into ‘organizations’. One of them, is in progress to get contributed upstream to KubeVirt project Katacoda (still getting some reviews to land on final repo), and the other is under Citellus organization. As the goal was not to lose visits using the prior links, I contacted the team behind Katacoda Support (thanks a lot Ben!!) and the requirements to get a ‘redirect’ in place is to:...

July 31, 2019 · 1 min · Pablo Iranzo Gómez

Katacoda scenario creation

After some time checking the scenarios at https://learn.openshift.com, I decided to give it a try. With the help of Mario Vázquez, author of Getting Started with Kubefed, I did create two scenarios: How to use Citellus on Citellus: Troubleshooting automation KubeVirt on a ‘browser-based’ approach for MiniKube setup for validating KubeVirt: Kubernetes with VM Virtualization (versus the regular containers). You can check how them can be created by looking at their code at: Katacoda Scenarios or the ‘playable’ version at https://www....

June 11, 2019 · 1 min · Pablo Iranzo Gómez

Contributing to OSP upstream a.k.a. Peer Review

Introduction In the article “Contributing to OpenStack” we did cover on how to prepare accounts and prepare your changes for submission upstream (and even how to find low hanging fruits to start contributing). Here, we’ll cover what happens behind the scene to get change published. Upstream workflow Peer review Upstream contributions to OSP and other projects are based on Peer Review, that means that once a new set of code has been submitted, several steps for validation are required/happen before having it implemented....

October 16, 2018 · 6 min · Pablo Iranzo Gómez

Peru for syncing specific git repository files

Peru a repository synchronizer Some projects upstream bind together lot of files which might not be of interest, but still the convenience of a git pull to get latest updates, makes you to download the whole repository for just a bunch of files or folders. For example, this website uses Pelican to generate the webpages out of markdown files. Pelican does have a rich set of plugins but all of them are in the same folder in the git checkout....

September 25, 2018 · 2 min · Pablo Iranzo Gómez
This blog is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.