Notifications between Aeolus components

Bryan Kearney bkearney at redhat.com
Wed Jan 23 18:16:22 UTC 2013


On 01/23/2013 01:14 PM, Mo Morsi wrote:
> On 01/22/2013 01:09 PM, David Lutterkort wrote:
>> On Wed, 2013-01-09 at 08:01 -0500, Bryan Kearney wrote:
>>>> +1. We tried AMQP / QMF before and it ended up being a pain. Introduced
>>>> another service / point of failure.
>>> Just thinking out loud... QMF is a pain but is dead now I think. if you
>>> do callbacks you have to buy off on alot of networking. Can you put
>>> image factory in EC2 and run Aeolous in house?
>
> Sorry Bryan, missed your question. Unfortunately not at the current
> time. imagefactory depends on oz which depends on libvirt which cannot
> be run in the cloud since we don't have virt-in-virt yet. There had been
> discussions at various points to support separating the imagefactory
> frontend / backends so as to facilitate things like this but that never
> got implemented (and you'd potentially run into firewall problems in
> this scenario as well).
>
> I had discussed this w/ clalance in the context of changing the
> tdl-launch utility [1] to use Oz directly but that looks like it won't
> be feasible at the current time.


Well, just thinking out loud.. can any component go into the cloud which 
may not be in the same VPN space?


-- bk



More information about the aeolus-devel mailing list