devel

devel@lists.centos.org

4 participants
4668 discussions

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

[meeting] RDO meeting (2018-10-24) minutes
by Haïkel 24 Oct '18

24 Oct '18

============================== #rdo: RDO meeting - 2018-10-24 ============================== Meeting started by number80 at 15:01:23 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_10_24/2018/rdo_m… . Meeting summary --------------- * roll call (number80, 15:01:31) * reserve rdo-* namespaces on gitlab (number80, 15:12:03) * considering to move gerrit replication from github to gitlab (number80, 15:15:33) * AGREED: Allow reserving rdo-* namespaces on both gitlab and bitbucket (number80, 15:21:55) * ACTION: apevec reserve rdo-* namespaces on gitlab and bitbucket (number80, 15:23:50) * ACTION: number80 mail apevec and Duck about gitlab namespaces (number80, 15:24:48) * Booth volunteers for OpenStack Summit Berlin (number80, 15:25:19) * LINK: https://etherpad.openstack.org/p/berlin-summit-community-pod (number80, 15:27:14) * open floor (number80, 15:30:32) * python3 enabled status (number80, 15:31:18) * LINK: https://lists.rdoproject.org/pipermail/dev/2018-October/008952.html -> call for help on tempest plugins (chandankumar, 15:32:47) * new promotion pipeline running for puppet (fedora) (number80, 15:36:03) * easyfix project (number80, 15:42:13) * ACTION: PagliaccisCloud will start emails with Rain & Rich on possible 1st time contributor workshop at upcoming Red Hat Summit (PagliaccisCloud, 15:56:52) * ACTION: chandankumar to kick discusssion on merging efforts taken by tripleo rdo and openstack community to attract contributors (chandankumar, 15:56:55) * number80 again chairing next week (number80, 15:58:20) Meeting ended at 15:58:52 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to kick discusssion on merging efforts taken by tripleo rdo and openstack community to attract contributors * number80 * number80 mail apevec and Duck about gitlab namespaces * openstack * chandankumar to kick discusssion on merging efforts taken by tripleo rdo and openstack community to attract contributors * PagliaccisCloud * PagliaccisCloud will start emails with Rain & Rich on possible 1st time contributor workshop at upcoming Red Hat Summit People present (lines said) --------------------------- * number80 (70) * chandankumar (63) * amoralej (53) * PagliaccisCloud (23) * ykarel (9) * hitchover (7) * jpena (6) * tosky (5) * openstack (5) * rdogerrit (3) * vkmc (2) Generated by `MeetBot`_ 0.1.4

1 0

SIG reporting
by Rich Bowen 22 Oct '18

22 Oct '18

At the recent SIG day at CERN, we discussed more formal reporting from the SIGs to the broader community. In particular, we discussed quarterly reporting, covering the following topics: * Membership update (members added, removed. Chair changes.) * Releases in the most recent quarter (or most recent release, if none in that quarter) * Health report and general activity narrative. * Issues for the board to address, if any. So, this is 4 short paragraphs, to give the board, and the community, some idea of what the SIG is up to, and whether it is healthy. Not terribly onerous, but extremely valuable in discerning how our SIGs are operating. It was proposed that SIGs be arrange in a quarterly reporting schedule. I suggest the following schedule, starting in January of 2019: Group 1: Reports January, April, July, October * Core * Atomic * Config Management * PaaS * Software Collections Group 2: Reports February, May, August, November * Alt Arch * Cloud * NFV * Promo * Storage Group 3: Reports March, June, September, December * Artwork * Cloud Instance * OpsTools * Public CI * Virtualization I further propose that reports are due by the second Monday in the designated month. To this end, it is important that each SIG clearly designate a SIG chair, documented on your SIG wiki page. Some SIGs have this, and some do not. Some that have it are out of date, and the SIG needs to designate a chair again. Note that the chair is not necessarily a technical lead, they're just the person responsible for reporting - the voice of the SIG, if you will. If you have any questions or comments about this plan, please do speak up, so that we can work out any difficulties by January. Thanks. -- Rich Bowen: CentOS Community Manager rbowen(a)redhat.com @rbowen // @CentOSProject 1 859 351 9166

1 0

[SCLo SIG] new sclo-php*-php-ast packages available for testing
by Remi Collet 22 Oct '18

22 Oct '18

Yet another package available in centos-sclo-sclo-testing php-ast exports the AST internally used by PHP 7. php-ast is significantly faster than PHP-Parser, because the AST construction is implemented in C. However, php-ast may only parse code that is syntactically valid on the version of PHP it runs on. https://pecl.php.net/package/ast Can be used by Phan (PHP Static Anyalyser) https://packagist.org/packages/phan/phan For rh-php71 (EL-7 only) * sclo-php71-php-ast-1.0.0-1 For rh-php70 * sclo-php70-php-ast-1.0.0-1 Notices: Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

If you didn't attend yesterday's SIG day at CERN ...
by Rich Bowen 19 Oct '18

19 Oct '18

Yesterday at CERN we had a gathering of CentOS SIGs. We discussed changes that are coming in the CentOS infrastructure. We also discussed how SIGs can better engage with the larger CentOS community, and bring in broader participation from the user community, as well as from related projects (eg, how the Cloud SIG might attract participation from more IaaS platform projects.) I will be sending a longer report on the event once today's event is over. We had representation from only a handful of our SIGs, and we would like to understand why other SIGs did not attend, and what we might do differently next time to attract more of you to attend. To that end, I've made a very short survey that I would ask you to take 5 minutes to fill out if a) you're involved in one of our SIGs, and b) you did NOT attend our event yesterday. https://goo.gl/forms/A5P4yaxvduDDrw0T2 Thank you. -- Rich Bowen: CentOS Community Manager rbowen(a)redhat.com @rbowen // @CentOSProject 1 859 351 9166

1 0

Small service interruption : paste.centos.org
by Fabian Arrotin 09 Oct '18

09 Oct '18

Due to a HDD swap/replacement, we'll have to shut down a node, proceed with maintenance, and restart the server Migration is scheduled for """"Tuesday 9th October, 4:00 pm UTC time"""". You can convert to local time with $(date -d '2018-10-9 16:00 UTC') The expected "downtime" is estimated to ~20 minutes. Affected services: - some internal services for centos infra - https://paste.centos.org Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

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

Upcoming changes to downloading AltArch .iso images
by Anssi Johansson 08 Oct '18

08 Oct '18

Hi, this notice is for those who employ some sort of an automation to download AltArch (ie. aarch64, armhfp, i386, power9, ppc64, ppc64le) CentOS 7 .iso/.raw.xz images from mirror.centos.org. Those using a regular browser to download these images are not particularly affected, and you can continue to the next message. Previously, only main architecture .iso image downloads from mirror.centos.org were redirected to isoredirect.centos.org, which then displayed the user a list of nearby external mirrors. We will shortly extend this configuration to cover AltArch image downloads as well, ie. direct AltArch image downloads from mirror.centos.org will no longer be possible. mirror.centos.org will still serve .rpm downloads for all architectures as before. There are two reasons for the change. First, to save bandwidth from mirror.centos.org nodes directly managed by the CentOS Project. Most of these mirror.centos.org hosts are also used for seeding the 600+ external mirrors we have. By directing some of that .iso download traffic to external mirrors we can offer faster sync speeds for those external mirrors, and for people downloading individual rpms from mirror.centos.org. Second, most of those external mirrors offer faster download speeds to end users than what could be achieved by downloading from mirror.centos.org, so the users will benefit from this change as well. The above change will be implemented some time between the releases of RHEL 7.6 and CentOS 7.6.18xx, so that external mirrors syncing CentOS 7.6.18xx content would not need to fight for bandwidth between AltArch .iso downloaders. The other change, which has already been implemented, is related to how isoredirect.centos.org behaves when accessed with curl or wget. If you now do a "wget http://isoredirect.centos.org/altarch/7/isos/i386/CentOS-7-i386-Everything-…", isoredirect will notice that you are trying to download the file and will redirect the request to the nearest external mirror. If you access the same URL with a regular browser, you will see a list of nearby mirrors from which you can pick your favourite mirror. wget will follow redirects by default, but curl needs a --location switch to follow redirects. If a filename is not specified, you will get a list of mirrors regardless of the browser used. So, combining the effects of the above two changes: If you currently use some sort of a script that downloads AltArch .iso images from mirror.centos.org, those requests will soon be served by external mirrors instead of mirror.centos.org. In the case of wget you will only see one additional request and you probably don't need to change anything, but if you use curl, you must add the --location switch to curl to follow the redirect issued by isoredirect.centos.org. If you want to eliminate one redirect, you can change mirror.centos.org to isoredirect.centos.org in your script. The rest of the URL is the same, ie. /altarch/<release>/isos/<arch>/<filename.iso or .raw.xz> As an aside, even though mirror.centos.org nodes are managed by the CentOS Project, those servers and their hosting are donations from various organizations. If you think your organization could donate an additional server to share the load and to give us better geographical coverage, please see https://wiki.centos.org/Donate If you have questions regarding this change, please let me know. Thanks!

1 0

(How) do others SIGs provide kernel modules?
by Niels de Vos 07 Oct '18

07 Oct '18

Hi, There is an oustanding request for the Storage SIG to package and provide VDO: > VDO (which includes kvdo and vdo) is software that provides inline > block-level deduplication, compression, and thin provisioning > capabilities for primary storage. Both components ate packaged in a Fedora COPR, and a reasonable .spec file is provided by the upstream project. However, the kernel module is packaged with DKMS. This would result in building the module during RPM installation, and possibly on reboot after a kernel update. There is a dkms package in the CBS (by Haïkel), but it is only tagged with -candidate. I would like to know what the reasons were to not consumer it for a release. It seems that there is one (that I could find) package in the CBS that provides a kernel modules (openafs-kmod by Jonathan). It utilizes DKMS as well, but also never made it a repository for release. Then there is the kmod package (build by Lokesh). This is an alternative way of building kernel modules. It compiles the module in the CBS, for a specific (sortof major) kernel version. The resulting RPM can then be installed without the need to build it again. My personal preference would be to provide kernel modules with the kmod practise. But I love to hear opinions and experiences from others. Thanks, Niels

4 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel