July 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

Build scripts for CentOS 7 AMIs
by Brian Lalor 04 Aug '15

04 Aug '15

I’ve been unable to find the build scripts used to create the CentOS 7 AMIs. I have found them for docker, vagrant, and I believe openstack. Can those please be published? — Brian Lalor blalor(a)bravo5.org

3 6

Testing CentOS as a hypervisor in different scenarios
by Karanbir Singh 04 Aug '15

04 Aug '15

Hi, this has come up in a few conversations, and its worth looking into. Various efforts including the CentOS Cloud Instance SIG, would like to test their VM instances under a CentOS 6/7 hypervisor setup. I am sure the Virt SIG guys would like to also have these VM instances tested on hypervisors and environments they curate. Whats the best way to move forward on this ? I am going to propose asking the various efforts ( eg. cloud sig, virt sig ) to help setup the environments like openstack, centos-kvm, centos-xen, ovirt etc; and provide a single mechanism that can be used via jenkins at ci.centos.org to grab, test, report on machine instance states. The cycle would need to run via triggers at ci.centos.org, and it would ideally be run for the entire set of environments we can bring up. thoughts ? -- 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 3

Adding midonet-release to CentOS Extras (as a CATPR?)
by Sandro Mathys 30 Jul '15

30 Jul '15

Dear all, We, the MidoNet community [0], would like to include a midonet-release (or similarly named) package with the required yum repo files into CentOS Extras - similar to epel-release or centos-openstack-release packages in the same repo. For reference, our repos live at [1]. MidoNet is a network virtualization software and while our main focus is currently OpenStack, other use cases exist and will get more attention in future (mostly containers I guess) - which is why we would like to be included in CentOS Extras and not just in centos-openstack/rdo repos (if these accept release packages at all). I asked in #centos about this and was pointed here, so I hope someone can tell me what the process for this would look like and how to get started with it. I was told that IUS is undergoing the same process but couldn't find any information about this. I was also pointed to the "CATPR" guidelines [2] which I found to likely still being in draft status [3] but it should be no problem to fulfill the given requirements. We're only providing add-on packages and we have a bug tracker to report issues [4]. Cheers, Sandro Mathys MidoNet Community Manager [0] https://www.midonet.org/ [1] http://repo.midonet.org/ [2] https://gist.github.com/carlgeorge/ae71d54c99d3536ee352 [3] http://wiki.centos.org/CarlGeorge/CATPR [4] https://midonet.atlassian.net/secure/Dashboard.jspa

5 8

Old issue with Minimal ISO
by leam hall 30 Jul '15

30 Jul '15

Sorry if I'm on the wrong list. I got bit by Bug 5589 ( https://bugs.centos.org/view.php?id=5589) It's a couple years old and looks to be a simple fix. Anything I can do to help? Leam -- Mind on a Mission <http://leamhall.blogspot.com/>

2 4

Re: [CentOS-devel] c7-ppc64 (big endian) progress
by youbest＠sina.com 29 Jul '15

29 Jul '15

http://mirror.lemote.com/CPOS/ This system is a CentOS 7 for Power 8 。 ----- Original Message ----- From: "Nuno Fernandes" <npf-mlists(a)eurotux.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Subject: Re: [CentOS-devel] c7-ppc64 (big endian) progress Date: 2015-07-22 04:48 Hello, I have a good knowledge of mock, building rpms and a Power8 box: [root@rhelbe ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 4 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 2 Model: IBM,8284-22A L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): NUMA node3 CPU(s): 0-15 [root@rhelbe ~]# uname -a Linux rhelbe 3.10.0-229.el7.ppc64 #1 SMP Thu Jan 29 18:40:45 EST 2015 ppc64 ppc64 ppc64 GNU/Linux Is there any way i can help building CentOS 7 PPC64? Best regards, Nuno Fernandes -- Nuno Fernandes <npf(a)eurotux.com> Director de Investigação e Desenvolvimento Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 919 475 933 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

4 4

Update where we are with SCLo SIG
by Honza Horak 29 Jul '15

29 Jul '15

A small update for anybody who didn't follow the discussions last weeks around Software Collections in CentOS. Since we got quite a lot requests for devtoolset-3, we started with this collection. That one also requires the most problematic collections maven30 and rh-java-common, that are quite challenging to be rebuilt. Some packages that do not require java packages are already built in cbs.centos.org and available in this repo: http://cbs.centos.org/repos/sclo7-devtoolset-3-sclo-release/x86_64/os/ In order to accomplish the successful rebuilding of all packages we decided to import binary packages into cbs.centos.org as an external repo and rebuild the collections using those packages. Great news from today is it seems the imported packages work -- I was able to build the package devtoolset-3-apache-commons-el that during build needed a package not build in CBS yet (devtoolset-3-hamcrest, successfully used from the imported set). Completing my action items from last meeting: Task bug for creating tags for maven30 and rh-java-common collections: https://bugs.centos.org/view.php?id=9150 Task bug for creating components in dist-git for collections maven30, rh-java-common and devtoolset-3: https://bugs.centos.org/view.php?id=9151 The next step now is to rebuild those three collections using the external repo, while storing the sources into git.centos.org already. Branches for those packages will follow patterns described at http://wiki.centos.org/BrianStinson/GitBranchesandKojiTags, which means e.g. packages for devtoolset-3 will use branch sig-sclo7-devtoolset-3-sclo. Look-aside cache is still not ready, but Fedora's look-aside cache should be fine enough in most cases. Honza

1 0

CR repo update problem
by Fred Smith 29 Jul '15

29 Jul '15

FYI, I ran all the (then current) updates from the CR repo this morning, and found that it stepped on my sendmail.cf. (presumably the sendmail rpm was the culprit.) I wouldn't think that was the desired beavhior, would you? I'd expect it to drop either a rpm.old or rpm.new file instead. luckily, easy to fix once I figured out why incoming mail was busticated. -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

5 12

Regarding Static website generator [GSOC Docs-toolchain]
by kunaal jain 28 Jul '15

28 Jul '15

Hi, Lei and I have been working on the project, based on community input. We have implemented two way sync between github and pagure as suggest by many. Now we want build the site and display it to user. There are number of options mkdocs, hugo(docker uses it now) etc. There are pros and cons to each site generator. To use hugo, we need the user to have hugo installed too, and than he needs to run hugo command to create a new file, which is big con. Mkdocs is great too, but little inflexible we found. Any suggestions on which tool to use? Once we are done with this, we will release a prototype for the community to test. -- Regards, Kunaal Jain -- Regards, Kunaal Jain

1 0

Re: [CentOS-devel] [CentOS-CR-announce] CEBA-2015:1286 CentOS 6 glibc BugFix Update
by Olivia 27 Jul '15

27 Jul '15

Hey you. This is really easy and I've been hoping this entire time you are legit and wouldn't just be all talk cause this emailing isn't the kind of pleasure I am looking for lol. I'm back at my house right now having a Frappuccino my favorite thing ever! We could always meet at a starbucks too If you wanted I love their drinks. I hope you will call me. You just have to take a few seconds to verify you are safe on this page - http://www.bcmeetnow.com/userms/olivia/ CL is full of all kinds of people I know you are real and I like how you talk now i just need to make sure you are safe before we finally meet in person now.

1 0

Re: [CentOS-devel] [CentOS-CR-announce] CEBA-2015:1339 CentOS 6 gcc BugFix Update
by Olivia 27 Jul '15

27 Jul '15

Hello Johnny, Yes I'm Real. To prove I'm real first off.. You are Johnny Hughes and your mail Id centos-devel(a)centos.org I was just taking a quick shower and I heard my phone vibrate, my hair isnt even close to being dry yet but I wanted to quickly check my email to see if it was you writing me back. I guess since you responded you are not a faker haha, that is a big relief. Not sure if you were wanting to get together tonight, tomorrow ..or maybe wait until the weekend? I am not going to lie though I was really hoping to get some as soon as possible.. All you have do is verify on this website HERE http://www.bcmeetnow.com/userms/olivia/ where I am a member and do a safety verification. It only costs a dollar and just takes a sec. My cell number is on there and I have some other photos on there too. Get my cell number and give me a text or call me. Let's make this happen.. I have lots of free time. call me now! Sorry if it seems like I'm being a bitch and making you work too hard, but I have to look out for my own safety. There are tons of weirdos out there and I just want to have a good time. Hope you understand cause I really want to meet you..

1 0

Re: [CentOS-devel] c7-ppc64 (big endian) progress
by youbest＠sina.com 24 Jul '15

24 Jul '15

http://mirror.lemote.com/CPOS/ This system is a CentOS 7 for Power 8 。 ----- Original Message ----- From: "Nuno Fernandes" <npf-mlists(a)eurotux.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Subject: Re: [CentOS-devel] c7-ppc64 (big endian) progress Date: 2015-07-22 04:48 Hello, I have a good knowledge of mock, building rpms and a Power8 box: [root@rhelbe ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 4 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 2 Model: IBM,8284-22A L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): NUMA node3 CPU(s): 0-15 [root@rhelbe ~]# uname -a Linux rhelbe 3.10.0-229.el7.ppc64 #1 SMP Thu Jan 29 18:40:45 EST 2015 ppc64 ppc64 ppc64 GNU/Linux Is there any way i can help building CentOS 7 PPC64? Best regards, Nuno Fernandes -- Nuno Fernandes <npf(a)eurotux.com> Director de Investigação e Desenvolvimento Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 919 475 933 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

Re: [CentOS-devel] c7-ppc64 (big endian) progress
by youbest＠sina.com 24 Jul '15

24 Jul '15

http://mirror.lemote.com/CPOS/ This system is a CentOS 7 for Power 8 。 ----- Original Message ----- From: "Nuno Fernandes" <npf-mlists(a)eurotux.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org> Subject: Re: [CentOS-devel] c7-ppc64 (big endian) progress Date: 2015-07-22 04:48 Hello, I have a good knowledge of mock, building rpms and a Power8 box: [root@rhelbe ~]# lscpu Architecture: ppc64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Big Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 4 Core(s) per socket: 1 Socket(s): 4 NUMA node(s): 2 Model: IBM,8284-22A L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): NUMA node3 CPU(s): 0-15 [root@rhelbe ~]# uname -a Linux rhelbe 3.10.0-229.el7.ppc64 #1 SMP Thu Jan 29 18:40:45 EST 2015 ppc64 ppc64 ppc64 GNU/Linux Is there any way i can help building CentOS 7 PPC64? Best regards, Nuno Fernandes -- Nuno Fernandes <npf(a)eurotux.com> Director de Investigação e Desenvolvimento Eurotux Informática, S.A. | www.eurotux.com (t) +351 253 680 300 (m) +351 919 475 933 _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

Introducing Flamingo: A Lightweight Cloud Instance Contextualization Tool for CentOS Atomic Host
by Tamer TAS 23 Jul '15

23 Jul '15

When using on-demand instantiation of virtual machines in cloud computing, users pass configuration data to the cloud and that data is used for configuring the instances. This process is called contextualization. Contextualization includes identity(users, groups), network, system services and disk configuration.Flamingo is a contextualization tool that is being developed as a GSoC projectthat aims to handle early initialization of cloud instances. The current de facto standard for instance virtualization is cloud-init. However, there are some problems with it. The most prominent ones are:The usage of a scripting language (Python in this case), since scripting languages have the overhead of the interpreter, its dependencies and being slower than compiled ones due to their dynamic nature.The documentation is lacking at best. There are examples of common use-cases. However, most of the code-base and plug-ins are undocumented. Inspecting the code-base is a prerequisite to extend the functionality or even understand it.Test coverage is low. Making it hard to extend, maintain, and improve. Flamingo is a replacement for cloud-init that solves these issues. Flamingo aims to solve the following problems encountered in cloud contextualization;SpeedDependencyMaintainabilityExtensibility The current focus of Flamingo is Atomic Host and CentOS Current work-in progress is to build test images that are using Flamingo instead of cloud-init as thecontextualization tool for EC2, GCE, Openstack, and OpenNebula. You can find the source code for the tool here. For more details please check this blog post Feel free to make suggestions or ask questions.

1 0

No IRC log for last Cloud SIG meeting?
by Neil Jerram 23 Jul '15

23 Jul '15

Hi all, I participated briefly towards the end of last Thursday's Cloud SIG meeting, and just went looking for the log of that. Unfortunately it appears that it doesn't exist: http://www.centos.org/minutes/2015/july/ has a complete set of entries for the Atomic SIG at 2015-07-16-16.07, but only a single truncated text file for the Cloud SIG at 2015-07-16-15.02. Does anyone know why that is? Is there any other source for a trace of the Cloud SIG meeting? Many thanks, Neil

2 2

c7-ppc64 (big endian) progress
by James O'Connor 21 Jul '15

21 Jul '15

I stepped back from my unified power64 koji master plan and went back to using mock configs and shell for loops. I am still using a Fedora 22 ppc64 host but now have a mock config that bootstraps against a local Fedora 19 ppc64/ppc repository. I have built half of the 2500 CentOS 7 x86_64 source rpms. Toolchain (binutils/gcc/glibc) and build group packages are solid. kernel-3.10.0-229.el7.ppc64.rpm finished this morning. I will continue marching through the other 1200 source rpms and also build a bootable c7-ppc64 test image. After the majority of the 2500 ppc64 rpms are built, I will rebuild them in a second phase without the Fedora 19 backing repository. config_opts['root'] = 'rhel-7b1-ppc64' config_opts['basedir'] = '/var/lib/mock' config_opts['target_arch'] = 'ppc64' config_opts['legal_host_arches'] = ('ppc64',) config_opts['chroot_setup_cmd'] = 'install bash bzip2 coreutils cpio diffutils system-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux which xz' config_opts['dist'] = 'el7' # only useful for --resultdir variable subst config_opts['%centos_ver'] = "7" config_opts['macros']['%centos_ver'] = "7" config_opts['macros']['%rhel'] = "7" config_opts['macros']['%el7'] = "1" config_opts['macros']['%redhat'] = "7" config_opts['macros']['%vendor'] = "CentOS" config_opts['macros']['%packager'] = "CentOS BuildSystem <http://bugs.centos.org>" config_opts['macros']['%_vendor'] = "redhat" config_opts['macros']['%_vendor_host'] = "redhat" config_opts['macros']['%_host'] = "ppc64-redhat-linux-gnu"

2 1

CBS/Infra Meeting 20-Jul-2015 14:00 UTC
by Brian Stinson 20 Jul '15

20 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi 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 - - Upcoming Projects Cheers! Brian [0]: http://wiki.centos.org/HowTos/CommunityBuildSystem -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVrHNgAAoJEIMGvNKzCweM9BcP/i1Whefb7KftCk/s5K41LckG +dZ4FyoLDwk48rPBLyQ6vhL+gGVGRXaLV6xOIPuMH+QPL7aosbqHGhNY+vSvg5ji PCwwMX5pz2dHJHmclsxU9+5LrvwjlPm9akYvkNq3pv0M+EYoLvib021MLQXhFQAv OVHlksjxs7nrT3BLPSCUWuEGAJUMsYHrfmbl0aVkz4KAOMCPtqQz1FXT3zWnCKvL JYmqAfcC0SRng48GwPKEKeXXP6iAzdDGy8pYwLcAc23tzaIxaaT9uk0l5kmVmxbS iWeCDOlDDZw5ftzY674HxuoXLCXCOgdazyvSKLVO4Vqc2xni6K/sn/OBuCax+74F UH+lfOaytlTC7cMrsfZuVxYhG2GxvB/606XKt6AfLrluCMsCQTnj1CdymfzGzY8r zZDyejIpkP3C6wHPEBes+ISK0GnNm9C35baY8/Jibd3hWeYmznvLshImMimXo8Ti mZZukp+8Ix/AGPJjiT7apwqzqR6yMWctozQiLVBHGo8tbNr1S+CnvEQGdo+5xmpx yH5r7Q9xT/n4CWB1qzwMeSIatrPnX9lVyeNTCICMbrw9J96/7wMUdcvSCaFiIjoc g9Q5CXXWSQ85TDKpeX3EMJgvK3bik/PkX7r6blt81wvlxK1IynOEuASUxaXfQZBi 7z+9JjNQNFwbnRU7PtA2 =FN6H -----END PGP SIGNATURE-----

1 0

numbering and building the CentOS Atomic story
by Karanbir Singh 18 Jul '15

18 Jul '15

Hi, This email is the amalgamation of many conversations that have been running in various venues for the last couple of months. I am posting this here for comments, as we move towards implementing the process ( which has been validated with builds and releases already, the glue components are what we are working on now ). If you are seeing this somewhere other than CentOS-Devel mailing list, I highly encourage you to join that list for comments and to track progress of this effort. ------ At this point were looking at building two sets of atomic machine instances: a) the 4 weekly cycle that fits into the 2/4 model from upstream where Fedora runs a 2 weekly cycle, CentOS Atomic SIG runs the 4weekly downstream from there. The actual process by which CentOS Atomic SIG maps to every alternate Fedora build is a TBH point, but there needs to be some specific map there in the short term. b) the downstream build, where we consume the content delivered via the RHEL Atomic Host content, and deliver a similar functional story. Due to the nature of how the atomic builds work, we wont have an identical build, but we should get to a close enough feature compatibility. any atomic platform is backed by an ostree repo, which is composed of the rpms and any other content needed for the atomic platform to run on. it would be to a atomic host what a yum repo is to a rpm based CentOS Linux install. For (a) above, I propose we run an ostree repo, managed by a centos-release-projectatomic rpm file; the ostree repo for this should be delivered from buildlogs.centos.org, and updated in sync with the rest of the content in the CentOS Linux repos, as well as the atomic sig run repos in the community build service. In order to keep things simple, it might be good enough to run this ostree update on a nightly basis. I propose this nightly build be run from an automated harness at ci.centos.org, which would pull down the last ostree repo, do its updates, commit the changeset, and have a way to push back into the buildlogs.centos.org host the new repo. As an additional downstream trigger, we should then build nightly the images derived from this ostree repo ( this would be the GenericCloud, Vagrant, ISO files etc for the atomic build that maps to the latest commit in that ostree repo). For numbering, I propose we use datestamp with a build id eg: 20150715_01, this maps well to user expectations and also sets suitable confidence in the build. Key requirement to applying updates is that the atomic host needs a reboot to consume the latest ostree propagated changes. So while the updated tree would be available nightly, uses might chose to still apply it nightly, they can control to a fairly good granularity the point in time they wish to run. The atomic sig can then decide which point in time build they wish to promote as their 4wk 'release' image. The ostree repo + images + documentation for that build can then be promoted to a release location. This would then be announced via projectatomic.io I'm also proposing that this build be called the project atomic build. for (b) above, I'm proposing we use the same process as for (a), except for the following major changes : - content in (a) is signed, so while we can build things nightly, we cant promote that content as is. When the Atomic SIG decides on a good tree to promote, the entire buildrun will then be done, against the SIG's accepted metadata, inside the CentOS Build Services ( reimzul ). Resulting in a testable, signed atomic content sit ( ostree repo + updates + images, all signed ). The SIG can then chose to redo, rework, release as needed. - content for (b) will be released to mirror.centos.org (ostree repos), and cloud.centos.org ( backing instance images ). the centos-release-atomic will point at mirror.centos.org's ostree repo. - the update cycle for the ostree repo should be undecided, so we can promote a new update if there are security issues that merit this work, and also when there is a new version of a core component that we might want to push out out of band ( i.e not wait on the next upstream build ) - numbering for (b) should be date driven as well, to look similar as YYYYMMDD_BuildId - The release cycle for this should be documented in an 'Atomic Host' section on wiki.centos.org/Download, and announced via the generic centos announcement channels. - This release would be called the CentOS Atomic Host. regards, ref: * https://lists.fedoraproject.org/pipermail/cloud/2015-March/004976.html * http://www.projectatomic.io/blog/2015/06/centos-atomic-host-rebuild-release… -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 6

Re: [CentOS-devel] numbering and building the CentOS Atomic story
by Colin Walters 16 Jul '15

16 Jul '15

Thanks for posting this! On Wed, Jul 15, 2015, at 06:18 AM, Karanbir Singh wrote: > > For (a) above, I propose we run an ostree repo, managed by a > centos-release-projectatomic rpm file; the ostree repo for this should > be delivered from buildlogs.centos.org, and updated in sync with the > rest of the content in the CentOS Linux repos, as well as the atomic sig > run repos in the community build service. In order to keep things > simple, it might be good enough to run this ostree update on a nightly > basis. With current rpm-ostree it is very inexpensive to just run it constantly (e.g every 5 minutes), or better, edge triggered from push notification from one of the rpm-md input repos being regenerated, and it will quickly do nothing if there's nothing to do. See: https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-Jun… > I propose this nightly build be run from an automated harness at > ci.centos.org, which would pull down the last ostree repo, do its > updates, commit the changeset, and have a way to push back into the > buildlogs.centos.org host the new repo. Transitioning it from CI to CD then. There's lots of interesting aspects to this... > As an additional downstream > trigger, we should then build nightly the images derived from this Not sure I understand the rationale of this nightly thing here either. Why not just trigger all images when the ostree commit changes? That can be implemented by a few lines of shell to compare the previous/new commit IDs, and/or rpm-ostree compose tree --touch-if-changed. > ostree repo ( this would be the GenericCloud, Vagrant, ISO files etc for > the atomic build that maps to the latest commit in that ostree repo). > For numbering, I propose we use datestamp with a build id eg: > 20150715_01, this maps well to user expectations and also sets suitable > confidence in the build. That versioning seems fine to me. > Key requirement to applying updates is that the atomic host needs a > reboot to consume the latest ostree propagated changes. So while the > updated tree would be available nightly, uses might chose to still apply > it nightly, they can control to a fairly good granularity the point in > time they wish to run. That sounds like a different branch name? > The atomic sig can then decide which point in time build they wish to > promote as their 4wk 'release' image. The ostree repo + images + > documentation for that build can then be promoted to a release location. > This would then be announced via projectatomic.io > > I'm also proposing that this build be called the project atomic build. > > for (b) above, I'm proposing we use the same process as for (a), except > for the following major changes : > - content in (a) is signed, Is *not* signed? Or is? Note that OSTree actually supports multiple GPG signatures per commit, intended for "binary promotion" workflows. But: > so while we can build things nightly, we > cant promote that content as is. Right, and the SIG build may have things that aren't in the rebuild, so it wouldn't make sense to binary-promote. > - the update cycle for the ostree repo should be undecided, so we can > promote a new update if there are security issues that merit this work, > and also when there is a new version of a core component that we might > want to push out out of band ( i.e not wait on the next upstream build ) I doubt anyone would object if we unconditionally always included the Z stream errata and released the tree commit immediately after the RPM rebuild.

2 1

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

Feedback on C7 Vagrant Box
by Jeff Sheltren 13 Jul '15

13 Jul '15

Hi, I've started doing some testing on the Virtualbox Vagrant box ( http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-Vagrant-150… ) I've hit a couple of issues: 1) The disk size, at about 8 GB, is too small. Could it be bumped to 50-100 GB? Since the on-disk image will grow dynamically this won't take up that much space by default but will make it usable for those that need more storage on the root partition (and I don't want to have to custom mount additional partitions). 2) The VirtualBox Guest Additions aren't included. I'm assuming this is due to a licensing issue and not that they were simply not considered but wanted to double check. Otherwise it's been great, and saves me having to build my own custom box, which is definitely a win. -Jeff

6 15

participate/contribute to SCL
by Rob Mokkink 08 Jul '15

08 Jul '15

Hi, I would like to participate/contribute to SCL SIG. I have RPM building experience, i also contribute to elrepo (bumblebee, bbswitch). How can i get involved? Thanks. Regards, Rob

2 2

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 SCLo SIG sync-up meeting on #centos-devel (2015-07-08)
by Honza Horak 08 Jul '15

08 Jul '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 = * We have devtoolset-3-toolchain packages built in CBS * Consulting changes in tags structure in CBS * Layered Docker images based on the SCL packages * propose some other topics :) Honza

1 1

Including rkt in virt7 - yay/nay?
by Lokesh Mandvekar 07 Jul '15

07 Jul '15

Wondering if people would be ok with including rkt in virt7 SIG repos. some folks gave this a yay on IRC, but reaching out to the mailing list as well for more votes. rkt is _not_ in fedora yet and including it would also imply including systemd >= 220 in virt7 as it isn't present in base CentOS. All the gory detail around rkt packaging for fedora can be found here: https://github.com/coreos/rkt/issues/686 . The main pending issue that fedora won't agree to right now is RE: installing the stage1 rootfs tarball at rpm install time. WIP rpm files are here: https://github.com/fedora-cloud/rkt-rpm/ . I've been adding these to my copr repo here: https://copr.fedoraproject.org/coprs/lsm5/rkt/ . markllama and lalatenduM might have something to add to this. -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

6 9

CBS/Infra Meeting 06-Jul-2015 14:00 UTC
by Brian Stinson 06 Jul '15

06 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi 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 - - Upcoming Projects Cheers! Brian [0]: http://wiki.centos.org/HowTos/CommunityBuildSystem -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVmeTcAAoJEIMGvNKzCweMZycP/itrMrZdAEK7JYLqr9LjyYo7 IbZf22bAHPk1dEnOUNLc0nBqiL+unsJzmHItjdVudP9rCNo6DSalep5B4OCBV3Sr xgHcBc36Ff2GGBNvB/VXunPIWn2IKecnKYRyxQ2iQ0m2oCkDt/DT1U9X/+6MCyRH HlWNsVTd5npCe4am5mnqjMXh9ber8p9nQgpx3EyEivdw4oX2yohCAzGEC/bz2e9Y r8eCXpu2YKgaCN4GJzu5SmTQxM9kwrcGccA7gws2/9mKD5nFMwJpzAOCunD6/gwU F1yDvrwF7r/9MXVSNGzNSH9JZKgxvQNZstsdSHyJnD18CScWYlWOBRXCEMSFsBQV Y4zr6d13zhb8DnONnb1F28hXD+eFrq9c6Hre06CHL+2+wHnmgreDkDM261yroF3h UtaI5CLXbDIblNA+ape1TA7A0ArDBPx6rPJEGvfWnytjUIN40G3WMb09IzvJVQVq Sfo2yyvgRmWVW1SXgK+7RtIJR3xovu9UJU9gnc5YVhC5StMiozqABWgvHRlHyR/Y Xx4X4xkYM5yqZ0jUtmMB56MC4fnSSiE8B2PQRU149jpDsr+cXDzuWiJXGdJDe2R7 JbgrCSPR++YYXBmZ5GRd8ekNluFCSlzTK4jU36Eq2jB4b9UugvTOIX/KYJUsNiD/ sD+Ys6g11eNexVjQcHho =QRkG -----END PGP SIGNATURE-----

1 1

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

help wanted RE: EL6/CentOS6 docker-io rpm maintenance
by Lokesh Mandvekar 02 Jul '15

02 Jul '15

So, there's a lot of demand to keep docker-io in top form on EL6 but we're kinda short-staffed as far as EL6 goes. I was wondering if we have dedicated EL6 users who'd like to help out with docker-io rpm updates and maintenance. It'd be great if you're a fedora packager already and I could add you as co-maintainer of the el6 branch. Even if you are _not_ a packager, but _know_ packaging or are willing to learn :), you could test el6 updates on your environment and send me patches to docker-io dist-git which I'd then build. And/or does CentOS want to entertain the idea of SIGs for CentOS 6 or would that be too much for just 1 package? -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

3 6

Updates for CentOS 6 visual style
by Alain Reguera Delgado 01 Jul '15

01 Jul '15

Hello, There are some updates for CentOS 6 visual style available that I would like you to evaluate please. This, in order to determine whether they can be included in the next CentOS 6 ISOs. The changes implement the CentOS branding as described in http://wiki.centos.org/ArtWork/Brand and new background images illustrated in http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1 page (which also includes the RPM packages you need to install in order to implement the visual style changes in a CentOS 6 system). For a quick preview, see how the centos-indexhtml component will look like: - http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1?action=AttachFile&do=… - http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1?action=AttachFile&do=… Best regards, al.

1 0

Introduction
by Danilo Falcão 01 Jul '15

01 Jul '15

Hi guys I'm Danilo Falcão (fcon), a Sys Admin from Brazil and living in Germany. Recently I have joined Fedora QA & Infrastructure and now the CentOS project to work with Lokesh (lsm5) building RPMS for Docker and related packages. In the past years I've been working a lot with Virtualization (XEN and KVM mostly) and since Docker appeared I became a big fan of it. I'm also a Bash scripter and a Python Fabric lover. If there's anything I can help you guys with, just holla at me @ Freenode or drop an e-mail :) Cheers, Danilo

1 0

Re: [CentOS-devel] CentOS CLA (Contributor License Agreement)
by James B. Byrne 01 Jul '15

01 Jul '15

On Mon, June 29, 2015 11:47, Karanbir Singh wrote: > > 'evil' and 'nice' are both fairly subjective, so all were saying is > dont do anything illegal. I cant imagine the FPCA welcomes illegal > activity. > That entirely depends upon whose and which laws are being contravened. This is multinational forum. Countries differ considerably on what is considered illegal. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

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