<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CloudForms on Forward or Reverse</title>
    <link>https://blog.wannemacher.us/categories/cloudforms/</link>
    <description>Recent content in CloudForms on Forward or Reverse</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 Jul 2016 22:05:28 +0000</lastBuildDate>
    
	<atom:link href="https://blog.wannemacher.us/categories/cloudforms/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Men and Mice API Client Gem for Ruby</title>
      <link>https://blog.wannemacher.us/posts/p588/</link>
      <pubDate>Sun, 17 Jul 2016 22:05:28 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p588/</guid>
      <description>Part of what I am doing these days is integrating Red Hat CloudForms / ManageIQ with the Men and Mice IP address management (IPAM) application. In order to reduce gem dependencies, reduce duplication, and handle some architecture issues I have been working on a client gem that uses the JSON-RPC API provided by Men and Mice.
If you are using Ruby and want to integrate with M&amp;amp;M please check out the gem and provide any feedback you have through Github issues.</description>
    </item>
    
    <item>
      <title>Helper utility for ManageIQ/CloudForms Automate</title>
      <link>https://blog.wannemacher.us/posts/p573/</link>
      <pubDate>Mon, 24 Aug 2015 16:19:03 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p573/</guid>
      <description>As I do Automate development on RedHat CloudForms I am seeing a lot of copy/paste code which is the opposite of DRY. Our process was to put commonly used code in a starting template for an Automate method. This is nice because someone new to development gains the experience of a nice starting point, but it results in a lot of extra code. We also lose the benefit of bug fixes to the helper methods.</description>
    </item>
    
    <item>
      <title>Getting ManageIQ instance attributes without executing methods/states</title>
      <link>https://blog.wannemacher.us/posts/p564/</link>
      <pubDate>Tue, 26 May 2015 21:18:47 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p564/</guid>
      <description>I want to use the values from the ProvisionRequestQuotaVerification instance. The problem is that using $evm.instantiate will cause the code to run. This results in an exception or error.
Digging around I found
1  $evm.instance_get(path)   Which works as long as you know the full path including the domain, but then you can not rely on domain inheritance.
1  my_instance = $evm.instance_get(&amp;#34;/ManageIQ/Infrastructure/VM/Provisioning/StateMachines/ProvisionRequestQuotaVerification/default&amp;#34;)   Here is my current workaround:</description>
    </item>
    
    <item>
      <title>Red Hat CloudForms/ManageIQ – Examples</title>
      <link>https://blog.wannemacher.us/posts/p558/</link>
      <pubDate>Thu, 26 Mar 2015 13:05:54 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p558/</guid>
      <description>For me, one of the easier ways to begin to learn something is to learn by example. Even if the example does not solve my exact problem, I can use it to figure out ways of extracting the information I need and patterns for implementing new functionality. As a response to a forum question regarding provisioning approvals, Kevin Morey pointed out a Github repository that I was unaware of (https://github.com/ramrexx/CloudFormsPOC). This repo is a great source of example code to get you started exploring more advanced usage of CloudForms.</description>
    </item>
    
  </channel>
</rss>