For those of you who want to get most out of Oracle technologies to evolve your IT to the Next Wave, I encourage you to register to the up coming Oracle Optimized Datacenter event that will take place in Paris on November 28th. You will get the opportunity to exchange with Oracle experts and customers having successfully evolve their IT by leveraging Oracle technologies. You will also get the latest news on some of the Oracle systems announcements made during OOW 2012.
During this event we will make an update about Oracle and Clouds, from private to public and hybrid models. So in preparing this session, I thought it was a good start to make a status of Cloud Computing in France, and CIO requirements in particular. Starting in 2009 with the first Cloud Camp in Paris, the market has evolved, but the basics are still the same : think hybrid.
From Traditional IT to Clouds
One size doesn't fit all, and for big companies having already an IT in place, there will be parts eligible to external (public) cloud, and parts that would be required to stay inside the firewalls, so ability to integrate both side is key. None the less, one of the major impact of Cloud Computing trend on IT, reported by Forrester, is the pressure it makes on CIO to evolve towards the same model that end-users are now used to in their day to day life, where self-service and flexibility are paramount. This is what is driving IT to transform itself toward "a Global Service Provider", or for some as "IT "is" the Business" (see : Gartner Identifies Four Futures for IT and CIO), and for both models toward a Private Cloud Service Provider.
In this journey, there is still a big difference between most of existing external Cloud and a firm IT : the number of applications that a CIO has to manage. Most cloud providers today are overly specialized, but at the end of the day, there are really few business processes that rely on only one application. So CIOs has to combine everything together external and internal. And for the internal parts that they will have to make them evolve to a Private Cloud, the scope can be very large. This will often require CIOs to evolve from their traditional approach to more disruptive ones, the time has come to introduce new standards and processes, if they want to succeed.
So let's have a look at the different Cloud models, what type of users they are addressing, what value they bring and most importantly what needs to be done by the Cloud Provider, and what is left over to the user.
IaaS, PaaS, SaaS : what's provided and what needs to be done
First of all the Cloud Provider will have to provide all the
infrastructure needed to deliver the service. And the more value IT
will want to provide, the more IT will have to deliver and integrate
: from disks to applications. As we can see in the above picture,
providing pure IaaS, left a lot to cover for the end-user,
that’s why the end-user targeted by this Cloud Service is IT
people.
If you want to bring more value to developers, you need to provide
to them a development platform ready to use, which is what PaaS
is standing for, by providing not only the processors power, storage
and OS, but also the Database and Middleware platform.
SaaS being the last mile of the Cloud, providing an
application ready to use by business users, the remaining part for
the end-users being configuring and specifying the application for
their specific usage.
In addition to that, there are common challenges encompassing all
type of Cloud Services :
Security : covering all
aspect, not only of users management but also data flows and data
privacy
Charge back : measuring
what is used and by whom
Application management : providing capabilities not
only to deploy, but also to upgrade, from OS for IaaS, Database, and
Middleware for PaaS, to a full Business Application for SaaS.
Scalability : ability to evolve ALL the components of
the Cloud Provider stack as needed
Availability : ability to cover “always on”
requirements
Efficiency : providing a infrastructure that leverage
shared resources in an efficient way and still comply to SLA
(performances, availability, scalability, and ability to evolve)
Automation : providing the orchestration of ALL the
components in all service life-cycle (deployment, growth &
shrink (elasticity), upgrades,...)
Management : providing monitoring, configuring and
self-service up to the end-users
Oracle Strategy and Clouds
For CIOs to succeed in their Private Cloud implementation, means
that they encompass all those aspects for each component life-cycle
that they selected to build their Cloud. That’s where a
multi-vendors layered approach comes short in terms of efficiency.
That’s the reason why Oracle focus on taking care of all
those aspects directly at Engineering level, to truly provide
efficient Cloud Services solutions for IaaS, PaaS and SaaS. We are
going as far as embedding software functions in hardware (storage,
processor level,...) to ensure the best SLA with the highest efficiency.
The beauty of it, as we rely on standards, is that the
Oracle components that you are running today in-house, are exactly
the same that we are using to build Clouds, bringing you
flexibility, reversibility and fast path to adoption.
With Oracle Engineered Systems (Exadata, Exalogic &
SPARC SuperCluster, more specifically, when talking about Cloud), we
are delivering all those components hardware and software already
engineered together at Oracle factory, with a single pane of glace
for the management of ALL the components through Oracle Enterprise
Manager, and with high-availability, scalability and ability to evolve by design. To give you a feeling of what does that bring in terms just of implementation project timeline, for example with Oracle SPARC SuperCluster, we have a consistent track of record to have the system plug into existing Datacenter and ready in a week. This includes Oracle Database, OS, virtualization, Database Storage (Exadata Storage Cells in this case), Application Storage, and all network configuration.
This strategy enable CIOs to very quickly build Cloud Services,
taking out not only the complexity of integrating everything
together but also taking out the automation and evolution complexity
and cost.
I invite you to discuss all those aspect in regards of your
particular context face2face on November 28th.
