UNIX and Linux System Administration Handbook. Shell differences. Bit Calculator. Deploying Overnight. Are you still doing deployments at 3:00am?
If you are, you should have taken a look at Brian Crescimanno's post: "Why are you still deploying overnight? " Whatever you call the process of turning your development codebase into a live, production application, I sincerely hope you’re not living in the Stone Age and doing it in the middle of the night under the guise of avoiding customer impact. Unfortunately, if my past experiences, and the experiences of many I’ve spoken to, are the norm, you very likely are.
If your strategy to avoid customer interruption is based solely on trying to avoid your customers, you’re setting yourself up for even more headaches and long-term failure. --Brian Crescimanno Brian asserts that if you're doing these overnight deployments to avoid your customers during the initial release, then it's probably indicates that one or more things are broken in your process.
Problem 1: You presume there will be problems that impact availability. Source - Source - Dpkg-query. Gzip vs. Bzip2 vs. LZMA. 2005-05-31 Lasse Collin How the test files were selected I was especially interested how well LZMA compression would fit in binary package management of GNU/*/Linux distributions distributing source code of free software In both uses the files are compressed on one computer and decompressed many times by users around the world.
In practice the most important factors are: compressed size (faster to download; more packages fit into one CD or DVD) time required in decompression (fast installation is nice) memory requirements for decompression (should the user want to use the file on e.g. an old i486 with 8 MB RAM) common format that everyone knows how to uncompress/install Less important: Despite the many common factors, the contents of binary packages and source tarballs are quite different. Test conditions Tests were run on a laptop: AMD mobile Athlon XP2400+ 512 MB RAM Linux 2.6.12-rc4 (preempt, 4k stacks, regparm) gzip 1.3.3, bzip2 1.0.3, LZMA SDK 4.17 The tables of the test results Conclusions. DevOps. DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) operations professionals. DevOps is a response to the interdependence of software development and IT operations.
It aims to help an organization rapidly produce software products and services. Companies with very frequent releases may require a DevOps awareness or orientation program. What Is DevOps? DevOps is a term for a group of concepts that, while not all new, have catalyzed into a movement and are rapidly spreading throughout the technical community.
Like any new and popular term, people have somewhat confused and sometimes contradictory impressions of what it is. Here’s my take on how DevOps can be usefully defined; I propose this definition as a standard framework to more clearly discuss the various issues DevOps covers. Like “Quality” or “Agile,” DevOps is a large enough concept that it requires some nuance to fully understand. Planet DevOps. PaaS (1/3) Welcome to the first in a series of articles that will dive into Open Source Software (OSS) available for cloud computing.
In this post, I’m going to focus this series on a particular OSS Platform as a Service (PaaS) called CloudFoundry. VMware initiated this product with wide OSS industry support. By far this PaaS offering is one of the most open, but also provides some of the widest support of any PaaS product on the market. CloudFoundry provides many technology frameworks to build with, while preventing lock-in to any single infrastructure platform, hardware provider or vendor. What Does a PaaS Do For Your Software Development Efforts? Traditional Highly Coupled Applications Most developers have seen this traditional application architecture.
Highly Coupled Environments Of these highly coupled application architectures, a software team usually sets up an environment that mimics the servers and tools they need. Alright? CloudFoundry provides support for many platform frameworks. PaaS (2/3) Welcome to Part 2 of my series on Removing the OS Barrier with PaaS.
In Part 1, I covered the Platform as a Service (PaaS) product based on Open Source Software (OSS) Cloud Foundry and the .NET fork called Iron Foundry. In this entry I want to dive into some of the various parts, configuration, and setup of these products. Running with Cloud Foundry The easiest way to get up and running with Cloud Foundry is to use one of the existing services that use Cloud Foundry such as AppFog or CloudFoundry.com.
But I’m not going to take the easy route. Instead I’m going to dive into getting some real instances up and running. Another thing to be aware of is the difference in Cloud Foundry sites. Getting the Ops in DevOps Unless you want to go the completely manual path, the first thing you’ll need to do is sign up for an account. CloudFoundry Manual Setup First you’ll need to get an Ubuntu 10.04.2 Server 64 bit OS image. PaaS (3/3) Welcome to a double feature blog entry for Part 3.
I’ve gotten a lot of feedback for Part 1 and Part 2 of this series. Because of the number of emails, comments, Tweets and other messages, there is an apparent need to add more context to PaaS, the NoOps/AppOps/DevOps thought, and how Cloud Foundry is stepping up to make this future happen.