Posts written by Oz Akan
What is Marconi?
Marconi is an open source message queue implementation that utilizes a RESTful HTTP interface to provide an asynchronous communications protocol, which is one of the main requirements in today’s scalable applications. Using a queue as a communication layer, the sender and receiver of the message do not need to simultaneously interact with the message queue. As a result, these can scale independently and be less prone to individual failures.
Marconi supports publisher-subscriber and producer-consumer patterns. In this post, I will focus on producer-consumer patterns, and, under the section "Python Way," I will give an example using the python requests library.
In the second article, we configured three environments: a
base environment will have very generic formulas, which we would like to apply to all servers we will ever create with Salt. A
marconi-base environment will have formulas that are identical in all Marconi environments. For example, the way we will install MongoDB isn't different in a production environment than a development environment so we will place MongoDB formulas in a
marconi-base environment. There is a little trick here, that I mentioned in the previous article; we will never use a
marconi-base environment but will use it in an overlay setup with the third environment,
marconi-preview-ord. Let's go over the folder structure to make this a little more clear.
In the first article we configured salt-master and created a Cloud Server. In this article we will start building up the Marconi environment and while doing so shape what our salt configuration will look like.
We have two goals in mind. First, we have to be capable of creating several Marconi environments with little effort. As an example, we should have servers under dev, test and production environments managed under one configuration. Taking it a step further, we may have these in different locations. So having the ability to managing multiple environments is essential. Second, we will try to build generic configurations (SLS Formulas) that we can use for different projects. For example, we could have a generic firewall formula that will set proper iptables rules on Linux servers based on the role and environment they are in.
When Henry Ford invented the assembly line at his automobile company he changed the world as we know it. It wasn’t the automobile itself that sparked that dramatic change; it was the mass production of the automobile that enabled people to go wherever they wanted whenever they wanted that created a world of possibilities. The automobile was not the final product; it was the great tool to build new products on top of it. And the ability to create a million copies of that great tool gave birth to the industrial age. Our story starts with cloud computing era when IT finally gets rid of the boundaries of physical environments but still finds itself incapable of delivering the "great tool" quickly enough to the people who are building new products on top of it. The great tools in this story are computers or better put, servers configured for specific purposes. In this series, we will explore Salt and automate an OpenStack Marconi environment. When we are done, with very little effort, we will be able to:
- Create new environments like production, development, test, etc. in different locations
- Create an unlimited number of Linux servers of different types
- Automatically adjust the environment when a component is changed
- Create a MongoDB primary-secondary replica set with desired number of secondaries in minutes
- Takes actions based on some metrics (like autoscale if average load is over five)
WARNING: this blog post contains information that is not up to date. Consult this guide for authoritative and up to date information.
Insurance can help to manage risks of relatively rare but expensive events that you will be responsible for covering. Still, insurance doesn't eliminate the risks of unlikely events from happening; instead it provides a mechanism to get out of that event with minimal loss.
If you swap the word "insurance" with "backup" in the paragraph above it still makes sense. With insurance, you would like to make the smallest investment but still be covered for any possible event. Cloud Backup does just that - no tapes, no rotation, no physical requirements. Just a few calls and with little effort you are covered.
Rackspace has a powerful, easy-to-use service called Cloud Backup which can back up Cloud Servers at file level. It supports encryption, compression and de-duplication, which are important for data security at rest and cost control. For more information, take a look at Cloud Backup:FAQs