October 2018 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

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

[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

scap-security-guide rebuild problem
by aleksander.baranowski 04 Oct '18

04 Oct '18

Hi, I recently tried to rebuild: http://ftp.scientificlinux.org/linux/scientific/7.5/SRPMS/vendor/scap-secur… or CentOS: http://vault.centos.org/7.5.1804/updates/Source/SPackages/scap-security-gui… or http://vault.centos.org/7.5.1804/updates/Source/SPackages/scap-security-gui… and failed miserably :(. Steps to reproduce: ```bash sudo yum install @development wget libxslt openscap-scanner python-lxml cmake -y wget http://ftp.scientificlinux.org/linux/scientific/7.5/SRPMS/vendor/scap-secur… rpmbuild --rebuild scap-security-guide-0.1.36-10.sl7_5.src.rpm ``` Or with mock ``` mock scap-security-guide-0.1.36-10.sl7_5.src.rpm ``` The patch that breaks build is scap-security-guide-0.1.39-fix-failing-rules-for-PCI-DSS-DISA-UGSCB.patch. It has number 12 in the spec file. Is there anything that I'm missing? Unfortunately, I'm unable to find scap-security-guide on CentOS CBS, so I'm clueless. Bests, Alex

3 2

CERN Dojo in 2 weeks: Registration closes soon
by Rich Bowen 03 Oct '18

03 Oct '18

A reminder: The CERN Dojo will be held in Meyrin, Switzerland, on October 19th, and registration closes soon, as we have to issue security badges for all attendees. Attendance is free, but you must register to get in the front door. We'll have a full day of deep-dive CentOS content, in the midst of one of the most famous research facilities in the world. You don't want to miss it! http://cern.ch/centos See you at CERN! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Ohio LinuxFest next weekend
by Rich Bowen 03 Oct '18

03 Oct '18

Next weekend, CentOS will be sponsoring Ohio LinuxFest, and will have a table there. If you expect to be at OLF, and can spare an hour, or even a half hour, to sit at the table and answer questions, it would be a great help to me. Please have a look at the schedule - https://ohiolinux.org/schedule/ - and let me know what time(s) you might be able to spend at the table. For your convenience, I've made a list of available times here: https://docs.google.com/spreadsheets/d/1TqTqaLoswMYzyfvQCnzjkVazlQkP87CCKBS… Thanks, and I hope to see some of you in Columbus. --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

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

CFP for FOSDEM Dojo closes next week.
by Rich Bowen 02 Oct '18

02 Oct '18

The Call for Presentations for the FOSDEM Dojo - https://wiki.centos.org/Events/Dojo/Brussels2019 - closes next weekend. And, so far, it's looking pretty grim, with only THREE submissions. If you anticipate being at FOSDEM, and would like to present at our annual FOSDEM Dojo on topics relevant to CentOS or Fedora, please consider submitting a talk: https://goo.gl/forms/XkXbC2AZBgKvfDNF2 Please see https://wiki.centos.org/Events/Dojo/Brussels2018 for some idea of what kind of talks we had last year. But we're also asking the Fedora community to submit talks this year. --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel October 2018