This is a really simple export routine for VMware using a custom button.
In an implementation I would maybe wrap this with
- A dialog to offer different export locations and naming of the export to include date/time stamp and maybe a checkbox to enable disable the overwrite of existing exports.
- Add in the approval system, basically some workloads should require authorisation by a manager to allow the export, we could do this by tag, and capture this in the method.
- Some error checking and folder creation stuff in the simple method.
Continue reading “Exporting VM (VMware)”
If you so happen to have the VMware OVF version of CloudFORMs CFME, and you want to convert to run on KVM, this is how.
1. If the OVF is zipped, Unzip the appliance image:
$ unzip evm-v220.127.116.11-r.zip
2. Convert each of the 5 disks from VMDK format to RAW:
$ for i in `seq 1 5`; do qemu-img convert -p evm-v18.104.22.168-r/ovf-disk$i.vmdk disk$i.img; done
Continue reading “CloudFORMS CFME on KVM”
This post will solve anything! Quite simply anything you can script, code or model in CloudFORMS you can call externally too using simple web services.
We will need a few things as follows;
- A sample method that we can call
- A ruby script to call our web services and execute our sample method.
Continue reading “CloudFORMS and Simple WebServices (RUBY)”
Use Case – I want that when I provision a virtual machine I can specify certain workload types that I wish to avoid being placed with.
Example 1 – I will be requesting a virtual machine that will be very intensive on CPU or Disk I/O, therefore I want to ensure that I do not place it with any Database Servers, as I may impact their operation or they could equally stave me of resources. But I don’t know where the Database servers are located nor do I care, also real time the database servers are DRS managed therefore they may not be where they were first provisioned!
Continue reading “Workload Placement by Type (Not Near That)”
Enable CloudFORMS to clone a template, and retaining the disk layout. So CloudFORMS currently deploys new virtual machines in RHEV either by PXE or ISO. It does this by cloning a BLANK template and attaching new disks, where a PXE or ISO process will install an operating system. Those from the VMware world and those in Windows land will want to deploy directly from a template a clone, without having to install an operating system, because the template already has it installed in its disk. Reasonable request…. this is how…
Continue reading “Clone from Template (RHEV)”
You want to delete a Template in RHEV from the CloudFORMS UI, but how?
This is easy, because the ReST API’s are so lovely in RHEV. Here is how;
Create a custom button that will execute your method, remember this is for VM Template and not just VM.
Now create the Automate parts, (if you need assistance on the general wiring of automate, try here first)
Continue reading “Delete Template from Disk (RHEV)”
CloudFORMS lacks currently the ability to create a template from an existing VM, here is the method to enable this function from a custom button.
First you need a dialog to collect from the new user the name of the template, so create a dialog of your liking, including at least;
Textbox – Name = dialog_name
Continue reading “Create Template from VM (RHEV)”
Hooking Cobbler and CloudFORMS 2.0 together is actually quite simple. Lets first understand the use case.
We want to deploy virtual machines using PXE boot from Cobbler.
Cobbler stores each vm’s boot information as a “System Record”, there is a nice API that you can launch that will create these system records, you just need to pass the right parameters. The data required to drive Cobbler to create a system record are;
Continue reading “Cobbler Provisioning via CloudFORMS 2.0”