This is pretty simple but very useful. I have done a little research and whilst inspect is a way of seeing inside of an object its also hard to read and not very re-usable. Being somewhat old now (crazy thought) XML used to be the way we described things. Yes I know yaml, json etc have come to replace XML in languages such as Ruby, but I cannot get away from XML is far easier to read and self describing than the aforementioned.
This subject is only the hottest on the block at the moment…why? I guess because InfoBlox is pretty cool, it provides DHCP, DNS and IP Address Management services for any size of network. Its fairly easy to configure and InfoBlox are a good company who allow you to try their software for 60 days eval license. You can integrate using simple RestAPI (there is a Ruby GEM, but I don’t advise using it, I found it problematic, and Rest is so easy anyway!)
Its here and looks great. You can now populate a drop down list from an external source!
Simply create an Instance and Method, its advised you create a new Namespace to store dialog controls into rather than mixing them up into the general automation model.
These been some discussion about Build-In vs In-line methods, here is a quick example of a Built-In method that sends email from instance attributes that is quite commonly done as a In-Line method when it does not need to be In-Line.
CloudFORMS has workflows for many different tasks including approval, quotas and placement to name just a few. This blog entry is going to add to the placement category of workflows. A previous post of mine showed how you could place new workloads NOT_NEAR “Workload Placement by Type (Not Near That)” other workloads which I still think is really cool. This placement workflow is quite simple, it matches template tags against cluster tags. Example;
The base automate model does not contain the email methods for the VM Reconfigure approval process, this post gives you this capability.
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.
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-v126.96.36.199-r.zip
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.