You are probably thinking that CITEIS is a typo – but it’s not. In fact, CITEIS stands for Cisco IT Elastic Infrastructure Services and it’s the name that Cisco’s IT department coined for our internal private cloud.
You can read more about CITEIS here, including an explanation of the two options: CITEIS “Express” for on-demand access to virtual compute resources from a shared pool of resources; and CITEIS “VDC” (Virtual Data Center) to provision your own virtual data center with a reserved pool of compute, storage, and network capacity.
We recently recorded a brief demo video of the Express version so you can see how it works:
Today, Cisco introduced the Third-Generation of Fabric computing. The power of unification can be seen in all aspects of the Cisco Unified Computing System (UCS). It unifies physical and virtual compute environments. It integrates the server and network access. It also unifies and simplifies the management of rack and blade servers. The choice between using blade and physical server is not obvious and usually sparks a heated debate. The Cisco UCS Manager with B-Series blades and C-Series Rack-mount servers makes this argument moot.
Without passing judgment on whether rack or blade servers are better, lets begin by listing the benefits of the two form factors. Blade server use is growing and there are many reasons for this:
Data center space / Power / Cooling constraints -- Data center space can get expensive depending on the location. In this CBS 60 minutes segment, proximity to the stock exchange is extolled. This fascinating video shows the collocation of data centers in urban nerve centers. I am sure data center space in these locations commands a premium. Energy efficiencies also become important in the overall cost structure. Power constraints may also favor the use of blades that consume less power than equally powerful rack mount servers.
What is the saying, two great tastes that taste great (better) together? This is in essence, the best way to describe the value of putting your Cisco Unified Communications on the Cisco Unified Computing Platform. While its certainly logical that we do something like this but and to the benefit of our customers, we have steadily increased the number of materials that help explain not just why this can be a huge cost and workflow savings, but also how one goes about doing it.
You can get a lot of written details but we of course suggest you watch one of our latest in the ‘Fundamentals’ series to get you ready.
Bonus points for the learners among you after the jump.
Cisco Business Warehouse Accelerator (BWA) is no longer sold. For more information on this product, please contact John Stone (email@example.com).
In-memory computing has been cited as one of the top technologies for 2012, SAP has introduced exciting new solutions based on this technology, and it is clearly part of the future of Business Intelligence (BI). But if you’re evaluating SAP BI solutions, what hardware systems are right for you today and in the future?
Maybe you recently acquired a license for SAP’s BusinessObjects Explorer and Business Warehouse Accelerator software. Maybe you want to prepare your data center for next generation in-memory computing databases like SAP HANA, but you’re not quite ready to invest in it yet. Maybe you know that you need an appliance to run it in your data center and are evaluating options.
One of my favorite books is The Pillars of the Earth by Ken Follet, I’ve read it and reread it many times and each time I read it I get something new out of it. With so many good books out there it seems silly to reread a book, especially a very long book. I think what it is, is that the story is so good, the characters so compelling that I don’t want to leave them and when I’m finished with the book I miss them. Fortunately the book was made into a mini-series that I enjoyed and brought a nice visualization of the story. I also think the mini-series may have attracted a new set of readers in the viewing audience.
New audiences come with new methods of distribution for the same, similar or different presentation of an already published work. With the intent to reach a new audience I am republishing a UCS XML API focused blog from another blog site on Cisco Developer NetworkUCS Section. I wrote this blog in April 2010, but the methods utilized seemed to flow from my prior entries on this site.The previously published blog has references to other blogs on the on the Cisco Developer Network site in the Cisco UCS section.
The previous blog…
Last time I wrote about using telnet to connect to the UCS Manager XML API as a way to introduce the API and show it’s lack of complexity. Now I don’t expect anyone to write an application that uses telnet to manage a UCS system, I just wanted to get across that if text, XML structured text, can be pushed across an open port to the listening API process on the UCS then it doesn’t matter how the push is done.
However telnet is not very practical, so I thought I would write about curl and xmlstarlet (xmlstarlet referred to as xml in this entry). curl is used to handle the request and response cycle with the UCS and xml is used to process the XML response. In some of my early scripts I used sed and awk to “parse” the output. I say parse but it was more pattern matching; by the way sed and awk are great tools, but maybe I’m partial to them because I’ve been around for a while. The reason I started with curl, sed and awk was not because I lacked XML experience but because I wanted to appeal to the administrators out there and show that XML experience, while beneficial, is not specifically needed.