Software-defined storage (SDS) has usually meant storage that augments, optimizes, aggregates, and presents some form of cloud gateway. It is storage manipulated by an automation with an orchestration layer that ties differing data functions together. The ultimate in automation and orchestration for storage is the inclusion of Docker. Docker, or any container technology, needs storage—persistent storage. How storage is presented to Docker is unimportant to Docker. It is, however, important to the storage team. SDS is about making storage simpler by reusing, improving, or automating delivery. How does your storage fit with Docker?
SDDC & Hybrid Cloud
Cloud computing has evolved from focusing only on how to construct, secure, manage, monitor, and utilize IaaS, PaaS, and SaaS clouds. As the paradigm matures, it is moving from a pure resource management paradigm to a data and resource management paradigm. (Read More)
SDDC is the next evolution in on-site data center technology. It has taken the knowledge gained from the server virtualization revolution and blended it with software-defined storage and networking to create a data center defined and managed by software running on invisible hardware.
Hybrid Cloud covers the technologies and operational processes, both technical and business, for deploying, consuming, and utilizing this paradigm.
Major areas of focus include barriers to adoption; progress on the part of vendors in removing those barriers; where the lines of responsibility are drawn between the cloud vendor and the customer for IaaS, PaaS, SaaS, and hybrid clouds; and management tools that are essential to deploying and managing the cloud, ensuring its security and the performance of applications.
On the March 9, 2016, Virtualization and Cloud Security Podcast, we spoke with Sridhar Karnam, director of product marketing for Arctic Wolf, a Security Operations Center (SOC) as a Service provider. In our ongoing series on scale within IT security, a SOC is the next logical stop. The scale of data in today’s environments far exceeds people’s ability to view the data, make sense of it, and say there is a problem in a timely fashion. For this, we need automation, but we also need human intelligence!
Whenever AWS has an outage, it makes the news. In fact, AWS said the recent issue wasn’t even an outage, and it still made the news. Issues with S3 returning a lot of errors in the US-East-1 region caused application problems for a few hours. Personally, it affected my morning routine. I start the day reading blog posts using NewsBlur. NewsBlur wouldn’t show me any blogs. Instead, it reported server errors caused by this S3 issue, so my usual source of news couldn’t tell me that there was news about an AWS S3 issue. Before we start talking about how unreliable the cloud is, let us ask who among us has private infrastructure that is without fault? While cloud service outages make the headlines, on-premises outages happen all the time, too. Also, who cares if your application isn’t available for a few hours every couple of years? Not every application needs 100% uptime. It may be the right business decision to accept an application outage when there is an infrastructure outage.
We have all heard those words from the great and wise when we were starting out in our IT journey, the intimation being that it is a simple process—so simple that even a child can do it. In fact, I bet you can hear yourself saying that exact statement, maybe regarding a different service: “It’s OK—you just configure an iSCSI VMkernel port, and you’re good to go.” I know I have been guilty of saying this as an off-the-cuff comment to imply that something is simple, and it does not need my input. I’d be thinking, “You should be able to do this yourself; why are you bothering me with this?” I know you do not mean it like that. In your mind, you feel that you are empowering your staff to just get on with it. You know that they can do the work, and you do not want to belittle your colleagues, embarrassing them by aiding them in completing such a simple process.
Well, today I was on the receiving end of this statement, and do you know what? There is no such thing as a simple process. If you do not understand how to do a process, all things are difficult. Cast your mind back to when your child or your younger sibling was learning to tie their laces or put their shoes on the correct feet.
The recent Amazon Web Services Simple Storage Service (S3) outage has taught us quite a bit about fragile cloud architectures. While many cloud providers will make hay during the next few weeks, current cloud architectures are fragile. Modern hybrid cloud architectures are fragile. We need to learn from this outage to design better systems: ones that are not fragile, ones that can recover from an outage. Fragile cloud is not a naysayer: it is a chance to do better! What can we do better?