Liberty, the 12th release of OpenStack, came out last week

With 1,933 individual contributors and 164 organizations contributing to the release, Liberty offers finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies such as containers in production environments ...

 

Quoting from its web-site:

“OpenStack Liberty, the 12th release of the open source software for building public, private, and hybrid clouds, offers unparalleled new functionality and enhancements. With the broadest support for popular data center technologies, OpenStack has become the integration engine for service providers and enterprises deploying cloud services.

With 1,933 individual contributors and 164 organizations contributing to the release, Liberty offers finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies such as containers in production environments”

 

Here you can see a short video explanation:
https://www.youtube.com/watch?v=e7r2-p8Mki4?autoplay=1



And the press release is quoted below:
 

Newest OpenStack® Release Expands Services for Software-Defined Networking, Container Management and Large Deployments

AUSTIN, Texas // October 15, 2015 — Cloud builders, operators and users unwrap a lengthy wish list of new features and refinements today with the Liberty release of OpenStack, the 12th version of the most widely deployed open source software for building clouds. With the broadest support for popular data center technologies, OpenStack has become the integration engine for service providers and enterprises deploying cloud services.

 

Available for download today, OpenStack Liberty answers the requests of a diverse community of the software’s users, including finer-grained management controls, performance enhancements for large deployments and more powerful tools for managing new technologies like containers in production environment.

 

Enhanced Manageability
Finer-grained access controls and simpler management features debut in Liberty. New capabilities like common library adoption and better configuration management have been added in direct response to the requests of OpenStack cloud operators. The new version also adds role-based access control (RBAC) for the Heat orchestration and Neutron networking projects. These controls allow operators to fine tune security settings at all levels of network and orchestration functions and APIs.

 

Simplified Scalability
As the size and scope of production OpenStack deployments continue to grow—both public and private—users have asked for improved support for large deployments. In Liberty, these users gain performance and stability improvements that include the initial version of Nova Cells v2, which provides an updated model to support very large and multi-location compute deployments. Additionally, Liberty users will see improvements in the scalability and performance of the Horizon dashboard, Neutron networking Cinder block storage services and during upgrades to Nova’s compute services.

 

Extensibility to Support New Technologies
OpenStack is a single, open source platform for management of the three major cloud compute technologies; virtual machines, containers and bare metal instances. The software also is a favorite platform for organizations implementing NFV (network functions virtualization) services in their networking topologies. Liberty advances the software’s capabilities in both areas with new features like an extensible Nova compute scheduler, a network Quality of Service (QoS) framework and enhanced LBaaS (load balancing as a service).

 

Liberty also brings the first full release of the Magnum containers management project. Out of the gate, Magnum supports popular container cluster management tools Kubernetes, Mesos and Docker Swarm. Magnum makes it easier to adopt container technology by tying into existing OpenStack services such as Nova, Ironic and Neutron. Further improvements are planned with new project, Kuryr, which integrates directly with native container networking components such as libnetwork.

 

The Heat orchestration project adds dozens of new resources for management, automation and orchestration of the expanded capabilities in Liberty. Improvements in management and scale, including APIs to expose what resources and actions are available, all filtered by RBAC are included in the new release.

 

1,933 individuals across more than 164 organizations contributed to OpenStack Liberty through upstream code, reviews, documentation and internationalization efforts. The top code committers to the Liberty release were HP, Red Hat, Mirantis, IBM, Rackspace, Huawei, Intel, Cisco, VMware, and NEC.

 

Focus on Core Services with Optional Capabilities
During the Liberty release cycle, the community shifted the way it organizes and recognizes upstream projects, which became known by community members as the “big tent.” Ultimately, the change allows the community to focus on a smaller set of stable core services, while encouraging more innovation and choice in the broader upstream ecosystem.

The core services, available in every OpenStack-Powered product or public cloud, center around compute (virtualization and bare metal), storage (block and object) and networking.

New projects added in the last six months provide optional capabilities for container management (supporting Kubernetes, Mesos and Docker Swarm) with Magnum, network orchestration with Astara, container networking with Kuryr, billing with CloudKitty and a Community App Catalog populated with many popular application templates. These new services join already recognized projects to support big data analysis, database cluster management, orchestration and more.

 

Supporting Quotes
“Liberty is a milestone release because it underscores the ability of a global, diverse community to agree on technical decisions, amend project governance in response to maturing software and the voice of the marketplace, then build and ship software that gives users and operators what they need. All of this happens in an open community where anyone can participate, giving rise to an extensible platform built to embrace technologies that work today and those on the horizon.”
— Jonathan Bryce, executive director, OpenStack Foundation

 

“We use OpenStack because it delivers the core services we need in a production cloud platform that can extend to new technologies like containers. The ability to embrace emerging technologies as an open community rather than going solo is a primary reason why we’re sold on OpenStack.”
— Lachlan Evenson, cloud platform engineering, Lithium Technologies

 

“OpenStack has emerged as an increasingly capable and widely deployed open cloud technology. The companies using it successfully are those that have done their research, engaged with the project’s community and deployed in manageable stages. We expect OpenStack-based service providers will outgrow the overall IaaS service provider market through 2019.”
— Al Sadowski, research director, 451 Research

 

“Notable Fortune 100 enterprises like BMW, Disney, and Wal-Mart have irrefutably proven that OpenStack is viable for production environments. These are regular companies, not firms that were born digital like Etsy, Facebook, and Netflix. OpenStack’s presence in the market is now accelerating, leveraging the success of these pioneers.”
— Lauren Nelson, senior analyst, Forrester Research, as written in “OpenStack Is Ready — Are You?,” a May 2015 report from Forrester Research.

CloudSpaces project gets the OCEAN’s Quality Open Cloud label

 

I’m proud to announce the R&D Project CloudSpaces, partially funded by FP7 Programme of the European Union, has obtained the Quality Check of the OCEAN  project.

 

   

As they say, only 20 over 74 open cloud projects in the OCD received an OCEAN Open Cloud label:

-  7 Open Cloud projects obtained the Quality Checked by OCEAN label 2014.

- 13 Open Cloud projects obtained the Reviewed by OCEAN label 2014.

 

The CloudSpaces project is been developed by a consortium integrated by 3 Universities: “Rovira i Virgili”, Eurecom (France), and Ecole Polytechnique Fédérale de Lausanne (Switzerland), and 3 Companies: EyeOs, NEC and, of course, TISSAT.

 

Besides, it should be remembered that CloudSpaces is the project where it’s been developed StackSync (a personal cloud software) that recently wined 3 “Software Libre 2014” open software awards (see my last post in 2014-nov-07).

 

Please let me partially quote its e-mail with more data about the OCEAN’s Open Cloud Quality label.

 

- – - – - – - – - – - – - – - – - – - – - – - – - – -

Dear Open Cloud Supporter,

I’m glad to inform you that your Cloud Project has been evaluated by the OCEAN project team (www.ocean-project.eu) and received the Quality Checked by OCEAN label.

 

The OCEAN Open Cloud labels recognize innovative assets, new concepts, architecture documentation and/or re-usable open source cloud components described in the Open Cloud Directory (OCD).

 

The Open Cloud Directory 2014 brochure contains a short description of your project. Included links and QR codes give access to project details such as technologies, licenses, classification, and quality reports about submitted open source codes.

 

Your OCEAN Open Cloud label offers several dissemination opportunities:

1- Your project is listed in the Open Cloud Directory Brochure – to be distributed at OpenStack Summit Paris and upcoming cloud events.

2- You can use the attached OCEAN Open Cloud label and place it on your website and documentation with a direct link to the Open Cloud Directory : http://www.ocdirectory.org/

3- Do not hesitate to mention your OCEAN Open Cloud label on social networks, in your dissemination deliverables and Press Releases.

 

Only 20 over 74 open cloud projects in the OCD received an OCEAN Open Cloud label:
-  7 Open Cloud projects obtained the Quality Checked by OCEAN label 2014
- 13 Open Cloud projects obtained the Reviewed by OCEAN label 2014

On behalf of the entire OCEAN project team, congratulations to your consortium!

StackSync has wined 3 “Software Libre 2014” awards

    

I’m proud to announce that StackSync (http://stacksync.org/), an open-source scalable software (for personal clouds built on OpenStack) developed jointly by the “Rovira i Virgili” University (Tarragona, Spain) and the company Tissat, inside the CloudSpaces Project that is partially funded by European Commission (under the FP7 R&D Programme), has got 3 “Software Libre” (free software) awards in the 2014 call (its 6^th edition). The “Software Libre” is an initiative of “PortalProgramas”.

StackSync has wined in the 3 categories it has competed:

- ESENCIAL PARA EMPRESAS (essential for companies)

- ESENCIAL PARA LA TECNOLOGÍA (essential for technology)

- MAYOR POTENCIAL DE CRECIMIENTO (bigger potential growing)

It that categories it competes against other famous software as, LibreOffice, Ubuntu, NetBeans, Gecos, QVD, and so on

More details here or clicking in the “GANADOR” word in the red label of the next award logos:

“Juno” release of OpenStack has just been delivered

This post is only to remember that last Friday (October the 17^th) the new version of OpenStack, named Juno, was released.

 

As Stefano Maffulli says in its e-mail to the OpenStack community, IT IS THE RESULT OF THE EFFORT OF 1.419 PERSONS, from 133 organizations, that contributed to its development. OpenStack Juno is tenth release of the open source software for building public, private, and hybrid clouds and it has 342 new features to support software development, big data analysis and application infrastructure at scale.

 

Let me make emphasis that in this new version, Sahara it’s completely integrated (it was in incubation in the previous vesion). Sahara is the Data Processing module based in Hadoop for Big Data processing suport, i.e. this module capabilities let automate provisioning and management of big data clusters using Hadoop and Spark. Big data analytics are a priority for many organizations and a popular use case for OpenStack, and this service lets OpenStack users provision needed resources more quickly.

 

Another significant advance is that the foundation for Network Functions Virtualization (NFV) has been consolidated in Juno, providing improved agility and efficiency in telco and service provider data centers.

 

Let me copy and mix from the Juno website and the Official Press Release for summarizing the main features (module by module):

• Compute (Nova). Operational updates to Compute include improvements for rescue mode that enable booting from alternate images with the attachment of all local disks. Also, per-network settings are now allowed by improved nova-network code; scheduling updates to support scheduling services and extensibility; and internationalization updates. Key drivers were added such as bare metal as a service (Ironic) and Docker support through StackForge. Additional improvements were made to support scheduling and live upgrades.
• Object Storage (Swift). Object Storage hit a major milestone this release cycle with the rollout of storage policies. Storage policies give users more control over cost and performance in terms of how they want to replicate and access data across different backends and geographical regions. Other new features include updated support for the Identity project (Keystone) and account to account copy feature rollout. Additional work on erasure coding within object storage continues and is expected sometime during the Kilo release cycle.
• Block Storage (Cinder). Block Storage added ten new storage backends this release and improved testing on third-party storage systems. Cinder v2 API integration into Nova was also completed this cycle. The block storage project continues to mature each cycle building out core functionality with a consistent contributor base.
• Networking (Neutron). Networking features support for IPv6 and better third-party driver testing to ensure consistency and reliability across network implementations. The release enables plug-ins for the back-end implementation of the OpenStack Networking API and blazes an initial path for migration from nova-network to Neutron. Supporting Layer 3 High Availability, the networking layer now allows a distributed operational mode.
• Dashboard (Horizon). Dashboard rolled out the ability to deploy Apache Hadoop clusters in seconds, giving users the ability to rapidly scale data sets based on a set of custom parameters. Additional improvements include extending the RBAC system to support OpenStack projects Compute, Networking, and Orchestration.
• Identity Service (Keystone). Federated authentication improvements allow users to access private and public OpenStack clouds with the same credentials. Keystone can be configured to use multiple identity backends, and integration with LDAP is much easier.
• Orchestration (Heat). In Juno, it is easier to roll back a failed deployment and ensure thorough cleanup. Also, administrators can delegate resource creation privileges to non-administrative users. Other improvements included implementation of new resource types and improved scalability.
• Telemetry (Ceilometer). Telemetry reported increases in performance this cycle as well as efficiency improvements including metering of some types of networking services such as load balancers, firewalls and VPNs as a service.
• Database Service (Trove). The database service went through its second release cycle in Juno delivering new options for MySQL replication, Mongo clustering, Postgres, and Couchbase. A new capability included in Juno allows users to manage relational database services in an OpenStack environment.
• Image Service (Glance). The Image Service introduced artifacts as a broader definition for images during Juno. Other key new features included asynchronous processing, a Metadata Definitions Catalog and restricted policies for downloading images.
• Data Processing (Sahara). The new data processing capability automates provisioning and management of big data clusters using Hadoop and Spark. Big data analytics are a priority for many organizations and a popular use case for OpenStack, and this service lets OpenStack users provision needed resources more quickly.

 

In Tissat we’ve been testing the last beta versions and they look great, and we are starting to plan the migration IN LIVE.

Yesterday VMware announced it own OpenStack distro

Due to last hard work weeks (even months) and further vacations period I’ve not been active in this blog, however the following news have made me change:

 

Yesterday VMware announced it own OpenStack distro.

Let me quote the original VMware’s advertisement (underlying, by my own criteria, some of the ideas):

 

Today (Aug 25, 2014) at VMworld 2014, VMware announced the following: VMware Integrated OpenStack

 

– VMware Integrated OpenStack is a new solution that will enable IT organizations to quickly and cost-effectively deliver developer-friendly OpenStack APIs and tools on top of their existing VMware infrastructure. The VMware Integrated OpenStack distribution will leverage VMware’s proven technologies for compute, network, storage and management to provide enterprise-class infrastructure that reduces CAPEX, operational expense (OPEX) and total cost of ownership for production-grade OpenStack deployments.

 

With the VMware Integrated OpenStack distribution, customers can quickly stand up a complete OpenStack cloud to provide API-driven infrastructure for internal developers, and to repatriate workloads from unmanageable and insecure public clouds. IT can manage and troubleshoot an OpenStack cloud with the same familiar VMware tools they already use every day, providing significant operational cost savings and faster time-to-value.

 

Read more about the forthcoming VMware Integrated OpenStack solution here.

Of course, VMware’s Integrated OpenStack doesn’t necessarily mean that VMware is pushing customers to use  OpenStack, as John Gilmartin, VP and GM of VMware’s software defined data center suite business unit, explained in an interview.

“Icehouse” release of OpenStack has just been delivered

This post is only to remember that, as foreseen, just a couple of days ago (Thursday, the 17^th) the new version of OpenStack, named Icehouse, was released.

 

As Stefano Maffulli says in its e-mail to the OpenStack community, IT IS THE RESULT OF THE EFFORT OF 1.202 PERSONS, from 120 organizations, that contributed to its development.

 

Approximately 350 new features has been added (rolling upgrades, federated identity, tighter platform integration, etc) , but in my opinion the most significant is that “OpenStack Database Service” (Trove), which was incubated during the Havana release cycle, is now available.

 

Other programs still in incubation (already developing during Icehouse) are Sahara (OpenStack Data Processing, i.e. to provision a Hadoop cluster on OpenStack), Ironic (OpenStack Bare Metal as a Service), Marconi (OpenStack Messaging) and, and we hope they go live in the next release of OpenStack, code-named Juno, foreseen in 6 month.

 

In Tissat we have been testing the last beta versions and they look great, and we are starting to plan the migration IN LIVE.

 

Quoted from the the official press release these are the main features (module by module):

• OpenStack Database Service (Trove): A new capability included in the integrated release allows users to manage relational database services in an OpenStack environment.
• OpenStack Compute (Nova): New support for rolling upgrades minimizes the impact to running workloads during the upgrade process. Testing requirements for third-party drivers have become more stringent, and scheduler performance is improved. Other enhancements include improved boot process reliability across platform services, new features exposed to end users via API updates (e.g., target machines by affinity) and more efficient access to the data layer to improve performance, especially at scale.
• OpenStack Object Storage (Swift): A major new feature is discoverability, which dramatically improves workflows and saves time by allowing users to ask any Object Storage cloud what capabilities are available via API call. A new replication process significantly improves performance, with the introduction of s-sync to more efficiently transport data.
• OpenStack Block Storage (Cinder): Enhancements have been added for backend migration with tiered storage environments, allowing for performance management in heterogeneous environments. Mandatory testing for external drivers now ensures a consistent user experience across storage platforms, and fully distributed services improve scalability.
• OpenStack Networking (Neutron): Tighter integration with OpenStack Compute improves performance of provisioning actions as well as consistency with bulk instance creation. Better functional testing for actions that require coordination between multiple services and third-party driver testing ensure consistency and reliability across network implementations.
• OpenStack Identity Service (Keystone): First iteration of federated authentication is now supported allowing users to access private and public OpenStack clouds with the same credentials.
• OpenStack Orchestration (Heat): Automated scaling of additional resources across the platform, including compute, storage and networking is now available. A new configuration API brings more lifecycle management for applications, and new capabilities are available to end-users that were previously limited to cloud administrators. Collaboration with OASIS resulted in the TOSCA Simple Profile in YAML v1.0, demonstrating how the feedback and expertise of hands-on OpenStack developers can dramatically improve the applicability of standards.
• OpenStack Telemetry (Ceilometer): Improved access to metering data used for automated actions or billing / chargeback purposes.
• OpenStack Dashboard (Horizon): Design is updated with new navigation and user experience improvements (e.g., in-line editing). The Dashboard is now available in 16 languages, including German, Serbian and Hindi added during this release cycle.

 

And these are other interesting links:

• The source code
• The Webinar: OpenStack Icehouse Release Update
• The release notes
• The Icehouse Activity Report
• The official press release

Virtualization vs. Cloud Computing (III): business differences, plus other technical ones, and conclusions

Once again let me start reminding that this post is referred to the scope and context defined in my first post of this series (titled “Virtualization vs Cloud Computing (I): what are we going to compare?”), although at the end of this post we’ll widen it.

 

Besides, as summary, in the two previous posts we concluded:

• Virtualization is an enabling technology for Cloud Computing, one of the building blocks used “generally” for building Cloud Computing solution (“generally” but not always, because nowadays Cloud is starting to use other technologies away from pure virtualized environments to offer  “Baremetal as a Services” …)
• The services provided by “Cloud Computing Management Environment” and by a “Virtualization Management Environment” ARE QUITE DIFFERENT IN HOW THE SERVICES ARE PROVIDED: both the self service characteristic and location independence feature (in the sense of no location knowledge) are the main difference, but in some cases (depending on the platform) also massive scale out.

 

Going to the subject, another technological point of comparison is that Virtualization Management Environment (at the present almost none) does not offer to the user the knowledge in real time of how long it has been using the VM and other metrics of the service (“measured services” is a essential characteristic), or maybe the user can get that knowledge but not in a friendly way. The main reason for that is the different business model they were “initially” thought of:

• Virtualization was born to take advantage of unused resources in a physical machine, solving several problems that appeared in scale-out servers: different physical characteristics for different cluster subsets (after one or more expansions), coarse granularity in the resource assignment that led to unused resources, security issues when applications from competing companies were run on the same physical machine. However, although virtualization allows to take advantage of unused resources in a secure way, in the practice it let to traditional DataCenter Service provider to pass (or add) from a (physical) “Hosting” business model to a “Virtual Hosting” model with lower prices, but the billing model was the same: in general the customer is billed in the same way as for physical hosting: a monthly fixed rate where the cost is proportional to the power (performances) of VM and the associated resources it has contracted, but disregarding of the real usage (the user does) of the virtual machine.
• Cloud Computing was born to “allow” a real pay-per-use model. For this reason it’s as important the self-serving feature as the capability to turn on or off the VM whenever the customer wants, because (s)he doesn’t pay for the standstill period. About this subject, please note that the technological Cloud Computing concept only defines that the services must be metered (and that information must be continuously available for the customer), what allows the provider to bill for the real usage, but it’s not mandatory to do it.
• Of course, both business models mentioned above were the two extremes of a broad market and represent the “pure” business models, but today there are several intermediate hybrid business models: for example, cloud computing environment based model that offer discounts if you contract for long fixed period or that offer lower price-per-hour if you pay a monthly fee (one of the Amazon options) or pure technological Virtualization Management Environment that offer pay-per-use business model, and so on. AMAZON (the great Cloud innovator) is a good example of that: for example, “Reserved Instances” give you the option to make a low, one-time payment for each instance you want to reserve and in turn receive a significant discount on the hourly charge for that instance (there are three Reserved Instance types: Light, Medium, and Heavy Utilization Reserved Instances, that enable you to balance the amount you pay upfront with your effective hourly price), the also offer volume discounts or “Spot Instances”, and so on.

 

Finally, concerning to the comparison points in the initial (reduced) scope defined, new customers needs are emerging to deploy applications on your physical servers, as well as your virtual servers, but keeping all the cloud model advantages (and essential characteristics): that’s the case, for example, when your application requires physical servers, or your production environment is too performance sensitive to run in VMs. Actually you don’t need to have a virtualized environment to be considered a cloud environment: your “virtual” instance might be a “container” which is not virtualized but running on bare metal (just sharing it with other containers) or even running directly and using completely the bare metal: “containers”, as aforesaid, are considered by some authors as sort of virtualization; so let me present an example of the latter case: OpenStack is currently developing the new “Iron” module that it’ll provide “Baremetal as-a-Service”, so  it’ll be possible to use the same API and the same pipeline to build, test, and deploy applications on both virtual and physical machines. Therefore, cloud technology is starting to use other technologies away from pure paravirtualized environments.

 

We initially limited the scope of this comparison to “compute as a resource”, but if we slightly widen that context to include (as usual) any computing related resources, i.e, storage, and communications resources, then new differences arise (depending on the solution that was used for building both the Cloud Management Environment and the Virtualization Management Environment):

• Most (but not all) of Virtualization Management Environments offer only compute and block storage services, but usually they do not offer Object Storage as a Service; besides they use to offer “Storage Virtualization” (SV, i.e. capacity is separated from specific storage hardware resources) but don’t offer “Software Defined Storage” (SDS), that differs from the former (SV) because in the SDS not only capacity but also services are separated from the storage hardware.
• Moreover, and almost none of them (Virtualization Management Environments) offers communications management as a Services. I mean not only virtual networks, but also main communications devices provided as a service: router, firewallls, load balancers and so on. Moreover, the “Software Defined Networking” (SDN) it’s a technology that, as far as I now, is been currently used only in Cloud Computing Environments where this kind of services are starting to be offered. Of course, some Virtualization Environments offer this kind of communication services, but not in a self-service way and where you can self-define your internal communications layout and structure, and so on, e.g. as shown in the next picture (taken from the topology designed by a customer using the TISSAT’s Cloud Platform mounted on OpenStack):

TISSAT’s IaaS Cloud Platform

 

 

At the end of this 3 post series, as summary, three conclusions:

1. The technological concepts (virtualization and cloud computing) should not be confused with the pure business models they were initially intended for: virtual hosting (a fixed monthly rate lower that physical hosting) and pay-per-use (that some person call the Cloud Computing business model), respectively. And don’t forgot that at the present there are a lot of mixed business models disregarding the underlying technology.
2. Both virtualization and cloud computing allow you to do more with the hardware you have by maximizing the utilization of your computing resources (and therefore, if you are contracting the service you can expect lower expenses). However, although currently there is an inevitable connection between them, since the former (virtualization) is “generally” used to implement the latter (cloud), this connection could be broken soon with the arising of new technologies and innovations, and they are not exactly the same: BOTH ARE QUITE DIFFERENT IN HOW THE SERVICES ARE PROVIDED (self service feature, no location knowledge, massive scale out, even metered service in some cases) and there are some technical differences between them. Additionally, depending on user’s needs one of them could be better or not: a lot of customers have enough with server virtualization, and it could even be the best solution for their needs; but in other cases cloud is the best solution for the customer’s needs, and no virtualization.
3. Although still circumscribed to IaaS (i.e. forgetting PaaS and Saas), when we widen the comparison scope to include (as usual) any computing related resources, (not only compute but also storage and communications resources), then new differences arise since, for example, communications related Services (routing, firewalls, load balancing, etc.) are seldom (or never) offered as a Service in Virtualized Management Environments (in a self-service way and where you can self-define your internal communications layout and structure, and so on, taking advantage of Software Defined Networking technology). Besides, another main difference is how the Storage as a Service is provided: in a Virtualization Environment use to be reduced to Block Storage, no including Object Storage (as Cloud Environments do), and provided as Storage Virtualization but not as Software Defined Storage.

Note: Please, let me add that  Tissat (the company I’m working for) is offering all this sort of real IaaS Cloud Services as well more traditional DataCenter services (such as housing, hosting, virtualized hosting, DRP, and so on) based on its Data Centers Federation (that includes Walhalla, a DC certified as Tier IV by The Uptime Institute)  and using different product and solutions (currently VmWare, OpenStack, and so on) and most of the ideas of this post series are extracted from that experience.