Popular in Course
verified elite notetaker
Popular in Business
This 9 page Document was uploaded by an elite notetaker on Sunday December 20, 2015. The Document belongs to a course at a university taught by a professor in Fall. Since its upload, it has received 8 views.
Reviews for VA-s-Own-David-Linthicum--Well-Known-Cloud-Blogger78
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 12/20/15
VA's own David Linthicum, well-known cloud blogger for InfoWorld and CTO and founder of Blue Mountain Labs opted to take a deeper dive into architecture vs. general business benefit etc. of cloud computing and hybrid clouds. Virtual Server Hosting The promise of hybrid cloud is really being able to leverage the best of both worlds In 2007 and 2008 we talked about public clouds In 2009 and beyond, private cloud was the game changer So how is this going to be leveraged? According to David, hybrid clouds will provide architectural power like we haven't seen in the past Your ROI with private cloud is not as high as with public cloud, since you're still managing your infrastructure With hybrid cloud, we're able to move data back and forth on whatever platform is most efficient to the needs of the environment The approaches you see here at Cloud Expo are replication and migration (moving code or moving data between private and public cloud), interface abstraction (behavior, data, process), and extending virtualized environments With interface abstraction, you can take behavior and processes and put behind a common interface There is a common extraction layer Most everyone moving to hybrid cloud is moving in this direction The challenge is identifying the common API to focus on, and how to implement in your environment Consider this though - this is another complex distributed architecture (think SOA) There are bandwidth limitations that hinder the architecture Most advanced product-orientated solutions are just emerging - many haven't reached the value of actually working ROI is also all over the place - whether or not you're going to use hybrid cloud environments, your business case might be very different It could be very high or very low ROI - and companies need to determine that before moving to hybrid cloud environment The target value is to have some kind of workload manager that looks at everything in the data center There is a need to avoid capex and buying expensive tools, but still have the ability to burst up or down based on need The current patterns are primitive in terms of hybrid architectures You're either migrating - moving components or data processes from public to private cloud (ports, data, etc ) and hoping it's compatible Or, you're looking at interoperability - looking to form a synergic environment between public and private cloud, using APIs You want your private and public cloud services to operate as ONE cloud But, the best option according to David is cloud abstraction - the ability to have an abstraction layer that works with multiple public and private clouds and the ability to manage all those resources in one place The interface abstraction layer is an easy place to manage it all Cross-cloud compatibility through single consoles is the future of the hybrid cloud Four emerging hybrid cloud architectural patterns include: - static placement - assisted replication - auto migration - dynamic migration Static placement: all about putting things on a particular platform and being bound to it It's difficult or impossible to migrate and there is little of no use of standards Virtual Server Hosting Assisted replication: typically is productized You will be able to take code and move it into a PaaS or IaaS environment It will be assisted by platforms that can assist with the migration - going to public to private cloud and back This is not an operational instance, it's not dynamic The problem with this is it requires shutting everything down, moving, testing, and sometimes shutting down again Auto migration: the ability to, at any given time, migrate code Even when systems are operating This is more ideal because virtualization, code and data are working together and moving data between different systems The downside of this - not a lot of people have been able to actually do the in a real world scenario Dynamic migration: back to nirvana, or the ideal hybrid cloud environment This uses dynamic VM migration within a single logical OS The ability to use logical and physical abstraction - which is really cool If achieved, this will be the most valuable distributed computing trick to-date But remember, you must have governance and security to do any of these changes to architecture Governance is the ability to set policies on how your run, balance and load these systems as well as maintain compliance is instrumental to how your system behaves Bottom line: we need cloud abstraction Where do you start? Define your information, define your services, define your processes, map to the proper architecture (static placement, assisted replication, auto migration or dynamic migration), and finally select your technology solution Don't forget: the security model is systemic to all of this - you will get hacked or will have compliance issues if you don't think about that The governance model is also systemic to this, as is rigorous testing, which is critical to success Virtual Server Hosting
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'