Rebecca Jacoby, Cisco Senior Vice President and Chief Information Officer, discusses Cisco’s journey to the cloud. Cisco is running a private cloud as a utility and is moving toward an inter-cloud approach. This capability will give Cisco the business process opportunity to source services from multiple places and deliver them seamlessly to employees in a flexible, cost-effective manner.
If you’ve ever gone fishing, then you know it requires a great deal of patience. So, what if you could fish in a barrel, and catch a lot of fish, rather than fish in the ocean and risk coming away empty-handed?
That would be great, right? Well, guess what, that ability to “fish in a barrel” is one of the advantages that is offered by Partner Plus, which was announced at Partner Summit last month. Partner Plus is targeted at partners who invest in selling Cisco to mid-sized customers, which IDC estimates as a $61B market opportunity. Aimed at accelerating business for these partners, Partner Plus provides incremental incentives, virtual engineering support, marketing, sales enablement, and customer intelligence to partners who commit to a highly collaborative selling approach with Cisco to accelerate their business more quickly than the market.
Partner Plus will bring together the power of Cisco sales and the partner sales force to go after the fast growing market opportunity with mid-sized customers. Watch this video to learn about the impact that Partner Plus can have in your business.
Read on to learn more about how Partner Plus can help you drive sales. Read More »
This part 1 of the series “10 Things Vmware Server Admins Should Know About Self-Service Catalogs and Lifecycle Management” that I’ll be publishing over the next few weeks--I hope! (The boy is nothing if not ambitious).
1. The service catalog is a tool for driving users to standard configurations.
To get the operational efficiencies we hope to achieve from virtualization and / or cloud computing, we need to establish standard configurations. This is tough, for a couple of reasons.
First, the challenge is the gap between the language of the customer, and the detail needed by the operations group typically generates a lot of back and forth during the “server engineering” process. Instead of having “pre-packaged” configurations, every thing is bespoke.
Instead of having useful abstraction layers and levels, the customer has to invent their own little bit of the data center. This made sense when the new app meant a whole new hardware stack to which the app would be fused to and the concrete poured on it. It doesn’t make sense now.
Second, there’s resistance from customers to adopt standard VM builds. Sometimes the reasons are valid, other times less so. The issue arises because the technical configurations have not been abstracted to a level the user can understand what they get and what’s available for configuration. Nor can they compare one template to another in ways that are meaningful to them.
The service catalog is the tool to help deal with these two obstacles. The service catalog is a useful tool to communicate, in the language of the customer, the different options available from IT for hosting environments.
A service catalog will support multiple views (customer, technical, financial, etc) so that when the customer selects “small Linux” for testing, this generates both a bill of materials and standard configuration options. Once that base is selected, self-service configuration wizards provide both guidance and gutter-rails so the customer is both helped to the right thing and prevented from making errors.
From this customer configuration, the environment build sheet is generated which will drive provisioning and configuration activities or to execute any policy automation in place.
And the catalog allows the VM admins to figure out what their “market” is buying; which is very useful for capacity planning.
Organizations small or large can deploy collaboration technologies on premises, on the cloud, or on both with a hybrid deployment. I believe that the source or the provider of collaboration technology should be transparent to the end-user and that the experience should be the same regardless of deployment model or device used.
At Cisco we’re very focused on offering flexible deployment models that support on-premises, cloud, or hybrid deployments of our collaboration technologies. Of course, these are built on our collaboration architecture to ensure the interoperability and user experience. Read More »
Welcome to a world of many clouds. Today’s leaders can architect their own private clouds for maximum security, purchase services from public-cloud providers, or find the right balance between the two. In some cases, business services that once cost millions of dollars in internal technology and IT staffing can be garnered for just hundreds of dollars per month when outsourced to the public cloud. Enterprises are significantly impacted by top- and bottom-line benefits.
Top-line growth results from a host of enhancements: