Virtualization Delta V (production Environment)

as wondering if anyone is currently running Delta V in a production environment, I am currently looking at setting a new VM environment.  I have a pretty extensive background with VMWare, but from what I understand Delta V Virtual Studio is based off Hyper-X.

If people would not mind posting their feedback with Virtualization I would appreciate it, little detail on your network configuration would be fantastic as well.

 I am looking at setting up three R720 host servers and one R320 Virtualization Domain Controller.  The storage device I will be using is a Dell MD3220i.

 Again any feedback would be appreciated.  (issues\good\bad etc.)

 

-Robert

10 Replies

  • **fixed message from above, could not find an edit button**

    Was wondering if anyone is currently running Delta V in a production virtualized environment, I am currently looking at setting a new Virtual environment. I have a pretty extensive background with VMWare, but from what I understand Delta V Virtual Studio is based off Hyper-V.

    If people would not mind posting their feedback with Virtualization I would appreciate it, little detail on your network configuration would be fantastic as well.

    I am looking at setting up three R720 host servers and one R320 Virtualization Domain Controller. The storage device I will be using is a Dell MD3220i.

    Again any feedback would be appreciated. (issues\good\bad etc.)

    -Robert

  • Emerson has announced plans for supporting a virtual environment for production systems based on HYPER-V servers.  This solution will support online switch over of VM's if a VM Host were to fail, using a SAN Device and implementing certain best practices.  After all, this is a DeltaV system, not an IT computing framework.

    The biggest benefit is that Hyper-V role can be enabled on the Server 2008 (R2) OS without additional licensing costs.  The Production architecture will run the servers an HYPER-V 2008 (R2) servers, with the ability to run Windows  OS workstations for DeltaV Operator Stations, and or Server OS for Application Stations or Remote Desktop servers.  New Thin Client devices will support 1, 2 or 4 monitor arrangements, attached to a Worstation VM.  You can implement the virtual workstation and servers on v10, v11 or v12  online systems.

    If you role your own with VMWare and have issues, there could be limitations on what Emerson can do to support you.  I've been playing with the Hyper-V and set up a couple offline systems, and find the 2008 (R2) Hyper V manager easy to use and helpful.  I've also run a pre release of the Virtual Studio and it has some nice features for managing these in the context of a DeltaV control system.  

    Andre Dicaire

  • In reply to Andre Dicaire:

    From what I understand Virtual Studio is just taking the IT side of the environment out and they will not be releasing it with High Available (HA) or DRS until some time after its official release, but I spoke with Bruce and if one is fimiliar enough with virtulization they are giving the blessing for one to make changes directly to hyper-v manager for the features end users are currently looking for.

    Also I believe it is only a matter of time before the give the blessing for VMWare instead of Hyper-V, people are already asking for it.  In their white paper they sates DeltaV releasees are tested in an VMWare environment and are already supported for off-line, non-production applications and have strategic partnerships with both VMWare and Microsoft.  (If you need access to the white paper let me know I can shoot it over.)

  • In reply to ibethebot:

    Hi Ibethebot, i would like to get the whitepaper with the detailed implementation guidelines for using DeltaV in VMware.

    I appreciate it

    Thanks in advance

  • As Andre indicated, DeltaV will be supported in a HyperV environment.
     
    Not to say it doesn’t work in VMWare, but I doubt they will produce a WP for something they don’t support.
     
    From: JavierB [mailto:bounce-JavierB@community.emerson.com]
    Sent: Friday, May 03, 2013 6:44 AM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] Virtualization Delta V (production Environment)
     

    Hi Ibethebot, i would like to get the whitepaper with the detailed implementation guidelines for using DeltaV in VMware.

    I appreciate it

    Thanks in advance

  • In reply to AdrianOffield:

    great place to see documents:

    www.slideshare.net/.../deltav-development-systems-in-a-virtualized-environment

    some "really" old slideshow/white paper

    www.slideshare.net/.../deltav-and-virtualization

    Niklas Flykt 

    Klinkmann Oy

    Key Account Manager safety products

    nikfly@gmail.com

  • I see DVVS supports the use of 9.3 ~ 12.3 DV versions, but can I live migrate an existing 9.3 system to VMs?
     
    Is High Availability supported for other versions or only DV12 (as per the note reference to six month after V12.3 ships)? Failover is a technology of windows so it should be supported for all VM’s.
     
    I can create the same configurations without DVVS, either manually or with System Center VMM, is DVVS really required?
     
     
     
    From: István Orbán [mailto:bounce-Istvan_Orban@community.emerson.com]
    Sent: Friday, May 03, 2013 4:58 PM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] Virtualization Delta V (production Environment)
     
  • In reply to AdrianOffield:

    Adrian,

    As ibethebot stated,  DVVS "is just taking the IT side of the environment out."  Much the same as you could construct a server from all of the component parts if you had the time and expertise, you could likewise manually construct a Hyper-V or VMWare virtual environment.  DeltaV Virtual Studio builds much of the necessary IT expertise into the software, so that you can focus on your process.

    Failover clustering is, as you said, a feature of the Hyper-V Server 2008 R2 hypervisor software.  Live migration and other features of Failover Cluster Manager are not specific to the revision of DeltaV nor the operating system running inside of the virtual machine.

    Converting an existing physical production environment machine to a virtual machine (a "P2V" conversion) can be done using System Center Virtual Machine Manager (SCVMM) or more manually by creating a virtual hard disk (VHD) using other available tools.  It is generally preferable to avoid P2V conversions if possible and construct your virtual machines in their "native" virtual environment.  DeltaV Virtual Studio takes this one step further and utilizes standard template virtual machines for varying DeltaV revisions and base operating systems to deploy new VM's.

  • Thank for the feedback Ben, but that still doesn’t answer the original query about migration or failover in earlier versions. I can see the purpose of DVVS, but as you know us technical guys like to know the “ins and outs” of a technology we will ultimately end up supporting.
     
    What would be the preferred migration practice for a live DV9.3/10.3 installation? I know what options are available but what will Emerson support?
     
    Can I assume from your feedback that failover will actually work in DV9.3/10.3 migrated systems, not just 12.3?
     
     
     
    From: Ben Bishop [mailto:bounce-bbishop@community.emerson.com]
    Sent: Wednesday, May 15, 2013 4:32 PM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] Virtualization Delta V (production Environment)
     

    Adrian,

    As ibethebot stated,  DVVS "is just taking the IT side of the environment out."  Much the same as you could construct a server from all of the component parts if you had the time and expertise, you could likewise manually construct a Hyper-V or VMWare virtual environment.  DeltaV Virtual Studio builds much of the necessary IT expertise into the software, so that you can focus on your process.

    Failover clustering is, as you said, a feature of the Hyper-V Server 2008 R2 hypervisor software.  Live migration and other features of Failover Cluster Manager are not specific to the revision of DeltaV nor the operating system running inside of the virtual machine.

    Converting an existing physical production environment machine to a virtual machine (a "P2V" conversion) can be done using System Center Virtual Machine Manager (SCVMM) or more manually by creating a virtual hard disk (VHD) using other available tools.  It is generally preferable to avoid P2V conversions if possible and construct your virtual machines in their "native" virtual environment.  DeltaV Virtual Studio takes this one step further and utilizes standard template virtual machines for varying DeltaV revisions and base operating systems to deploy new VM's.