Saturday, November 1, 2014

I have a lenovo Thinkpad T540p. This laptop has a Samsung 256GB SSD drive. This drive ran out of space long ago. The good thing is, you can add a disk to the T540p. I went to lenovo's site and ordered:

Friday, September 12, 2014

So I forked the Google Kubernetes project. Then I created a fedora_gs_guide branch. I made some changes to the getting started guide and then I submitted a pull request. I asked someone to review it and they had a couple of changes. So, I make the changes, and commit. Now when I look at the PR, I see multiple commits. I think it's best practice to squash all those commits into one if possible. So, how do you do that. Well, here's how I did it. I'm sure there are other ways to do this, probably a lot more efficiently (comments welcome). But, it worked. These are my notes from the process.

I needed to make sure my master and fedora_gs_guide branch were clean and rebased to upstream master.

These are my notes on how to get started evaluating a Fedora / Docker / kubernetes environment. I'm going to start with two hosts. Both will run Fedora rawhide. The goal is to stand up both hosts with kubernetes / Docker and use kubernetes to orchestrate the deployment of a couple of simple applications. Derek Carr has already put together a great tutorial on getting a kubernetes environment up using vagrant. However, that process is quite automated and I need to set it all up from scratch.

Install Fedora rawhide using the instructions from here. I just downloaded the boot.iso file and used KVM to deploy the Fedora rawhide hosts. My hosts names are: fed{1,2}.

The kubernetes package provides four services: apiserver, controller, kubelet, proxy. These services are managed by systemd unit files. We will break the services up between the hosts. The first host, fed1, will be the kubernetes master. This host will run the apiserver and controller. The remaining host, fed2 will be minions and run kubelet, proxy and docker.

This is all changing rapidly, so if you walk through this and see any errors or something that needs to be updated, please let me know via comments below.

Thursday, July 3, 2014

I have been following the progress of Jason and his 180 day coding challenge. I'm going to try something similar except that I'm going to work on go. The only problem is, that I can't start for 10 days because of some PTO that I have to take starting tomorrow. Having said that, I'm throwing down the gauntlet now and when I get back, I'll post everyday on my progress. A few rules, per Jason's post above - yes, I did steal these directly from him with one change on the first rule:

Every business day for a minimum of 30 minutes, I must write code or learn about the tool-chain used in the development process. Documentation about the code does not count.

The resulting code must be useful, or it should be code that points
towards something that eventually will be. No tweaking indentation, no
code re-formatting, and if at all possible no re-factoring. (All these
things are permitted, but not as the exclusive work of the day.)
Tutorials and working through code examples as a means to learn are
allowed.

All code must be written before midnight, and after 6AM.

The code must be Open Source and posted on Github.

My current status:

I have signed up for the Pluralsight on-line go class here. So far, I have made it to the "Variables, Types and Pointers" section. We just haven't written much code yet. So I won't count that.

In addition, I have downloaded and installed IntelliJ IDEA 13.1.3 IDE, community edition. The on-line class they use this so I figured I'd give it a try. It was relatively easy to set up, I should write a quick post on what I did for reference. I'm also going to evaluate the vim plug-ins out there for writing go more efficiently.

Tuesday, May 13, 2014

Today I moved my Fedora-Dockerfiles repo to the Fedora Cloud SIG github repo. All forks, stars, wiki pages, etc... were maintained during the transfer. This repo will still be the source for the fedora-dockerfiles package. The new location is at:

This makes it a bit more official. I will stay involved with the maintenance of the Fedora Dockerfiles moving forward. Also, please have a look at some of the work going on in the Fedora Cloud SIG here. There are always opportunities to help out. Exciting times!

Friday, May 9, 2014

Here's a great example of building out a Hadoop environment using Docker on Fedora. The Hadoop environment is distributed to 3 different containers - all on one host at the moment. It's a great way to get started learning both Docker and Hadoop.

The first lab had 80 students and went very well. Lots of people were able to walk through the entire lab and finish up. The second lab had 160 students and it also went well. It was an intro to Docker on Red Hat Enterprise Linux 7 beta and had two sections: 1. Intro to Docker 2. Linking containers. Once again, almost all students were able to finish both sections and get it all done.

Friday, March 28, 2014

On of my colleagues here showed me a great trick that I had to document immediately. The question of the day was "How do I access a container without having SSH installed?" It turns out, it's easier than you might think. Let's take a look at the process.

The first thing that you need to do is get the PID (Process ID) of the container that you want to enter. So, grab the <Container ID> and inspect it.

Monday, March 3, 2014

In just a few simple steps, you can have an instance of the earthquake terminal based twitter client up and running in a Docker container. Maciej was kind enough to contribute this gem - no pun intended. It's actually a really cool project and just one of the many apps that can be dockerized. Check out his webpage here and give him a follow.

Sunday, March 2, 2014

Please check out and test fedora-dockerfiles. This package provides a community contributed set of examples that can assist in learning about Docker containers. Use these examples to stand up test environments using the Docker container engine. The following Dockerfiles are included:

Friday, February 14, 2014

In just a few simple steps, you can have an instance of Hadoop up and running in a Docker container. This was tested with Hadoop 2.2 on Docker 0.7.6 on a Fedora 20 host. This article will also take a minute to explain how to use volumes as well. You may also want to view this in depth blog post by Michael Crosby.

Friday, January 24, 2014

Labs are a lot of fun. They give us a great opportunity to interact with customers and show of our new products. We had a lab session last year and it was wait listed. Over 80 attendees showed up and were able to complete our session. I'm really looking forward to this year as well. See you there!

Thanks to the node.js Fedora Dockerfile contribution from Jay Clark. In just a few simple steps, you can have an instance of node.js up and running in a Docker container.
Here's how you run it. This was tested on Docker 0.7.2

Wednesday, January 22, 2014

I had a great time presenting at the Austin Cloud meeting last night. There was a great turnout, probably ~ 125 or so people showed up.

The agenda consisted of:

• James Turnbull (skype-in), Intro to Docker and The Docker Book
• Scott Collier to talk about docker files in fedora.
• Ian Richardson to talk about Docker+Rundeck.
• Nars Tadepali to talk about Docker usecases at Actian.
• Aater Suleman to talk about Docker usecases at Flux7.
• Paul Czarkowski to talk about Deis.

Tuesday, January 14, 2014

OK, so today the fedora-dockerfiles package was created: fedora-dockerfiles. It should go through the process and be released in a few days to a week. The fedora-dockerfiles package provides examples of dockerfiles to get people up and running quickly. It's trivial code, but it's still my first time maintaining upstream code for a package. Here are some things that I see I need to start learning / testing:

Automated way to ensure the dockerfiles are working with each new release

etc... I'm sure I've missed something that will pop up eventually

I'm looking forward to being an active maintainer of these dockerfiles and I'll try to stay on top of it. The good thing is, if I run into any problems, I'm only an IRC chat away from having them resolved as anyone I've ever worked with that's involved in the Fedora Project has been happy to help.