Oracle VM Template for MySQL Enterprise Edition =========================================================================== === Note: * This is first release of MySQL in a Template delivery for installation in an Oracle VM Environment. It is assumed that user of this template has working knowledge of Oracle VM, Oracle VM Manager and simple basics of MySQL and its use as a database server. 1. Introduction =============== The Oracle VM Template for MySQL, allow fast deployment of a MySQL database environment without expert knowledge or requiring complex setup procedures to achieve High Availability and agile infrastructure. This documentation describes purpose and scope of templates. It also describes flow and details step-by-step instructions for downloading templates and deploying an HA MySQL environment. The contents of this document are based on following software versions: - MySQL HA Database Template * Oracle Linux 5 Update 6, 64 bit * MySQL 5.5 Update 10.1, 64 bit The following considerations were made when se templates were designed: * This template can be used for Production. Production use assumes additional configuration of underlying Oracle VM environment, specifically virtual shared disk configuration, and virtual network configuration, to achieve specific performance goals. On intial boot, template will step a user through available choices found in current Oracle VM environment to configure MySQL server.
* English is only language currently supported in template itself and Oracle Linux operating system. * This template is based on a para-virtualized architecture. Hardware virtualization (HVM) will require a future HVM template. * A limited familiarity with MySQL is assumed. MySQL Documentation, http://dev.mysql.com/doc/refman/5.5/en/ remains best source for MySQL issues. This Template installs commercial Enterprise Edition of MySQL, and user must follow current practices for obtaining any subscription or licenses required. * The template carries or rpm objects normally found in MySQL Community Server tarball, MySQL Client, MySQL Development Libraries, MySQL Shared components, MySQL Test Suite. This is done so that optional libraries or libraries deployed to remote clients will match installed server. Or MySQL download components, such as Workbench are not found in this template. This document is intended to help you get started deploying MySQL in Oracle VM environment. For concepts that are found unfamiliar or vague you are encouraged to review Oracle VM Manager guide at http://www.oracle.com/technetwork/documentation/vm-096300.html 2. Installation Instructions ============================ 2.1 Minimum Hardware Requirements -------------------------------------------------- 1) Sufficient filesystem space ( following presumes sparse file support as found in VM 2.2 ocfs2) The 5.5.10 version of template Under /OVS ( virtual manager server pool shared storage): /seed_pool 14GB - template image /running_pool 14GB - system and mysql images 10GB - mysql database image (sized for default configuration for Innodb)
additionally, temporary storage for compressed template and scratch space to decompress before import into template library (/ seed_pool) template zip file 1.8G scratch space 2G 2) platform minimums * sufficient memory 2G is default Dom-U virtual machine allocation (per copy) * sufficient CPU 1 physical core per virtual machine, strongly recommended 1 core per. * 2 network cards (NIC) requirement of Oracle VM when configured with HA Enabled * IP address 1 public for MySQL service note: Oracle VM 2.2 bundles OCFS2 v1.4.4 which by default is configured for sparce file support. EXT3 also supports sparse file. NFS can be configured for sparse file for some configurations. file sizes reported can be 10x when sparse file is not supported by underlying file system. 2.2 Template Description --------------------------------- The MySQL VM Template is actually a 'golden' template based on Oracle VM Linux 5 Update 6 template, with additions for MySQL. The additions follow Oracle VM Template pattern for first boot configuration prompting and installation as a High Available service. The MySQL VM Template uses separate virtual images, mysql and mysqldb, to separate product software and data from base Oracle Template software and data. This allows update of MySQL image to reflect compatible software release update without a requirement to deploy or reinstall eir OS or MySQL data. It also supports deploy ment of MySQL database as a single image greatly improving performance of database copy. (i.e., copy of a database is limited by byte transfer speed, not byte transfer plus backup
and reload speeds) The OS image is a minimal install of Oracle Linux 5 Update 6 with Unbreakable Kernel. Only basic RPM packages have been installed as required by OS or MySQL Server. The MySQL image is a basic install of MySQL 5.5.10 Server and MySQL 5.5.10 Client. The corresponding RPMs of an Enterprise Release can be found in image /mysql/rpm, e.g., development, embedded, shared and test. MySQL is configured for a standard production deployment, using one of 6 configuration baselines found in Enterprise release of MySQL. The Template is delivered as a single ZIP file (~1.8Gbytes). Inside this ZIP file is a single compressed tar (tar gzip) file with approximately same size, requiring ~2Gbytes temporary storage for expanding as a template. These zip/tgz files can be deleted once template has been imported. 2.3 Prepare OVM Environment ----------------------------------------- Allocate necessary hardware and install Oracle VM from E-Delivery. i) Download and install OVM Server from http://edelivery.oracle.com/ oraclevm ii) VNC viewer software is recommended to connect to guestôøωs console for initial configuration tasks. While any VNC viewer is acceptable, all references are for tightvnc, http://www.tightvnc.com/ iii) See Oracle VM Server and Oracle VM Manager guides for minimum hardware requirements. The MySQL Template requires approximately an additional minimum 20GB for unzipped, untarred template and 20GB for each virtual machine created from template. The MySQL database is created on underlying shared storage that is created during Oracle Server installation, and assigned to Server Pool. Refer to MySQL documentation for specific database sizing, Virtualization environment does not change any size calculations for database itself.
2.4 Download Templates ---------------------- Use following link to download unzip package for Linux (if needed): http://oss.oracle.com/el4/unzip/unzip.html The following are filenames for this template distribution: V26747-01.zip MySQL VM Template for Oracle Linux 5.5 (64 bit) with Unbreakable Linux Kernel <versioned-package-id> OVM_OL5U6_X86_64_MySQL5_5_10_PVM.tgz Follow instructions for login and agreement to download at http://edelivery.oracle.com/linux, Oracle VM Templates, x86_64 packages, and finally OVM_OL5U6_X86_64_MySQL5_5_10_PVM.tgz media pack. The following assumes this object was downloaded to /tmp, any local directory is supported, just modify reference appropriately. # mkdir OVS/seed_pool/OVM_OL5U6_X86_64_MySQL5_5_10_PVM # cd OVS/seed_pool/OVM_OL5U6_X86_64_MySQL5_5_10_PVM # tar -xvf /tmp/ovm_ol5u6_x86_64_mysql5_5_10_pvm.tgz 2.5 Import Templates -------------------- At this point you should have a directory containing extracted VM template. This comprises a vm.cfg file and a number of disk images -.img files. For example: /OVS/seed_pool/OVM_OL5U6_X86_64_MySQL5_5_10_PVM - System.img (OS image file) - mysql.img (MySQL DB Software)!- mysqldb.img (MySQL Database & Logs) - vm.cfg (VM configuration file) - README The next step is to import template into Oracle VM Manager. i) Log into Oracle VM Manager and navigate to Resources tab. The
Virtual Machine Templates screen is displayed. Click Import. The Source screen is displayed. ii) Choose Select from Server Pool (Discover and register) and click Next. The General Information screen is displayed. iii) Enter or select following: Server Pool Name: Select server pool on which virtual machine will be located. Virtual Machine Template Name: Select Oracle VM template to be imported. Operating System: Select operating system of virtual machine - OEL 64 bit for this template Virtual Machine System Username: Enter username used to log into virtual machine. Enter 'root' here. Virtual Machine System Password: Enter password used to log into virtual machine. Enter 'ovsroot' here. Description: (Optional) Enter a description of virtual machine. Click Next. The Confirm Information screen is displayed. iv) Click Confirm. The Virtual Machine Template screen is displayed with a message to confirm import of template. v) To make virtual machine template available for use, select virtual machine template and click Approve. The View Virtual Machine Template screen is displayed. Click Approve. The Oracle VM template is now imported and ready for use in Oracle VM Manager. 2.6 Creating a Virtual Machine from Template
------------------------------------------------- This section describes how virtual machines can be created from template using Oracle VM Manager. For additional information on VM creation using Oracle VM Server command line consult OVM documentation referenced in introduction. i) Log in to Oracle VM Manager and navigate to Virtual Machines tab. Click Create Virtual Machine. The Creation Method screen is displayed. ii) Select Create virtual machine based on virtual machine template. Click Next. The Server Pool screen is displayed. iii) Select Server Pool on which to create virtual machine. Select an option from Preferred Server dropdown. Click Next. The Source screen is displayed. iv) Select template you imported in Step 1, and click Next. The Virtual Machine Information screen is displayed. v) Enter virtual machine name in Virtual Machine Name field. Enter console password in Console Password field. Confirm console password by entering it again in Confirm Console Password field. Select network Interface Card. Click Next. The Confirm Information screen is displayed. vi) Confirm virtual machine information, and click Confirm. The Virtual Machine screen is displayed with message "Creating Virtual Machine". vii) When virtual machine is created, Status changes from Creating to Powered Off. To power on virtual machine, click Power On. viii) When virtual machine status is changed from Initializing to Running, you must connect to VM console via VNC. If you are not familiar with VNC you may want to consult OVM Documentation and check within
README file that was extracted with template. see workaround below, if VNC can not be used in current OVM environment. ix) At this point you will be prompted with a very specific set of questions specific to MySQL server installation. This first boot script will complete installation of MySQL Server in this virtual domain, start MySQL server, and set domain to automatically start this server at each poweron event. This first boot script is n de-activated. 2.6.1 Database Initialization ------------------------------ The following questions will be asked when MySQL VM is being initialized. * Specify TCP port that will be used for MySQL Server [3306]: * Specify a default configuration from my-huge, my-large, my-small, my-medium or my-innodb-heavy-4g configuration defaults. * Specify wher MySQL is automatically or manually started at system POWERON * follow prompts of mysql_secure installation script to specify a password to be used for database accounts. Note that same password will be used for 'root' and 'mysql'. se can be subsequently changed once server is started. See MySQL documentation for details. The configuration is saved to /etc/my.cnf, which can be edited for any additional configuration settings. 3. Using Virtual Environment ================================= Once your virtual machine(s) have been created in steps above y are ready to used. * ssh to virtual machine and invoke mysql client. #mysql -u root -p <password>
* [as needed, download mysql client rpm to a local machine and install] #mysql -u root -p <password> -h <virtual-machine system name> 4. Administration of Running Environment ============================================ The MySQL environment is administered in same way as a conventional bare metal environment. You use same utilities to manage your environment such as mysqladmin or MySQL Workbench. 4.1 MySQL Configuration -------------------------------- The virtual machine creation will place configuration in /etc/my.cnf for server startup. These values can be changed using an editor on text file, to be used on subsequent server startups. Note: server is started from an unstarted state wheen virtual machine is created, or after domain was shutdown or rebooted. If domain was paused or suspended, on unpause or restore running MySQL server resumes same configuration as at time it was put into suspension, i.e., it does not re-read my.cnf file. 4.2 User names and Passwords ---------------------------- There are two defined users at completion of first boot installation, root and mysql. user can make any furr changes to users and ir passwords that will remain for duration of created virtual machine. 5. Debugging ====================== When problems arise, it is necessary to take a look at VM from to determine
where problem originates. The following helps in first determination of wher it is virtual machine configuration or mysql configuration. Debugging MySQL configuration is fully documented in http://dev.mysql.com/doc/refman/<version> * log into Dom0 environment ssh <server-platform> and examine logs in /var/log/ovs-agent for any problems occuring between Oracle VM Manager and Oracle VM Server. * log into DomU environment for this VM ssh <vm> and examine log /var/log/oraclevm-template.log This contains information about fundamentals of environment startup and can provide useful clues as to why VM is not behaving as expected. 6. Known Issues * Workarounds ============================= a. Oracle VM Manager Console may not be available at first boot due to issues with firewall configuration and or security measures. The user can complete firstboot prompts for Oracle Enterprise Linux and MySQL by connecting a VNC console from any one of Oracle Server Host platforms. The firstboot prompts will wait for first VNC console attached to virtual machine. The VNC Manager will show virtual machine as Running, but ssh and or external connections will not be possible until firstboot scripts have completed. e.g., if 'OVS1' is platform in serverpool newly created virtual machine '99_MySQLVM1' has been started with POWERON. OVS1> xm vncviewer 99_MySQLVM1 will allow firstboot scripts to prompt user for values for: a.1 OS
b. MySQL Configuration c. MySQL secure installation b. VNC may not be available at first boot due to issues with firewall configuration and or security measures. Alternatively, user can, after creating virtual machine from template through Oracle VM Manager use a command line approach to complete first boot dialogue. This is done by performing underlying xm commands on Dom0 of a target server in current server pool on virtual machine configuration directly. # ssh <Dom0> Dom0> cd /OVS/running_pool/<vm-uniqueid> ## perform any manual updates to vm.cfg as necessary ## n startup vm and open a console window Dom0> xm create vm.cfg -c user n follows same first boot dialogue to complete installation of MySQL Server in this VM <vm-uniqueid>. This uses built in vncviewer of xm hypervisor, avoiding any updates to iptables or or bridging mechanisms for peculiarities of your network and security environments. if creating a domain and starting its VNC bridged console hang (an additional issue with VNC and firewall settings), use above workaround to use a separate 'xm vncviewer <domain>' connection to complete first boot script. c. current, some multiple fault scenarios require manual intervention to resume service. specifically, if both Dom-0 hypervisor managing a Dom-U Guest and server pool storage manager (commonly configured on same platform) fail concurrently (hardware power loss), only if server pool storage manager is dual ported, allowing it to recover independently of VM environment, can this double fault recover without manager intervention. If MySQL virtual machine image is stopped through any mechanism, error
or command, or than through Oracle VM Manager, it is automatically restarted. this includes invoking reboot/init 6 from virtual machine command shell or command 'xm destroy <domain>'. as mentioned this high availability response is result of heartbeat between Oracle VM Manager and Oracle VM Server that domain is currently executing. As mentioned, errors which impact Oracle VM Manager concurrently (e.g., loss of underlying shared storage) may prevent this automatic recovery, requiring manual intervention. Oracle VM Manager will determine wher to re-use original Oracle VM Server or a different server in server pool. Migration to an alternate platform causes automatic migration of original virtual machine network configuration, allowing external clients ability to reconnect without reconfiguration as soon as service is re-initialized on an available server in serverpool.