The document discusses the automation of Oracle database deployments on Amazon Web Services using Boto and Fabric. It covers key concepts such as automated deployment, infrastructure-as-a-service, and devops, while providing a workflow for provisioning and deploying database servers. Additionally, it outlines criteria for determining the suitability of cloud automation for various business needs.

1. AUTOMATING ORACLE DATABASE
SEMOP
DEPLOYMENT WITH AMAZON WEB Feb. 1 2 th , 2013
SERVICES, FABRIC, AND BOTO

2. INTRODUCTION
 Michael J Bommarito II
 CEO, Bommarito Consulting, LLC
 Email: michael@bommaritollc.com
 Web: http://bommaritollc.com/
 LinkedIn: http://linkedin.com/in/bommarito
Expert infrastructure, development, and
data services.
 CIO, Solid Logic Technol ogy, Inc.
 Web: http://solidl ogi c.com/
Large, labor -intensive sof tware and infrastructure
projects.
© Bommarito Consulting

3. GOALS
 DEF INE - Under stand the myriad of acronyms and cr yptic phrases:
 IaaS, DevOps, automated deployment…
 DESIGN - Under stand how the requirements fit together:
 IaaS provider and/or private cloud
 Boto
 Fabric
 Oracle
 EXECUTE – Run and modify a basic deployment example.
 EXTRAPOLATE – Discuss possibilities for real business needs.
© Bommarito Consulting

4. DEFINE
The Cloud is dead. Long live the Cloud!
Note: I try to use “cloud” as little as possible in this discussion.
What do we need to cover (in increasing difficulty)?
 Automated deployment
 Virtualization
 Automated provisioning
 Configuration management
 Infrastructure-as-a-Service (IaaS)
 Programmable infrastructure (“infrastructure as code”)
 DevOps
© Bommarito Consulting

5. DEFINE
 Automated deployment: Process-driven build of software, OS and up.
 Examples: Oracle response files, RHEL kickstart, Puppet, that maze of
bash or perl scripts.
 Virtualization: Abstract raw compute and storage for more flexible, efficient
utilizations.
 Hardware: Xen/KVM, ESx, Hyper-V, Oracle VM (Xen), VirtualBox
 “Storage:” SAN, DFS, S3, OpenStack Swift, Storage-as-a-Service
 Automated provisioning: Process-driven build of compute, storage, and
network resources.
 Examples: Norton Ghost, vSphere/VMware Automation, xen-api, AWS APIs
© Bommarito Consulting

6. DEFINE
 Configuration management: Process-driven management of software
(apt, yum) and configuration (/ etc/, Windows Registry).
 Examples: Puppet, Chef, Fabric(~), CFEngine, and, again, that maze of
bash or perl scripts.
 Unlike automated deployment, this is stuff you live with and change every
day.
 Some tools, like Puppet, can gracefully span automated deployment and
configuration management.
 Infrastructure-as-a-Service (IaaS): Compute, storage, and network
virtualization, but with someone else running the data center and
virtualization operations.
 Many providers offer some form of IaaS/cloud/virtualization, but very few
add real cost-adjusted value.
© Bommarito Consulting

7. DEFINE
 Programmable infrastructure (“infrastructure as code ”): When your IaaS has
a featureful API and unbounded capacity relative to your needs.
 Never ask a hardware rep about lead times.
 Never ask a technician when a box will be cabled.
 Never ask a sysadmin when your server will be ready.
 Never pay for unutilized, depreciating assets.
 DevOps: Collaborative, process-driven approach to managing infrastructure
and software.
 Think Toyota Production System + “cloud” for infrastructure and ALM.
 Reduce cost of failure and probability of failure.
 Make ITIL and CMMI easy (…well, easier)!
 Honest truth: More of a culture than a methodology.
© Bommarito Consulting

8. DESIGN
Phew. Enough theory and philosophy. Let’s take inspiration from the
previous slides and actually build something to solve a real problem:
“I want an Oracle database server. I want it now. I want it to look the same
every time, but be easily configurable if I do want it to change. I only want to
pay for it when I use it. Did I mention now?”
Components:
 IaaS: Amazon Web Services
 Automated Provisioning: boto/Fabric
 Automated Deployment: Fabric
© Bommarito Consulting

9. DESIGN
IaaS: Amazon Web Services
 Fully programmable infrastructure.
 Plug in credit card and email, download credentials.
Automated Provisioning: boto/Fabric
 Provision network, storage, and compute resources for server.
 Python + configuration
Automated Deployment: Fabric
 Update host and ensure Oracle prereqs met.
 Install software.
 Configure listener and database.
 Python + configuration
© Bommarito Consulting

10. DESIGN
What does basic configuration look like?
 Configuration
 fabricrc: Basic fabric configuration for users, SSH config, behavior
 hosts.txt: Hosts managed by Fabric infrastructure.
 python-requirements.txt: Required packages for deployment server.
 yum-requirements.txt: Required packages for target servers.
 Templates
 database.rsp: Oracle database software response file
 dbca.rsp: Oracle database response file
 netca.rsp: Listener response file
 public-yum-el5.repo: Yum repo config, e.g., RHEL5U9
© Bommarito Consulting

11. DESIGN
What does Boto look like?
© Bommarito Consulting

12. DESIGN
What does Fabric look like?
© Bommarito Consulting

13. DESIGN
Workflow Overview
1. Provision (boto)
1. Create security group.
2. Create storage mapping.
3. Create instance.
2. Deploy (Fabric)
1. Resize root volume (not required by newer OS images).
2. Disable software firewall (no routing/ QoS, use AWS hardware).
3. Upgrade base OS packages and reboot.
4. Enroll system in public OEL yum and install oracle -validated.
5. Setup basic Oracle DB and OFA requirements.
6. Install database software and run post-install scripts.
7. Create a listener.
8. Create a database.
© Bommarito Consulting

14. EXECUTE
© Bommarito Consulting

15. EXECUTE
And an aside on cloud performance: don’t let anyone tell you that I/O
isn’t available on public cloud.
 hi1.4xlarge instances: ORION benchmarks at 1.8GB/s large
reads, 40k IOPS, stable <1ms latency.
 Provisioned IOPS: dynamically provisioned storage that can be
configured to provide guaranteed IOPS.
 RAID/LVM: just as viable in the cloud as with DAS/NAS.
 Application design: Was I/O the bottleneck because it had to be or
because your application was designed when memory was expensive ?
© Bommarito Consulting

16. EXTRAPOLATE
Let’s go back to our motivating problem:
“I want a ________ server. I want it now. I want it to look the same every
time, but be easily configurable if I do want it to change. I only want to pay for
it when I use it. Did I mention now?”
How many times have you heard something like this need?
 Development for testing, QA, skunkworks.
 Sysadmins for testing, QA, skunkworks.
 Sysadmins for HA, DR.
 Management for compliance, cost, and urgency.
© Bommarito Consulting

17. EXTRAPOLATE
Signs you might be a good candidate:
 Large number of similar assets.
 Large number of repetitive tasks (or large sysadmin team).
 Audit requirements around deployment and ongoing configuration changes.
 Unpredictable, variable, or low utilization, e.g., uncertain usage, bursty
usage, or overcapacitization.
 Bottlenecking in the dev->sysadmin->QA workflow.
Signs you might not be a good candidate:
 Tasks are not repeated enough relative to complexity/cost to amortize setup
costs.
 Total number of assets is low.
 Predictable, high utilization.
 Low-to-no compliance environment.
© Bommarito Consulting

18. REFERENCES
 Bommarito Consulting Blog
 Oracle ORION I/O benchmark results for AWS EC2 hi1.4xlarge
instance type
 Software:
 Fabric
 Boto
 Puppet
 Chef
 Businesses
 Amazon Web Services
 Rackspace
 Microsoft Azure
 Fabric and Boto for Managing EC2. Graham Poulter.
© Bommarito Consulting

19. THANKS!
You can get these slides on my blog – http://bommaritollc.com/blog/.
 Michael J Bommarito II
 CEO, Bommarito Consulting, LLC
 Email: michael@bommaritollc.com
 Web: http://bommaritollc.com/
© Bommarito Consulting