How To Make A Cloud Based System A Successful Business Model

Transcription

1

2 Virtualization in an automation perspective Torbjörn Turpeinen Senior Technical Sales Consultant 2010 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners. Slide 2 Invensys 00/00/00 Invensys proprietary & confidential

3 Topics Why? Why Virtualize? What is new Trends and Roadmap HA,DR and FT Failover Clustering Sizing RDP Technologies Considerations Memory Storage Network

4 1 Why Virtualization Slide 4

5 Slide 5 Why is Virtualization beneficial?

6 Slide 6

7 Slide 7

8 Slide 8

9 2 What s New Slide 9

10 Top ten technologies for 2010 Invensys Investments areas: -1. Cloud Computing. -5. Virtualization. -9. HA and Virtualization -10. Mobile Applications

11 Top ten Technologies 2011 Slide 11

12 Cloud Computing Invensys Announces Alliance with Microsoft to Help Accelerate Windows Azure Development It will afford end users cloud-based offerings in the manufacturing and infrastructure operations space Providing cloud-based reporting and collaboration services allows customers to pay for what they use, which means they can better scale and manage their technology deployment costs. It s an attractive model for any customer that has widely distributed operations, limited IT resources or the need to rapidly scale. Customers will have the choice of different usage models, so they pay for only what they need Slide 12

13 Virtualization 2.0 Virtualization is all about flexibility and the ability to adapt. These advantages go beyond mere hardware savings Slide 13

14 Target Customers for Virtualization Some of the benefits of Virtualization apply to almost all customers But some are especially valuable to customers who Have long production runs with minimal opportunities to upgrade hardware Customers who require high availability and need to minimize downtime to ensure meeting production commitments or avoid production losses These tend to be Heavy process and infrastructure industries (Power, Water, Gas, etc). Customers who might be disaster prone e.g. Earth quake regions, Flooding Regions, Tornado Regions, etc. Slide 14

15 System Platform 2012 System Platform 2012 and components are supported on Microsoft Hyper-V (this was announced at release in November) System Platform 2012 and components are also supported on VMWare VMESXI v5.0 and VSphere v5.0 Simplex (multiple virtuals on one Host) High Availability (co-located Hosts with failover) Disaster Recovery (geographically separated Hosts) VMmotion ability to move Vmachine to another Host SnapShots ability to save the state of the VM creating a recovery point Slide 15

16 Microsoft VMM 2012 Fabric Management Hyper-V and Cluster Lifecycle Management Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V cluster Third party Virtualization Platforms: add and manage Citrix XenServer & VMWare ESX hosts and Clusters Network Management Manage IP Address Pools, MAC Address Pools and Load Balancers Manage Storage Pools and LUNs Dynamic Optimization: proactively balance the load of VMs across a cluster Cloud Management Abstract server, network & storage resources into private clouds Delegate access to private clouds w/control of capacity, capabilities & user quotas Service Lifecycle Management Define service templates to create sets of connected virtual machines, OS images & application packages Compose OS images & applications during service deployment Scale out the number of virtual machines in a service Leverage powerful application virtualization technologies such as Server App-V

17 Technologies supported in System Platform 2012 Standard and Enterprise is supported 2008 Server R2 Virtualization Visualization Hyper V Failover Clustering Live migration Quick Migration VMM2008 VMM 2012 Smartcard support in RDP sessions Multi Monitor Support in RDP Access VLANS Remote Apps Remote Desktop Network load balancing

18 VMWARE Virtualization Management Slide 18

19 Market prediction Virtualization Hypervisors become a commodity. Management solutions for Purchase from either vendor. Choice of Private or Public Cloud including deployment off VM s Resources become a Fabric, Optimization and automation of Life cycle control and deployment.

20 Reduction of HW boxes. Information Client InTouch for SP w/trend Active Factory AOS Data Server AOS Data Server AOS Data Server Information Server Historian Server GR Field Devices Slide 20

21 Consolodation what is the Risk So great we now virtualized our enviroment and we are completely happy.perhaps not for long. Untill the day that server fails or its network fails or it needs an update. on that day the server is out it means 5, 10, 15 or perhaps even 20 machines are down. how can this be resolved?..answer High Availibilty!!! Slide 21

22 3 High Availibility and Disaster Recovery Slide 22

23 Slide 23

24 Slide 24

25 Different levels of Redundancy in control systems Virtualizing ArchestrA System Platform 23 Level Description Comments Level Description Comments Level 0 Redundancy Level 1 Cold Standby Redundancy Level 2 High Availability (HA) No redundancy built into the architecture for safeguarding critical architectural components Redundancy at the Application Object level Safeguards single points of failure at the DAServer level or AOS redundancy. With provision to synchronize in real-time Uses virtualization techniques Can be 1-n levels of hot standby Can be geographically diverse (DR) Uses standard OS and nonproprietary hardware Expected failover: None Expected failover: 10 to 60 seconds Expected failover: Uncontrolled 30 seconds to 2 minutes, DR 2-7 minutes Level 3 Hot Redundancy: Level 4 Lock-step Fault Tolerance (FT) Redundancy at the application level typically provided by Invensys controllers. For example, hot backup of Invensys software such as Alarm System. Provides lock-step failover Expected failover: Next cycle or single digit seconds Expected failover: Next cycle or without loss of data. For ArchestrA System Platform, this would be a Marathon-type solution, which also can be a virtualized system. System Platform Supports Level 1,Level 2 in System platform 2012

26 Solution for Disaster recovery and high availability Using Hyper V and a Failover clustering. Using Sios for data replication over LAN or WAN with or without SAN. Optional our services to migrate and validate your system. Turnkey project to deliver your tailored disaster recovery solution or highly available system.

27 What is a Failover Cluster. A Failover system consists out of two or more servers defined within a failover cluster the resources can be assigned to certain server and become highly available. The voting of who is in control is done trough a quorum. This shows a Failover cluster running three virtual machines, a GRNODE, Historian and a remote App server (terminal server) There two networks a LAN and a WAN. Virtualization Server 2008 Hyper V Failover Cluster New technologies

28 Combined Technologies provide HA and DR

29 Clustering Provides High Availability Slide 29

30 Clustering providing High Availibility and Disaster Recovery Slide 30

31 Use of Vlan s for Networks Use of VLANS is beneficial where: A. There is only one LAN / WLAN and segregation is needed. B. In use of Virtual Networks. Slide 31

32 Load Balancing of terminal Servers 2008 R2 InTouch enhancement will automatic detect and assign to a core. Slide 32

33 4 Considerations regarding Virtualization Slide 33

34 Virtualization guide Slide 34

35 Key considerations Some of the key considerations in an successful virtualization implementation Cores and Memory Storage Network Slide 35

36 The number one consideration regarding automation virtualization in a distributed network. High Performance SQL Server Workloads Time synchronization for real time data collection Real case in a large system the response time for stored procedures that normally executes below 30ms took 1 minute, this was caused by r/w delays. Slide 36

37