under development. • This overview of new technology represents no commitment from VMware to deliver these features in any generally available product. • Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. • Technical feasibility and market demand will affect final delivery. • Pricing and packaging for any new technologies or features discussed or presented have not been determined. Disclaimer 2
isn’t good enough. • Better justification is: – Extended lifecycle – Compatibility (must upgrade to ESXi 6.5 for VSAN 6.5+) – vCenter Server HA – VM encryption 6
upgrade with distinct methodology • Rehost vs rearchitect • It’s not about “the bells and whistles” but meeting the business requirements • Plan the upgrade project end-to-end before beginning implementation • Validate post implementation 7
solution that meets the requirements. Deploy the design in the production environment. Validate the deployment against the design and requirements. Requirements Education and Knowledge Transfer (Ongoing) • Educate stakeholders to provide design input. • Communicate technical and operational changes. 8
should be highly available. • Constraints – Example: vSAN must be used for virtual machine storage. • Assumptions – Example: Organization will continue to purchase vSphere Enterprise Plus licensing • Risks – Example: Staff has not been trained in the use of vSphere Web Client 11
Manageability – Performance – Recoverability – Security • How does your organization rank them, and why? • Use these to drive your design choices and business cases. Availability Security Performance 17
fix issues in infrastructure design. – Design Decision: Old environment gets upgraded; new clusters added are re-architected. – Design Decision: New deployment is configured according to new design; existing infrastructure is re-architected cluster-by-cluster. 18
features can prove value. – Be sure to determine key success criteria at the outset! • Examine operational cost of continuing with old architectures. – Compare to operational cost of deploying new architectures or rearchitecting existing. • Consequences of not upgrading. – Support implications, lifecycle, etc. 19
running vSphere 5.5 across 3 sites. Currently, each site is independently managed. – Requirements: • Manage all sites through a single interface. • Ensure virtual infrastructure components adhere to 10 minute RTO. • Centralized logging in each site. – Constraints: • No additional hardware may be purchased. – Assumptions: • Licensing is available. – Risks: • Staff is not trained to use vRealize Log Insight 22
currently running vSphere 5.5 across 3 sites. Currently, each site is independently managed. – Design Decisions: • Consolidate vSphere SSO domains (must be done prior to upgrading) • Use Enhanced Linked Mode. • Migrate to vCenter Server Appliance • Use vCenter Server High Availability • Deploy vRealize Log Insight
Version Comments vCenter Server 5.5 6.5u1 vCenter Server 6.5a needed for NSX ESXi 5.5 6.5u1 NSX 6.3 6.3.3 Req vSphere 5.5 U3 minimum vRealize Automation 7.0 7.3 Side by side upgrade vRealize Operations Manager 6.0.1 6.6.1 Two steps: 6.0.x to 6.3.1 to 6.6 vRealize Log Insight n/a 4.5 New per requirement
with vSAN within a single site. A new compliance regulation requires user data to be encrypted. All users leverage VDI for desktops. – Requirements: • Adhere to new regulatory compliance. • Centralized monitoring for virtual infrastructure. – Constraints: • Horizon must be used for VDI solution. – Assumptions: • The current number of Connection Servers provides sufficient number of sessions – Risks: • Staff is unfamiliar with vRealize Operations Manager 28
with vSAN within a single site. A new compliance regulation requires user data to be encrypted. All users leverage VDI for desktops. – Design Decisions: • Use vCenter Server High Availability • Deploy vRealize Operations Manager • Install Horizon adapter for vRealize Operations Manager • Leverage vSAN data-at-rest encryption 29