Oracle Mul*tenant. The Bea'ng Heart of Database as a Service. Debaditya Cha9erjee Senior Principal Product Manager Oracle Database, Product Management

Transcription

1

2 Oracle Mul*tenant The Bea'ng Heart of Database as a Service Debaditya Cha9erjee Senior Principal Product Manager Oracle Database, Product Management

3 Safe Harbor Statement The following is intended to outline our general product direc*on. It is intended for informa*on purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or func*onality, and should not be relied upon in making purchasing decisions. The development, release, and *ming of any features or func*onality described for Oracle s products remains at the sole discre*on of Oracle.

4 Mul*tenant Architecture What is Mul$tenant?

5 Oracle Database Architecture Requires memory, processes and database files System Resources GL OE AP 5

6 New Mul*tenant Architecture Memory and processes required at container level only System Resources GL OE AP GL OE AP 6

7 Oracle Database Architecture More efficient u'liza'on of system resources System Resources GL OE AP 7

8 Mul*tenant Architecture Components of a Mul'tenant Container Database (CDB) PDBs Root CDB Pluggable Databases Mul*tenant Container Database 8

9 Mul*tenant Architecture DB Link GL OE AP Mul*tenant architecture can currently support up to 252 PDBs PDB / non- CDB compa*bility guarantee: You cannot tell, from the viewpoint of a connected client, if you re using a PDB or a non- CDB

10 A Pluggable Database Is a Portable Database Unplugging a PDB and plugging it in PO GL OE AP AP Simply unplug from the old CDB and plug it into the new CDB Moving between CDBs is a simple case of moving a PDB s metadata An unplugged PDB carries with it lineage, opatch, encryp*on key info etc. 10

11 Unplug / Plug Orchestra*on Performed Using SQL You already know how to use it! Unplug alter pluggable database OE unplug into '/u01/app/oracle/oradata/ /oe.xml' Plug create pluggable database My_PDB using '/u01/app/oracle/oradata/ /oe.xml'

12 Oracle Data and User Data Before 12.1: Oracle and user data intermingle over 'me New database contains Oracle meta- data only OBJ$ TAB$ SOURCE$ EMP DEPT Meta- Data PDB Root User Data Populate database with user data Oracle and customer meta- data intermingled Portability challenge! Mul*tenant fix: Horizontally- data Only Oracle- supplied meta- data remains in root

13 Mul*tenant Scalability Only small increments in memory as addi'onal PDBs are added 3 MEMORY MEMORY MEMORY 2.5 GL OE AP PO HR GB GL OE OE AP AP PO AR Pluggable Pluggable Database Pluggable Database Database

14 Before We Begin What is Database- as- a- Service?

15 Explaining with Pizzas On- Premise Make Pizza at home. You are responsible for buying all the ingredients including making the dough. Bake it in your own oven IaaS Purchase some of the ingredients. Buy pre- packaged dough and you mix the ingredients yourself and make the pizza yourself. PaaS Pizza delivered at home. Setup the table and soda and eat it. SaaS Dining out. Ea*ng Pizza at a restaurant. ** Ar@cle by Albert Barron, Architect at IBM

16 Database- as- a- Service What type of service model is Database- as- a- Service? Type of PlaGorm- as- a- Service o capability provided to the consumer to deploy onto the cloud infrastructure consumer- created or acquired applica*ons created using programming languages and tools supported by the provider o Exists in all 4 deployments models Essen'al Characteris'cs On- Demand Self Service Broad network access Resource Pooling Rapid Elas*city Measured Service Deployment Models Private Cloud Community Cloud Public Cloud Hybrid Cloud

17 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

18 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

19 Current State of Database Deployments Siloed, Dispersed, Varied and Complex Ever growing database popula*on Poor resource u*liza*on High cost of deployment and opera*on Mul*ple versions and patch levels Compliance challenges 28% have an annual database instance growth of more than 20% Less than 50% have consolidated *IOUG Survey, 2013

20 Tradi*onal Database Provisioning Process Time- consuming and Inefficient Developer Request DB Get access to DB Manager Approval DBA Request HW and Storage Configure Cluster and create DB System Admin Setup OS & Network Storage Admin Allocate Storage

21 Business Drivers Customers facing great pressure to consolidate databases in cloud IT Wants User Wants Simplified deployment on standardized plalorms Less maintenance and bemer support More budget and *me for innova*on Cut Costs Requirements Tenant isolation Easy adoption Manage many as one Retain granular control Self- service Rapid provisioning Simplified management Metered Use Performance op*mized for service levels

22 Database Consolida*on on Clouds Tradi'onal consolida'on methods Virtual Machines Clustered Databases Schema Mul'tenant Consolida'on Database Consolida*on Density Shared Servers Shared Servers & OS Shared Servers, OS, & Database 22

23 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

24 What Mul*tenant Offers Powered by Oracle Mul'tenant, Database as a Service is more a9rac've as it offers Portability through Pluggability and Cloning Complete Manageability for All Layers and All Players Pluggable Database as a Service (PDBaaS) all for one price

25 Unprecedented Agility with Portable Pluggability PDB migrates through SLAs as it becomes more mission cri'cal GOLD RAC, Data Guard SILVER RAC BRONZE Backups 25

26 Mul*tenant for Provisioning Perfect for migra'ng Development & Test environments to cloud GL- 1 GL- 2 AP- 1 PDBs can be cloned from within the same CDB PDBs can be cloned from remote CDBs GL OE AP PDBs can also be remote snapshot cloned within the same storage sub- system 26

27 Cloning a on- premise non- CDB to a PDB in cloud Seed GL OE 1. Convert a non- CDB upgraded to directly as a PDB using a database link 2. The data files for clone the are copied over from the source using the database link over SQL Net 3. Once pluggable database is created you will need to run noncdb_to_pdb.sql 4. No need to generate the XML manifest file. GL OE

28 Convert schema based consolida*on to a PDB in cloud AP GL Schema GL OE AR Customers have implemented schema based consolida*on The subset clone using USER_TABLESPACES clause migrate these schemas into individual pluggable databases 28

29 What Mul*tenant Offers to Your Customers Powered by Oracle Mul*tenant, Database as a Service is more amrac*ve to your customers than compe**ve offerings Portability through Pluggability and Cloning Complete Manageability for All Layers and All Players Pluggable Database as a Service (PDBaaS) all for one price

30 Environment Management Understanding the Different Layers APAC EMEA Americas Project 3 Project 2 Project 1 Oracle PDBaaS Master Tst2 Tst1 Dev3 Dev1 Dev2

31 Environment Management Manageability in all layers for all players APAC EMEA Americas Project 3 Project 2 Project 1 Oracle PDBaaS Master Dev3 Tst2 Dev1

32 Environment Management Manageability in all layers for all players APAC EMEA Americas Project 3 Project 2 Project 1 Oracle PDBaaS Master Dev3 Tst2 Dev1 EMCC Repos EM Cloud Control Enterprise Cloud Departmental Cloud PDB EM Express CDB PDBSS

33 What Mul*tenant Offers to Your Customers Powered by Oracle Mul*tenant, Database as a Service is more amrac*ve to your customers than compe**ve offerings Portability through Pluggability and Cloning Complete Manageability for All Layers and All Players Pluggable Database as a Service (PDBaaS) all for one price

34 Tradi*onal Model Compe'tors offer inferior solu'ons One virtual machine per database Results in virtual machine sprawl Difficult to manage Migrates the sprawl from on- premise to the cloud 34

35 Pluggable Database as a Service All for one price Pay once; provision addi'onal PDBs at insignificant incremental cost Pay once for the Container. Adding a new database has insignificant incremental cost Adding a new database does not move the meter PDBs Root CDB Pluggable Databases Mul*tenant Container Database 35

36 Cost of VM Sprawl Fixed overhead with Mul'tenant; Overhead costs propor'onal to #DBs in legacy model Overhead Costs Mul*tenant Non- CDB # DBs 36

37 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

38 Provider: Efficient Use of Cloud Compute Resources Support more customer environments in given cloud infrastructure footprint GL OE AP Self- contained PDB for each applica'on Applica*ons run unchanged Rapid provisioning (via clones) Portability (via pluggability) Common opera'ons performed at CDB level Manage many as one (upgrade, HA, backup) Granular control when appropriate Efficient use of compute resources, minimizes conten'on Complementary to VMs Shared memory and background processes Highly Consolidate more applica*ons per server Public 38

39 Increase Agility and Reduce Opera*ng Costs For opera*onal purposes, CDB is the database Ability to manage many databases as one Increased opera*onal efficiency with Backup Patching High- Availability Configura*on Agility in changes to SLA Data Migra*on Services (from on- premise data center to Cloud)

40 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

41 Demo Moving to the cloud

42 Program Agenda Current State of Database Deployments Mul*tenant Value Proposi*on Advantage Mul*tenant Demo Summary

43 Summary Mul*tenant delivers compe**ve advantage to the cloud provider through fine- grained consolida*on, providing: Portability through Pluggability and Cloning Complete Manageability for all Layers and all Players Pluggable Database as a Service (PDBaaS) all for one price Offer these services at a lower cost More efficient use of Cloud compute resources Accommodate more customers in given Cloud Infrastructure Opportunity for Cloud Provider to offer value- add services compe**vely Ability to manage many databases as one à Reduce OpEx

44

45