This document discusses VMware hybrid cloud solutions from Datacomm and outlines several use cases. It describes the operational challenges of on-premise and multi-cloud environments and how a hybrid cloud approach addresses these issues through flexibility, scalability, security and consistent operations. Specific use cases discussed include disaster recovery and running SAP workloads on Datacomm's hybrid cloud. It provides details on Datacomm's cloud infrastructure, facilities and certifications.
4. A Modern Data Center is Hybrid Cloud-Ready
4
Flexible and scalableHighly agile Extensive reach
Robust security Consistent operations
5. • Cloud bursting – the ability to move workloads between public and private
resources automatically
• Dynamic scalability – the ability to automatically adjust resource consumption to
data loads as they ebb and flow over time
• Dramatic cost control – the ability to pay for only what you use on a highly
granular basis
• Consistent Infrastructure
• Reduce complexity
• Reduce risk
• Reduce cost
Hybrid cloud advantages
5
7. Increasing capacity, you need perfect amount, not too much, not too little and
in the right places.
• New project
• Locate to new region
• Adding capacity of your new data center
Data Center Expansion
Maintain
Expand
9. Application Migration - moving workload between on premises to vmware
cloud using same vmware technology
• - no complex conversions
• - no alternate machine formats
• - no re-architecting
Application Migration
Consolidate
Consolidate Migrate
10. • seamlessly recover your workloads
• perform non-disruptive DR drill
• on-demand testing anytime
Disaster Recovery
Primary Secondary
12. Consideration
Primary Secondary
Costs Traditional DR Cloud-based DR
Datacenter for Disaster Recovery
(including facilities utility and electrical power
source)
Own manage Cloud Service Provider
Stand-by Hardware System Own manage Cloud Service Provider
Manpower – Network Operation Own manage Cloud Service Provider
Manpower – System & IT Security
Operation
Own manage Cloud Service Provider
Capacity expansion
Own manage
(procurement process + more
hardware to manage)
Easily provided through
flexibility and agility of Cloud
Expense 1.5 – 2X 1.2 – 1.5X
15. 1. RTO less than 10 minutes
2. DR plan
3. DR Drill/Test
4. Resource to run up to 3 days/year
5. More than 3 days will be charge full IaaS services
Deliverables
20. Resources allocation
Jan Feb Mar Apr May Jun Jul Aug Sept Oct Nov Dec
Dev $$ $$ $$ $$ $$ $$ $$ $$ $$ $$ $$ $$
QA $$ $$ $$ $$ $$ $$ $$ $$ $$ $$ $$ $$
Prod $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$ $$$
Jan Feb Mar Apr May Jun Jul Aug Sept Oct Nov Dec
Dev $$ $$ $$
QA $$ $$
Prod $$ $$ $$ $$ $$ $$ $$ $$
On premise
On cloud
22. • On-demand infrastructure as a service (IaaS) for SAP.
• SAP applications for both production and non-production activities.
• IaaS running on Vmware environment – SAP virtualization partner.
• Scalable up to 4TB.
• Supported by HPE systems, the leading SAP hardware provider.
• Deployable on both SUSE Linux Enterprise Server (SLES)m or Red Hat
Enterprise Linux (RHEL) operating system.
• Bring Your Own License
Deliverables
25. • Vmware Infrastructure on Datacomm cloud
o Vmware Vshpere version 6.0
o Vcloud Director version 8.2
o NSX version 6.2
• Local Support and Data center location
• 24x7 Help Desk Support Center
• 24x7 Network Support Center
• 24x7 Security Desk Support Center
Infrastructure & Facilities
26. • Rated 3 Constructed Facilities by TIA-942
• DCOS Maturity 4 by TIA-942
• ISO 9001:2008
• ISO 27001:2013
• ISO 20000:2011
• PCI-DSS
Infrastructure & Facilities
Hinweis der Redaktion
Implementation: Takes time, personnel, and equipment to set up a new environment. Additional hardware/software purchases may be needed.
Support & Maintenance: You are responsible for maintaining the hardware and the application; your IT is responsible for ensuring high availability and disaster recovery. Offers control over your data and provides greater sense of ownership.
Upgrade Cycles: You own the responsibility for upgrades, which are often expensive and time-consuming
Cost: High entry and operations costs compared to cloud due to infrastructure and support staff needs. Ongoing maintenance fee, including building, electricity, cooling. Tangible hardware assets.
Security: Additional time, security team, hardware and software for security required.
Scalability: Needs longterm planning and commitment of resources for scaling.
Complexity: Each cloud has its own operating model due to differences in how each cloud is built and configured. As a result, there is a lack of architectural consistency across different clouds. Support teams must also contend with disparate tools, management consoles, and technologies across the different cloud environments, which contributes to a growing IT “skills gap”.
Cost: Operating across multiple disparate clouds limits economies of scale for the organization and often results in duplicate resources being deployed in different clouds. Additional staff and training may be necessary to support different cloud environments and limited skill sets (the IT “skills gap”) may disrupt business agility, increase time-to-market, and slow operations, resulting in costly downtime.
Risk: Greater complexity increases the risk of improperly or inadequately configured and managed security, compliance, and governance measures.
It’s flexible and scalable, because it is software defined, highly virtualized, highly automated, and ready to scale up, down, and/or out as required
It has consistent operations, providing a consistent operational model for faster and more efficient infrastructure and application delivery and management.
It has extensive reach, giving you the ability to seamlessly extend your reach across private and public clouds and manage those resources and costs as one.
It’s highly agile, supporting cloud-native apps, container technologies, and microservices-based architectures to drive faster innovation and enable rapidly changing systems at scale.
It has robust security, helping you protect data, applications, and infrastructure and meet your compliance requirements.
– The customer site must be running vSphere 6 Update 3 or later (6.5.0 and 6.5 Update 1 are also both supported).– If the customer wishes to use L2VPN network extension and is already running VMware NSX, this must be v6.2.8 or v6.3.2.– The cloud provider must be running vCloud Director v8.20 or v9.0.
– The customer site must be running vSphere 6 Update 3 or later (6.5.0 and 6.5 Update 1 are also both supported).– If the customer wishes to use L2VPN network extension and is already running VMware NSX, this must be v6.2.8 or v6.3.2.– The cloud provider must be running vCloud Director v8.20 or v9.0.