devel

devel@lists.centos.org

16 participants
4590 discussions

GitLab AMA Topic Follow Up: Namespace & Issue Tracking
by Aoife Moloney 23 Nov '20

23 Nov '20

Hi everyone, I've posted this to devel-announce(a)lists.fedoraproject.org but I will always post this over here too in case there are interested people on this mailing list that may not see it on the Fedora one. Thanks again for your involvement in the GitLab AMA session on IRC in September. This email discussion thread is on Namespace & Issue Tracking. I have pulled the relevant questions and answers from the original hackmd doc into one email and if you would like to discuss this topic specifically, here might be a good place to do so so your conversations don't go down a 'rabbit hole' :) Here are some links to resources 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/oZrDwbSeSWO-l_X65A1ndg?view ## Namespace & Issue Tracking - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: It may need to be checked again, but it appears you can turn on/off the issue tracker at the project level. - Question: Currently dist-git in Fedora has several namespaces: rpms, modules, containers, tests... All namespaces but the ``tests`` namespace have their issue tracker in bugzilla. Would this work in gitlab? Can we selectively enable/disable issue tracking per namespace for the entire instance? (ie: w/o giving the possibility to ``owner`` or ``maintainer`` to toggle that setting.) - Answer: You can turn the GitLab issue tracker on and off by project. See https://docs.gitlab.com/ee/user/project/settings/#sharing-and-permissions Namespaces map to “group” in GitLab. Here’s more info about them: https://docs.gitlab.com/ee/api/namespaces.html - Question: Fedora, as far as I understand, still plan on using bugzilla as issue tracker. Currently default assignee and the CC are gathered using the ``main admin`` (ie: the ``owner`` for GitLab iiuc), the other maintainers (who did not ``unwatch issues`` in the project - mechanism for them to opt-out of being in the CC list) and the people having enabled ``Issue watching`` for the project (mechanism for them to opt-in into being in the CC list). Would this work in a GitLab world? - Answer: There are a number of options related to that. For one, users can control their notifications globally and by name space in a fine grained way (see GitLab Notification Emails). - Question: Fedora is part of GitLab’s Open Source program and we have a migration tracker issue that we are using to keep track of feature requests, bugs, etc that are important to Fedora. The Fedora migration team has been working with us at GitLab to maintain that and community members can add relevant issues there so we can track them. It’s also helpful for our product managers to hear about why particular issues are important for the Fedora use case, and to have upvotes, so doing that will help! Where can you submit requests/bugs/report issues? - Answer: Fedora Migration Tracker: https://gitlab.com/gitlab-org/gitlab/-/issues/217350 Feature template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature… Bug template: https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Bug Please do review the original questions doc in case I have missed any that relate to namespace and issue tracking and thank you again for your engagement with these emails! The next email topic will be on 'Branches'. Have a good week! Aoife -- Aoife Moloney Product Owner Community Platform Engineering Team Red Hat EMEA Communications House Cork Road Waterford

1 0

mirror.centos.org/centos-7/7.9.2009 missing?
by Giedrius Rekašius 19 Nov '20

19 Nov '20

Hello, I don't see the 7.9.2009 release directory in http://mirror.centos.org/centos-7/. Up until now each minor release used to have it's own directory with the latest minor having same contents as the major release. Did something change recently and those minor release directories won't be provided going forward? Regards, Giedrius

3 2

SIGs Building Against CentOS Stream
by Johnny Hughes 18 Nov '20

18 Nov '20

All, Currently, here is a list of tags in the CBS who can build against CentOS Stream. https://cbs.centos.org/koji/search?match=glob&type=tag&terms=*8s-* If your SIG is interested in building against CentOS Stream, you can ask on this list to get a new tag created. The CentOS Project would be happy to enable building against CentOS Stream, so just let us know. Thanks, Johnny Hughes

1 0

[NFVSIG] NFV SIG meeting minutes - 2020-11-18
by Alfredo Moralejo Alonso 18 Nov '20

18 Nov '20

============================================= #centos-meeting: NFV SIG meeting - 2020-11-18 ============================================= Meeting started by amoralej at 15:08:57 UTC. The full logs are available athttps://www.centos.org/minutes/2020/November/centos-meeting.2020-11-18-15… . Meeting summary --------------- * ovs/ovn update to FDP 20.H (amoralej, 15:12:02) * ovs and ovn 2.13 from FDP 20.H have been tested and pushed to official mirrors (amoralej, 15:12:29) * ovs and ovn 2.11 from FDP 20.H have been tested and pushed to official mirrors (dholler, 15:12:45) * RDO Ussuri is also moving to OVS/OVN 2.13 from NFV SIG builds (amoralej, 15:18:54) * New centos-release-nfv pushed to mirror (amoralej, 15:20:56) * now the network-extras repo can be enabled by installing centos-release-nfv-extras (amoralej, 15:21:44) * LINK: https://pagure.io/centos-infra/issue/50 (ykarel, 15:31:55) Meeting ended at 15:34:36 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (32) * dholler (10) * ykarel (6) * centbot (4) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

7.9.2009 Live ISOs
by Ladar Levison 18 Nov '20

18 Nov '20

I noticed there is no live media in the new 7.9 ISO directory. Is that an oversight, a task that is pending, or will there be no live media for the 7.9.2009 release? The missing files are CentOS-7-x86_64-LiveGNOME-2009.iso and CentOS-7-x86_64-LiveKDE-2009.iso ... L~

3 2

7.9.2009 Live ISOs
by Ladar Levison 17 Nov '20

17 Nov '20

1 0

Container Images & Docker Hub Rate Limiting
by Stephen Benjamin 17 Nov '20

17 Nov '20

Hi all, At the beginning of November, Docker instituted rate limiting on Docker Hub. Some builds happening in Quay are now hitting this limit[1], including those using the CentOS base images. Docker has a program to remove the rate limiting for open source projects[2]. Has anyone applied yet on behalf of the CentOS project? If not, who would be the right person to contact? We did notice that CentOS has its own registry[3], but it's currently returning 502 Bad Gateway when you hit the index page. However registry.centos.org/centos/centos:8 works -- is that a stable place for us to get the latest CentOS container images? Alternatively, would it be possible to get official builds for CentOS published to quay? Thanks - Stephen [1] https://groups.google.com/g/metal3-dev/c/6T6rMoFEOIc/m/KT68jzF5BAAJ [2] https://www.docker.com/blog/expanded-support-for-open-source-software-proje… [3] https://wiki.centos.org/ContainerPipeline

3 3

centos8 openvswitch-dpdk RPM
by Satish Patel 16 Nov '20

16 Nov '20

Folks, Recently i started playing with openvswitch on centOS for openstack SDN, and found centos8 doesn't have openvswitch with dpdk support, I was looking around RPM but didn't find any RPM also, do i need to compile openviswtch+dpdk support or rpm is available but i am not aware of it. ~S

2 10

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

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