Ucs invicta & application performance

Editor's Notes

• #5: Here is what we built UCS to do Customers told us: they were struggling to apply flash/solid-state technology in the environment Data Acceleration Layer for Applications Address scale of new data sets Address new velocity requirements Manage as a System Simplify infrastructure to drive TCO Multi-Workload / Multi-Tenant Flexibility
• #6: Reduction in Provisioning Times Reduction of Cabling Reduction of Ongoing Management Costs Reduction of Power and Cooling Costs World-Record Application Performance Benchmarks
• #13: Our portfolio consists primarily of two products. The t appliance has very high performance, has very good bandwidth, and it has very good storage characteristics. That foundation appliance can be deployed as parte of a UCS Invicta Scalable System, allowing the customer to scale on both performance and capacity axes. It's scalability, modularity, the ability to accelerate an application, the ability to optimize the data, also to handle multiple workloads at the same time, which can all be done without sacrificing performance.
• #16: Need to update throughput numbers in all cases What are our two sets of building blocks, if you will? If you have the ACCELA appliance, you’re really looking at the ability to either accelerate workloads or reduce the amount of data that were actually stored. It's a unique offer. We're really the only vendor in the marketplace today that allows our customer to choose the kind of appliance they would like to use. Those same building blocks, enfold into our UCS Solid State Systemstechnology, become what we refer to as silicon nodes. The customer can choose one or the other, or they can actually combine them under the same architecture. Of course what you can see here are the performance and capacity characteristics.
• #17: Need to update throughput numbers in all cases What are our two sets of building blocks, if you will? If you have the ACCELA appliance, you’re really looking at the ability to either accelerate workloads or reduce the amount of data that were actually stored. It's a unique offer. We're really the only vendor in the marketplace today that allows our customer to choose the kind of appliance they would like to use. Those same building blocks, enfold into our UCS Solid State Systemstechnology, become what we refer to as silicon nodes. The customer can choose one or the other, or they can actually combine them under the same architecture. Of course what you can see here are the performance and capacity characteristics.
• #18: Traditionally, you either have a single appliance that has all the centralized functions with it and over time, people discovered something very interesting about that approach, which is if they needed to add more capacity, they couldn’t do it. You would run out of slots. So they moved into what we refer to as “Scale Up”. We then took all of the functions, we move them above the storage itself and then we were able to add more capacity. With this approach, of course, is as we added more capacity, those functions were stretched. You go across more and more storage affecting performance, so people decide to look to Scale Out. By moving to Scale Out, we take different types of appliances, put them together, and all of the functions are somewhat decentralized. You do end up with more performance, you do end up with more capacity, but you actually sacrifice some very important things that centralization brings. So we've taken a different approach. We have what we refer to as HyperScale, the ability to scale up and scale out either independently or together. It's really up to you. We do this through what we refer to as our INFINITY Scale Up/Out architecture.
• #19: When we combine it all together, what we adopt with here is a Scale Up/Scale Out architecture. You can start as little as pair of routers and a pair of nodes. If you decide that you need to drive more throughputs to the nodes, you can add more routers. If you decide that you would like to add more performance and capacity, you can add more nodes. Every time you add a node, you're adding CPU, memory, operating system, independently managed function, and most importantly, flash management. This is what sets us apart from many of our competitors.
• #20: Need to update throughput numbers in all cases What are our two sets of building blocks, if you will? If you have the ACCELA appliance, you’re really looking at the ability to either accelerate workloads or reduce the amount of data that were actually stored. It's a unique offer. We're really the only vendor in the marketplace today that allows our customer to choose the kind of appliance they would like to use. Those same building blocks, enfold into our UCS Solid State Systemstechnology, become what we refer to as silicon nodes. The customer can choose one or the other, or they can actually combine them under the same architecture. Of course what you can see here are the performance and capacity characteristics.
• #21: When we combine it all together, what we adopt with here is a Scale Up/Scale Out architecture. You can start as little as pair of routers and a pair of nodes. If you decide that you need to drive more throughputs to the nodes, you can add more routers. If you decide that you would like to add more performance and capacity, you can add more nodes. Every time you add a node, you're adding CPU, memory, operating system, independently managed function, and most importantly, flash management. This is what sets us apart from many of our competitors.
• #22: In addition to the create buttons in the reports menu, UCSD allows the use of Macros to create customized workflows to help automate tasks. During the creation of a Cisco UCS Director workflow, you can use macros for Workflow Task inputs. During the runtime execution of the workflow, the Orchestrator replaces the values for each macro before executing the associated action. Each Cisco UCS Director workflow typically has the following components: 1. Workflow inputs that are defined by the administrator. 2. Tasks that are drag-and-dropped by the administrator from a predefined set of the task library. Each task has an ID, set of inputs, and outputs. Macros may be used for each task input. Any workflow level input or a previous task output can be used as a macro in a subsequent task. The figure shows the pre-defined tasks for Cisco UCS Invicta products in 4.1 UCSD.
• #24: Speaker Notes: The Invicta OS within UCS Invicta Series already resides on Cisco hardware! Available today are flash media management, data protection and de-duplication and UCS Director support. UCS Director support is a key differentiator that will enable consumer business imperatives – it allows for storage provisioning under the same management pane as the rest of the UCS architecture. The fuller vision of Cisco UCS is to have compute, network and storage living in the same architecture being managed by UCSD and UCS Manager for a fully unified Data Center management perspective. With the addition of UCS Manager, service policies can be provisioned in the same environment as storage policies. This will further eliminate Data Center complexity by reducing resource deployment from weeks to minutes and allowing resources to dynamically be reconfigured as business priorities change.