I had to rush off to the airport and crashed out, back home in Adelaide now. It was a very interesting event, and was great to get the opportunity to talk to some key HP staff. I’ll summarise the whole event in a few days once I’ve absorbed it all.
Bit of a gap as this section was particularly technical around layers, zones, repositorys, pools, catalogues – you get the idea :)
Architecture Deep Dive for HP Cloud:
IT becomes the service broker, and also needs to choose where to put what. It should also be designed to be able to be moved from one environment to the next.
This requires a common foundation. There are three layers for an Integrated cloud platform to cover all IaaS, PaaS and SaaS (hmm most things seem to be in threes today) – Demand – User Interraction, Deliver – Service Orchestration and Supply – Resource Operation.
If someone uses your hosted severs for an attack, who is at fault? The provider or the consumer? I’m not sure this one was actually answered (please correct me if I’m wrong!) but regardless it’s a good question, and there are a lot of grey areas because laws never keep up with new technologies.
Consumer responsibility vs Provider responsibility in order: IaaS, PaaS and SaaS. So if you want the least responsibility, SaaS is the way to go.
Cloud Security is about perspective. HP have a lot of considerations and understanding of this, read some cloudy stuff here:
Had a walkthrough of HP’s Comms Room Showcase Extravaganza, check my twitter feed @AdamFowler_IT for the pics (later because all forms of internet are now crawling here).
HP Networking – When you’ve got a single network switch that has 100’s of blades connected to it with 1000’s of VM’s, the MAC table is going to grow huge, and there are limits. HP manage the networking for your cloud to make sure these issues don’t occur… plus it’s their own switches and routers in use!
HP will support VMWare, Microsoft, Citrix and HP ux virtualisation technologies.
Welcome to part two, and I’ve now converted to local Sydney time to keep things confusing.
The building blocks that HP has to make your cloud: Private, Managed and Public all used converged infrastructure. The three key steps are: Standardize, Virtualise and finally Automate.
HP CloudSystem is 45% cheaper than Amazon EC2 as long as you buy enough. Based on 4 Chassis, 64 blades with 768 VM’s etc – that’s a rather decent deployment!
There are two stages to cloud; Step-by-step and fast track.
Step-by-step includes Standardize and consolidate, then Virtualise and automate.
Fast Track is then Self service infrastructure, self service applications with full lifecycle management and finally becoming a service broken in a hybrid environment.
The above is a bit deeper defining what I was talking about in Part 1. You’re smart, you’ll find where that is if you need to.