Hello,
quite a while ago, I asked for creation of the messaging SIG.
There is even a wiki page for this[1], and it was created over
half a year ago, the initial discussion has even been older.
However, this wasn't resolved (yet). I also have to realise,
I couldn't put the deserved energy and time to this proposal.
Nevertheless, I still think the idea is good and would help
other SIGs with their use of messaging related packages and
setups.
So with that, can we please go back to start and get this
finished? Maybe it would be benificial, if someone else
from the Centos Board could jump in and help KB with this?
Thank you,
Matthias
[1] https://wiki.centos.org/SpecialInterestGroup/Messaging
--
Matthias Runge <mrunge(a)matthias-runge.de>
I've been noticing, over the last 3 or 4 months, that many of our SIGs
are no longer in the habit of holding their (bi-)weekly meetings on IRC.
I don't know why this is happening - perhaps they're having their
discussions elsewhere, or perhaps there's nothing to discuss.
However, I want to remind you that these meetings are a window into your
work for the larger community. Your meeting minutes are public, and
useful for people who are not directly involved in the SIG but who want
to know what's happening. Even a 5-minute status checkin is valuable to
our users.
I would point you to the excellent example of this from the CBS/Infra
weekly meeting, the transcript of which you can see here:
https://www.centos.org/minutes/2019/February/centos-devel.2019-02-18-14.02.…
Note that there's only one meeting participant, but the meeting is held
to offer the opportunity for discussion should anyone need it.
Please do get back in the habit of meeting regularly.
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
Next week, I'll be at FOSSAsia, along with a few other projects (Fedora,
ManageIQ, Dogtag).
If you'd like for me to promote the work that you're doing with your
SIG, there's a way for you to do that with our pamphlet template.
At
https://github.com/rbowen/centos-community-tools/tree/master/pamphlets
you can see the template(s) for creating your own SIG pamphlet, and two
examples of what this will look like.
You can take the file CentOS-SIGs.odt and fill it in with the relevant
information about your SIG - what it's for, how to get involved, how to
consume the output of the SIG, and so on - and send me a copy, or send a
pull request with your new file.
I'll be printing a few hundred copies of each when I get to the event.
Thanks.
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
** Recipient inbox full **
Your message couldn't be delivered to curtiskwong101(a)gmail.com. Their inbox is full, or it's getting too much mail right now.
The response was:
Storage quota exceeded
916;
Mon, 04 Mar 2019 21:07:41 -0800 (PST)
X-Google-Smtp-Source: APXvYqxI7hDKwVDzkjqa0+y4WWedAVi4kDWTGuPiGOAfbEcSyBRTn=
Jf7cAYy3MFkg68cVb51tYZ9
X-Received: by 2002:aa7:c413:: with SMTP id j19mr18083097edq.200.1551762460=
674;
Mon, 04 Mar 2019 21:07:40 -0800 (PST)
ARC-Seal: i=3D1; a=3Drsa-sha256; t=3D1551762460; cv=3Dnone;
d=3Dgoogle.com; s=3Darc-20160816;
b=3DKw+M5jmeMYKfIBrZf/jy9RvYJXjYe7EB95UqrdnYboU1o4TM4FM4B8w6dA92Kbf=
az2
ZwgfZaamTdUyj8LgCDZ7EM20cgik57Cr/Wy8pIabwLfC9aiDu1iCiPL7sL05txyeW4=
t7
mLyFwOJK2482erE02oRAVS/eeq8kFXkWcWALequJYYTKFnxesM/V7aTzGSzJYOkU0w=
Tm
ivKzK+ynhKywmBcDBLkX63gGXlD1mY5CnF/FolZIZ+zd9mnX9cXlCSI2BzMqu1QvWE=
vN
E9KnY+z9qTESsrRzoKHV/7mTWOnJnEjF8FDd5NnLuibvePvGZRA+M/DzlvA/DRjoy1=
LB
1b1g=3D=3D
ARC-Message-Signature: i=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dgoog=
le.com; s=3Darc-20160816;
h=3Derrors-to:list-subscribe:list-help:list-post:list-archive
:list-unsubscribe:list-unsubscribe:list-id:precedence:message-id
:date:subject:to:reply-to:sender:from:content-transfer-encoding
:mime-version:dkim-signature:delivery-date;
bh=3D/jbaWpoOJZvGnrF9kTuUPYpBmQ9mMY1Fid1Hn3YI9i0=3D;
b=3DOSZCnTkRG6l1OLQtOGXGpGe6IHEYv+ah5R+WUEl5Qmo+eUQ2N1MmdnQ2bt6r0xW=
Zbn
xZNqE4zb/XjOtjME5LQQKe5R0fvVhKVQTcasspWlHXlCrpNUJ2pHxkmxt9xu/ozvMt=
iC
CIIfL9wZGF6aT1OoKHoVzNzeMMAS5YHYH/J2ZCfvZYlePZNIosyx/gnvIxTjNFa27l=
9N
fEDAVvllgo/z8DpaeDPT29qR23JWkpaqq/DOU9oigySLedJHncxtzoF/wuc7mXz0un=
nH
rdgtmYJcjwEciZef+G++hll6SqEI5fpZuNEC2Ejtnw3FJVOn2ynCJ3ii2XHosjGmI/=
O3
OSfQ=3D=3D
ARC-Authentication-Results: i=3D1; mx.google.com;
dkim=3Dpass header.i=3D(a)opayq.com header.s=3Dabine header.b=3DdetRcS=
Ko;
spf=3Dpass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com designa=
tes 184.105.182.73 as permitted sender) smtp.mailfrom=3DFWD.8ltx5hf60pqr@op=
ayq.com;
dmarc=3Dpass (p=3DNONE sp=3DNONE dis=3DNONE) header.from=3Dopayq.com
Return-Path: <FWD.8ltx5hf60pqr(a)opayq.com>
Received: from 123-he.filtered.junkemailfilter.com (retry2.ctyme.com. [184.=
105.182.73])
by mx.google.com with ESMTPS id p21si1448746eda.281.2019.03.04.21.0=
7.40
for <curtiskwong101(a)gmail.com>
(version=3DTLS1_2 cipher=3DECDHE-RSA-AES128-GCM-SHA256 bits=3D128/1=
28);
Mon, 04 Mar 2019 21:07:40 -0800 (PST)
Received-SPF: pass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com design=
ates 184.105.182.73 as permitted sender) client-ip=3D184.105.182.73;
Authentication-Results: mx.google.com;
dkim=3Dpass header.i=3D(a)opayq.com header.s=3Dabine header.b=3DdetRcS=
Ko;
spf=3Dpass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com designa=
tes 184.105.182.73 as permitted sender) smtp.mailfrom=3DFWD.8ltx5hf60pqr@op=
ayq.com;
dmarc=3Dpass (p=3DNONE sp=3DNONE dis=3DNONE) header.from=3Dopayq.com
Delivery-date: Mon, 04 Mar 2019 21:07:40 -0800
Received: from 137-he.filtered.junkemailfilter.com ([184.105.182.137]:40970=
) helo=3D137-he.filtered.junkemailfilter.com
by retry2.junkemailfilter.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SH=
A384:256)
(Exim 4.90_1)
id 1gzgy3-0003Iv-Iw on interface=3D184.105.182.73
for curtiskwong101(a)gmail.com; Fri, 01 Mar 2019 04:08:43 -0800
Received: from smtp4.opayq.com ([23.21.143.60]:58376) helo=3D[23.21.143.60]
by opayq-outbound.junkemailfilter.com with esmtps (TLSv1.2:AES256-SHA256:2=
56)
(Exim 4.90)
id 1gzgxw-0005zW-C4 on interface=3D184.105.182.150
for curtiskwong101(a)gmail.com; Fri, 01 Mar 2019 04:08:36 -0800
DKIM-Signature: v=3D1; d=3Dopayq.com; t=3D1551441801; b=3DdetRcSKo8drZ6WdPc=
w/TlIRNSAp/KaNgNX+TVHHakpyanhnYtrp5BDBHviLW+onj1V3axLOKe0yaWPKa8nIwuhmuUVsL=
WrTxvSbnRHEuWVPxeDLTuOnTQsqZ4E8biRUHzHCk+pYJnaZoTCxKYu/YsEvwrer58Zn7tuqN/L3=
rpuQ=3D; s=3Dabine; c=3Drelaxed/relaxed; a=3Drsa-sha256; bh=3D/jbaWpoOJZvGn=
rF9kTuUPYpBmQ9mMY1Fid1Hn3YI9i0=3D; h=3DDate:From:Reply-To:Subject:To:List-U=
nsubscribe;
MIME-Version: 1.0
Content-Type: text/plain; charset=3D"us-ascii"
Content-Transfer-Encoding: 7bit
X-GetAbine-Processed: 1
From: "centos.org [Masked]" <FWD.8ltx5hf60pqr(a)opayq.com>
Sender: "centos.org [Masked]" <FWD.8ltx5hf60pqr(a)opayq.com>
Reply-To: FWD.8ltx5hf60pqr(a)opayq.com
To: 82ee9d11(a)opayq.com
X-GetAbine-Sender: centos-devel-bounces(a)centos.org
X-GetAbine-Disposable: 82ee9d11(a)opayq.com
X-GetAbine-Host-Address: 23.21.143.60
Subject: CentOS-devel Digest, Vol 169, Issue 1
Date: Fri, 01 Mar 2019 12:00:04 +0000
Message-ID: <mailman.17.1551441604.5429.centos-devel(a)centos.org>
X-BeenThere: centos-devel(a)centos.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The CentOS developers mailing list." <centos-devel.centos.org>
List-Unsubscribe: <https://lists.centos.org/mailman/options/centos-devel>,
<mailto:centos-devel-request@centos.org?subject=3Dunsubscribe>
List-Unsubscribe: <mailto:unsubscribe-345585171-82ee9d11@opayq.com>, <https=
://emails.abine.com/disableDisposable?fwd=3DFWD.8ltx5hf60pqr@opayq.com>
List-Archive: <http://lists.centos.org/pipermail/centos-devel/>
List-Post: <mailto:centos-devel@centos.org>
List-Help: <mailto:centos-devel-request@centos.org?subject=3Dhelp>
List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos-devel>,
<mailto:centos-devel-request@centos.org?subject=3Dsubscribe>
X-Sender-Domain: centos.org
X-Spamfilter-host: plato.junkemailfilter.com - http://www.junkemailfilter.c=
om
X-Key-ID: ODJlZTlkMTFAb3BheXEuY29tIGNlbnRvcy1kZXZlbC1ib3VuY2VzQGNlbnRvcy5vc=
mcgMjAxOS0wMy0wMSAwNDowMzoyMC4zODUgMWd6Z3NxLTAwMDdPZi03TA=3D=3D
X-Content-flags: 3rxi aging application attachment available bowen componen=
ts dashes date dating details devel developers email email-adr game games h=
ello here https information irxq link links longword meetings message month=
number-text opics optout phone-num php please public re record regards rep=
lying request special specially stars subscribe subscribed text-plain thank=
s time-ref twitter unsubscribe utf-8 via web work
X-Domain-list: centos.orgsteadfastdns.netsteadfast.net
X-Sender-Host-Address: 208.100.23.70
X-Sender-Host-Name: mail.centos.org
Errors-to: <>
X-Key-ID: Y3VydGlza3dvbmcxMDFAZ21haWwuY29tIGZ3ZC44bHR4NWhmNjBwcXJAb3BheXEuY=
29tIDIwMTktMDMtMDEgMDQ6MDg6MzYuNTI1IDFnemd4dy0wMDA1elctQzQ=3D
X-Sender-Domain: junkemailfilter.com
-------------------------Blur-------------------------
This email is forwarded from a MASKED EMAIL you created using Blur. (https=
://dnt.abine.com/#help/faq/faq-whataremaskedemails).
IF THIS IS SPAM, CLICK HERE TO BLOCK:
https://dnt.abine.com/#/block_email/82ee9d11@opayq.com/FWD.8ltx5hf60pqr@opa=yq.com
Want to shop safely and privately online? Go Premium: https://dnt.abine.com=
/?pk_campaign=3DmaskHeader#premium
-------------------------by Abine-------------------------
Send CentOS-devel mailing list submissions to
centos-devel(a)centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-devel
or, via email, send a message with subject or body 'help' to
centos-devel-request(a)centos.org
You can reach the person managing the list at
centos-devel-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-devel digest..."
Today's Topics:
1. C7 shim 15-2 update - No announce (Phil Wyett)
2. Re: GlusterFS 6.0RC Test Days (27th, 28th Feb) (Niels de Vos)
3. Re: C7 shim 15-2 update - No announce (Johnny Hughes)
4. Re: C7 shim 15-2 update - No announce (Johnny Hughes)
5. Re: C7 shim 15-2 update - No announce (Phil Wyett)
6. Re: Lightning talks at Red Hat Summit (Rich Bowen)
7. Re: Weekly SIG meetings (Matthias Runge)
8. Messaging SIG (Matthias Runge)
----------------------------------------------------------------------
Message: 1
Date: Thu, 28 Feb 2019 12:31:03 +0000
From: Phil Wyett <philwyett(a)kathenas.org>
To: "The CentOS developers mailing list." <centos-devel(a)centos.org>
Subject: [CentOS-devel] C7 shim 15-2 update - No announce
Message-ID:
<0f248d87a6878518a35666735cffd06bc931a808.camel(a)kathenas.org>
Content-Type: text/plain; charset=3D"UTF-8"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
There has been a shim update (to 15-2) but no related announcement. Is one =
on
the way?
Regards
Phil
- --=20
*** If this is a mailing list, I am subscribed, no need to CC me.***
Playing the game for the games sake.
IRC: kathenas
Web: https://kathenas.org
Github: https://github.com/kathenas
GitLab: https://gitlab.com/kathenas
Twitter: kathenasorg
GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJcd9SSAAoJEDM/YNywubt3j1gP/jynow8VlCNISND5qZgXcsHJ
/FYAOXLEvt/zoTeHENVFxcRHZ1LxZ09IgrbywZIOqSIwwmmf0/zgrMM2ovPa+1Zb
+agGKbW8b8ejHGMc646IrxqilpdsBHWppulZqSZSHBSbkW1H0jmq6nVSJZKEaaZm
Z/L/EsfI5BmhhgqqgIr/Znibr/CpS1B1pf3lqVHgdt2A2dsB2yBeZqVkL9+h3rXi
I09LMa3irr4eS1gn0xetiZpoCdcD3Er382hfbLhXO+Eq14XbdR+UueJuWS3+UDxR
A/2EIPzNn8D9/sXlwRpAxeoAN4jnYEt4Ft2sG5hpR68xj7ge2lYNbEBA5Wc3eSgA
bISZqI2JL2/YvFzI79GFBkClvXG8zzLAseqC91MuzO9cgyScT2FusGuDBdv1lOFj
0CmDqsZLkxXu1vRkeWZs8ynxZD+02R+WWNX+MgB7viEp+7FV3RSh2S1VB5AwREWw
8iMAb9ohe6mIpoPNRCaVjCe6xf0wubY+r6MRU4ARv+weU4zzW2tovIAcY+OgeFkM
/ZQyemGOaIIDTMzgtSmRBwYni5CKmZRL+OTdaHo6toAo/bvhbjIOBFKtDKLYHF3V
fL3GZSpRlfi7a/UOYbzrncFaLidIWXg4aL3OMsMazwvYOgjeIGdFG3Q6+dn6Ajvh
mnjm6dfac9KyT2J2rWq9
=3D4jKQ
-----END PGP SIGNATURE-----
------------------------------
Message: 2
Date: Thu, 28 Feb 2019 15:24:08 +0100
From: Niels de Vos <ndevos(a)redhat.com>
To: "The CentOS developers mailing list." <centos-devel(a)centos.org>
Subject: Re: [CentOS-devel] GlusterFS 6.0RC Test Days (27th, 28th Feb)
Message-ID: <20190228142408.GP3839@ndevos-x270>
Content-Type: text/plain; charset=3Dutf-8
On Mon, Feb 25, 2019 at 04:46:19PM -0500, Rich Bowen wrote:
> Gluster users/developers,
>=20
> We are calling out our users, and developers to contribute in validating
> ?glusterfs-6.0rc? build in their usecase. Specially for the cases of
> upgrade, stability, and performance.
>=20
> Full details and participation information may be found on the
> Gluster-devel mailing list, here:
> https://lists.gluster.org/pipermail/gluster-devel/2019-February/055876.ht=
ml
Packages from the CentOS Storage SIG are now availabl
----- Message truncated -----
If you expect to be at Red Hat Summit [1] and if you have some community
project that you'd like to tell the world about, please consider
submitting a Lightning Talk for the Community Central section of the event:
https://docs.google.com/forms/d/e/1FAIpQLSc5phwBJclz7ubP9B3Ax_W7Fr9S0Olcgzk…
Lightning talks will be 15 minutes, plus 5 for Q&A. If what you have to
talk about is shorter than that, that's fine too.
Thanks!
--Rich
[1] Red Hat Summit - https://www.redhat.com/en/summit/2019 - May 7-9,
Boston, MA, USA.
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
There has been a shim update (to 15-2) but no related announcement. Is one on
the way?
Regards
Phil
- --
*** If this is a mailing list, I am subscribed, no need to CC me.***
Playing the game for the games sake.
IRC: kathenas
Web: https://kathenas.org
Github: https://github.com/kathenas
GitLab: https://gitlab.com/kathenas
Twitter: kathenasorg
GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJcd9SSAAoJEDM/YNywubt3j1gP/jynow8VlCNISND5qZgXcsHJ
/FYAOXLEvt/zoTeHENVFxcRHZ1LxZ09IgrbywZIOqSIwwmmf0/zgrMM2ovPa+1Zb
+agGKbW8b8ejHGMc646IrxqilpdsBHWppulZqSZSHBSbkW1H0jmq6nVSJZKEaaZm
Z/L/EsfI5BmhhgqqgIr/Znibr/CpS1B1pf3lqVHgdt2A2dsB2yBeZqVkL9+h3rXi
I09LMa3irr4eS1gn0xetiZpoCdcD3Er382hfbLhXO+Eq14XbdR+UueJuWS3+UDxR
A/2EIPzNn8D9/sXlwRpAxeoAN4jnYEt4Ft2sG5hpR68xj7ge2lYNbEBA5Wc3eSgA
bISZqI2JL2/YvFzI79GFBkClvXG8zzLAseqC91MuzO9cgyScT2FusGuDBdv1lOFj
0CmDqsZLkxXu1vRkeWZs8ynxZD+02R+WWNX+MgB7viEp+7FV3RSh2S1VB5AwREWw
8iMAb9ohe6mIpoPNRCaVjCe6xf0wubY+r6MRU4ARv+weU4zzW2tovIAcY+OgeFkM
/ZQyemGOaIIDTMzgtSmRBwYni5CKmZRL+OTdaHo6toAo/bvhbjIOBFKtDKLYHF3V
fL3GZSpRlfi7a/UOYbzrncFaLidIWXg4aL3OMsMazwvYOgjeIGdFG3Q6+dn6Ajvh
mnjm6dfac9KyT2J2rWq9
=4jKQ
-----END PGP SIGNATURE-----
Gluster users/developers,
We are calling out our users, and developers to contribute in validating
‘glusterfs-6.0rc’ build in their usecase. Specially for the cases of
upgrade, stability, and performance.
Full details and participation information may be found on the
Gluster-devel mailing list, here:
https://lists.gluster.org/pipermail/gluster-devel/2019-February/055876.html
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
Hi there,
I would like to implement a command , to be able to disable all variants(or at least the ones causing performance impact). As per the RH article: https://access.redhat.com/articles/3311301, we would be able to only disable spectre variant 2 and 3(pti).
I need an option to disable variant 1, 3a and 4 as well. Some of the recent articles suggest that options like no_spectre_v1, no_spectre_v2 and spec_store_bypass_disable parameters are available in latest versions of kernel(4.15 and above).
https://www.zdnet.com/article/linux-kernel-gets-another-option-to-disable-s…https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?h…
Can this be made available in our Centos 7 kernels? Or is there any plan for RH to implement the same in any future release?
Regards,
Nupur
Hi Folks,
I've done a bit of work on centpkg, now that we have a testbed at
git.stg.centos.org. The goal here is to allow centpkg and fedpkg
(Fedora's site) to both understand the different formats. The test
version of centpkg described below is the first step in that direction.
Basically you can try this out by pulling a container image:
`podman pull quay.io/bstinsonmhk/centpkg:develop`
Why a container image?
- The patches to make this happen involve invasive changes to rpkg,
that are still in flight (basically,
https://pagure.io/rpkg/pull-request/393)
- I wanted to bake in the sources and configs to develop this a little
faster as we find problems.
What's included, and where to file bugs?
- centpkg from:
https://bitbucket.org/bstinsonmhk/centpkg/branch/develop
- rpkg from:
https://pagure.io/fork/bstinson/rpkg/tree/centpkg-inbound
- fedpkg from:
https://pagure.io/fedpkg/tree/master
Here's how I run it for testing CentOS packages (substitute your centos
user certificate and a path to RPMs to fit your workstation):
`podman run --rm -it -v
/home/bstinson/.centos.cert:/home/centpkg-user/.centos.cert:Z -v
/home/bstinson/rpms:/home/centpkg-user/rpms:Z
quay.io/bstinsonmhk/centpkg:develop`
If you're a SIG member, you can push to a sig branch. For example, if I
was a mamber of the atomic SIG I could do:
# Clone the repo
$ centpkg clone -b c7 a2ps
# Download the sources from C7
$ centpkg sources
# Change to a SIG branch
$ git checkout -b c7-sig-atomic-cockpit-preview
# Manual push is needed here until we work out a way to register the
# new branches
$ git push -u origin c7-sig-atomic-cockpit-preview
# Upload sources to the SIG branch in the lookaside
$ centpkg upload SOURCES/a2ps-4.14.tar.gz SOURCES/i18n-fonts-0.1.tar.gz
# CBS does not yet build from SCM, so still need srpms
$ centpkg scratch-build --srpm
# Try out a fedora branch
$ centpkg switch-branch f28
$ centpkg clean
# From a Fedora branch this should use your Fedora creds
$ centpkg scratch-build # this should work with Fedora's ko
What I need help with:
- Review the open PRs to rpkg as they come in
- Help me find more places where we need to use the new 'Layout'
objects (that is where rpkg has paths hard-coded)
- Test Fedora workflows, and other commands with centpkg
- Help add new commands
- to request SIG branches
- to translate from one layout to another (ex. bringing a Fedora
branch into a CentOS SIG branch)
Happy building!
--Brian
Hi,
In October 2018, we (pre)announced that we were working on a
consolidated pagure infra for git.centos.org and src.fedoraproject.org.
(https://lists.centos.org/pipermail/centos-devel/2018-October/016997.html)
We asked feedback from community and one of the remarks we had was about
being able to follow commits for all /rpms/*
While there were requests to have that available through pagure API
(for people already using the gitblit RPC feature of current
https://git.centos.org instance), another idea was to simply send that
to a message broker, so that people can just subscribe to that broker on
a particular topic and consume the message payloads posted there.
As such MQTT support landed in pagure, we decided to upgrade (both
instances) and we have (only at the CentOS side) implemented MQTT
notifications to a "public" broker
Example :
This dummy commit (specific branch) :
https://git.stg.centos.org/rpms/bacula/c/61cd3575ba64b5f7afbf16eeb5c8dea729…
(automatically replicated to
https://src.stg.fedoraproject.org/rpms/bacula/c/61cd3575ba64b5f7afbf16eeb5c…)
posted the following json message on our MQTT staging broker :
git.stg.centos.org/git.receive {"forced": false, "agent": "arrfab",
"repo": {"custom_keys": [], "name": "bacula", "parent": null,
"date_modified": "1539692831", "access_users": {"owner": ["centosrcm"],
"admin": [], "ticket": [], "commit": []}, "namespace": "rpms",
"priorities": {}, "close_status": [], "access_groups": {"admin": [],
"commit": [], "ticket": []}, "milestones": {}, "user": {"fullname":
"CentOS Sources", "name": "centosrcm"}, "date_created": "1539692831",
"fullname": "rpms/bacula", "url_path": "rpms/bacula", "id": 6, "tags":
[], "description": " Cross platform network backup for Linux, Unix, Mac
and Windows"}, "end_commit": "61cd3575ba64b5f7afbf16eeb5c8dea7293b1241",
"branch": "c7-sig-altarch-test", "authors": [{"fullname": "Fabian
Arrotin", "name": "arrfab"}], "total_commits": 1, "start_commit":
"61cd3575ba64b5f7afbf16eeb5c8dea7293b1241"}
The first part is just the topic, while the message payload is the json
How can you subscribe to that MQTT broker (if you want to automate some
workflow) ?
The only requirement is to trust our ACO (https://accounts.centos.org)
CA cert and also to have your TLS cert from ACO
All those steps are done automatically through centos-cert (from
centos-packager, see https://wiki.centos.org/HowTos/CentosPackager)
From that point, you can use your MQTT client of choice (mosquitto_sub
from mosquitto pkg, or python-paho-mqtt for python client, etc) and
point to mqtt.stg.centos.org:8883
Simple example with mosquitto_sub :
mosquitto_sub --cafile ~/.centos-server-ca.cert --cert ~/.centos.cert
--key ~/.centos.cert -h mqtt.stg.centos.org -p 8883 -t
git.stg.centos.org/# -v
Hope that it helps people willing to get automatic notifications in
"real-time" when repositories are created or that there are new commits
landing there.
Worth noting that it's still only in staging, but once we have a green
light, we should migrate git.centos.org to pagure with the same features
set as the one deployed on staging.
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab