Slide overview of Red Hat OpenShift Enterprise 2 Private PaaS product launch. Includes slides from Cisco and FICO use cases. References integration with OpenStack and Docker.
4. 20-50
# OF LIVE APPLICATION UPDATES PER DAY AT ECOMMERCE FIRM
100’s
# OF APPLICATIONS LAUNCHED PER MONTH BY MAJOR MOTION
PICTURE STUDIO
15,000
# OF JVMS SUPPORTING APPLICATIONS AT FORTUNE 100 FIRM
4
10. OPENSHIFT IS
PaaS BY RED HAT
ü Multi-language
ü Auto-scaling
ü Self-service
ü Open Source
ü Enterprise-grade
ü Secure
ü Built on Red Hat
10
11. RED HAT’S PaaS STRATEGY
Open Source
PaaS
Project
Public PaaS
Service
11
On-premise or
Private PaaS
Software
12. OPENSHIFT INNOVATION
Over 50 new features and
enhancements in past year
60
40
20
0
New Features
and
Enhancements
OpenShift Online
Updates
2013
15 service
updates in
past year
12
OpenShift
Enterprise
Releases
4 product
releases in
past year
13. OPENSHIFT RECOGNITION
Source: Gartner, Magic Quadrant for On-Premises
Application Platforms, June 27, 2013
This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in
the context of the entire document. The Gartner document is available upon request from Red Hat, Inc..
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not
advise technology users to select only those vendors with the highest ratings. Gartner research publications
consist of the opinions of Gartner's research organization and should not be construed as statements of fact.
Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of
merchantability or fitness for a particular purpose.
13
15. OPENSHIFT ONLINE
Latest Update Expands
Availability and Reduces
Prices
Public
PaaS
Service
15
•
•
•
50% price reduction on Gear/Hrs
New Large 2GB Gear Sizes
Available in 14 New countries
16. Building on a successful year selling to
some of the worlds biggest enterprise
customers, Red Hat is proud to
announce…
2
16
18. OPENSHIFT ENTERPRISE
Empowering Ops with
Enterprise Features
JBoss
RHEL
Broker
Node
Web Console
Eclipse IDE
Cmd Line
MySQL
•
•
•
•
RHEL
Node
Self-Service
On-Demand
Automated
Elastic
RHEL
Node
Public / Hybrid / Private / Virtualization / Bare Metal
18
Self-Service for Developers, Efficiency for Operations
19. WHAT'S NEW IN OPENSHIFT ENTERPRISE 2
ü Red Hat has teamed with our customers
to drive open source innovation:
New &
Updated
Languages
Admin
Console
OpenStack
Integration
Web Routing
Layer and HA
Enhancements
Dev Team
Collaboration
Deployment
Enhancements
19
23. OPENSTACK HEAT INTEGRATION
l
OpenShift component Disk Images
l
HEAT Orchestration Templates
l
Automatically Deploy OpenShift on OpenStack!
Images
Result in OpenShift Deployed on
OpenStack
Plus HEAT deployment
Metadata
23
24. AND, STILL THE BEST PaaS DEVELOPER
EXPERIENCE FOR ENTERPRISE JAVA
ü JBoss EAP delivers EE6 with CDI
ü JBoss WS delivers Tomcat
ü Jenkins for Continuous Integration
ü Maven for Build Management
ü JBoss Tools and Eclipse
24
25. WHAT’S NEXT?
RED HAT AND DOCKER TEAM ON CONTAINERS
RHEL
CGroups
Node (RHEL)
SELinux
Broker (RHEL)
GEAR
My
App
GEAR
Her
App
Red Hat Enterprise Linux
Node (RHEL)
Node
ü Red Hat is teaming with Docker to drive
converged Container technology
25
IDLED
26. MORE COMMUNITY MOMENTUM:
Partnering to extend the Platform
DEVELOPER
Java
JBoss EAP
RHEL
PHP
MY GEAR
Broker (RHEL)
JBoss EWS
JBoss
Python
MySQL
MySQL
jenkins
cron
logs
sshd
Node (RHEL)
Red Hat Enterprise Linux
Node (RHEL)
Node
ü Red Hat is teaming with Jelastic to drive
Cartridge Standard for PaaS
26
Ruby
Postgres
Node.js
Mongo
Perl
Maven
Jenkins
CUSTOM
CARTRIDGES
27. OPENSHIFT
Letting you manufacture
applications with...
Velocity
•
•
•
•
•
DevOps
Continuous Delivery
Dynamic Languages: Node.js, Ruby,
PHP, Python
Mobile and Responsive Web
NoSQL
Stability
•
•
•
•
•
Enterprise Java EE6 via JBoss
Multi-tenancy and Security via Red Hat
Enterprise Linux
Jenkins, Maven, Git
Auto-Scaling
Extensible and No-Lock-in
Public PaaS and Enterprise PaaS supported by Red Hat
27
30. The Problem that Needed Solving
Business needs
- Reduce TtV (Time to Value) for our customers
- Create opportunities in Mid-Market
- Engage community of customers’ data scientists
Technology needs
- Private cloud & On-prem (and Public cloud option)
30
31. How OpenShift was Used
Cloud features (self provisioning, auto-scaling)
Templatized deployment (custom cartridges)
Completely abstracted (FICO cloud controller)
31
32. Tips or Best Practices
Node settings critical for performance in gear creation
Fine tune Idling
Invest heavily in monitoring
32
34. The Problem that Needed Solving
1 to 2 minutes to create virtual machines followed by
several days if not weeks of platform configurations (web,
app, db, etc..).
Developers did not have Web Masters’ skills.
Agility & speed required to configure new environments
put significant strain on Infrastructure resources (WM,
SA, etc..).
34
Java/JEE is 70% of apps but php, Python are growing
fast.
35. How OpenShift was Used
Initially used as “developer” PaaS.
Cartridges most commonly used include mySQL, PHP,
Python.
Building Self & Community Support for Cartridges.
Building Stage & Prod PaaS—in synch with Jan Release.
Leveraging existing App deployment tools for lifecycle mgt.
Leveraging Auto-scaling for Priority 2 & 3 Applications.
35
36. Tips or Best Practices
Educate your developer community on what PaaS is and
as important what PaaS is Not!
Start with “developer” PaaS, followed by non-business
critical apps, then move to BC apps.
Align with PaaS roadmap rather than building potentially
throw-away workarounds!
36