<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Development on Forward or Reverse</title>
    <link>https://blog.wannemacher.us/categories/development/</link>
    <description>Recent content in Development 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/development/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>Foreman ESXi Installation Never Completes</title>
      <link>https://blog.wannemacher.us/posts/p540/</link>
      <pubDate>Fri, 21 Nov 2014 19:36:10 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p540/</guid>
      <description>In our environment we want to use Foreman to build our OCP hardware. It was working well except that the installation would repeatedly PXE boot to reinstall because Foreman would not know that the PXE portion was complete.
The standard notification code below was failing for some reason.
1 2  %post --interpreter=busybox --ignorefailure=true wget -O /dev/null &amp;lt;%= foreman_url %&amp;gt;   After running the unattended install in a Fusion VM so I could have console access I reviewed the install log and a misleading message from wget about the URL being bad.</description>
    </item>
    
    <item>
      <title>OpenZIS installation guide</title>
      <link>https://blog.wannemacher.us/posts/p516/</link>
      <pubDate>Fri, 31 Jan 2014 01:59:01 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p516/</guid>
      <description>I have spent a day or so trying to get the OpenZIS project up and running on a CentOS machine. A lack of updated instructions and an older code base made this process harder than I expected.
While I am still investigating if OpenZIS will meet my needs, I wanted to publish what I did as a reference to others who might try to install it. The doc is in my forked version of OpenZIS.</description>
    </item>
    
    <item>
      <title>Google Book Advanced Search Query Parameters</title>
      <link>https://blog.wannemacher.us/posts/p280/</link>
      <pubDate>Fri, 19 Mar 2010 02:15:17 +0000</pubDate>
      
      <guid>https://blog.wannemacher.us/posts/p280/</guid>
      <description>A reference for those working on Google book searches other than full text queries. Let me know if something is incorrect or missing.
&amp;lt;th&amp;gt; Values &amp;lt;/th&amp;gt;  &amp;lt;td&amp;gt; All of the words. &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; Exact phrase. &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; At least one of the words. &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; Without the words. &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; 0=AllBooks, 1=FullView, 3=Limited preview and full view, 4=Public domain only &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; One of &amp;quot;ALLTYPES&amp;quot;, &amp;quot;BOOKS&amp;quot;, &amp;quot;MAGAZINES&amp;quot; &amp;lt;/td&amp;gt;  &amp;lt;td&amp;gt; Empty for all languages otherwise a language code.</description>
    </item>
    
  </channel>
</rss>