Getting started with Ansible and Oracle

Transcription

1 Getting started with Ansible and Oracle DOAG, Germany 22 nd Nov 2017

2 About Me Ron Ekins Oracle Solutions Architect for Pure Storage ron@purestorage.com Twitter: Enterprise Architect and Oracle technologist for +25 years. Oracle ACE, UK OUG Database SIG co-chair 2

3 500+ Technical Experts Helping Peers Globally 3 Membership Tiers Oracle ACE Director Oracle ACE Oracle ACE Associate bit.ly/oracleaceprogram Connect: oracle-ace_ww@oracle.com 3 Nominate yourself or someone you know: acenomination.oracle.com

4 Who are Pure Storage? Source: Gartner (June 2015) A MAGIC QUADRANT LEADER Source: Gartner Magic Quadrant for Solid State Arrays This graphic was published by Gartner, Inc. as a 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 Pure Storage. 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 or other designation. 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 and warranties of merchantability or fitness for a particular purpose. 4

5 Agenda Getting started with DevOps, Ansible and Oracle What is DevOps What is Ansible? Why use Ansible Getting started Ansible and Oracle demo 5

6 For many years we have heard, But finally, Winter is Here and so is DevOps that DevOps is Coming 6

7 So what is DevOps Borrowing from Wikipedia, the term DevOps is defined as DevOps (a clipped compound of "development" and "operations") is a culture, movement or practice that emphasizes the collaboration and communication of both software developers and other informationtechnology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment where building, testing, and releasing software, can happen rapidly, frequently, and more reliably. 7

8 DevOps Principles Organisation and cultural change enabled by technology Dev Ops Paid to add new features Paid to add keep system stable, secure, fast and available DevOps New Goal: Paid to add features and keep system stable, secure, fast and available 8

9 DevOps drives Business Value Faster Time-to-Market Increase frequency of releases Faster time-to-market for individual features Reduce the time and risk it takes to perform a release Enable parallel development and testing through dedicated environments 9 Cost Automate what was previously done manually Prevent costly human error Reduce downtime, save money Realise benefits of developments quicker. Quality Perform more test cycles using full size representative test data. Identify issues earlier in development lifecycle. Increase quality of releases, smaller changes

10 Why DevOps To Accelerate Development, Improve Quality and reduce Time-to-Market How: By performing more, and quicker test cycles against Production like systems. Performing parallel development and testing Delivering smaller frequent releases (less change) Deploying with repeatable, reliable processes Monitoring and validate Operational quality Removing communication barriers with traditional silo ed teams DevOps needs: More data copies, quicker refreshes, full size copies DevOps needs: More, faster, repeatable test cycles 10

11 DevOps Terms Continuous Integration The automated integration and testing of code as soon at it s available Continuous Delivery The delivery of code into a pre-production / release area as soon as available. Continuous Deployment The deployment of code into Production as soon as it s ready. Continuous Operations Monitoring and feedback from Production into development. Infrastructure as Code The use of code to describe a desired state of configuration 11

12 Infrastructure As Code (IaC) 12

13 Infrastructure as Code (IaC) Modern Approach to managing Infrastructure IaC is a way of describing your infrastructure as code letting you deliver software more reliably. Configurations are consistently tested, shared and promoted across all environments, from dev laptops through to test and production. Why Cost Reduction - Remove manual effort through automation Speed - Infrastructure automation enables speed through faster execution Risk - Automation removes risk of human error, miss-configuration and security violations. 13

14 Focus on a reliable deployment 14

15 Infrastructure Methods - Push or Pull Ansible and Salt both use a Push method of communication that does not not require any agents to be installed on remote servers. Puppet and Chef have taken a Pull-based approach, where agents installed on the remote servers periodically check in with a central server and pull down configuration information. 15

16 Traditional vs DevOPS approach 16

17 What is 17

18 Why is Ansible, Ansible The term Ansible is a Science Fiction reference for a ficitonal communications device that can transfer information faster than the speed of light. The author Ursula LeGuin invented the concept in her 1966 book Rocannon s World, subsequently other SciFi authors have borrowed the term. 18 Michael DeHaan the creator of Ansible took inspiration for the name Ansible from the book Enders Game by Orson Scott Card. In the book Ansible is used to control a large number of remote ships at once, over large distances. From now on whenever I mention Ansible it will be to control remote infrastructure not ships.

19 What is Ansible? It s a simple automation language that can perfectly describe an IT application infrastructure in Ansible Playbooks. It s an automation engine that runs Ansible Playbooks UI Frameworks Ansible Tower - commercial solution by RedHat Ansible AWX - Open Source Ansible Tower project Ansible-Semaphore Open Source Tower alternative 19

20 Ansible Tower Available with RedHat Support Options 20

21 Ansible Architecture 21

22 Why use 22

23 What can you do with it? Configuration Management Application deployment Provisioning Continuous Delivery (CD) Orchestration Security and Compliance 23

24 Let s get started 24

25 Ansible Basics Playbooks contain plays Plays contain tasks Tasks call modules Tasks run sequentially Handers are triggered by tasks, and are run once, at the end of plays. 25

26 Ansible Playbooks Use plain text YAML files that describe the desired state of something Human and machine readable Can be used to build entire application environments Break out Tasks into separate files to assist with readability and encourage re-use. 26

27 Ansible Variables There are many different ways to source variables: Playbooks Files Inventories (group vars, host vars) Command Line Discovered variable (facts) YAML originally said to mean Yet Another Markup Language However, now short for YAML Ain't Markup Language 27

28 Ansible Inventories Static lines of servers Groups, Ranges Other custom things e.g. Configuration Database Dynamic lists of servers e.g. AWS, Azure, Oracle Cloud Target group Source group Parent group Server variables Group variables 28

29 Ansible shell module The shell module is almost exactly the same as the command module but run through the command through a shell /bin/sh on the remote server e.g. Variable substitution OS command 29

30 Ansible mount module - mounted Mount Linux filesystems Mount Point Name Mount State Source (device name) File System Type 30

31 Ansible Mount Module unmounted Unmount Linux filsystem Mount Point Name Mount State 31

32 The Ansible URI module Use the URI module to interact with HTTP / HTTPS web services Consume RESTful API s to interact with infrastructure, Services and Applications. 32 Variable substitutions

33 The Ansible copy module The copy module copies local or remote file to a location on the remote server. Useful for static scripts and configuration files. e.g. Destination File Name Source File Name File Permissions 33

34 The Ansible template module The template module is similar to the copy module but support Jinja2 template processing. Useful for the dynamic creation of OS and SQL scripts e.g. - Destination File Name Source Jinja2 Template File Name File Permissions 34

35 Jinja2 Template file rename.sql.j2 Variables subsituted at runtime Variable substitutions 35

36 Template file becomes rename.sql Variables substituted 36

37 Using Ansible How to RUN Ad-Hoc: ansible <inventory> -m Runs a command or calls a module directly from the command line, no Playbook required. Playbooks: ansible-playbook <inventory> <options> Via Ansible frameworks: ansible-semaphore (Open Source) RedHat Ansible Tower (commercial) RedHat Ansible AWX (Open Source) 37

38 Ansible-semaphore UI Self Service One Click Database Refresh 38

39 2.4 39

40 Pure Storage Ansible module Ansible 2.4 Storage Module 40

41 Pure FA Ansible Create Volume Name Volume Size Protection Group Name Protection Group Members (Volumes) Protection Group Snapshot Name Protection Group Snapshot Suffix 41

42 Pure FA Ansible Delete Protection Group Snapshot Name Protection Group Snapshot Suffix Protection Group Name Volume Name 42

43 It s all about that database 43

44 Ansible Oracle database Refresh Demo Perform Production database storage snapshot Shutdown Target database Unmount Target database volume(s) Refresh Target databases volume(s) Mount Target database volume(s) Restart Target Database(s) Rename Target Database(s) Rename Target Database directories Rename Target Database data files 44 Demo delivered using TMUX (Terminal Multiplexer)

45 Don t waste your time looking back, you re not going that way -Ragnar Lothbrok 45

46