Description of problem: Currently depending on the client status.. deltacloud will report either 1. a valid ip 2. a mac addr 3. a vnc add (rhevm) Deltacloud has fixed a bug that indicates and differentiates the type. Aeolus should only return a valid ip or some text indicating a valid ip is not reported from the instances This will help reduce the confusion around ip addr and instances.. People sshing into rhevm clusters..etc..
From https://issues.apache.org/jira/browse/DTACLOUD-143 -- <public_addresses><address port='5902' type='vnc'>qeblade27.rhq.lab.eng.bos.redhat.com</address></public_addresses> <private_addresses></private_addresses> So the type='vnc' is key. I'll look at what we get for an instance IP, and I think we should discard anything that isn't that. (Unless we want to track MACs or VNC addresses separately, which might be a nice enhancement.)
On list: http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-February/008855.html
Pushed to master: commit acd8031878cbabcef121646e61be6388c4e6d52f Author: Matt Wagner <matt.wagner> Date: Tue Feb 14 16:03:24 2012 -0500 BZ 790516 - Only accept ipv4, hostname addresses for instances Deltacloud labels 'vnc' and 'mac' addresses; don't set them as instance addresses! (There is no 'ipv6' type currently.) Resolves https://bugzilla.redhat.com/show_bug.cgi?id=790516
acd8031 (maint 61e2cd2) in aeolus-conductor-0.8.0-31
verified in [root@qeblade31 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-0.8.0-35.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch