On 07/10/2015 10:03 AM, Haïkel wrote: > 2015-07-10 15:59 GMT+02:00 Ryan Brown <rybrown@xxxxxxxxxx > <mailto:rybrown@xxxxxxxxxx>>: > > On 07/10/2015 09:48 AM, Matthew Miller wrote: >> On Fri, Jul 10, 2015 at 07:52:29AM -0500, Major Hayden wrote: >>> Whenever I've spoken with customers about what they want from an >>> OS in a virtual machine, they want it to contain a small package >>> set that lets them run their automation on top of it (i.e. >>> Ansible, Chef, Puppet). Removing Python from that image would be >>> a serious curveball since most people expect to have Python >>> available on any system running yum/dnf. >> >> Yeah, I'm willing to back down on wanting to remove Python. > > +1 It'd be a lot of work (rewriting dnf/whatever, maintaining both > codebases, etc) for (relatively) little gain. Depends: for end-users, > it could mean a smaller bill each month on storage. Yes, but the engineer-hours to make that transition might better spent making the cloud image (or our docs, or whatever) awesome in other ways. > But I agree that we're not ready to drop python and it's *unlikely* > before a long time. I also agree that it shouldn't be a high/medium > priority task. > > As for dnf, there are discussion upstream to rewrite it in C, VMWare > has also written a drop-in replacement for dnf based on > hawkey/librepo that could be considered. > > The more problematic component is cloud-init. Indeed. CoreOS has a sorta-ish-done cloud-init written in go, but it's nowhere near feature complete last I checked. -- Ryan Brown / Software Engineer, Openstack / Red Hat, Inc. _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
