Upgrade to Pro — share decks privately, control downloads, hide ads and more …

OBIEE DevOps with Containers: How and Why

OBIEE DevOps with Containers: How and Why

Provisioning developers’ sandboxes or regression testings and continuous integration in OBIEE, some common DevOps tasks which often take time and resources. Containers technology provides a quick and flexible answer to these growing needs and as opposed to virtual machines require less resources (storage and memory). You will learn about containers (Docker) and how OBIEE can fit into it and be managed easily to fulfil these common tasks. Having nightmares thinking at your next upgrade or patch? OBIEE in a container can be a solution for having sweet dreams every night. Works both on prem and cloud (OCCS or others).

Gianni Ceresa

June 15, 2017
Tweet

More Decks by Gianni Ceresa

Other Decks in Technology

Transcript

  1. Server Host OS Hypervisor Guest OS bins/libs App B Guest

    OS bins/libs App A Guest OS bins/libs App A’ VM Server Host OS bins/libs App A App A’ bins/libs App B App B’ App B’ App B’ Docker Container Containers are isolated, but share OS and, where appropriate, bins/libraries
  2. • • • • Single “RUN”, download binaries “on the

    fly” YUM install required packages Oraclelinux “slim” image My Oraclelinux “BI” image My OBIEE image
  3. • • • • • • • • • •

    • • • • • •
  4. Master Dev/yy Dev/xx Compare BVT results with the latest one

    of Master Deploy this version to TEST environment This branch is developed in an OBIEE sandbox running on Docker to make provisioning simple and fast
  5. The CI steps use Docker to execute OBIEE. First thing

    is to create a new OBIEE environment, that’s why the container start by configuring OBIEE (RCU, create domain, start components)
  6. When OBIEE is running (inside the Docker container) the RPD

    and catalog from GIT are deployed. Finally BVT is executed.
  7. At the end time to cleanup: RCU schemas are dropped

    from the database, results of tests (artifacts) are saved in GitLab before to drop the container. There is nothing left from this OBIEE instance, like if it never existed…
  8. All the results of automated tests have been stored as

    “artifacts” and can be downloaded for detailed analysis
  9. Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

    | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 39
  10. Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

    | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. 40 Twitter private message: Could we start a thread on email please so I can find out more? I'm at [email protected] thanks. We're currently working on officially supporting OBI on docker (early May 2017) • Name of the Oracle employee known by the Presenter • Remember the Safe Harbor Statement • If asked about this I will refuse to confirm or infirm this information :D