devel

devel@lists.centos.org

2 participants
4652 discussions

Hurricane Florence and CentOS CI/CBS
by Brian Stinson 12 Sep '18

12 Sep '18

Hi All, Some of you may know that the CentOS Community Build System, and CentOS CI Infrastructures are hosted in Raleigh, North Carolina. I wanted to take this opportunity to let all of you know that outages are possible (but not expected) in the coming days as Hurricane Florence makes its way toward the US East coast. We are confident in the precautions taken by our datacenter vendor, and in the preparedness plans by our DC operations team. If there happen to be outages, we will work to get things back as soon as we can. Cheers! -- Brian Stinson CentOS Infrastructure Team

1 0

September newsletter
by Rich Bowen 10 Sep '18

10 Sep '18

The September newsletter has been published - https://blog.centos.org/2018/09/centos-pulse-newsletter-september-2018-1804/ You'll notice (if you make a habit of reading the newsletter) that this edition has moved from the wiki to the blog, for various reasons discussed over on the promo mailing list. I will begin drafting the October newsletter later today. If you'd like to participate in that process, please let me know, so that we can get you added to the editors list. blog.centos.org authenticates against your existing CentOS account, so you already have an account on there, we just need to add you to the right ACL. --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

[RFE] Distinguished volume ids between different kinds of ISOs
by Fabiano Fidêncio 10 Sep '18

10 Sep '18

The reasoning behind this request is to have more accurate data in osinfo-db that could be used, for instance, by GNOME Boxes and virt-manager. Currently, as the "Everything", "DVD", "Minimal" and "Network" ISOs have exactly the same Volume id (CentOS 7 x86_64) we can't distinguish the ISOs the user have in order to help them to properly pick up whatever is better for their needs. The way we have been currently working this around is by having the ISO's volume size (which are usually different) combined with their Volume id. This approach, however, won't work well in CentOS case as we're offering the "Rolling" ISOs to the users and their volume size will change on every new addition/removal. I've also noticed that for the Live ISOs they volume id is already distinguished (CentOS-7-x86_64-LiveKDE-* vs CentOS-7-x86_64-LiveGNOME-*) thus the RFE to see whether doing the same for the other ISOs would be something appealing to CentOS. This conversation can also be done in https://bugs.centos.org/view.php?id=15260 in case the developers prefer that way. Best Regards, -- Fabiano Fidêncio

1 0

HPC Sig
by Paul Graydon 06 Sep '18

06 Sep '18

Hi all, There was some email conversation on this list a couple of weeks ago about the HPC SIG, but it didn't really seem to go anywhere or have any solid conclusion, other than "join #centos-devel". Between some freenode instability/spam protections etc. some issues with my usual persistent session, and just sheer quantity of conversation happening there, it's somewhat hard to figure out where anything sits. I didn't see any obvious signs of further conversation there, but there's a good chance I missed it. If there was further conversation and someone would be able to point me towards it off list, I'd love to read it. As a cloud provider that provides high spec bare metal servers to customers, we're finding a lot of usage and interest from customers with various forms of HPC workloads, everything from GROMACs to Hadoop and beyond. CentOS, likewise, continues to be a popular distribution for our customers, across every hardware and virtual machine specification. If there's ideas on how to make HPC better on CentOS, I'd love to be part of the conversation, and see if there are opportunities to help. Paul

3 5

Thursday SIG day at CERN: YOU MUST REGISTER
by Rich Bowen 06 Sep '18

06 Sep '18

Hi, folks, If you're planning to attend the THURSDAY portion of the Dojo at CERN - the day that's devoted to SIG and Board discussions - you MUST register in order to gain physical access to the site, due to CERN's security policies. You may register here: https://indico.cern.ch/event/755673/ See you at CERN! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

4 4

Introduction
by Vipul Siddharth 06 Sep '18

06 Sep '18

Greetings everyone, I am Vipul, an associate software engineer at Red Hat. I have been contributing to Fedora and Gluster for a while now and have recently joined Fedora&CentOS Infra Team. As I am a **very** new addition to the team, I yet have to discover different areas and projects to decide what I will be working on. Thankfully Brian [0] is helping me fill the gaps. I know my way around Python, Bash, Ansible and little bit of Jenkins. Using these (and learning more on the way), I am hoping to be of some help as soon as possible. You can know more about me at [1] Looking forward to getting involved in the community. Thank you [0]: https://wiki.centos.org/BrianStinson [1]: vsiddhar.me/about/ -- Vipul Siddharth Fedora | CentOS Red Hat

1 0

SIG updates for newsletter due
by Rich Bowen 04 Sep '18

04 Sep '18

I'm running very late on the September newsletter, due to travels. If your SIG has any updates that you'd like to share with the community, covering activity in August, please let me know ASAP. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

LinchPin v1.6.1 (bugfix) has been released
by Clint Savage 04 Sep '18

04 Sep '18

We are happy to announce that LinchPin v1.6.1 has been released. The following release fixes the following bugs: - Inventory is not correctly populated after provisioning with libvirt #540 (Fixed by #674 / #668) - No IPs are rendered in inventory file if auto_ip:no is set for openstack provider (Fixed regression in #596) One enhancement was added to this release: - Add linchpin validate command #647 The official release notes are available at https://github.com/CentOS- PaaS-SIG/linchpin/releases/tag/v1.6.1 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)

1 0

Cancelling the CBS meeting 03-Sep-2018
by Brian Stinson 03 Sep '18

03 Sep '18

Hi Folks, We'll cancel this week's CBS meeting and pick things up next week. Cheers! -- Brian Stinson

1 0

SecureBoot : rolling out new shim pkgs for CentOS 7.5.1804 in CR repository - asking for testers/feedback
by Fabian Arrotin 30 Aug '18

30 Aug '18

When we consolidated all CentOS Distro builders in a new centralized setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64, aarch64 and armhfp those days), we wanted also to add redundancy where it was possible to. The interesting "SecureBoot" corner case came on the table and we had to find a different way to build the following packages: - shim (both signed and unsigned) - grub2 - fwupdate - kernel The other reason why we considered rebuilding it is that the cert we were using has expired : curl --location --silent https://github.com/CentOS/sig-core-SecureBoot/raw/master/CentOS_7/kernel/SO… | openssl x509 -inform der -text -noout|grep -A2 Validity While technically it doesn't really matter for Secureboot itself, it was better to get a new key/cert rolled-in and use the new one for new builds. That's where it's interesting as because shim embeds the certs in the Machine Owner Key (MOK), and that each other component used in the boot chain is validated against that (so grub2 first, then kernel and kernel modules) that means that once deployed , the new shim would not be able to boot previous grub2/kernel. But there is a solution for that : instead of "embedding" only the new cert, we can have both the old one and new one, permitting us to still boot older kernels but also the new ones we'll build/push soon (built on the new build system), and that's what we used for that new shim package. That's where we'd like you (SecureBoot users) to give us feedback about that new shim pkg. It was already validated on some hardware nodes, passed some QA tests, but we'd prefer to have more feedback. Worth noting that such rebuild has also a patch that should fix an issue we had with shim not allowing to import key in MOK through mokutil (see https://bugs.centos.org/view.php?id=14050) How can you test ? If you're using UEFI with SecureBoot enabled , we have signed/pushed those pkgs to the CR repository (see https://wiki.centos.org/AdditionalResources/Repositories/CR) That repo is by default disabled, but following command would let you update shim : yum update shim --enablerepo=cr Then reboot and it should work like before, so validating the boot chain (while still using grub2/kernel packages signed with previous key) We'd appreciate feedback on this list, or #centos-devel on irc.freenode.net I'd like to thank Patrick Uiterwijk and Peter Jones for their help for the patch and validation for that shim -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel