On 09/27/2012 06:02 PM, Greg Blomquist wrote: > 1) Requires setting up and configuring a configsever. In all > honesty, this is pretty straightforward: install from brew RPM and > run aeolus-configserver-setup on the same box where conductor > is running. > > 2) Requires deploying to a non-EC2 back end (e.g., rhev). This > can be a pain b/c not all of us have access to a rhev cluster, > and those that do may not have configured conductor to deploy > to rhev. Even if you know of a rhev cluster, you also need > access to the rhevm admin UI so that you can get the IP address > from the launched instances and validate the launch worked > correctly and the configurations succeeded.
hi guys, I've a working ce-1.1-latest-puddle deployment which can be used for the purpose, it's also rhev/vmware backed already I'm in QE, point me at the brew build you want to test so we can collaborate on this. I'm on IRC as 'giulivo' -- Giulio Fidente, gpg key id 08D733BA
