devel

devel@lists.centos.org

4 participants
4640 discussions

Victoria RDO Release Announcement
by Amy Marrich 16 Nov '20

16 Nov '20

If you're having trouble with the formatting, this release announcement is available online https://blogs.rdoproject.org/2020/11/rdo-victoria-released/ --- RDO Victoria Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack Victoria for RPM-based distributions, CentOS Linux and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Victoria is the 22nd release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network at http://mirror.centos.org/centos/8/cloud/x86_64/openstack-victoria/. 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. 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, is 100% open source, with all code changes going upstream first. PLEASE NOTE: RDO Victoria provides packages for CentOS8 and python 3 only. Please use the Train release, for CentOS7 and python 2.7. Interesting things in the Victoria release include: - With the Victoria release, source tarballs are validated using the upstream GPG signature. This certifies that the source is identical to what is released upstream and ensures the integrity of the packaged source code. - With the Victoria release, openvswitch/ovn are not shipped as part of RDO. Instead RDO relies on builds from the CentOS NFV SIG. - Some new packages have been added to RDO during the Victoria release: - ansible-collections-openstack: This package includes OpenStack modules and plugins which are supported by the OpenStack community to help with the management of OpenStack infrastructure. - ansible-tripleo-ipa-server: This package contains Ansible for configuring the FreeIPA server for TripleO. - python-ibmcclient: This package contains the python library to communicate with HUAWEI iBMC based systems. - puppet-powerflex: This package contains the puppet module needed to deploy PowerFlex with TripleO. - The following packages have been retired from the RDO OpenStack distribution in the Victoria release: - The Congress project, an open policy framework for the cloud, has been retired upstream and from the RDO project in the Victoria release. - neutron-fwaas, the Firewall as a Service driver for neutron, is no longer maintained and has been removed from RDO. Other highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/victoria/highlights. Contributors During the Victoria cycle, we saw the following new RDO contributors: Amy Marrich (spotz) Daniel Pawlik Douglas Mendizábal Lance Bragstad Martin Chacon Piza Paul Leimer Pooja Jadhav Qianbiao NG Rajini Karthik Sandeep Yadav Sergii Golovatiuk Steve Baker 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 58 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: Adam Kimball Ade Lee Alan Pevec Alex Schultz Alfredo Moralejo Amol Kahat Amy Marrich (spotz) Arx Cruz Bhagyashri Shewale Bogdan Dobrelya Cédric Jeanneret Chandan Kumar Damien Ciabrini Daniel Pawlik Dmitry Tantsur Douglas Mendizábal Emilien Macchi Eric Harney Francesco Pantano Gabriele Cerami Gael Chamoulaud Gorka Eguileor Grzegorz Grasza Harald Jensås Iury Gregory Melo Ferreira Jakub Libosvar Javier Pena Joel Capitao Jon Schlueter Lance Bragstad Lon Hohberger Luigi Toscano Marios Andreou Martin Chacon Piza Mathieu Bultel Matthias Runge Michele Baldessari Mike Turek Nicolas Hicher Paul Leimer Pooja Jadhav Qianbiao.NG Rabi Mishra Rafael Folco Rain Leander Rajini Karthik Riccardo Pittau Ronelle Landy Sagi Shnaidman Sandeep Yadav Sergii Golovatiuk Slawek Kaplonski Soniya Vyas Sorin Sbarnea Steve Baker Tobias Urdin Wes Hayutin Yatin Karel The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Wallaby. 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. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use 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. 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 has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on 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 devel mailing list 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, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the Freenode IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube. *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz <https://www.redhat.com/>

1 0

404 on vault.centos.org/centos/7/updates/Source/repodata/repomd.xml
by Jan Pazdziora 13 Nov '20

13 Nov '20

Hello, /etc/yum.repos.d/CentOS-Sources.repo from centos-release-7-6.1810.2.el7.centos.x86_64 configures [updates-source] name=CentOS-$releasever - Updates Sources baseurl=http://vault.centos.org/centos/$releasever/updates/Source/ but currently http://vault.centos.org/centos/7/updates/Source/repodata/repomd.xml returns 404 Not Found. Is that an expected move of the CentOS 7 sources to some other location or is that a temporary glitch? Thank you, -- Jan Pazdziora Product Owner, Platform Security Readiness, Red Hat

2 1

EPEL-ANNOUNCE EPEL-6 is End of Life in 2020-11-30
by Troy Dawson 13 Nov '20

13 Nov '20

EPEL 6 is End Of Life (EOL) on November 30 2020. That is two weeks away EPEL 6 will be moved to archives in the first week of December 2020. That is three weeks away EPEL Steering Committee

1 0

CentOS 8.3 Release date
by Satish Patel 12 Nov '20

12 Nov '20

Folks, Redhat has released RHEL 8.3 for the general public last week so curious when CentOS 8.3 is coming out for the public? ~S

8 11

Update centos-release-openstack
by Alfredo Moralejo Alonso 12 Nov '20

12 Nov '20

Hi, Some days ago we requested to update the centos-release-openstack package to include new release OpenStack Victoria (branch c8-sig-cloud-openstack-victoria): https://git.centos.org/rpms/centos-release-openstack/c/2cdca07a1db5cf0418b2… We are waiting for it to announce the new release publicly. Is there any ETA to get it built and shipped in the extras repo? Best regards, Alfredo

2 3

[infra] Announced outage : hardware maintenance for network in main DC
by Fabian Arrotin 10 Nov '20

10 Nov '20

Due to some network switches upgrade in the DC hosting some community projects (including but not limited to CentOS), we'll have a large majority of our infra not reachable. Migration is scheduled for """"Tuesday November 10th, 2:00 am UTC time"""". You can convert to local time with $(date -d '2020-11-10 14:00 UTC') We unfortunately can't announce/give you any expected downtime as it can last for several hours (info I received through invite) but we'll try to restore all services/connectivity as soon as possible. Impacted services in that DC : - *all* Non impacted services (easier to just mention short list of things not in that DC, so items not listed below *will* be down) : - https://www.centos.org - https://forums.centos.org - https://lists.centos.org - mirrorlist.centos.org -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 4

Question about NFS Ganesha [Storage SIG]
by Strahil Nikolov 09 Nov '20

09 Nov '20

Hello All, I am trying to deploy a GlusterFS 8 on a CentOS 8.2.2004 with NFS Ganesha. It seems that Ganesha provided by centos-release-nfs-ganesha28 & centos-release-nfs-ganesha30 require resource-agents >= 4.2, but HighAvailability repo provides only 4.1 . How can I obtain resource-agents suitable for NFS Ganesha. Some output: [root@glustera ~]# yum install glusterfs-ganesha.x86_64 Последната проверка за остарялост на метаданните: преди 0:00:30 на 24.10.2020 (сб) 20:50:19 EEST. Грешка: Проблем: cannot install the best candidate for the job - nothing provides resource-agents >= 4.2.0 needed by glusterfs-ganesha-8.1-1.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Best Regards, Strahil Nikolov

3 20

NFS Ganesha on EL8 needs redesign
by Strahil Nikolov 09 Nov '20

09 Nov '20

Hello All, I have been playing around with Ganesha on CentOS 8 and I have noticed some issues so far. Could you assist me in pinpointing the correct location for tracking the issues: - 'gluster nfs-ganesha enable' builds pacemaker groups that use 'ocf:heartbeat:portblock', but that resource is relying on IPTABLES, while EL8 is using NFTABLES. - nfs-ganesha.service is starting the process via "/bin/bash -c" which SELINUX hates and of course blocks. Custom selinux policies were needed. - the glusterfs-ganesha.x86_64 rpm is deploying the following boolean 'semanage boolean -m ganesha_use_fusefs --on' but it seems that something disables it. Manual setting of 'setsebool -P ganesha_use_fusefs 1' is necessary - rpcbind is blocked by selinux, I had to enable 'rpcd_use_fusefs' - nfs-ganesha.service is starting before the shared volume is mounted locally, dependency is needed like this one: [root@glustera ~]# cat /etc/systemd/system/nfs-ganesha.service.d/01-debug.conf [Unit] After=run-gluster-shared_storage.mount Requires=run-gluster-shared_storage.mount I will rebuild my cluster to find out if I missed something. Any feedback is appreciated. P.S.: If anyone is interested , I can share the deployment procedure. Best Regards, Strahil Nikolov

1 0

CPE Weekly: 2020-11-08
by Aoife Moloney 08 Nov '20

08 Nov '20

Hi Everyone, Below is this week's CPE weekly for week ending 2020-11-08 for both Fedora & CentOS, and if you want to visit the hackmd link https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view you can then use the header bar on your left to skip to Fedora or CentOS updates that interest you. ## General Project Updates We've updated our How to work with us section on our wiki https://docs.fedoraproject.org/en-US/cpe/initiatives/ Updated initative timetable can be viewed here https://docs.fedoraproject.org/en-US/cpe/time_tables/ And we have a new initiative repo live on Pagure https://pagure.io/cpe/initiatives-proposal Below are the scheduled projects the CPE team are currently working on for the months of October, November & December: * CentOS Stream Phase 4 - Build system services * Noggin Phase 4 - Data Migration of Fedora & CentOS Accounts, Community testing * OSBS for aarch64 - this will begin in November * Fedora Messaging Schemas - this work is continuing from Q3 and is being worked on part-time ### Misc #### GitLab New GitLab topic sent to devel-announce(a)lists.fedoraproject.org & centos-devel(a)centos.org on Message Bus is out. See email in hackmd here https://hackmd.io/tfOqCXNEQtqsGNLAEfZ2zg?view ## Project Updates *The below updates are pulled directly from our CPE team call we have every week.* ### CentOS * Update CentOS CI Openshift clusters to latest 4.5.16 * Storage resync completed this week. ### CentOS Stream * The team are working on developing ODCS service in the Stream build infra * Developing scripts to help automate adding artifacts to module builds * Check out the CentOS Stream page on centos.org/centos-stream for information on the latest download information and how to convert from CentOS Linux to Stream - especially if you are running on CentOS Linux 6 which is EOL on November 30th :) ### Fedora * F33 is released!!!! * F33 arm images are re-created and pushed as a point release * Testdays app up in openshift stg: https://testdays.stg.fedoraproject.org/events and may even be in production at the time of this email! * Openqa has all hardware up and running except one broken power9 box - working on resolving this ### Staging Environment * Build system nearly done - waiting on a firewall change ### Noggin/AAA * If you maintain an application that uses FAS, please test your app authentication in staging and report any issues you may find to the team in #fedora-aaa. * The team are particularly interested in if you cannot login or your user does not have the right groups/permissions/attributes, eg [cla_done] * The teams kanban board where they track their work can be found here https://github.com/orgs/fedora-infra/projects/6 * And we have a project tracker available to be viewed here https://github.com/fedora-infra/aaa-tracker ### OSBS for aarch64 * The team are tracking their work here https://pagure.io/cpe/osbs-project/issues * This project started on November 4th and the team are investigating technical approaches and requirements such as permissions & access to images. ### Fedora Messaging Schemas * This project is worked on on a part time basis as we are prioritizing completing Noggin first before fully committing to its completion * There is a list of applications that require messaging schemas can be found here https://hackmd.io/@nilsph/H1i8CAbkP/edit * There is a readme which contains documentation on messaging schemas, a cookie-cutter template to create the schema and a definition of Done for writing a schemas https://github.com/fedora-infra/fedora-messaging-schemas-issues * The board they are working from can be viewed here https://github.com/orgs/fedora-infra/projects/7 ## Team Info ### CPE Product Owner Office Hours IRC office hours are now once per month.Below are the logs from the most recent meetings and dates for the next ones. #### #fedora-meeting-1 * Next Meeting: 2020-11-12 @ 1300 UTC on #fedora-meeting-1 #### #centos-meeting * Next Meeting: 2020-11-10 @ 1500 UTC on #centos-meeting ## Background: The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give. See our wiki page here for more information:https://docs.fedoraproject.org/en-US/cpe/ As always, feedback is welcome, and we will continue to look at ways to improve the delivery and readability of this weekly report. Have a great week! Aoife Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

GitLab AMA Session Topic: Message Bus
by Aoife Moloney 08 Nov '20

08 Nov '20

Hi Cent-onians? Ive sent this week's GitLab AMA topic to Fedora's devel-announce list, but in case there are those of you who are interested in the GitLab discussion here too, I would like to share it on your email list also. This week's topic from the GitLab AMA session on September 10th is on Message Bus. As always, here are some links to the resources I have been pulling content from as well: * Questions and Answers hackmd link https://hackmd.io/RW8HahOeR7OJPON1dwuo3w * Chat log from session https://meetbot.fedoraproject.org/fedora-meeting-1/2020-09-10/ama_session_w… * AMA Blog post https://communityblog.fedoraproject.org/gitlab-ama-follow-up/#more-9346 * Here is this email in hackmd if you wish to view it there: https://hackmd.io/tfOqCXNEQtqsGNLAEfZ2zg?view ## Topic: Message Bus - Question: Fedora uses a message bus to integrate different parts of its infrastructure. How should we onboard GitLab into this message bus? - Answer: Currently we would need to have a service that proxies GitLab’s events to fedora-messaging something similar to github2fedmsg. There were some concerns raised about the order of events sent by GitLab’s webhooks, these will need to be looked after during a Proof of Concept stage. - Question: How would git push over http work with GitLab? (assuming gitlab does not have Fedora's password since they are stored in FAS) - Answer: GitLab has a good number of authentication options and integrations where the "best" solution usually depends on a team's specific needs and use case. As such, the best way to know and meet Fedora's needs and use cases is to have a conversation and discuss the options with GitLab. How does git push over HTTP work with FAS right now, and what git push (over HTTP) auth requirements/flow would you like to have for your projects in GitLab? These are the only two questions and answers I could gather relating to message bus from the AMA question sheet, however I know there was a lot of discussion regarding this topic during the AMA session itself, so if you would like to resume/kick off that conversation again, please feel free to use this email to discuss. A personal note and for full transparency: the weeks seem to be passing in the blink of an eye lately, I assume it's because I'm busy(?) but it might be just the weird 2020 vibe the world is on nowadays. I really don't know. Whatever the reason, there has been no further discussion with GitLab since early October-ish, but we will be returning to the conversation of how this migration could be technically possible soon, so sincerely thank you all again for engaging with us/me here as I found reading the discussion that came from the Fedora devel list on permission and access much easier to follow and have been taking notes on expectations to use that feedback in conversations with GitLab when we pick the discussion back up. I hope you all had a good weekend and will talk to you all next week when the topic of Namespace & Issue Tracking is sent! Kindest regards, Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

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