Last week I introduced this topic, the pervasive problem of “comatose” servers in data centers, based upon an interesting recent eWeek article entitled “30 Percent of Servers Worldwide Sit Idle”, which in turn was based upon the research report by Stanford University in conjunction with the Anthesis Group. In my blog, I described the costs of this problem, ranging from the obvious (e.g. power and facilities) to the hidden (e.g. un-used software licenses). This week I’ll discuss why this happens and what you can do about this problem.
In my role in Cisco Services, I’m more interested in the challenges of technology adoption and deployment than I am in speeds and feeds, statistics and technology fads. I actively seek out case studies where technology goes wrong – admittedly most of these examples turn out to be issues around introducing and managing the technology, rather than the technology itself. So I have to admit, I was fascinated by a recent eWeek article (full details below) which discussed the huge proportion – the report uncovers evidence of up to 30%!! – of (physical) servers in enterprise data centers that are typically running doing nothing!! Yes – up to 30% – even in these days of virtualization!
Yes, even in your data center, it’s probably a safe bet to say that you have some servers that are not doing that much information processing today! In this part 1 of my blog, I’ll discuss the costs – obvious and hidden – of the idle server challenge. And next week I’ll discuss why this happens and what you could and indeed should do about it!
Lately I’ve been giving a lot of presentations about storage basics. I actually really enjoy it, because it makes me rethink some of the things that I took for granted, and it helps me understand some of the gaps in my own knowledge when questions arise.
When you think of how we do certain things for storage, such as choosing block-based (e.g., FC, FCoE, iSCSI), file-based (e.g., NFS, SMB), or object (e.g., Ceph, Swift, CDMI) storage platforms and protocols, it’s easy to ignore the why these types of storage affect our Data Center architectures and performance. Read More »
On behalf of the development team. I’m pleased to announce the 0.3.0 release of Microservices Infrastructure. In the weeks since 0.2, we’ve added a number of features and improvements.
The software can be downloaded at:
Documentation is located at:
What is it?
Microservices Infrastructure is software that launches servers and then configures them to support a wide range of applications – like continuous delivery or realtime data processing.
Today, enterprises need greater business agility and faster time-to-market for applications. That’s why, in many instances, they are building their own private clouds or adopting on-demand private cloud. Companies that are most suited to building their own private clouds are those that have deep engineering and IT leadership and need strong security and governance around applications and services.
Depending on the needs of the business and core competencies, other types of companies can benefit from a managed private cloud. For these companies, it’s not core to the business to be great at infrastructure, but it is crucial to be able to focus on the services offered on top of the infrastructure. These types of organizations may not have strict regulatory or data sovereignty requirements. Typically, they gain the most advantage from using managed private clouds.