Lyon AWS User Group Talk - Enterprise & the Cloud - Nov-16-2016 https://www.meetup.com/fr-FR/LAWS-Lyon-Amazon-Web-Services-User-Group/events/234749190/

1. DISCLAIMERDISCLAIMERDISCLAIMERDISCLAIMER
• All opinions & thoughts are my own and do not reflect views or
opinions of my current or past companies.

2. #cloud-config : Setup environment variables

3. Buzz lightyear - 1995
Credits:
https://www.netflix.com/fr/title/70242311
http://toystory.disney.com/

4. About me,
from the basement … to the cloud
• @matt_traverse
• Former Microsoft & vmware infrastructure guy
• Currently IT Lead Architect for a big French company
• Reader of The Phoenix Project (and it opened my eyes on devops, lean management and so much more)
• Fan Follower of @werner, @adrianco, @botchagalupe, @cote & many more…
• Enthusiast about cloud, containers and all that cool tech stuff
• From now, speaker @ Lyon AWS UG
That was me in the early days
of my career
Credits:
http://www.channel4.com/programmes/the-it-crowd
https://www.amazon.com/
https://aws.amazon.com/
This is what I’m working
on today

5. About my company
Let’s call it « Transportation World Company »
• Big French company in transportation (which does not have high speed
trains!), ~90 000 employees & ~€7B/year revenue
• WW presence (~20 countries: mainly France, USA, the Netherlands,
Germany, Sweden & Australia)
• IS/IT is a few hundred people, mainly focused on keeping the whole engine
running
• Few internal developments (that means everything is bought to ISV, either
big ones for Corp. applications or from niche players for Business ones)
• ~600 servers in France’s DataCenter (almost all Windows) with a
virtualization ratio near 90% (that means there are still Phy. Servers!)

6. Agenda
• Part1: Talkin’ bout a revolution
• Why cloud computing is now a thing for Enterprises?
• Part2: Restart the game
• Feedback about Transportation World Company’s journey to the cloud
• Demo: The Days
• The quorom replatforming – a Cloud use case for Enterprises
Credits:
http://www.tracychapman.com/
http://www.klingandemusic.com/
http://www.avicii.com/

7. Part1: Back to the future
Credits:
http://www.backtothefuture.com/

8. Cultural check – Ops oriented
Do you know what’s that… electronic stuff?

9. Cultural check – Dev oriented
Do you know what’s that… code stuff?
https://ec2.amazonaws.com/?Action=CreateVolume
&Size=250
&AvailabilityZone=eu-west-1a
&VolumeType=gp2
&AUTHPARAMS

10. StartUp & Enterprise, the divergence
StartUp has: Enterprise has:
Slack Outlook
Agile Waterfall
Cloud native mindset Weight of history
Infrastructure as code Legacy DataCenters
DevOps Pizza Teams Siloed IT
Entrepreneurs Dinosaurs
Kanban Gantt
FeedBack Loops V-Model

11. But Enterprises’ IT are not
They don’t go GreenField, so that means change…
…and change is hard!

12. StartsUps’ chance: The GreenField Project

13. Enterprises’ reality: Dealing with the legacy*
* Or how to change without making the whole ship to sink

14. Don’t forget that StartUps of today may be Enterprises of tomorrow
Even Netflix has to handle some kind of legacy: relocation of their whole infrastructure in VPCs (Watch this
year re:invent BO Session about it « NET304:Moving Mountains »):
https://www.portal.reinvent.awsevents.com/connect/sessionDetail.ww?SESSION_ID=8592

15. The main reason Enterprise are also
embrassing the cloud… Especially AWS
“There is a light at the end of
the tunnel, but it’s a train
coming at me.”
--David Cappuccio, managing vice president of
Gartner, in his keynote “What Will Happen to IT in the
Next Five Years?” at the Gartner Data Center
Conference
Credits:
http://www.gartner.com/webinar/2998717
https://www.gartner.com/doc/reprints?id=1-2G2O5FC&ct=150519

16. Crossing the chasm, there’s now 4-lanes
highway bridge

17. How do you go from this…

18. Legacy DataCenter
Happy legacy IT
Operators dealing with
firmware update or
Hardware upgrade

19. …To that…

20. Infrastructure as Code

21. Choose the right trigger(s)
Opportunist project:
- Build/ReBuild Infrastructure/Application
Relocation of Non-Critical environments:
- DEV/Test environments
Money-triggered projects:
- Avoid CAPEX wall
Or, the big switch:
- Whole IS/IT Transformation… (Consultants’ fortune, needs strong sponsorship, mindset
switch, a lot of Evangelization… You have to convince everyone about everything!)

22. Part2: The Empire Strikes Back
Credits:
http://www.starwars.com/films/star-wars-episode-v-the-empire-strikes-back

23. Opportunist project 1: New BI application
• WW deployment for a BI application, project managed directly by a
foreign BU
> Main need: Up scaling!
> Unexpected benefit: server portability (region relocation)
> Software vendor was sceptical about the ability of AWS infrastructure
to host its application but the setup was straight forward

24. Opportunist project 2: SaaS to SaaS plugin
• SaaS to SaaS connector
Why bring back data internally when both source & target are external
and there is no need for data transformation?
> PHP application hosted in Elastic BeanStalk (just ship it!)

25. Non-Critical env. relocation: Archiving
• 17TB of video archives relocation to S3/Glacier with SnowBall transfer
> IAM permissions for cross-services are a little bit tricky to set up
> Glacier fundementals are not so simple to understand (Asynchronous
commands/results)
> AWS Cli or 3rd party tools (or make your own) to manage Glacier jobs
(not possible through the console, at least for the moment)
> Currently waiting for our SnowBall to be shipped

26. Money-Triggered Project: DR Rebuild
• Disater Recovery rebuild, POC based on Zerto/AWS
Reason: big investments for standby infrastructure
> Replicate our critical applications/technical services to S3
> Volume: 15VMs & 2TB of storage

27. Money-Triggered Project: DR Rebuild
Credits:
http://www.zerto.com/

28. Money-Triggered Project: DR Rebuild
• Lessons learned:
In nominal mode, very cheap infra (only data storage & replication appliance run in AWS)
For 15 VMs (2TB) that means around $200/month
Ultra-Short RPO: 10s average
Performance of replication very impressive
Permit partial failover
Small impact on existing infrastructure
No automatic Failback
RTO hardly predictable and highly dependant on AWS hard limits (max // tasks for
VMImport API)
Some custom configurations not or badly covered (VMs with more than 12 vdisks, MS FO
Clusters)

29. Strategic project
• Evolution of our traditional DataCenters
Scope: Complete migration to the cloud
> Business Case is very complex
> Good knowledge of assets, costs & financial model(s) is mandatory
> Be prepared to push Excel to its limits
> Make sure you always have Advil available (headache-intense work)

30. The holly TCO, know your enemy! #1
• Everytime you want to change someting you have to prove the
benefit and most of the time the expected benefit is money!
• As you will change from a CAPEX Model to an OPEX one, you have to
make sure you are comparing apples with apples
• Calculate the TCO in AWS is easy: AWS Monthly calcultator
• Calculate the TCO in an Enterprise is sooooo long & complicated

31. The holly TCO, know your enemy! #2
• Gartner gives the following standard TCO for a Windows server
hosted in a Datacenter: $5053/year (including HW/SW & Ops)
• And this TCO is splitted as below:
Credits:
https://www.gartner.com/doc/2937328/it-key-metrics-data-
HW 26% $ 1 314
SW 21% $ 1 061
Personnel 43% $ 2 173
Connectivity 1% $ 51
Facilities/Occupancy 7% $ 354
DR 1% $ 51
Other 1% $ 51
Total 100% $ 5 053

32. The holly TCO, know your enemy! #3
• Standard VM @ Transportation World Company is 2vCPUs & 8GB
vRam + 100GB storage for standard workload
• Target AWS gabarit could be: m4.large > $2 825/year (onDemand –
100% uptime), so let’s make a little comparison:
HW 26% $ 1 314
SW 21% $ 1 061
Facilities/Occupancy 7% $ 354
Total 54% $ 2 729

33. Part3 (demo): The Half-Blood Prince
Credits:
http://wwws.nz.warnerbros.com/hp6/

34. The middle age: Application initial design
Based on Gartner’s TCO, the
annual cost of this
infrastructure design is around
$15k ($ 8187 for IaaS part)

35. Step1: Lift & Shift
Credits:
http://www.pixar.com/features_films/Brave#

36. Step1: Lift & Shift
Migration path:
• Export VMs from vmware/hyperv/kvm (choose your prefered one, in
our case vmware)
• Copy exported files to S3
• Import the vdisks into EC2 instances
• Apply settings tied to the new run environment (IP address,
application parameters…)

37. Step1: Lift & Shift
Server count: 3
Includes right sizing and
commitment on price (RIs)

38. Step1: Lift & Shift
Challenging 54% of the cost on 3 servers
What cost(s) do we tackle?

39. Step1: Lift & Shift
• Based on AWS Monthly Calculator, the annual cost of this
infrastructure design is:
• That means up to 35% savings on the IaaS part, and around 20% on
the total TCO
$ 5 278

40. Step2: Leveraging DBaaS managed service

41. Step2: Leveraging DBaaS managed service
Migration path:
• Export VMs from vmware/hyperv/kvm (chose your prefered one, in
our case vmware) and DataBase from SQLServer Engine
• Copy exported files to S3
• Import the vdisks into EC2 instances
• Apply settings tied to the new run environment (IP address,
application parameters…)
• Create RDS instance & restore database

42. Step2: Leveraging DBaaS managed service
Server count: 2
Includes right sizing and
commitment on price (RIs)

43. Step2: Leveraging DBaaS managed service
Challenging 54% of the cost on 2 servers
What cost(s) do we tackle?
And…

44. Step2: Leveraging DBaaS managed service
Challenging 97% of the cost on DB Service
What cost(s) do we tackle?

45. Step2: Leveraging DBaaS managed service
• Based on AWS Monthly Calculator, the annual cost of this infrastructure design is:
• That means up to 47% savings on the IaaS part, and around 40% on the total TCO
$ 4 302

46. Step3: Total Wipeout! (that’s where the magic
happens)

47. Step3: Total Wipeout! (that’s where the magic
happens)
Migration path:
• Export application code from TomCat server and DataBase from
SQLServer Engine
• Copy exported files to S3
• Create RDS instance & restore database
• Create Elastic BeanStalk application and load the code

48. Step3: Total Wipeout! (that’s where the magic
happens)
Server count: 0

49. Step3: Total Wipeout! (that’s where the magic
happens)
Challenging 97% of the cost on 3 Services
What cost(s) do we tackle?

50. Step3: Total Wipeout! (that’s where the magic
happens)
• Based on AWS Monthly Calculator, the annual cost of this infrastructure design is:
• That means up to 60% savings on the IaaS part, and around 75% on the total TCO
$ 3 702

51. BONUS, Next Step

52. Step3bis: Total Wipeout! (Dark Magic version)

53. Step3bis: Total Wipeout! (Dark Magic version)
Migration path:
• Export application code from TomCat server
• Migrate DataBase from SQLServer Engine to an MySQL/Aurora One
• Copy exported files to S3
• Create RDS instance & restore database
• Create BeanStalk application and load the code

54. Step3bis: Total Wipeout! (Dark Magic version)
Server count: 0
Use DMS to transform
the DataBase to an
MySQL/Aurora One

55. Step3bis: Total Wipeout! (Dark Magic version)
Challenging 97% of the cost on 3 Services
What cost(s) do we tackle?

56. Step3bis: Total Wipeout! (Dark Magic version)
• Based on AWS Monthly Calculator, the annual cost of this infrastructure design is:
• That means up to 69% savings on the IaaS part, and around 80% on the total TCO
$ 2 994

57. One more thing…

58. The Pets vs Cattle paradigm:
change the way your applications rely on
infrastructure (ie: stateless/dynamic scaling…)
Credits:
http://dduportal.github.io/presentations/docker-meetup-lyon-
20140528/
http://fr.slideshare.net/randybias/the-history-of-pets-vs-cattle-
and-using-it-properly