devel

devel@lists.centos.org

4 participants
4640 discussions

SIG announcements for monthly newsletter?
by Rich Bowen 05 Nov '18

05 Nov '18

If your SIG would like to have any kind of announcement in the monthly newsletter, it is currently in draft on the blog, and I hope to send it out just as soon as I have the schedule selected for the Dojo at FOSDEM - *hopefully* tomorrow. So if you want to insert something into the newsletter, you have about 24 hours. Thanks! --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

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

Point-release Freeze is Active
by Brian Stinson 01 Nov '18

01 Nov '18

Hi Folks, As is usual, we freeze the SIG Sign + Push process as part of preparing for a point release. This helps us once CR is ready (it isn't yet, though) so that we can seed it quickly in CBS to build against. The Point-release Freeze does not affect content moving from the testing tags in CBS to buildlogs.c.o, that will continue to show up as it is built. Do note: since we do want to give testers and developers an opportunity to build and test against an upcoming point-release before it goes GA, content coming from buildlogs.centos.org may require enabling the CR repo once it's ready. Any new requests for sign+push (adding new tags to mirror.c.o) during Point-release Freeze will be held until the point release goes GA. If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson

2 3

Volunteers needed: FOSDEM Dojo content selection
by Rich Bowen 01 Nov '18

01 Nov '18

I need 3 or 4 people who are willing to review the submitted content for the FOSDEM Dojo and select a schedule. I estimate 2-3 hours of your time, and I'm able to "pay" for your participation with CentOS swag - see https://photos.app.goo.gl/a9GqLnm1WUUJebU17 - and my undying appreciation. :) Please contact me off-list if you're willing to do this, and you feel competent to evaluate the quality of submission abstracts. It is not required that you'll be attending the event to participate. You're also welcome if you're one of the people who have submitted a presentation. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Fwd: FOSDEM 2019 - Distributions Devroom Call for Participation
by Rich Bowen 01 Nov '18

01 Nov '18

The Distributions devroom will take place Sunday 3 February 2019 at FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles. As more and more workloads are being considered for containerization in the future and are finally landing in virtualized environments today, distributions remain a critical success factor and are more important than ever. Containers, like virtual machines, are not magical and rely on piles of software being assembled in a way that is repeatable, reliable, and functional. This is at the very heart of the problem that distributions have always solved. Each distribution is responsible for building, testing, and releasing software as well as managing the lifecycle of each application in the collection. Additionally, distributions do very important work in ensuring that various versions of upstream software work well together and can co-exist. Distributions are also, often responsible, for "de-vendoring" upstream software so that security fixes can be applied more quickly. We welcome submissions targeted at contributors interested in issues unique to distributions, especially in the following topics: # Topics and Areas of Focus ## Focus Areas - The ways that distribution technologies can be leveraged to allow for easier creation of a multi-verse of artifacts from single source trees. This includes the increasing move toward self-contained applications and providing multiple non-parallel installed versions of software. - Efforts being made in shared environments around Build/Test/Release cycles. - Topics related to the delivery problem as it impacts updates in terms of both size and rollback/reliability are expected to be featured. ## Additional Topic Ideas - Distribution and Community collaborations, eg: how does code flow from developers to end users across communities, ensuring trust and code audibility - Automating building software for redistribution to minimize human involvement, eg: bots that branch and build software, bots that participate as team members extending human involvement - Cross-distribution collaboration on common issues, eg: content distribution, infrastructure, and documentation - Growing distribution communities, eg: onboarding new users, helping new contributors learn community values and technology, increasing contributor technical skills, recognizing and rewarding contribution - Principals of Rolling Releases, Long Term Supported Releases (LTS), Feature gated releases, and calendar releases - Distribution construction, installation, deployment, packaging and content management - Balancing new code and active upstreams verus security updates, back porting and minimization of user breaking changes - Delivering architecture independent software universally across architectures within the confines of distribution systems - Effectively communicating the difference in experience across architectures for developers, packagers, and users - Working with vendors and including them in the community - The future of distributions, emerging trends and evolving user demands from the idea of a platform Ideal submissions are actionable and opinionated. Submissions may be in the form of 25 or 50 minute talks, panel sessions, round-table discussions, or Birds of a Feather (BoF) sessions. Dates ------ Submission Deadline: 02-Dec-2018 @ 2359 GMT Acceptance Notification: 7-Dec-2018 Final Schedule Posted: 14-Dec-2018 How to submit -------------- Visit https://penta.fosdem.org/submission/FOSDEM19 1.) If you do not have an account, create one here 2.) Click 'Create Event' 3.) Enter your presentation details 4.) Be sure to select the Distributions Devroom track! 5.) Submit What to include --------------- - The title of your submission - A 1-paragraph Abstract - A longer description including the benefit of your talk to your target audience, including a definition of your target audience. - Approximate length / type of submission (talk, BoF, ...) - Links to related websites/blogs/talk material (if any) Administrative Notes ---------------- We will be live-streaming and recording the Distributions Devroom. Presenting at FOSDEM implies permission to record your session and distribute the recording afterwards. All videos will be made available under the standard FOSDEM content license (CC-BY). If you have any questions, feel free to contact the devroom organizers: distributions-devroom(a)lists.fosdem.org (https://lists.fosdem.org/listinfo/distributions-devroom)

1 0

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

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