"Manufacturing Polkadot Warplanes" -- build for change. Introduces Red Hat PaaS and OpenStack story. Public release of CORNERSTONE solution.

1. Manufacturing
Polkadot Warplanes
Shawn Wells | shawn@redhat.com

5. http://www.npr.org/2011/09/07/140256967/shipping-container-inventor-transformed-world-trade

8. STORAGE
(RHS)
HARDWARE
(x86)
VIRTUALIZATION
(RHEV)
OPERATING SYSTEM
(RHEL)
APPLICATION PLATFORM
(JBOSS, PHP, RUBY, ETC)
APPLICATION
Provider Managed
Managed and
Controlled by
Customer
IaaS PaaS SaaS
Increased Control
Increased Automation

9. STORAGE
(RHS)
HARDWARE
(x86)
VIRTUALIZATION
(RHEV)
OPERATING SYSTEM
(RHEL)
APPLICATION PLATFORM
(JBOSS, PHP, RUBY, ETC)
APPLICATION
Provider Managed
Managed and
Controlled by
Customer
IaaS PaaS SaaS
Increased Control
Increased Automation

10. STORAGE
(RHS)
HARDWARE
(x86)
VIRTUALIZATION
(RHEV)
OPERATING SYSTEM
(RHEL)
APPLICATION PLATFORM
(JBOSS, PHP, RUBY, ETC)
APPLICATION
Provider Managed
Managed and
Controlled by
Customer
IaaS PaaS SaaS
Increased Control
Increased Automation

11. CRAFTWORK → MASS PRODUCTION
With PaaSVirtualized
How to Build an App:
1. Have Idea
2. Get Budget
3. Submit hardware acquisition request
4. Wait
5. Get Hardware
6. Rack and Stack Hardware
7. Install Operating System
8. Install Operating System
Patches/Fix-Packs
9. Create user Accounts
10. Deploy framework/appserver
11. Deploy testing tools
12. Code
13. Test
14. Configure Prod servers (and buy
them if needed)
15. Push to Prod
16. Launch
17. Order more servers to meet demand
18. Wait…
Physical

12. CRAFTWORK → MASS PRODUCTION
With PaaS
How to Build an App:
1. Have Idea
2. Get Budget
3. Submit VM Request request
4. Wait
5. Deploy framework/appserver
6. Deploy testing tools
7. Code
8. Test
9. Configure Prod VMs
10. Push to Prod
11. Launch
12. Request More Prod VMs to
meet demand
13. Wait
14. Deploy app to new VMs
15. Etc.
Virtualized
How to Build an App:
1. Have Idea
2. Get Budget
3. Submit hardware acquisition request
4. Wait
5. Get Hardware
6. Rack and Stack Hardware
7. Install Operating System
8. Install Operating System
Patches/Fix-Packs
9. Create user Accounts
10. Deploy framework/appserver
11. Deploy testing tools
12. Code
13. Test
14. Configure Prod servers (and buy
them if needed)
15. Push to Prod
16. Launch
17. Order more servers to meet demand
18. Wait…
Physical

13. CRAFTWORK → MASS PRODUCTION
With PaaS
How to Build an App:
1. Have Idea
2. Get Budget
3. Code
4. Test
5. Launch
6. Automatically Scale
How to Build an App:
1. Have Idea
2. Get Budget
3. Submit VM Request request
4. Wait
5. Deploy framework/appserver
6. Deploy testing tools
7. Code
8. Test
9. Configure Prod VMs
10. Push to Prod
11. Launch
12. Request More Prod VMs to
meet demand
13. Wait
14. Deploy app to new VMs
15. Etc.
Virtualized
How to Build an App:
1. Have Idea
2. Get Budget
3. Submit hardware acquisition request
4. Wait
5. Get Hardware
6. Rack and Stack Hardware
7. Install Operating System
8. Install Operating System
Patches/Fix-Packs
9. Create user Accounts
10. Deploy framework/appserver
11. Deploy testing tools
12. Code
13. Test
14. Configure Prod servers (and buy
them if needed)
15. Push to Prod
16. Launch
17. Order more servers to meet demand
18. Wait…
Physical

14. Row 1 Row 2 Row 3 Row 4
0
2
4
6
8
10
12
Column 1
Column 2
Column 3
MANUFACTURING FOUNDATIONS
(for IaaS)

15. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

16. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

17. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

18. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

19. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

20. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

21. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

22. RED HAT OPENSTACK
- MODULAR ARCHITECTURE
- DESIGNED TO SCALE OUT
- BASED ON (GROWING) SET OF CORE SERVICES

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

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

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

26. Row 1 Row 2 Row 3 Row 4
0
2
4
6
8
10
12
Column 1
Column 2
Column 3
SOLUTION ENABLEMENT:
CORNERSTONE

27. 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

28. CORNERSTONE

29. CORNERSTONE

30. PANDORA RADIO

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

33. DESIGN CONSIDERATIONS
INFRASTRUCTURE
- Integration with PKI (NSA CASPORT), Active Directory,
LDAP
-
-

34. DESIGN CONSIDERATIONS
INFRASTRUCTURE
- Integration with PKI (NSA CASPORT), Active Directory,
LDAP
- Data retains encryption across backup and disaster
recovery
-

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

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

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)

38. SECURITY
- FIPS VALIDATION
* Federal Information Processing Standard 140-2
- COMMON CRITERIA CERTIFIED FOUNDATIONS
* Operating System: EAL4+, CAPP/RBAC/LSPP
* Crypto: EAL2+
- MULTIPLE ALGORITHM SUPPORT
* AES (256 bits, 196 bits, 128 bits)
* TripleDES (168)
* SHA-2 hash functions (SHA-224, -256, -384, -512)
* ECC and RSA TLS protocols

41. HDFS vs CORNERSTONE

42. Row 1 Row 2 Row 3 Row 4
0
2
4
6
8
10
12
Column 1
Column 2
Column 3
MANUFACTURING FOUNDATIONS
(for PaaS)

43. PaaS = Platform as a Service
Code Deploy Run

44. OPENSHIFT STRATEGY
Public
Cloud
Service

45. OPENSHIFT STRATEGY
Public
Cloud
Service
On-
premise
or Private
Cloud
Software

46. OPENSHIFT STRATEGY
origin
Public
Cloud
Service
On-
premise
or Private
Cloud
Software
Open
Source
Project

47. WEB CONSOLE

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

49. ECLIPSE, TOO.

50. HOW IT WORKS

51. YES, WE STILL HAVE INFRASTRUCTURE
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal

52. RHEL IS THE FOUNDATION
RHEL RHEL RHEL
OpenShift is Built on Instances of
Red Hat Enterprise Linux (RHEL)
RHEL
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal

53. RHEL GIVES US MULTI-TENANCY
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
RHEL RHEL
SELinux Policies securely subdivide
the Node instances.
RHEL

54. RHEL GIVES US MULTI-TENANCY
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
RHEL RHEL
SELinux Policies securely subdivide
the Node instances.
RHEL RHEL RHEL
CARTRIDGES are how
OpenShift installs
Languages & Middleware
Broker Node Node Node
RHEL
JBoss MySQL

55. CARTRIDGES

56. EVERYTHING DEVELOPERS ALREADY USE

57. YES, YOU CAN BUILD YOUR OWN
AWS / CloudForms / OpenStack (IaaS) / RHEV (Virt) / Bare Metal
RHEL RHEL
SELinux Policies securely subdivide
the Node instances.
RHEL RHEL RHEL
CARTRIDGES are how
OpenShift installs
Languages & Middleware
Broker Node Node Node
RHEL
JBoss MySQL
Developers can add custom
language, data-store, or
middleware with with a custom
Cartridge.
CUSTOMEtc.
Etc.
Ruby
Python
PHP
Java
Postgres
MySQL
OpenShift Default
Cartridges

58. Established New