AWS re:Invent 2021 - A technical deep dive on VMware Cloud on AWS Outposts (sponsored by VMware)
AWS re:Invent 2021 - A technical deep dive on VMware Cloud on AWS Outposts (sponsored by VMware)
Learn how to bring cloud experience, agility, and innovation to the data center so that you can focus on business innovation, while VMware and AWS take care of managing your on-premises IT infrastructure. VMware Cloud on AWS Outposts is an on-premises-as-a-service offering powered by VMware Cloud Foundation. It integrates VMware’s enterprise-class Software-Defined Data Center software with next-generation, dedicated Amazon Nitro-based Amazon EC2 bare metal infrastructure. This session provides an overview of the service and its key use cases; technical specifications for VMware Cloud on the AWS Outposts rack; a description of the network topology, architecture, and order flow; a walkthrough of how to get started; and much more. This presentation is brought to you by VMware, an AWS Partner. Speakers: Ivan Oprencak (VMware) and Larry Henderson (VMware)
Learn more about re:Invent 2021 at https://bit.ly/3IvOLtK
Subscribe:
More AWS videos http://bit.ly/2O3zS75
More AWS events videos http://bit.ly/316g9t4
ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.
AWS is the world’s most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.
#AWS #AmazonWebServices #CloudComputing
Content
0.375 -> (upbeat music)
11.1 -> - Hello, my name is Ivan Oprencak,
12.49 -> and today I'm gonna be talking about
13.903 -> a technical deep dive on
VMware Cloud on AWS Outposts.
17.9 -> I'm a senior director here at VMware,
19.89 -> responsible for product marketing
for VMware Cloud on AWS.
23.58 -> Joining me today is Larry Henderson,
25.4 -> who's a senior product manager at VMware,
27.57 -> also covering the VMware Cloud
on AWS Outposts solution.
31.78 -> What we're gonna cover
in this presentation
33.33 -> is provide you a general
overview of the solution,
36.14 -> some of the business problems it solves,
37.75 -> and the value that it delivers
40.68 -> to the customer, key use cases,
41.94 -> and then Larry's gonna cover
43.87 -> more of the technical
deep dive on the solution.
48.66 -> So with that, let me get started.
52 -> Now, just to step back and provide context
54.12 -> for what we're doing at
VMware Cloud on AWS Outposts.
56.613 -> When we're looking across our customers
58.93 -> and across the industry,
60.71 -> we see a large number of initiatives
62.49 -> that can be summarized on
their digital transformation.
65.37 -> And this is something that customers
66.863 -> have been doing for a number of years,
69.2 -> but with the pandemic over the
last year and a half or so,
71.84 -> these initiatives have accelerated
74.19 -> because many customers had to convert
75.92 -> their physical processes that they have
78.38 -> into a virtual one, into digital ones,
80.32 -> and that's accelerating
how quickly customers
83.31 -> are adapting different
digital technologies.
86.18 -> In fact, when we look at
87.69 -> the entire direct digital transformation
91.59 -> as a market, as an industry,
93.48 -> it's estimated to be almost $7 trillion
96.27 -> and growing about 16% year over year
98.74 -> over the next couple of years.
101.05 -> Now, the area of digital transformation
103.73 -> covers a large number of technologies,
106.08 -> and delivering modern IT infrastructure
109.19 -> is one of the core pillars
of this transformation,
112.22 -> and VMware Cloud on AWS Outpost
114.18 -> is a product and service and a technology
117.13 -> that fits into this area.
120.61 -> Now, when we look at
digital transformation,
123.91 -> there are number of different
technical transitions
128 -> and technology transitions
that are happening,
130.53 -> public cloud infrastructure
132.28 -> has been a key enabler of
digital transformation.
136.107 -> The cloud delivers customers
innovative services,
138.78 -> it delivers customers agility,
140.69 -> it delivers them a lot more flexibility
143.19 -> in terms of how they're
running their applications
145.55 -> and how they're paying
for their applications,
148.24 -> whether it's through the ability
149.27 -> to scale on demand very quickly,
151.34 -> whether it's outsourcing the
operation to a cloud provider,
155.16 -> whether it's taking advantage
157.44 -> of a very granular cloud
consumption models,
160.35 -> or accessing innovative services,
162.59 -> these are the key capabilities
that cloud delivers
165.63 -> to ensure that customers
can quickly and efficiently
170.58 -> go through their digital transformation,
172.16 -> deliver those applications
much more efficiently
174.71 -> to their end customers.
176.49 -> One of the examples of this
is VMware Cloud on AWS,
179.23 -> which is a joint offering
180.26 -> that we had between VMware and AWS
182.99 -> that released a few years
ago into the market,
185.03 -> and it provides all these key capabilities
186.88 -> that I just talked about.
190.81 -> Now, despite a cloud being
one of the key enablers
195.87 -> and being a key technology
in digital transformation,
200.81 -> there is number of different
reasons as to why applications,
206.26 -> there's gonna be number of applications
207.253 -> that still need to run on premises.
211.33 -> Some of the reasons are
listed in this slide,
213.16 -> and essentially, the key ones,
215.41 -> there are applications that
will require low latency,
218.87 -> they might be sitting next to devices
220.66 -> that are generating and consuming data,
223.37 -> the response to those devices
needs to be very quick.
226.29 -> And so applications that require
229.01 -> these slow latency requirements
230.81 -> cannot be sitting on the
other side of the VEN,
232.93 -> to be able to do that,
they need to be local,
234.41 -> they need to be next to those devices,
236.35 -> next to those data sources and data syncs,
238.27 -> so that's one of the requirements.
240.08 -> The other one, there is
number of regulatory mandates
244.92 -> and compliance needs that
require for applications
248.92 -> to be sitting within specific
geographic boundaries,
252.04 -> or within a specific location,
254.68 -> and these data sovereignty,
these regulatory reasons
257.91 -> are another reason why application
260.39 -> needs to stay on premises.
262.39 -> And another big reason is,
264.69 -> certain applications
either generate or consume
267.39 -> large amount of data,
268.35 -> it would be prohibitively
expensive and time consuming
271.02 -> to send this data over
a VEN link to a cloud,
273.62 -> and applications that do have these,
276.35 -> that do generate these
large volumes of data,
279.53 -> need to be sitting close
to where that data piece
281.76 -> is being produced or consumed.
284.17 -> So these are some of the three reasons
285.66 -> that we see why applications
287.31 -> still continue running on premises.
292.61 -> Now, however of it, all the innovations
297.88 -> and all the market transitions
300.39 -> that have been happening in cloud,
303.14 -> our customers are demanding
that some of that innovation,
306.1 -> where appropriate and
where it makes sense,
308.69 -> is actually available on premises.
310.7 -> And there is another trend going on
313.15 -> across the technology industry
316.2 -> where cloud capabilities
and cloud operating models
320.28 -> are coming back on premises,
321.73 -> and in fact, the industry analysts
323.51 -> are predicting that this is going to be
325.57 -> the next big thing, the next big trend,
328.1 -> where customers are consuming cloud
332.68 -> in a distributed fashion,
334.83 -> and applications live
whichever environment
340.01 -> best meets those
applications' requirements.
342.98 -> And those applications
might be distributed,
344.72 -> whether they're in someplace
on centralized cloud,
346.807 -> whether they're at an edge location
348.219 -> or they're sitting in a data center.
350.21 -> So the ability to deliver
local cloud infrastructure
354.01 -> is one of the key trends
that we're seeing.
356.68 -> In fact, analyst IDC is predicting
360.58 -> that this is gonna be almost
an $8 billion market by 2025,
365.21 -> it shows delivering this
dedicated cloud infrastructure
368.39 -> as a service, on premises
or at edge locations.
375.2 -> Now, VMware and AWS have
jointly collaborated
379.61 -> to deliver offerings to our customers
382.31 -> that essentially enable
them to deploy applications
385.94 -> wherever those applications'
requirements are best met,
389.75 -> and specifically by delivering
391.96 -> number of hybrid cloud solution services
396.4 -> and offerings to the market.
399.36 -> We started this partnership
about five years ago,
401.59 -> initially we focused on
taking VMware technologies
404.23 -> and delivering them in AWS data centers,
405.84 -> this is the VMware Cloud on AWS offering.
408.95 -> And over time, we grew that in
terms of making it available
412.54 -> to our public sector customers
417.08 -> and making sure that AWS customers
419.55 -> can also purchase it through AWS,
421.51 -> and then really declaring that AWS
425.63 -> is VMware's preferred public partner,
429.93 -> and likewise is VMware Cloud on AWS
432 -> is AWS's preferred service
for vSphere-based workloads.
436.3 -> And just about a month ago,
438.94 -> we are happy to announce that
VMware Cloud on AWS Outposts,
442.79 -> which is our on-prem offering,
444.14 -> is now general available to our customers.
446.86 -> And essentially what we're trying to do
447.933 -> with all these offerings and
all these services that we have
450.84 -> is deliver best of what
VMware has to offer,
453.88 -> the leader in on-premises
data-center technologies,
458.59 -> together with the leader in public cloud,
460.8 -> taking best of those technologies
and essentially delivering
464.42 -> the best of both worlds to our customers,
466.68 -> whether they're looking at
467.64 -> they're on-public-cloud footprint,
470.01 -> or they're looking at
on-premises footprint,
471.68 -> and now VMware Cloud on AWS
Outposts, joining them together,
474.6 -> delivering a deeply integrated
hybrid cloud solution.
479.76 -> Now, that's kind of it generally
480.98 -> in terms of what's
going on in the industry
482.78 -> and a bit about our
collaboration on this offering,
486.67 -> now, just to provide a
little bit of an overview
489.21 -> of VMware Cloud on AWS Outposts,
491.13 -> and Larry will talk
through all the details.
493.3 -> So let me just lay it out here,
495.93 -> so what we've done with
VMware Cloud on AWS Outposts,
498.21 -> we have taken the VMware
software-defined data center,
500.953 -> this is our compute storage
networking, vSphere NSX vSAN,
505.29 -> along with vCenter
management, is running on top
509.18 -> of the bare metal AWS
Outposts infrastructure,
514.3 -> the bare metal instances,
and it's running on premises.
517.9 -> Now, because it's VMware on bare metal,
519.92 -> customers get the same performance,
521.33 -> scalability, resilience, security
523.43 -> that are accustomed
for having from VMware,
525.51 -> but they're getting it on
526.44 -> the next-generation,
high-performance hardware
529.05 -> from AWS on the bare metal
AWS Outposts hardware.
533.05 -> Now, this is a fully managed service,
535.153 -> with VMware being a single
point of contact for support,
539.613 -> AWS is involved in that it
provides proactive monitoring
542.64 -> on the hardware, and we'll
talk about those details later,
544.71 -> but it is a fully managed service.
549.21 -> Now, this infrastructure,
because it's based on VMware,
552.673 -> it's the same technologies
and capabilities
555.82 -> customers are running on premises,
558.546 -> and customers get that
consistency and familiarity
562.22 -> with what they were
running out on premises,
563.61 -> now they get it with VMware Cloud on AWS,
566.461 -> and Outposts running on AWS hardware.
570.35 -> Because it's the same infrastructure base,
572.14 -> customers can also easily migrate,
574.91 -> port, move over to their workloads
576.55 -> into VMware Cloud on AWS Outposts
578.51 -> and to other VMware-based environments
582.04 -> should they choose to do so,
583.43 -> that's enabled with VMware HCX,
586.09 -> which is our cloud-to-cloud
interconnect technology
588.07 -> that essentially allows customers
589.47 -> to migrate large number
of application at scale,
594.29 -> without any changes,
595.36 -> in fact, they can move running
applications using vMotion
599.84 -> from one environment to the other,
601.28 -> including VMware Cloud on AWS Outposts.
604.844 -> Now, even though it's
VMware running on hardware,
611.49 -> we also wanted to make sure
612.87 -> that some of the key characteristics,
616.7 -> some of the key attributes
and features of the cloud
618.77 -> are present in this offering,
620.53 -> and so the notion of you
providing resilience,
623.67 -> you providing a degree of
scalability on premises
626.95 -> is preserved in this offering,
628.48 -> and we'll talk about the
details a little bit later.
632.47 -> One of the key advantages,
634.86 -> one of the key benefits that we've done
636.96 -> with this environment is integrated back
639.41 -> with what is running in the AWS Cloud,
642.48 -> specifically VMware Cloud on AWS,
645.27 -> that gives our customers the ability
647.64 -> to easily scale their capacity
649.7 -> should they wanna go from
on premises into cloud,
652.44 -> as well as it gives them access
654.4 -> to over 200-plus regional services
658.06 -> that AWS is providing,
659.42 -> so they can enrich their applications
661.63 -> or they can take advantage
of these services.
665.12 -> Overall, probably the best way
666.61 -> of thinking about this offering is
669.23 -> single, fully manage end-to-end
hybrid cloud as a service
674.55 -> where you have fully compatible
software on both sides,
678.62 -> where it's public and private cloud,
680.36 -> and you have the same operator
682.32 -> of that service on both sides,
684.02 -> so full end-to-end managed hybrid cloud
687.93 -> as a service.
690.4 -> The other reason is around
delivering the VMware software
694.67 -> on top of next-generation
AWS Outposts hardware.
698.93 -> What we're leveraging is
700.16 -> the high-performance
Nitro-based bare metal
703.09 -> that Amazon has available.
706.79 -> This infrastructure has been built in
708.843 -> with additional dark note capacity,
711.22 -> essentially there's capacity
714.23 -> within the racks that we're offering
715.8 -> that allows us to provide
additional level of resiliency
719.13 -> and built-in redundancy doing so.
723.19 -> The Nitro System has been designed
725.06 -> from ground up to be secure
726.69 -> and have additional levels
of security controls,
731.01 -> so it's a very secure environment.
733.16 -> And then because it's VMware
software-defined data center
737.05 -> with all the capabilities
738.15 -> that we're offering for developers,
739.89 -> it is a infrastructure
that customers can procure
744.06 -> and make very quickly
available to their developers.
748.17 -> And it can get this
infrastructure procured
750.01 -> in matter of weeks and they
don't have to spend months
752.87 -> assembling, reading it
and putting it together,
755.65 -> so we allow them to essentially get
758.06 -> a developer infrastructure
on a very short timeframe.
764.76 -> And then finally, when you
look at the hybrid cloud,
768.87 -> VMware Cloud on AWS, traditionally,
772.33 -> by being able to connect
773.45 -> to VMware infrastructure on premises
775.07 -> created the hybrid cloud.
776.44 -> However, with that hybrid cloud,
777.73 -> customers still manage their
on-premises infrastructure
780.61 -> and the capability of that infrastructure
782.45 -> might've been very different.
783.94 -> Now, with VMware Cloud on AWS,
785.19 -> you're essentially getting
the same VMware SDDC
788.603 -> that is hosted in VMware Cloud on AWS,
790.95 -> now you're getting it
791.783 -> on top of the AWS Outposts
hardware on premises,
794.85 -> so that gives you a
consistent capabilities
797.99 -> across these different environment,
799.6 -> but it also gives you the same operator
803.17 -> that's running your public cloud
804.44 -> is now also running your private cloud,
806.57 -> and essentially the entire thing
808.49 -> can think of it as a hybrid cloud,
809.98 -> as a servicing operational
consistency end to end,
813.68 -> and you get the familiar
tools on both sides,
816.22 -> and you can use the same
skill sets that you have.
820.21 -> Because of this consistency
821.35 -> and because of the compatibility
822.38 -> between the different
environments, it allows you
824.02 -> to provide easy, bi-directional
application mobility,
828.79 -> it can easily extend to cloud
830.73 -> if you need additional capacity,
832.76 -> and the entire
environment's been validated
836.05 -> for a large number of
third-party solutions
839.12 -> from our partner ecosystem,
840.4 -> we have over 300 validated solutions
842.74 -> that run both on the VMware Cloud on AWS,
845.298 -> on Outposts, on premises,
846.43 -> as well as in VMware Cloud on AWS itself.
850.7 -> So these are kind of the
three reason at a high level,
853.24 -> and we'll kind of go into
more technical details
855.74 -> a little bit later.
858.32 -> Now, when we look at
the specific use cases
860.17 -> for this service, I would bucket
them into three categories.
863.27 -> The first category
addresses some of the needs
865.51 -> that I talked about earlier,
866.84 -> which is customers have a need
868.59 -> to run applications on premises
870.32 -> because of low latency requirements,
872.7 -> because they need to process data locally,
874.81 -> or because there is mandatory,
878.13 -> or policy mandates and compliance mandates
883.51 -> that they need to follow
884.83 -> where the data cannot
move specific locations.
887.17 -> So that's one very clear reason
889.35 -> why you might need to
have local applications.
893.67 -> The other reasons, our customers,
896.08 -> we have a large number of
customers that are cloud first
900.75 -> and wanna move all their
applications to cloud over time,
903.06 -> but also we do have a relatively
large number of customers
906.23 -> that continue to stay on premises
908.07 -> and they wanna use
cloud very strategically
910.29 -> for very specific reasons.
912.15 -> One of the reasons that
they wanna use cloud for
914.55 -> is to be able to, for example,
916.97 -> very quickly scale their capacity.
919.1 -> So customers that are essentially looking
921.46 -> to make their on-premises data center
925.21 -> more elastic, more scalable,
927.8 -> can use VMware Cloud on
AWS Outposts to do so,
930.98 -> because it connects to VMware Cloud on AWS
933.36 -> and that gives you the ability
935.04 -> to rapidly scale the
infrastructure, should you need to,
939.65 -> failures on premises,
things that don't go right,
941.63 -> you can fail workloads over
into VMware Cloud on AWS,
944.88 -> so it gives you that
additional level of resiliency.
949.03 -> And then finally,
949.863 -> if you wanna develop
applications for the cloud,
952.21 -> you can start building them on premises,
953.9 -> and then over time, migrate
them to VMware Cloud on AWS,
956.7 -> so essentially it gives you
that cloud-ready infrastructure,
959.41 -> essentially this is the use case
961.42 -> for a deeply integrated hybrid cloud.
965.16 -> And then the final use case
966.28 -> that we see across our customers
967.62 -> is customers that are looking specifically
969.91 -> at application modernization initiatives,
973.15 -> with VMware Cloud on AWS Outposts,
974.81 -> they'll get the latest, most up-to-date,
977.88 -> most capable both hardware,
as well as software,
981.16 -> so it allows them to
modernize that infrastructure,
982.99 -> it gives them those abilities.
984.7 -> And then on top of this infrastructure,
986.12 -> they can use AWS services to
modernize the applications,
990.24 -> and should they choose to later
on move them to the cloud.
993.3 -> And finally, for branch office locations
996.6 -> that are large in size,
999.17 -> it gives them an option to
modernize those locations
1003.38 -> with an offering that is being
managed by VMware and AWS.
1009.13 -> So those are some of the use cases
1010.91 -> that we've seen across
the VMware Cloud on AWS
1013.88 -> customers' early interests.
1019.49 -> Now, in terms of what this offering
1022.18 -> helps our customers to do,
1024.01 -> we kind of bucketize into three things.
1026.27 -> So first, it allows them
1027.56 -> to uplift their infrastructure operations,
1030.31 -> because VMware is managing
the VMware software,
1034.92 -> AWS is proactively
monitoring the hardware,
1037.69 -> the low-level infrastructure manage
1039.89 -> has been essentially outsourced
1041.3 -> to the people that have
created the infrastructure,
1043.792 -> so you're getting the world experts,
1045.16 -> the people that created
this managing it for you,
1048.28 -> that reduces the overhead of
what the local teams need to do
1051.24 -> in terms of managing that infrastructure,
1054.37 -> allows them to focus on
more strategic priorities,
1056.81 -> and because you have the people
1059.01 -> that are essentially creating
1060.61 -> this infrastructure managing it,
1062.02 -> it does improve security and reliability
1064.23 -> of that infrastructure.
1066.05 -> The other business benefit,
1068.25 -> the other business outcome
we've seen from customers
1070.83 -> is the ability to transform
1072.43 -> into a more agile infrastructure,
1074.34 -> definitely been hybrid cloud,
1075.48 -> you can easily scale to cloud
1077.48 -> much, much quicker and
much more seamlessly.
1080.18 -> And there is a single operator model,
1082.69 -> whether it's public,
whether it's on premises,
1084.28 -> that improve its efficiency.
1085.89 -> And because this is a turnkey
solution that comes packaged
1089.6 -> and it gives the I&O teams the ability
1092.93 -> to stand up the infrastructure
much more quicker
1095.76 -> and deliver it much more
easier to the developers.
1099.08 -> And then finally,
1100.19 -> as I kind of started off in the beginning
1102.17 -> talking about digital transformation
1103.61 -> as being one of the key
initiatives going on,
1105.94 -> this particular offering
helps our customers
1108.01 -> accelerate those digital
transformation initiatives
1110.82 -> by being able to run with
next-gen applications
1113.45 -> much more quicker,
accelerate that delivery.
1117.96 -> Over time, we'll deliver containers
1121.44 -> on top of this infrastructure
1122.69 -> and allows customers to
improve their CI/CD pipelines,
1125.86 -> and then leverage the
expertise of VMware on AWS
1130.78 -> in terms of operating that infrastructure
1133.53 -> and gain more efficiencies
1135.59 -> and accelerate the delivery
of infrastructure services
1139.01 -> to the application consumers
1141.16 -> and to the applications
team within the company.
1144.83 -> So with that, that concludes
the high-level overview
1148.17 -> of the VMware Cloud on AWS Outposts,
1150.39 -> and at this point, I'll pass it to Larry
1152.66 -> to talk about the more technical details.
1155.68 -> - Thanks for that transition, Ivan.
1157.98 -> So we're gonna go ahead and get started
1159.63 -> regarding the countries that are supported
1161.18 -> for VMware Cloud on AWS Outposts.
1163.935 -> As you can see here,
1164.768 -> we're actively setting in the US region,
1168.2 -> and other regions are
available upon request.
1171.57 -> If you want to be attributed
1173.51 -> to these available regions upon request,
1175.89 -> or you do not see your region
or country on this list,
1178.84 -> please reach out to your
VMware or AWS representative
1182.05 -> as additional regions and
countries can be supported.
1188.86 -> In terms of the packaging for
VMware Cloud on AWS Outposts
1192.6 -> for hardware and software,
1194.05 -> comes with an AWS Outposts 42U rack,
1196.96 -> dedicated Nitro-based
Amazon EC2 instances,
1200.43 -> the VMware software
stack, in terms of SDDC,
1203.71 -> and VMware ACX can be included.
1206.61 -> For the services, the
VMware-managed SDDC software,
1209.603 -> the VMware Cloud Console,
1211.93 -> and then operated by VMware SREs.
1216.04 -> Amazon-managed Outposts infrastructure,
1218.32 -> the supply chain and
logistics is done by AWS,
1221.29 -> and then also ongoing monitoring
1223.17 -> for hardware support for
break-fix is done by AWS.
1227.57 -> For support, VMware is
the main point of contact.
1232.419 -> AWS support through VMware
directly for our customer,
1235.46 -> for the purchase of hardware break-fix.
1238.24 -> The options for purchasing
1239.89 -> is a three-year
subscription-based pricing,
1243.198 -> the choice of paying through SPP credits,
1245.64 -> the minimum for host
purchase is a three-year,
1249.25 -> sorry, a three-hosts,
1251.33 -> purchase up to eight hosts.
1253.15 -> It also comes with dark capacity
1254.537 -> for the purposes of auto-remediation,
1256.513 -> LCM and EDRS scale out.
1260.277 -> And yes, we can see here,
pricing is available online.
1263.89 -> For the technical specs for compute,
1266.32 -> it comes with the instance
side with i3en.metal.
1269.5 -> As stated, three through
eight host configurations.
1272.52 -> And also as stated, dark capacity
for the purchase of EDRS,
1276.38 -> auto-remediation,
1277.62 -> and then also lifecycle
management purposes.
1281.44 -> Storage and compute, up to
45 terabytes of raw capacity,
1285.38 -> up to 40 terabytes of usable storage,
1288.02 -> depending on your RAID and FTT settings,
1290.44 -> 768 gigs of RAM, 48 physical cores,
1294.5 -> and up to 96 logical cores.
1298.61 -> For networking, connectivity
to the AWS local region
1302.56 -> via public internet,
1303.7 -> or AWS Direct Connect via
private or public VIF,
1306.8 -> which we'll get to a little bit later.
1309.63 -> Connectivity to your local
on-premises environments
1312.3 -> using the LGW construct,
1315.51 -> and then connectivity to
the AWS regional services
1318.42 -> using constructs SDDC, ENI, or
a network elastic interface,
1323.96 -> and then also VMware Transit Connect.
1327.71 -> So what's in the rack?
1329.2 -> As stated, an industry standard 42U rack,
1331.93 -> it gets fully assembled
1333.29 -> and ready to be rolled
into final position by AWS.
1336.53 -> Installed by AWS, simply
plugged into power and network.
1339.86 -> It comes with redundant
power conversion units
1342.16 -> and also redundant active
top-of-rack switches.
1345.33 -> And also, as stated before,
1346.91 -> the standby nodes, or dark capacity
1348.69 -> for the purpose of the maintenance,
1350.35 -> auto-remediation, EDRS,
1352.7 -> and then lifecycle management.
1356.52 -> Here's a view of the rack,
1357.89 -> so as stated, a 42U rack,
1359.68 -> as you can see here in the middle,
1360.651 -> in terms of the patch panels
showing the optical options
1364.07 -> for one, 10, 40, and 100-gig uplinks,
1367.277 -> the network switches and hosts.
1369.7 -> And then in terms of the power,
1371.23 -> consumption of power availability,
1373.45 -> it supports up to five to
15 kVA for power supply,
1377.27 -> and we'll go into the configurations
1378.85 -> associated with that later.
1381.09 -> Security on the rack,
1383.23 -> it comes with built-in tamper detection,
1385.4 -> it's an enclosed rack
with a lockable door.
1388.15 -> All the data on an Outpost is encrypted,
1390.35 -> comes with a removable and
destroyable security key.
1394.08 -> Encrypted network connection
back to the AWS Region.
1397.71 -> And the physical security
1399.34 -> is the responsibility of the customer,
1401.14 -> in terms of securing the Outposts rack
1403.5 -> in their data center or colo facility.
1406.63 -> There's also network encryption
1407.97 -> between the nodes in the Outposts.
1410.15 -> And it comes with a
destroyable destruction key,
1414.02 -> if you need it in this case.
1417.74 -> The deployment model for
VMware Cloud on AWS Outposts
1420.82 -> is the same as VMware Cloud on AWS,
1423.06 -> where a customer deploys their instances
1425.11 -> in terms of the VMware shadow account
1426.92 -> associated with an AWS Region.
1429.95 -> For communication from the
Outposts back to the AWS Region,
1433.34 -> it's this piece called the service link,
1434.93 -> which is responsible for
control plane traffic,
1437.11 -> and then also data plane
traffic if need be.
1441.36 -> For that service in connectivity
1442.82 -> and connecting back to the region,
1445.07 -> what we'll call regional connectivity,
1447.67 -> the communication back to AWS
1449.23 -> can be done over the public internet,
1450.92 -> which I stated before, has
an encrypted connection,
1453.17 -> or can be done over AWS Direct Connect
1455.46 -> via private or public VIF.
1459.1 -> For local communication,
1460.56 -> there is an additional construct
called the local gateway,
1462.81 -> which allows the communication
1464.17 -> associated with the AWS Outposts rack,
1466.22 -> or in this case, the VMware
Cloud on AWS Outposts solution,
1469.17 -> to communicate with the
customer's local infrastructure.
1472.14 -> As you can see here on the
left, having the NSX construct
1475.29 -> so the compute gateway,
management gateway, T0,
1478.29 -> and then the physical
top-of-rack switches,
1480.8 -> the local gateway is the responsibility,
1482.97 -> or it gives the responsibility
to allowing communications
1485.73 -> to communicate with the
customer's local infrastructure.
1488.52 -> One additional requirement here
is to use link aggregation.
1492.73 -> So here's an example of the
setup, so you can see here,
1495.9 -> in terms of VMware Cloud
on AWS Outposts rack,
1498.17 -> with the NSX constructs,
the local gateway,
1500.93 -> the AWS top-of-rack switches,
1502.57 -> and then in this case,
1504.2 -> using BGP for a point-to-point connection
1506.71 -> for the purpose of the service link.
1508.32 -> And then servicing communication
going back to the region
1511.25 -> via either internet,
or AWS Direct Connect,
1513.97 -> or using a local gateway path
1516.02 -> for communication going locally
1518.01 -> to the customer's local infrastructure
1519.33 -> or workloads, per se.
1524.71 -> So deployment requirements
and availability.
1529.72 -> So when bringing in an Outposts rack
1532.64 -> to a customer's data center,
1534.05 -> there is additional requirements
that are associated,
1536.58 -> so HVAC, facility, and also
additional power requirements.
1539.72 -> So as you can see here,
temperature and humidity,
1542.4 -> airflow, loading dock, weight support,
1545.41 -> and in the case of power,
as we stated before,
1547.68 -> the support for five to 15 kVA.
1551.93 -> For our customers to be
able to bring the solution
1553.813 -> to their data center,
1554.87 -> all these requirements must be met,
1556.95 -> and AWS will actually
be doing a site survey
1559.25 -> to go ahead and validate
these requirements
1561.68 -> before actually building the rack
1563.069 -> and delivering it to a customer's site.
1568.32 -> Next, we have the network requirements,
1570.42 -> as stated before,
regarding the service link,
1573.33 -> you have an option of doing internet
1575.88 -> or doing the encrypted
connection for the service link
1578.04 -> back to the region over internet,
1579.76 -> or using AWS Direct Connect
via private or public VIF.
1584.31 -> You'll need dedicated VLANs
for the purposes of BGP,
1587.179 -> for the purpose, or for a service link,
1589.3 -> and also a local gateway communication.
1591.93 -> You'll need dedicated subnet or a /26
1594.27 -> for the purpose of
service and communication.
1597.27 -> There's also a dedicated
subnet for management
1599.49 -> or VMC management, which
is a minimum of a /23.
1603.37 -> Just like VMware Cloud on AWS,
1604.72 -> there'll need to be a VPC CIDR
1607.03 -> associated with the
customer-connected account.
1609.68 -> And then there's gonna be CIDRs
1611.36 -> associated with the overlay
network for compute.
1615.73 -> For the solution, the network device
1617.35 -> supports one, 10, 40, and 100-gig uplinks,
1620.18 -> there's a minimum of one-gig
bandwidth for the service link,
1624.08 -> and then less than 150 milliseconds
1625.97 -> between the parent and the rack location.
1629.28 -> In terms of the fiber types,
1631.12 -> this solution supports single-mode fiber
1632.9 -> and also a multi-mode fiber.
1638.39 -> Some additional requirements
1639.38 -> are associated with the account.
1641.36 -> So to deploy VMware Cloud on AWS Outposts
1643.537 -> and also to order VMware
Cloud on AWS Outposts
1646.37 -> the customer would need
a VMware Cloud/account,
1651.72 -> and then also an AWS
customer-owned account.
1654.31 -> So in terms of the VMware Cloud account,
1656.32 -> this is an org, so if you
are an existing customer
1658.217 -> and have VMware Cloud on AWS,
1660.27 -> this can be an existing org,
1661.66 -> or in a case of a new customer,
1663.28 -> this is a VMware Cloud account/org.
1669.38 -> Support, as stated,
1672.67 -> VMware will be the main point of contact,
1674.69 -> fixing and troubleshooting
any SDDC-related issues.
1678.05 -> VMware will reach out to
AWS wherever applicable,
1681.17 -> customers can use the
Support tab or chat functions
1684.48 -> as used today, in terms
of your common AWS,
1687.5 -> in the VMware Cloud Console.
1690.803 -> AWS supports hardware
break-fix, instance replacement,
1694.09 -> and then hardware troubleshooting.
1697.29 -> So order, prep and install workflow.
1701.54 -> So the sales process and
then the workshops associated
1704.86 -> can be interchangeable.
1706.17 -> In terms of your workshops,
what we'll do here,
1707.777 -> and this doesn't matter if this is done
1710.54 -> through AWS, so via AWS Resale,
1713.02 -> or directly through VMware,
1714.78 -> the solutions architects
or solutions engineers,
1716.91 -> will work with the customers
1717.77 -> to fully realize the solution,
1719.8 -> understand the solution
from a technical perspective
1722.05 -> all the requirements associated,
1724.03 -> and then also potentially help a customer
1725.88 -> to build out their solution
1727.68 -> from an architectural perspective.
1730.55 -> Once all that information is realized,
1732.16 -> the customer then can go on
to the VMware Cloud Console,
1734.83 -> of course, after finishing
the sales process,
1736.79 -> and then receiving their link
to access to the VMware Cloud,
1740.86 -> they go onto the VMware Cloud Console
1742.45 -> and actually order their
VMware Cloud on AWS Outposts.
1746.65 -> Once the order is submitted,
1748.1 -> an email will be sent to the customer
1749.76 -> basically stating that the order
has been success submitted,
1753.75 -> and then also a list of some next steps.
1756.45 -> Some of the next steps are AWS
would be sending a customer
1760.76 -> a logical networking form.
1763.44 -> This information needs
to be sent back to AWS
1766.22 -> before performing the site survey.
1768.06 -> And in terms of what's included there,
1770.04 -> the logical networking piece
1771.29 -> is associated with the subnets
1772.53 -> that we were speaking about before,
1774.18 -> and also ASN information
associated with BGP.
1779.46 -> In terms of the information
being sent back to AWS,
1782.673 -> once that information is sent back,
1784.29 -> AWS will be scheduling the
site survey with the customer.
1788.03 -> Within this timeframe,
1789.07 -> the customer also needs to
be doing an implementation
1791.98 -> of those configurations
associated with networking,
1794.8 -> power and also in terms
of your facilities,
1797.61 -> as AWS will be doing this site survey
1799.7 -> to do this full validation
1801.04 -> of all this information end to end.
1803.689 -> AWS will conduct the site survey,
1805.82 -> and then once the site survey
is done and signed off on,
1808.62 -> AWS would then build the rack.
1810.38 -> AWS will schedule the rack
delivery with the customer,
1814.397 -> AWS will deliver the rack.
1816.21 -> There's some additional
provisioning that needs to be done
1818.16 -> and validation that needs to be done,
1819.47 -> which can take up from three to five days.
1822.49 -> At that point in time,
1823.89 -> once the rack has been fully configured
1826.25 -> and validated and
available for deployment,
1828.91 -> VMware would then notify the customer
1830.81 -> that the rack is ready for deployment,
1832.4 -> and then the customer can
go in and deploy their SDDC.
1836.82 -> So now we have a demo,
1838.14 -> and this goes through the order workflow,
1841.095 -> and we'll watch this now, thank you.
1844.29 -> Hello, today, we are going
to walk through the process
1847.4 -> of how to order a VMware
Cloud on AWS Outposts.
1851.3 -> My name is Larry Henderson,
1852.62 -> product manager for VMware
Cloud on AWS at VMware.
1856.87 -> Before we get started,
1858.16 -> this assumes the customer's
already been working
1860.51 -> with VMware or AWS Sales
to purchase a solution,
1864 -> and that the customer has
had a series of workshops
1866.27 -> with either VMware solutions architects,
1869.1 -> or solutions engineers,
1870.69 -> or AWS VMC-related solutions
architects or specialists.
1879.42 -> A couple of basic
requirements for ordering,
1882.68 -> a VMware Cloud account/org,
1886.03 -> a general understanding of the solution,
1888.78 -> desired instance amount or configuration,
1892.01 -> an understanding of
1893.59 -> or can speak to the facility requirements,
1896.39 -> cooling requirements, power requirements,
1899.22 -> and networking requirements,
1900.7 -> and lastly, a customer AWS account.
1906.91 -> So let's get started.
1908.61 -> The ability to order a
VMware Cloud on AWS Outposts
1911.86 -> is available to new and existing
1913.54 -> VMware Cloud on AWS customers.
1916.24 -> For our example today,
1917.69 -> we are walking through the
process as a new customer.
1920.34 -> The start point today is a customer
1922.02 -> who just received their,
1923.987 -> "Welcome to VMware Cloud
on AWS Outposts," email.
1928.28 -> From here, we will click
1929.77 -> the Join VMware Cloud Services link.
1933.13 -> This will take us to the
VMware Cloud Services Console,
1936.34 -> where we follow the standardized process
1938.4 -> as a first-timer to the
Cloud Services Console
1941.29 -> by creating an account,
1943.32 -> populating the necessary information,
1945.26 -> including identity and payment.
1950.27 -> From there, we will be taken
1951.78 -> to the VMware Cloud landing page,
1954 -> where we will click to expand
1955.76 -> the VMware Cloud on AWS Outposts tab.
1959.19 -> There is a choice to
Order Now or Learn More,
1962.14 -> which would provide a brief
overview of the solution.
1967.23 -> Taking the Learn More path,
1968.81 -> the next step will be to click
1971.09 -> Order a VMware Cloud on AWS Outposts.
1978.78 -> From here, we will walk
through the steps required
1981.34 -> to successfully complete an order.
1983.29 -> As stated in the beginning,
1984.59 -> there are specific
requirements for this solution.
1987.91 -> Step one, "Provide a name
1989.89 -> for your VMware Cloud on AWS Outposts."
1996.97 -> Step two, "Connect to your AWS account,"
1999.96 -> this also follows the
standard VMware Cloud on AWS
2003.02 -> account-linking process,
2004.1 -> where as a new customer, you would click
2006.06 -> the Open AWS Console With
Cloud Formation Template link,
2009.95 -> sign into your account,
2012.75 -> choose the region where you plan to deploy
2014.89 -> your VMware Cloud on AWS Outposts,
2016.617 -> and run the cloud formation template.
2019.05 -> Once completed, your
account will be linked
2021.57 -> and the VMware Cloud Console
will show the following.
2030.3 -> Step three, "Region and availability zone,
2034.17 -> select the region and availability zone
2036.1 -> where your VMware Cloud on AWS
Outposts will be connected."
2039.34 -> Note, the connection must be
2041.36 -> to a VMware Cloud on AWS-supported region,
2045.02 -> as it will be shown in the
dropdown during your order.
2048.83 -> However, if your location
is in a country slash region
2052.31 -> where VMware Cloud is not supported,
2054.43 -> please consult your VMware
or AWS representative
2057.52 -> as supportability may be available
2059.77 -> as long as there is a connection back
2061.56 -> to a VMware Cloud-supported region.
2064.59 -> For today, we're gonna be choosing
2067.39 -> US East Ohio as our region
2070.36 -> and us-east-2a as our availability zone.
2080.24 -> Step four, "Establish a VMware
Cloud on AWS Outposts site."
2084.83 -> Shown here is the option
to create a new site,
2087.63 -> or for existing customers who already
2089.51 -> have a VMware Cloud on
AWS Outposts site created,
2092.56 -> the ability to select that
site for ordering purposes.
2098.47 -> The site information will
cover the requirements
2100.74 -> associated with the
site name, site address,
2103.87 -> facilities, power and networking.
2106.25 -> We will walk through each of
their required selections.
2110.05 -> First, we will enter a site
name and site description
2114.54 -> and populate the site address.
2123.28 -> Next are the facility
condition requirements.
2126.5 -> Does your site meet the
requirements as shown here,
2128.88 -> the specific temperature
and humidity range
2131.81 -> and airflow requirements?
2133.22 -> If so, select Yes and continue.
2138.13 -> Facility clearance requirements,
2140.69 -> loading dock accommodation
of 94 inches high,
2143.49 -> 54 inches wide, and 48 inches deep,
2146.37 -> with the ability to
provide a clear access path
2149.36 -> to the rack's final rack position.
2153.29 -> If your site does meet these requirements,
2156.63 -> select Yes and continue.
2162.2 -> Next, we have the rack
position requirements.
2166.89 -> Max weight, each site is different,
2169.61 -> provide the max weight
your site can support,
2172.15 -> shown here as a selection
of 2,000-plus pounds,
2175.3 -> there is also a dropdown
for lesser weight.
2178.25 -> Bracing requirements,
2179.86 -> does your site have bracing requirements?
2182.06 -> If so, specify here.
2184.33 -> If there are no requirements, select No.
2187.25 -> Installation equipment,
during the delivery
2190.16 -> of your VMware Cloud on AWS Outposts rack,
2193.11 -> will AWS to be able to bring installation
2194.867 -> and equipment into the site,
2196.84 -> i.e. an AWS-owned laptop?
2199.36 -> If so, select Yes,
2200.73 -> if no, select No.
2205.12 -> Moving on to power information.
2209.61 -> Power draw, how much primary power
2212.47 -> will be available at the rack's position?
2215.2 -> The supported options for
VMware Cloud on AWS Outposts
2218.28 -> are five, 10 or 15 kVA,
2221.57 -> depending on your selected host count.
2224.11 -> If there is a question on the
power draw of your selection,
2227.69 -> please consult your VMware
or AWS representative
2230.27 -> to ensure you select
the correct power draw.
2232.9 -> For today's order, we are choosing 15 kVA.
2236.71 -> Upstream breaker, do you have a 30
2239.37 -> or 32-amp breaker at this position?
2242.25 -> Specify Yes or No.
2244.83 -> Power option, will you provide single
2247.34 -> or three-phase power at this position?
2249.79 -> For today's order, we will be
selecting three-phase power.
2253.61 -> Power connector, to connect the
VMware Cloud on AWS Outposts
2257.53 -> to your power source,
2258.82 -> what power connections
would best suffice for you?
2261.67 -> When ordering, there are
options in a dropdown.
2265.35 -> For today's order, we will be choosing
2267.12 -> red, 32-amp, three-phase
connectors as shown here.
2272.36 -> Power feed drop, at the position,
2275.07 -> will the power come from
above or below the rack?
2278.42 -> We will be selecting Above the rack.
2281.96 -> Last for power, redundancy
at the position,
2286.3 -> will there be redundant power connections?
2288.52 -> We are selecting Yes for today's order.
2291.35 -> Note, for more information
on power requirements
2294.77 -> for VMware Cloud on AWS Outposts
2296.81 -> can be found online at
both AWS and VMware.
2301.29 -> If there are questions,
2302.38 -> please consult your VMware
or AWS representative.
2306.95 -> And last for the site requirements,
2310.12 -> networking for installation.
2313.77 -> Uplink speed, as seen here,
2316.15 -> there are the options of one,
10, 40, or 100 gigabytes.
2320.51 -> As shown, we are selecting
10 gig for today's order.
2324.94 -> Number of uplinks,
2326.81 -> there are two devices for
top-of-rack switches per rack,
2330.22 -> how many would you use to
connect to your network?
2333.1 -> Our selection is two,
2334.61 -> meaning a total of four per rack.
2337.74 -> Fiber type and optical standard,
2340.41 -> the rack supports single-mode
or multi-mode fiber,
2343.68 -> depending on the choice will
define the optical standard,
2347.14 -> different selections are
available in the dropdown.
2349.47 -> For today's order, we are
choosing multi-mode fiber
2353.07 -> and 10GBASE-SR for optical standard.
2357.21 -> Network redundancy, will you
be providing redundant devices,
2361.55 -> allowing for both devices
2362.99 -> in the VMC on AWS Outposts
rack to connect to?
2367.02 -> In our order today, we
will be selecting Yes.
2373.27 -> Next is capacity.
2378.24 -> Here, you would choose the host count
2379.54 -> based on your planned purchase
2381.04 -> for VMware Cloud on AWS Outposts.
2383.44 -> As shown here, we are selecting
a total of six instances.
2389.01 -> The summary includes the
instance type I3ein.metal,
2392.01 -> with the number of hosts being six
2394.5 -> and the total capacity.
2400.97 -> Next, Outposts connectivity,
2404.25 -> this speaks to the requirement
2405.9 -> of connecting the VMware
Cloud on AWS Outposts
2408.43 -> back to a VMware Cloud-available region.
2411.15 -> Natively, an Outpost uses
what's called a service link
2414.43 -> to connect back to a region.
2417.31 -> The options for that connectivity
2419.07 -> are by default over the internet,
2421.4 -> which a customer provides internet access
2423.37 -> and the Outpost calls home to AWS.
2427.43 -> The other option is over Direct Connect
2429.36 -> using private VIF or public VIF.
2433.51 -> The selection here is to
choose private connectivity,
2436.92 -> meaning the servicing will communicate
2438.69 -> over AWS Direct Connect via private VIFs.
2441.79 -> When selecting this, specific
information must be provided.
2445.95 -> Note, different than native AWS Outposts,
2450.03 -> the private connectivity VPC
2451.87 -> must be associated with
the VMware shadow account.
2456.23 -> With that said, a customer
will still have to do
2459.36 -> the standard Direct Connect setup
2461.24 -> and private VIF creation
in their AWS account,
2464.43 -> and share their private VIF
with the VMware shadow account.
2468.69 -> For more details on this,
2469.95 -> please consult your VMware
or AWS representative.
2475.93 -> When making a selection,
2478.49 -> we show what's required here.
2481.27 -> A private connectivity CIDR,
2484.13 -> this is a minimum of a /25,
2486.8 -> but we recommend a /24
for the purpose of growth.
2491.08 -> A VGW ASN, this should be
specified by the customer.
2497.41 -> A private VIF ID,
2499.32 -> the customer must create the
private VIF in their account,
2503.37 -> the associated ID needs
to be provided here.
2507.55 -> Again, for more details,
2509.57 -> please consult your VMware
Cloud or AWS representative.
2513.81 -> For today's purposes,
2515.62 -> we are not selecting private connectivity.
2524.67 -> Payment term, VMware Cloud on
AWS Outposts payment options
2529.16 -> are only three year up front.
2531.61 -> Specific details about
this can be discussed
2534.01 -> with their VMware or AWS
sales representative.
2537.82 -> For the purpose of this section,
2539.74 -> there is nothing to be
selected here, click Next.
2546.57 -> The last step before order submission,
2548.75 -> review and acknowledgement.
2551.01 -> Shown here is the general order summary,
2554.23 -> the name of the Outposts,
your AWS account number,
2558.53 -> the selected region and availability zone,
2561.29 -> the associated site, host capacity,
2564.21 -> the connectivity choice,
2565.89 -> and lastly, the payment term.
2567.82 -> Note, the numbers shown here
2569.27 -> do not represent the actual
cost of the solution.
2573.87 -> Before submitting the order,
2575.65 -> acknowledgement that the term charges
2577.76 -> start only after the successful
deployment of the first SDDC
2582.41 -> on the VMware Cloud on AWS Outposts rack,
2586.06 -> pricing is based on the
subscription period,
2588.52 -> and finally, the approximate
delivery timeframe.
2592.04 -> Note, the delivery timeframe
is just that, approximate,
2596.16 -> please work with your
VMware or AWS representative
2598.737 -> for actual delivery timeframes and dates.
2602.61 -> The last thing to do here
is submit your order.
2611.02 -> After submitting the order,
2612.6 -> you will receive an email
confirming the order
2614.61 -> and a list of important next steps
2616.07 -> that include the following.
2618.14 -> AWS will be contacting you
2619.76 -> to set up a time and
date for the site survey.
2623.11 -> You will receive an email with a form
2625.8 -> for the purpose of logical networking,
2627.91 -> please fill this out as soon as possible.
2630.21 -> Note, the information will be covered
2632.63 -> as part of the workshops
2634.9 -> and should not come as a surprise.
2637.23 -> If there are any questions
on what's required,
2639.26 -> please contact your VMware
or AWS representative.
2643.58 -> It would also let you know
2644.86 -> that you can track the
status of your order
2646.303 -> in the VMware Cloud
Console, as shown here.
2650.26 -> This concludes the order process
2651.97 -> for VMware Cloud on AWS
Outposts, thank you.
2657.31 -> That was the demo, going
through the order flow.
2659.55 -> If you have any questions,
2660.74 -> please feel free to reach out
2661.89 -> to your AWS or VMware representative
regarding the solution
2666.27 -> and how you can go ahead and get started.
2667.96 -> In terms of learning more,
2668.91 -> you can go to the VMware
website and search for Outposts,
2672.89 -> or in this case, vmware/vmcoutposts,
2676.091 -> and also you can follow us on
Twitter, @vmwarecloudonaws.
2679.52 -> Definitely give us a shout
at @vmwarecloudonaws.
2683.11 -> And then in terms of
learning more, as stated,
2685.36 -> you can always work with your
VMware or AWS representatives
2688.69 -> to learn more about the solution
and get started, thank you.
2692.747 -> (upbeat music)
Source: https://www.youtube.com/watch?v=YdbROWC8q9A