MCooperAUS
1 Nickel

FEHC Mandatory Components

Jump to solution

HI All,

More of a learning topic than anything from me.  With FEHC covering VSPEX, VBlock and BYO, the lines are a little blurred for me in understanding what a customer actually needs to deploy a fully legitimate and supported FEHC???

I understand that an EHC solution is an engineered solution consisting of reference architectures for virtualization orchestration and storage, as well as blueprints and workflows for automation which enables a customer to build a hybrid cloud in 28 days, but WHAT does a customer need from a supporting infrastructure and VMWare layer to tick the federation boxes?


Further to the above, I also understand the Core, Automation and NEI pods in the FEHC architecture but can't find anything definitive that lists what components of these PODs HAVE to be deployed as part of a FEHC on VSPEX, VBlock or BYO.  Is it all of them, is it part of them?

The FEHC architecture comprises the following elements:

  1. VMware: vRealize Automation, vRealize App Services, vRealize Orchestrator, vRealize Operations, vRealize Business Standard, vRealize LogInsight, NSX or vCNS, vSphere, vCloud Air.
  2. EMC: ViPR Controller, EMC Storage Analytics (ESA), EMC ViPR Analytics, Data Protection Advisor, Avamar, RecoverPoint, VPLEX with customer integration workflows for ViPR, Avamar & DPA.
  3. Built on VCE Vblock, VCE VxBlock, EMC VSPEX or the Customers Choice Of EMC Infrastructure (VNX, VMAX, VMAX3, XtremIO, ScaleIO, Isilon for HDFS)

If a customer has a VSPEX deployment on VNX with VMware but does not have LogInsight and ViPR, do they need these to deploy a "certified FEHC"?  If they do, are these components supplied as part of a FEHC solution or do they procure these through other avenues?

I am just trying to get my head around the actual implementation of FEHC and the mandatory components that a customer needs to deploy this.  I hope I am over complicating this and there is a simple solution

Thanks in advance.

Michael

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
Sanzone1
1 Nickel

Re: FEHC Mandatory Components

Jump to solution

Here's some info that may help clarify the solution a bit for you...

1.  The foundation solution is not installed or implemented by the customer, but but the EMC (or certified EHC partner) in conjunction with our highly prescriptive build process.  The existing VSPEX implementation would need to be validated by the services teams to ensure that it meets the needs and requirements of the solution before the implementation of the cloud solution.

2.  To see wha the physical resource requirements are, the best starting point is the currently published reference architecture docuementation, avaialble HERE:

     http://www.emc.com/collateral/technical-documentation/h13531-eehc-federation-sddc-ra.pdf

3.  As to what's required, in order to get the full value of the solution, it's highly recommended that you deploy the entire suite.  There are several elements of the solution that are highly recommended , but could be removed. It's important to understand the loss of functionality for each element that's removed.

  • LogInsight can be removed, given the loss of he integrated reporting and logging functionality that's important to managing the cloud infrastructure.
  • NSX can be removed, given a pretty significant loss of functionality around the security and micro-segmentation features of the solution.  Also, the DR Infrastructure Extensions do require NSX.
  • vCloud Air is an option for customers who want to extend to the public cloud, but is not required.
  • vRealize Operations and the associated management packs could "technically" be removed, but that's a HUGE loss to the ability to monitor and manage the solution as a while.
  • vRealize Automation, vRealize Business, vCenter Orchestrator, AppServices, vSphere are all required elements and cannot be removed.
  • ViPR Controller, PowerPath/VE (for block storage), EMC validated Storage Arrays, are required elements.
  • Avamar, Recoverpoint, VPLEX, and DPA are optional elements that are referred to as "Modular Add-Ons"

I sure hope this helps.  It's a complicated topic as there are many parts to this solution.  Best bet for additional info would be to connect you with a local vSpecialist to dive deeper on the solution architecture and what's required, especially in the context of your pre-existing VSPEX environment.  Glad to help with that if need to make a connection.

jim

3 Replies
Sanzone1
1 Nickel

Re: FEHC Mandatory Components

Jump to solution

Here's some info that may help clarify the solution a bit for you...

1.  The foundation solution is not installed or implemented by the customer, but but the EMC (or certified EHC partner) in conjunction with our highly prescriptive build process.  The existing VSPEX implementation would need to be validated by the services teams to ensure that it meets the needs and requirements of the solution before the implementation of the cloud solution.

2.  To see wha the physical resource requirements are, the best starting point is the currently published reference architecture docuementation, avaialble HERE:

     http://www.emc.com/collateral/technical-documentation/h13531-eehc-federation-sddc-ra.pdf

3.  As to what's required, in order to get the full value of the solution, it's highly recommended that you deploy the entire suite.  There are several elements of the solution that are highly recommended , but could be removed. It's important to understand the loss of functionality for each element that's removed.

  • LogInsight can be removed, given the loss of he integrated reporting and logging functionality that's important to managing the cloud infrastructure.
  • NSX can be removed, given a pretty significant loss of functionality around the security and micro-segmentation features of the solution.  Also, the DR Infrastructure Extensions do require NSX.
  • vCloud Air is an option for customers who want to extend to the public cloud, but is not required.
  • vRealize Operations and the associated management packs could "technically" be removed, but that's a HUGE loss to the ability to monitor and manage the solution as a while.
  • vRealize Automation, vRealize Business, vCenter Orchestrator, AppServices, vSphere are all required elements and cannot be removed.
  • ViPR Controller, PowerPath/VE (for block storage), EMC validated Storage Arrays, are required elements.
  • Avamar, Recoverpoint, VPLEX, and DPA are optional elements that are referred to as "Modular Add-Ons"

I sure hope this helps.  It's a complicated topic as there are many parts to this solution.  Best bet for additional info would be to connect you with a local vSpecialist to dive deeper on the solution architecture and what's required, especially in the context of your pre-existing VSPEX environment.  Glad to help with that if need to make a connection.

jim

MCooperAUS
1 Nickel

Re: FEHC Mandatory Components

Jump to solution

Thanks Jim for your response,

Greatly appreciated!

Best Regards,

Michael C

Mobile (+61) 402-105-686

Twitter: @MCooperAus

0 Kudos
stevefulmer
1 Nickel

Re: FEHC Mandatory Components

Jump to solution

Jim, Thanks I am sharing this with my team.Great knowledge.

0 Kudos