On 7/6/20 3:55 PM, Karanbir Singh wrote:
> Hi,
>
> never been involved with the nfv sig,
>
Karanbir, looks like you are the only one in the adminstrator role of
sig-nfv.
> regards
>
> On 06/07/2020 14:23, Alfredo Moralejo Alonso wrote:
>> Adding kb as NFV Sig chair.
>>
>> What needs to be done to get this moving on?, some maintainers
>> (including myself) have requested access to nfv-sig group but there has
>> been no response.
>>
>> What's the status of NFV SIG?
>>
>>
>> On Wed, Jun 17, 2020 at 2:32 PM Dominik Holler <Dominik.Holler(a)gmx.net
>> <mailto:Dominik.Holler@gmx.net>> wrote:
>>
>>
>>
>>
>>
>> > From: Alfredo Moralejo Alonso <amoralej(a)redhat.com
>> <mailto:amoralej@redhat.com>
>> > <mailto:amoralej@redhat.com <mailto:amoralej@redhat.com>>>
>> > Date: Wed, Jun 17, 2020 at 1:24 PM
>> > Subject: [CentOS-devel] Rebuilding OpenvSwitch and OVN from Fast
>> > DataPath in NFV Sig
>> > To: The CentOS developers mailing list. <centos-devel(a)centos.org
>> <mailto:centos-devel@centos.org>
>> > <mailto:centos-devel@centos.org <mailto:centos-devel@centos.org>>>
>> >
>> >
>> > Hi,
>> >
>> > During the last years OpenVswitch and OVN have become a major
>> > dependency for several projects and SIGs in the CentOS ecosystem,
>> > including OpenStack, oVirt and OpenShift. During this time each
>> > project has been following its own way with limited coordination
>> > (just some opportunistic cross-tagging between SIGs) and different
>> > approaches, rebuilding Fedora builds or FDP srpms from
>> ftp.redhat.com <http://ftp.redhat.com>
>> > <http://ftp.redhat.com>
>> > from time to time in their own tags and repos.
>> >
>> > This has led to multiple issues and suboptimal usage resources so I
>> > think a good step ahead would be to use existing NFV SIG [1] as a
>> > collaboration area for all the interested projects to build, test and
>> > ship OpenvSwitch and OVN using public SRPMs from Fast Datapath [2].
>> >
>> > What I'm proposing is that the interested people in becoming
>> > maintainers for OVS/OVN in NFV Sig request membership to nfv-sig group
>> > [3]. Then, we'll coordinate to request new tags/buildroots for OVS/OVN
>> > and start building and testing the required releases.
>> >
>> > Any thoughts on this proposal?
>> >
>>
>> I think this would be efficient.
>> I already applied to become a member of sig-nfv to help.
>>
>> > Best regards,
>> >
>> > Alfredo
>> >
>> >
>> > [1] https://wiki.centos.org/SpecialInterestGroup/NFV
>> > [2]
>> >
>> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRP…
>> > [3] https://accounts.centos.org/group/members/sig-nfv
>> >
>> > _______________________________________________
>> > CentOS-devel mailing list
>> > CentOS-devel(a)centos.org <mailto:CentOS-devel@centos.org>
>> <mailto:CentOS-devel@centos.org <mailto:CentOS-devel@centos.org>>
>> > https://lists.centos.org/mailman/listinfo/centos-devel
>> >
>> >
>> > --
>> > Didi
>> >
>>
>
>
============================================
#centos-meeting: NFV SIG relaunch 2020-07-22
============================================
Meeting started by amoralej at 15:00:39 UTC. The full logs are available
athttps://www.centos.org/minutes/2020/July/centos-meeting.2020-07-22-15.00.…
.
Meeting summary
---------------
* roll call (amoralej, 15:01:22)
* current situation of NV SIG (amoralej, 15:04:27)
* LINK: https://review.rdoproject.org/etherpad/p/NFVSIG-meeting
(amoralej, 15:04:32)
* my proposal was to relaunch it to host Red Hat Fast DataPath
packages for CentOS and other packages related to NFV (amoralej,
15:07:35)
* goals for NFV SIG (amoralej, 15:08:41)
* the first goal is to rebuild FDP released SRPMs (amoralej,
15:09:03)
* LINK:
http://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SR…
(amoralej, 15:09:51)
* the goal is rebuild FDP srpms with minimal (hopefully none)
divergence from FDP (amoralej, 15:19:50)
* if some change is needed in distgits, we'll use NFV SIG branches of
openvswitch and ovn in git.centos.org (amoralej, 15:20:21)
* initially OVS 2.11 and 2.13 will be rebuilt for CentOS8 (amoralej,
15:22:16)
* we'll create per-release branches in openvswitch and ovn repos in
git.centos.org to store spec for the different releases (amoralej,
15:26:53)
* ACTION: amoralej to create branches in openvswitch and ovn repos
(amoralej, 15:27:07)
* a single tag/repo will be created to contain all rebuilds from fdp
(amoralej, 15:40:47)
* AGREED: tag for ovs/ovn will be nfv8-openvswitch-2 (amoralej,
15:45:18)
* ACTION: amoralej to request new tags (amoralej, 15:45:32)
* once the packages are tagged in -testing, we can send a mail to
centos-devel ML asking users to test it (amoralej, 15:49:13)
* sig members (amoralej, 15:53:32)
* ACTION: amoralej to send a mail to current members of nfv sig to ask
if they want to stay as maintainers (amoralej, 15:55:15)
* ACTION: anyone interested in participating in the sig can request
access to the sig-nfv group in
https://accounts.centos.org/group/view/sig-nfv (amoralej, 15:57:24)
* SIG communication (amoralej, 15:58:02)
* for mailing list communication we can use centos-devel with [nfv]
tag (amoralej, 15:59:53)
* irc conversations will be in #centos-devel in freenode (amoralej,
16:00:12)
* a bi-weekly meeting will be scheduled on Wednesday at 15:00 UTC
starting next week (amoralej, 16:03:15)
* ACTION: amoralej to update NFV Sig home page in wiki (amoralej,
16:04:23)
* LINK:
https://wiki.centos.org/action/newaccount/FrontPage?action=newaccount
(amoralej, 16:08:05)
Meeting ended at 16:10:57 UTC.
Action Items
------------
* amoralej to create branches in openvswitch and ovn repos
* amoralej to request new tags
* amoralej to send a mail to current members of nfv sig to ask if they
want to stay as maintainers
* anyone interested in participating in the sig can request access to
the sig-nfv group in https://accounts.centos.org/group/view/sig-nfv
* amoralej to update NFV Sig home page in wiki
Action Items, by person
-----------------------
* amoralej
* amoralej to create branches in openvswitch and ovn repos
* amoralej to request new tags
* amoralej to send a mail to current members of nfv sig to ask if they
want to stay as maintainers
* amoralej to update NFV Sig home page in wiki
* **UNASSIGNED**
* anyone interested in participating in the sig can request access to
the sig-nfv group in https://accounts.centos.org/group/view/sig-nfv
People Present (lines said)
---------------------------
* amoralej (208)
* dholler (49)
* cfontain (34)
* ykarel (17)
* centbot (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi,
During the last years OpenVswitch and OVN have become a major dependency
for several projects and SIGs in the CentOS ecosystem, including OpenStack,
oVirt and OpenShift. During this time each project has been following its
own way with limited coordination (just some opportunistic cross-tagging
between SIGs) and different approaches, rebuilding Fedora builds or FDP
srpms from ftp.redhat.com from time to time in their own tags and repos.
This has led to multiple issues and suboptimal usage resources so I think a
good step ahead would be to use existing NFV SIG [1] as a collaboration
area for all the interested projects to build, test and ship OpenvSwitch
and OVN using public SRPMs from Fast Datapath [2].
What I'm proposing is that the interested people in becoming maintainers
for OVS/OVN in NFV Sig request membership to nfv-sig group [3]. Then, we'll
coordinate to request new tags/buildroots for OVS/OVN and start building
and testing the required releases.
Any thoughts on this proposal?
Best regards,
Alfredo
[1] https://wiki.centos.org/SpecialInterestGroup/NFV
[2]
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRP…
[3] https://accounts.centos.org/group/members/sig-nfv
Hi,
I've got a task to have a small number of laptops netboot Linux over
WiFi. The kernel is loaded off the USB stick of cource, it's off topic
for now.
The WPA-supplicant daemon is started early by dracut off initrd. It
works. Mostly.
The problem is that upon shutdown systemd terminates all the processes
FIRST and unmounts filesystems NEXT.
Guess what? Upon termination, wpa-supplicant brings the wireless
interface down and the system hangs being unable to unmount now-defunct
NFSroot.
There were some discussions regarding similar matter and there's even
the RH Errata:
https://access.redhat.com/errata/RHBA-2018:2447
But I'm woking on a fully updated CentOS Linux release 7.8.2003 and
nevertheless I've got the problem.
I don't have rights to see the BZ.
https://bugzilla.redhat.com/show_bug.cgi?id=1593649
I'm deciding to use a quick and dirty hack to do a totally ungraceful
shutdown/reboot:
https://unix.stackexchange.com/questions/533307/systemd-fails-to-umount-man…
Any better ideas?
Best regards,
Dmitry Mikhailov.
How does RHEL receive the latest Firefox package before CentOS Stream ?
https://access.redhat.com/errata/RHSA-2020:2828
"This update upgrades Firefox to version 68.10.0 ESR."
Here's is CentOS Stream...
[ahall@ctream ~]$ cat /etc/centos-release
CentOS Linux release 8.2.2004 (Core)
[ahall@ctream ~]$ yum info firefox
Installed Packages
Name : firefox
Version : 68.9.0
Release : 1.el8_2
[ahall@ctream ~]$ sudo yum upgrade firefox
[sudo] password for ahall:
Last metadata expiration check: 0:11:36 ago on Tue 07 Jul 2020 03:43:44 BST.
Dependencies resolved.
Nothing to do.
Complete!
[ahall@ctream ~]$ yum info firefox-68.10.0
Last metadata expiration check: 0:06:42 ago on Tue 07 Jul 2020 03:48:12 BST.
Error: No matching Packages to list
Hi,
It appears[1] no pruning of old repodata is being done for the playground repo and the directory is excessively large (2.9GB) because of it.
If this isn't the right place to report, please accept my apologies...pointers would be appreciated.
Thanks!
[1] https://dl.fedoraproject.org/pub/epel/playground/8/Everything/x86_64/os/rep…
Hi Everyone,
As we kick off our team's work for Quarter 3 of this year, we would
like to take this opportunity to ask for your feedback on our
engagement over the last few months.
The CPE has been working on trying to improve our communication with
our communities and increase visibility on how we decide on what to
work on. We have taken many steps to improve our communication such as
IRC Office hours, regular initiative updates on our taiga board,
weekly mail and blog posts on what we achieved in each quarter and
what we are planning to work on next.
We have also had a few discussions before with some Fedora Council and
CentOS Board members on how best to engage with the CPE Team when you
wish to brief in an initiative or need to file a
bug/issue/enhancement, and as time goes by we are refining our
processes.
We would like to share with you our current approaches that we are
using for you to provide feedback on how you feel these are working.
It is important for our team to feel like their time is protected so
that they are able to enjoy a healthy work-life balance, so we have
categorized work requests that the team responds to into two
categories which we believe benefits both the CPE team and the
communities we serve:
- Project Teams
- These teams are created based on an initiative that has been:
- Received by our product owner in advance
- The work involved has been scoped, reviewed and accepted to
the backlog by the CPE Review Team
- Prioritized and actioned for work during our teams quarterly
planning sessions by CPE Team Stakeholders and Review Team
- Sustaining Team
- This team responds to 'lights on work' and requests that come in
on an ad hoc & regular basis such as:
- BAU infra/releng requests
- RFEs
- Bug fixes
## How we propose to deal with Project Team Initiatives?
* We have published deadlines for initiatives to be briefed into our
team by for each quarter here:
https://docs.fedoraproject.org/en-US/cpe/time_tables/
* Project requests that are recieved are then discussed further with
the requestor and relevant team lead(s) with our product owner
* During our monthly quarterly planning sessions, the CPE Review Team
reviews and prioritises which proposals to scope.
* All scoped proposed initiatives are brought into our QP session for
review and consideration to be worked on in the next quarter.
* Our CPE Review Team review all and vote on the initiatives they
would like to see actioned in the next quarter. Our CPE Review Team
include:
* Fedora - mmiller, mnordin, bcotton
* CentOS - rbowen, bex
* RHEL - bex, dperpeet, aslobodova
* CPE -
* CPE Product Owner - amoloney
* CPE Management - lgriffin, antcarroll, smattejiet
* CPE Team Leads - pingou, bstinson
As a picture is worth a thousand words, so here is one :)
> 
> Image Credit goes to Smera Goel, the very talented graphic designer that is currently interning as part of the Fedora Outreachy Project.
## How we propose to deal with Sustaining Team BAU requests, RFEs and bug fixes?
In order to allow the people working on initiatives to focus on them,
our Sustaining Team members will be responsible for dealing with all
these requests. They can be filed in the normal ways by community
members.
BAU infra requests can be made on the fedora-infrastructure issue tracker:
https://pagure.io/fedora-infrastructure/
BAU releng requests can be made on the releng issue tracker:
https://pagure.io/releng/
## Project Team vs Sustaining Team Work Classification
### Project Initiatives
Initiatives are weeks to months long projects involving a team of
people to work on and deliver.
We have some deadlines that we try to work towards
Examples of initiatives:
- rawhide package gating
- FAS replacement
- ...
### BAU infra/releng requests
Business As Usual (BAU) requests are simple requests that do not need
anyone to code something, just run some code to solve the request.
Examples of BAU requests:
- A new mailing list
- A new FAS/dist-git/copr group
- A new IRC channel
- A new project on ci.centos.org
- A new tag in koji
### RFE
Requests For Enhancements (RFE) are requests to improve a changes made
to either an application or a workflow used in Fedora.
### Bug fixes
Bug fixes are what they are, request to fix bugs.
Examples of bug fixes:
- Well you know: https://github.com/fedora-infra/bodhi/issues or
pagure.io/pagure/issues are full of them ;-)
This is our team's current way of working, and we are seeing the
benefits from this but wanted to have your feedback too. We would like
to publish this as a 'policy' of sorts for our team on docs.fpo and on
the CentOS wiki and want to include you in this process.
So what are your thoughts on these ideas?
Are they suitable for you or do they need more adjustments?
If they do, what are your suggestions?
To view this email in hackmd, please visit this link
https://hackmd.io/xgkPVcv1Swuy9U-wGiKQPw?view
Looking forward for your feedback,
Aoife
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
As per the process described at
https://wiki.centos.org/SIGGuide#SIGGuide.2FSIGProcess.Proposal I would
like to propose a Documentation SIG.
The SIG page -
https://wiki.centos.org/SIGGuide#SIGGuide.2FSIGProcess.Proposal - has
listed a Documentation SIG for some time, but the link went nowhere. Now
I propose that we formalize it.
The Documentation SIG is responsible for the content of the Wiki, and
other public sources of documentation. This includes, but is not limited to:
* Determining, and imposing, a hierarchy/architecture of content in the wiki
* Editing/pruning existing content when it is incorrect/outdated/obsolete
* Recruiting subject matter experts to do some of that editing
* Recruiting translators to keep our various translations in sync
The Doc SIG uses the centos-docs(a)centos.org mailing list as their
primary channel of communication, but also raises issues to centos-devel
for clarification of specific details in the docs.
The following individuals have indicated interest in being the initial
membership of this SIG.
Rich Bowen <rbowen(a)centosproject.org>
Thibaut Perrin <thibaut.perrin(a)gmail.com>
Manuel Wolfshant <wolfy(a)nobugconsulting.ro>
Jonathan Billings <billings(a)negate.org>
Pany <geekpany(a)gmail.com>
Earl Ramirez <earlaramirez(a)gmail.com>
John R. Dennison <jrd(a)gerdesas.com>
You will note that, initially, the SIG is focused on the Wiki - work
which is already ongoing by this group and many others.
An actual SIG gives structure to this effort, authority to make larger
decisions about the documentation effort, a place/time to meet regularly
to encourage others to participate, and gives the effort more visibility
within the community.
We ask that the board acknowledge this request and let us know what the
next steps are.
Thanks.
> From: Alfredo Moralejo Alonso <amoralej(a)redhat.com
> <mailto:amoralej@redhat.com>>
> Date: Wed, Jun 17, 2020 at 1:24 PM
> Subject: [CentOS-devel] Rebuilding OpenvSwitch and OVN from Fast
> DataPath in NFV Sig
> To: The CentOS developers mailing list. <centos-devel(a)centos.org
> <mailto:centos-devel@centos.org>>
>
>
> Hi,
>
> During the last years OpenVswitch and OVN have become a major
> dependency for several projects and SIGs in the CentOS ecosystem,
> including OpenStack, oVirt and OpenShift. During this time each
> project has been following its own way with limited coordination
> (just some opportunistic cross-tagging between SIGs) and different
> approaches, rebuilding Fedora builds or FDP srpms from ftp.redhat.com
> <http://ftp.redhat.com>
> from time to time in their own tags and repos.
>
> This has led to multiple issues and suboptimal usage resources so I
> think a good step ahead would be to use existing NFV SIG [1] as a
> collaboration area for all the interested projects to build, test and
> ship OpenvSwitch and OVN using public SRPMs from Fast Datapath [2].
>
> What I'm proposing is that the interested people in becoming
> maintainers for OVS/OVN in NFV Sig request membership to nfv-sig group
> [3]. Then, we'll coordinate to request new tags/buildroots for OVS/OVN
> and start building and testing the required releases.
>
> Any thoughts on this proposal?
>
I think this would be efficient.
I already applied to become a member of sig-nfv to help.
> Best regards,
>
> Alfredo
>
>
> [1] https://wiki.centos.org/SpecialInterestGroup/NFV
> [2]
> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/8Base/en/Fast-Datapath/SRP…
> [3] https://accounts.centos.org/group/members/sig-nfv
>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org <mailto:CentOS-devel@centos.org>
> https://lists.centos.org/mailman/listinfo/centos-devel
>
>
> --
> Didi
>