devel October 2018

devel@lists.centos.org

37 participants
26 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

python-jwt in RHEL's addons and CentOS
by Ken Dreyer 01 Nov '18

01 Nov '18

Red Hat recently shipped python-jwt in http://access.redhat.com/errata/RHEA-2018:1032 This went into the "High Availability" and "Resilient Storage" add-ons of RHEL, not the usual RHEL Base/Optional/Extras. I was wondering why CentOS has this package in its base repositories now. Does CentOS 7 include RHEL's HA addon or the Resilient Storage addon? - Ken

3 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

[CentOS PaaS SIG]: Origin v3.11 rpms available for testing
by Daniel Comnea 31 Oct '18

31 Oct '18

Hi, We would like to announce that OKD v3.11 rpms are available for testing at [1]. As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies. And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo: 1. in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed) Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues. On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos. The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues) Thank you, PaaS SiG team [1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/

6 10

What is the preferred approach to get golang >= 1.9.4 in buildroots in the CBS?
by Niels de Vos 31 Oct '18

31 Oct '18

Hi, It seems that the golang version (1.8) in the CentOS build (base?) repository is not recent enough to build one of the Gluster components. GlusterD2-5.0 needs golang >= 1.9.4. There is a build of golang-1.10.2-1.el7 in the CBS, but that is only for x86_64, and I would need a version that has ppc64le and aarch64 as well. Early on, golang was included in CentOS Extras, is that a possible location to keep a more recent version? Thanks, Niels

2 3

RSB filling is enabled for CentOS 7 Kernel?
by Veetil, Vyshnav 30 Oct '18

30 Oct '18

Hi All, We ran the spectre meltdown checker tool provided by: https://github.com/speed47/spectre-meltdown-checker. And it says that we are still vulnerable to variant #2 since RSB filling is not enabled in our kernel When we googled, the following bugzilla from RH suggests that it is enabled by default: https://bugzilla.redhat.com/show_bug.cg ... 2018-15572 When I was checking the source code of the latest CentOS kernel ,i don't see this feature flag set anywhere - X86_FEATURE_RSB_CTXSW. Could you please tell us ,If the Latest CentOS kernel supports RSB filling or not ?! Regards, Vyshnav

2 1

multistage booting and grubby
by Element, Paul-Emile 30 Oct '18

30 Oct '18

Hi, We are working with a system configure to boot using tboot Using grub2 and multiboot2, we have grub2 booting tboot and then booting centos. Grub2 fully supports this scenario and it works fine. The problem we have is that some centos packages use grubby to modify the boot configuration / boot parameters. Grubby does not appear to have any support for this, and so all invocations of grubby end up doing nothing and fail silently. Question is, would you know if there is any plan to add support for multiboot2 in an upcoming version of grubby? Thanks, Paul-Emile

1 0

Upcoming changes to git.centos.org are now in staging
by Jim Perrin 26 Oct '18

26 Oct '18

In August, the CentOS Project and Fedora announced the intention to combine their dist-git sources, and since then Fabian Arrotin of CentOS and Patrick Uiterwijk of Fedora have worked to make that happen. Last week at the CERN dojo, they demonstrated this work, and today we’d like to welcome community testing of it. We’ll be keeping this content updated, so you'll be able to continue to track sources appropriately. You can help us by testing the new system, providing feedback, and contributing additional tooling to help improve the overall state of the project. Structure: Currently git.stg.centos.org and src.stg.fedoraproject.org are linked via RepoSpanner[1], and sharing common repositories. Packagers for the roughly 6700 common packages in both communities will see the additional branches.. For the Fedora community, there should be no changes required for the day to day operation of dist-git or packaging. CentOS community members will note that the platform change to pagure brings a variety of new features, including a new API[2] , a new UI, pull requests, and issue tracking. The current tooling for CentOS sources will continue to work (after updating to the staging server) and we plan to add support for tooling for centpkg, which would mirror the functionality found in fedpkg. In the coming weeks we'll be putting out documentation around the expected uses for pull requests, and the issue tracking features within pagure, as we don't intend it to replace bugs.centos.org. Permissions and ownership: There are protections enabled to prevent either community from accidentally overwriting code from the other, so only CentOS community members will be able to push to c#-* branches, while only Fedora community members can push to f#*/epel#* branches. With the new dynamic ACL validation in place, CentOS SIG members will automatically get the rights to push on their specific branches. While the repositories and content are shared between the communities, authentication is not. To push to c# branches, you will have to authenticate against accounts.centos.org. Similarly Fedora community members will continue to authenticate against accounts.fedoraproject.org. 1. https://github.com/repoSpanner/repoSpanner 2. https://git.stg.centos.org/api/0/ -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

5 9

Cockpit on CentOS 7 bugs/issues
by Harry Mallon 26 Oct '18

26 Oct '18

Hi all, I am trying cockpit on CentOS 7. 1. Cockpit-system v176 install subscription-manager by default. This is very annoying on CentOS as I do not have a subscription and do not want one. 2. Cockpit-system v176 has cockpit-sosreport rolled into it. However, the rpm does not have the sos package required as it should do. Who makes the packages for the "extras" repo? Is there a better place to report these issues? Harry Mallon Harry Mallon Senior Software Engineer T+44 203 7000 989 60 Poland Street | London | England | W1F 7NT

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2018