Push-button Composition of Oracle Application and Database Environments: Avi Miller, Oracle

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Push-button Deployment of Oracle
Applications and Database with
OpenStack Murano
Avi Miller
Product Management Director
Oracle Linux
OpenStack Australia Government Day
14 November 2016

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

Deploying Oracle Products in
OpenStack using Murano
What you will need…
4

Deploying Oracle Products in OpenStack using Murano
• Oracle OpenStack for Oracle Linux version 3.0+
– Based on OpenStack Mitaka
– Oracle VM Server 3.4.2
– NOTE: KVM is not a certified platform for any Oracle product
• Cinder volumes for database storage
– Possible to use ephemeral, only suggested for dev / test environments
– ASM for the database storage management
– Do not use the LVM driver for production
What you will need
5

Why Murano for the Oracle Database
6

• Release scheduling
– The Oracle Database is on a very different release schedule compared to OpenStack
• Using Murano allows us to update / release new versions or patches any time
– Decoupling the products allowing us to line up updates on the application’s schedule and features
• Allows us to expose more of the Oracle Database’s advanced and powerful
features
• We would be able to make use of the new ReST API’s etc. that is being added to Oracle Database to
make the user experience deploying and managing the Oracle database even easier and more
integrated
• Provides a platform to build on allowing us to bring all of the Oracle
Products to OpenStack
7
Why Murano for the Oracle Database

Murano Architecture
8
Source: docs.openstack.org

Layers of Abstraction
9
Heat
Murano
Nova Neutron Other
Application Packages: data & logic
Orchestration Templates: data only

Heat Orchestration Layer
10
OS::Cinder::Volume
OS::Nova::Server
OS::Neutron::Port
OS::Neutron::Network
my_vm:
type: OS::Nova::Server
properties:
block_device_mapping_v2:
device_type: disk
boot_index: 0
volume_size: {get_param: bootvol_size}
image_id: {get_resource: boot_image}
delete_on_termination: false
flavor: {get_param: flavor}
key_name: {get_param: keypair}
networks:
- port: {get_resource: my_vm_port}
security_groups:
- {get_resource: my_secgroup}
software_config_transport: String
user_data: {get_param: cloudinit_data}
user_data_format: raw

Trove’s Approach
11
OS::Cinder::Volume
OS::Nova::Server
OS::Neutron::Port
OS::Neutron::Port
OS::Trove::Instance

Murano’s Approach
12
OS::Cinder::Volume
OS::Nova::Server
OS::Neutron::Port
OS::Neutron::Port
OS::Cinder::Volume
OS::Nova::Server
Database server
composed of vanilla
compute resources.

Murano’s Approach
Consumers & Providers at the Application Package Layer
13
ExtendsApplication
Database
LinuxApplication
SqlDatabaseExtends
Package Package Type
Consumes

Murano Agent
14
Source: docs.openstack.org

Murano vs Trove
Trove
• Trove well suited for the “just give
me a database” use case.
• Changes:
– can entail API change, requiring broad
consensus.
– released on a fixed schedule.
• Design mitigates toward “lowest
common denominator”.
• Strict abstraction
Murano
• Potential to excel for complex
Database configurations.
• Changes to Database package:
– can be done in an appropriate scope to
minimize risk to other packages.
– can be released at any time.
• Framework facilitates exposure of
unique Database features.
• Loose abstraction (applications can
affect DB configuration)
15

Oracle Database Murano Application Catalog Entry - Architecture
16

• Building on top of proven Oracle Template technology
– Using the standard Oracle Database Template (available for both 11gR2 and 12cR1)
• The latest template has some minor changes to accommodate deployment in OpenStack better
– e.g.: The Oracle UID has been changed to 54321 to prevent clashing with cloud-init which requires UID 1000
• Template consists of two disk image files
– Operating System - OL7U2 or OL6U8
– Application Disk – Oracle Database 11gR2 or 12cR1
Oracle Database Murano Application Catalog Entry - Architecture
17

• Database installation and configuration
– Automated using ‘buildcluster.sh’
• Battle tested deployment of Oracle Databases over quite a few years
• Able to handle many different environments
• Template supported deployments
– Single Instance
– Single Instance Data Guard
– Multi-node Real Application Clusters (RAC)
– Multi-node Real Application Clusters (RAC) with Data Guard
Oracle Database Murano Application Catalog Entry – Under the Hood
18

• Storage
– Strongly suggest using Cinder Volumes
• For dev / test ephemeral is OK as long as it is backed by shared storage like CEPH etc.
– ASM used to present / manage the storage for the database
• Configurable redundancy level
– NOTE: Be very careful when selecting external redundancy
Oracle Database Murano Application Catalog Entry – Under the Hood
19

• What you will see today is still fairly early days for the Oracle Database
Application Catalog Entry
– We will release a full Tech Preview very soon
• NOTE: This is only for the MACE, the Oracle Database Template is fully production ready and
supported by Oracle
• Work with the Murano community on enhancements to Murano to better
support complex Enterprise Applications
• We really would like get feedback from the OpenStack community,
customers and users
– Any and all feedback is welcome to make this useful for the broader community
Oracle Database Murano Application Catalog Entry – What’s next?
20

• Enable more integration using the APIs
– For example, today there is no Ceilometer integration with the Oracle Database
• The Oracle Database is a black box to Ceilometer
• Multi-attach volume support in Nova
– Required for Oracle Real Application Clusters (RAC)
Limitations with the Oracle Database in OpenStack today
21

• Memory overcommit is not supported
– Can lead to performance issues
– Not supported by Oracle VM Server
• Ephemeral storage
– Use shared (Ceph) backend to enable live migration of instances
• Oracle Database specific
– NOTE: Oracle Real Application Clusters (RAC) not yet supported
• Require multi-attached volumes – not yet available in Nova
• CPU overcommit with RAC is unsupported – can lead to node evictions
22
Limitations with the Oracle Database in OpenStack today

OK, so we can spin up a Oracle Database…
Awesome, but where are we going with all this?
23

• The Oracle Database is just the first step
• Started working with the other product groups in Oracle to add them to
the App Catalog as well
• Intending to follow the same path we did for the Oracle Database
– In other words, start with the current Oracle product template and build on that
• Work with the community on a Reference Architecture with the Oracle
Database
Next on deck – Applications
24

Stay connected
@ORCL_Linux
Facebook.com/OracleLinux
Blogs.oracle.com/linux
Oracle Linux Experts Group
YouTube.com/OracleLinuxChannel
Or visit us at: www.oracle.com/linux
25
@ORCL_Virtualize
Facebook.com/OracleVirtualization
Blogs.oracle.com/virtualization
Oracle VM Group
YouTube.com/OracleVirtualization
Or visit us at: www.oracle.com/virtualization

Push-button Composition of Oracle Application and Database Environments: Avi Miller, Oracle

Recommended

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to Push-button Composition of Oracle Application and Database Environments: Avi Miller, Oracle (20)

More from OpenStack (19)

Recently uploaded (20)

Push-button Composition of Oracle Application and Database Environments: Avi Miller, Oracle