Removing the G-Cloud lock inGovernment ICT 2.0 - Seminar Session One16th September 2014Jeremy Brown – Head of Middleware UK&I, Red Hatjeremy@redhat.com@tenfourty

Lock-In?

A Historical Perspective on Lock-In in IT

So, How to Prevent Lock-In?1980’s: Standards!

1990’s: FOSS – Free Open Source Software

And then comes The CloudCloud will be the ultimate lock-in

Back to the Future w lock-in

The Broken Way : without open standards

● The vendor defines the level playing field● Direct Interoperability● NDA, IPR● 1:1 deals,no openness

● Closed market● No verificationpossible bythird party

Open standards required!

Open Standards allow you the flexibility to make the best choice

for your business

The Better Way : with open standards

The Standard defines the levelplaying field

Open market 1:n relation Implementationscan be verifiedby third parties

What is an open standard?

A standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed (e.g. open process).

Benefits of open standards● Application & platform independence● Long-term access

● Architectural integrity

CHOICE!!!!

Discussion:

How is open source different from open standards?

No Lock-In on where- On-Premise, Hosted, Hybrid

● Cloud should provide flexibility in where applications can run

● Hosted Cloud

● Needs Secure, Fine-grained, Multi-tenancy

● On-Premise Cloud

● Should run on choice of Hypervisors

● Hybrid-Cloud

● Leverage benefits of scale when needed

OpenStack

Amazon

vSphere

RedHatEnterprise

Virtualization

No Lock-Out on Operational Model

● You have real-world restrictions that impact Cloud● Governance, Compliance, Ent. Arch Standards, ITIL, Security, etc.

● Your Cloud must support different Models

Benefits of No Lock-In

o Productivity

• Let Developers work the way they want to work

o Agility

• Move and Scale applications to adapt to changing business conditions

o Survivability

• Minimize the impact of hosting providers

o Accountability

• Control Costs

Insist on Open

o Open Source

o Open Standards

o Open APIs

Open Hybrid Cloud

OPEN STANDARDS

Private Cloud (Customer Datacenter)

Public Cloud(Amazon, Rackspace, Google,

etc.)

Hybrid Cloud

Fact: All customer & service provider data centers have HETEROGENOUS technology from MULTIPLE vendors

Open Platform

● Open Standards are essential for the success of the Open Hybrid Cloud.

● Open Standards form the links between the Datacenter, Private Cloud, and Public Cloud.

● Open Standards are the DNA of Red Hat and JBoss.

● Adopt Open Standards whenever possible.

● Create new technology and drive to standards when possible.

Recommendations for an open cloud● (open) Standards for interoperability between all Key Reference Points

● Modular approach that offers fair competition, regardless of development model and license

● Reusability is best when the interfaces are stable and the upstream projects have proven to be sustainable

● Not all reference points can be standardised in this way

● Identify gaps, work with vendor/community ecosystem, move forward

● Identify Lock-In as risk on all Key Reference Points

● Closed APIs prohibit choice and Open Source participation

● Drive up cost

● Complicate interoperabilty

The UK Government already gets it...

https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs

Though I prefer this headline!

http://www.theregister.co.uk/2014/07/23/uk_government_officially_adopts_open_document_format/

YOUR MOTHER WAS RIGHTIT'S BETTER TO SHARE

SO LETS DO THE SAME FORTHE G-CLOUD

Goals of the Red Hat model● Bring Open Source Software to the enterprise

● Catalyst of Open Source Communities

● Faster technology innovation

● Open Standards

● Better quality

● Better price/performance

● Alignment to customer needs