| cgeorges | should the line at https://opendev.org/openstack/puppet-glance/src/branch/master/manifests/api.pp#L425 be updated so that it is up to date with the multistore backends? https://opendev.org/openstack/puppet-glance/src/branch/master/manifests/backend/multistore looks like vsphere should be removed and s3 added? using s3 as the backend type in glance::api::enabled_backends | 04:34 |
|---|---|---|
| cgeorges | fails because of this | 04:34 |
| opendevreview | Takashi Kajinami proposed openstack/puppet-glance master: Allow s3 backend https://review.opendev.org/c/openstack/puppet-glance/+/935034 | 05:09 |
| opendevreview | Takashi Kajinami proposed openstack/puppet-glance master: Drop remaining logic of VMWare backend https://review.opendev.org/c/openstack/puppet-glance/+/935035 | 05:09 |
| tkajinam | cgeorges, ^^^ so noone has used really the s3 backend support we re-added some time ago | 05:09 |
| tkajinam | I'm not too sure about status of actual s3 backend implementation in glance though. It was dropped because of no maintainer, and was readded because some people "are committed" to maintain it and then they immediately left | 05:13 |
| tkajinam | I reached out them again a few years back and they said they will be commited again but I've not seen ANY activity by then since then, for 2 years | 05:13 |
| tkajinam | by *them* | 05:14 |
| tkajinam | that's basically out of our scope but I personally discourage using it | 05:14 |
| cgeorges | we were messing with this in our development environment to see the possibility of using s3 for a moment for some testing and ran into this, thought i should report it thanks tkajinam | 05:18 |
| cgeorges | is there a specific reason you discourage its usage tkajinam? | 05:27 |
| tkajinam | cgeorges, because I've not seen people actively maintaining the driver ( here I mean the actual driver implementation in glance_store) for a few years | 08:40 |
| tkajinam | for example it has not been tested in CI for very long period | 08:42 |
| tkajinam | https://review.opendev.org/c/openstack/devstack/+/934307 | 08:42 |
| tkajinam | there seems to be some recent works to address the ci coverage concern, though. you might want to check status of the driver with glance folks | 08:42 |
| tkajinam | https://docs.openstack.org/glance_store/latest/user/drivers.html | 08:43 |
| tkajinam | the driver in this list hasn't been involved with the community for some time. he said he will get someone to replace him but I've never seen any update for 2-3 years | 08:44 |
| tkajinam | "the maintainer" instead of the driver, I mean | 08:44 |
| d1nuc0m | Hi tkajinam I guess this might be interesting - as of early 2025 no more official builds of Open Source Puppet (https://www.puppet.com/blog/open-source-puppet-updates-2025) | 09:14 |
| d1nuc0m | I haven't been active on IRC lately, sorry if you've already discussed it | 09:14 |
| tkajinam | d1nuc0m, no, not yet. thanks for raising it | 09:22 |
| tkajinam | The new development license is an EULA that allows developers free access to our hardened Puppet releases (up to 25 nodes). Capacities higher than 25 nodes will require a Puppet Labs Support Commercial License. We will share more details on this new license option in early 2025. | 09:23 |
| tkajinam | hmm I'm a bit confused by that message. so are they making puppet effectively closed source (which allows access upon EULA) ? | 09:28 |
| tkajinam | or are they still keep the code itself open ? | 09:28 |
| tkajinam | s/are they/will they/ | 09:28 |
| d1nuc0m | tkajinam, no, they'll keep the "base" Puppet open as Open Source Puppet, and release a commercial product ("hardened" Puppet) based on OSP | 09:29 |
| d1nuc0m | It's more clear on Reddit, where the devs commented it https://www.reddit.com/r/Puppet/comments/1glrhz5/open_source_puppet_updates_2025/ | 09:29 |
| tkajinam | ah, ok | 09:29 |
| tkajinam | so what we may loose is free rpm/deb packages of puppet provided by puppet labs | 09:29 |
| d1nuc0m | Yes, no more official binary builds | 09:30 |
| d1nuc0m | Source-only releases | 09:30 |
| tkajinam | the decision may depend on ones by distros I guess. At this moment RDO and Ubuntu releases their puppet packages | 09:30 |
| d1nuc0m | Yes, and also on Vox Pupuli, maybe they might be interested in providing builds to ease collaboration with OSP | 09:31 |
| d1nuc0m | As I don't see why should devs be willing to contribute directly to hardened Puppet | 09:32 |
| tkajinam | yeah | 09:32 |
| d1nuc0m | Anyway thanks, I just wanted to give a heads up | 09:33 |
| tkajinam | d1nuc0m, thank YOU. we have to keep our eyes on their changes and things happening upon that announcement | 09:33 |
| tkajinam | tobias-urdin, ^^^ just in case you are not aware of this | 09:34 |
| d1nuc0m | Btw, you might be interested in monitoring #voxpupuli on Libera (as they don't have an archive) and Foreman's community - these are two communities that are impacted by the announcement | 09:35 |
| tkajinam | My own opinion at this moment is that we may continue our project as long as OSP is available and distributions provide packages of these. | 09:36 |
| tkajinam | d1nuc0m, thanks. will do | 09:36 |
| tkajinam | I used to have access to puppet slack but I lost it when I left my prev. company and I don't know if I can contact any of the admins to ask them to reset my account. | 09:36 |
| tkajinam | Just a note. We have to update all integration tests to use distro packages instead of puppetlabs' builds | 09:38 |
| d1nuc0m | tkajinam, there have been some issues with Puppet slack afaik https://www.reddit.com/r/Puppet/comments/1g5xl0v/perforce_takes_over_independent_slack_community/ | 09:54 |
| tobias-urdin | tkajinam: d1nuc0m thanks for the heads up! | 12:36 |
| d1nuc0m | tobias-urdin, you're welcome :) | 12:50 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!