Extending your Data Center into the Cloud #CTODailyDose
Transcript
how's it going mm from the CTO advisor calm you're looking at today's daily dose they I think is August wait hold on what is today is it's the 14th work Oh scared it was only the 11:00 my brother's birthday is on the 14th and I got a little scared that I hadn't called him today is August 11 you're watching you're a CTO of Iser daily dose we're going to talk about the difference between expanding your data center into the cloud versus adopting a cloud native approach
to the cloud now that might sound a little loaded at the beginning like why would not want to be cloud native of course that's the all the cool kids are doing cloud native and if I'm not going to do cloud native why even do the cloud you may be asking yourself what does even cloud needham will answer that question in today's CTO daily dose so conceptionally we have to decide when we're building a cloud strategy whether or not we're going to expand our data center so
you know inside of our data center we have a set of services you know basic services we will do the virtual machine so we'll provide virtual machines to our end users will have our service management such as no service now inside of our datacenter we'll have storage platforms maybe some nads for file sharing the list goes on and on and on our end users will open a service request to leverage one of these services inside of our enterprise data center there's basic business challenges that comes
with running these services out of our data center one we need to over subscribe or over build these physical resources so that we can consume provide them as a target of sumption for our end users we don't want to run out of sow sharing space we don't want to run out of virtualization hold space storage service now needs to be robust and always available etc etc etc the internet needs to be up and running that means that there's a capital commitment from a depreciation perspective in
a people ops perspective that really can be a challenge to manage and calm the cloud so initially services like AWS xuer focused on infrastructure as a service that was geared towards startups people who were not burdened with a legacy data center they can go into AWS and loot use the services natively as designed for the cloud later on companies like AWS decided they needed to appeal to the enterprise and allow for enterprise class services so there's this concept that instead of using resources financial resources from
a capex perspective to expand your data center your big data center footprints and meet the needs of your end-users that you can expand these services into the cloud so that offers two benefits one it moves from a capex model where we have capital expenditures and depreciation schedules to an optics model that we can use services as we consume them or pay for services as we consume them and this should add a bit more agility since I don't have the physical footprint of the data vendor needing
to install bare metal servers install a VM on top of it configure the the virtual machine environment etc etc manage all of that physical infrastructure we can also source that to the cloud provider so in the cloud provider we just simply offer them our ServiceNow platform or whatever our ITSM is our virtual machines I'm sorry our storage platform our file sharing services all of this looks very similar to what we're doing in the data center today and the cloud just becomes an extension of our data
center and data center services we're not doing anything cloud native we're just taking our operations model lifting is shifting that to the cloud or extending that to the cloud a lot of people take this approach when they migrate to the cloud they just do what they do today is someone else's data center this is where the term that the cloud is just someone else's computer come from or originates from this is very appealing one it's simple to do and employees are not really being reached true
to retool to retrain on a new set of processes and technologies outside of understanding the cloud portal and the control plane for the cloud everything else is pretty straight forward end users exact same process they open the ticket and they're your ITSM and then that request needs to get fulfilled on the back end from your data center team directly or a proxy of your data center team inside the cloud we can put all kind of services on top of that AWS even offers immense servers for
this model however if your business objective is to transform the way you deliver IT services and you don't only want to just have this hybrid IT perspective on which we're expanding your data center but you also want to consume services such as AWS lambda serverless or kubernetes AWS just recently announced their support in kubernetes they joined the c CNF to cloud computing something found Ives to get that acronym and then other services no past services that you don't offer today in your data center etc etc
AWS has a call managers sad services etc that now your end users have the ability either through some type of orchestration tool to consume that in the cloud or they bypass that directly and go directly to the cloud portal into Subin this is definitely transformation obviously you're leveraging the tools of the cloud ikka cloud native you're using using the native capability of a cloud service provider to provide services that you simply don't offer in your data center so this is not just an extension of your
data center but that new capability that you're adding to your IT service portfolio much more difficult transformation because then you answer all of the challenges of managing integrating hybrid IT and cloud native into your supporting agencies finance needs to understand this model compliance security all of that needs to be wrapped in all these processes purchasing all that needs to be wrapped into this cloud native approach whereas before when we're keeping when ITP I'm sorry when IT is a gatekeeper for accessing cloud we're doing just a
narrow set of services that we can replicate both in our data center and our public cloud it keeps it very simple we can move service public public cloud provider to public cloud provider just based on that baseline set of I'm going to do them storage networking etc just the way I do it today just in the cloud versus this cloud native model so that's it for the CTO adviser visit me on the web the CTO advisor com subscribe to the podcast also Atlas EQ advisor comm
and of course follow me on Twitter at CTO of either you engage me only this will be shared on LinkedIn so that you can comment and have an extended conversation about this today's conversation talk to you guys next CTO advisor
