Tuesday, December 27, 2011

Step By Step CloudStack Single Node Installation Tutorial



#### Step By Step CloudStack Installation on REdHat/CentOS ####

# 1.Log in to your OS as root. All the following commands should be run as root.
# 2.Check for a fully qualified hostname
    hostname --fqdn     (otherwise vi /etc/hosts
# 3.Disable SELinux. /etc/selinux/config
     setenforce permissive
# 4. Make sure that the Management Server can reach the Internet.
     ping www.google.com
# 5. (RHEL 6.x) If you do not have a Red Hat Network account, you need to prepare a local Yum repository.
     a. If you are working with a physical host, insert the RHEL 6.0 installation CD. If you are using a VM, attach the RHEL6 ISO.
     b. Mount the CDROM to /media.
     c. Create a repo file at /etc/yum.repos.d/rhel6.repo. In the file, insert the following lines:
     [rhel]
     name=rhel6
     baseurl=file:///media
     enabled=1
     gpgcheck=0

### Install the Management Server (Single Node) ####
1.Install the CloudStack packages. You should have a file in the form of CloudStack-2.2.2.1.tar.gz Untar the file and then run the install.sh script inside it:

# tar xzf CloudStack-2.2.12-1-centos.tar.gz
# cd CloudStack-2.2.12-1-centos
# ./install.sh
#M.the Management Server
> M

#### Single Node Database Install ####
# ./install.sh
D. Install the database server
> D

2.
Edit the MySQL configuration (vi /etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the
[mysqld] section. You can put these lines below the datadir line. The max_connections parameter should be set to 350
multiplied by the number of Management Servers you are deploying. This example assumes 1 Management Server.

innodb_rollback_on_timeout=1
innodb_lock_wait_timeout=600
max_connections=350
log-bin=mysql-bin
binlog-format = 'ROW'

# service mysqld start
# mysql รข€“u root
mysql> SET PASSWORD = PASSWORD('<abcdef123>');
#exit

# cloud-setup-databases cloud:abcdef123@localhost --deploy-as=root:abcdef123
# cloud-setup-management



Reboot

type in Browser   http://localhost:8080/client

Tuesday, December 20, 2011

VMware P2V Converter Best Practices

The best/easiest approach to converting a Windows operating system from a physical machine to a virtual machine is to perform a hot migration with VMware Converter installed locally on the source (physical machine) operating system. Below an overview of the different steps involved in a P2V (Physical to Virtual) conversion. Note that these steps only apply to Windows operating systems.


 BEFORE CONVERSION

  • Confirm that the source server has at least 200 MB free disk space on its system volume. This space is required to operate the disk snapshot features in VMware Converter
  • Confirm that the source machine has at least 364 MB RAM
  • If you have software mirroring, break the mirror (but not the data) since VMware converter does not support software mirrors.
  • Clean-up any temporary files and un-needed data
  • Change all hardware related services to “disabled” startup mode
  • Download the following utilities/scripts and install them to the directory c:\Temp\P2Von the source server. The following files are included:
    • p1-HWPhysical.bat
    • p2-installP2VConverter.bat
    • p3-SystemConfigUtil.bat
    • v1-HWVirtual.bat
    • v2-vmprofile.bat
    • v3-enablehdwacc.bat
    • v3-enablehdwacc.vbs
    • v4-renameNICs.bat
    • v4-renameNICs.vbs
    • v5-setip.bat
    • v6-uninstallP2Vconverter.bat
    • v7-SystemConfigUtil.bat
    • v8-hiddendevices.bat
    • v9-HALupdate.bat
    • PSPCleaner.exe
    • comm.exe
    • libiconv2.dll
    • libintl3.dll
    • devcon.exe
    • VMware vCenter Converter Standalone 4.01 build 161434 (See also http://www.vmware.com/download/converter/)
  • Log on to the source machine (mstsc -v: servername /F -console) with a local administrator account and open a command window
  • Run c:\Temp\P2V\p1-HWPhysical.bat
    •  The script creates a list of all devices of the physical machine (including non-present devices)
  • Install the VMware vCenter Converter Standalone software by executing c:\Temp\P2V\p2-installP2VConverter.bat
  • Run the System Configuration Utility on the source server by executing c:\Temp\P2V\p3-SystemConfigUtil.bat to reduce the number of services and applications running on startup (all software except for all Microsoft Services and VMware Converter Service).
    • On the General tab
      • Select “Selective Startup
      • Uncheck “Load Startup Items”
    • On the Services tab
      • Select “Hide All Microsoft Services”
      • Click “Disable All”
      • Mark the VMware vCenter Converter Agent
      • Mark the VMware vCenter Converter Server
    • Click “Apply”
    • Click “Close”
    • Click “Restart

CONVERSION

  • Log on to the source machine with a local administrator account
  • Start the VMware vCenter Converter Standalone application (A shortcut should be available on the desktop)
  • Select “Convert Machine”
  • Specify Source
    • Select source Type: Powered-on machine
    • Specify the powered-on machine: This local machine
    • Click NEXT
  • Specify Destination
    •  Destination Type
      • Select destination type: VMware Infrastructure virtual machine
      • VMware Infrastructure details
        • Server: type in the IP address of the ESX server you want to convert to (or of your Virtual Center server)
        • User name: type the user name of an administrative account for the above server
        • Password: type the password of the above user name
        • Click NEXT
    • Host/Resource
      • Select the ESX host/group you want to convert to
      • Virtual machine name: type the name of the destination virtual machine (this is normally already set)
      • Datasource: select the datastore in which to place the destination virtual machine
      • Click NEXT
  • View/Edit Options
    • Data to copy
      • Keep the defaults unless you need to re-size the partitions
      • Select “Ignore page file and hibernation file”
    • Devices
      • Select the number of processors: adapt if needed (Remember to revert the HAL after conversion if you are changing from a multi-processor to a uni-processor machine)
      • Disk controller: select SCSI LSI logic for Windows 2003 and beyond
      • Memory for this virtual machine: adapt if needed
    • Network adapters
      • Choose the number of network adapters you need
      • Select the appropriate VLAN
      • Select Connect at power-on
    • Services
      • Go to tab “Destination Services”
      • Change starting mode to “Disabled” for all services you will not need in the virtual machine
    • Advanced options
      • De-select “Synchronize changes that occur to the source during cloning”
      • De-select “Power on target machine”
      • De-select “Install VMware Tools on the imported machine”
      • Select “Remove System Restore checkpoints on destination”
      • Select “Reconfigure destination virtual machine”
    • Click NEXT
  • Ready to Complete
    • Review the summary information
    • Click NEXT

AFTER CONVERSION

  • Shut down the physical machine
  • Use the VI client to log on to your virtual center server or to your ESX server
  • Review and adjust the virtual hardware settings:
    • Adjust the number of NICs, CPUs, RAM, …
    • Remove any unnecessary devices such as serial ports, USB controllers, COM ports, floppy drives, …
  • Start the virtual machine
  • Log on to the virtual machine
  • Run c:\Temp\P2V\v1-HWVirtual.bat
    • Creates a list of all devices that matches the virtual machine
    • Compares the list of all devices of the physical machine (created in the step “before conversion” with the list of all devices that matches the virtual machine (created in the previous step)
    • Removes all phantom hardware
    • Rescans hardware
    • Reboots the  server
  • Change registry key regarding profile problem in VMware (see VMware article) by executing c:\Temp\P2V\v2-vmprofile.bat
  • Enable Video Hardware Acceleration by executing c:\Temp\P2V\v3-enablehdwacc.bat (this command calls the vbs script c:\Temp\P2V\enablehdwacc.vbs)
  • Rename your network connections by executing c:\Temp\P2V\v4-renameNICs.bat (this command calls the vbs script c:\Temp\P2V\renameNICs.vbs)
  • Set IP information on the first network connection by executing c:\Temp\P2V\v5-setip.bat  %1 %2 %3 %4 %5 %6 %7
  • From this step on you should be able to connect to the virtual server via RDP
  • Uninstall VMware vCenter Converter Standalone by executing c:\Temp\P2V\v6-uninstallP2Vconverter.bat
  • If you are converting from HP Proliant hardware you can clean up the HP hardware related drivers, utilities, agents using the HP Proliant Support Pack Cleaner from Guillermo Musumeci. Execute c:\Temp\P2V\PSPCleaner.exe
  • Run the System Configuration Utility on the virtual server by executing c:\Temp\P2V\v7-SystemConfigUtil.bat, select the “normal startup” option and reboot your server
  • Show all hidden devices and uninstall any unused devices by executing c:\Temp\P2V\v8-hiddendevices.bat
    • Select show hidden devices
    • Check if there are still unused devices present and uninstall them manually
  • Update the HAL if you changed from multi to uniprocessor by executing the script c:\Temp\P2V\v9-HALupdate.bat
  • Reboot your server
  • Install VMware Tools
Please also read the VMware vCenter Converter Standalone 4.0 Release Notes at http://www.vmware.com/support/converter/doc/releasenotes_conv40.html

Migrating vCenter Server to a different host machine

Details

This article provides steps for:
  • Moving vCenter Server to a different host machine
  • Relocating the SQL database

Solution

Note: vCenter Server has interdependencies with other services. Care must be taken to not break any of these interdependencies. As with any major change in your infrastructure, good backups are essential in providing smooth, limited downtime changes.
To move your vCenter Server and SQL database:

  1. Shutdown the Virtual Center Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
  2. Take a backup of the SQL database.
  3. If the SQL database is also being moved, create a second instance of your database and use the vendor's tools to migrate the data.
  4. If you are migrating a vCenter Server 4.x database, you must also migrate the ADAM database. For more information, see Manually backing up and restoring the vCenter Server 4.x ADAM instance data (1029864).
  5. Create the appropriate System DSN connections on the new vCenter Server host. For more information, see the Viewing and modifying the database server section of vCenter Server installation fails with ODBC and DNS errors (1003928).
  6. Begin the installation of the vCenter Server software on the new server. If you are installing vCenter Server in a virtual machine, see the vCenter Server and the vSphere Client Hardware Requirements section of the ESXi Installable and vCenter Server Setup Guide and Technical Resource Center for guidelines to deploy vCenter Server in a virtual machine, including sizing, installation, functionality, and configuration of VMware High Availability (HA).
  7. When prompted, select Use existing database, and provide the correct credentials to that database.
  8. When prompted, select to not re-initialize the data, as this erases all your inventory data.
  9. Reboot the machine after the installation completes.

  10. When you first start the vCenter Server Client, it may ask for licenses. Configure the licenses as you had previously in your environment. For more information about licensing for ESX hosts, see the Installation Guide for your version of ESX. For more information about licensing for ESXi hosts, see the Setup Guide for your version of ESXi. You are now able to see the same settings and configuration details.

  11. If the IP address of the new vCenter Server has changed, your ESX hosts must be made aware of that change, otherwise the ESX hosts will continue to send their heartbeats to the original IP address of vCenter Server and appear as Not Responding or Disconnected. For more information, see VirtualCenter Server IP address change caused ESX Servers to show in a Disconnected state (1001493).

  12. Confirm that your SQL Agent rollup jobs are present. Detaching/attaching, importing, or restoring a database to a newer SQL server does not recreate these jobs. If these jobs are not present, there are problems viewing performance data and the database begins increasing in size. For more information, see Updating rollupjobs after the error: Performance data is currently not available for this entity (1004382).
  13. If vCenter Server is moved to another server with a fresh installation, the SSL certificates change and the ESX hosts show as disconnected within vSphere Client connected to vCenter Server. Right-click the disconnected hosts, click Connect, provide the root login credentials, and follow the prompts.
Note: If you are using custom or CA signed certificates, see Replacing vCenter Server Certificates.

Additional Information

If you are moving your database, you must follow all recommendations and instructions provided by the third party database vendor. If necessary, consult the appropriate documentation or engage third party vendor support.
If you are using VMware Consolidated Backup, on the VCB server you will need to edit the file %PROGRAMFILES\<VCB directory>\config\config.js and change the host line to the new IP or DNS name of the vCenter Server using a text editor to restore communications. 
For information about Microsoft's Copy Database Wizard, see the Microsoft Knowledge Base article 274463.
For information on the osql utility, see the Microsoft Knowledge Base article 325003.

For information on the vCenter data migration tool, see the vSphere Upgrade Guide.
If you are using customer SSL certificates for Update Manager, see Replacing SSL certificates for VMware vCenter Update Manager (1023011).

Sunday, December 18, 2011

What’s New in VMware vSphere 5?

• vSphere Storage API Program—Take advantage of extensions to the Array Integration API that support thin provisioning. Leverage the new Storage Awareness and Discovery API to interface with arrays when using the new vSphere Storage DRS and Profile-Driven Storage features.

Network
• vSphere Network I/O Control—New per–virtual-machine controls allow more-granular SLA enforcement.
• vSphere Distributed Switch—Improves visibility of virtual machine traffic through NetFlow and enhances monitoring and troubleshooting through Switched Port Analyzer (SPAN) and Link Layer Discovery Protocol (LLDP) support. Application Services

(Availability, Security, and Scalability)


Availability
• vSphere High Availability—New architecture enables superior guarantees, simplified setup and configuration, and expanded scalability.
• vSphere vMotion—Migration of virtual machines over higher latency network links is now supported.

Security
• ESXi Firewall—New service-oriented and stateless firewall engine restricts access to specific services by IP address or subnet. This is particularly useful for third-party components that require network access.


Scalability
• Larger virtual machines—Virtual machines can now grow four times larger than in any previous release to support even the largest applications. Virtual machines can now have up to 32 virtual CPUs and 1TB of RAM.

Management Services

Core Management
• vSphere Web Client—Access vSphere from any Web browser anywhere in the world.
• VMware vCenter Server Appliance—Run vCenter Server as a Linux-based virtual appliance.

VMware® vSphere® is the industry-leading virtualization platform for building cloud infrastructures. It enables users to run business-critical applications with confidence and respond to business needs faster.
vSphere accelerates the shift to cloud computing for existing data centers and underpins compatible public cloud offerings, forming the foundation for the industry’s only hybrid cloud model. Infrastructure Services
(Compute, Storage, and Network)


Compute


• vSphere ESXi™ convergence—vSphere 5 is converging on the ESXi hypervisor architecture. ESXi—the gold standard in hypervisors— enables vSphere users to leverage a thinner architecture, a more secure footprint, and a streamlined patching and setup model.

• vSphere Auto Deploy—Auto Deploy is a new deployment and patching model for new vSphere hosts running the ESXi hypervisor. Deploy more vSphere hosts in minutes and update them more efficiently than ever before.

• New virtual-machine format (Version 8)—The new virtual machine format in vSphere 5 has several new features, including support for
-3D graphics for Windows Aero
-USB 3.0 devices

• Support for Apple products—vSphere 5 supports Apple Xserve servers running OS X Server 10.6 (Snow Leopard) as a guest operating system.

Storage
• vSphere Storage DRS—Improve management and enable more-efficient use of storage resources through grouping, placement and balancing.

• Profile-Driven Storage—Identify the appropriate storage to use for a given virtual machine depending on service level. The result is a streamlined approach to selecting the correct storage and ensuring its delivery.
• vSphere File System—Leverage enhanced scalability and performance through a non-disruptive upgrade to the platform’s latest clustered file system version.

• vSphere Storage I/O Control—Improve management and enforcement of service-level agreements (SLAs) through extension of limits and shares in Network File System (NFS) datastores

Hope you learned and enjoyed, it is the official document from VMware.

Thanks