devel

devel@lists.centos.org

5 participants
4656 discussions

Re: [CentOS-devel] Setting up fedmsg for centos
by Jan Chaloupka 01 Jun '15

01 Jun '15

On 06/01/2015 03:28 PM, Karanbir Singh wrote: > can we move this conversation to the centos-devel list please. > > - KB > > On 01/06/15 14:25, Jan Chaloupka wrote: >> Hi, >> >> CentOS does not have any equivalent to fedmsg bus [1] at the moment. >> What is it used for? Services (koji, pkgdb, ...) can send messages about >> their state and result of tasks they run into the bus to notify other >> service which can react accordingly. Thus creating a modular >> infrastructure. E.g. koji send a message about finished build. Agent >> read the message, trigger a jenkins job and run additional tests on the >> build. Daily statistics about number of finished /failed builds can be >> collected. Other application can have their own use cases. Example of >> bus topology [4]. [5] is another source of some info about fedora >> infrastructure. >> >> What needs to be done to set up the bus? Basic demo and setup of fedmsg, >> fedmsg-relay is at [3]. First would be great to setup the bus for koji. >> Koji runs on CentOS 6. fedpkg package is in epel6 repository [2]. We >> will be needing fedmsg-hub, fedmsg-relay, koji-hub and koji-plugin parts >> in the topology at the moment [4]. CentOS koji and Fedora koji are not >> exacly the same but both APIs are compatible. So maybe take an >> inspiration from Fedora's koji plugin. In order to set up bus and >> clients, endpoints has to be set. Setting of endpoints is discussed at >> [6]. Context of endpoints is described at [3]. Configuration files are >> shared and must be the same on all machines using the bus. Bus messages >> can be saved into database [7]. >> >> What we can start with? >> 1) create an instance of centos/fedora for fedmsg to run >> 2) create/reuse koji plugin (where it can be found?) >> 3) set/implement koji plugin to send messages for fedmsg >> >> What other application do you have in centos that could use fedmsg? >> >> Once there is a running msg bus, instances set, etc., it will be easier >> to debug and test. >> >> Ralph, Pierre, what would be the optimal distribution of instances for >> fedmsg? Is one instance of centos enough? What would be the best first >> step to set up fedmsg? Where can I found koji-plugin, resp. its >> implementation? This question is confusing. I supposed fedmsg is a master and all services are slaves. However, as Pierre-Yves informed me there is no master. fedmsg bus is decentralized and distributed among all services. Thus thus the configuration distributed on each host. >> This is only a discussion at the moment. Any other ideas are >> appreciated. Other issues and problems will arise while configuring the >> bus and koji. >> >> [1] https://github.com/fedora-infra/fedmsg/ >> [2] http://koji.fedoraproject.org/koji/buildinfo?buildID=630367 >> [3] http://fedmsg.readthedocs.org/en/latest/deployment/ >> [4] http://fedmsg.readthedocs.org/en/latest/topology/ >> [5] https://fedoraproject.org/wiki/Messaging_SIG >> [6] http://fedmsg.readthedocs.org/en/latest/config/#term-endpoints >> [7] http://fedmsg.readthedocs.org/en/latest/deployment/#store-all-messages >> >> Kind Regards >> Jan >

1 0

Fwd: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR)
by Alan Bartlett 29 May '15

29 May '15

Forwarding to the CentOS development list to ensure that there is the appropriate exposure. ---------- Forwarded message ---------- From: Carl George <carl.george(a)rackspace.com> Date: 29 May 2015 at 00:04 Subject: [CentOS-docs] proposal for Community Approved Third Party Repos (CATPR) To: Mail list for wiki articles <centos-docs(a)centos.org> Howdy, I am proposing a process for 3rd party repositories that would allow them to have their release RPM added the the CentOS Extras repository. http://wiki.centos.org/CarlGeorge/CATPR I would like to start a discussion about approving the proposal and how to move forward. Carl George IUS CoreDev Team _______________________________________________ CentOS-docs mailing list CentOS-docs(a)centos.org http://lists.centos.org/mailman/listinfo/centos-docs

1 0

arm/armv7hl rebuild and arm-dev list reminder
by Fabian Arrotin 29 May '15

29 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Just a little reminder that we have a CentOS list dedicated to arm platform (http://lists.centos.org/mailman/listinfo/arm-dev) So if you're intersted in arm/aarch64 (arm64), feel free to read the archives, subscribe to the list and join the party ! - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVoaKgACgkQnVkHo1a+xU7zQgCfdEfCng64DHhrd+bZ8RaPZNXN G4gAn1Zr1Ytwwc2YUQnUmB5kbadkgtDL =CB8v -----END PGP SIGNATURE-----

1 0

[PATCH] Backport futex: Ensure get_futex_key_refs() always
by Adrian Muraru 29 May '15

29 May '15

Fix for http://bugs.centos.org/view.php?id=8803 <http://www.google.com/url?q=http%3A%2F%2Fbugs.centos.org%2Fview.php%3Fid%3D…>

2 1

Suggest Cockpit 0.59
by Stef Walter 27 May '15

27 May '15

I'd like to suggest packaging Cockpit 0.59 in CentOS. I'm not sure of the current state of affairs, but 0.59 is a stable version that makes use of CentOS branding when running on CentOS. If you have questions about packaging, or Atomic vs. normal install, I'd be happy to help. Stef

2 1

Status update on the Central Auth project
by Brian Stinson 27 May '15

27 May '15

Hi All, I thought I would give a quick update on the status of the Central Authentication project. Most of these items are being tested in a staging environment and are not yet in production. Here's what I've worked on so far: User DB ======= FAS (https://github.com/fedora-infra/fas) was chosen as our authentication system, but it needed some work to remove the bits specific to The Fedora Project. That debranding work can be found here: https://github.com/bstinsonmhk/fas These are the major things that happened: - Replaced Fedora branding/assets with CentOS branding/assets - Patched out bugzilla operations - Patched out the CLA/FPCA Tool Integration - Gitblit ========================== git.centos.org is a public-facing gitblit (http://gitblit.com) instance, and needed a plugin to authenticate with FAS. That work was a chance for me to brush up on some Java :) and can be found here: https://github.com/bstinsonmhk/gitblit-fas-plugin As of now, this plugin is functional but some optimizations are still needed in jFAS2 (the component that communicates with the FAS instances) Tool Integration - Lookaside ============================ The lookaside is for non-text sources necessary for building RPMs in the CBS (e.g. upstream source tarballs). Some modifications were needed to the upload script from Fedora to accommodate our infrastructure. Special thanks to Howard Johnson for getting us started: https://github.com/bstinsonmhk/centos-lookaside Staging Instance ================ Very soon, a staging setup will be complete and running in devcloud (http://wiki.centos.org/DevCloud) This will include shadow instances of each of our services (koji, gitblit, FAS, etc.) for testing purposes. Mostly this has been infrastructure work, but I'm happy to talk about the details if anyone is interested. Outstanding action-items I'm working on for the staging instance: - Put shadow-gitblit behind a servlet container (Tomcat) - Add the test CA to shadow-koji - Write up an easy testing workflow (connecting to the private network) How to help =========== As soon as we have a staging instance up and running I'd like a bit of help testing the whole workflow, from initial signup to joining a group to building a package. If you're a member of a SIG and would like to spend a couple of minutes going through this please let me know and I'll contact you when we're ready. Feel free to look through the repositories listed above, and add comments or patches here on the mailing list. Cheers! Brian

1 0

Bridge Networking for Xen in Box proposal
by Gautam Malu 26 May '15

26 May '15

Hi, I am doing xen in box gsoc project. The aim of the project is to have custom installer ISO which delivers xen stack running on c7 along with necessary bridge networking configuration. But I am getting confused over how to package bridge networking settings, so that I can deliver that during installation itself. I can use bridge-utils and package ifcfg-* files as differnet package. But for that I need to have the network information like how many NIC are present in the system, and which NIC is active is it eth0 or wlan0. I can probably write a script to set up bridge networking, which can be used to start bridge networking and stop, and ship that script as a package. Any suggestions? Best regards, Gautam Malu

4 3

No CBS meeting Monday 25-May-2015
by Brian Stinson 25 May '15

25 May '15

Hi All, Since it's a holiday in quite a few places on Monday, there will not be a meeting this week. I do plan on hanging around in #centos-devel for a little while starting at 14:00 UTC if anyone has anything to discuss. Cheers! --Brian

1 0

CBS tag for rpm-ostree-toolbox dependencies
by Jason Brooks 21 May '15

21 May '15

The atomic sig is using rpm-ostree-toolbox for building our trees and images. rpm-ostree-toolbox is in the cbs, under atomic7-testing, but there are a bunch of install deps needed from epel: https://gist.github.com/jasonbrooks/6b32df17c142d2cf1b1c They should be easy enough to build in the cbs, and some of them are already there, built for other projects. Does it make sense to tag these deps as atomic7 as well, or should we use some other tag? Thanks, Jason --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com

1 0

[release] Kilo EL7 and Juno EL6 repos available from CentOS Cloud SIG
by Rich Bowen 21 May '15

21 May '15

The CentOS Cloud SIG is pleased to announce the availability of OpenStack Kilo package repositories for CentOS 7, and Juno repositories for CentOS 6. These are the result of the last few months of work by the Cloud SIG membership, and, of course, we owe a great deal of gratitude to the upstream OpenStack community as well. The CentOS 7 Kilo repository may be found at http://mirror.centos.org/centos/7/cloud/x86_64/ The Juno CentOS 6 repository may be found at http://mirror.centos.org/centos/6/cloud/x86_64/ The actual -release files will reside in Extras, so that you can yum install centos-release-openstack-kilo for Kilo and yum install centos-release-openstack-juno for Juno, without needing to mess with repo configurations. See also the Juno EL6 RDO QuickStart at http://wiki.centos.org/Cloud/OpenStack/JunoEL6QuickStart CentOS cares about OpenStack. We test all of our cloud images against OpenStack, in the CentOS 5, 6, and 7 branches. The CentOS Cloud SIG is very keen on facilitating community efforts at CentOS, and we have resources available for CI, repos, and other needs, which the community can use. We welcome your participation in this effort. We're dedicated to ensuring that CentOS is a solid, dependable platform for deploying OpenStack, and that all versions of OpenStack are thoroughly tested against CentOS, and vice versa. You can find out more about the CentOS Cloud SIG, and how to get involved, at http://wiki.centos.org/SpecialInterestGroup/Cloud and about the RDO project at http://rdoproject.org/ -- Rich Bowen - rbowen(a)redhat.com http://rdoproject.org/

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