Ansible Playbook for Wekan

Ansible Playbook for Wekan

My team is experimenting with using open-source tools deployed internally for Kanban cards.

One tool we are exploring is Wekan, formerly known as Libreboard.

I deployed a Wekan instance to a RHEL 7 virtual machine for our testing. For this deployment, I wrote a simple Ansible playbook with a few additional configuration files (nginx config, Node PM2 configuration), in case there is ever a need to re-deploy the instance.

You can find my playbook and associated files on Github: wekan-setup. The files are as follows:

  • purekan.yml—Ansible playbook
  • wekan.yml—Node PM2 configuration
  • wekan.conf—nginx proxy configuration

You’ll need to customize things slightly based on your domain name or if you are using a distribution other than RHEL.

Corporate Service Corps

Corporate Service Corps

I had never heard of IBM’s Corporate Service Corps until my friend David Wierbowski participated in one of IBM’s 2014 corporate service teams.

IBM’s corporate service program is one of the ways that IBM contributes back to the communities where it does business. From what I’ve seen, it is also a fantastic experience for the individuals involved, offering both professional and personal challenges and rewards.

Dave recounted and reflected on his experience before, during, and after his service on his CSC blog. I enjoyed reading about the corporate service program through his eyes.

Stopping all instances on your PureApplication System

If your PureApplication System is protected by an uninterruptible power supply (UPS), you likely want to automate a graceful and orderly system shutdown in case of a power loss. To do this, you might create a Linux or AIX virtual machine nearby or even within your PureApplication System, have it monitor for SNMP traps indicating the UPS has detected a power loss, and then trigger an orderly shutdown of both the deployed application instances in your system, as well as triggering the shutdown of the system itself.

Here is a simple PureApplication command-line script that will stop all application instances on a system. If you are running this within the system itself, you should remember to exclude your own deployment from the list of deployments being stopped, and stop it last. This script stops all deployments without regard to dependencies between deployments. You may need to modify it so that dependent deployments are stopped in a particular order.

Finally, this script uses a different method than calling stop() on virtual system and virtual application objects. The built-in stop() method waits for each instance to complete stopping before moving to the next. Instead, this script initiates the stop of all instances in parallel, and then waits for all instances to complete stopping.

# Collect all deployments
listOfVsysClassic = deployer.virtualsystems.list()
listOfVsysRegular = deployer.virtualsysteminstances.list()
listOfVApps = deployer.virtualapplicationinstances.list()

# Initiate stops for all deployments
for vsys in listOfVsysClassic :
  print "Stopping vsys classic: %s" % vsys.name
  vsys.stop() # vsys classic method does not wait
for vsys in listOfVsysRegular :
  print "Stopping vsys: %s" % vsys.deployment_name
  deployer.http.putJSON(vsys.uri, {"operation": "stop"})
for vapp in listOfVApps : # This includes shared services
  print "Stopping vapp: %s" % vapp.deployment_name
  deployer.http.putJSON(vapp.uri, {"operation": "stop"})

# Wait for all deployments to reach a non-transient state
print "Waiting for all instances to stop"
for vsys in listOfVsysClassic :
  vsys.refresh()
  vsys.waitFor()
for vsys in listOfVsysRegular :
  vsys.refresh()
  vsys.waitFor()
for vapp in listOfVApps :
  vapp.refresh()
  vapp.waitFor()

PureApplication 2.2

PureApplication 2.2

Last week, IBM announced the general availability of PureApplication System, Software, and Service version 2.2. There are a lot of exciting developments in this release.

As previously announced, there is now a beta offering of OpenStack Kilo on Intel-based systems.

There are a number of multi-system enhancements that I’m excited about. For example, we are raising the limit on the number of systems in a subdomain from two to four. We are also alleviating the problem of the proliferation of multi-system shared service deployments, by allowing you to link shared service deployments from one multi-system environment profile to another. We’ve also improved the workflow for managing multi-system certificate trust stores.

We’ve significantly enhanced the chargeback reporting capabilities for PureApplication System in version 2.2. And on top of this list of highlights, there are many additional minor enhancements and improvements.

I’m very proud to have had a small part in reaching this milestone. Congratulations to the rest of the PureApplication development team!

Over rock and under tree

Well, that was fast. In a matter of a few weeks, I made the jump from Knight Wazer to Royalty Wazer, after having driven a total of 4,665 miles. It is interesting to me that, during this period of two and a half weeks, the point value required to reach royalty did not change. It makes sense to me that this value may be recalculated less frequently, perhaps on a weekly or monthly basis, but I crossed both week and month boundaries without the point value being updated.

This indicates to me that the activity at the 1% mark for Waze members—at least in North Carolina—is stagnant, as the 1% bar is not moving. Thus, in North Carolina less than 1% of the total Waze membership is highly active.

Roads go ever ever on

Last November I joined the Waze traffic and navigation community. I’ve been using Waze since then for my daily commute and also used it for our family’s Thanksgiving trip. My commute time is 35 minutes in one direction compared to the national average of 25 minutes.

It is now mid-February, three months later, and I’m a little surprised at how rapidly I’ve been able to progress in ranking. Just today I received the Waze Knight status, which means that I am in the top 4% of users in my state, North Carolina.

Thus far I have driven only 3,472 miles with Waze. The majority of my Waze points come from driving miles, although I have achieved a fairly normal set of bonus points (for example, using Waze four days out of one week). That is not a lot of activity to reach the top 4%!

If I’d had to guess, I would have expected that somewhere in the neighborhood of 20% of Waze’s user base was fairly active. But from my experience, at least in North Carolina I would say that number must be less than 5% and could be much less than that. Now I’m very curious to see whether and how quickly I’m able to reach the top 1%.

PureApplication and hybrid cloud

hybrid-redbookIBM has published a new Redbook that discusses how you can build a hybrid cloud solution using PureApplication System, Software and Service.

I’m privileged to have served as a contributor to this Redbook, with a particular focus on the ways in which PureApplication’s multi-system management and deployment capabilities allow you to build cross-site and hybrid business solutions.

But even beyond multi-system deployment, the power of patterns combined with the variety of PureApplication offerings allows for a genuine “write once, run anywhere” model for applications.