The Red Planet

Simple guide for creating a VM using oVIRT In this step by step guide we will create a VM using oVirt and highlight the differences between oVirt and vCenter as necessary to help admins migrate vSphere skills to oVirt with ease Here is discussed the whole process from transferring files to running a VM for the first time. On each step we elaborate below: STEP1: Downloading and uploading your ISO. First we make a decision on what VM we want to install. In this scenario we will grab Server 2012 as we already have license for one. Once the ISO is downloaded from Microsoft or elsewhere we need to upload the ISO to oVirt. This is plain file transfer between two machines, feel free to use SFTP, SCP, FTP as suitable. In our scenario SCP is used as the transfer is between to Linux client and SCP is built in CLI package to move files across.- - Check we have the ISO in our Documents directory - Upload the file to the ovirt server in then ISOs directory - Login to the...

.NET 3.5 on Windows Server 2012 with or without source ISO   When working on Windows Server where you do not have full control can be very tricky to install .NET 3.5 framework. This is especially the case when you are setting up a system for a customer on a cloud hosted server for example. You get your server from your cloud provider and you get credentials to login and thats all. No control over virtual environment.  Why would you need .NET 3.5 framework? - There are tons of applications that still use and are built on .NET 3.5 still and yes all those applications are current releases. Now, lets get down to business. You have two options to enable/install .NET 3.5 on server 2012 / 2012 R2 using few fairly simple steps. Both of this options are discussed below in its own separate section. Install .NET 3.5 framework on Server 2012 with INTERNET access In this scenario your server has Internet access. You do not have access to the source ISO o...

oVirt ISO Storage Domain In oVirt, since version 4 there is a new version type introduced " POSIX Compliant File System Storage". This means that now you can use standard linux file structure such ext4 to map storage to the cluster. This sounds like a vSphere now.  Remember how you can have combination of vSAN Datastore and Local Datastore available to ESXi? Does this means that we can now create partition on oVirt Node (KVM) an mount this as storage domain to the cluster? - Not so quick. oVirt is made for High Availability and builds on that concept. All hosts in the cluster MUST be able to see the storage domain. Even if you manage to add a local storage domain to oVirt, lets say ISO Storage Domain which makes perfect sense, you'll most likely end-up with orphaned cluster. All hosts unable to see the new storage domain will be kicked out of the Cluster. Now, since we've seen that POSIX Compliant File System Storage does not really make much sense ...