<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>VIO on vUnhandledException</title>
		<link>https://fbuechsel.eu/tags/vio/</link>
		<description>Recent content in VIO on vUnhandledException</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
			<copyright>Copyright © 2013-2026, Frank Escaros-Buechsel; all rights reserved.</copyright>
		
		
			<lastBuildDate>Fri, 12 Mar 2021 20:36:45 +0000</lastBuildDate>
		
			<atom:link href="https://fbuechsel.eu/tags/vio/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Hooking into the RabbitMQ bus of VIO</title>
				<link>https://fbuechsel.eu/post/nfv/exposeviormq/</link>
				<pubDate>Fri, 12 Mar 2021 20:36:45 +0000</pubDate>
				<guid>https://fbuechsel.eu/post/nfv/exposeviormq/</guid>
				<description>&lt;p&gt;&lt;strong&gt;If you are using vCloud Director or vRealize Automation you will know that both products allow for custom extensibility via similar frameworks by being able to utilize a message bus to trigger workflows based on events. This blog post will explore how to achieve a similar outcome using VMware Integrated OpenStack.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;exposing-the-rmq-bus-to-external-sources&#34;&gt;Exposing the RMQ bus to external sources&lt;/h2&gt;&#xA;&lt;p&gt;By default the RabbitMQ bus is configured for internal consumption only in a VMware Integrated OpenStack deployment. The service is configured using ClusterIP which we can easily change over to NodePort using the following command.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
