Slides used by Simon Haslam during a panel session about automated provisioning at the Oracle OpenWorld 2014 conference in San Francisco.
For more details see http://o-box.com/2014/10/o-box-oracle-openworld-2014
%+27788225528 love spells in Toronto Psychic Readings, Attraction spells,Brin...
How did we get here?! Choice of Chef for O-box
1. 1 | 10
1 • 8
How did we get here?! Choice of Chef for O-box
Simon Haslam
1 October 2014
2. 2 | 10
2 • 8
What is O-box SOA Appliance?
SOA in a box highly available secure best practices (e.g. EDG)
3. 3 | 10
3 • 8
Mid-2013: We need a provisioning tool! Requirements No wheel re-invention! Minimal extra cost Flexible
4. 4 | 10
4 • 8
Architecture
WebLogic Admin Server
Oracle Traffic Director
Oracle Traffic Director load balancer
SOA Cluster
EE/RON/RAC Database
OTD
Admin Server
O-box
Manager
5. 5 | 10
5 • 8
Considerations Features Platform support Underlying language Community License for commercial use (Central server or master-less)
6. 6 | 10
6 • 8
Provisioning Choice
Modern generation Puppet Chef Ansible Salt
Old generation CFengine
Home grown, e.g. supported by m4
Enterprise Manager (packs)
7. 7 | 10
7 • 8
The EM question Availability Customer pack purchase Scope (e.g. Linux) Different approach to using standard WLS ODA Harder to make self-contained for an appliance
NB: we made our choice before EM 12c R4
8. 8 | 10
8 • 8
Conclusions
We like Chef… a lot
It probably doesn’t matter too much which tool you use, as long as you use something!
9. 9 | 10
9 • 8
How did we get here?! Choice of Chef in O-box
http://o-box.com