AWS vs. Private Cloud - TechTalk Episode 30
Transcript
hi welcome to virtualizes geek Tech talk episode 30 you know what it's been a while since uh I've engaged with you guys via this medium uh via the YouTube channel mainly because uh I wanted to uh change kind of the format or not necessarily the format but the frequency of the content that I was posting I wanted to make sure that I talked about uh topics that I think I could uh really engage you guys on go on uh uh via uh Google+ and YouTube and
today's topic I think is a pretty engaging topic I I think it's uh it it's it's mey enough that it at least wared a uh video before the end of the year and that's the topic of AWS kind of versus everything else so over the past couple of weeks I've had some pretty interesting posts that's gotten some pretty interesting engagement either on Twitter or on the blog uh direct directly and that's virtualized geek.com you can uh uh spelled right down there for you guys uh but
basically the concept is AWS not kind of Enterprise ready that's not entirely true AWS uh Amazon has made some strides in a lot of of different areas obviously the uh their foray into desktop is a service is I think is a needed um is a needed feature uh the whole concept of being close to the data I think is very critical if you're if Amazon hopes to uh Outsource the data center to uh their cloud or Outsource the Enterprise data center to AWS uh they need
to be able to provide realistic and uh reliable uh desktop performance so uh vdi is most definitely a way to provide that service obviously AWS is seeing an uptick in the Enterprise in the form of Shadow it so when I say that AWS is not Enterprise ready it's not Enterprise ready as far as the it manager and the CIO we're not consuming uh those Services uh so we're not you know taking Amazon Service uh putting a um front end in front of that and allowing our
in users to consume that uh for various reasons but before we get into those reasons uh I wanted to kind of focus on the Enterprise it discussion or specifically the shadow it discussion part of the Amazon uh use case uh Amazon has been extremely compelling for uh individual departments the ideal that they can just whip out their credit card get uh the compute resources that they need a higher in-house developer to spin up a Amazon cloudbased application and get the type of response time and elic
elasticity that they need to deliver whatever uh project or Mission they're working on is extremely compelling and I think from from a business perspective and from an IT operations perspective we understand that so we'll take a solution like open stack eucalyptus um uh vcloud take your pick of the various Cloud managements and Cloud managers and Cloud providers out there we take those Solutions uh and we make we build very robust solutions that offer the same richness as Amazon but but for whatever reason uh the shadow
IT Crowd is not taking up uh that those Services they're just not consuming it and I think as a result Enterprises are kind of looking at open stack and they're looking at vcloud and they're looking at these providers uh and this is just one reason they're shrugging their shoulders at it because the bottom line is that if our customers don't consume the service then what's the point of deploying it or if we haven't really considered why they're not deploying the services and we build them and
they don't come then you know we've just spent a lot of time and money on uh solution that ultimately didn't meet the requirements of our Enterprise customer so I kind of want to you know one of the other blog posts was about kind of the uh you know taking a look at the nature of the Shadow it so one of the things that we take for granted when it comes to Shadow it is that they're not it professionals they're mainly developers and they don't know how
to run it operations they know what they need uh and they know that Amazon or services like Amazon can provide what they need very quickly so they build uh in a lot of cases pretty robust and production like uh applications built on the whole AWS Amazon model uh they develop uh Cloud development skills uh and familiarity with the Amazon uh API the AWS API and that's kind of what they know so my argument in a post was is the Reas is one of the reasons why
uh openstack or vcloud or any one of your Solutions are not getting traction with this Shadow it cloud is because of API compatibility these developers uh whether or not the Enterprise intended them to uh learn AWS apis or not that's what they know you know we can draw a parallel to kind of net programmers you know I don't see a whole lot of of of theet cloud moving over to developing in Linux environments because they know net they build Windows applications uh those windows applications do
what they need to do and there's really not a uh from a developer perspective why why develop on Linux if you know if the resource that I'm developing on is virtually free which uh for a development crowd is there there is no cost internally from a it perspective it's a hidden cost for them to develop onnet versus on uh a lamp stack or whatever uh we use in the Linux world so they there's not a lot of incentive to move unless that uh unless there's an
atificial in placed on them by the CIO so bringing back to the Amazon conversation uh again if they have a budget and they can say and you give and we give them a open a perfectly fine open stack environment that gives them all of the richness of the AWS experience and it's and there's not a compelling reason to embrace it whether it's a you know uh this is the problem with Shadow it the CIO can't come into the marketing department and say thou shalt use the
open the internal private open stack Cloud that's the advantage of them having their credit card and being able to go out to AWS there has to be a compelling reason for them to change uh so I thought you know what maybe if we provided complete API um compatibility with uh the AWS um Cloud that would have developers stop uh that shadow it change their habits and start consuming the internal resources that's available to them and then you have to think about you know what's the you
know what's the incentive and incentive is pretty much cost the question boils down to can I uh whether it's the the same credit card like transaction or if it's a uh internal chargeback system whatever the chargeback mechanism is can I help that developer reduce a pain point for them which is cost and I can guarantee you that any Shadow it uh resource uh when they they they get surprise AWS bills so if we can give them that oh I hate to to bring uh this bad
example to them but we can give them that whole net Windows is free attitude to their if we can hide the cost uh again and this is one thing that it does well is it hides the cost of doing Enterprise it from the enduser if it's just part of their regular Bill their regular charge back then I think it becomes a much more appealing solution especially if we can give them a familiar look and feel that they don't have to go and get retrained again I
think we have to look at it as a partnership and really as a uh as us servicing the as competition to services like AWS that we need to give compelling reasons uh for these folks in these departments to move over and it just can't be we can do everything that Amazon does of course you can do everything that Amazon does but why change why you know we have to give them a reason to fight inera uh basically so you know what I would love to hear
feedback because I know you guys are pretty passionate about this Amazon versus AWS I think I'll make that the title of the this session Amazon versus I mean I'm sorry uh Amazon AWS versus open stack uh I think it's a fundamental question that's just not a technical question but this is really where you know we need to put on our business hats and really understand uh from a uh uh enduser the developers scenario what's the compelling reason to use the internal it resources versus a resource
that I don't have all these restrictions on us which also brings us to a whole another conversation about uh software defined networking and have been able to explode out to services like AWS uh visit the the blog virtualized geek.com or follow me on tw Twitter at virtualized geek to get more of this conversation like the um the video uh comment is now ungraded with Google+ uh and we'll talk to you guys hopefully before the new year but if not before the new year you guys have
a happy New Year and talk to you in social media thanks
