As many of you know, OpenStack is a fully distributed system. As such, it keeps its services (nova, glance, cinder, keystone, etc ) as decoupled as possible and tries to stick to most of the distribution paradigms, deployments strategies and architectures. For example, one of the main tenets throughout OpenStack is that every module should be using Shared Nothing Architecture (SNA) which states. that each node should be independent and self-sufficient. In other words, all nodes in a SNA are completely isolated from each other in terms of space and memory.
There are other distribution principles that are part of OpenStack’s tenets, however, this post is not about what principles OpenStack as a whole tries to follow, but rather on how OpenStack sticks together such a heavily distributed architecture and makes it work as one. The first thing we need to do is evaluate some of the integration methods that exist out there and how they’re being used within OpenStack. Before we get there, let me explain what an integration method is.
Continue reading “OpenStack Services Integration: Pros and Cons”
By, Gordon Haff, Cloud Evangelist, Red Hat
January 27, 2014
In spite of its considerable momentum, there are still skeptics about whether OpenStack will ultimately succeed. My colleague Bryan Che tackled some of that skepticism in a blog post late last year and I’m not going to rehash his arguments here. Rather, I’m going to make some observations about how OpenStack is paralleling and will likely continue to parallel the adoption of another open source project that I think we can all agree has become popular and successful—namely Linux.
1. Part and parcel of a new approach to computing
Linux came about at a time when computing was changing. It had become distributed and the rise of the Web was leading to new functions and new requirements. Much of Linux’ early-on growth came from powering new Internet infrastructure. It was from that beachhead that Linux branched out into more traditional enterprise operating system roles. Similarly, OpenStack is part of the cloud computing wave which is characterized by new levels of standardization and automation combined with an on-demand and self-service approach to delivering computing resources to users.
Continue reading “7 Ways in which OpenStack Adoption Parallels Linux”
By, Steve Gordon, Product Manager, Red Hat
January 23, 2014
This week heralds a refresh of Red Hat’s cloud portfolio offerings, including Red Hat Cloud Infrastructure 4.0, Red Hat Enterprise Linux OpenStack Platform 4.0, and the latest release of Red Hat’s traditional data center virtualization management platform, Red Hat Enterprise Virtualization 3.3.
We’ve put a lot of effort into our long-term cloud product strategy and the updates this week show the beginning of those efforts coming together. With this refresh, it’s clear that integration and management is the key theme behind the marketing launch activities. However, delivering real, tangible, and deployable value to our customers through Red Hat infrastructure software, is the key to success for us and this update provides you (us) the first step.
So why is integration so important in your data center? And why integrate with OpenStack? The answer lies within your own existing infrastructure, as well as your long-term plans. No, I don’t have magical powers to see your datacenter or your plans, but statistically-speaking, I can see just fine.
Continue reading “The Importance of Integrating Datacenter Infrastructure”
By, Gordon Haff, Cloud Evangelist, Red Hat
January 7, 2014
Cloud infrastructure and cloud management. As an industry, we conflate these two things far too often.
This is understandable up to a point. Cloud computing architectures are relatively new and new architectural approaches often involve figuring out how functions are best partitioned and how they relate to each other. The process tends to be pragmatic; that’s how the networking stack first developed. That terminology is often morphing and inconsistently applied (innocently or otherwise) doesn’t help matters.
The overall building blocks of the private and hybrid cloud stack have now crystallized to a significant degree. The boundaries of these blocks aren’t hard-edged of course; there’s always overlap in the management space given that basic functions tend to come built-in even if they’re superseded at scale or for more complex requirements. But we’re at a point where we can describe the relationship of a cloud platform such as OpenStack to cloud management platforms (CMP)s like CloudForms that shouldn’t be too controversial.
By, Chuck Dubuque, Director Product Marketing, Red Hat
December 18, 2013
Returning from OpenStack Summit in Hong Kong, I had some time on the fourteen-hour flight to think about Red Hat’s accomplishments within the OpenStack community, and more importantly, why they should matter to customers in the enterprise software space.
While I am gratified that Red Hat was again the top corporate contributor to the OpenStack Havana release, for me it goes beyond just the marketing value of being able to make that statement. It goes to the heart of the value of a subscription to our Red Hat Enterprise Linux OpenStack Platform, and the unique characteristics of open source projects versus commercial products.
In my previous blog post, I have shared the vision of Disaster Recovery as a Service for OpenStack (DraaS) as an umbrella topic that describes what needs to be done to protect workloads running in an OpenStack cloud from a large scale disaster.
Last week we shared this vision in several sessions at the OpenStack summit. While OpenStack attendees were dealing with infrastructure Disaster Recovery topics in Hong Kong, the strongest tropical cyclone in recorded history “Typhoon Haiyan” also known as Typhoon Yolanda, devastated multiple coastal cities in the Philippines and took the lives of tens of thousands of people with millions evacuated. The storm destroyed complete cities, villages, airports, roads, power and communications infrastructures.
If there’s one thing that history has not only taught us, but also keeps on teaching us every year, is that catastrophic events do happen and that if we don’t invest in preventative measures now, we will pay a hefty price later.
Putting the PaaS in OpenStack (Platform as a Service)
For OpenShifters and PaaS aficionados in general, the Summit was all about cross community collaboration. As a PaaS, OpenShift touches on a lot of different OpenStack projects and related communities: Heat, Neutron, Nova, Docker, and now Solum to name a few. It’s important that we not only understand these projects, but participate actively in their design and development process.
As the OpenShift Origin Community Manager, and a huge fan of OpenStack, I was thrilled to get to attend the Hong Kong Summit, to chair the “Apps on OpenStack” track, participate in a panel on Why Enterprise Developers Should Care about OpenStack with such industry luminaries as Lew Tucker (Cisco), Chris Ferris (IBM), & Adrian Otto (Rackspace) and then moderate the closing panel on PaaS with participation from OpenShift, Docker, & Solum communities.
The OpenStack community gathered in Hong Kong in the first week of November to define the roadmap for the upcoming Icehouse release cycle and reflect on Havana, the release that forms the basis of the upcoming Red Hat Enterprise Linux OpenStack Platform 4.0.
This was the first time the biannual OpenStack summit had been held outside of North America but was still the largest ever with over 3500 stackers in attendance. The OpenStack Foundation rose to the challenge, organizing yet another exemplary event. Here at Red Hat, we’ve spent some time gathering up a grab bag of our personal highlights for the week.
OpenStack is on the verge of greatness
For fellow Stackers, this statement is obviously opinionated. But for those new to or in the early stages of exploring OpenStack, let us give you an objective view, a teaser if you will as to why we feel this statement is true.
Some interesting developments are taking place in the community. These developments are focused on the ability to deploy and manage OpenStack. The quick summary here is that as these developments mature — they will provide the leverage needed to accelerate the adoption of OpenStack by orders of magnitude.
In a time where the rules of Enterprise IT are constantly changing and every day there seems to be a new app born in the cloud, we must not forget to ask ourselves what are the challenges we face with these changes and rapid app development. What do we need to do to secure the horizon? What technology bridges are still waiting to be built in order to get us where we want to be in term of service level and securing cloud workload availability.