Cisco Blogs


Cisco Blog > Data Center and Cloud

Why Implement Microsoft SQL Server on Cisco Unified Computing System (UCS)?

November 4, 2014 at 2:00 pm PST

A Guest Blog by Cisco’s Frank Cicalese:  Frank is a Technical Solutions Architect with Cisco, assisting customers with their design of SQL Server solutions on Cisco Unified Compute System. Before joining Cisco, Frank worked at Microsoft Corporation for 10 years, excelling in several positions, including as Database TSP. Frank has in-depth technical knowledge and proficiency with database design, optimization, replication, and clustering and has extensive virtualization, identity and access management and application development skills. He has established himself as an architect who can tie core infrastructure, collaboration, and application development platform solutions together in a way that drives understanding and business value for the companies he services.

Ah yes, it’s that time of year again.  It’s time for PASS Summit! I hope all of you are having a great event thus far. During my conversations with customers and peers, I am inevitably asked “Why should we implement SQL on UCS?”  In this blog I cover this very common question. First off, for those of you not familiar with Cisco UCS, please visit here when you have a moment to learn more about this great server architecture. So, why would anyone want to consider running their SQL workloads on Cisco UCS?  Read on to learn about what I consider to be the top reasons to do so…

Mitigate Risk: 

High availability is one of the most important factors for companies when it comes to considering an architecture for their database implementations.  UCS provides companies with the confidence that their database implementations will be able to recover quickly from any catastrophic datacenter event in minutes as opposed to the hours if not days that it would take to recover on a competing architecture.  UCS Manager achieves this through its implementation of Service Profiles.  Service Profiles contain the identity of a server.  The UCS servers themselves are stateless and do not acquire their personality (state) until they are associated with a Service Profile.  This stateless type of architecture allows for the re-purposing of server hardware dynamically and can be utilized for re-introducing failed hardware back in to production within five to seven minutes.

Service Profiles can provide considerable relief for SQL Server administrators when re-introducing failed servers back in to production. Service Profiles make this a snap!  Just un-associate the Service Profile from the downed server, associate it with a spare server and the workload will be back up and running in five to seven minutes.  This is true for both virtualized and bare-metal workloads!  Yes!  You read that last statement correctly!!  Regardless of the workload being virtual or bare-metal, Cisco UCS can move the workload from one server to another in five to seven minutes (providing they are truly stateless i.e., booting from SAN).

Foster Standardization:

Since every server in UCS that is serving a workload requires that a Service Profile be associated with it, Cisco UCS Manager provides the ability to create Service Profile Templates which ease the administrative effort involved with the creation of Service Profiles.  Server administrators can configure Service Profile Templates specifically for their SQL Servers and foster consistent standardization of their SQL Server implementations throughout the enterprise via these templates.  Once the templates are created, Service Profiles can be created from these templates and associated to a server in seconds.  Furthermore, these operations can be scripted via Cisco’s Open XML API and/or PowerShell integration (discussed next) simplifying the deployment process even more.

To learn more about Service Profile Templates and Service Profiles, please visit here.

Manage Workloads Efficiently: 

Cisco UCS has very tight integration with Microsoft System Center.  Via Cisco’s Operations Manager Pack, Orchestrator Integration Pack, PowerShell PowerTool and Cisco’s extensions to Microsoft’s Hyper-V switch, administrators are able to monitor, manage and maintain their SQL Server implementations proactively and efficiently on Cisco UCS.  Additionally, Cisco’s PowerTool for PowerShell, with its many cmdlets, can help to automate any phase of management with System Center thus optimizing the overall management/administration of Cisco UCS even more so.  All of this integration comes as a value-add from Cisco at no extra cost!

Please visit http://communities.cisco.com/ucs to learn more about, download and evaluate Cisco’s Operations Manager Pack, Orchestrator Integration Pack and PowerShell PowerTool.

Read More »

Tags: , , , , , , , , ,

How Cisco uses Open Source Cloud to transform Telcos (Part 1 of 2)

Here is my first blog, which I am writing to you from Johannesburg, South Africa where I am on an assignment with a customer engagement.  Based in Dubai, I’m the part of the Cloud and IT Transformation Practice in Cisco Advanced Services, and I’d like to share some of my day-to-day consulting experience with you with respect to Telco and OpenStack.

The Customer Challenge

Telcos today are entrenched in their heterogeneous, disparate and multi-vendor operating environments. Whilst their web-scale counterparts can provision services often in minutes, a telco-grade offer sometimes takes weeks for fulfilment.

At the same time, demand is changing – present day users demand for “anywhere, any-time” data and service availability, secure, and with a satisfactory SLA. Further, they demand agile services, which provision quickly and at low cost and fully align with customer needs. For example, adding a new end point to a customer VPN should take very little provisioning time.

Not only this, but with the inception of the Internet of Everything, Telcos must invest to expand their capacity. According to Cisco’s Visual Networking Index, the mobile data traffic alone is projected to grow at a compound annual growth rate (CAGR) of 61 percent (starting from 2013 all the way to 2018), reaching 15.9 exabytes per month by 2018.

photo3

Last but not least, capacity needs are dynamic - peak and non-peak usage of capacity differ by many factors, and idle capacity is a costly luxury. Neither the telco’s technical architecture nor the operating model and environment are ready today to meet the challenges of agile, high volume, fluctuating needs at an attractive cost.

New Telco Architectures

Especially when compared to hardware, software is a better environment to respond to these challenges: faster to adopt; more easily embodies new features; quickly reflects new customer configurations; scales up and down with more ease; and has little or no production cost. As a consequence, telcos try to move their environments as much to software as possible.

The next debatable item is the Software strategy: Commercial or OpenSource? Of course, Commercial Software comes with support and documentation and may be less susceptible to hackers due to its closed nature, while OpenSource offers a multitude of functions at little to no cost and is constantly updated and adapted.

To make Commercial Software more affordable for the Service Providers, vendors often suggest the “Pay As you Grow Model”.  Under this business model, vendors allow Service Providers to make relatively small initial investments in capacity and/or functionality. As the SP leverages software licensing to drive core initiatives, the investment in technology is  expanded incrementally if and when the business need arises.

This incremental model is often favored by businesses today as it insulates them against the downside of over-investing. For the vendor, this model promises both present and future revenue.

On the other hand, OpenSource comes with the source code which means Service Providers can have their own teams of developers and they can modify/update the contents as per the Business and Technical requirements.

Road to the OpenSource Cloud starts from Workload consolidation and then Infrastructure virtualization and then Operations Automation and then Cloud Computing and finally OpenSource Cloud so basically it’s a Journey not just a destination.

So what needs to be done here? It seems everyone is trying to move toward XaaS (everything “X” as a service) because this where cloud is popping up as the dominant way to provider infrastructure, applications and solutions – characterized by an off-premise, self-service, opex model of delivery.

But before a telco embarks itself on the path of transformation, it needs to identify its identity, i.e., what kind of services it is going to be offering. Some of the incumbent service providers are offering services such as Cloud Compute, Cloud Storage, Network enabled Cloud, Private Cloud, and VDI ….to name just  a few. What about your organization?

In my next blog, I’ll continue with our approach here at Cisco and how we are helping customers. In the meanwhile, please join us at OpenStack Summit in Paris:

The OpenStack Paris Summit started November 3. In addition to the general speaking sessions, booth, demos and other events captured here, Cisco’s team members are also leading and participating in several design sessions to shape the Kilo OpenStack release.

We look forward to having some great discussions at the Summit and hope to see you there as well! Please stop by Cisco (Booth C3) and our newest acquisition, Metacloud (Booth E37). Visit us at Cisco’s OpenStack webpage for more information.

I hope you have enjoyed this blog. Please feel free to get in touch via the comments field.

photo2

Tags: ,

Cisco Global Cloud Index (2013 – 2018): Data Center and Cloud Traffic for the Next Five Years

What do our GCI Forecast projections mean for you?

Today, Cisco released the fourth annual update of its Global Cloud Index, or GCI (see media release). For most people who follow cloud-computing, it’s no real surprise to learn that global data center traffic will nearly triple over the next five years or that cloud traffic is expected to nearly quadruple. Examining the trends within the top-line forecast projections is where we begin to see what this growth means for service providers, businesses, and consumers (and how data center networking is being transformed).

Instagram-play

For Service Providers and Data Center Operations:

GCI Highlight: The workload density (that is, workloads per physical server) for cloud data centers was 5.2 in 2013 and will grow to 7.5 by 2018. Comparatively, for traditional data centers, workload density was 2.2 in 2013 and will grow to 2.5 by 2018.

The Benefit: An important factor in the rapid expansion of cloud computing is increasing data center virtualization, which provides services that are flexible, fast-to-deploy, and efficient. Virtualized data centers require fewer physical servers and offer great scalability than traditional data centers. This can ease capex and opex pressures (allowing for investment in other areas).

For Large Enterprises and Small-to-Medium Business Read More »

Tags: , , , , , , , ,

Cisco and Red Hat – All In with OpenStack for the Enterprise

When it comes to driving innovation in next generation data center architectures, open source is clearly at the forefront. A perfect example is OpenStack, which is defining the future of cloud computing across private, public and hybrid clouds. This innovation is being driven by a strong and vibrant community that is taking place in Paris this week for the OpenStack Summit. I’m looking forwarding to reconnecting with friends in the OpenStack community and discussing the recently announced Cisco and Red Hat solution for OpenStack.

Interest in OpenStack as a cloud platform is clearly on the rise. At the recent Cisco Unified Computing System (UCS) launch event in New York City, Cisco and Red Hat introduced the UCS Integrated Infrastructure for Red Hat Enterprise Linux OpenStack Platform (UCSO).  The pre-integrated and validated solution is a major step forward in providing an enterprise ready private cloud solution based on OpenStack.

Read More »

Tags: , , , ,

The Top 5 OpenStack Adoption Challenges – View from Cisco Services’ Experts

November 3, 2014 at 11:34 am PST


openstackOpenStack is gaining increasing industry attention and, while it can deliver huge advantages, some may say it is “hyped”. Although OpenStack has an ever growing range of enthusiastic practitioners and advocates,  as you may be aware, OpenStack is not without its critics – including Gartner - who outline the challenges of OpenStack adoption. It’s therefore generally recommended that OpenStack adopters consider engaging professional services experts to help them avoid the pitfalls

With the November 2014 OpenStack Summit in Paris opening as I write this – you can find us at stand C3 along with our newest acquisition, Metacloud (Stand E37) if you are going - my thoughts turn to the issues and challenges facing our customers when they deploy OpenStack into production projects.  And who better to ask than our Cisco Services consultants who are delivering OpenStack adoption services (which we launched this time last year at the Summit in Hong Kong).

These consultants are at the “coal face” (as we say in my part of the world, Scotland) of OpenStack– they are the experts digging deep in the IT equivalent of the mines working with real customers going live with real-world OpenStack.    More than R&D investigations, these deployments are happening with customers who are betting their business dollars, pounds, yen and other currencies on OpenStack.  However as the video (below) shows, OpenStack has its deployment complexities.  Hence increasing numbers of our customers are engaging Cisco Services to help them on OpenStack.

To share our practical experiences with you, we sat down and came up with our “top 5” adoption challenges list which you may find useful if you are considering or embarking upon an OpenStack deployment:

  1. Cross-domain technical expertise is mandatory
  2. Going deep with Open Source
  3. “It’s just middleware”
  4. Don’t underestimate the learning curve
  5. Expect your OPEX to increase (sorry!)

Read More »

Tags: , , , , ,