Journey to the Cloud – Guidance and Lessons Learned Michael Rizzo Value Architect +1 818-314-4271 Michael_Rizzo@bmc.com Is this how you feel about this topic??

What is “Cloud” / “Migration” / “Journey to the Cloud” 4/11/2019 What is “Cloud” / “Migration” / “Journey to the Cloud” Saas Provider (Office365) Vendor Solutions (on premise currently  cloud) Servers moving from on premise to hosting in the cloud Server staying on premise for phase 1 because of risk or time needed to move …and many more scenarios The key point is that it is a re-evaluation of your organization – what’s working, what’s not, what do we have Tell the BMC story about Seibol vs. Salesforce

What are the steps to move to the cloud? 4/11/2019 What are the steps to move to the cloud? Step 1 is to answer simple questions that have proven very difficult to answer for both the public AND private sector What services do we really provide both internally and externally? How are those services built? Where is the hardware, software, network, storage, database, etc.… for each service and how is all put together today? Who is paying for the service today? How do we secure our move to the cloud?

Is your service “cloud ready” especially for public facing services? OS is up to date and patched with a mechanism in place to keep everything up to date Monitoring and security have been accounted for moving to a public or hybrid cloud There are no components that are end of life / support (Windows Server 2008 for example) Big Challenge ***How are integrations going to work both for internal integrations, cloud integrations and vendor integrations?***

What do I move first and why? Legacy applications can be difficult to migrate and it is clear that we need to balance risk, importance and complexity. Example – In a number of state agencies in California, all brand new development/systems are being provisioned in the cloud. Why It is far easier to start with something new versus a legacy application The project typically starts with a much smaller set of needs that grows naturally as the project moves forward

Service Orientated – Understand The End to End Process 4/11/2019 Service Orientated – Understand The End to End Process The services need to be understood end to end This process involves getting various groups together to fully understand each of the services today This is also a good opportunity to build out full test scripts for both the current service These test scripts will be used during the migration to ensure that the users will continue to work when the service is migrated to the cloud I’m going to let you in on a secret – it’s basically a data center move but rather going to one you control, it goes to a cloud provider Many of the same exact tasks are performed and unless you want to transform the way you do things, the idea is to keep critical services up and running. Consolidation first – I understand that the vast majority of compute is virtualized so that makes it much easier The key consideration is – if and when to start creating content that is cloud-first using things like containers?

Current integrations vs. web-ready integrations (REST API) Some current integrations are based on legacy ideas – API, scripts, etc.… even from commercial vendors There is a need to evaluate every service and understand what to do around the integrations – upgrade to a web-ready version, move to a SaaS version, etc.… The “de facto” standard for web ready integrations is the REST API. The vast majority of vendors solutions, cloud providers and open source solutions have REST API libraries and this is the most common way to integrate (on premise, in the cloud, cloud to cloud, etc..) One step that we see is that moving forward, all integrations are “web ready” by using the REST API calls

Example – California DMV and PCI / PII Information Outsourcing California DMV used to take credit card information over the web (PCI compliance) and fingerprint information (PII compliance) using internal systems   As part of the “cloud migration” plan, California DMV outsourced both of these functions to 3rd party vendors California residents that pay on the web for registration goes to a 3rd party who integrates with California DMV each night with the Registration # and payment in full once per day (overnight) Fingerprints information is now verified by the 3rd party system and the DMV systems receive a message – match or no match from the 3rd party system

Example – On Premise  Cloud Migration Multiple Agencies (State and Local) have started the journey LA Unified School District and LA Department of Water and Power – moved multiple vendor applications from on premise to cloud-based vendor applications Data security concerns, especially for asset data, were top discussion points especially for LADWP (Water and Power) Phased approach for both agencies with new development starting in the cloud with a phased rollout of legacy applications  

4/11/2019 Example – Retirement = risk for legacy systems – operations and migrations The State of California had an ancient legacy system that controlled all lines (phone and data) as well as billing for all the state agencies The person who originally built the system retired and his replacement moved on to another position in the State. When the state was looking to modernize the application, they needed to start from the beginning to actually understand what functions were performed by the system! The various agencies in the State of Washington almost certainly have old or even ancient legacy system that are not well documented or understood. They are almost certainly not ready to migrate to the cloud at this time   65% of all of the state of California work force is age 46+ and 30% are 55+ (age of retirement)

Conclusion and Discussion 4/11/2019 Conclusion and Discussion You must know what you have and how it connects in order to make intelligent decisions on what to do (upgrade, migrate, go to a SaaS solution, etc..) This is a process and you will need to carefully plan over multiple phases – what to move first and why. Security will be involved and will be very important to the process – they can delay or even stop the migration to the cloud if there are legitimate security concerns You will run a hybrid cloud for years – some on premise and some in the cloud for years DON’T WAIT UNTIL 2023! Start planning now to gain experience and collaborate with each other on challenges and how you overcame those challenges   65% of all of the state of California work force is age 46+ and 30% are 55+ (age of retirement)