Re: Supporting Ansible as another tool for ovirt infra mgmt

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2CJSCa5kfB0ILu2JVP8i3TauuEkNCqE1m Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, On 04/11/2016 05:38 PM, Barak Korren wrote: Help about the VM, you replied to this part (which unfortunately began off-list, my bad), thanks. The other part is tracking the features you need, to see if upgrading Foreman and using the work Misc pointed at could be a working solution. Because if an important feature is missing, then this path will not happen now. And then if it is a possible path, are you all willing to work on this migration? I only viewed Mailman as a proof of concept. I agree maintaining both systems sux. So that's why I'm talking about a possible migration. I guess if it fails then we'll be back to reintegrating MailMan in the current system and this is not that horrible. If it works we can work on converting the rest with the knowledge we gained. I'd be happy to help but clearly I would need some time and energy from people in the project. Other OSAS members could also give a hand. I've no idea about your workload, nor about the urgency of migrating Mailman. I think this is important to check our availability and will to invest on this. there. Probably. Nevertheless it seems most projects OSAS are in touch with are getting out of Puppet and I myself in other projects decided not to go into this solution after some comparison and XP collection. So you may understand I'd like to invest my time in something not totally ephemeral. But if this migration is rejected or postponed, I will. I'm new here :-), neither do I. Regards. --2CJSCa5kfB0ILu2JVP8i3TauuEkNCqE1m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" --2CJSCa5kfB0ILu2JVP8i3TauuEkNCqE1m--