devel

devel@lists.centos.org

2 participants
4653 discussions

RHEL 8 is out
by Rob Thomas 08 May '19

08 May '19

For those that missed the announcement, 8 has been released. Now we just get to sit back and wait for all the repackaging magic to happen! --Rob

3 3

[Meeting] RDO meeting (2019-05-08) minutes
by Javier Pena 08 May '19

08 May '19

----- Forwarded Message ----- ============================== #rdo: RDO meeting - 2019-05-08 ============================== Meeting started by jpena at 15:00:31 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_05_08/2019/rdo_m… . Meeting summary --------------- * roll call (jpena, 15:00:36) * request to update to puppet 6 in RDO:- https://trello.com/c/isJkCzYZ (jpena, 15:05:29) * LINK: https://etherpad.openstack.org/p/RDO-Meeting (fultonj, 15:05:45) * puppet 6 will need to wait until centos 8 is available, can do some pre-work in Fedora (jpena, 15:06:43) * ACTION: ykarel to propose pr to update puppet in fedora (amoralej, 15:16:56) * ACTION: amoralej to update puppet in fedora stabilized repo once is built in fedora (amoralej, 15:17:19) * ceph/ansible post-update follow up (jpena, 15:18:33) * ppc64le container uploads (jpena, 15:30:30) * LINK: https://ci.centos.org/job/tripleo-upstream-containers-build-master-ppc64le/… ? (amoralej, 15:32:03) * LINK: https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master… is the most recent build log, for example (baha, 15:33:03) * LINK: https://trunk.rdoproject.org/centos7-master/deps/latest/ (ykarel, 15:37:52) * ACTION: jpena to check potential alternatives for the RDO registry (jpena, 16:15:44) * chair for the next meeting (jpena, 16:17:17) Meeting ended at 16:18:41 UTC. Action items, by person ----------------------- * amoralej * amoralej to update puppet in fedora stabilized repo once is built in fedora * jpena * jpena to check potential alternatives for the RDO registry * ykarel * ykarel to propose pr to update puppet in fedora People present (lines said) --------------------------- * amoralej (57) * jpena (52) * ykarel (32) * tonyb (19) * fultonj (18) * weshay (18) * mwhahaha (15) * baha (14) * fmount (7) * openstack (7) * Vorrtex (4) * rdogerrit (3) Generated by `MeetBot`_ 0.1.4 _______________________________________________ dev mailing list dev(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/dev To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org

1 0

Installing kernel 4.14.34 through kickstart
by Far Had 06 May '19

06 May '19

Hi, Trying to compile and put kernel 4.14.34 into the CentOS 7 (1511 release) DVD with a ks.cfg already configured. This ks DVD has been working fine with the original 3.10 kernel. Here is what I did: I built rpm packages of the 4.14.34 kernel with disabled kernel debugging option. This gave me 3 rpm files: kernel, kernel-header and kernel devel. I replaced them with their equivalents in isolinux/packages directory in the DVD ISO image and made a new ISO file out of it. when booting from this image, automatic installation fails after installing all packages in the post installation at "generating initramfs" phase. The exact error text is: "No such file or directory" (image attached) Regards.

1 0

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

IRC Meeting Changes
by John R. Dennison 01 May '19

01 May '19

For the past few years the CentOS Project has been holding IRC meetings for our various Special Interest Groups (SIGs) and other projects in the #centos-devel channel on the freenode IRC network. This has, for the most part, worked out fairly well. However, as this is a shared channel, at times things can become a bit hectic and confusing as people occasionally interrupt a meeting in progress. Not only does this break the flow of the meeting but it also injects noise into the logs that the project maintains for historical reference. This policy was also different from most other projects which have a dedicated "meetings" channel to be used for these purposes. In order to address the issue the project has made the decision to transition meetings to the #centos-meeting channel. This is a dedicated channel to be used solely for meetings. We feel this will help alleviate any potential issues with interruptions and other distractions. This channel is managed by the same group of people, our IRC Ops Team, as is #centos-devel and our channel bots are present to help as necessary. An additional bonus of this transition will be that the meeting bot (centbot) responsible for meeting oversight and logging will now be able to set the channel topic to reflect meeting status. This was not previously possible due to policy as we did not want to have the bot op'd unless absolutely necessary in a shared channel. We are planning this transition for June 1st in order to give the stakeholders involved ample time to alert their communities of the change and to ensure we have made the necessary changes on our end to ensure a smooth transition for people who access the logs via the https://www.centos.org/minutes/ interface. Any questions regarding this transition should be addressed either via the centos-devel mailing list or on the #centos-devel IRC channel on freenode. Additionally people can reach out to me personally on IRC (Bahhumbug on freenode) or via email if they have questions or concerns regarding this or other CentOS IRC matters. Thanks and see you in #centos-meeting :) -- The most valuable thing you can make is a mistake - you can't learn anything from being perfect. -- Adam Osborne (1939-2003), American entrepreneur

1 0

[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

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