IaaS
PaaS
SaaS
APPLICATION APPLICATION PLATFORM (JBOSS, PHP, RUBY, ETC) OPERATING SYSTEM (RHEL) VIRTUALIZATION (RHEV) HARDWARE (x86) STORAGE (RHS) Managed and Controlled by Customer Provider Managed
Increased Control Increased Automation
Slide 9
IaaS
PaaS
SaaS
APPLICATION APPLICATION PLATFORM (JBOSS, PHP, RUBY, ETC) OPERATING SYSTEM (RHEL) VIRTUALIZATION (RHEV) HARDWARE (x86) STORAGE (RHS) Managed and Controlled by Customer Provider Managed
Increased Control Increased Automation
Slide 10
IaaS
PaaS
SaaS
APPLICATION APPLICATION PLATFORM (JBOSS, PHP, RUBY, ETC) OPERATING SYSTEM (RHEL) VIRTUALIZATION (RHEV) HARDWARE (x86) STORAGE (RHS) Managed and Controlled by Customer Provider Managed
Increased Control Increased Automation
Slide 11
CRAFTWORK → MASS PRODUCTION Physical How to Build an App: 1. 2. 3. 4. 5. 6. 7. 8.
9. 10. 11. 12. 13. 14. 15. 16. 17. 18.
Have Idea Get Budget Submit hardware acquisition request Wait Get Hardware Rack and Stack Hardware Install Operating System Install Operating System Patches/Fix-Packs Create user Accounts Deploy framework/appserver Deploy testing tools Code Test Configure Prod servers (and buy them if needed) Push to Prod Launch Order more servers to meet demand Wait…
Virtualized
With PaaS
Slide 12
CRAFTWORK → MASS PRODUCTION Physical How to Build an App: 1. 2. 3. 4. 5. 6. 7. 8.
9. 10. 11. 12. 13. 14. 15. 16. 17. 18.
Have Idea Get Budget Submit hardware acquisition request Wait Get Hardware Rack and Stack Hardware Install Operating System Install Operating System Patches/Fix-Packs Create user Accounts Deploy framework/appserver Deploy testing tools Code Test Configure Prod servers (and buy them if needed) Push to Prod Launch Order more servers to meet demand Wait…
Virtualized How to Build an App: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.
Have Idea Get Budget Submit VM Request request Wait Deploy framework/appserver Deploy testing tools Code Test Configure Prod VMs Push to Prod Launch Request More Prod VMs to meet demand Wait Deploy app to new VMs Etc.
With PaaS
Slide 13
CRAFTWORK → MASS PRODUCTION Physical How to Build an App: 1. 2. 3. 4. 5. 6. 7. 8.
9. 10. 11. 12. 13. 14. 15. 16. 17. 18.
Have Idea Get Budget Submit hardware acquisition request Wait Get Hardware Rack and Stack Hardware Install Operating System Install Operating System Patches/Fix-Packs Create user Accounts Deploy framework/appserver Deploy testing tools Code Test Configure Prod servers (and buy them if needed) Push to Prod Launch Order more servers to meet demand Wait…
With PaaS
Virtualized How to Build an App: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.
Have Idea Get Budget Submit VM Request request Wait Deploy framework/appserver Deploy testing tools Code Test Configure Prod VMs Push to Prod Launch Request More Prod VMs to meet demand Wait Deploy app to new VMs Etc.
How to Build an App: 1. 2. 3. 4. 5. 6.
Have Idea Get Budget Code Test Launch Automatically Scale
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 16
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 17
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 18
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 19
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 20
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 21
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 22
RED HAT OPENSTACK - MODULAR ARCHITECTURE - DESIGNED TO SCALE OUT - BASED ON (GROWING) SET OF CORE SERVICES
Slide 23
RED HAT INVOLVEMENT - Be to OpenStack what Red Hat is to Linux - Create Enterprise Distribution * Supportability * Stability * Enterprise Features (e.g. security, performance) * Certified Ecosystem * Lifecycle
Slide 24
OPENSTACK RELEASE CADENCE - Upstream * Source code only * Releases every 6 months * No bugfixes / snapshots after next release - RDO (e.g. “Fedora” of OpenStack) * Follows upstream cadence * Delivers binaries
Slide 25
OPENSTACK RELEASE CADENCE - Red Hat OpenStack * Initially 1 year lifecycle (e.g. support for Folsum ends after Grizzly) * Will increase lifecycle over time (likely to move to 2 years) * Ecosystem of Support * Government Ready
CORNERSTONE Open, unified, and extensible scale-out object storage solution for on-premise, virtualized and cloud environments
Which includes Pervasive, flexible encryption with an innovative approach to unified symmetrical key management
Slide 28
CORNERSTONE
Slide 29
CORNERSTONE
Slide 30
PANDORA RADIO
Slide 31
Slide 32
DESIGN CONSIDERATIONS - Consistent, global information accessibility through REST API - Consistent access through high and low-latency networks - Cost effectiveness and scalability for big data growth - Open system, empowering developers
Slide 33
DESIGN CONSIDERATIONS INFRASTRUCTURE - Integration with PKI (NSA CASPORT), Active Directory, LDAP -
Slide 34
DESIGN CONSIDERATIONS INFRASTRUCTURE - Integration with PKI (NSA CASPORT), Active Directory, LDAP - Data retains encryption across backup and disaster recovery -
Slide 35
DESIGN CONSIDERATIONS INFRASTRUCTURE - Integration with PKI (NSA CASPORT), Active Directory, LDAP - Data retains encryption across backup and disaster recovery - Encrypted files do not require significant additional space; storage requirements change non perceptibly
Slide 36
DESIGN CONSIDERATIONS ADMINISTRATION - Role Based Access Control (RBAC), augmented with Mandatory (MAC) and discretionary (DAC) granularity - Real-time modification to access control policies, to include time limits, number of accesses, etc - All operations, including key access, are audited
Slide 37
DESIGN CONSIDERATIONS END-USER - De-identify sources & methods: Expand data encryption options to protecting relationships - Anonymize Datasets: Replace sensitive portions of data records with cryptographic pseudonyms - Protect and control access to multiple data sources from a query device (e.g. remote wireless tablet vs physical desk at DIA)
OPENSHIFT STRATEGY
Public Cloud Service
Onpremise or Private Cloud Software
Slide 46
OPENSHIFT STRATEGY Open Source Project
Public Cloud Service
origin
Onpremise or Private Cloud Software
Slide 47
WEB CONSOLE
Slide 48
CLI? OF COURSE Create Apps rhc app create -a javasample -t jbossas-7
Add MongoDB rhc app cartridge add -a javasample –c mongodb-2.0
Add add EAR file to your deployments directory cd javasample cp /path/to/ear/earfilename.ear ./deployments
Add the EAR file to git git add ./deployments/earfilename.ear
Push your code git push
Done
Slide 49
ECLIPSE, TOO.
Slide 50
HOW IT WORKS
Slide 51
YES, WE STILL HAVE INFRASTRUCTURE
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
Slide 52
RHEL IS THE FOUNDATION
OpenShift is Built on Instances of Red Hat Enterprise Linux (RHEL)
RHEL
RHEL
RHEL
RHEL
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
Slide 53
RHEL GIVES US MULTI-TENANCY
SELinux Policies securely subdivide the Node instances.
RHEL
RHEL
RHEL
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
Slide 54
RHEL GIVES US MULTI-TENANCY
JBoss
CARTRIDGES are how SELinux Policies securely subdivide OpenShift installs the Node MySQL instances. Languages & Middleware
RHEL Broker
Node
RHEL
RHEL
Node
Node
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
Slide 55
CARTRIDGES
Slide 56
EVERYTHING DEVELOPERS ALREADY USE
Slide 57
YES, YOU CAN BUILD YOUR OWN
Java
CARTRIDGES are how SELinux Policies securely subdivide OpenShift installs Postgres theEtc. Node CUSTOM MySQL instances. Languages & Middleware MySQL
PHP
JBoss Python Ruby Etc.
RHEL Broker
OpenShift Default Cartridges
Node
Developers can add custom RHEL RHEL language, data-store, or middleware with with a custom Node Cartridge. Node
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal