On Thu, Apr 5, 2018, at 4:57 PM, Jeremy Stanley wrote:
> On 2018-04-05 14:35:27 +0000 (+0000), Jens Harbott wrote:
> > 2018-04-04 2:33 GMT+00:00 David Moreau Simard <dmsim...@redhat.com>:
> > > It won't be very exciting but we really need to do one of the
> > > following two things soon:
> > >
> > > 1) Ansiblify control plane 
> > > 2) Update our puppet things to puppet 4 (or 5?)
> > >
> > > Puppet 3 has been end of life since Dec 31, 2016. 
> > >
> > > The longer we draw this out, the more work it'll be :(
> > >
> > > : https://review.openstack.org/#/c/469983/
> > > : https://groups.google.com/forum/#!topic/puppet-users/IdutL5FTW7w
> > I agree and would vote for option 1), that would also seem to blend
> > well with upgrading to Xenial. Avoid having to invest much effort in
> > making puppet things work for Xenial, like we just discovered would be
> > needed for askbot.
> It's not immediately clear to me how rewriting numerous Puppet
> modules in Ansible avoids having to invest much effort... or is it
> the case that a lot of the things we're installing now have
> corresponding Ansible modules already? Has anyone skimmed through
> and figured out how many of those seem supported by the existing
> Ansible ecosystem vs how many we'd have to create ourselves?
> Jeremy Stanley
The puppet modules are already tested with puppet-apply and beaker on Xenial.
There should be very little if any effort to ensure they work on Xenial. It is
a bit hard for me to imagine that a complete rewrite would be easier.
OpenStack-Infra mailing list