Reston Virtualization Group 9-18-2014

Editor's Notes

• #11: Location Independence, private data center, inter-data center and hybrid private-public data center Physical infrastructure independent, use existing and have flexibility for best price-performance for added capacity and new deployments Virtual Infrastructure – Software defined data center infrastructure, decoupled from physical, operational model of a VM for entire data center environment, complete visibility, security and scale Applications – Any application, on-demand provisioning, isolation, mobility, speed and agility Application Consumption – Anywhere, Anytime, Any Device office, mobile, home, whatever.
• #12: Let’s look at the anatomy of modern data centers…the biggest, badest, most agile, most efficient data centers in the world. They have moved system intelligence into software (their custom applications or platform) They have decoupled from physical infrastructure allowing them to use any x86, any storage and any IP networking hdwr This approach has dramatically increased agility, reduced cost and provided a highly scalable inftrastructure An SDDC approach
• #13: Now, back to the choice enterprise have to make if they are going to provide “New IT” - HDDC or SDDC SDDC looks a lot like what Amazon, Google and Facebook have proven is the right approach, and they did it very intentionally without a vertically integrated hardware specific approach.
• #14: SDDC can span across multiple data centers and into hybrid service providers, independent of physical infrastructure
• #18: Financials: Goldman Sachs JP Morgan Chase Morgan Stanley Other big names to know about Apple, Yahoo,
• #19: (NOTE: Working on Juniper announcement strategy, will loop this in as nail this down. But, we may not need this slide, as we can keep the keynote focused on customers) NSX also has very broad ecosystem support. Practically every networking and security company out there has joined us to build a great partner eco-system for NSX. Since NSX GA in October. We’ve deepened these relationships, most notably…. Click…First, with HP…. Click…Second, then with PAN Click…Third, and today with Juniper. This week we are announcing….
• #22: F5 has a solution for SDAS called F5 Synthesis https://devcentral.f5.com/articles/f5-synthesis-software-defined-application-services SDN coveres OSI layer 1-3 SDAS coveres OSI layer 4-7
• #24: The video length is 00:03:52
• #29: Make sure to emphasize the ability to quarantine individual systems (Red VM in Image)
• #33: Public cloud options have not historically been a seamless extension of the data center but more a mutually exclusive and net new environment. So, public clouds represent an additional and proprietary platform Which are primarily optimized for developing new apps, not existing apps Because it’s a different platform, it has offered limited network integration and associated changes necessary for security and compliance Because it’s a different platform, it requires new and separate tools Which require different and new processes and skill sets All of these combined can mean increased operating expenses, increased security and compliance control challenges and a situation where your infrastructure is no longer your data center.
• #34: vCloud Air now offers three service offerings that can be deployed individually or in combination with one another. Both Dedicated Cloud and Virtual Private Cloud are Core Compute Cloud services, and the Disaster Recovery Service is our new business continuity service. Each can be deployed in monthly, yearly or ELA terms. The first is a Dedicated Cloud that is physically isolated – meaning there are no shared compute resources. It has a dedicated cloud management stack and the networking and storage are logically isolated. The service offering provides a minimum compute service of 30GHz vCPU / 120GB vRAM, and a minimum of 6TB storage and 50 megabits per second (Mbps) of bandwidth. The Dedicated Cloud delivers steady state, predictable performance which means it is ideal for production and mission-critical and security/compliance-driven workloads. Some example workloads for the dedicated cloud include Oracle, SAP, Exchange or other vertical-specific workloads or new application development. The second offering is the Virtual Private Cloud. This is a multi-tenant virtual private cloud service where compute, networking and storage are logically isolated. This service offering provides a minimum compute service of 5GHz reserved / 10GHz burst vCPU / 20GB vRAM, and a minimum of 2TB storage and 10 megabits per second (Mbps) bandwidth. The Virtual Private Cloud delivers burst workloads and is ideal for smaller accounts or short-term projects that don’t require a dedicated infrastructure. Example workloads include test and development, Web or mobile applications, or basically any development type environment. This offering is also ideal for a vCHS proof of concept. Finally, our newest offering is Disaster Recovery. This simple, easy to use business continuity solution provides customers with a much needed sense of security in the event of a problem with their on premises solution. Disaster Recovery is a cost effective, feature rich solution that provides customers with Recovery Time and Recovery Point selections to best achieve the appropriate DR solution. Similar to our Virtual Private Cloud, Disaster Recovery is built on shared infrastructure offers similar features and add ons as our other cloud services. Note: Capacities listed are minimum and that all compute, storage & networking capacities can be increased.
• #35: vCloud Air meets a broad number of use cases that represent how many of our customers are leveraging the service to deliver quicker incremental value. Dev/Test is a very well understood use case in that it is how many customers began the early phases of their virtualization journey. In a hybrid cloud environment, dev and test resources can be instantly accessed and are purpose built to production standards. So, the cycle from development to test to production is accelerated and delivers a test once, deliver anywhere outcome. For extending your existing apps to cloud-based infrastructure, vCloud Air make it easy by delivering cost effective data center capacity, seamless application interoperability and consistent reliable performance. Disaster Recovery options have never been simpler with easy deployments, reliable dynamic resizability and superior price/performance recovery times. Modernizing Enterprise Applications is easier with faster cloud adaptation on a common platform that leverages the same tools and processes for transitioning applications and application tiers with better control and reliability. And finally, an accelerated development process leveraging a readily available menu of developer services and instantly available production-ready infrastructure can accelerate building Next Generation Applications on a reliable hybrid platform with interoperable network constructs.
• #37: VMware vRealize™ Suite is the new brand name for our cloud management platform solution, purpose-built for the hybrid cloud. The platform combines our existing cloud automation, cloud operations, and cloud business management solutions into a comprehensive management stack for IT services on vSphere and other hypervisors, physical infrastructure and public and private clouds, all with a unified management experience. New management products just introduced include: VMware vRealize™ Air™ Automation (Beta), which lets you automate delivery of personalized infrastructure as a service across the public & private cloud with policy-based control ("Air" designates that this is an as-a-service offering) VMware vRealize™ Operations Insight™ which provides you with intelligent operations and policy-based automation, from apps to storage across physical and virtual infrastructure What we learned at VMworld is that he vRealize name has been applied across our entire management product line.  "vRealize" describes the power our management software gives you to gain insights, make decisions, and take action across the entire IT landscape. So lets review the two solutions released at Vmworld…. vRealize Cloud Management Platform, and vRealize Operations Insight, or vROI.
• #42: In order to address the challenges covered on the last slide, we need a SET of tools targeted for specific areas. These tools must be able to manage each of the five pillars of Operational Analytics: Log management, Capacity management, Configuration management etc.
• #43: At VMworld we launched vRealize Operations Insight (vROI), version 5.8. vROI is a unified IT operations and log management solution for performance management, capacity optimization, and real-time log analytics. vROI uses predictive analytics by leveraging both structured and unstructured data, for proactive issue avoidance and faster problem resolution. It is available as an add-on to VMware vSphere with Operations Management (“vSOM”), and is a solution comprised of two components: VMware vCenter Operations Management Suite Advanced and VMware vCenter Log Insight For businesses of all sizes using VMware vSphere, who are concerned about application downtimes, return on IT investment, and capital expenditure, vRealize Operations Insight (“vROI”) is the IT operations and log management solution that delivers intelligent operations and policy-based automation from apps to storage across physical and virtual infrastructure. Here’s a quick list of capabilities provided by vROI: Performance and Infrastructure Health Management: Predictive analytics and smart alerts drive proactive identification and remediation of issues. Capacity Planning, Modeling and Optimization: Automated capacity optimization and planning increases resource utilization. Real-Time Log Analytics: Universal log collection with real-time monitoring, search and log analytics enables faster problem resolution. Application Dependency Mapping: Simplifies and accelerates root-cause analysis. OS Monitoring: Monitors operating system resources – CPU, disk, memory, network, for Windows and Linux systems. Storage and Network Visibility: Provides SAN Storage analytics and is extensible with data feeds from third-party storage and network monitoring tools. vSphere Hardening, Change, Configuration and Regulatory Compliance: Automated detection and enforcement of standards to ensure compliance. Unified Management through an Open and Extensible Platform: Full visibility from apps to storage – for vSphere and physical hardware, supported by extensions for third-party tools, like Microsoft SCOM, and others. vSOM offers vSphere + vCops Standard, with the vRealize Operations Insight package you can add vCops Advanced & Log Insight to your infrastructure. vRealize Operations Insight is available on a per-processor perpetual license model (which includes unlimited virtual machines and underlying hardware), as an add-on solution to VMware vSphere with Operations Management.
• #44: vROI extends intelligent operations management beyond vSphere to include operating systems, physical servers, storage and networking hardware, and is supported by an extensive marketplace of extensions for third-party tools, including Microsoft SCOM, NetApp, Brocade, EMC, Cisco, and more.
• #45: Delete? Maybe just brief the team, then take it out before presenting.
• #47: Change vCHS logo to new name
• #48: What are we doing? Delivering a comprehensive cloud management platform for managing your hybrid and heterogeneous clouds as a Service Easy to try, flexible, rapid time to value Why? Our customers Industry Trends
• #57: http://www.youtube.com/watch?v=J30zrhEUvKQ
• #60: Delete?
• #61: VMware is the number 4 contributor to the OpenStack initiative. VMware announces further integration of OpenStack and vSphere through a new vitual appliance called VMware Integrated OpenStack (VIO): VMware + OpenStack = Better Together. OpenStack offers already integration with vCenter/ESX, NSX, vSphere Datastores and VSAN, using OpenStack Nova, Neutron, Cinder and Glance. New is VMware Integrated OpenStack (VIO) is the combination of OpenStack and vCloud Suite. A special OpenStack Virtual Appliance will be available for download. The OpenStack appliance will connect and prepare you vSphere environment to be used by OpenStack
• #63: The History is even before we joined the foundation.
• #68: No OpenStack PHD required! Leverage known vmware products and tools to build, operate and maintain OpenStack cloud Time is money. We have seen DIY efforts and even distro supported efforts take multiple months to get a production grade openstack functional. We believe we can cut this to few hours! Building the cloud on products that you trust, that have proven track record in enterprises Complete single vendor support. No need to run to multiple vendors to support the OpenStack cloud.
• #71: www.Cloudvolumes.com Product Demo Video Length is 00:02:09 Direct integration with virtual infrastructure and storage CloudVolumes enables all files, data, and applications used by more than one virtual machine to be placed into shared virtual volumes (i.e., VMDK files in the case of VMware) and CloudVolumes does the magic to make this shared data accessible to all virtual machines that need it in a way that is transparent to the virtual machine. These volumes can be placed on any type of storage that the hypervisor supports (i.e., SAN accessed via Fibre Channel or iSCSI, NFS, locally attached storage, etc.). CloudVolumes Manager will place the shared volumes or writable volumes on any datastore of your choosing. CloudVolumes is not inline in the storage path, it operates as more of a broker—we attach or detach volumes from virtual machines in response to certain events that will be discussed in more detail later. Reads and writes are sent directly from the virtual machine (where the volumes appear as local disks) to the datastore’s underlying storage through the hypervisor. This approach enables storage tiering. Shared volumes (which receive only read requests) can be placed on a datastore optimized for read operations. As an example, it would not be cost effective to put entire virtual machines on an SSD datastore because of the cost of SSD. However, because CloudVolumes requires only a single copy of applications and shared data, those shared volumes can be placed on an SSD datastore and provide better application performance with only a marginal increase in storage cost. Shared volumes: Install once, use anywhere CloudVolumes Manager is configured to work with an Active Directory domain (or any other LDAP-based directory service) and a VMware vCenter. Shared volumes are then assigned to a user, computer, or group. A volume assigned to a computer will be attached when the computer turns on. As an example, SQL Server 2012 could be provisioned into a shared volume and assigned to an Active Directory group called “SQL Servers.” Whenever a new virtual machine is created or powered on that is a member of the SQL Servers group, CloudVolumes Manager will attach the shared SQL Server 2012 VMDK into that virtual machine. A volume assigned to a user will be attached into the virtual machine the moment the user logs into the virtual machine, and detached the moment the user logs out of the virtual machine. As an example, Visual Studio 2012 could be assigned to the Developers group, and whenever a developer logs into a virtual desktop, the Visual Studio will be instantly attached to the virtual machine before the login has even completed. Users are unaware that the applications are being instantly delivered the moment they logged in, because it happens so quickly that it is attached prior to users seeing their desktop or start menu. Applications delivered via CloudVolumes are indistinguishable from native applications Through the magic of CloudVolumes, an application is installed or updated only and then shared across all virtual machines. Applications contained in shared volumes will behave the same as locally installed applications. The application and OS are both unaware that the application is shared virtual machines. The files, data, registry settings, etc. are located the same place they would normally be. This is because, at the time the application was provisioned, it was provisioned in the same way an application is normally installed natively. CloudVolumes transparently put the application (and its dependencies if any were installed) into the sharable volume while it was in provisioning mode. For example, as soon as a shared volume containing a default installation of SQL Server 2012 is attached to a virtual machine, it is automatically started and you can immediately start interacting with it. The files are located where they normally are: C:Program FilesMicrosoft SQL Server. Similarly, its registry keys are in the regular location (HKLMSOFTWAREMicrosoftMicrosoft SQL Server), its Windows services are visible in the Services management console, etc. Scalable architecture One CloudVolumes Manager can easily serve 10,000 virtual machines which is as many virtual machines as one VMware vCenter support. The CloudVolumes Manager is a stateless web server that stores all of its session state and information into a shared database. So you can operate as many CloudVolumes Managers as you’d like for load balancing or high availability. If the database shared by all of the CloudVolumes Managers is put onto a SQL Server cluster, then there is no single point of failure. The CloudVolumes Manager sits idle until either the IT administrators visits the management page using a web browser, or a CloudVolumes Agent located within a virtual machine contains the CloudVolumes Manager. The CloudVolumes Agent is installed into any virtual machine that you’d like CloudVolumes to manage, and it only contains the CloudVolumes Manager during power on, power off, user login, and user logout. Even if a new VM is being powered on or created every second, a single CloudVolumes Manager can handle the load because it translates to only one HTTP request per VM. Once the CloudVolumes Agent contains the CloudVolumes Manager to report the VM power-on event, the CloudVolumes Manager checks its database to see if there are any volumes associated with that VM or a group that VM is a member of. If so, the CloudVolumes Manager communicates with the hypervisor to attach the volumes to the VM, and then its job is done and there is no further communication between the CloudVolumes Manager and Agent until the next logon, logoff, or poweroff event occurs. Most of the magic happens within the virtual machine once the volume has been attached to the virtual machine. The CloudVolumes virtualization software within the virtual machine detects when a writable volume or shared volumes have been attached instantly overlays its contents on top of the virtual machine based on the volume’s policy. This operation is instant because no files are being transferred. When the application launches, the I/O is transparently redirected to the appropriate location so that the application and operating system work exactly as they normally do. If the number of virtual machines supported per hypervisor (VM density) in your existing environment is bound by RAM or CPU, CloudVolumes will make the virtual machines and applications easier to manage, but it won’t likely improve your VM density. However if your VM density is bound by IOPS, CloudVolumes will likely enable you to increase your VM density by enabling you to put shared content on faster, read-optimized storage. Similarly, CloudVolumes shared volumes can be easily cached at the hypervisor level so that the I/O doesn’t leave the physical box. If the applications are shared and the VM’s base disks are shared (using linked clones or using “fast provisioning” in VMware vCloud), then most IOPS from the VMs can be serviced from the cache without ever reaching the shared storage.
• #72: You tube Video length is: 00:02:09
• #73: Press Release: Ir.vmware.com/releasedetail.cfm?ReleaseID=867787
• #78: In 6.1 we have added out of box vCO workflows for refreshing production DBs of Oracle 12c and Microsoft SQL Server 2012, the workflows executes the following steps: 1.       Provision a new database based on an Oracle 12c or SQL 2012 AppD Blueprint (the AppD BPs are also out of the box) - This step deploys the DB application blueprint from AppD based on a set of parameters provided by the DBA 2.       Import data from a backup copy of the DB to the newly provisioned database – Executes an “Update” operation from AppD that is called “Import Data for Oracle/SQL” onto the newly deployed instance 3.       Mask the imported production data by extending into existing scripts the customer have for data masking – has the capability to run a out of the box custom task to call a script to mask data   After this had been done we will have a “Golden Image” of the production DB deployed that can be added to vCAC for consumption using either full clone or linked clone, we do this in the same way we currently create blueprints in vCAC from an existing VM.
• #85: 1) Security: Micro-segmentation/Security pitch is Network Virtualization enables isolation of workloads, segmentation into multiple zones & advanced security service insertion for threat mitigation. 2) Networking: On-demand programmatic networking that is available datacenter-wide & decoupled from physical hardware, enabling cross-host & cross-container connectivity. We remove network silos, simplify IP address space management and optimize East-west traffic with distributed implementation of routing & firewalling services. Today containers use NAT’ing and its challenging around IP address management Its also difficult to have a containerized enterprise app that spreads across the datacenter (more than 1 host) and NSX solves those problems for containerized workloads. Current Integrations Native support for all Linux Containers via Open vSwitch integration, including Docker. Lead Open vSwitch, NSX & OpenStack integration. Supports multiple Container deployment models across multiple hypervisor types & bare-metal hosts.
• #86: Binaries and content are packaged in Docker containers during build and moved to staging and pro-duction using Jenkins Pipeline Our backend is processing customer data, acquiring more data from online sources, and generating content for the front-end It is also validating the content and serves as staging environment Some services use fleet and some are managed by Mesos In our front-end, over dozen micro-services run in Docker containers on CoreOS VMs: Web Server x3 Database x3 Content Load Balancer Session Store Authentication Licensing DNS Provisioning Monitoring …