devel April 2019

devel@lists.centos.org

18 participants
20 discussions

CentOS 8 Artwork needed
by Rich Bowen 31 Jan '20

31 Jan '20

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

10 30

Using mirrorlist in centos-release-* packages
by Anssi Johansson 12 Sep '19

12 Sep '19

Hi, as mentioned in https://lists.centos.org/pipermail/centos-devel/2018-September/016949.html mirrorlist.centos.org has been updated to produce mirror lists for SIG content as well. Some centos-release-* packages have already been modified to use mirrorlist.centos.org instead of mirror.centos.org, but many still point to mirror.centos.org. Most of mirror.centos.org hosts are also used for seeding the 600+ external mirrors we have. By directing some of their 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 better geographical coverage does not hurt either. mirror.centos.org nodes are donated servers, and it would be kind to the sponsors to use their bandwidth sparingly. The .repo files should be modified so that the current baseurl line gets commented out and a mirrorlist entry gets added, like this: mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… #baseurl=http://mirror.centos.org/$contentdir/$releasever/storage/$basearch/gluster-4.1/ Note that mirrorlist.c.o can automatically choose between main and altarch content based on the arch parameter. The repo names are constructed from the repository path by stripping away the architecture and changing any slashes to dashes: sclo/x86_64/rh -> sclo-rh, sclo/x86_64/sclo -> sclo-sclo, paas/x86_64/openshift-origin311 -> paas-openshift-origin311, storage/x86_64/gluster-5 -> storage-gluster-5 etc. You can use 'curl' to check what mirrorlist outputs for your repository. New repos are added to mirrorlist.centos.org automatically once the repository hits mirror.centos.org. That script is currently run every three hours. I guess it could be run more frequently (it's fairly lightweight), but you should give the external mirrors a few hours to sync before announcing your release anyway. You can either submit an update to your current centos-release-* file now, or wait until you need to create a new centos-release-* package for other reasons such as releasing softwarepackage-(version+1) which uses different paths. My recommendation would be to submit an update to your current centos-release-* package, so that you would not need to worry about this when you eventually need to publish a new one for other reasons. We released an updated centos-release package for CentOS AltArch before 7.6.1810 was released for this exact reason, ie. we didn't need to worry about this change at 7.6.1810 release time. Other people (such as bstinson, arrfab and hughesjr) can probably help with creating and publishing an updated centos-release-* package, but the usual tagging procedure to extras will apply. The SIG Guide https://wiki.centos.org/SIGGuide should have all the needed details for this (if not, complain to bstinson). It is highly recommended to actually test your new centos-release-* package from buildlogs before you ask that package to be signed and pushed to extras. The holiday season is fast approaching so (I) don't expect much activity regarding these changes in the following days. I'm hoping that the SIGs would take a look at this in early 2019, though. Thanks to those SIGs who have already made these changes to their centos-release-* packages! If you have questions, feel free to ask either here or on #centos-devel. Thanks for your time!

1 2

May SIG reports
by Rich Bowen 01 May '19

01 May '19

In case you have not seen the reminders that I've sent out, we're coming up on the time for the May SIG reports. As documented at https://wiki.centos.org/SpecialInterestGroup we expect reports from SIGs in Group 2: * Alt Arch * Cloud * NFV * Promo * Storage Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 1

[RDO] Stein RDO Release Announcement
by Rain Leander 27 Apr '19

27 Apr '19

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2019/04/rdo-stein-released/ --- The RDO community is pleased to announce the general availability of the RDO build for OpenStack Stein for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Stein is the 19th release from the OpenStack project, which is the work of more than 1200 contributors <http://stackalytics.com/> from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/7/cloud/x86_64/openstack-stein/. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG <https://wiki.centos.org/SpecialInterestGroup/Cloud>. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform <https://www.redhat.com/en/technologies/linux-platforms/openstack-platform>, is 100% open source, with all code changes going upstream first. <https://i2.wp.com/blogs.rdoproject.org/wp-content/uploads/2019/04/yucel-mor…>Photo by Yucel Moran on Unsplash New and Improved Interesting things in the Stein release <https://releases.openstack.org/stein/highlights.html> include: - Ceph Nautilus <https://ceph.com/releases/v14-2-0-nautilus-released/> is the default version of Ceph, a free-software storage platform, implements object storage on a single distributed computer cluster, and provides interfaces for object-, block- and file-level storage, within RDO (or is it the default without OpenStack?). Within Nautilus, the Ceph Dashboard has gained a lot of new functionality like support for multiple users / roles, SSO (SAMLv2) for user authentication, auditing support, a new landing page showing more metrics and health info, I18N support, and REST API documentation with Swagger API. - The extracted Placement service <https://docs.openstack.org/placement/latest/usage/index.html>, used to track cloud resource inventories and usages to help other services effectively manage and allocate their resources, is now packaged as part of RDO. Placement has added the ability to target a candidate resource provider, easing specifying a host for workload migration, increased API performance by 50% for common scheduling operations, and simplified the code by removing unneeded complexity, easing future maintenance. Other improvements include: - The TripleO deployment service <http://tripleo.org/>, used to develop and maintain tooling and infrastructure able to deploy OpenStack in production, using OpenStack itself wherever possible, added support for podman and buildah for containers and container images. Open Virtual Network (OVN) is now the default network configuration and TripleO now has improved composable network support for creating L3 routed networks and IPV6 network support. Contributors During the Stein cycle, we saw the following new RDO contributors: - Sławek Kapłoński - Tobias Urdin - Lee Yarwood - Quique Llorente - Arx Cruz - Natal Ngétal - Sorin Sbarnea - Aditya Vaja - Panda - Spyros Trigazis - Cyril Roelandt - Pranali Deore - Grzegorz Grasza - Adam Kimball - Brian Rosmaita - Miguel Duarte Barroso - Gauvain Pocentek - Akhila Kishore - Martin Mágr - Michele Baldessari - Chuck Short - Gorka Eguileor Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 74 contributors who participated in producing this release. This list includes commits to rdo-packages and rdo-infra repositories: - yatin - Sagi Shnaidman - Wes Hayutin - Rlandy - Javier Peña - Alfredo Moralejo - Bogdan Dobrelya - Sławek Kapłoński - Alex Schultz - Emilien Macchi - Lon - Jon Schlueter - Luigi Toscano - Eric Harney - Tobias Urdin - Chandan Kumar - Nate Johnston - Lee Yarwood - rabi - Quique Llorente - Chandan Kumar - Luka Peschke - Carlos Goncalves - Arx Cruz - Kashyap Chamarthy - Cédric Jeanneret - Victoria Martinez de la Cruz - Bernard Cafarelli - Natal Ngétal - hjensas - Tristan de Cacqueray - Marc Dequènes (Duck) - Juan Antonio Osorio Robles - Sorin Sbarnea - Rafael Folco - Nicolas Hicher - Michael Turek - Matthias Runge - Giulio Fidente - Juan Badia Payno - Zoltan Caplovic - agopi - marios - Ilya Etingof - Steve Baker - Aditya Vaja - Panda - Florian Fuchs - Martin André - Dmitry Tantsur - Sylvain Baubeau - Jakub Ružička - Dan Radez - Honza Pokorny - Spyros Trigazis - Cyril Roelandt - Pranali Deore - Grzegorz Grasza - Bnemec - Adam Kimball - Haikel Guemar - Daniel Mellado - Bob Fournier - Nmagnezi - Brian Rosmaita - Ade Lee - Miguel Duarte Barroso - Alan Bishop - Gauvain Pocentek - Akhila Kishore - Martin Mágr - Michele Baldessari - Chuck Short - Gorka Eguileor The Next Release Cycle At the end of one release, focus shifts immediately to the next, Train, which has an estimated GA the week of 14-18 October 2019. The full schedule is available at https://releases.openstack.org/train/schedule.html. Twice during each release cycle, RDO hosts official Test Days shortly after the first and third milestones; therefore, the upcoming test days are 13-14 June 2019 for Milestone One and 16-20 September 2019 for Milestone Three. Get Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation <https://www.rdoproject.org/install/packstack/>. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use the TripleO Quickstart <https://www.rdoproject.org/tripleo/> and you’ll be running a production cloud in short order. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program <https://www.openstack.org/passport>. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project participates in a Q&A service at https://ask.openstack.org. We also have our users(a)lists.rdoproject.org <https://lists.rdoproject.org/mailman/listinfo/users> for RDO-specific users and operrators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list <https://lists.rdoproject.org/mailman/listinfo/dev>. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org <https://lists.rdoproject.org/mailman/listinfo>. You can also find extensive documentation on RDOproject.org <https://www.rdoproject.org/>. The #rdo channel on Freenode IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS mailing lists <https://lists.centos.org/mailman/listinfo> and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages <https://www.rdoproject.org/contribute/>, peruse the CentOS Cloud SIG page <https://wiki.centos.org/SpecialInterestGroup/Cloud>, and inhale the RDO packaging documentation <https://www.rdoproject.org/documentation/rdo-packaging/>. Join us in #rdo on the Freenode IRC network and follow us on Twitter @RDOCommunity <http://twitter.com/rdocommunity/>. You can also find us on Facebook <https://facebook.com/rdocommunity> and YouTube <https://www.youtube.com/channel/UCWYIPZ4lm4P3_pzZ9Hx9awg>.

2 1

Suggestion regarding CentOS 8 artwork
by jatin 22 Apr '19

22 Apr '19

We are getting closer to the GA of RHEL 8 and as posted on twitter that they need new artwork it will be great to have the Logo of the same theme. Both Red hat and fedora have a logo of head accessories i.e a hat and a fedora. It will be great to have centOS artwork of a similar kind thats what my suggestion is. A bit about myself - Jatin Garg Nation- India DOB - 18th December 2001 Notable contributions to CentOS project - https://github.com/jatin-cbs/Lutris-RHEL-CentOS7 making lutris wine gaming accessible on RHEL, CentOS to users creating sh scripts. Contribution to Vulkan, Unreal Engine to optimize performance and wiki improvements for CentOS.

3 2

python3 version of centos-packager/python-centos
by Troy Dawson 17 Apr '19

17 Apr '19

Hi, I'm just curious if there is a python3 version of centos-packager, and python-centos? With python2 nearing end of life and RHEL8/CentOS8 being python3 based, it would be a good time for it to be python3 based. Although, if it's a matter of priorities, I'd prefer CentOS8 being out sooner, versus centos-packager in python3. I was more asking incase there was a version someone was working on that I might be able to test/use.

3 2

SCL SIG: RHSA-2019:0746
by Johnny Hughes 16 Apr '19

16 Apr '19

We are getting questions on the main mailing list (and on IRC) concerning: https://access.redhat.com/errata/RHSA-2019:0746 Does the SCL SIG plan on building these soon : httpd24-httpd-2.4.34-7.el7.1.src.rpm httpd24-httpd-2.4.34-7.el6.1.src.rpm Thanks, Johnny Hughes

1 0

Re: [CentOS-devel] eight.centos.org
by Trevor Hemsley 11 Apr '19

11 Apr '19

On Thu, Apr 11, 2019 at 10:47:07AM +0530, Thomas Stephen Lee wrote: > Will there be a eight.centos.org ? As far as I know, seven.centos.org was renamed to blog.centos.org and the "seven" name was just kept for backwards compatibility. I doubt if there needs to be an eight. Trevor

1 0

Re: [CentOS-devel] git.centos.org Migration 11-April-2019 13:30 UTC
by Brian Stinson 10 Apr '19

10 Apr '19

We're starting with this: https://wiki.centos.org/Sources_new which will replace this: https://wiki.centos.org/Sources We can probably come up with something afterward for the blog. -- Brian Stinson brian(a)bstinson.com On Wed, Apr 10, 2019, at 15:34, Rich Bowen wrote: > Can we get a writeup for the blog, covering what, why, how it benefits, > how to use (whether you need to change what you're doing). Thanks. > > On 4/10/19 12:38 PM, Brian Stinson wrote: > > > > Hi Folks, > > > > We have a go-ahead to perform the switchover of git.centos.org to Pagure/Repospanner starting tomorrow at 13:30 UTC. > > > > I'll switch the A record to the new machine and perform a final sync at that time. > > > > I'll be hanging out in #centos-devel on Freenode if there are any questions. > > > > Cheers! > > > > -- > Rich Bowen - rbowen(a)redhat.com > @CentOSProject // @rbowen > 859 351 9166 >

1 0

package missing? nfs-ganesha-utils 2.7.2
by Stefan Kärst 10 Apr '19

10 Apr '19

hi! we are using CentOS 7.6.1810 and I tried to update all packages including nfs-ganesha.* It seems like all packages for nfs-ganesha are available with version 2.7.2 except nfs-ganesha-utils. why is that? I checked this mail-archive for the last months and searched the web, without luck. http://mirror.centos.org/centos-7/7.6.1810/storage/x86_64/gluster-4.1/ [ ] nfs-ganesha-mount-9P-2.7.1-1.el7.x86_64.rpm 2019-01-08 12:06 15K [ ] nfs-ganesha-mount-9P-2.7.2-1.el7.x86_64.rpm 2019-03-25 09:01 19K [ ] nfs-ganesha-nullfs-2.7.2-1.el7.x86_64.rpm 2019-03-25 09:01 26K [ ] nfs-ganesha-proxy-2.7.1-1.el7.x86_64.rpm 2019-01-08 12:06 54K [ ] nfs-ganesha-proxy-2.7.2-1.el7.x86_64.rpm 2019-03-25 09:01 58K [ ] nfs-ganesha-utils-2.7.1-1.el7.x86_64.rpm 2019-01-08 12:06 70K <---------- ?! [ ] nfs-ganesha-vfs-2.7.1-1.el7.x86_64.rpm 2019-01-08 12:06 54K [ ] nfs-ganesha-vfs-2.7.2-1.el7.x86_64.rpm 2019-03-25 09:01 58K nfs-ganesha-utils contains the ganesha_mgr tool, to manage NFS shares. so I have to either uninstall this tool or lock versions to 2.7.1. I hope someone can shed some light on this. Many Thanks! Stefan K.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2019