Infrastructure Consolidation with OCI

Transcription

1 Infrastructure Consolidation with OCI

2 Who we are Experts At Your Service Over 60 specialists in IT infrastructure Certified, experienced, passionate Based In Switzerland 100% self-financed Swiss company Over CHF 10.5 mio. Turnover Leading In Infrastructure Services More than 170 customers in CH, D & F Over 50 SLAs dbi FlexService contracted Infrastructure Consoliation with OCI Page 2

3 About me Thomas Rein Senior Consultant Oracle VM 3.0 Certified Specialist Infrastructure Consoliation with OCI Page 3

4 Agenda 1.Current Situation 2.OCI Terminology 3.Planning and Implementing in OCI 4.Conclusion dbi services Page 4

5 Current situation Overview Migration & consolidation, why? Goals & Timelines Infrastructure Consoliation with OCI Page 5

6 Current Situation Overview System architecture customer has round about 12 content management systems based on Censhare each System contains one or more JETTY application server on Cent OS all CM Systems use one Adobe InDesign Server on Windows 2012 R2 some systems have one ore more satellite servers which provides Web content, also based Censhare each system has Oracle SE database for storing the metadata databases size per system <= 20 GB content size ranges from 200GB up to 8TB systems are hosted on VMs by a provider Page 6

7 Current Situation Migration & consolidation, why? Oracle Database Licensing issues with VMs on ESX Handling and maintenance more than 12 databases Oracle runs out of support VMs in general current provisioning process complexity to high handling of more than 24 VMs (application servers and satellites) changes in infrastructure not really flexible hosting company s pricing is too expensive Page 7

8 Current Situation Goals & Timelines Oracle Database at least on Oracle maybe Oracle 18c scalability of DB storage and database systems Oracle upgrades should be easy with near zero downtimes never ever have licensing issues PDBs instead of single instances Application servers & Satellites easy provisioning for new customers OS upgrades with near zero downtime scalability of storage and VMs Timeline POC 06/18, Decision 9/18 Project 10/18 12/18 Page 8

9 OCI Terminology Overview Administrative Components Physical components Network Resources Instance Resources Storage Resources Infrastructure Consoliation with OCI Page 9

10 OCI Terminology Overview OCI is not OCI is not the Oracle Call Interface (for those C and Embedded SQL Programmers) OCI does not provide any high level services as SaaS or DaaS OCI means Oracle Cloud Infrastructure provides datacenter services > VMs (Oracle Linux, Windows or tailored OS) > Database Machines (VM/ODA/EXADATA with Oracle RBMS ) > Load balancers, Virtual Networks, > Availability Domains (each location has at least 2 physical DCs) It means also: building your own virtual datacenter > Network architecture, Firewalls, SSH Tunnels Page 10

11 OCI Terminology Administrative Components Tenant A name assigned a company or a company s organization Users provide their tenant when signing in to the OCI console A company can have more than one tenant Acts as billing structure Compartment Organize and control access to cloud resources A tenancy always has a root compartment and can contain additional compartments Resources (VMs, Networks etc.) are located in compartments Are granted to users and groups via policies Cannot be deleted (only rename possible) Page 11

12 OCI Terminology Administrative Components Users Connecting through the console or cli to manage resources (create/start/stop/terminate) Created through Oracle Identity Cloud Service OCI uses federation, you do not have local OCI Users Groups Created in IAM and OCI correlated through mappings between IAM and OCI Users are mapped to groups in IAM Policies Control access to compartments and resources Attached to groups not to users Allows access but cannot deny access Page 12

13 OCI Terminology Physical Components Regions Are geographic locations Contains one or more availability domains Currently 4 regions available (2 in US, 1 London and 1 Frankfurt) Some resources are bound to a region i.e. Networks Availability Domains One ore more datacenters form an Availability Domain Some resources are bound to an Availability Domain i.e. VMs or Database Machines Each AD itself is fault tolerant ADs in a Region are connected by low latency high bandwidth networks ADs can be used for high availability and disaster recovery Page 13

14 OCI Terminology Network Resources Virtual Cloud Network (VCN) A single, contiguous IPv4 CIDR block ( /8, /12, and /16) At least one VCN is necessary, more VCNs possible Subnets and Routing Lists A VCN is split into subnets (i.e /24, /24, ) Subnets are bound to a AD Internet Gateways Router between your VCN and the Internet Security Lists Firewall rules for the VCN Page 14

15 OCI Terminology Instance Resources Compute Instances Either Bare Metal or VM (Windows, Linux or customized Image) Bare Metal storage either NVMe or standard block storage Up to 8 GPUs on Bare Metal possible VMs up to 24 OCPU possible, storage either on standard block storage or NVMe Instance is bound to availability domain DB Systems Exadata, Bare Metal or virtual machines possible License included or bring your on license (BYOL) Database Version , , , 18.1 or 18.2 (currently no 18.3) Editions SE, EE (no Options), EE High Performance (all except ADG and RAC), EE extreme Performance Autonomous Databases DSS and OLTP also available Instance is bound to availability domain Page 15

16 OCI Terminology Storage Resources Block Storage Exadata, Bare Metal or virtual machines possible Object Storage Bound to a region, can be used in all availability domains Is used for RMAN backups Database duplication from backup between ADs File Storage NFS Filesystems Page 16

17 Planning and Implementing in OCI Basic Infrastructure Network connectivity Backend infrastructure Middleware infrastructure Frontend infrastructure Infrastructure Consoliation with OCI Page 17

18 Planning and Implementing in OCI Basic Infrastructure Location EU Frankfurt 1 2 Availability Domains AD3 used in the future Subnet /24 Subnet /24 Network VCN /16 for the region 3 Subnets per AD Subnet /24 Subnet /24 > Loadbalancer and Bastion Host > Application servers and Satellites > Backend for database Networks in AD2 planned for HA and Data Guard AD3 will be used for Observer (DG) Subnet /24 EU-Frankurt-1-AD-1 REGION: EU-Frankfurt-1 Subnet /24 EU-Frankurt-1-AD-2 AD-3 VCN: /16 Page 18

19 Planning and Implementing in OCI Network connectivity Internet EU Frankfurt 1 2 Availability Domains AD3 used in the future Internet Gateway Frontendd Subnet /24 Frontend Subnet /24 VPN to customer Dynamic Routing GW VPN between On Premise and VCN Security Lists 3 security lists for each network type one list Routing 1 Routing table VPN Dynamic Routing Gateway EU-Frankurt-1-AD-1 REGION: EU-Frankfurt-1 Frontend List Middleware Subnet /24 Middleware List Backend Subnet /24 Backend List Middleware Subnet /24 Backend Subnet /24 EU-Frankurt-1-AD-2 Frontend List Middleware List Backend List AD-3 Route Table VCN: /16 Page 19

20 Planning and Implementing in OCI Backend Infrastructure Database servers Oracle EE High Performance Package Configured as CDB 2 OCPU (VM.Standard2.2) 1024 GB Storage 30 GB Memory 2 nd server planned for Data Guard Backup Object Storage in VCN CDB with automatic Cloud Backup (weekly level 0, daily level 1) VPN Dynamic Routing Gateway EU-Frankurt-1-AD-1 REGION: EU-Frankfurt-1 Subnet /24 Subnet /24 Subnet /24 Subnet /24 Internet Gateway Subnet /24 Subnet /24 MIS01LDB MIS02LDB Object Storage EU-Frankurt-1-AD-2 AD-3 VCN: /16 Page 20

21 Planning and Implementing in OCI Middleware Infrastructure Application servers Oracle Linux OCPU (VM.Standard2.2) 30 GB Memory 2 8 TB additional Block Volume attached Application server is connected to database Satellite servers Configured like application servers Satellite is connected to application server VPN Dynamic Routing Gateway EU-Frankurt-1-AD-1 REGION: EU-Frankfurt-1 Subnet /24 Subnet /24 Subnet /24 MIS01LAPP Subnet /24 MIS01LSAT Internet Gateway Subnet /24 Subnet /24 MIS01LDB MIS02LDB Object Storage EU-Frankurt-1-AD-2 AD-3 VCN: /16 Page 21

22 Planning and Implementing in OCI Frontend Infrastructure Load balancer (planned) Mbps depending on customer s needs HA solution for the application servers and satellites Bastion server Jump server from outside SSH with public keys VPN Dynamic Routing Gateway Subnet /24 Subnet /24 MIS01LLB Subnet /24 MIS01LAPP MIS01LBAS MIS01LSAT Internet Gateway Subnet /24 MIS02LSAT MIS02LLB MIS02LAPP Subnet /24 Subnet /24 EU-Frankurt-1-AD-1 REGION: EU-Frankfurt-1 MIS01LDB MIS02LDB Object Storage EU-Frankurt-1-AD-2 AD-3 VCN: /16 Page 22

23 Planning and Implementing in OCI Database architecture Consolidation CDBs for production, staging and development each customer gets at least two PDBs (production and staging) TNSNAMES.ORA entry for each PDB Service Disaster Protection Data Guard Primary databases in AD1 Standby databases in AD2 DB Upgrades possibilities Upgrade standby and switchover Unplug / plug New Database system EFG01LDB MISMLDB01_fra1km (Prod) MISMSDB01_fra1km (Staging) EU-Frankurt-1-AD-1 DOR01LDB XXX01LDB EFG01SDB Oracle Data Guard DOR01SDB XXX01SDB MISMLDB01_fra2km (Prod) MISMSDB01_fra2km (Staging) EU-Frankurt-1-AD-2 Observer EU-Frankurt-1-AD-3 Page 23

24 Planning and Implementing in OCI Application server architecture Template VM Create VM which is used as a template Create and attach additional block storage (mount /opt/corpus) size 2TB Later resizing possible Install additional packages (i.e. java) Install Censhare to /opt/corpus (completely self contained) Attach content storage i.e. /opt/work Create custom image from VM Creating customer VMs Create VM from custom image Clone and attach Application Volume Create and attach Content Storage Volume Boot Volume 50G Boot Clone Template Server Create custom image Application Volume 200GB /opt/corpus App Clone Disk Content Storage 2TB Clone Volume Content Storage Customer Server Page 24

25 Conclusion Database systems Middleware systems Additional Information Infrastructure Consoliation with OCI Page 25

26 Conclusion Database systems Advantages Easy provisioning of databases systems Scaleup of storage possible 5 possible database releases , , , 18.1 and Editions SE, EE (no Options), EE High Performance (all except ADG and RAC), Extreme Performance Grid and database patching is simple via GUI or with dbcli Disadvantages Release 18.3 missing Creating additional PDBs through GUI not supported VM scaleup (memory or cores) not possible (only on Exadata Shapes) Page 26

27 Conclusion Middleware systems Advantages Easy and fast provisioning of new customer VMs Scaleup of Block Storage possible Easy setup of custom images HA Solutions easy through load balancers Disadvantages None Plan your basic infrastructure carefully (VCNs, Subnets, Security and Routing Lists then OCI is easy to handle Page 27

28 Basel Delémont Zürich Any questions? Please do ask! Nyon We would love to boost your IT-Infrastructure How about you? Infrastructure Consoliation with OCI Page 28

29 Let s meet at booth 242