RHEL Atomic Documentation - Get Started

Lots of good stuff to get everyone started.  Lots of options to get started.

Getting Started with Atomic:

https://access.redhat.com/articles/881893

Atomic on RHEV:

https://access.redhat.com/articles/rhel-atomic-install-rhev

Atomic on AWS:

https://access.redhat.com/articles/rhel-atomic-install-aws

Out of Space... Add a disk!

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:

• ThinkPad 9.5mm SATA Hard Drive Bay Adapter IV
• ThinkPad 500GB 7200rpm 7mm SATA3 Hard Drive 

After installing the drive, I had to figure out how to carve up the new space.  There are probably many ways to do this, but I knew I wanted to:

• Add more space to the /dev/fedora/root LV.
• Keep the new, slower disk in a separate VG.  I didn't want any LV's to span these two disks.

Simple git rebase example

Situation:

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.

Make sure I'm on my local master.

$ git checkout master

Getting Started with Kubernetes / Docker on Fedora

EDIT 9/16/2014 ***********************

I have taken these instructions and put them on the kubernetes github repo:

Kubernetes Gitub

End EDIT ******************


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.

So let's get started.

Getting Started with go

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:

1. 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.
2. 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.
3. All code must be written before midnight, and after 6AM.
4. 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.


So, When I get back I plan on kicking this off full steam ahead.

Quick VIM Macro Reference

Pulled from: Here

qd	start recording to register d
...	your complex series of commands
q	stop recording
@d	execute your macro
@@	execute your macro again

Moving Fedora Dockerfiles - It's Official!

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:

https://github.com/fedora-cloud/Fedora-Dockerfiles

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!

Excellent usage of Fedora Dockerfiles to build out a Hadoop Environment

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.

Building Images:
http://rrati.github.io/blog/2014/05/06/apache-hadoop-plus-docker-plus-fedora-building-images/

Running Images:
http://rrati.github.io/blog/2014/05/07/apache-hadoop-plus-docker-plus-fedora-running-images/

Why it Works:
http://rrati.github.io/blog/2014/05/08/apache-hadoop-plus-docker-plus-fedora-why-it-works/

Issues / Limitations:
http://rrati.github.io/blog/2014/05/09/apache-hadoop-plus-docker-plus-fedora-issues-and-limitations/

New fedora-dockerfiles Package is out

Just this week the new fedora-dockerfiles package was released. Check out the examples that are provided.


$ repoquery --list fedora-dockerfiles | grep Dockerfile
/usr/share/fedora-dockerfiles/apache/Dockerfile
/usr/share/fedora-dockerfiles/bind/Dockerfile
/usr/share/fedora-dockerfiles/couchdb/Dockerfile
/usr/share/fedora-dockerfiles/earthquake/Dockerfile
/usr/share/fedora-dockerfiles/firefox/Dockerfile
/usr/share/fedora-dockerfiles/hadoop/single_container/Dockerfile
/usr/share/fedora-dockerfiles/lighttpd/Dockerfile
/usr/share/fedora-dockerfiles/memcached/Dockerfile
/usr/share/fedora-dockerfiles/mongodb/Dockerfile
/usr/share/fedora-dockerfiles/mysql/Dockerfile

Red Hat Summit Labs Released

I had a great time at Red Hat summit this year in San Francisco.  Here are the labs that I worked on.

1. Deploying OpenShift Enterprise on Red Hat Enterprise Linux Openstack Platform via Heat

Specifically:

Github Master Doc

2. Containers & resource management in Red Hat Enterprise Linux 7 beta

Specifically:

Github Master Doc

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.