June 2015 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

CI for kubernetes, docker, etcd and other atomic packages
by Jan Chaloupka 15 Jul '15

15 Jul '15

Hi, at the moment kubernetes, docker, etcd and other atomic packages has no CI testing in CentOS. The packages built for CentOS are taken from Fedora's repositories. There is already an effort to create CI for Fedora builds. Currently kubernetes has its own CI job which can be taken as an template for other jobs for docker, etcd, etc. in Fedora. The job among other things consists of a builder, i.e. script that can be broken down into two parts: installation and testing. The installation part takes care of installing, updating and downloading all necessary builds. Testing part runs tests. As the script is universal and differs only in the installation part, other distributions can reuse it. RHEL does that after a simple modification of the installation part. The workflow is following: update kubernetes ci job for Fedora, if it works, update it for RHEL. I would like to continue in the same sense for CentOS. Create a job for centos's kubernetes. The question is where should it run? All jobs (for Fedora and RHEL) are run in redhat's internal Jenkins. For CentOS it would be better to run the job in its own CI environment as this is not the only job. Docker, possible etcd and cadvisor can have its own set of sets that are suitable. So distributing CI effort among all distributions that are involved is natural. Another option is to run all centos jobs related to atomic packages in the internal Jenkins. Why should we bother with running centos's jobs in redhat's environment? I have all jobs at one place so I can update them all at once and they don't get out of sync. It does not take me much time to create another ci job for CentOS once I have created one for Fedora. However, I need a trigger that will trigger the job (I have started a discussion on setting up fedmsg for CentOS that could provide such a trigger [1]). Second, the CI environment is internal so everyone who wants to take a look at run jobs must have RH credentials. If CentOS's CI is used the responsibility for maintaining all jobs and keeping them in sync is completely on CentOS side. Or something between? What about I will first test the new or updated job for CentOS in internal env and then forward all changes to someone responsible for CentOS's CI which would be who? I am not against taking care of this part if I get an access/credentials to CentOS to access your CI. Some jobs in internal RH Ci environment contain private data so I can not go public. What can go public is the builder (script) for Fedora. However I don't see any benefit sharing the script without the entire *.yaml files that create the job. On the other hand if you provide a public repository I can contribute to I will update CentOS's jobs as changes or new jobs appears. Provided your template for a job. [1] http://lists.centos.org/pipermail/centos-devel/2015-June/013415.html Kind Regards Jan

4 4

Problems with custom centos-atomic-host build
by Andres Toomsalu 08 Jul '15

08 Jul '15

Hi, Im trying to do custom centos-atomic-host build - from unmodified https://github.com/CentOS/sig-atomic-buildscripts configuration source and following instruction in https://developerblog.redhat.com/2015/01/08/creating-custom-atomic-trees-im… blog post series. Im able to produce ostree and installer.iso image - BUT rpm-ostree-toolbox creates ostree tree with missing grub file, resulting in a failing installer. More details about this problem here: https://github.com/projectatomic/rpm-ostree-toolbox/issues/77 Commands used for ostree and installer creation were: --- rpm-ostree-toolbox treecompose -c ~/repos/sig-atomic-buildscripts/config.ini --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/ rpm-ostree-toolbox installer -c /root/repos/sig-atomic-buildscripts/config.ini \ --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/ \ --outputdir /var/www/html/latest/ --overwrite cp ~/repos/sig-atomic-buildscripts/centos-atomic-host-7.ks /var/www/html/ virt-install --name=atomic-iso --memory=1024 --vcpus=1 \ --disk=/var/lib/libvirt/images/test.qcow2,size=5 \ --location /var/www/html/latest/images/installer.iso \ --noautoconsole --accelerate --os-type=linux --os-variant=rhel7 \ --extra-args "ks=http://192.168.122.1/centos-atomic-host-7.ks" --- Another issue is that also imagefactory KVM centos-atomic-host image build fails in anaconda install stage - complaining about unknown missing file - might be the same problem - not sure... Command used for kvm image creation: --- rpm-ostree-toolbox imagefactory \ -c /root/repos/sig-atomic-buildscripts/config.ini -i kvm \ --ostreerepo /srv/rpm-ostree/centos-atomic-host/7/ \ --outputdir /srv/rpm-ostree/centos-atomic-host/7/images --- Error screenshot from imagefactory launched build VM console: http://prntscr.com/7lq38e From the build VM /tmp/anaconda.log: --- 21:40:35,454 INFO anaconda: Creating xfs on /dev/vda1 21:40:36,242 INFO anaconda: executing ostreesetup=<pykickstart.commands.ostreesetup.RHEL7_OSTreeSetup object at 0x7fdd038d3110> 21:40:36,570 ERR anaconda: Failed to pull from repository: Server returned status 404: Not Found --- Last lines from the build VM /tmp/program.log: --- 21:40:36,339 INFO program: Running... ostree --repo=/mnt/sysimage/ostree/repo remote add --set=gpg-verify=false installmedia http://192.168.122.1:47990/ 21:40:36,377 DEBUG program: Return code: 0 --- Any suggestions how to debug it further? Where should I file a bug report? Kind regards, -- <http://www.getpostbox.com>---------------------------------------------- Andres Toomsalu,andres(a)opennodecloud.com <mailto:andres@opennodecloud.com>

3 4

CentOS CLA (Contributor License Agreement)
by Fabian Arrotin 06 Jul '15

06 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As it seems FAS (Fedora Account Ssytem) has been chosen as the central authentication system for CentOS.org infra, I'm now trying to find documentation around it .. One thing that I see is the CLA (default in Fedora, that each user must sign and agree with) so that means that for FAS we also need to have one. Has someone already looked at it and so what would be the CentOS CLA that we'll use when people will register/sign for a FAS account on centos.org ? - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlWREFIACgkQnVkHo1a+xU73jwCdF8/yIovWYalefgwBmV7npnbs aDwAn0ka66T3xgC5OoziXEja5e4f8X99 =Kt+l -----END PGP SIGNATURE-----

10 23

[NFV SIG][CBS] Question building DPDK
by Joseph Gasparakis 27 Jun '15

27 Jun '15

Hi all, I have some questions as this is the first time I am using CBS :-) First of all I have done all the prework on my .koji directory and I have verified I can build: <snap> [jgaspara@jg-vm ~]$ koji list-permissions --mine build </snap> I am trying to build DPDK 2.0 (commit id 493db80afd) and I (believe I) have successfully created a dpdk package for nfv7-opnfv-arno-[testing|release]: <snap> [jgaspara@jg-vm ~]$ koji add-pkg --owner "jgasparakis" nfv7-opnfv-arno-testing dpdk [jgaspara@jg-vm ~]$ koji add-pkg --owner "jgasparakis" nfv7-opnfv-arno-release dpdk </snap> Then, I suppose I need to kick off a git build, but it seems like I need to somehow add the DPDK git tree to the permitted SCMs for CBS: <snap> [jgaspara@jg-vm ~]$ koji build nfv7-opnfv-arno-el7 "git+http://dpdk.org/git/dpdk?#493db80afd009eea35ee7d95ad4aba49df5113a3" Created task: 15451 Task info: http://cbs.centos.org/koji/taskinfo?taskID=15451 Watching tasks (this may be safely interrupted)... 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): open (x86_64-2.cbs.centos.org) 15452 buildSRPMFromSCM (/git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): free 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): open (x86_64-2.cbs.centos.org) -> FAILED: BuildError: dpdk.org:/git/dpdk is not in the list of allowed SCMs 1 free 0 open 0 done 1 failed 15452 buildSRPMFromSCM (/git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): free -> FAILED: BuildError: dpdk.org:/git/dpdk is not in the list of allowed SCMs 0 free 0 open 0 done 2 failed 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3) failed </snap> Am I right? If so can someone please change permissions for the repo or let me know how I can add the repo to the allowed ones? If not can you point me to what I am doing wrong? :-) Again, the DPDK repo is http://dpdk.org/git/dpdk, the commit id that matches tag v2.0.0 is 493db80afd009eea35ee7d95ad4aba49df5113a3 and the spec file lives in pkg/dpdk.spec. I am assuming CBS will pick it up and create the rpm based on that spec file. Thanks! Joseph

2 2

c7-power64 proof of concept
by James O'Connor 25 Jun '15

25 Jun '15

I realize the altarch-power64 SIG is not officially established, but I want to share some technical progress. I created a private c7-power64 koji hub/builder environment using a pair of Fedora 22 PowerKVM guests. One guest is running Fedora 22 ppc64 and serving as a ppc/ppc64 koji builder. The second guest is running Fedora 22 ppc64le and serving as a ppc64le koji builder, koji hub, postgresql and httpd server. A pair of koji builders (ppc64, ppc64le) could be setup to integrate with cbs.centos.org instead of creating a separate koji hub. I created a c7-power64-build tag that contains arches "ppc64 ppc64le" and I am using Fedora 22 external koji repositories to serve as a build backstop until enough c7-power64 rpms are built. I am currently building with src rpms from http://vault.centos.org/7.1.1503/os/Source/SPackages/ although some ppc64le specific patches will need to be pulled from the c7-ppc64le branch on git.centos.org $ koji taginfo c7-power64-build Tag: c7-power64-build [2] Arches: ppc64 ppc64le Groups: build, srpm-build This tag is a buildroot for one or more targets Current repo: repo#16: 2015-06-24 18:16:29.668635 Targets that build from this tag: c7-power64 External repos: 10 f22-ppc64 (http://c7-ppc64.localnet/mirror/f22/ppc64/os/) 15 f22-ppc64le (http://c7-ppc64le.localnet/mirror/f22/ppc64le/os/) Inheritance: 0 .... c7-power64 [1] Next steps involve resolving some toolchain hiccups. c7 binutils fails to build with Fedora 22 gcc-5.1 and c7 gcc.ppc64 fails to build because Fedora 22 doesn’t have a 32-bit libc.so.6 needed for multilib gcc. To preserve the RHEL 7 ppc/ppc64 multilib environment a few interim c7 gcc/glibc builds will be needed. Happy to share any configuration steps or help do the work on official CentOS infrastructure as we move forward with an altarch-power64 SIG.

2 2

Weird Qt painting bug on CentOS7
by Justin Clift 22 Jun '15

22 Jun '15

With the upstream DB4S project (previously known as SQLite Browser), we've had a bug reported filed of a weird Qt painting problem... which only happens on CentOS 7: https://github.com/sqlitebrowser/sqlitebrowser/issues/354#issuecomment-1117… The direct sceenshot here: https://cloud.githubusercontent.com/assets/1067355/8144743/f944b27e-11e3-11… In the field names (middle section, not bottom section), the new name "XX" is overwriting the old name "Field1". On other OS, and other Linux distro's, the "Field1" text has been correctly wiped already so only shows "XX". Has anyone seen anything like this before, or know how we should figure out what's going wrong? Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift

2 1

"Rebuild" images ready for testing
by Joe Brockmeier 21 Jun '15

21 Jun '15

Good News, Everybody! KB let me know today that we've got some images of the rebuild of RHEL Atomic Host ready to test. You can find images here: http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/ This includes 2 flavors of Vagrant box (libvirt/KVM and VirtualBox), a qcow2 image, and ISO image suitable for installing onto bare metal or other environments. We've done some preliminary testing but more is needed. We're hoping to announce next week, so I'd invite all interested parties to test these and let us know if you find any anomalies. Best, jzb -- Joe Brockmeier | Open Source and Standards (OSAS) jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://projectatomic.io/

4 6

Finished a prototype of GSoC project: Implement a new doc toolchain
by Lei Yang 20 Jun '15

20 Jun '15

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and contributor discuss on Pagure 4. When the pull request can be accepted, it is marked as “fixed”, and the pull request on github is automatically merged 5. New change is synced to Pagure (doc website will update according to Pagure repo, to be implemented later) We have made a prototype performing the steps above, and is now running ;) Next we plan to integrate a CI so the doc can be built in real time and ready for staff to review. Could you please give us some suggestions about the workflow above and about the toolchain? The original GSoC idea can be found here: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain <http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain> We use Pagure as a part of the toolchain. Pagure is an excellent git-centered forge created by Pierre-Yves Chibon <pingou(a)pingoured.fr <mailto:pingou@pingoured.fr>>. Currently Pagure is in its early stage and the APIs and web hooks are changing and improving. We are working closely with Pierre to better integrate Pagure into the toolchain. In the future we plan to sync complete pull request so that discussion can happen either on github or Paugre, and contributor doesn’t need to leave github in the whole process, which lowers the barrier of contributing a lot. To test it, you may create a PR on github. A corresponding issue will be created automatically on Pagure, so you may go to Pagure.io to check it. If you want to merge the PR, change the status of issue from Open to Fixed on Pagure (need admin access to the repo, if you want to test this part, please email me or Kunaal <kunaalus(a)gmail.com <mailto:kunaalus@gmail.com>> so we can add you as admin). Once the issue is marked as Fixed, the PR on github will be merged. GitHub repo link: https://github.com/yangl1996/doc-test <https://github.com/yangl1996/doc-test> Pagure repo link: https://pagure.io/docs-test <https://pagure.io/docs-test> The syncing tool is a prototype and is a basic part of the toolchain. Please tell us what you think about the workflow, the syncing tool and the idea. Thank you in advance :) Also, we are not very sure whether running a Pagure instance will add much workload to sys admin team. What’s your idea? Thanks! Regards, Lei

1 0

Re: [CentOS-devel] [atomic-devel] "Rebuild" images ready for testing
by Karanbir Singh 18 Jun '15

18 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/06/15 22:57, James wrote: > On Thu, Jun 18, 2015 at 4:49 PM, Joe Brockmeier <jzb(a)redhat.com> > wrote: >> KB let me know today that we've got some images of the rebuild of >> RHEL Atomic Host ready to test. >> >> You can find images here: >> >> http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/ > > > RHEL or CentOS ? > > The CentOS Atomic Host is a downstream rebuild of the RHEL Atomic Host. These are images of the CentOS Atomic Host. regards, - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVg0qZAAoJEI3Oi2Mx7xbteYYH/RtSt0JGUJKTUwU4HfRMRxBO pt/RwKAjdeLVU+ZD2Zg7vy12X1YEsrjcxlYzLw4usnNtyBa6rpgHZ/DFGoP85BCX cr0BKXjT4QrK02urlX4GndnST84jcYZYEl/WvpNIK2VfvPtSwRSxLqsaqqMWVHq9 psy0B0vP+thQrdFEd0DKg9xuEMu2HKUXQyYS4Tz4Rs2aOkknEVuM5lcHScL8+/OK 58FuDvAX9b3NITpPtEup4hyhuBM7/HUtoLlpr0uYNwBjnWQpws9S4Og+EsKj7BPK XLUIqrqReQSTkUzzVlFSFygR+DRhLvOzQoBHpolpkWuoHZzH1Iibua/okkrm9yA= =I/mK -----END PGP SIGNATURE-----

1 0

CentOS Cloud SIG meeting notes
by Rich Bowen 18 Jun '15

18 Jun '15

===================== #centos-devel Meeting ===================== Meeting started by rbowen at 15:05:53 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-06-18-15.05.log.html . Meeting summary --------------- * CentOS Cloud SIG (rbowen, 15:06:00) * Roll Call (rbowen, 15:06:31) * GSoC Update (rbowen, 15:08:03) * ACTION: tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. (tmrts, 15:12:11) * LINK: https://github.com/TamerTas/cloud-init (tmrts, 15:12:25) * ACTION: tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. (tmrts, 15:13:31) * LINK: https://github.com/TamerTas/cloud-init (tmrts, 15:13:38) * Action items (rbowen, 15:24:56) * LINK: http://seven.centos.org/2015/06/introduction-to-cloud-sig-talk-in-fudcon-pu… (rbowen, 15:27:08) * ACTION: rbowen will write posts about "big tent" on seven.centos.org (rbowen, 15:28:03) * Packaging/CI update (rbowen, 15:28:25) * Open Floor (rbowen, 15:32:23) * LINK: https://github.com/apevec/centos-release-openstack/ <= this is the content of our release package (number80, 15:41:43) Meeting ended at 15:52:46 UTC. Action Items ------------ * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * rbowen will write posts about "big tent" on seven.centos.org Action Items, by person ----------------------- * rbowen * rbowen will write posts about "big tent" on seven.centos.org * tmrts * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * rbowen (50) * number80 (31) * dneary (23) * tmrts (18) * kbsingh (16) * kushal (12) * asad_ (9) * centbot (3) -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Office Hours / Happy hours
by Karanbir Singh 18 Jun '15

18 Jun '15

hi, Over the last couple of months, an increasing number of people have been getting in touch with me to ask about various things in the project and also to find out how they can get started contributing to the project. So what I'd like to do is start up a set of office-hours slots in a week where I will make myself available on irc, phone, web ( hangout ? ) and anyone can come along for a chat. I shall also try and have other people come along and join in from the existing contributors pool. To start things off, I am going to be available on all Thursdays: - 08:30-09:00 am UTC (9:30am London, 2:00pm, India, 4:30pm Singapore) - 04:00-04:30 pm UTC (5:00pm London, 12noon Eastern, 9am Pacific ) During this time, you can find me on #centos-devel irc.freenode.net ( as 'kbsingh'), and you can also call me on the phone at +44 207 009 4455. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 15

[PATCH/cbs-tools] create_sig script: Loop through all koji permissions
by Brian Stinson 17 Jun '15

17 Jun '15

A user may have multiple permissions in addition to admin. This patch looks through all permissions in case admin is not the only permission assigned to a user. --- scripts/create_sig.sh | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/scripts/create_sig.sh b/scripts/create_sig.sh index 349c01b..281500d 100755 --- a/scripts/create_sig.sh +++ b/scripts/create_sig.sh @@ -81,7 +81,14 @@ fi # Check if user is allowed to send command to koji and has 'admin' permission KOJI=`which koji` PERM=`$KOJI list-permissions --mine` -if [ "$PERM" != "admin" ] +ADMIN=false + +for P in $PERM +do + [[ $P == 'admin' ]] && ADMIN=true; break +done + +if [ "$ADMIN" != true ] then echo "[ERROR] Koji misconfigure/missing admin privilege for creating SIG tags" exit 1 -- 1.8.3.1

1 0

[CI] Short scheduled Jenkins restart between 15:00 and 16:00 UTC
by Brian Stinson 17 Jun '15

17 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, We are working on adding a few plugins to Jenkins and we need to schedule a very short reboot (we are expecting it to take less than 30 seconds) sometime between 15:00 and 16:00 UTC. The reboot will happen in that window as soon as the currently running jobs finish. If you have any questions, please send email to ci(a)centos.org Cheers! Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVgYKJAAoJEIMGvNKzCweM3s4P/1MYqpJGPjzXrLaCJDxZXYVg Ebrknsbl/sfXIEsbS3lXqfEPhaRvhghLawG+oNN9EKiaEUe9ETEAWtKnLOBQvH3A gxgxnNDoLsK+aBAL2IaRnJDFE0Pm5sh6u6tSkziZdczARvaoffAuNeYfW3FdtTxI VdTbz2o7EsPNaudYDdH1LO1LytnloW3z4GJxkyy4CaV3IOuJF+m35fOLK0qxqQKU MZ9F7oyGgXHWJKrpklC+GxuUufylXj6S0QW38+NgxeRA0L4v/TNmoM9nfAQCaMR5 FL4mn15no96sXBV1yAJ46mOVeij5EBLYGancc5alHeN5eDRhOl7dVUmbw/311BwI n3e+GC4ZKxK1Wn7N/nS1l0OLf+2nO0QU0VOfPqj0PizWxXzJV5kCYsHC10Y7uExH ZtPwSVgtZ8hAmP455SjfD3HvbkHUK11ors8IIg1Wa+WAxQFqVqR/W19S0Z6/fwKf l9nXtd3uWy9Z/GavO/TKxOQ605c66gIbksuFh13XwgtVEcBgDOI9/qM+Jy7BB/AA iMCgkXgxVMJ0F530fzGmCO3RT2KGmqgHHmfaathd3gHIEUJyETITwk5DfCIgou5G N+LVm6/kLn8LH7g27zud1H1OhxpInzEw65eXR+jSiDUbfXgBobS9vZZRT23pN6VQ xdE8lmjB0u5e1dyF4300 =pX6g -----END PGP SIGNATURE-----

1 2

Kubernetes package new build tag
by Navid Shaikh 17 Jun '15

17 Jun '15

Hi, There was a discussion to move kubernetes package under virt7-docker-*, earlier the kubernetes used to get updated under virt7-testing tag. Added the package in `virt7-docker-common-testing` tag, and tried building it for target `virt7-docker-common-el7`, however it failed with error: 15144 build (virt7-docker-common-el7, kubernetes-0.19.0-0.4.gita8269e3.el7.src.rpm): FAILED: BuildError: package kubernetes not in list for tag virt7-docker-common-candidate Then, I added the package in tag `virt7-docker-common-candidate` and the build [1] is green. I could see the built packages in repo `virt7-docker-common-candidate` [2]. Is kubernetes package populated in correct repo? I was expecting it go in testing repo `virt7-docker-common-testing` [3] first. Please correct me if I am missing something here. [1] http://cbs.centos.org/koji/buildinfo?buildID=1330 [2] http://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/Package… [3] http://cbs.centos.org/repos/virt7-docker-common-testing/x86_64/os/Packages/ -- Navid

2 1

inter-SIG dependencies
by Lokesh Mandvekar 16 Jun '15

16 Jun '15

Should've sent this earlier, but better late than never. At the last virt SIG meeting we were looking at good places to keep packages like cockpit, which I'm not sure belongs in a particular SIG yet. Also, it was mentioned that we could make SIG repos depend on each other, and IIUC, KB has an example (in theory atleast) demonstrating that. Over to you KB.. -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

3 3

[PATCH] better error reporting on invalid dir
by Pat Riehecky 15 Jun '15

15 Jun '15

Recently I've found it handy to know where I am when the various commands complain about an invalid source directory. So I've added slightly more detail to the resulting error message. Odds are it shouldn't bug any existing tools and help with troubleshooting mass commands. Pat Riehecky (1): Better error reporting on invalid dirs get_sources.sh | 3 ++- into_srpm.sh | 3 ++- return_disttag.sh | 3 ++- show_possible_srpms.sh | 3 ++- 4 files changed, 8 insertions(+), 4 deletions(-)

1 1

help with the IPA tests
by Karanbir Singh 15 Jun '15

15 Jun '15

hi, Can someone help debug why the ipa tests are failing when run inside a VM ? ref: https://ci.centos.org/view/AtomicApp/job/vagrant-libvirt-base/27/console I've bumped machine resources to multiple cores and 4G of ram, but afaict, its not failing due to running out of resources here. seems to work fine when run in the same infra, but on the bare metal machine. Which makes me think it might be network related ? this is the same test running on the bare metal: https://ci.centos.org/view/CentOS-Core-QA/job/CentOS-Core-QA-t_functional-c… regards -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

4 4

SIGS with outstanding blockers on the CBS
by Brian Stinson 13 Jun '15

13 Jun '15

Hi All, I've been lurking at a few SIG meetings this week to get an idea of which SIGs are blocked on things in the CBS. So far here is a high-level list of outstanding items: - Central Authentication for Koji/Gitblit/Lookaside (Priority: HIGH) - Lookaside upload tools (Priority: HIGH) - New release of CBS build tools - centpkg, /usr/bin/cbs (Priority: HIGH) - EPEL package import features in the build tools (Priority: Medium) - Notifications/Messaging from Koji (Priority: Medium) If your SIG is blocked on something in the CBS or if you have any feature requests, please let me know. Cheers! Brian -- Brian Stinson brian(a)bstinson.com | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

3 4

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-06-10)
by Honza Horak 10 Jun '15

10 Jun '15

SCLo SIG meeting will be at 15:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * sync-up on current status - how does it look with the devtoolset-3 test SCL - any news from infrastructure (look-aside cache), any ETA? * propose some other topics :) Honza

2 1

CentOS Linux 6 Vagrant
by Timothy Rees 10 Jun '15

10 Jun '15

Great to see a project CentOS 7 box made available for Vagrant. Are there any plans to provide an official CentOS 6 variant with the same update cycle? Cheers, Tim

2 2

devtoolset-3 rebuild in SCLo
by Honza Horak 09 Jun '15

09 Jun '15

On the last meeting [1] we talked about whether we need maven and rh-java-common for rebuilding devtoolset-3. Unfortunately it is a requirement right now, so we need to have maven and rh-java-common collections first. However, the maven and rh-java-common SCL dependencies are needed just for the devtoolset-3-ide part, so for devtoolset-3-toolchain and devtoolset-3-perftools we may remove the requirements temporarily. Anyway, there have been requests for devtoolset and gcc-5 especially, often from other projects based on CentOS, so copr builds are not enough. We're still not ready with the centpkg/lookaside-cache things, but what about to create necessary tags from devtoolset-3 collection and build packages from srpms for now? Thomas, is it ^ possible? What information do you need from me? Let's limit on sclo part and RHEL-7 only. Based on the tags we consulted before, that should mean to create: * sig-sclo7-devtoolset-3-sclo tag * sclo7-devtoolset-3-sclo-el7 target and associated buildroot Correct? Will it be possible to tag built packages (I speak still about scratch builds) to sig-sclo7-sclo, which other SIGs could depend on? [1] http://www.centos.org/minutes/2015/may/centos-devel.2015-05-20-14.31.html [2] https://copr.fedoraproject.org/coprs/rhscl/devtoolset-3-el7/builds/ Honza

5 5

Setting up fedmsg for centos
by Jan Chaloupka 08 Jun '15

08 Jun '15

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 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

5 6

CentOS 7 (1503) i686 Beta Architecture
by Johnny Hughes 08 Jun '15

08 Jun '15

All, The Beta release of the 32-bit (i686) Architecture of CentOS-7 (1503) is currently on build logs. Right now, only the boot.iso is available, but after some testing from the users here with feedback, we can spin another tree with fixes and actual installer isos. http://buildlogs.centos.org/centos/7/os/i386/ updates are also here: http://buildlogs.centos.org/centos/7/updates/i386/ Current known issues are: 1. If installing on a QEMU (kvm) i386 VM, you must modify the VM cpu to use "copy host cpu" http://bugs.centos.org/view.php?id=8748 2. The gnome desktop will not exit or log out from the menu. http://bugs.centos.org/view.php?id=8834 If someone can figure out how to fix this issue, it would be much appreciated :) ====================== Please report bugs on bugs.centos.org or to this Centos-Devel mailing list will we do the beta testing and lets see if we can find/fix all the issues before the full release of this arch. Thanks, Johnny Hughes

12 21

CBS/Infra Meeting 08-Jun-2015 14:00 UTC
by Brian Stinson 08 Jun '15

08 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey All, It's time for another meeting to talk about the Community Build System[0]. We will meet in #centos-devel on irc.freenode.net Proposed Agenda: - - Status Updates: - General - Central Auth - - Fedmsg[1] in the CBS - - Merging the ci.dev.c.o and ci.c.o Jenkins instances Cheers! Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVdK1jAAoJEIMGvNKzCweM7WUP/RULhbw6LCSzB/Hu5sMwVldp /ZGB/PQLXFGInUIv7McT5pfjlD5VBgsG+B8XXepxs/YbMQM/cGufRy0qhRubvs/U PNGxNAjZlu8RNTt9r/wVyZm2QoMmKzq67k4EZKCTr1cXT2KpIG5OoNgW3PuQESNH ygKNtrLJAK4EiPOoStIFVkEGfCL8YbRXvWVXpGglrLRWC1rzXbgjLfBOFF7CA3sI SVBGhVW368VJTRC1zrEUr1GVX69afPP4OKtdojxnMYPf2so0l9X0fpAxlg7qKAac Wx56uqF7cq7P4E5Fozk2J2yVfy24p61z9E4U+FPRzBcUSAUHr2kjS8iH1+BfjaZh Zk0B9VgT3WaKb5SMf0WWJQ/nn8ION42DV4ca15DHARqJS3MgUPnKOIYQRm3uUNfU hQD0SKs+eJR0wK84fC/QTyCRNUwZE9RLUrO4PJ53tI5vy9LdWcU0qBEwIZvMPgE2 7L1JZRWeJky8WbNRQrCBy1tTvRXGOcikx8S98GbZoPnw47Oa6qZ8rjq6Qb+z3Z26 g+VfIuQQ//Esh36wv4ir+fa8+IXkm59EDOyfjSVfkuCzat4MFX3Z4w+H0R9Bvs3c mc42197T+rgjKaCOOVWCBWSMEdjYTbfSSYE9jC+6gyRqT4T+mkLSTjlLMkyWssUJ 5D/L4NCwQlHnQBH6Q4zQ =pqC0 -----END PGP SIGNATURE-----

1 1

python build script for ci.centos.org
by Karanbir Singh 08 Jun '15

08 Jun '15

hi, I've just pushed a basic script that uses the Duffy[1] interface to request machines, run jobs, discard machines. The source for this is at https://github.com/kbsingh/centos-ci-scripts . Its pretty simple, but should work. Help to expand this into a more functional script is welcome. Specially getting some exception handling around failed builds and failed requests to Duffy. Hopefully this script should be helpful enough that projects using ci.centos.org can just use it as is. Someone mentioned the thought of writing a Duffy plugin for Jenkins directly, and I am not sure if that is very useful over a simple script like this. regards [1]: http://wiki.centos.org/QaWiki/CI/Duffy - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Automated tracking of RPMs from EPEL
by Lalatendu Mohanty 08 Jun '15

08 Jun '15

Hi, For Storage SIG (Gluster) we have dependency on a pkg i.e. userspace-rcu from EPEL . Looks like we can not have EPEL repo linked to the SIG target. So we have to rebuild the pkg in SIG and maintain it. I am not interested to maintain the pkg myself in SIG as I dont have skills to maintain it. However I am fine to rebuild the pkg if I get notified if a newer version of it is available in EPEL or we have some automation do the rebuild. I am looking for suggestion or alternative of how this is being done in other SIGs or can be done in CBS. Thanks, Lala

1 0

Resources Needed for Doc Toolchain Project [GSoC]
by kunaal jain 05 Jun '15

05 Jun '15

Hi, As discussed earlier about the workflow, I and Lei will need a server space to host Bugzilla, a test repository at Github + a git repository at git.centos.org. This is temporary, required for development and testing. Please let us know how do we obtain the same? We need it to get started on our project. Thanks! Regards, Kunaal

6 12

Re: [CentOS-devel] Regarding GSoC project : Documentation Toolchain
by Lei Yang 05 Jun '15

05 Jun '15

> On Sat, May 30, 2015 at 1:04 AM, kunaal jain <kunaalus at gmail.com <http://lists.centos.org/mailman/listinfo/centos-devel>> wrote: > > The typical workflow might look like this: > > > > 1. Author writes content in markdown language. > > 2. Makes a pull request on github. > > Is this github.com or, a git instance off CentOS infrastructure? Authors are supposed to make a pull request on github. > > > 3. Corresponding to the pull request a issue is created on bugzilla. > > 4. CentOS staff can either review the article on github pull request, or on > > bugzilla. > > I would recommend using one tool for handle inbound and review. Having > 2 tools that need to be kept synchronized would add overhead that you > don't want to deal with. Also, it has the effect of puzzling > contributors. Thanks for your suggestion! Staff will do the review only on bugzilla, but we think some contributors are only familiar with github, so we sync the comments between two platforms, so contributors don’t need to leave github to finish the whole process. > > > 5. Comments are two way synced. > > 6. At each point the article can be viewed on bugzilla, using an extension > > we propose to make. > > 7. After many iterations of commenting, and improving, article is finally > > accepted. > > Have you considered review workflow tools like Gerrit? We considered Gerrit and other code review platforms. However we are handling markdown or some similar markup languages, so we plan to build the doc on a CI and let the staff review the built docs. > > > 8. Staff tags it, and pushes to git.centos.org. > > 9. Using git.centos.org, new website is generated and pushed. > > 'Website' or, is the content rendered from the version control (g.c.o) > and pushed live? The content is rendered from g.c.o. built into HTML files using static site generator tool like jekyll. Regards, Lei

2 4

Meeting log from this week's cloud sig meeting
by Kushal Das 05 Jun '15

05 Jun '15

=============================== #centos-devel: CentOS Cloud SIG =============================== Meeting started by kushal at 15:00:32 UTC. The full logs are available at http://centos.org/minutes/2015/may/centos-devel.2015-05-28-15.00.log.html . Meeting summary --------------- * Roll Call (kushal, 15:00:39) * tmrts is developing a cloud instance contextualization tool as a GSoC project (kushal, 15:04:45) * ACTION: tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. (kushal, 15:06:57) * tmrts's project will focus on CentOS Atomic Host. (kushal, 15:08:01) * Update from OpenNebula (kushal, 15:09:52) * jmelis is studying about CBS. (kushal, 15:11:39) * jmelis is developing a set of tests to test the CBS based installs. (kushal, 15:12:43) * LINK: http://meetbot.debian.net/Manual.html (kushal, 15:14:27) * Openstack updates (kushal, 15:15:21) * Open Floor (kushal, 15:22:41) * LINK: http://community.redhat.com/blog/2015/05/highlights-from-rdo-meeting-at-ope… (kushal, 15:24:29) * LINK: https://review.openstack.org/#/c/185187/ (number80, 15:26:06) * planning a RDO track at FOSDEM CentOS dojo (number80, 15:29:18) Meeting ended at 15:35:26 UTC. Action Items ------------ * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. Action Items, by person ----------------------- * tmrts * tmrts will put up the roadmap to a github repo and share the link in the centos-devel list. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (62) * rbowen (30) * number80 (26) * jmelis (11) * tmrts (10) * Arrfab (5) * alphacc (3) * centbot (3) * Evolution (3) * hughesjr (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal Das -- Fedora Cloud Engineer CPython Core Developer Director @ Python Software Foundation http://kushaldas.in

2 1

Re: [CentOS-devel] Where to GSoC blog?
by Lei Yang 05 Jun '15

05 Jun '15

Hi, I think writing on a central place like seven.centos.org <http://seven.centos.org/> is a great choice. I’ve written some blog articles in Chinese, and I am willing to write them in English and post on seven.centos.org <http://seven.centos.org/> :) Regards, Lei

1 0

Regarding GSoC project : Documentation Toolchain
by kunaal jain 05 Jun '15

05 Jun '15

Hi, Over the last week, Lei and I have been researching about the review platform where the content submitted can be reviewed, commented, tagged and pushed. This will be an alternative to github pull requests interface, which will thus reduce our dependency on Github in case Github changes its API anytime in future. Even firefox is considering using Github as an alternative medium to receive contribution. http://gregoryszorc.com/blog/2015/01/12/utilizing-github-for-firefox-develo… Lei made a great chart comparing the platforms. https://drive.google.com/file/d/0B9sUy41_Rk3KdGl4RVhDSXZIZmc/view?usp=shari… So overall Bugzilla looks a great option. But there is one major flaw, we need to view the article submitted at each point(code review) which bugzilla lacks. The solution to this is creating a plugin for markdown previewing. The typical workflow might look like this: 1. Author writes content in markdown language. 2. Makes a pull request on github. 3. Corresponding to the pull request a issue is created on bugzilla. 4. CentOS staff can either review the article on github pull request, or on bugzilla. 5. Comments are two way synced. 6. At each point the article can be viewed on bugzilla, using an extension we propose to make. 7. After many iterations of commenting, and improving, article is finally accepted. 8. Staff tags it, and pushes to git.centos.org. 9. Using git.centos.org, new website is generated and pushed. There are many challenging tasks in this, especially the bugzilla issue creation on pull request and two way comment sync. This has never been done before, but we looked at the API and think we can make it work. Another challenging task is markdown preview on bugzilla. Please let us know, what you think about this? Regards, Kunaal -- Regards, Kunaal Jain

2 1

Cloud SIG meeting minutes (2015-06-04)
by Rich Bowen 05 Jun '15

05 Jun '15

Thanks to those that attended the Cloud SIG Meeting. Minutes follow. Minutes may also be found online at: http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.txt http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.html Full logs may be found at: http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.html http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.txt ===================== #centos-devel Meeting ===================== Meeting started by rbowen at 15:00:53 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-06-04-15.00.log.html . Meeting summary --------------- * LINK: https://etherpad.openstack.org/p/cloud_sig_agenda (rbowen, 15:01:05) * rollcall (rbowen, 15:01:16) * Update on Juno/Kilo releases (rbowen, 15:04:19) * GSOC updates (rbowen, 15:06:03) * My project is related to atomic, fedora and centOS (tmrts, 15:07:43) * LINK: https://github.com/TamerTas/cloud-init/blob/master/ROADMAP.md (tmrts, 15:08:38) * First few weeks I'll be focusing on the core part of the cloud-init (users, network, ssh, custom scripts) then I'll get to the specifics of each target system (tmrts, 15:09:37) * Open Floor (rbowen, 15:17:22) * ACTION: I'll add CentOS 6 to the cloud-init test environment (tmrts, 15:22:26) Meeting ended at 15:28:31 UTC. Action Items ------------ * I'll add CentOS 6 to the cloud-init test environment Action Items, by person ----------------------- * **UNASSIGNED** * I'll add CentOS 6 to the cloud-init test environment People Present (lines said) --------------------------- * rbowen (33) * kbsingh (19) * tmrts (17) * apevec (6) * centbot (2) * number80 (2) * alphacc (1) * Evolution (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

moving ci.dev
by Karanbir Singh 05 Jun '15

05 Jun '15

hi guys, I believe we are fairly well established on the ci.centos.org infra to now consider moving the ci.dev instances from their present location at godaddy.com. This would also allow us to run the ci.dev nightly tests on baremetal machines. It would also allow us to consolidate the jenkins instance, and maybe SIGs and other tested projects could use the distro runs as a trigger for their own validation / testing. Brian, can we find a slot in one of the CBS meetings to work through this ? Regards, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

4 4

Image builds in cbs.centos.org
by Karanbir Singh 05 Jun '15

05 Jun '15

hi, Why do the image builds in cbs/koji take so long ( upto 45 minutes ) when the same kickstart run with virt-install will finish in ~ 3 min, and the qemu-img converts take a few minutes as well. On similar spec hardware as the koji builders themselves. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Where to GSoC blog?
by Karsten Wade 04 Jun '15

04 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One of the tasks of the GSoC students is to write up their work and experiences as they go, typically with at least one blog post per week. Often projects then put the students on the main project planet or a special GSoC-specific planet. KB had the idea that instead we might want students and mentors to use e.g. seven.centos.org to blog from instead. I've asked around and can't be sure how project planets get used. Some people read them, many don't. Individual blogs get picked up in e.g. Google, so that's one reason for using seven.centos.org -- to improve searching around the GSoC topics. Thoughts? We're a bit in to the process, I should have pushed on a decision sooner, so I appreciate any quick feedback. Thanks - Karsten - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVwnyIACgkQ2ZIOBq0ODEEwRQCg2hbch9DkVjoJEL6NKTa8tu6I gmsAoMsQjTAqZep1z2IhT8S928YLVsds =wSd/ -----END PGP SIGNATURE-----

2 1

CentOS SCLo SIG sync-up meeting on #centos-devel next week
by Honza Horak 03 Jun '15

03 Jun '15

Sorry for late announcement, but I'm not able to hold today's meeting, let's try the next week. However, if there are some updates since last meeting two weeks back about look-aside cache or koji tags stuff, give us know, please. Adam, Brian, have you got in touch somehow? Honza

1 0

CentOS 7 i686 Repository for mock (Multilib Builds)
by Mykola Ulianytskyi 02 Jun '15

02 Jun '15

Hi I need to build multilib packages for CentOS 7 using mock. Is CentOS 7 i686 devel repository publicly available (repohost)? mock.cfg example: http://buildlogs.centos.org/c7-updates/kernel/20141224145219/3.10.0-123.13.… Thank you -- With best regards, Mykola

7 7

[NFV SIG] Need info
by Gasparakis, Joseph 01 Jun '15

01 Jun '15

Hi Haikel/Dave, As discussed in: http://wiki.centos.org/HowTos/CommunityBuildSystem I created bug #8784 in the CentOS BT (Project Buildsys/Component community builds): http://bugs.centos.org/view.php?id=8784 ...and I believe the next step is for one of you to add a note to the issue to verify my role in the SIG. Can you please take care of it? Thanks Joseph -- Joseph Gasparakis Software Engineer Network Platform Group Software Defined Networking Division

6 10

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2015