Whilst researching how to reconcile ITIL with DevOps I came across this interesting blog post from the IT Skeptic entitled “Kamu: a unified theory of IT management – reconciling DevOps and ITSM/ITIL”. This lead me to Jez Humble’s post on “On Antifragility in Systems and Organizational Architecture” referencing Nicholas Taleb’s book “Antifragile” and generally lead to a lot of intense cogitation on fragility versus robustness versus antifragility.
The IT Skeptic (Rob England) expands on his thoughts in this presentation which introduces this diagram below
However I struggled to mentally conceptualise the differences between the 3 points of the triangle until I came up with the following analogies (and please bear with me while I explain my thoughts behind them!):
- Fragile = Humpty Dumpty
- Robust = A medieval castle
- Anti-fragile = The Borg collective
“Fragile” systems are those (often legacy) systems that you really…
View original post 668 more words
At the OpenStack Operators meetup the question was asked about monitoring issues that are related to RabbitMQ. Lots of OpenStack components use a message broker and the most commonly used one among operators is RabbitMQ. For this post I’m going to concentrate on Nova and a couple of scenarios I’ve seen in production.
It’s important to understand the flow of messages amongst the various components and break things down into a couple of categories:
- Services which publish messages to queues (arrow pointing toward the queue in the diagram)
- Services which consume messages from queues (arrow pointing out from the queue in the diagram)
It’s also good to understand what actually happens when a message is consumed. In most cases, the consumer of the queue is writing to a database.
An example would be for an instance reboot, the nova-api publishes a message to a compute node’s queue. The compute service running…
View original post 413 more words
I think a bunch of folks have heard already that B.D.O.S.S. was working on a new Apache Kafka Client For Go. Go Kafka Client was open sourced last Friday. Today we are starting the release of Minotaur which is our lab environment for Apache Zookeeper, Apache Mesos, Apache Cassandra, Apache Kafka,Apache Hadoop and our new Go Kafka Client.
Ideas and goals behind the Go Kafka Client:
1) Partition Ownership
View original post 382 more words
For the past several months, it seemed like Docker was on its way to becoming the de-facto standard for container technology, the hottest thing in cloud computing in 2014. Then along came CoreOS, which dropped a bomb (or in this case, a rocket) on Monday, kicking off what could become a container-standardization war between the two entities.
CoreOS’s announcement that it built a container engine that can potentially compete with Docker’s container technology caused quite a commotion within the tech community on Monday. Docker has enjoyed a swift ride to prominence this past year with its container skills catching on with some of the biggest names in the industry, such as Google, Amazon and Microsoft. CoreOS’s decision to detail its own container plans in light of Docker’s momentum is an aggressive move, one that highlights CoreOS’s belief that it can capitalize on Docker’s perceived weaknesses.
[company]CoreOS[/company] would like you to…
View original post 1,034 more words