{"id":12013,"date":"2019-03-21T02:53:12","date_gmt":"2019-03-21T02:53:12","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=12013"},"modified":"2019-03-21T02:53:12","modified_gmt":"2019-03-21T02:53:12","slug":"how-to-install-redhat-enterprise-virtualization-rhev-3-5","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/03\/21\/how-to-install-redhat-enterprise-virtualization-rhev-3-5\/","title":{"rendered":"How to Install RedHat Enterprise Virtualization (RHEV) 3.5"},"content":{"rendered":"

In this series we are discussing\u00a0RHEV3.5<\/strong>\u00a0administration topics. RHEV is the RedHat Enterprise Virtualization solution, which is based on\u00a0oVirt<\/strong>\u00a0project [open-source Virtualization project].<\/p>\n

Red Hat Enterprise Virtualization is a complete virtualization management solution for virtualized servers and desktops.<\/p>\n

This series will discuss (How to) administration topics including the RHCVA exam objectives.<\/p>\n

Part 1<\/b>:\u00a0How to Install RedHat Enterprise Virtualization (RHEV) 3.5<\/b><\/div>\n
Part 2<\/b>:\u00a0How to Deploy RedHat Enterprise Virtualization Hypervisor (RHEV-H)<\/a><\/div>\n
Part 3<\/b>:\u00a0How to Deploy Data-Centers with Cluster and Add ISCSI Storage in RHEV Environment<\/a><\/div>\n
Part 4<\/b>:\u00a0How to Deploy \u2018Linux\u2019 and \u2018Windows\u2019 Virtual Machines under ISO Domains in RHEV<\/a><\/div>\n
Part 5<\/b>:\u00a0RHEV Clustering and RHEL Hypervisors Installation<\/a><\/div>\n
Part 6<\/b>:\u00a0How to Manage RedHat Enterprise Virtualization (RHEV) Virtual Machines Operations and Tasks<\/a><\/div>\n
Part 7<\/b>:\u00a0How to Manage RedHat Enterprise Virtualization Environment Users and Groups<\/b><\/div>\n

In our first article, we are discussing\u00a0RHEV<\/strong>\u00a0environment and basic deployment.\u00a0RHEV<\/strong>\u00a0consists of two main components, like Hypervisor and Management system.<\/p>\n

RHEV-H<\/strong>\u00a0is the Hypervisor of\u00a0RHEV<\/strong>\u00a0platform, it is a bare-metal hypervisor which used to host virtual machines. It\u2019s also based on KVM and RHEL.<\/p>\n

RHEVM<\/strong>\u00a0is the management system of the environment which controls the environment hypervisors. It\u2019s also used to create, migrate, modify and control virtual machines hosted by hypervisrors and a lot of other many tasks will be discussed later.<\/p>\n

RHEV3.5 Features<\/h4>\n
    \n
  1. Open source solution based on the Red Hat Enterprise Linux kernel with the Kernel-based Virtual Machine (KVM) hypervisor technology.<\/li>\n
  2. Supported limit of up to 160 logical CPUs and 4TB per host and up to 160 vCPU and 4TB vRAM per virtual machine.<\/li>\n
  3. OpenStack integration.<\/li>\n
  4. Supported Daily missions like offline migration, High availability, Clustering, etc..<\/li>\n<\/ol>\n

    For more features and details read:\u00a0RedHat Enterprise Virtualization Guide<\/a><\/p>\n

    Prerequisites<\/h4>\n

    During our series, we will work on two nodes \u2018hypervisors\u2019 and \u2018hosts\u2019 with one manager and one iscsi storage node. In the future we will add one IPA and DNS server to our environment.<\/p>\n

    For deployment scenarios we have two:<\/p>\n

      \n
    1. Physical Deployment \u2013 Real environment, so you will need at least three or physical machines.<\/li>\n
    2. Virtual deployment \u2013 Test labs\/environment, so you will need one physical machine with high resources e.g. i3 or i5 processor with 8G or 12G ram. Additional to another virtualization software e.g. Vmware workstation.<\/li>\n<\/ol>\n

      In this series we are working on the second scenario:<\/p>\n

      Physical Host OS<\/strong> : Fedora 21 x86_64 with kernel 3.18.9-200\r\nRHEV-M  machine OS<\/strong> : RHEL6.6 x86_64\r\nRHEV-H  machines hypervisor<\/strong> : RHEV-H 6.6 \r\nVirtualization software<\/strong> : Vmware workstation 11\r\nVirtual Network interface<\/strong> : vmnet3\r\nNetwork<\/strong> : 11.0.0.0\/24\r\nPhysical Host IP<\/strong> : 11.0.0.1\r\nRHEV-M machine<\/strong> : 11.0.0.3\r\n<\/pre>\n
      \n
      \"RedHat<\/a><\/p>\n
      RedHat Enterprise Virtualization Diagram<\/p>\n<\/div>\n
      In the future articles, we will add additional components like storage nodes and IPA server so make your environment scalable as possible.<\/p>\n
      For\u00a0RHEV-M<\/strong>\u00a0machine take care about this prerequisites:<\/p>\n
        \n
      1. RHEL\/CentOS6.6 x86_64 new minimal installation [Clean installation].<\/li>\n
      2. Make sure your system is up-to-date.<\/li>\n
      3. Static IP for your network configuration.<\/li>\n
      4. Your host-name something like machine.domain.com.<\/li>\n
      5. Update your local \/etc\/hosts file with host-name and IP [Make sure the host-name is resolvable].<\/li>\n
      6. The minimum requirement is 4G for memory and 25GB for hard disk.<\/li>\n
      7. Mozilla Firefox 37 is recommended browser to access WUI.<\/li>\n<\/ol>\n
        Installation of RedHat Enterprise Virtualization Manager 3.5<\/h3>\n
        1.<\/strong>\u00a0To get access for\u00a0RHEV<\/strong>\u00a0packages and updates, you should get a free 60-day trial subscription from the redhat official site using co-prorate mail from here:<\/p>\n
          \n
        1. RedHat Enterprise Virtualization 60-Day Evaluation<\/a><\/li>\n<\/ol>\n
          Note<\/strong>: After\u00a060-day<\/strong>\u00a0your environment will work fine, but without availability to update your system if there is new updates.<\/p>\n
          2.<\/strong>\u00a0Then register your machine to redhat channels. Steps explained here.<\/p>\n
            \n
          1. Register RHEV Machine to RHN<\/a><\/li>\n<\/ol>\n
            3.<\/strong>\u00a0Lets install\u00a0rhevm<\/strong>\u00a0package and its dependencies using yum command.<\/p>\n
            [root@rhevm ~]# yum install rhevm\r\n<\/pre>\n
            4.<\/strong>\u00a0Now its time to configure\u00a0rhevm<\/strong>\u00a0by runing \u201cengine-setup<\/strong>\u201d command, which will check the status of\u00a0rhevm<\/strong>\u00a0and any available updates with asking a series of questions.<\/p>\n
            We could summarize the questions in main sections :<\/p>\n
              \n
            1. Product Options<\/li>\n
            2. Packages<\/li>\n
            3. Network Configuration<\/li>\n
            4. DataBase Configuration<\/li>\n
            5. oVirt Engine Configuration<\/li>\n
            6. PKI Configuration<\/li>\n
            7. Apache Configuration<\/li>\n
            8. System Configuration<\/li>\n
            9. Configuration Preview<\/li>\n<\/ol>\n
              Hint<\/strong>: Suggested configuration defaults are provided in square brackets; if the suggested value is acceptable for a given step, press\u00a0Enter<\/strong>\u00a0to accept that value.<\/p>\n
              To run the command:<\/p>\n
              [root@rhevm ~]# engine-setup\r\n<\/pre>\n
              Product Options<\/h5>\n
              First thing you will be asked about is to install and configure the engine on the same host.\u00a0For our tutorial, keep the default value (Yes<\/strong>). If you want\u00a0WebSocket Proxy<\/strong>\u00a0to be configured on your machine, keep the default value (yes<\/strong>).<\/p>\n
              \n
              \"Product<\/a><\/p>\n
              Product Options<\/p>\n<\/div>\n
              Packages<\/h5>\n
              Script will check any updates are available for the packages linked to the\u00a0Manager<\/strong>. No user input is required at this stage.<\/p>\n
              \n
              \"Package<\/a><\/p>\n
              Package Updates<\/p>\n<\/div>\n
              Network Configuration<\/h5>\n
              Let script configures your\u00a0iptables<\/strong>\u00a0firewall automatically. For now we won\u2019t use\u00a0DNS<\/strong>, so make sure that your host-name is fully qualified name by updating\u00a0\/etc\/hosts<\/strong>\u00a0as we did previously.<\/p>\n
              \n
              \"Network<\/a><\/p>\n
              Network Configuration<\/p>\n<\/div>\n
              Database Configuration<\/h5>\n
              The default database for\u00a0RHEV3.5<\/strong>\u00a0is\u00a0PostgreSQL<\/strong>. You have the option to configure it on the same machine or remotely. For our tutorial will use the local one and let script to configure it automatically.<\/p>\n
              \n
              \"Database<\/a><\/p>\n
              Database Configuration<\/p>\n<\/div>\n
              Ovirt Configuration<\/h5>\n
              In this section you will provide the\u00a0admin<\/strong>\u00a0password and the application mode for you environment.<\/p>\n
              \n
              \"Ovirt<\/a><\/p>\n
              Ovirt Configuration<\/p>\n<\/div>\n
              PKI Configuration<\/h5>\n
              RHEVM<\/strong>\u00a0uses certificates to communicate securely with its hosts. You provide the organization name for the certificate.<\/p>\n
              \n
              \"PKI<\/a><\/p>\n
              PKI Configuration<\/p>\n<\/div>\n
              Apache Configuration<\/h5>\n
              For\u00a0RHEVM<\/strong>\u00a0web user interface, manager needs Apache web-server to be installed and configured, lets make setup configure it automatically.<\/p>\n
              \n
              \"Apache<\/a><\/p>\n
              Apache Configuration<\/p>\n<\/div>\n
              System configuration<\/h5>\n
              RHEV<\/strong>\u00a0environment has ISO library which you could store many OS ISO in. This ISO lib called also ISO domain, this domain is a network shared path, usually it shared by NFS. This domain\/path will be on the same RHEVM machine so you could create it manually or let script configures it automatically.<\/p>\n
              \n
              \"System<\/a><\/p>\n
              System Configuration<\/p>\n<\/div>\n
              Configuration Review<\/h5>\n
              In this section you will review all previous configuration and confirm if everything is OK.<\/p>\n
              \n
              \"Configuration<\/a><\/p>\n
              Configuration Review<\/p>\n<\/div>\n
              Summery<\/h5>\n
              This is the last stage which show additional information about how to access the admin panel and starting the services.<\/p>\n
              \n
              \"Summary\"<\/a><\/p>\n
              Summary<\/p>\n<\/div>\n
              Hint<\/strong>: Warning may appears, if the memory used is low than the minimum requirement. For test-environment it\u2019s not very important just keep on.<\/p>\n
              To access RHEVM web user interface:<\/p>\n
              http:\/\/$your-ip\/ovirt-engine\r\n<\/pre>\n
              \n
              \"RedHat<\/a><\/p>\n
              RedHat Enterprise Virtualization Manager<\/p>\n<\/div>\n
              Then select\u00a0Administrator Portal<\/strong>\u00a0and provide your credentials\u00a0Username:admin<\/b>\u00a0and the password you entered during the installation. Click\u00a0Login<\/strong>.<\/p>\n
              \n
              \"RedHat<\/a><\/p>\n
              RedHat Enterprise Virtualization Administrator Portal<\/p>\n<\/div>\n
              This is the administration portal which will be discussed later. You will notice that hosts tab is empty as we didn\u2019t add any\u00a0host\/hypervisor<\/strong>\u00a0to our environment yet.<\/p>\n
              \n
              \"Administrator<\/a><\/p>\n
              Administrator Dashboard<\/p>\n<\/div>\n
              Conclusion<\/h3>\n
              This is first article in our\u00a0RHEV3.5<\/strong>\u00a0administration series. We just introduce the solution, its features and its main components then we installed\u00a0RHEV-M<\/strong>\u00a0for our\u00a0RHEV<\/strong>\u00a0environment. In next article we will discuses\u00a0RHEV-H<\/strong>installation and adding them to\u00a0RHEV<\/strong>\u00a0environment under\u00a0RHEVM<\/strong>\u00a0management.<\/p>\n
              How to Deploy RedHat Enterprise Virtualization Hypervisor (RHEV-H) \u2013 Part 2<\/h1>\n
              In this second part, we are discussing the deployment of\u00a0RHEVH<\/strong>\u00a0or the\u00a0Hypervisor<\/strong>\u00a0nodes of our environment with some tips and tricks for your virtual lab or virtual environment.<\/p>\n
              \n
              \"Deploy<\/a><\/p>\n
              Deploy RedHat Enterprise Virtualization Hypervisor \u2013 Part 2<\/p>\n<\/div>\n
              As we discussed before, in our scenario which including two hyprvisors with separate RHEVM machine. The reason to deploy the manager in separate machine is more reliable than deploying it on one of the environment hosts\/nodes. If you try to deploy it (as a virtual machine\/appliance) on one of environment nodes\/hosts and for any reason this node becomes down, the RHEVM machine\/appliance will become down due to the node failure, on other words, we wont RHEVM depends on environment nodes so we will deploy it over separate machine which doesn\u2019t belong to DataCenter\/Environment nodes.<\/p>\n
              Deploying RedHat Enterprise Virtualization Hypervisor<\/h3>\n
              1.<\/strong>\u00a0For our virtual environment, you should now have this network virtual interface \u201cvmnet3<\/strong>\u201d with this specification at\u00a0VMware workstation 11<\/a>.<\/p>\n
              \n
              \"Virtual<\/a><\/p>\n
              Virtual Network Editor<\/p>\n<\/div>\n
              2<\/strong>. Lets deploy our nodes, you will need to create normal virtual machine with some customization as presented in screen-shots.<\/p>\n
              \n
              \"Create<\/a><\/p>\n
              Create New Machine<\/p>\n<\/div>\n
              \n
              \"Select<\/a><\/p>\n
              Select Hardware Compatibility<\/p>\n<\/div>\n
              \n
              \"Select<\/a><\/p>\n
              Select Install Source<\/p>\n
               <\/p>\n<\/div>\n
              3.<\/strong>\u00a0Make sure about OS type in next step : Other,\u00a0Other64-bit<\/strong>.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Guest OS Type<\/p>\n<\/div>\n
              4.<\/strong>\u00a0Select your suitable name and path for your virtual machine.<\/p>\n
              \n
              \"Set<\/a><\/p>\n
              Set Name of OS<\/p>\n<\/div>\n
              5.<\/strong>\u00a0If you have more resources, increase the number of cores\/processors on demand.<\/p>\n
              \n
              \"Processor<\/a><\/p>\n
              Processor Configuration<\/p>\n<\/div>\n
              6.<\/strong>\u00a0For memory, don\u2019t choose less than\u00a02G<\/strong>, we won\u2019t to suffer later.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select VM Memory<\/p>\n<\/div>\n
              7.<\/strong>\u00a0For now, select\u00a0NAT<\/strong>\u00a0connection, it isn\u2019t make different as we will change it later.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Network Type<\/p>\n<\/div>\n
              8.<\/strong>\u00a0It is very important point to select SAS controller.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select I\/O Controller Types<\/p>\n<\/div>\n
              9.<\/strong>\u00a0Choose SCSI Disk Type.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Disk Type<\/p>\n<\/div>\n
              10.<\/strong>\u00a0We will work with shared storage later, so\u00a020 G<\/strong>\u00a0is more than suitable.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Storage Capacity<\/p>\n<\/div>\n
              \n
              \"Select<\/a><\/p>\n
              Select Storage Drive<\/p>\n<\/div>\n
              11.<\/strong>\u00a0Before finishing, lets make some additional modification\u2026click\u00a0Customize Hardware<\/strong>.<\/p>\n
              \n
              \"Customize<\/a><\/p>\n
              Customize Hardware<\/p>\n<\/div>\n
              First modification will be for\u00a0Processor<\/strong>\u00a0as we will check the two options to enable virtualization features in our Processor.<\/p>\n
              \n
              \"Enable<\/a><\/p>\n
              Enable Virtualization<\/p>\n<\/div>\n
              Second modification will be for\u00a0Network Configuration<\/strong>\u2026 change it to be\u00a0Custom<\/strong>\u00a0and insert the path of \u201cvmnet3<\/strong>\u201d.<\/p>\n
              \n
              \"Network<\/a><\/p>\n
              Network Configuration<\/p>\n<\/div>\n
              Last modification will be our\u00a0Hypervisor-ISO<\/strong>\u00a0path, then close, review and finishing.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Hypervisor ISO Path<\/p>\n<\/div>\n
              \n
              \"Virtual<\/a><\/p>\n
              Virtual Machine Summary<\/p>\n<\/div>\n
              12.<\/strong>\u00a0Before starting your virtual machine, we should make some manual modification in\u00a0vm configuration<\/strong>\u00a0file. Go to the path of you virtual machine, you will find file with \u201cvmx<\/strong>\u201d extension.<\/p>\n
              \n
              \"Virtual<\/a><\/p>\n
              Virtual Machine Configuration<\/p>\n<\/div>\n
              13.<\/strong>\u00a0Open it with your preferred editor and add those two option at the end of file.<\/p>\n
              vcpu.hotadd = \"FALSE\"\r\napic.xapic.enable = \"FALSE\"\r\n<\/pre>\n
              \n
              \"Configure<\/a><\/p>\n
              Configure VM<\/p>\n<\/div>\n
              Then save and go back to our virtual machine as its time to start it.<\/p>\n
              \n
              \"Start<\/a><\/p>\n
              Start VM<\/p>\n<\/div>\n
              Press any button, DON\u2019T continue with Automatic boot. This list will appear\u2026<\/p>\n
              \n
              \"VM<\/a><\/p>\n
              VM Boot Menu<\/p>\n<\/div>\n
              Make sure you selected the 1st line the press \u201ctab<\/strong>\u201d to edit some options.<\/p>\n
              \n
              \"Change<\/a><\/p>\n
              Change Boot Options<\/p>\n<\/div>\n
              Remove \u201cquiet<\/strong>\u201d from booting options and Press enter to continue.<\/p>\n
              \n
              \"Remove<\/a><\/p>\n
              Remove Quiet Option<\/p>\n<\/div>\n
              \n
              \"VM<\/a><\/p>\n
              VM Booting<\/p>\n
              14.<\/strong>\u00a0In the start console make sure about\u00a0INFO<\/strong>\u00a0which talking Virtualzation H\/W was detected and enabled. Don\u2019t continue with anything else..<\/p>\n
              \n
              \"Install<\/a><\/p>\n
              Install Hypervisor<\/p>\n<\/div>\n
              15.<\/strong>\u00a0Check you preferred language and continue with your local storage.<\/p>\n
              \n
              \"Select<\/a><\/p>\n
              Select Language<\/p>\n<\/div>\n
              \n
              \"Select<\/a><\/p>\n
              Select Disk Storage<\/p>\n<\/div>\n
              Hint<\/strong>: Use arrows keys to change and space to select and deselect options.<\/p>\n
              \n
              \"Selected<\/a><\/p>\n
              Selected Disk Storage<\/p>\n<\/div>\n
              16.<\/strong>\u00a0There is no need to change the default values of storage volumes and system portions, so keep it as defaults and make sure to review and confirm settings.<\/p>\n
              \n
              \"Storage<\/a><\/p>\n
              Storage Volumes<\/p>\n<\/div>\n
              \n
              \"Confirm<\/a><\/p>\n
              Confirm Disk Selection<\/p>\n
              17.<\/strong>\u00a0For security reasons, root account isn\u2019t available directly by-default as you should login with admin account, which have full privilege \u2013 then switch to root account. So take care about admin password as its equivalent to root password in importance.<\/p>\n
              Mainly, root account be needed for maintenance and troubleshoot proposals. Any configuration or customization done be admin account only.<\/p>\n
              \n
              \"Enter<\/a><\/p>\n
              Enter Login Details<\/p>\n<\/div>\n
              Wait minutes until installation finishes and then \u201cReboot<\/strong>\u201d the system.<\/p>\n
              \n
              \"Hypervisor<\/a><\/p>\n
              Hypervisor Installation<\/p>\n<\/div>\n
              \n
              \"RHEV<\/a><\/p>\n
              RHEV H Installation<\/p>\n<\/div>\n
              18.<\/strong>\u00a0After rebooting, provide admin credentials to login.<\/p>\n
              \n
              \"Root<\/a><\/p>\n
              Root Login<\/p>\n<\/div>\n
              This is the default console to manage the basic configuration of your hypervisor.<\/p>\n
              \n
              \"RHEV<\/a><\/p>\n
              RHEV H Console<\/p>\n<\/div>\n
              Hint<\/strong>: Review the status of your hypervisor and make sure it looks like the above.<\/p>\n
              19.<\/strong>\u00a0Now, we will make three major, basic and important configuration.<\/p>\n
                \n
              1. Network<\/li>\n
              2. Security<\/li>\n
              3. RHEV-M<\/li>\n<\/ol>\n
                Network:<\/h4>\n
                Select\u00a0Network<\/strong>\u00a0tab [using arrows].<\/p>\n
                \n
                \"Network<\/a><\/p>\n
                Network<\/p>\n<\/div>\n
                Change you hypervisor hostname and add DNS IP address.<\/p>\n
                \n
                \"Set<\/a><\/p>\n
                Set Hostname and DNS<\/p>\n<\/div>\n
                Hint<\/strong>: For our VMware workstation environment, we will provide the gateway IP address.<\/p>\n
                Next, configure Static IP for your NIC.<\/p>\n
                \n
                \"Configure<\/a><\/p>\n
                Configure IP Address<\/p>\n<\/div>\n
                Then save and close \u2018wait few minuets<\/strong>\u2018\u2026<\/p>\n
                \n
                \"Network<\/a><\/p>\n
                Network Interface Configuration<\/p>\n<\/div>\n
                Test your connectivity with internet using\u00a0ping<\/strong>.<\/p>\n
                \n
                \"Test<\/a><\/p>\n
                Test Network Connectivity<\/p>\n<\/div>\n
                Important<\/strong>: Check the connectivity between hypervisors nodes and manager machines using\u00a0ping<\/strong>.<\/p>\n
                Security<\/h4>\n
                Select\u00a0security<\/strong>\u00a0tab. By default ssh is disabled enable it [by check it using \u2018space<\/strong>\u2018] and then save and close.<\/p>\n
                \n
                \"Enable<\/a><\/p>\n
                Enable SSH<\/p>\n<\/div>\n
                \n
                \"Security<\/a><\/p>\n
                Security Configuration<\/p>\n<\/div>\n
                RHEV-M<\/h4>\n
                The last and important thing is establish connection between\u00a0hypervisors<\/strong>\u00a0and\u00a0manager<\/strong>\u00a0then registration them under the manager.<\/p>\n
                \n
                \"RHEV-M<\/a><\/p>\n
                RHEV-M Configuration<\/p>\n<\/div>\n
                Due to SSL connection you should compare SSL Finger print with Internal CA from RHEVM.<\/p>\n
                \n
                \"Check<\/a><\/p>\n
                Check RHEV-M Fingerprint<\/p>\n<\/div>\n
                Hint<\/strong>: If you reviewed it with\u00a0Install RedHat Enterprise Virtualization \u2013 Part 1<\/a>\u00a0article, we will find them identical.<\/p>\n
                Then accept and close the tab, next go to status tab and review everything.<\/p>\n
                \n
                \"Configuring<\/a><\/p>\n
                Configuring RHEV-M<\/p>\n<\/div>\n
                \n
                \"RHEV-H<\/a><\/p>\n
                RHEV-H Summary<\/p>\n<\/div>\n
                20.<\/strong>\u00a0Final check, using\u00a0RHEVM<\/strong>\u00a0web interface. If you reviewed previous article, you will find there is no hosts under hosts tab.<\/p>\n
                \n
                \"RHEV<\/a><\/p>\n
                RHEV Interface<\/p>\n<\/div>\n
                You will find node is registered successfully and ready for admin approval to be included under data-center.<\/p>\n
                Conclusion<\/h3>\n
                We\u2019ve discussed how to deploy our environment hypervisors and connect them to manager, in our next upcoming article we will see how to deploy to general datacenter with clusters using shared storage. Last thing, If you working over real environment, skip VMware preparation section.<\/p>\n
                Reference Links<\/strong>:<\/p>\n
                  \n
                1. Red Hat Enterprise Virtualization Installation Guide<\/a><\/li>\n
                2. Red Hat Enterprise Virtualization Administration Guide<\/a><\/li>\n<\/ol>\n
                  How to Deploy Data-Centers with Cluster and Add ISCSI Storage in RHEV Environment<\/h1>\n
                  In this part, we are going to discuss how to deploy data-center with one cluster which contains our two hosts in the RHEV environment. Both of two hosts connected to shared storage, additional to previous preparation, we will add another\u00a0CentOS6.6<\/strong>\u00a0virtual machine acts as storage node.<\/p>\n
                  \n
                  \"Create<\/a><\/p>\n
                  Create Data-Centers and Cluster in RHEV \u2013 Part 3<\/p>\n<\/div>\n
                  Data Center is a terminology describes the\u00a0RHEV<\/strong>\u00a0environment resources such as logical, network and storage resources.<\/p>\n
                  Data Center<\/strong>\u00a0consists of Clusters which include a set of node or nodes, which host virtual machines and its related snapshots, templates and pools. Storage domains are mandatory attached to Data Center to make it working effectively in enterprise environments. Multiple data centers in the same infrastructure could be managed separately by the same RHEVM portal.<\/p>\n
                  \n
                  \"Data<\/a><\/p>\n
                  Data Center Diagram<\/p>\n<\/div>\n
                  Red Hat Enterprise Virtualization uses a centralized storage system for virtual machine disk images, ISO files and snapshots.<\/p>\n
                  Storage networking can be implemented using:<\/p>\n
                    \n
                  1. Network File System (NFS)<\/li>\n
                  2. GlusterFS<\/li>\n
                  3. Internet Small Computer System Interface (iSCSI)<\/li>\n
                  4. Local storage attached directly to the virtualization hosts<\/li>\n
                  5. Fibre Channel Protocol (FCP)<\/li>\n<\/ol>\n
                    Setting up storage is a prerequisite for a new data center because a data center cannot be initialized unless storage domains are attached and activated. For clustering features and enterprise deployment needs, its recommended to deploy shared-storage in your environment instead of host-based local storage.<\/p>\n
                    In general, storage node will be accessible by Data Center hosts to create, store and snapshot virtual machines beside other important tasks.<\/p>\n
                    Red Hat Enterprise Virtualization platform has three types of storage domains:<\/p>\n
                      \n
                    1. Data Domain: used to hold the virtual hard disks and OVF files of all the virtual machines and templates in a data center. In addition, snapshots of the virtual machines are also stored in the data domain. You must attach a data domain to a data center before you can attach domains of other types to it.<\/li>\n
                    2. ISO Domain: used to store ISO files which are needed to install and boot operating systems and applications for the virtual machines.<\/li>\n
                    3. Export Domain: temporary storage repositories that are used to copy and move images between data centers in Red Hat Enterprise Virtualization environments.<\/li>\n<\/ol>\n
                      In this part we are going to deploy Data Domain with following storage node specifications for our tutorial:<\/p>\n
                      IP Address : 11.0.0.6\r\nHostname : storage.mydomain.org\r\nVirtual Network : vmnet3\r\nOS : CentOS6.6 x86_64 [Minimal Installation]\r\nRAM : 512M\r\nNumber of Hard disks : 2 Disk  [1st: 10G for the entire system,  2nd : 50G to be shared by ISCSI]\r\nType of shared storage : ISCSI \r\n<\/pre>\n
                      Note: You could change the above specs as per your environment needs.<\/p>\n
                      Step 1: Creating New Data Center with Cluster of Two Nodes<\/h3>\n
                      By default,\u00a0RHEVM<\/strong>\u00a0create default data-center contains one empty cluster with name\u00a0Default<\/strong>\u00a0in our RHEV environment. We will create new one and add the two (Pending Approval) Hosts under it.<\/p>\n
                      Check the current data-centers, by selecting\u00a0Data centers<\/strong>\u00a0tab.<\/p>\n
                      \n
                      \"Data<\/a><\/p>\n
                      Data Centers<\/p>\n<\/div>\n
                      1.<\/strong>\u00a0Click on\u00a0New<\/strong>\u00a0to add new\u00a0Data center<\/strong>\u00a0to your environment. Wizard window like this will appear, Fill it as shown:<\/p>\n
                      \n
                      \"Create<\/a><\/p>\n
                      Create New Data Center<\/p>\n<\/div>\n
                      2.<\/strong>\u00a0You will be asked to create new cluster as apart of \u201cData-Center1<\/strong>\u201d. Click (Configure Cluster<\/strong>) and fill it as shown..<\/p>\n
                      \n
                      \"Configure<\/a><\/p>\n
                      Configure Cluster<\/p>\n<\/div>\n
                      \n
                      \"Configure<\/a><\/p>\n
                      Configure Cluster for Data Center<\/p>\n<\/div>\n
                      Important<\/strong>: Make sure that\u00a0CPU Type<\/strong>\u00a0is correct one and ALL nodes have the same CPU Type. You can modify any setting as per your environment needs. Some settings will be discussed in details later..<\/p>\n
                      3.<\/strong>\u00a0Click (Configure Later<\/strong>) to exit the wizard.<\/p>\n
                      \n
                      \"Configure<\/a><\/p>\n
                      Configure Cluster Later<\/p>\n<\/div>\n
                      4.<\/strong>\u00a0Switch to\u00a0Hosts<\/strong>\u00a0tab to approve and add (Pending Approval<\/strong>) node to our environment. Select your first node and click\u00a0Approve<\/strong>.<\/p>\n
                      \n
                      \"Add<\/a><\/p>\n
                      Add Pending Node<\/p>\n<\/div>\n
                      5.<\/strong>\u00a0Fill the appeared wizard with the new created \u201cData-Center1<\/strong>\u201d and its first cluster as shown:<\/p>\n
                      \n
                      \"Configure<\/a><\/p>\n
                      Configure Data Center and Cluster<\/p>\n<\/div>\n
                      Important<\/strong>: You may see warning about\u00a0Power Management<\/strong>\u00a0just skip it by clicking\u00a0OK<\/strong>, repeat the same steps with the second node..<\/p>\n
                      If everything goes well, status should be changed from \u201cPending Approval<\/strong>\u201d to (Installing<\/strong>).<\/p>\n
                      \n
                      \"Installing<\/a><\/p>\n
                      Installing Data Centers<\/p>\n<\/div>\n
                      Wait another few minutes, status should be changed from \u201cInstalling<\/strong>\u201d to (Up<\/strong>).<\/p>\n
                      \n
                      \"Data<\/a><\/p>\n
                      Data Centers Up<\/p>\n<\/div>\n
                      Also you could check which cluster and data center are assigned to the two node..<\/p>\n
                      Step 2: Prepare ISCSI Storage for RHEV Environment<\/h3>\n
                      Lets switch to storage node to configure\u00a0ISCSI<\/strong>\u00a0storage.<\/p>\n
                      6.<\/strong>\u00a0First you need to install some needed packages to configure ISCSI target.<\/p>\n
                      [root@storage ~]# yum install scsi-target-utils\r\n<\/pre>\n
                      7.<\/strong>\u00a0For this tutorial we use\u00a0sdb<\/strong>\u00a0as our backing device, so we should add the below section to the\u00a0configuration<\/strong>file\u00a0targets.conf<\/strong>.<\/p>\n
                      [root@storage ~]# vim \/etc\/tgt\/targets.conf\r\n<\/pre>\n
                      Add the following lines to this file, save and close it.<\/p>\n
                      <target iqn.2015-07.org.mydomain:server.target1>\r\n    backing-store \/dev\/sdb\r\n<\/target>\r\n<\/pre>\n
                      Important<\/strong>: Make sure that\u00a0sdb<\/strong>\u00a0is a raw device.<\/center>8.<\/strong>\u00a0Start\u00a0tgtd<\/strong>\u00a0service and make up with system booting.<\/p>\n
                      [root@storage ~]# service tgtd start\r\n[root@storage ~]# chkconfig tgtd on\r\n<\/pre>\n
                      Important<\/strong>: Make sure that ports\u00a0860<\/strong>\u00a0and\u00a03260<\/strong>\u00a0are opened in firewall or flush it (Not recommended<\/strong>).<\/p>\n
                      Fore more details about\u00a0ISCSI<\/strong>\u00a0configuration and deployment, check\u00a0tecmint\u2019s iscsi<\/a>\u00a0series.<\/p>\n
                      Step 3: Add ISCSI storage Node to RHEV Environment<\/h3>\n
                      The\u00a0Red Hat Enterprise Virtualization<\/strong>\u00a0platform enables you to assign and manage storage using the\u00a0Administration Portal\u2019s Storage<\/strong>\u00a0tab. The Storage results list displays all the storage domains, and the details pane shows general information about the domain.<\/p>\n
                      9.<\/strong>\u00a0Select\u00a0Data-Center1<\/strong>\u00a0from Left tree, then select\u00a0storage<\/strong>\u00a0tab as shown.<\/p>\n
                      \n
                      \"Select<\/a><\/p>\n
                      Select Storage Tab<\/p>\n<\/div>\n
                      10.<\/strong>\u00a0Click on\u00a0New Domain<\/strong>\u00a0to add new storage domain for our\u00a0data-center1<\/strong>\u00a0then fill the wizard as shown.<\/p>\n
                      \n
                      \"Add<\/a><\/p>\n
                      Add New Domain to Data Center<\/p>\n<\/div>\n
                      Important<\/strong>: Make sure you select Storage Type \u201ciSCSI<\/strong>\u201d in the type list.<\/p>\n
                      11.<\/strong>\u00a0Then click\u00a0Discover<\/strong>, here you will find the\u00a0target name<\/strong>\u00a0of our storage node. Click the arrow button to go on.<\/p>\n
                      \n
                      \"Target<\/a><\/p>\n
                      Target Name<\/p>\n<\/div>\n
                      12.<\/strong>\u00a0You will find our storage is discovered. Check it then Click\u00a0OK<\/strong>\u00a0as shown, then wait a while and check our new storage domain under\u00a0Storage<\/strong>\u00a0tab.<\/p>\n
                      \n
                      \"Discovered<\/a><\/p>\n
                      Discovered Storage<\/p>\n<\/div>\n
                      \n
                      \"Storage<\/a><\/p>\n
                      Storage Domain<\/p>\n<\/div>\n
                      13.<\/strong>\u00a0Review and check size, Status and attaching Data Center.<\/p>\n
                      \n
                      \"Review<\/a><\/p>\n
                      Review All Settings<\/p>\n<\/div>\n
                      Conclusion<\/h3>\n
                      Now, our RHEV environment has active\u00a0Data Center<\/strong>\u00a0with one cluster which contains two active and ready nodes with active\u00a0ISCSI<\/strong>\u00a0shared storage. So, we are ready to deploy server and desktop virtual machines with visualization features such as HA, Snapshots , Pools, etc. that will be discussed in next articles\u2026<\/p>\n
                      References<\/strong>:\u00a0RHEV Storage Administration Guide<\/a><\/p>\n
                      Don\u2019t Miss:<\/strong><\/p>\n
                        \n
                      1. Install RedHat Enterprise Virtualization (RHEV) 3.5 \u2013 Part 1<\/a><\/li>\n
                      2. Deploy RedHat Enterprise Virtualization Hypervisor (RHEV-H) \u2013 Part 2<\/a><\/li>\n<\/ol>\n
                        How to Deploy Virtual Machines in RHEV Environment \u2013 Part 4<\/h1>\n
                         <\/p>\n
                        Our environment consist of one\u00a0datacenter<\/strong>\u00a0attached with\u00a0ISCSI<\/strong>\u00a0shared storage. This datacenter included one cluster with two hosts\/nodes which will be used to host our virtual machine.<\/p>\n
                        \"Deploy<\/a><\/p>\n
                        Deploy Virtual Machines in RHEV ISO Domain \u2013 Part 4<\/p>\n<\/div>\n
                        Basically in any environment, we could deploy physical\/virtual machines by using popular methods such as From ISO\/DVD, Network, Kickstart and so on. For our environment, there is no huge difference about previous fact, as we will use the same methods\/installation types.<\/p>\n
                        As a start we are discussing\u00a0VM<\/strong>\u00a0deployment using ISO file\/image.\u00a0RHEV<\/strong>\u00a0entertainment is very organized one, so it has special domain used only for this target, store ISO files used to create virtual machines, this domain is storage one called ISO Domain.<\/p>\n
                        Step 1: Deploy New ISO Domain<\/h3>\n
                        Actually,\u00a0RHEVM<\/strong>\u00a0creates\u00a0ISO Domain<\/strong>\u00a0during installation process. To check that, just navigate\u00a0storage<\/strong>\u00a0tab for the environment.<\/p>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm ISO Domains<\/p>\n
                        We could use the exist one and attach it to our datacenter, but lets create new one for more practice.<\/p>\n
                        Note<\/strong>: The exist one is used\u00a0NFS<\/strong>\u00a0shared storage on the\u00a0rhevm<\/strong>\u00a0machine\u00a0IP:11.0.0.3<\/strong>. The new created one will use NFS shared storage on our storage node\u00a0IP:11.0.0.6<\/strong>.<\/p>\n
                        1.<\/strong>\u00a0To Deploy NFS service on our storage node,<\/p>\n
                        [root@storage ~]# yum install nfs-utils -y\r\n[root@storage ~]# chkconfig nfs on \r\n[root@storage ~]# service rpcbind start\r\n[root@storage ~]# service nfs start\r\n<\/pre>\n
                        2.<\/strong>\u00a0We should create new directory to be shared using\u00a0NFS<\/strong>.<\/p>\n
                        [root@storage ~]# mkdir \/ISO_Domain\r\n<\/pre>\n
                        3.<\/strong>\u00a0Share the directory by add this line to\u00a0\/etc\/exports<\/strong>\u00a0file and then apply changes.<\/p>\n
                        \/ISO_Domain     11.0.0.0\/24(rw)\r\n<\/pre>\n
                        [root@storage ~]# exportfs -a\r\n<\/pre>\n
                        Important<\/strong>: Change the ownership of the directory to be with\u00a0uid:36<\/strong>\u00a0and\u00a0gid:36<\/strong>.<\/p>\n
                        [root@storage ~]# chown 36:36 \/ISO_Domain\/\r\n<\/pre>\n
                        Note<\/strong>: The\u00a036<\/strong>\u00a0is the uid for vdsm user \u201cRHEVM agent\u201d and the gid of kvm group.<\/p>\n
                        It is mandatory to make the exported directory is accessible be\u00a0RHEVM<\/strong>. So, your NFS should be ready to be attached as ISO Domain to our environment.<\/p>\n
                        4.<\/strong>\u00a0To create\u00a0New ISO<\/strong>\u00a0domain with\u00a0NFS<\/strong>\u00a0type\u2026 choose\u00a0Data-Center1<\/strong>\u00a0From system tab, then click on\u00a0New Domain<\/strong>from storage tab.<\/p>\n
                        \"Create<\/a><\/p>\n
                        Create New ISO Domain<\/p>\n<\/div>\n
                        5.<\/strong>\u00a0Then Fill the appeared window as shown:<\/p>\n
                        \"New<\/a><\/p>\n
                        New Domain Details<\/p>\n<\/div>\n
                        Note<\/strong>: Make sure about the Domain function\/Storage type is ISO \/ NFS.<\/p>\n
                        Wait a moment and check again under storage tab.<\/p>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm New ISO Domain<\/p>\n<\/div>\n
                        Now, our\u00a0ISO Domain<\/strong>\u00a0is successfully created and attached. So, lets upload some\u00a0ISO\u2019s<\/strong>\u00a0to it for VM\u2019s deploying.<\/p>\n
                        6.<\/strong>\u00a0Make sure you have ISO file on your\u00a0RHEVM<\/strong>\u00a0server. We will work with two ISO\u2019s one for Linux {CentOS_6.6<\/strong>} and the other one for windows {Windows_7<\/strong>}.<\/p>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm ISO Files<\/p>\n<\/div>\n
                        7.<\/strong>\u00a0RHEVM<\/strong>\u00a0provides tool called (rhevm-iso-uploader<\/strong>). It used to upload ISO\u2019s to ISO Domains beside useful tasks.<\/p>\n
                        First, we will use it to list all available ISO Doamins.<\/p>\n
                        \"Check<\/a><\/p>\n
                        Check ISO Domains<\/p>\n<\/div>\n
                        Hint<\/strong>: The upload operation supports multiple files (separated by spaces) and wildcards. Second, we will use it to upload ISO\u2019s to our iso domain \u201cISO_Domain<\/strong>\u201d.<\/p>\n
                        \"Upload<\/a><\/p>\n
                        Upload Files ISO Domain<\/p>\n<\/div>\n
                        Note<\/strong>: Uploading process takes some time as it depends on your network.<\/p>\n
                        Hint<\/strong>: ISO domain could be on the RHEVM machine, its recommended in some cases, any way its totally depend on your environment and infrastructure needs.<\/p>\n
                        8.<\/strong>\u00a0Check the uploaded ISO\u2019s from web interface.<\/p>\n
                        \"Check<\/a><\/p>\n
                        Check Uploaded ISO Files<\/p>\n<\/div>\n
                        Its time for second section \u201cVirtual Machines Deployment<\/strong>\u201d.<\/p>\n
                        Step 2: Virtual Machines Deployment \u2013 Linux<\/h3>\n
                        11.<\/strong>\u00a0Switch to\u00a0Virtual Machines<\/strong>\u00a0tab and click \u201cNew VM<\/strong>\u201d.<\/p>\n
                        \"Create<\/a><\/p>\n
                        Create New Virtual Machine<\/p>\n<\/div>\n
                        12.<\/strong>\u00a0Then fill the appeared windows as shown:<\/p>\n
                        \"New<\/a><\/p>\n
                        New VM Details<\/p>\n<\/div>\n
                        To modify some options like memory allocation and boot options, press \u201cShow Advanced Options<\/strong>\u201d.<\/p>\n
                        13.<\/strong>\u00a0Select \u201cSystem<\/strong>\u201d to modify Memory and vCPU\u2019s.<\/p>\n
                        \"Configure<\/a><\/p>\n
                        Configure Memory CPU<\/p>\n<\/div>\n
                        14.<\/strong>\u00a0Select\u00a0Boot Options<\/strong>\u00a0to attach our ISO image to virtual machines, then press\u00a0OK<\/strong>.<\/p>\n
                        \"Select<\/a><\/p>\n
                        Select Boot Options<\/p>\n<\/div>\n
                        15.<\/strong>\u00a0Before starting your virtual machine, you should create and attach virtual disk. So, press \u201cConfigure Virtual Disks<\/strong>\u201c in the automatically appeared window.<\/p>\n
                        \"Configure<\/a><\/p>\n
                        Configure Virtual Disks<\/p>\n<\/div>\n
                        16.<\/strong>\u00a0Then Fill the next appeared window as shown and press OK.<\/p>\n
                        \"Add<\/a><\/p>\n
                        Add Virtual Disk Details<\/p>\n<\/div>\n
                        Hint<\/strong>: We discussed the difference between \u201cPre-allocated<\/strong>\u201d and \u201cThin Provision<\/strong>\u201d previously in this article from kvm series at\u00a0Manage KVM Storage Volumes and Pools \u2013 Part 3<\/a>.<\/p>\n
                        17.<\/strong>\u00a0Close the window asks about adding another virtual disk. Now, Lets check our virtual machine.<\/p>\n
                        \"Check<\/a><\/p>\n
                        Check New Virtual Machine<\/p>\n<\/div>\n
                        Hint<\/strong>: You may need to install\u00a0SPICE<\/strong>\u00a0plug-in to make sure virtual machine console will work fine.<\/p>\n
                        For Redhat based Distro\u2019s<\/h5>\n
                        # yum install spice-xpi\r\n<\/pre>\n
                        For Debian based Distro\u2019s<\/h5>\n
                        # apt-get install browser-plugin-spice\r\n<\/pre>\n
                        Then restart your\u00a0Firefox<\/strong>\u00a0browser.<\/p>\n
                        18.<\/strong>\u00a0For first time, we will run virtual machine from \u201cRun once<\/strong>\u201d\u2026just click on it and then change the order of boot options \u2013 make First one is\u00a0CD-ROM<\/strong>.<\/p>\n
                        \"Run<\/a><\/p>\n
                        Run Virtual Machines<\/p>\n<\/div>\n
                        Note<\/strong>: Run once is used for modify vm setting just for one time (Not Permanent) for testing or installation.<\/p>\n
                        19.<\/strong>\u00a0After Clicking (OK<\/strong>), you will notice the state of virtual machine is changed to starting then to up!!.<\/p>\n
                        \"Starting<\/a><\/p>\n
                        \"Up-Virtual-Machine\"<\/a><\/p>\n
                        20.<\/strong>\u00a0Click on icon\u00a0<\/i>\u00a0open Virtual Machine\u2019s Console.<\/p>\n
                        \"Open<\/a><\/p>\n
                        Open Virtual Machine<\/p>\n<\/div>\n
                        Basically, we created a\u00a0linux-server<\/strong>\u00a0virtual machine successfully which hosted on\u00a0node1<\/strong>\u00a0{RHEVHN1<\/strong>}.<\/p>\n
                        Step 3: Virtual Machines Deployment \u2013 Windows<\/h3>\n
                        So, lets complete the journey with deploying another virtual machine acts as desktop machine, we will discuss the difference between server and desktop type later, this desktop virtual machine will be\u00a0Windows7<\/strong>.<\/p>\n
                        Generally, we will repeat almost previous steps with some additional ones. Follow steps as shown in next screens:<\/p>\n
                        21.<\/strong>\u00a0Click\u00a0New VM<\/strong>\u00a0and then fill the requested information.<\/p>\n
                        \"New<\/a><\/p>\n
                        New Virtual Machine<\/p>\n<\/div>\n
                        \"Add<\/a><\/p>\n
                        Add Information about New VM<\/p>\n<\/div>\n
                        22.<\/strong>\u00a0Create a new disk and confirm that the windows VM is created.<\/p>\n
                        \"Add<\/a><\/p>\n
                        Add Windows Virtual Disk<\/p>\n<\/div>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm Windows VM<\/p>\n<\/div>\n
                        Before continue to next steps, windows virtual machines needs some special\u00a0paravirtualization<\/strong>\u00a0drivers and tools to be installed successfully\u2026you can find them under:<\/p>\n
                        \/usr\/share\/virtio-win\/\r\n\/usr\/share\/rhev-guest-tools-iso\/\r\n<\/pre>\n
                        For this ISO used in this tutorial, we will need to upload those files to our ISO Domain and confirm from web interface.<\/p>\n
                        \/usr\/share\/rhev-guest-tools-iso\/RHEV-toolsSetup_3.5_9.iso\r\n\/usr\/share\/virtio-win\/virtio-win_amd64.vfd\r\n<\/pre>\n
                        \"Upload<\/a><\/p>\n
                        Upload Windows ISO<\/p>\n<\/div>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm Windows ISO Files<\/p>\n<\/div>\n
                        23.<\/strong>\u00a0Click Run once and Don\u2019t forget to attach the virtual floppy disk to open VM console.<\/p>\n
                        \"Run<\/a><\/p>\n
                        Run Windows Virtual Machine<\/p>\n<\/div>\n
                        \"Open<\/a><\/p>\n
                        Open Windows VM Console<\/p>\n<\/div>\n
                        24.<\/strong>\u00a0Follow windows instruction to complete the installation. At Disk partitioning stage, you will notice there is no appeared disks. Click on \u201dLoad Driver<\/strong>\u201d then \u201dBrowse<\/strong>\u201d.<\/p>\n
                        \"Windows<\/a><\/p>\n
                        Windows Driver Errors<\/p>\n<\/div>\n
                        \"Load<\/a><\/p>\n
                        Load Windows Drivers<\/p>\n<\/div>\n
                        25.<\/strong>\u00a0Then locate the path of drivers on the virtual floppy disk and select the two drivers related to\u00a0Ethernet<\/strong>\u00a0and\u00a0SCSI<\/strong>\u00a0controller.<\/p>\n
                        \"Browse<\/a><\/p>\n
                        Browse Drivers<\/p>\n<\/div>\n
                        \"Install<\/a><\/p>\n
                        Install Drivers<\/p>\n<\/div>\n
                        26.<\/strong>\u00a0Then Next and wait some time to load our 10G virtual disk is appeared.<\/p>\n
                        \"Installing<\/a><\/p>\n
                        Installing Drivers<\/p>\n<\/div>\n
                        \"Loaded<\/a><\/p>\n
                        Loaded Disk Drive<\/p>\n<\/div>\n
                        Complete the installation process until it finished successfully. Once it finished successfully, go to\u00a0RHEVM<\/strong>\u00a0web interface and change the attached CD.<\/p>\n
                        \"Change<\/a><\/p>\n
                        Change CD Drive<\/p>\n<\/div>\n
                        27.<\/strong>\u00a0Now attach\u00a0RHEV<\/strong>\u00a0tools\u00a0CD<\/strong>\u00a0and then go back to windows virtual machine, you will find tools CD is attached. Install\u00a0RHEV<\/strong>\u00a0tools as shown..<\/p>\n
                        \"RHEV<\/a><\/p>\n
                        RHEV Tools Setup<\/p>\n<\/div>\n
                        \"Install<\/a><\/p>\n
                        Install RHEV Tools on Windows<\/p>\n<\/div>\n
                        Follow the sequentially steps until it finished successfully then\u00a0reboot<\/strong>\u00a0the system.<\/p>\n
                        \"RHEV<\/a><\/p>\n
                        RHEV Tools Installation<\/p>\n<\/div>\n
                        and finally, your windows virtual machine is healthy up and running..:)<\/p>\n
                        Conclusion<\/h3>\n
                        We discussed in this part,\u00a0ISO Domain<\/strong>\u00a0importance and deployment then how to use for storing ISO files which be used later to deploy virtual machines. Linux and windows virtual machines have been deployed and fine working. In next part, we will discuss\u00a0Clustering<\/strong>\u00a0importance and tasks with how to use clustering features in our environment.<\/p>\n
                        RHEV Clustering and RHEL Hypervisors Installation \u2013 Part 5<\/h1>\n
                        In this part we are going to discuss some important points related to our RHEV series. In\u00a0Part-2<\/strong>\u00a0of this series, we\u2019ve discussed\u00a0RHEV Hypervisor deployments and installations<\/a>. In this part we will discuss another ways to install RHEV Hypervisor.<\/p>\n
                        \"RHEV<\/a><\/p>\n
                        RHEV Series: RHEV Clustering and RHEL Hypervisors Installation \u2013 Part 5<\/p>\n<\/div>\n
                        The First way was done by using dedicated\u00a0RHEVH<\/strong>\u00a0which customized by RedHat itself without any modification or change from admin side. The other way, we will use a normal RHEL server [Minimal installation] that will act as a RHEV Hypervisor.<\/p>\n
                        Step 1: Add RHEL Hypervisor to the Environment<\/h3>\n
                        1.<\/strong>\u00a0Install subscribed RHEL6 server [Minimal installation]. You may increase your virtual environment by adding additional subscribed RHEL6 server [Minimal installation] acts as hypervisor.<\/p>\n
                        Virtual Machine Specification<\/h5>\n
                        OS: RHEL6.6 x86_64\r\nNumber of processors: 2\r\nNumber of cores : 1\r\nMemory : 3G\r\nNetwork : vmnet3\r\nI\/O Controller : LSI Logic SAS\r\nVirtual Disk : SCSI\r\nDisk Size : 20G\r\nIP: 11.0.0.7\r\nHostname: rhel.mydomain.org\r\n<\/pre>\n
                        and make sure you checked the\u00a0virtualization<\/strong>\u00a0option in\u00a0vm<\/strong>\u00a0processor settings.<\/p>\n
                        Hint<\/strong>\u00a0: Make sure your system is subscribed to redhat channels and up-to-date, if you don\u2019t know how to subscribe to redhat subscription channel, you may read the article\u00a0Enable Red Hat Subscription Channel<\/a>.<\/p>\n
                        Tip<\/strong>\u00a0: To save your resources you can shutdown one of the both currently up and running hypervisors.<\/p>\n
                        2.<\/strong>\u00a0To turn your server into hypervisor {use it as a hypervisor} you may need install the RHEVM agent on it.<\/p>\n
                        # yum install vdsm\r\n<\/pre>\n
                        After packages installation complete, Go to\u00a0RHEVM<\/strong>\u00a0web interface to add it.<\/p>\n
                        3.<\/strong>\u00a0In against of\u00a0RHEVH<\/strong>\u00a0hypervisor, you can add RHEL hypervisor from one way from RHEM using the root credential of the RHEL hypervisor. So, from\u00a0rhevm WUI<\/strong>\u00a0switch to\u00a0Hosts<\/strong>\u00a0tab and click\u00a0new<\/strong>.<\/p>\n
                        \"Add<\/a><\/p>\n
                        Add RHEL Hypervisor<\/p>\n<\/div>\n
                        Then Provide your host information as shown.<\/p>\n
                        \"Add<\/a><\/p>\n
                        Add Host Information<\/p>\n<\/div>\n
                        Next, ignore Power\u00a0mgmt<\/strong>\u00a0warning and finish then wait for a few minutes and check the status of the newly added host.<\/p>\n
                        \"New<\/a><\/p>\n
                        New Host Status<\/p>\n<\/div>\n
                        \"Confirm<\/a><\/p>\n
                        Confirm Host Information<\/p>\n<\/div>\n
                        For more details about adding RHEL based Host, check out RedHat official\u00a0RHEV documentation<\/a>.<\/p>\n
                        Step 2: Managing RHEV Clustering<\/h3>\n
                        Clustering in RHEV describes a group of the same CPU type hosts are sharing the same storage [e.g. over network] and are using to do specific task [e.g.\u00a0High Availability<\/strong>\u00a0]<\/p>\n
                        Clustering in general has a lot of additional tasks you can check out the article that explains\u00a0What is Clustering and Advantages\/Disadvantages<\/a>\u00a0of it.<\/p>\n
                        The main advantage of clustering in\u00a0RHEV<\/strong>\u00a0is to enable and manage virtual machines migration between hosts that belong to the same cluster.<\/p>\n
                        So, How virtual machines migrate between hosts ?<\/h6>\n
                        RHEV has two strategies:<\/p>\n
                        1.<\/strong>\u00a0Live Migration
                        \n2.<\/strong>\u00a0High Availability<\/p>\n
                        1. Live Migration<\/h4>\n
                        Live Migration<\/strong>\u00a0used in non-critical situation which mean everything is working fine in general but you have to do some load balancing tasks (e.g. you found there is host is loaded by virtual machine over another. So, you may Live migrate virtual machine from host to another to achieve load balancing).<\/p>\n
                        Note<\/strong>\u00a0: There is no interruption to services, application or users running inside VM during Live Migration. Live migration also called as resources re-allocation.<\/p>\n
                        Live migration can be processed manually or automatic according to pre-defined policy:<\/p>\n
                          \n
                        1. Manually<\/strong>: Force selecting the the destination host then migrate VM to it manually using WUI.<\/li>\n
                        2. Automatic<\/strong>\u00a0: Using one of Cluster policies to manage Live migration according to RAM usage, CPU utilization, etc.<\/li>\n<\/ol>\n
                          Switch to\u00a0Clusters<\/strong>\u00a0tab and select\u00a0Cluster1<\/strong>\u00a0the click on edit.<\/p>\n
                          \"Clustering<\/a><\/p>\n
                          Clustering Tab<\/p>\n<\/div>\n
                          From window tabs, switch to\u00a0Cluster Policy<\/strong>\u00a0tab.<\/p>\n
                          \"Cluster<\/a><\/p>\n
                          Cluster Policy<\/p>\n<\/div>\n
                          Select\u00a0evenly_distributed<\/strong>\u00a0policy. This policy allows you to configure Max threshold for CPU utilization on the host and the allowed time for the load before starting Live migration.<\/p>\n
                          Hint<\/strong><\/p>\n
                          As shown I configured the max threshold to be 50% and duration to be 1 min.<\/p>\n
                          \"Configure<\/a><\/p>\n
                          Configure Cluster Properties<\/p>\n<\/div>\n
                          Then\u00a0OK<\/strong>\u00a0and switch to VM\u2019s tab.<\/p>\n
                          Select Linux vm [Previously created] then click\u00a0edit<\/strong>\u00a0and check this points.<\/p>\n
                          1.<\/strong>\u00a0From Host tab : Check\u00a0Manual<\/strong>\u00a0and\u00a0Automatic<\/strong>\u00a0Live Migration is allowed for this VM.<\/p>\n
                          \"Cluster<\/a><\/p>\n
                          Cluster Migration Options<\/p>\n<\/div>\n
                          2.<\/strong>\u00a0From HA tab : Check the\u00a0Priority<\/strong>\u00a0degree of your virtual-machine. In our case, its not very important as we are playing with only one vm. But it will be important to set priorities for your vms in large environment.<\/p>\n
                          \"Cluster<\/a><\/p>\n
                          Cluster VM Priorities<\/p>\n<\/div>\n
                          Then start Linux VM.<\/p>\n
                          First, we will use the\u00a0Manually Live Migration<\/strong>. Linux VM in now running on\u00a0rhel.mydomain.org<\/strong>.<\/p>\n
                          \"Linux<\/a><\/p>\n
                          Linux VM Status<\/p>\n<\/div>\n
                          Lets run the following command over vm console, before starting migration.<\/p>\n
                          # ls -lRZ \/ \r\n<\/pre>\n
                          Then select\u00a0Linux VM<\/strong>\u00a0and click\u00a0Migrate<\/strong>.<\/p>\n
                          \"Linux<\/a><\/p>\n
                          Linux VM Migrate<\/p>\n<\/div>\n
                          If you select automatically, system will check the most responsible host to be destination under the cluster policy. We will test this without any interference from administrator.<\/p>\n
                          \"Migrate<\/a><\/p>\n
                          Migrate Virtual Machines<\/p>\n<\/div>\n
                          So, after selecting manually and choose the destination, Click OK and go to console and monitor the running command. You can also check the vm status.<\/p>\n
                          \"Monitor<\/a><\/p>\n
                          Monitor VM Status<\/p>\n<\/div>\n
                          You may need to monitor Task events.<\/p>\n
                          \"Monitor<\/a><\/p>\n
                          Monitor Task Events<\/p>\n<\/div>\n
                          After a few seconds, you will find a change in he vm Hostname.<\/p>\n
                          \"Confirm<\/a><\/p>\n
                          Confirm VM Changes<\/p>\n<\/div>\n
                          Your\u00a0VM<\/strong>\u00a0is manually Live migrated successfully !!<\/p>\n
                          Lets try automatic\u00a0Live Migration<\/strong>, our target is to make CPU Load on the rhevhn1 Host is exceeded 50%. We will do that by increasing the load on the vm itself, so from console write this command:<\/p>\n
                          # dd if=\/dev\/urandom of=\/dev\/null\r\n<\/pre>\n
                          and monitor the load on Host.<\/p>\n
                          \"Monitor<\/a><\/p>\n
                          Monitor VM Load<\/p>\n<\/div>\n
                          After few minutes, the load on Host will exceeds 50%.<\/p>\n
                          \"VM<\/a><\/p>\n
                          VM Load Alert<\/p>\n<\/div>\n
                          Just wait another few more minutes then live migration will start automatically as shown.<\/p>\n
                          \"VM<\/a><\/p>\n
                          VM Live Migration<\/p>\n<\/div>\n
                          You can also check the tasks tab, and after little waiting, your virtual machine is automatically Live Migrated to rhel Host.<\/p>\n
                          \"Monitor<\/a><\/p>\n
                          Monitor VM<\/p>\n<\/div>\n
                          \"VM<\/a><\/p>\n
                          VM RHEL Migration<\/p>\n<\/div>\n
                          Important<\/strong>: Make sure that one of your hosts have resources more than the other one. If the two hosts are identical in resources. VM won\u2019t be migrated because there will be no difference !!<\/p>\n
                          Hint<\/strong>: Putting Host into\u00a0Maintenance Mode<\/strong>\u00a0will automatically Live Migration Up and running VM\u2019s to other hosts in the same cluster.<\/p>\n
                          For further information about VM Migrations, read\u00a0Migrating Virtual Machines Between Hosts<\/a>.<\/p>\n
                          Hint<\/strong>: Live Migration between different clusters isn\u2019t officially supported expect one case you can check it\u00a0here<\/a>.<\/p>\n
                          2. High Availability<\/h4>\n
                          In the against of\u00a0Live Migration<\/strong>,\u00a0HA<\/strong>\u00a0is used to Cover Critical Situation not just load balancing tasks. The common section that your VM will also migrated to another host but with rebooting down time.<\/p>\n
                          If you have Failure, Non-Operational or Non-responsive Host in your cluster, Live Migration Cannot help you. HA will power-off the virtual-machine and restart it on another up and running host in the same cluster.<\/p>\n
                          To\u00a0Enable HA<\/strong>\u00a0in your environment, you must have at least one power management device [e.g.\u00a0power switch<\/strong>] in your environment.<\/p>\n
                          Unfortunately, we aren\u2019t able to do that in our virtual environment. So for more about HA in RHEV please check out\u00a0Improving Uptime with VM High Availability<\/a>.<\/p>\n
                          Remember<\/strong>: Live Migration and High Availability are working with hosts in the same cluster with same type of CPU and connected to shared Storage.<\/p>\n
                          Conclusion:<\/h3>\n
                          We reached peak point in our series as we discussed one of the important features in RHEV Clustering as we described it and its importance. Also we discussed the second type [method] to deploy RHEV hypervisors which based on RHEL [at least 6.6 x86_64].<\/p>\n
                          In next article, we will be able to make some operations on virtual-machines such as snapshots, sealing, cloning, exporting and pools.<\/p>\n
                          How to Manage RedHat Enterprise Virtualization (RHEV) Virtual Machines Operations and Tasks \u2013 Part 6<\/h1>\n
                          In this part of our tutorial we are going to discuss the operations and tasks such as Taking Snaphots, Creating Pools, Making Templates and Cloning are the main operations which could be performed on RHEV virtual machines hosted by\u00a0RHEV<\/strong>\u00a0environment.<\/p>\n
                          Before going further, I request you to read the rest of the articles from this RHEV series here:<\/p>\n
                          RedHat Enterprise Virtualization (RHEV) Administration Series \u2013 Part 1-7<\/a><\/p>\n
                          \"Manage<\/a><\/p>\n
                          Manage RHEV VM Operations and Tasks \u2013 Part 6<\/p>\n<\/div>\n
                          Snapshots<\/h3>\n
                          Snapshot is used to save VM\u2019s state at specific Point-Time. This is very useful and helpful during software testing process or revert something going wrong on your system as you could return back to the Point-Time which you took snapshot at.<\/p>\n
                          1.<\/strong>\u00a0Start your\u00a0linux-vm<\/strong>\u00a0machine and verify the OS version and type before taking snapshot.<\/p>\n
                          \"Check<\/a><\/p>\n
                          Img 01: Check Linux OS Version<\/p>\n
                          2.<\/strong>\u00a0Click on \u201cCreate Snapshot<\/strong>\u201d.<\/p>\n
                          \"Create<\/a><\/p>\n
                          Img 02: Create RHEV Snapshot<\/p>\n<\/div>\n
                          3.<\/strong>\u00a0Add the description and select disks and saving memory then OK.<\/p>\n
                          \"Add<\/a><\/p>\n
                          Img 03: Add Snapshot Description<\/p>\n<\/div>\n
                          Check the status of snapshot and task status from tasks bar.<\/p>\n
                          \"Confirm<\/a><\/p>\n
                          Img 04: Confirm Created Snapshot Status<\/p>\n<\/div>\n
                          After finishing, you will note that status of snapshot changed from\u00a0Lock<\/strong>\u00a0to\u00a0OK<\/strong>, which meaning that your snapshot is ready and created successfully.<\/p>\n
                          \"Check<\/a><\/p>\n
                          Img 05: Check Snapshot Status<\/p>\n<\/div>\n
                          4.<\/strong>\u00a0Lets go to the VM console and delete\u00a0\/etc\/issue<\/strong>\u00a0file.<\/p>\n
                          \"Delect<\/a><\/p>\n
                          Img 06: Delete Issue File<\/p>\n<\/div>\n
                          5.<\/strong>\u00a0For reverting\/restoring process, your virtual machine should be at down state. Make sure its powered off and then click \u201cPreview<\/strong>\u201d to check the snapshot and reverting on-fly to it.<\/p>\n
                          \"Shut<\/a><\/p>\n
                          Img 07: Shut Down Snapshot<\/p>\n<\/div>\n
                          Now confirm\u00a0Memory<\/strong>\u00a0restoring.<\/p>\n
                          \"Restore<\/a><\/p>\n
                          Img 08: Restore Snapshot Memory<\/p>\n<\/div>\n
                          Wait for Previewing to be finished and after few minuets, you will noted that snapshot status is \u201cIn preview<\/strong>\u201d.<\/p>\n
                          \"Snapshot<\/a><\/p>\n
                          Img 09: Snapshot In Preview State<\/p>\n<\/div>\n
                          Now we have two ways:<\/h4>\n
                          6.<\/strong>\u00a0First one to directly \u201cCommit<\/strong>\u201d the restored snapshot to the original virtual machine and finishing the total reverting process.<\/p>\n
                          Second one to check the reverted changes before commit the restored snapshot to original vm. After checking we will go to the first way \u201cCommit<\/strong>\u201d.<\/p>\n
                          For this article, we will start via second way. So, we will need to power up the virtual machine and then check the\u00a0\/etc\/issue<\/strong>\u00a0file. You will find it without any changes.<\/p>\n
                          \"Check<\/a><\/p>\n
                          Img 10: Check Issue File<\/p>\n<\/div>\n
                          7.<\/strong>\u00a0Your VM should be powered off for reverting process. After powering off, Commit your snapshot to vm.<\/p>\n
                          \"Commit<\/a><\/p>\n
                          Img 11: Commit VM Snapshot<\/p>\n<\/div>\n
                          Then watch restoring commit process, after finishing commit process, you will find snapshot status is \u201cOK<\/strong>\u201d.<\/p>\n
                          \"Confirm<\/a><\/p>\n
                          Img 12: Confirm Commit Snapshot<\/p>\n<\/div>\n
                          Hints<\/strong>\u00a0: 1. If you don\u2019t want to confirm reverting to snapshot after preview stage, just click on \u201cUndo<\/strong>\u201d to skip snapshot. Its always recommended to take snapshot of power down VM instead of be running. You can create new VM from current snapshot, just select your preferred snapshot and click on \u201cClone<\/strong>\u201d.<\/p>\n
                          \"Create<\/a><\/p>\n
                          Img 13: Create VM Snapshot Clone<\/p>\n<\/div>\n
                          Templates:<\/h3>\n
                          Actually, template is a very normal virtual machine copy, but without any pre-configuration related to the original vm operating system. Templates are used to improve the speed and decrease time of vm operating system installation.<\/p>\n
                          Creating templates has two main process:<\/h6>\n
                            \n
                          1. A.<\/strong>\u00a0Sealing the original virtual machine.<\/li>\n
                          2. B.<\/strong>\u00a0Taking copy [Create Template<\/strong>] of the sealed vm to be separated template.<\/li>\n<\/ol>\n
                            A. Sealing Process:<\/h4>\n
                            To seal RHEL6 Virtual Machine you should make sure about this points :<\/p>\n
                            8.<\/strong>\u00a0Flagging system for pre-configuration for next booting by creating this empty hidden file.<\/p>\n
                            # touch \/.unconfigured\r\n<\/pre>\n
                            9.<\/strong>\u00a0Remove any ssh host keys and set hostname to be\u00a0localhost.localdomain<\/strong>\u00a0in\u00a0\/etc\/sysconfig\/network<\/strong>\u00a0file and also remove system udev rules.<\/p>\n
                            # rm -rf \/etc\/ssh\/ssh_host_*\r\n# rm -rf \/etc\/udev\/rules.d\/70-*<\/pre>\n
                            10.<\/strong>\u00a0Remove MAC address from Network interface configuration file eg. [\/etc\/sysconfig\/network-scripts\/ifcfg-eth0<\/strong>] and delete all system logs under\u00a0\/var\/log\/<\/strong>\u00a0and finally Power off your virtual machine.<\/p>\n
                            \"Commands<\/a><\/p>\n
                            Img 14: Commands to Follow<\/p>\n<\/div>\n
                            B. Creating Templates<\/h4>\n
                            11.<\/strong>\u00a0Select the sealed vm and click \u201cCreate Template<\/strong>\u201d.<\/p>\n
                            \"Create<\/a><\/p>\n
                            Img 15: Create New VM Template<\/p>\n<\/div>\n
                            12.<\/strong>\u00a0Provide details and proprieties about your new template.<\/p>\n
                            \"Add<\/a><\/p>\n
                            Img 16: Add Template Details<\/p>\n<\/div>\n
                            Now, you can check the process from tasks and also you could switch Templates tab to monitor the status of your new templates.<\/p>\n
                            \"Check<\/a><\/p>\n
                            Img 16: Check Template Information<\/p>\n<\/div>\n
                            \"Monitor<\/a><\/p>\n
                            Img 17: Monitor Template Status<\/p>\n<\/div>\n
                            Wait a few minutes, then check template status again.<\/p>\n
                            \"Check<\/a><\/p>\n
                            Img 18: Check VM Template Again<\/p>\n<\/div>\n
                            You will note that its converted from\u00a0lock<\/strong>\u00a0to\u00a0OK<\/strong>. Now our new template is ready to be used. Actually we will use it in the next section.<\/p>\n
                            Creating Pools:<\/h3>\n
                            Pool is a group of identical virtual machines. Pooling is used to create a given number of identical virtual machines in one step. Those virtual machines could be based on pre-created template.<\/p>\n
                            Creating New Pool<\/h4>\n
                            13.<\/strong>\u00a0Switch to\u00a0Pools<\/strong>\u00a0tab and click\u00a0New<\/strong>\u00a0then fill the appeared wizard windows.<\/p>\n
                            \"Create<\/a><\/p>\n
                            Img 19: Create New Pool<\/p>\n<\/div>\n
                            14.<\/strong>\u00a0Now check the status of created Pool\u00a0vms<\/strong>\u00a0and wait few minutes, you will note the status of virtual machines changed from\u00a0Lock<\/strong>\u00a0to\u00a0Down<\/strong>.<\/p>\n
                            \"VM<\/a><\/p>\n
                            Img 20: VM Pool Status Locked<\/p>\n<\/div>\n
                            \"VM<\/a><\/p>\n
                            Img 21: VM Pool Status Down<\/p>\n<\/div>\n
                            You could also check the status from\u00a0Virtual Machines<\/strong>\u00a0tab.<\/p>\n
                            \"Check<\/a><\/p>\n
                            Img 22: Check Pool Status from VM<\/p>\n<\/div>\n
                            15.<\/strong>\u00a0Lets try to run one of Pool virtual machines.<\/p>\n
                            \"Run<\/a><\/p>\n
                            Img 22: Run Virtual Machine<\/p>\n<\/div>\n
                            That\u2019s right, you will be asked for new root password and also you will be asked about basic authentication configuration. Once finished your new vm is now ready for use.<\/p>\n
                            \"Select<\/a><\/p>\n
                            23: Select Basic Authentication<\/p>\n<\/div>\n
                            Monitor VMs also from pools tab.<\/p>\n
                            \"Monitor<\/a><\/p>\n
                            Img 24: Monitor Virtual Machine<\/p>\n<\/div>\n
                            Notes<\/strong>:<\/p>\n
                              \n
                            1. To delete Pool, You should detach all of VMs from the Pool.<\/li>\n
                            2. To detach VM from Pool, VM must be at down state.<\/li>\n
                            3. Compare VM installation time [Normal way VS. Template using].<\/li>\n<\/ol>\n
                              Create VM Clones:<\/h3>\n
                              Cloning is normal Copy Process without any change to the Original Source. Cloning could done from Original VM or Snapshot.<\/p>\n
                              To take Clone:<\/h4>\n
                              16.<\/strong>\u00a0Select the Original source [VM or Snapshot] then click \u201cClone VM<\/strong>\u201d.<\/p>\n
                              \"Create<\/a><\/p>\n
                              Img 25: Create VM Clone<\/p>\n<\/div>\n
                              Hint<\/strong>: If you will take clone from VM, VM must be at down state.<\/p>\n
                              17.<\/strong>\u00a0Provide name to your cloned VM and wait few minutes, you will find the cloning process is done and the new vm now is ready to be used.<\/p>\n
                              \"Give<\/a><\/p>\n
                              Img 26: Give VM Clone Name<\/p>\n<\/div>\n
                              \"VM<\/a><\/p>\n
                              Img 27: VM Clone Details<\/p>\n<\/div>\n
                              Conclusion<\/h3>\n
                              As a RHEV administrator, there some main tasks to be done on environment virtual machines. Cloning, Creating Pools, Making Templates and Taking snapshots are basic and important tasks should be done by RHEV admin. This tasks also considered as the core tasks of any virtualization environment, So make sure you understood it well then do more and more,,, and more practical labs in your private environment.<\/p>\n
                              Resources<\/strong>:\u00a0RHEV Administration Guide<\/a><\/p>\n
                               <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
                              Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
                              In this series we are discussing\u00a0RHEV3.5\u00a0administration topics. RHEV is the RedHat Enterprise Virtualization solution, which is based on\u00a0oVirt\u00a0project [open-source Virtualization project]. Red Hat Enterprise Virtualization is a complete virtualization management solution for virtualized servers and desktops. This series will discuss (How to) administration topics including the RHCVA exam objectives. Part 1:\u00a0How to Install RedHat Enterprise … <\/p>\n
                              Continue reading “How to Install RedHat Enterprise Virtualization (RHEV) 3.5”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-12013","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12013","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=12013"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12013\/revisions"}],"predecessor-version":[{"id":12016,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/12013\/revisions\/12016"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=12013"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=12013"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=12013"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}