MySQL DBaaS with OpenStack Trove

Editor's Notes

• #4: This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template. One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy To learn more about this policy, e-mail: [email protected] For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information.   http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
• #5: With the cloud. Since 2000, about half of Fortune 500 have ceased to exist. Businesses that do not quickly go through this digital transformation won’t survive (they’ll either disappear or get acquired). Because of its: Ubiquity and ease of adoption Unlimited and dynamic capacity And the fact that it helps you innovate faster Cloud is the foundation for digital transformation
• #6: FYI MySQL in not only the most popular database on OnpenStack, it’s also very clearly the leading open source database in the cloud FYI. SaaS, PaaS and IaaS. Easy to plan an hybrid cloud where you would use both private and public clouds.
• #10: OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface.
• #11: The different OpenStack components are: OpenStack Compute (Nova) is a cloud computing fabric controller, which is the main part of an IaaS system. It is designed to manage and automate pools of computer resources and can work with widely available virtualization technologies, as well as bare metal and high-performance computing (HPC) configurations. OpenStack Object Storage (Swift) is a scalable redundant storage system. Objects and files are written to multiple disk drives spread throughout servers in the data center, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally simply by adding new servers. Should a server or hard drive fail, OpenStack replicates its content from other active nodes to new locations in the cluster. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used. OpenStack Block Storage (Cinder) provides persistent block-level storage devices for use with OpenStack compute instances. The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs. OpenStack Image Service (Glance) provides discovery, registration, and delivery services for disk and server images. Stored images can be used as a template. It can also be used to store and catalog an unlimited number of backups. The Image Service can store disk and server images in a variety of back-ends, including OpenStack Object Storage. OpenStack Identity (Keystone) provides a central directory of users mapped to the OpenStack services they can access. It acts as a common authentication system across the cloud operating system and can integrate with existing backend directory services like LDAP. It supports multiple forms of authentication including standard username and password credentials, token-based systems and AWS-style (i.e. Amazon Web Services) logins. OpenStack Networking (Neutron) is a system for managing networks and IP addresses. OpenStack Networking ensures the network is not a bottleneck or limiting factor in a cloud deployment, and gives users self-service ability, even over network configurations. OpenStack Telemetry Service (Ceilometer) provides a Single Point Of Contact for billing systems, providing all the counters they need to establish customer billing, across all current and future OpenStack components. The delivery of counters is traceable and auditable, the counters must be easily extensible to support new projects, and agents doing data collections should be independent of the overall system. Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API. OpenStack Database Service (Trove) is a database-as-a-service provisioning relational and non-relational database engines. OpenStack Dashboard (Horizon) provides administrators and users a graphical interface to access, provision, and automate cloud-based resources. The design accommodates third party products and services, such as billing, monitoring, and additional management tools. OpenStack Data Processing (Sahara) provides a simple means to provision a data-intensive application cluster (Hadoop or Spark) on top of OpenStack. OpenStack Bare-Metal Provisioning (Ironic) is an integrated OpenStack program which aims to provision bare metal machines instead of virtual machines, forked from the Nova baremetal driver. It is best thought of as a bare metal hypervisor API and a set of plugins which interact with the bare metal hypervisors. By default, it will use PXE and IPMI in concert to provision and turn on/off machines, but Ironic also supports vendor-specific plugins which may implement additional functionality. As a side note: you can use Ironic with the pxe_vbox driver to do provisioning using Oracle VM VirtualBox—this can come in quite handy for playing with OpenStack on your laptop/desktop.
• #13: Basic Open Stack Architecture. MySQL default database in the architecture. It was the first DB supported.
• #15: Oracle helps make OpenStack a first class solution for enterprise customers Interoperability and choice is very important for Oracle: customers will be able to choose other OpenStack distribution (e.g. Mirantis) with Oracle VM and Oracle Linux and be able to get support from Oracle. And customers will be able to use other Linux distributions if they elect to do so. Open and flexible approach from Oracle, partnering with other vendors.
• #16: This graphic represents some of the points of integration with OpenStack across the Oracle portfolio. While the Oracle Solaris engineering team have been strongly driving integration with OpenStack right across the cloud services, there are several other points of integration with other Oracle product teams such as Oracle VM, Oracle Linux, Oracle Virtual Networking, Oracle’s storage products, and Oracle’s public cloud services.
• #20: For creating clouds, OpenStack has huge momentum and has become an extremely popular solution. Mainstream companies are now adopting it.
• #21: https://gigaom.com/2015/02/17/openstack-comes-up-huge-for-walmart/ For those skeptics who still think OpenStack isn’t ready for prime time, here’s a tidbit: @WalmartLabs is now running in excess of 100,000 cores of OpenStack on its compute layer. And that’s growing by the day. It’s also the technology that ran parent company Walmart’s prodigious Cyber Monday and holiday season sales operations. If that’s not production, I’m not sure what is. San Bruno, California–based @WalmartLabs, which is the e-commerce innovation and development arm for the Walmart retail colossus, started working with OpenStack about a year and a half ago, at first relying heavily on the usual vendors but increasingly building up its in-house talent pool, Amandeep Singh Juneja, senior director of cloud operations and engineering, said in an interview. Building a private cloud at public cloud scale Get all the news you need about Cloud with the Gigaom newsletter @WalmartLabs has about 3,600 employees worldwide, 1,500 of whom are in the Bay Area. Juneja estimated the organization has hired about 1,000 engineers in the last year or so — no mean feat given that there are lots of companies, including the OpenStack vendors, in the market for this expertise. “Traditionally, Walmart is vendor-heavy in its big technology investments — name a vendor and we’ve worked with it and that was also true with OpenStack,” Juneja noted. “We started about one and a half years ago with all the leading distribution vendors involved … we did our first release with Havana and Rackspace. But then we invested internally in building our own engineering muscle. We attended all the meet-ups and summits.” Havana is the code name for the eighth OpenStack code release. Nothing says big like Walmart. It has around $480 billion in annual revenue, more than 2 million employees, and more than 11,000 retail locations worldwide (including Sam’s Club and Walmart International venues). Walmart.com claims more than 140 million weekly visitors. So scale was clearly an issue from the get-go. What @WalmartLabs loved about OpenStack was that it could be molded and modified to fit its specifications, without vendor lock-in. AWS need not apply This is a massive private cloud built on a public cloud scale. There are also some macro issues at play here. Since parent company Walmart competes tooth and nail with Amazon.com, the chances of Walmart using Amazon Web Services public cloud are nil. (I asked Juneja whether Walmart would ever use any public cloud capabilities and he politely responded that this question was above his pay grade.) The beauty of open-source projects like OpenStack is that new capabilities continually come on line and there is a community of deeply technical people working on the code. Going forward, Juneja is particularly interested in Ironic, an OpenStack project to enable provisioning of bare metal (as opposed to virtual) machines, and in the Trove database-as-a-service project. Trove, he noted, has matured a bit and Walmart will be using more DbaaS going forward. Another work in progress is the construction of a multi-petabyte object store using the OpenStack Swift technology, but there are also plans to bring more block storage in-house, possibly using OpenStack Cinder. And the team is looking at Neutron for software-defined network projects. One thing Walmart must deal with is its brick-and-mortar roots. The ability to order online and pick up in the store means that what @WalmartLabs builds must interact with inventory and other systems already running the Walmart/Sam’s Club storefronts. Non-e-commerce-related IT projects are run by Walmart’s Information Services Division at the company’s Bentonville, Arkansas headquarters. So the ability of the shiny new OpenStack systems to interface with infrastructure that’s been in place for decades or so — some for as much as 50 years — is critical. It also spells the full employment act for all those @WalmartLabs engineers.
• #22: http://www.theregister.co.uk/2015/02/18/fujitsu_group_goes_full_openstack/ Fujitsu is going to migrate its internal IT to an OpenStack cloud platform to save 35 billion yen and get world-leading creds for OpenStack expertise and commitment. The new group-wide cloud platform will involve about 640 large-scale and complex systems across 13,000 servers globally. The staged transition starts this month and is scheduled to be completed within five years with the 35 billion yen savings coming from a reduction in total cost of ownership (TCO). The internal systems include CRM/sales-support systems, SCM/ECM systems, corporate systems, such as for HR and accounting, and a global communications platform for 170,000 employees across some 540 group companies. It says: “The new cloud services platform will be used to quickly build systems that, by employing the latest technologies, such as mobile technologies and big data, can respond quickly to a changing business environment.” Fujitsu aims to develop reference models for large-scale customers seeking to do the same thing. It wants its own internal IT to contribute to its business, be efficient and have its internal deployments serve as reference models for its customers. It can say to customers we eat, live and breathe our own OpenStack meals. Does anybody else? This is probably the single most momentous and significant OpenStack commitment across the entire IT industry, and probably beyond. OpenStack supporters will be thrilled.
• #23: What are the top drivers for OpenStack adoption? Ability to innovate ranks #1. In line with the digital transformation we talked about. Go through list.
• #24: OpenStack is maturing very fast, used now a lot more in production than for Dev/QA and POC. On-premises private clouds represent the majority of deployments
• #25: Top 3 Workloads: Web Services QA/Tests Databases By far #1 Database: MySQL. Link: Let’s look at a couple of example where OpenStack is used in conjunction with MySQL
• #26: http://www.informationweek.com/cloud/infrastructure-as-a-service/photobucket-pictures-its-future-on-openstack/d/d-id/1112740 Photobucket Pictures Its Future On OpenStack Cisco's version of an OpenStack private cloud helps Photobucket ease implementation and management of networking issues. Photobucket is using a Cisco-built OpenStack cloud to better compete with the heavily financed Instagram, Pinterest, and Flickr as a lifetime destination for users' photos. Photobucket stores personal photos, provides editing tools, and generates a link to users' photos so that they can be displayed in documents or on other websites without being uploaded to those destinations. The 10-year-old, 74-employee company was once all the buzz. Now it has to compete with Pinterest, which wants to be everyone's lifetime scrapbook site for photos, videos, and documents. In late October, Pinterest garnered $225 million in venture capital to expand its services, following $200 million it received in February. Its estimated valuation is $3.8 billion. Photobucket knows it lags behind Instagram, the instant sharing service that adds a telegram-like ability to deliver images wherever its users want. But Photobucket figures it has edged ahead of Flickr, because it hosts 4 billion transactions a day, has links to 3 million websites, hosts 20 million unique visitors a month, and stores 14 billion pictures. [Want more on how Photobucket uses mobile applications? See Help Wanted 2.0: SMB Recruiting Goes Mobile.] Given the nature of the competition, Photobucket sought to operate in the most efficient manner possible. It knows that fractions of a penny saved in one part of its operations would support other operations as a long, competitive race runs itself out. These challenges prompted Mike Clark, Photobucket's co-founder and CTO, and Jay Kistler, its director of operations, to look for the best way to reorganize its infrastructure in 2012. Kistler realized that server utilization was only in the 15%-20% range for 800 bare-metal servers. Virtualization would improve that, but how should it virtualize? Key staff members began OpenStack pilots in what was still an early version of the open-source cloud software. The staff members "dove in" and found OpenStack a somewhat unruly amalgamation of code at the time, Kistler told us. "It's not for the faint of heart." Particularly baffling was the Quantum networking part of OpenStack (now renamed Neutron), which proposed a new way to do networking in the cloud. Kistler and Clark weren't too sure how its software-defined approach to virtualized networking was going to play out. "We actually are a strong command-line company," Kistler said. IT operations were comfortable with Cisco's converged approach to racks of servers, network switches, and storage in its unified computing system (UCS) architecture, but they didn't want an all-proprietary Cisco cloud. Cisco was happy to help Photobucket implement a Cisco version of OpenStack on top of UCS. Now, instead of 800 bare-metal servers, Photobucket operates MySQL databases serving content from 350-400 physical servers. Hadoop analytics (essential to understanding what users are doing and how they're using Photobucket servers) also runs unvirtualized on a bare-metal cluster. The rest of operations run on the OpenStack Cloud, which has cut an additional 350-400 servers down to two UCS clusters -- one running in Denver and one in Phoenix. Both are operated from one management console as a single OpenStack cloud.The Cisco distribution of OpenStack includes a plugin for OpenStack's Quantum networking that works with the Nexus 1000 switch for multiple virtual machines and Cisco's accompanying networking fabric. Clark said choosing this option saved Photobucket the task of deciphering an emerging and rapidly changing part of the OpenStack cloud. "It requires some real technical acumen to stand up an OpenStack cloud."Photobucket has gone its own way with the Salt open-source configuration and deployment engine, written in Python, the preferred language of the firm's developer teams. Kistler and Clark were enticed by the Xen hypervisor, a version of which runs the Amazon Web Services cloud. But in the end, they leaned toward OpenStack's default hypervisor, KVM, which was more efficient in their virtualization bakeoffs than VMware's ESX Server or even Red Hat's version of KVM used in its Enterprise Virtualization suite. "We stood up their version, but it didn't meet our internal benchmark as most performant," Clark said. The Photobucket staff members are comfortable dealing with the update and compatibility issues of open-source code, and they like Cisco's commitment to support the OpenStack project. They liked the vigor of the project itself, with its many large-company backers and long list of contributors. "The DOM zero stuff in Xen" -- the need to establish Domain 0 with Xen before it can operate -- "looked out of date" in comparison, Clark said. Contributions to Xen looked "not as relevant as those coming in to KVM," and some of the staff's favorite Xen contributors had moved over to the KVM project. Kistler and Clark still have reservations about the tendency of one OpenStack project to "solve the same problem" as another, leading to confusion over what should be implemented to rationalize operations. But again, they felt Cisco's OpenStack would have Cisco's guiding hand behind it, making choices for its UCS rack architecture. Now Photobucket's IT staff is looking at deploying fresh OpenStack servers in two to three minutes, instead of the minimum two to three hours that it used to take. It is using only 60% of its UCS rack architecture, leaving 40% available to plug in more converged servers and networking. Meanwhile, it has consolidated 10-12 servers down to a UCS blade or 2u rackmount server. Running Photobucket systems has gotten easier in the process. "Everyone's walking around with sort of a smile on their face, because they're not fighting to keep the infrastructure running," said Kistler. With his shop 60% virtualized today, he expects that figure to be 90% by this time next year, with more of it running on the OpenStack private cloud.
• #27: Example of DBaaS with MySQL: CERN Case Study: https://blogs.oracle.com/MySQL/entry/with_its_mysql_database_as The European Organization for Nuclear Research (CERN) is one of the world’s largest and most respected centers for scientific research. Founded in 1954 and located near Geneva on the Franco-Swiss border, CERN was one of Europe’s first joint ventures. Today, it has 20 member states. The organization uses the world’s largest and most complex scientific instruments to study fundamental particles and the origin of the universe. Challenges Better support the scientists associated with a CERN research program who selected MySQL as their database. Empower users, enabling them to be as self-reliant as possible. Minimize complexity and costs for the CERN IT department to support the growing number of MySQL deployments. Solution Delivered a MySQL Database-as-a-Service offering to the CERN employees and the scientists associated with the organization. Allowed researchers selecting MySQL for their project to get access to a database instance hosted by the CERN IT department, either from the start or once their application has become critical. Implemented the service using Oracle’s server virtualization software, Oracle VM, for increased flexibility and reduced costs. Empowered users with a self-service approach, providing them with tools to manage MySQL themselves while handling backups and other basic database administration tasks for them. Enabled scientists to rely on MySQL with increased reliability, security and manageability while reducing complexity and minimizing costs. "The Cloud model has allowed us to deliver a self-service platform to our MySQL users, empowering them while minimizing costs for CERN." Tony Cass, Database Services Group Leader, IT department, CERN. CERN is also using OpenStack: http://www.openstack.org/user-stories/cern/ Unleashing Secrets of the Universe with Help from OpenStack When one of the world's most prestigious research laboratories decided to embrace cloud computing, it chose OpenStack. Using the world’s largest, most complex scientific instruments, CERN, the European Organization for Nuclear Research, continues its study of the most basic constituents of matter – fundamental particles – to help scientists gain a better understanding of the very structure of the universe. Recently, after years of searching, calculations, speculation, and smashing atoms together, CERN together with the ATLAS and CMS experiments announced that the elusive Higgs Boson that provides mass to elementary particles had been found. An exciting time in science, indeed. And as one might suspect, all of this research generates tremendous amounts of data, which require thousands of computers to process. Using highly-specialized algorithms, the data from the most interesting – and scientifically promising – events are transferred to CERN’s data center for processing. The data are saved to tape storage and then distributed to the more than 150 sites worldwide that comprise the Worldwide LHC (Large Hadron Collider) Computing Grid (WLCG) for analysis. The instruments CERN uses to smash these particles and collect data are as massive as they are complex. The accelerators stimulate beams of particles to high energies before the beams are made to collide. The LHC detectors observe and record the results of these collisions, which generate up to an astonishing one petabyte (that’s a quadrillion bytes) every second before filtering. One of the detectors at the LHC is more than 7,000 tons measuring over 5 stories high. For years, commodity computing devices kept pace with these massive data processing needs. For instance, the CERN data center in Geneva boasts 10,000 servers, 80,000 disks, and 100 petabytes of data stored in mass-storage systems– but it has reached its power and cooling capacity. In Budapest, Hungary, an additional similar data center is online with 200 Gbp/s network connections connecting both sites. Still, as CERN’s data processing needs continued increasing while staffing remained fixed, the organization decided that cloud computing could provide a complementary approach to deliver services at scale to its physicists. Ready for Cloud The timing for that decision proved ripe. Cloud computing technologies had begun to mature to the point that they could help handle such demanding workloads. Also, CERN users were growing increasingly familiar with using public clouds to provide additional capacity during peak times. “Providing a modern infrastructure-as-a-service private cloud that had similar capabilities to those available in public clouds would support the data and compute demands of their research,” says Tim Bell, manager of infrastructure services at CERN. CERN began to investigate various virtualization and cloud platforms. CERN’s IT team decided it would build a private cloud that would need to integrate well with a very heterogeneous environment. CERN’s service consolidation environment is based on the Microsoft Service Center Virtual Machine Manager and the Hyper-V hypervisor. The IT team also built a cloud test bed based on OpenNebula and KVM (Kernel-based Virtual Machine) hypervisor. “Multiple hypervisors are attractive with respect to support models, performance analysis, and flexibility. The choice of hypervisor should be a tactical one not determined by the cloud infrastructure, and we plan to run a mixed hypervisor environment in the future,” says Bell. As CERN investigated potential components for new infrastructure tools and processes in 2011, it reviewed a number of candidates. In the end, CERN selected OpenStack. As a cloud platform, OpenStack controls and automates pools of compute, storage, and networking resources to turn standard hardware into a powerful cloud computing environment. Today, OpenStack is the fastest growing open cloud community, working to build software that powers public and private clouds for a growing number of organizations, including Cisco WebEx, Comcast, eBay, HP, Intel, MercadoLibre, NeCTAR and Rackspace. “OpenStack’s technical architecture clearly addressed our needs to run at scale,” says Bell. “Also, the technology and developer ecosystem around OpenStack are very vibrant and would enable us to build the services we needed within the cloud. With an open community, we can benefit from the work of the active contributors but also use our engineering skills to enhance the product for others.” A critical aspect of CERN’s move to cloud computing was the ability to interact with all of its existing IT services. “Our network infrastructure is based on a home-grown framework to meet the needs of running a laboratory with millions of IP devices. We were able to extend OpenStack to support dynamic allocation of network addresses and register those with our network management system. Further extensions for creating DNS entries, Kerberos, and X.509 certificates were also implemented,” he says. Building the CERN Private Cloud with OpenStack CERN’s IT department started working on OpenStack toward the end of 2011, building test clouds for physicists to explore cloud technologies and test integration with CERN specific customizations. Using Scientific Linux, developed by CERN and Fermilab based on the Red Hat distribution, a cloud was rapidly built with Compute, Image, Identity and Dashboard services. This environment has gradually grown to over 400 hypervisors with high availability on all OpenStack controllers using recipes from the community. Planning and testing is now ongoing to expand the cloud to 15,000 hypervisors with over 150,000 VMs in the next 18 months. “Seeing the size of several deployments in production that are already larger than our target validates our approach to be able to share and to benefit from others”, said Bell. During 2012, a team at the CMS detector at CERN, was planning their activities for the 2 year upgrade of the LHC. Currently, a compute farm of 1,300 servers and around 13,000 cores is installed to filter the data from the detector before sending it for recording at the CERN computer centre. However, during the upgrade, this farm would not be required. In less than two months, the team created a proof-of-concept cloud based on OpenStack with a controller, a distributed authentication service, two Compute nodes, and a node for Image Services. They used MySQL for their database, RabbitMQ for messaging, and because KVM had been used before in CMS, it was chosen as the hypervisor. “The deployed infrastructure was very stable and the OpenStack API layer makes it possible for us to fully manage the entire VM lifecycle,” says Jose Antonio who led the work to implement the cloud at CMS. At the beginning of October 2012, the team performed a large-scale test with OpenStack controlling about 1,200 hypervisors. The OpenStack environment deployed 720 virtual machines in roughly an hour – about one every 5 seconds. “The infrastructure and networking were stable. The cloud controller, a server with four cores, was at the limit of CPU usage,” says Wojciech Ozga, who completes the team that deployed OpenStack on the CMS cluster. Since the initial deployment, the infrastructure controller has been upgraded to a 16 core, 48GB RAM server, allowing greater throughput and is now serving physicists of the CMS experiment. The Vibrant OpenStack Community OpenStack attracts experts in various technologies and disciplines around the world to collaborate on the platform. “A big part of that success, and anticipated future successes, is the deep, active, and highly collaborative OpenStack development community. An example came from our collaborations with PuppetLabs, which produced a set of Puppet configuration recipes to allow easy, yet very specific, OpenStack deployments. Building on top of those recipes, we provided the configuration options that we needed, such as SSL and Red Hat support. We incorporated these changes back into the PuppetForge community for others to use,” Bell says. Another example is the significant identity management challenges at CERN. Currently, CERN has 44,000 users registered in its identity management system, and more than 400 users are added or removed each month. “Depending on their roles in the organization, some of these users will have rights to be administrators or project members of the private cloud,” Bell explains. While an earlier version of OpenStack provided basic LDAP support, a number of enhancements were required for Active Directory support at the scale CERN required. “Working with the OpenStack team, we enhanced the LDAP support to cover our use case – and these changes will be included in an upcoming version of OpenStack. These contributions illustrate the benefits of open communities and peer reviews that ensure both use case demand and software quality,” he says. And the cloud deployment has been a smashing victory. Today, multiple clouds at CERN successfully run collision reconstructions on OpenStack. “Cloud technology has allowed us to be much more responsive to our user community allowing them to explore the frontiers of science without waiting for hardware to be delivered and configured”, says Bell. See also: https://blogs.oracle.com/MySQL/entry/with_its_mysql_database_as With Its MySQL Database-as-a-Service CERN Empowers Scientists The European Organization for Nuclear Research (CERN) is one of the world’s largest and most respected centers for scientific research. Founded in 1954 and located near Geneva on the Franco-Swiss border, CERN was one of Europe’s first joint ventures. Today, it has 20 member states. The organization uses the world’s largest and most complex scientific instruments to study fundamental particles and the origin of the universe. Challenges Better support the scientists associated with a CERN research program who selected MySQL as their database. Empower users, enabling them to be as self-reliant as possible. Minimize complexity and costs for the CERN IT department to support the growing number of MySQL deployments. Solution Delivered a MySQL Database-as-a-Service offering to the CERN employees and the scientists associated with the organization. Allowed researchers selecting MySQL for their project to get access to a database instance hosted by the CERN IT department, either from the start or once their application has become critical. Implemented the service using Oracle’s server virtualization software, Oracle VM, for increased flexibility and reduced costs. Empowered users with a self-service approach, providing them with tools to manage MySQL themselves while handling backups and other basic database administration tasks for them. Enabled scientists to rely on MySQL with increased reliability, security and manageability while reducing complexity and minimizing costs. "The Cloud model has allowed us to deliver a self-service platform to our MySQL users, empowering them while minimizing costs for CERN." Tony Cass, Database Services Group Leader, IT department, CERN.
• #28: Lots of resources to get going on Openstack.org. Numerous white papers and other resource for Oracle OpenStack at: http://www.oracle.com/us/technologies/linux/openstack/overview/index.html
• #30: Indeed, the current state of DB deployments is typically Siloed, Dispersed, Varied and Complex, with multiple challenges. This is an inefficient use of resources.
• #31: Shared, standardized database platform for consolidation of existing apps and rapid development/deployment of new apps
• #32: DBaaS with MySQL Enterprise Edition helps you address all those key points. You can improve agility while also improving security, performance and uptime while reducing TCO with improved operational efficiency. DBaaS with MEE represents a foundation for digital transformation, enabling you to innovate faster (more details later in the pres on the different MEE components). Your teams/individuals get access to MySQL instances for rapid and agile application development while management of those DBs is centralised, automated and secure.
• #33: Trove is the Database as a Service module for OpenStack. It's designed to run entirely on OpenStack, with the goal of allowing users to quickly and easily utilize the features of a relational or non-relational database without the burden of handling complex administrative tasks. Cloud users and database administrators can provision and manage multiple database instances as needed. More info at: https://wiki.openstack.org/wiki/Trove Note for speakers: While Trove is already enjoying huge momentum, it is as noted relatively recent. MySQL was the first database supported and can absolutely be used now for DBaaS. Trove is however not yet supported in Oracle OpenStack for Oracle Linux 1.0, i.e. you cannot just yet get support from Oracle for the Trove piece. But, it will be supported in the next release.
• #37: General Talking Points - Ten developers on project - Two on core team - HQ in Cambridge, R&D in Toronto Most advanced Trove distribution available Enterprise grade support Certified with major databases and distributions Tesora is the enterprise’s trusted advisor for Trove #1 contributor to OpenStack Trove project Additional talking points for Enterprise Guest images Oracle multitenant DB support Early Upstream Replication improvements Access to patches and bug fixes PostgreSQL support Enterprise-only features Proprietary DBs Oracle support
• #40: MySQL Enterprise Edition includes the most comprehensive set of advanced features, management tools and technical support to help you make the most of your applications. Next I’ll cover the things that particularly helpful within the DBaaS context.
• #41: MySQL Enterprise Monitor provides real-time visibility into the performance and availability of all your MySQL databases. You can install the Enterprise Monitor agent directly in your Trove Guest Images, and configure the Agent so that it automatically reaches out to the Enterprise Monitor server. This helps you to easily ensure that all of your MySQL instances are being properly monitored. The MySQL Query Analyzer feature also enables developers and DBAs to quickly pinpoint problematic SQL code, and eliminate current performance problems and head off potential performance issues as your application grows.
• #42: MySQL Enterprise Backup provides enterprise-grade backup and recovery for MySQL. It delivers hot, online, non-blocking backups. It supports point-in-time recovery, backup validation, incremental backups, encryption, compression, and does all of this directly to OpenStack using the Swift API.
• #43: Considering the various security issues highlighted in the past year in the media, security is a very big concern for CIOs. I’ll note some of the security features of MySQL Enterprise Edition. The first is MySQL Enterprise Authentication. That includes ready to use external authentication modules to easily integrate existing security infrastructures, including Linux Pluggable Authentication Modules (PAM) and Windows Active Directory. By authenticating MySQL users from centralized directories, organizations can easily implement Single Sign On. The same user names, passwords and permissions can be used. This makes MySQL DBAs more productive by eliminating the need to manage credentials in individual systems. It also makes IT infrastructures more secure by leveraging existing security rules and processes (e.g. identifying weak passwords and managing password expiration).
• #44: MySQL Enterprise Encryption helps to protect sensitive data throughout its lifecycle, and it also provides industry standard functionality for asymmetric encryption (Public Key Cryptography). It also provides encryption, key generation, digital signatures and other cryptographic features to help organizations protect confidential data and comply with regulatory requirements including HIPAA, Sarbanes-Oxley, and the PCI Data Security Standard.
• #45: According to a 2014 study by the Ponemon Institute, 43% of companies have experienced a data breach of some sort in the past year. According to the Internet Security Threat Report 2014 from Symantec: 552 Million identities exposed in 2013. 493% increase over previous year. 77% of websites had a vulnerability, with 1-in-8 of them having a critical vulnerability. Total Breaches increased 62% in 2013 Firewall provides a “positive security model” and helps to prevent the following types of attacks: - SQL Injection Buffer Overflow Out of policy database transactions detected and blocked. It includes logging & analysis, and is really an essential part of operating MySQL within OpenStack, and the Cloud in general.
• #46: MySQL Enterprise Audit provides an easy to use, policy-based auditing solution that helps organizations implement stronger security controls and satisfy regulatory compliance. Auditing serves as the “Passive Defense” against the vulnerabilities and security threats: Collect and Analyze Database Activity Look for suspect activity Respond As more sensitive data is collected, stored and used online, database auditing becomes an essential component of any security strategy. To guard against the misuse of information, popular compliance regulations including HIPAA, Sarbanes-Oxley, and the PCI Data Security Standard require organizations to track access to information.
• #47: To meet the sustained performance and scalability of ever increasing user, query and data loads MySQL Enterprise Edition also provides advanced scalability with the MySQL Thread Pool. The Thread Pool provides a highly scalable thread-handling model designed to reduce overhead in managing client connections and statement execution threads.
• #48: We just mentioned MySQL Fabric for HA. It is indeed one of your options and also delivers scale-out through sharding. MySQL Fabric is integrated with OpenStack.
• #49: MySQL Enterprise Edition includes access to Oracle Premier Support for MySQL. You get direct access to our expert MySQL Support engineers who are ready to assist you in the development, deployment, and management of MySQL applications.
• #50: MySQL Consultative Support service is included in Premier Support. Consultative Support is a proactive approach that is designed to help you avoid critical outages. MySQL Support Engineers advise you on how to properly setup and tune your MySQL servers, schema, queries, and replication set-up to maximize performance and availability.
• #51: Also tools to enhance scaling, security and data protection. Whether you are running RT analytics, or serving results of Hadoop M/R job, need to ensure data is protected and secure. MySQL Enterprise Scalability: Thread Pool provides an efficient, thread-handling model designed to reduce overhead in managing client connections – important as data voles and velocity grow, delivering up to 20x higher performance. MySQL Enterprise Monitor: Allows you to ensure availability, best practices, and optimal performance for your MySQL servers. MySQL Enterprise Security: Provides ready to use external authentication modules to integrate MySQL with existing security infrastructures including PAM and Windows Active Directory, ensuring secure access to your most sensitive data. MySQL Enterprise Audit:  Enables you to quickly add policy-based auditing compliance to Big Data workflows. You can dynamically enable user level activity logging, implement activity-based policies, manage audit log files MySQL Enterprise Backup: performs online "Hot" backups of your databases. MySQL Enterprise Encryption: To protect sensitive data throughout its lifecycle, MySQL Enterprise Encryption provides industry standard functionality for asymmetric encryption (Public Key Cryptography). MySQL Enterprise Authentication: allows you to plug into and leverage your existing security and authentication infrastructure such as LDAP, Kerberos, or native Unix and Windows authentication. MySQL Enterprise HA: offers a wide range of options to ensure availability of your MySQL servers—MySQL Fabric, Windows Failover Clustering, Solaris Cluster, DRBD with Pacemaker+Corosync, Oracle Clusterware with MySQL plugin, Oracle VM templates for MySQL, and finally the new MySQL Group Replication which is available as a feature preview today on labs.mysql.com. Oracle Enterprise Manager for MySQL: integrate MySQL monitoring with your existing OEM infrastructure.
• #69: To conclude, I’d like to encourage you to register for MySQL Central @ OpenWorld. This is a unique opportunity to hear from Oracle executives and engineers about the latest MySQL innovations and plans while also meeting other users, customers and partners. There’ ll be: ... It’s a great opportunity for you to boost your MySQL skills and network and we hope to see you there. With that I’d like to thank you for attending this presentation and wish you a great day, afternoon or evening depending on where you’re based. Bye bye.