Posts about technology and arts.
Some weeks ago I started learning SaltStack for a project at work. But I couldn’t find a good Docker image for that and I had to ask the Ops team for some VM’s. We are having a rainy weekend in Auckland, so I decided to have another look at the Jenkins SaltStack Plug-in.
But now since I was at home, I couldn’t use the VM’s that I had access to at work. So decided to look again at Docker or Vagrant images. After playing with a few images, I found bbinet/salt-master. It not only sets up a master, but also provides an easy way to enable the cherrypy API (necessary for the Jenkins plug-in).
This post describes the steps that I took to have a running Salt Master with the API enabled. First you need to create some directories and files to use with the image.
shell$ mkdir ~/master && cd ~/master shell$ mkdir -p config/master.d/ shell$ vim config/master.d/api.conf
The api.conf contains the SaltStack API configuration. You can change port, user and other settings if necessary. Just remember to add a credential in Jenkins for the plug-in.
# File: api.conf external_auth: pam: saltapiuser: - .* - '@runner' - '@wheel' - '@jobs' rest_cherrypy: port: 8000 host: 0.0.0.0 disable_ssl: True static: /opt/molten static_path: /assets app: /opt/molten/index.html app_path: /molten
The image also conveniently provides a script that is executed before the entry point (if provided). So we can also create a user for the API automatically when the image is created.
shell$ vim config/before-exec.sh
#!/bin/bash # File: before-exec.sh useradd saltapiuser echo -e "nosecret\nnosecret\n" | passwd saltapiuser exit 0
Also make the script executable.
chmod +x config/before-exec.sh
And finally start the container.
docker run --name salt-master -v $PWD/config:/config \ -p 4505:4505 -p 4506:4506 -p 443:443 -p 8000:8000 \ bbinet/salt-master
Once the container is running, you can go to http://localhost:8000 and log in as saltapiuser:nosecret, and also configure your plug-in in Jenkins.
I just had a two week vacation, and I tried to use my time to rest, play some music, and complete a geek todo-list.
The list included things that I used some time ago but wanted to refresh my memory, things that I already used but never spent time reading the manuals, and other things that I saw somewhere but never actually used in any project.
Here the complete list, with the items that were completed highlighted. Some links with pointers to what I used to study.
Going to have less spare time now for Open Source and learning the rest of the stuff on this list, but there’s always some books to read, and things to learn anyway right ¯\(ツ)/¯
Table of Contents
A co-worker asked me this week about how to deploy a WAR file to Tomcat with Jenkins. In my team we are currently maintaining and deploying about 10 Java web systems, but we have no consistent way of deploying the applications to Tomcat yet. In the past I used Ant, Maven, Cargo, Grunt, and Jenkins, so I decided to write this short post to show a few different ways it can be achieved, à la Perl’s TMTOWTDI motto.
At first you may be tempted to write your own script to deploy to Tomcat with some Shell, Perl, Python or Java. But I think I would choose this option only because either I needed some feature that is not available in the other options, or in order to call other tasks or debug some problem.
$ docker run -d -p 8888:8080 jeanblanchard/tomcat:8 $ git clone https://github.com/spring-projects/spring-petclinic.git && cd spring-petclinic && mvn package $ curl --upload-file target/petclinic.war "http://admin:admin@localhost:8888/manager/text/deploy?path=/spring-petclinic&update=true" OK - Deployed application at context path /spring-petclinic
afl is a fuzzer, an application that combines a series of algorithms in order to try invoking programs with several different input values. It then analyses the application execution flow given different test case scenarios. You can read more about fuzzing at this OWASP page, or in other blogs that I also used while learning about afl 1 2
At work we are using MapServer for serving WFS and WMS. And I am using it for the NZ OpenStreetMap maps too. MapServer is written in C++ and is normally exposed as a CGI script, so I thought it was worth learning about afl and trying it on MapServer, as in case it finds any interesting bug I can submit it to the MapServer project.