I had the chance to give talks about evaluating the requirements for, and building private IaaS cloud platforms.
Often I was explained the following situation: A corporate manager went to OpenWorld, a local Oracle Day or a Virtualization Day, and has seen everywhere that cloud platforms are the future. As a good businessman, he wants to benefit from the new wave and wants you, the system administrator/datacenter engineer/platform architecht to build an Infrastructure as a Service platform to provide virtual environments for your internal or external customers. What do you do? Allow me to point out some of the requirements and considerations.
The cloud building blocks
Thinking outside of the box and on quite a high-level, you are going to need:
All these layers are bound to fulfill some requirements to enable a successful cloud platform. Let's see at each what the functional requirements are to choose the right product for each:
The blogpost has been broken down into a series of 5 smaller sections for readabilitly. This is the main post, linking to all the five sub-posts.
|Part I - Servers||https://blogs.oracle.com/orasysat/entry/how_to_build_a_private|
|Part II - Virtualisation||https://blogs.oracle.com/orasysat/entry/how_to_build_a_private2|
|Part III - OS||https://blogs.oracle.com/orasysat/entry/how_to_build_a_private3|
|Part IV - Shared Storage||https://blogs.oracle.com/orasysat/entry/how_to_build_a_private4|
|Part V - Platform Management|
|Part VI - Putting it all together: The WhitePaper|