devel September 2018

devel@lists.centos.org

24 participants
25 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

LinchPin v1.6.2 (Update Release) is now available
by Clint Savage 01 Nov '18

01 Nov '18

We are happy to announce the release of LinchPin v1.6.2 today! (Happy Day!) This release has the following enhancements: * Debug mode #650 * Add ability to provision additional disks for libvirt #639 / #500 * Use workspaces with linchpin fetch #644 / #618 / #619 * Create separate workspaces for each provider / use case #669 * Allow Repos and Packages to be installed (beaker provider) #658 / #651 This release fixes the following bugs: * Parsing JSON for hook using ansible-playbook extra vars breaks LinchPin v1.5.4 #659 (Fixed by #664) * linchpin validate fails when using 'type' instead of 'role' #677 (Fixed by #680) * Passing Openstack credentials only with environment variables fails #682 (Fixed by #683) This release adds/fixes testing: * Add inventory_gen unit tests #656 * Remove print statement that caused AWS inventory gen tests to fail #691 The official release notes are available at https://github.com/CentOS-PaaS -SIG/linchpin/releases/tag/v1.6.2 This update is available via PyPI: https://pypi.org/project/linchpin/ If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues). Cheers, Clint Savage, Release Manager Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin (freenode) P.S. As part of the improving the release process for LinchPin, releases should be coming out at regular intervals (currently, ~3 weeks). Hopefully, this should help innovation and fix issues much more quickly.

1 2

Re: [CentOS-devel] [CentOS-docs] Authorization to use CentOS logo in GNOME Boxes
by Karsten Wade 01 Nov '18

01 Nov '18

On 09/19/2018 03:35 AM, Pablo Sebastián Greco wrote: > From someone who doesn't know anything about design/legal, what is the > difference between this instance and what was done in point 7.3 of the > link (7.3. For special sub-projects)? Essentially similar, in that specific permission was granted and a specific logo was prepared. In this case, the permission has been requested and there is not a corresponding logo prepared on the ArtWork page. > BTW, that is the logo only; There are two aspects here: 1. Should the project allow for the graphical logo to be used without the wordmark? 2. If yes to 1, the project should adjust one or both guidelines to make it explicit what can and cannot be done. For #1 it may be that we want to do so for various cases, but there may be reasons and risks we are not aware of in using the logo stand-alone in various situations. For this I am seeking expert advice. As it happens, the trademark guidelines do allow for some uses of just the logo, point 5 here: https://www.centos.org/legal/trademarks/#acceptable-uses But there is not a corresponding graphic and how-to on the ArtWork page. What I want to do is i) as quickly as we can resolve the question of permission for GNOME so they can move on with their development, and ii) fix any actual or perceived inconsistencies between the trademark guidelines and the logo usage guidelines. Best regards, - Karsten -- Karsten Wade | Community Architect | @quaid Red Hat Open Source and Standards (OSAS) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://osci.io gpg: AD0E0C41 | https://red.ht/sig

3 4

Azure cli in cbs ?
by Karanbir Singh 08 Oct '18

08 Oct '18

Hi, There was some movement towards getting the Azure cli ( az ) into a cbs repo, any news on that ? Regards -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

2 2

CentOS Community Container Pipeline: re-architecture migration window
by Bamacharan Kundu 03 Oct '18

03 Oct '18

Hi, Since last few months, we were working on re-architecturing the CentOS Community Container Pipeline Service to make https://registry.centos.org as a stable and reliable source for CentOS based container images. We are now done with the changes for better throughput and stability. We are working on deploying the new service in production in coming weekend (between 28th Sep 2018- 1st Oct 2018). During this time service will be in maintenance mode. We will not be building new images for registry.centos.org. Existing images will not be updated based on RPM, or git source updates. However, during this migration registry.centos.org will be available to pull images from. We are trying to make sure the down time for CentOS Community Container pipeline service is minimal. Service: https://registry.centos.org Maintenance window: Service will not have downtime Impact: Users will be able to pull images from https://registry.centos.org Service: CentOS Container Community Pipeline Service Maintenance window: 28th Sep 2018 to 1st Oct 2018 (We are working on to make it minimal) Impact: PRs to https://github.com/centos/container-index will not be merged and no image updates are pushed to registry.centos.org. Sorry for the inconvenience, we will keep posted. Regards Bama Charan Kundu

1 1

Problems with qemu-img when generating Vagrant images
by Laurentiu Pancescu 02 Oct '18

02 Oct '18

Hello everyone, we switched from using qemu-img from CentOS 7.x to qemu-img-ev from the Virt SIG several months ago, to allow us to generate Hyper-V images. My attempts to build Vagrant images are failing the automated tests since the beginning of July, apparently due to corrupt filesystems. I see XFS metadata corruption in the CentOS 7 images when using qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6 images.[1] The distro installer runs just once and the resulting disk image is converted by Image Factory to different formats, depending on the virtualization target. Since the VirtualBox images are working as expected, while the libvirt images don't even boot due to filesystem corruption, I would assume that the installation produces a valid image, but the conversion of the disk images for libvirt-kvm fall prey to bugs in qemu-img-ev and the stock qemu-img. If anyone has the possibility to test with VmWare or Hyper-V, please write me off-list. I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real, were already fixed upstream - would it be possible to use a newer version than what qemu-img-ev provides? We reverted to using the EL7 qemu-img, but this still produces broken libvirt images and wețd have to drop the Hyper-V images as well. Any help or suggestions are appreciated. Best regards, Laurențiu [1] https://people.centos.org/bstinson/vagrant/c6-vagrant.png

2 4

SIG reports - October newsletter
by Rich Bowen 01 Oct '18

01 Oct '18

I've begun to draft the October newsletter on blog.centos.org If your SIG would like to report anything to the broader CentOS community, please do let me know what you'd like to say. Or, if you'd like to edit it yourself, please go right ahead and make your edits directly in my draft. If there's other content you'd like to contribute to the newsletter, please do let me know. The centos-promo list is the best place to discuss your newsletter ideas. The deadline for content is end of day, October 1st. If you've not edited anything in the blog before: Blog logins are tied to your CentOS account. After you've logged into the blog editing interface once - https://blog.centos.org/wp-admin - just let me know, and I can add you to the Editors group. Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 2

ecryptfs - bug reported
by lejeczek 01 Oct '18

01 Oct '18

hi guys I've reported this - https://bugs.centos.org/view.php?id=15160 - a while ago. I'd like to ask if there is anybody looking into this? many thanks, L.

2 2

[ppc64le] Request for publishing sensu in ppc64le opstools
by Michael Turek 25 Sep '18

25 Sep '18

Hello, Trevor Vardeman <Vorrtex>, Adam Kimball <baha>, and myself <mjturek> have been looking into TripleO container builds for ppc64le. This led to finding some missing dependencies. The current one we're struggling with is sensu. It seems like all of the dependencies for running sensu are published in ppc64le-opstools [0]. Additionally, the sensu package itself is noarch. Is there anything we could do to get this package published? Thanks! Mike Turek <mjturek> [0] http://mirror.centos.org/altarch/7/opstools/ppc64le/sensu/

1 0

mirrorlist code updated / SIGs and AltArch support rolled-in
by Fabian Arrotin 24 Sep '18

24 Sep '18

<paste> Recently I had to update the existing code running behind mirrorlist.centos.org (the service that returns you a list of validated mirrors for yum, see the /etc/yum.repos.d/CentOS*.repo file) as it was still using the Maxmind GeoIP Legacy country database. As you can probably know, Maxmind announced that they're discontinuing the Legacy DB, so that was one reason to update the code. Switching to GeoLite2 , with python2-geoip2 package was really easy to do and so was done already and pushed last month. But that's when I discussed with Anssi (if you don't know him, he's maintaining the CentOS external mirrors DB up2date, including through the centos-mirror list ) that we thought about not only doing that change there, but in the whole chain (so on our "mirror crawler" node, and also for the isoredirect.centos.org service), and random chat like these are good because suddenly we don't only want to "fix" one thing, but also take time on enhancing it and so adding more new features. The previous code was already supporting both IPv4 and IPv6, but it was consuming different data sources (as external mirrors were validated differently for ipv4 vs ipv6 connnectivity). So the first thing was to rewrite/combine the new code on the "mirror crawler" process for dual-stack tests, and also reflect that change o nthe frontend (aka mirrorlist.centos.org) nodes. While we were working on this, Anssi proposed to also not adapt the isoredirect.centos.org code, but convert it in the same python format as the mirrorlist.centos.org, which he did. Last big change also that was added is the following : only some repositories/architectures were checked/validated in the past but not all the other ones (so nothing from the SIGs and nothing from AltArch, so no mirrorlist support for i386/armhfp/aarch64/ppc64/ppc64le). While it wasn't a real problem in the past when we launched the SIGs concept, and that we added after that the other architectures (AltArch), we suddenly started suffering from some side-effects : * More and more users "using" RPM content from mirror.centos.org (mainly through SIGs - which is a good indicator that those are successful, which is a good "problem to solve") * We are currently losing some nodes in that mirror.centos.org network (it's still entirely based on free dedicated servers donated to the project) To address first point, offloading more content to the 600+ external mirrors we have right now would be really good, as those nodes have better connectivity than we do, and with more presence around the globe too, so slowly pointing SIGs and AltArch to those external mirrors will help. The other good point is that , as we switched to the GeoLite2 City DB, it gives us more granularity and also for example, instead of "just" returning you a list of 10 validated mirrors for USA (if your request was identified as coming from that country of course), you now get a list of validated mirrors in your state/region instead. That means that then for such big countries having a lot of mirrors, we also better distribute the load amongst all of those, which is a big win for everybody - users and mirrors admins - ) For people interested in the code, you'll see that we just run several instances of the python code, behind Apache running with mod_proxy_balancer. That means that if we just need to increase the number of "instances", it's easy to do but so far it's running great with 5 running instances per node (and we have 4 nodes behind mirrorlist.centos.org). Worth noting that on average, each of those nodes gets 36+ millions requests per week for the mirrorlist service (so 144+ millions in total per week) So in (very) short summary : mirrorlist.centos.org code now supports SIGs/AltArch repositories (we'll sync with SIGs to update their .repo file to use mirrorlist= instead of baseurl= soon) we have better accuracy for large countries, so we redirect you to a 'closer' validated mirror </paste> So that means that now the following combination are possible through mirrorlist: testing base os for aarch64 : curl 'http://mirrorlist.centos.org/?release=7&arch=aarch64&repo=os' testing RDO Rocky release for ppc64le : curl 'http://mirrorlist.centos.org/?release=7&arch=ppc64le&repo=cloud-openstack-r…' And so on .... :) There is no "pressure" to update your -release pkg to switch from baseurl=mirror.centos.org to mirrorlist=mirrorlist.centos.org but I just wanted to inform that it's now "live" and you can start thinking about that change, and why not with an update pkg just pushed to -testing (aka buildlogs.centos.org) and then move to that later ? Cheers, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2018