Interview with Nicolas Chalton, CIO of Agarik, about the new shared Open Stack platform launching.
Why opening a Private Cloud shared platform with Agarik, in a time of forced march to Public Cloud ?
NC: Analysts and market players are convinced, Public Cloud platforms will not be able to answer to all clients’ needs. Future is part of a fragmented IT’s consumption approach: For each need, a specific appropriate answer, based on Public SaaS, Public PaaS and Public IaaS, Private and even Legacy models.
The key word is environments’ hybridization to take advantage of each model’s best. So, this is in this kind of context that a Hybrid Cloud private shared platform makes sense.
What is the difference between Private and Public Cloud ?
NC: A private Cloud shared platform brings some benefits of a Private Cloud :
• Platform’s localization control and thus data
• Safety framework’s deployed control
• Capacity to set up devices or specific developments
As well as a shared infrastructure benefits :
• Platform’s entry cost
• Pay-per-use resources
• Capacity to benefit from service including for narrowed needs
What are mutualization’s impacts and how can we minimize them ?
NC: Resources mutualization, intrinsically, includes physical resources sharing between several environments, and thus several use profiles. It can involve side-effects from an environment to another and limits environments’ insulation to a « logical » insulation. Mutualization also imposes prerequises’ respect as well as settings’ constraints.
Agarik’s response, which enables to minimize those constraints, is the virtualization’s OpenStack technology use. This technology, which is now mature and unanimously recognized, allows an IaaS’ platform conception and orchestration with an advanced management of multi-tenant running.
It permits to ensure a full logical insulation of each environment from one to another, also including physical resources reservation to guarantee a stable service quality.
How can we integrate a hosted perimeter in a shared Private Cloud with other IT environments ?
NC: A Private Cloud shared platform’s value is driven by its capacity to « hybrid » to other environments.
Hybridization’s first level is the environments’ network interconnection, ideally in level 3 to allow Vlans’ extension. This interconnection may operate with all type of other environments: Public Cloud, third party Private Cloud, Legacy perimeter. On that first level, through its quality of network operator, Agarik is in full capacity to deploy and operate interconnections. Moreover, Agarik is now interconnected with Interxion’s Cloud Connect service, allowing a secured and private access to Microsoft Azure’s and AWS’ Public Clouds.
Hybridization’s second level is the capacity to orchestrate operations from an environment to another via standard APIs. Agarik’s Open Stack platform have the whole standard APIs enabling a hybridization with other Open Stack Clouds ( like OVH per example) but also most of market’s Public Clouds.
What are the native functions brought by Agarik’s shared Private Cloud ?
NC : New resources’ fast deployment via the self-provisioning portal and a package of pre-configured templates, network and safety bricks ready to use, redundancy mechanism, a per-use billing and, of course, Agarik’s Fantastik assistance service.
Could An Agarik client also benefit from an IaaS Open Stack platform dedicated to its own needs ?
NC: Of course, Open Stack technology can be used for dedicated environments. Agarik offers and operates on dedicated Private Cloud platforms based on OpenStack for some of its clients.
To extend the interview, meet-us on Twitter @NicolasChalton