What helps make up 21st century data centers? In my last article, I focused on the automation aspect of the modern-day data center. My main point was that there is no right or wrong answer when it comes to choosing which automation engine to use in your environment. There are plenty of options available, and you should make your decision based on which solution makes the most sense for your environment and the systems that are running on it. You should also take advantage of other automation tools or engines that may be provided as part of another solution. Native functionality that is vendor-provided is a gift that should be opened and taken advantage of. Continue reading Tools of the 21st Century Data Centers
I was at the Santa Clara Convention Center, next to the beautiful brand-new San Francisco 49ers stadium, this week to listen to two days of discussions about continuous delivery and Jenkins. Keynote speakers were Kohsuke Kawaguchi, creator of Jenkins and CTO at CloudBees, and Gene Kim, coauthor of The Phoenix Project and well-known speaker on DevOps. Continue reading Recap of CloudBees Jenkins User Conference
I recently spent a fruitless afternoon on the public PaaS version of Cloud Foundry. In this post, I document an equally fruitless afternoon spent on Red Hat’s OpenShift. It think it is fair to say that OpenShift has some advantages over Cloud Foundry for public PaaS. OpenShift feels more comfortable, its integration of a build server introduces a lot of flexibility into its deployment, it makes it easier to know what is going on, and it seems to have more documentation and more discussion on the forums. However, once you veer away from the standard use case, it doesn’t work terribly well. Ultimately, I failed to get it to do what I wanted, but maybe it was just too hard.
I plan to spend an afternoon getting an ISV application to run on the public PaaS version of OpenShift—to allow direct comparison with a fruitless afternoon spent on the public PaaS version of Cloud Foundry. In this post, I explain the radical difference in approaches I am taking in the two environments to deal with real-world issues in the application lifecycle.