So what we exactly we mean by a complete, integrated and business-driven cloud management solution?There are three key aspects of Oracle Enterprise Manager 12c that help accomplish this: Complete Cloud Lifecycle Solution To start with, Oracle Enterprise Manager 12c contains solutions to manage all phases of the building, managing, and consuming an enterprise cloud. Using Oracle Enterprise manager 12c you can build and manage a rich catalog of cloud services – whether it is Infrastructure-as-a-Service, Database-as-a-Service, or Platform-as-a-Service , all from a single product. Integrated Cloud Stack ManagementSecondly, Oracle Enterprise Manager 12c enables integrated management of the entire cloud stack – all the way from application to disk. Oracle Enterprise Manager 12c therefore eliminates much of the integration pains and costs that customers would have to otherwise incur by trying to create a cloud environment by integrating multiple point solutions. Business-Driven Clouds Finally, Oracle Enterprise Manager 12c enables creation of application-aware and business-driven clouds that has deep insight into applications, business services and transactions. Applications – whether they are packaged or home grown – power your businesses and therefore it is critical that an enterprise Cloud platform is not only able to run these applications but also has deep business insight and visibility. As the leading providers of business applications and the middleware that many of your custom applications are built on top of, we are able to offer you a cloud solution that is optimized for business services.
Today, customers have a choice of cloud models. They can choose among private clouds, public clouds and hybrid clouds.A private cloud is for the exclusive use of a single organization and is typically controlled and managed by in-house ITA public cloud is shared by multiple tenants on a shared basis, and it hosted and managed by someone else (a service provider). It’s a form of outsourcing.There are some basic trade-offs when deciding between private and public clouds.Public clouds are purchased out of operating expense, avoiding capital expenditures. Public clouds are faster and cheaper to get started, providing a “low barrier to entry.” However, private clouds can offer lower costs over the long term. For IT projects, the breakeven period tends to range from 2 to 4 years, averaging about 3. This is the similar to the decision some people make between owning vs. renting.Another trade-off is between public cloud outsourcing everything to a service provider, which is great if you don’t have the datacenter, hardware or the right skillsets, versus how in a private cloud, you are able to maintain control and visibility over customizations, security, regulatory compliance and quality of service.Both public and private clouds involved sharing or pooled resources, but in a private cloud, the sharing is different apps using shared platform or infrastructure all within a single organization. In a public cloud, the sharing may be the same or different apps among different tenants.<CLICK>Hybrid cloud is a fuzzy term with different meanings:Cloudbursting – steady state in private cloud, but when a spike or peak happens, use a public cloud, then return capacity to the pool when it’s no longer neededHybrid across app lifecycle – dev/test in one cloud, production in anotherHybrid can also mean different functions are performed in different clouds, such as for a business process that spans clouds, requiring B2B integration between them
Highlight the value of PaaS and the differential value provided by Oracle in the area of DBaaS and MWaaS leveraging its core competency . It first tries to establish the point as to why PaaS delivers greater enterprise value and then goes on to show EM 12c provides enterprises the most complete cloud management solution.
Consolidation means moving multiple applications onto pooled or shared computing resources. You have a very strategic decision here. You can move onto shared, standardized platforms or shared infrastructure.PaaS implies h/w and storage consolidation.<CLICK>Consolidating at the infrastructure level is typically done using virtualization technologies to share compute servers, and it can be done without standardization of the software stack. Sharing hardware enables you to run at higher utilization rates, which delivers cost savings from using less total hardware, power, cooling and data center space. However, the software stacks are unchanged, which means you still have the cost and complexity of these heterogeneous software stacks.<CLICK>Consolidating at the platform level means standardizing on a common Middleware and/or Database architecture for multiple or all applications. This standardization reduces the heterogeneity of applications, which is the real driver of complexity and cost. At the same time, a standardized platform speeds development of new applications.As the IOUG survey and customer examples show, more of our customers are consolidation at the PaaS level. Although it’s more difficult to standardize, but customers are doing it because there’s more value to do it, in terms of cost, efficiency and speed.
Three consolidation techniques. The level of consolidation achieved increased from left to right.
Brownfield Vs Greenfield: Are you reusing existing hardware or buying new one
Traditional IT operations are very admin driven, very customized for the application environment, and slow due to transition between different admin teams like hardware, storage, database, etc
The out of box portal, that support all three models – IaaS, DBaaS, and PaaS. The database portal shows the list of requested databases, the requests and their status, notifications for databases due to expire, and resource usage against quota set for the user.
When using non-OVM infrastructure i.e. physical or other VM technologies, then we use Deployment Procedures (DPs) as our provisioning/orchestration mechanism. Think of the database deployment procedure as a wrapper on top of DBCA, where you can save configuration details for the database like memory, cpu, storage, and other init parameters.Typically, each saved deployment procedure would have specialized database configurations. For example,. Small/Medium/Large 11.2.x single instance database. Small/Medium/Large 11.2.x clustered database on ASM/NFS. etc
Service placement in a DB Pool?If there are multiple databases in a pool, how will database services be placed?Change to tree
Standardization Infi file and default parameter to be used example cpu count , Control file name , patch Oracle home / version to be used .Shared file system for database dump for RMAN restoration .Fix memory allocation to each Database typeCreate max number of instance which can be provisioned by each user .
Business Drivers• Retail Assets Segment [Lending Business] • 50% of HDFC Bank‟s Top Line • Always under pressure to launch “New Schemes” to compete and stay ahead in this segment • IT must respond to this Business need because each new Scheme means – changes to application and testing against Production data [UAT database] • Agility in launching new business initiatives
Life Before Database Cloud• Average 3.5 days to provision UAT Database for Loan Management Application• Silo‟ed environment with Average 30% utilization• Compliance requirement consume UAT testing resources.• DBA activities mean $$ paid to SI for provisioning databases manually• Overhead in managing configuration drift between production and test environments.• Rollout impact/delay on new business initiatives
Database Consolidation – Application Classification• Classify application based on system availability requirement/criticality System classification Application Classification Tier 1 Top 15 in terms of systemic risk Customer facing mission critical systems Tier 2 Top end & middle tier High visibility & enterprise wide usage Tier 3 Bottom end of middle tier Smaller user base but critical business function Surround Systems - Satellite system build around core Tier 4 Low tier system
Database Consolidation Planning • Identify candidate application for Cloud • Further Group them based on availability requirement and sub classification based on OS/DBCloud Zone Zone based on criticality Sub category based on version Highly critical 11g zone Exadata Zone UAT system 11g zone (For pilot) 10 g zone Highly CriticalAIX zone 11g zone UAT system 11g zone (For pilot) 11g zoneWindows Medium critical 10g zone
Cloud Administration Setup• Zones Exadata Zone AIX zone• Role for each application on Exadata and AIX zone• Quota is set based on existing infra available 7 Databases on LOS Application 5 Databases on LMS Application 5 Databases on Web collection Application• Universal charge plan• Service Templates Exadata -Three templates with data Exadata -Three templates with only structure AIX template for Small, Medium, Large database only structure
Provision Databases using RMAN Backups• Beta Customer for RMAN restoration integration feature with DBaaS• Level 0 RMAN Backups of Production Databases from Standby[Bunker Copies]• Service Templates created for each of Level 0 Backups• Process to Provision Databases through RMAN is same as Empty Databases
Life after Database Cloud Go-live – Time to ProvisionSno List of activity during New DB infra requirement If Database infra not available time taken Post DBaaS implentation using EM 12c 1 IT team fill tech questionnaire and submit for discussion 0.5 0.5 0 If Database infra available time taken 2 Discussion and TCO in 3 days from discussion 3 0 0 3 Floating of funding proposal based on TCO 10 0 0 4 Approved funding raising PO for infra procurement 3 0 0 5 Delivery of server and infra structure 28 0 0 6 Asset code allocation and movement to DC 3 0 0 7 OS and other infra configuration 3 0 0 8 Identify server (compute+ memory ) 0 0.5 0 9 Storage allocation and publishing for new DB instance 3 0 0 10 Database installation and database creation 1 1 0 11 Database restoration 1 1 3 12 OEM or monitoring configuration 0.5 0.5 0 Total time taken in days /hour Day 56 Day 3.5 Hour 3