March 2018 - devel - lists.centos.org

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

SRPMS for AltArch (more specifically aarch64 kernel)
by Dominique Martinet 22 Aug '18

22 Aug '18

Hi folks, I've asked on IRC and have been pointed to this list. I can't seem to find this particular source rpm: kernel-aarch64-4.5.0-29.el7.src.rpm which is what is pointed by `rpm -qi kernel` on my system. Are these supposed to be available anywhere? Looking on google I only see one for an older release in someone's centos user/people page, but I can't seem to find these in any repo. The debuginfo are properly here but it's good to have sources as well when messing around with low level stuff :) Cheers and thanks for the hard work, -- Dominique Martinet

3 8

Notes from CERN pre-dojo
by Rich Bowen 23 May '18

23 May '18

The notes from the pre-dojo meeting at CERN, yesterday, may be found in the etherpad at https://public.etherpad-mozilla.org/p/cern-centos-thursday Those involved in the various discussion topics are requested to elaborate, where appropriate. Thanks to everyone who attended this very productive discussion. --Rich -- -- Rich Bowen - rbowen(a)redhat.com @rbowen // @rdocommunity // @CentOSProject 859 351 9166

5 7

URLs in centos-release-<sig> packages: /altarch vs. /centos/
by Brian Stinson 13 May '18

13 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations. tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed: `uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir` Here's the start of a proposal from the SIG perspective ## Requirements: - - The same noarch binary RPM *must* be distributable to the Extras repo for each architecture - - The centos-release-<SIG> packages *must* require centos-release ## New Recommendations for creating a centos-release file: - - A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use 1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example): [centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-que… gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4 ## Discussion I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release. Cheers! - -- Brian Stinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJanjEMAAoJEIMGvNKzCweMR6oQAMbsKqvJcfKW1+5yHsbEV33d QAAMwjEcKfZ+v9ypejErbPPh5RhuNCoRFFHUDAn4hBJNo2zb0YC0vKZJF3RIPIkV 9GAOwnnrWIvFJbeZ7sY4POMa/50IJXC3N8CeiW2XonDtf58rXZPsXM9/9JN9xCv7 X39FAIufCYA7rmedta236NMAutiEolyDFKWWJN6kwDzhm4p7BT9UVSyf7sWCBDzx t+TuCo7LZei4iwQWho1YL/9jbm0YP6EEyL3jJ/YT68cE8q9Mqd8qiE0gEMy0Eoof FuGNOLMrFhsvg3jNQr5DkbToDU+VwO3B+YVR29pTrd0Gf8bodmGTH31eCEljlhjg uPlms2cDvkaXlJmjO6XHM0D2cxmlTzBfVG7YrRwlD40JSk1Z3iyPyLkWJ967oyVM 9mmkhv4spNCX4okQlNI737bULwcxILM6ks3oCdO4i4Yk8BbZp/iwrJ9jcxr7U5YT Cvq2SuV5EbcXlxnhmMd/V6+F/VkgKqi0xrltKURlVUk+JzabHTw5zGwcRjnHxUQR nz2YiQ0mdR/pPuGyXl6xOqXl+M6khPBdCk4FHHdrZYw6aijo8FHzR1DYc63m4ibf Pkad1V9Awetuz0YwewgTp3MviRlklQte8jXMV/1Nh0TTp8xIs5e4ISNBwD3EtINL oqQYqpSGC0jkrwXD5fRG =F1Fp -----END PGP SIGNATURE-----

7 14

[Artwork] Is the Artwork SIG alive?
by Rich Bowen 03 May '18

03 May '18

I've been working through the various SIGs, trying to determine which ones are active. I'm curious about the state of the Artwork SIG. https://wiki.centos.org/SpecialInterestGroup/Artwork Is this still an ongoing effort, or is it "done"? -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

4 3

LinchPin v1.5.1 (update) has been released
by Clint Savage 09 Apr '18

09 Apr '18

We are happy to announce that LinchPin v1.5.1 has been released. This release has the following updates: * The command line shell now enables ansible verbose output (#456) * Made the uHash optional for instances and inventory files (#458) * Adjusted the default location of the RunDB to the workspace (#458) * General cleanup (#461) * Update the README * Remove references to outdated documentation. * Remove unused schemas and documentation. * Fixed documentation example links (#453) * Make generating resources optional (#462) * Additional libvirt updates (#464) * Add detail about libvirt and image copying rights to Provider doc * Libvirt supports 'become' functionality as an unprivileged user * Additional Documentation improvements to Getting Started Guide (#464) * Updated `mkvirtualenv` docs to point out the ``-p`` switch for newer distros with Python 3.x installed * Made aws topology option `keypair` optional (#466) The official release notes are available at https://github.com/CentOS-PaaS-SIG/linchpin/releases/tag/v1.5.1 This update is available via PyPI: https://pypi.python.org/pypi/linchpin If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues) Cheers and enjoy! Clint Savage LinchPin Maintainer Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin

1 1

Disabled weekly scanning in CentOS Container Pipeline for this weekend
by Dharmit Shah 29 Mar '18

29 Mar '18

Hi, We've not been able to push the fixes for weekly scanning process in CentOS Container Pipeline to prod environment. Hence, we've disabled it for this weekend. Apologies for the inconvenience. Regards, Dharmit -- Dharmit Shah Red Hat Developer Tools (https://developers.redhat.com/) irc, mattermost: dharmit

1 0

no mirrorlist in centos-release-scl* on el6
by BC 29 Mar '18

29 Mar '18

centos-release-scl-rh-2-3.el6.centos.noarch and centos-release-scl-7-3.el6.centos.noarch both list only a baseurl, not a mirrorlist even though this appears to be mirrored in several places. Is this an oversight?

2 1

CentOS PaaS SIG meeting (2018-03-28)
by Troy Dawson 28 Mar '18

28 Mar '18

Hello, It's time for our weekly PaaS SIG sync-up meeting This week will be a bit different because we are going to devote alot of the time to training new committee members. Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 28 March 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms - Training for new committee members - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/March/centos-devel.2018-03-21-17.01.log…

1 0

Can we expect the Fix for “OpenSSL error hex string is too long invalid hex key value” in next OpenSSL release.
by Veetil, Vyshnav 28 Mar '18

28 Mar '18

In CentOS7.4 ,we are getting this error “OpenSSL error hex string is too long invalid hex key value” . OpenSSL version we are using is openssl-1.0.2k-8.el7. We have solved this issue by applying a patch in openssl package suggested by openssl community (https://mta.openssl.org/pipermail/openssl-dev/2016-May/007266.html) Can we expect a Fix for this problem in next release of OpenSSL.

3 2

CentOS PaaS SIG meeting (2018-03-21)
by Troy Dawson 28 Mar '18

28 Mar '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 21 March 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Documentation - Upcomming Committee Member Changes - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/March/centos-devel.2018-03-14-17.01.log…

2 3

Re: [CentOS-devel] CentOS PaaS SIG meeting (2018-03-21)
by Brigman, Larry 27 Mar '18

27 Mar '18

Shouldn’t that last tag been an -rc0 instead of v3.9.0? From: users-bounces(a)lists.openshift.redhat.com [mailto:users-bounces@lists.openshift.redhat.com] On Behalf Of Clayton Coleman Sent: Tuesday, March 27, 2018 3:44 PM To: Troy Dawson <tdawson(a)redhat.com> Cc: users <users(a)redhat.com>; The CentOS developers mailing list. <centos-devel(a)centos.org>; dev <dev(a)lists.openshift.redhat.com> Subject: Re: [CentOS-devel] CentOS PaaS SIG meeting (2018-03-21) Still waiting for a last couple of regressions to be fixed. Sorry everyone, I know you're excited about this. On Tue, Mar 27, 2018 at 6:04 PM, Troy Dawson <tdawson(a)redhat.com<mailto:tdawson@redhat.com>> wrote: I didn't see anything saying that 3.9 was released yet. Last I heard they were working on some regressions. If I missed it, can someone point me at it. Maybe I just need a better place to look than the mailling lists. On Thu, Mar 22, 2018 at 11:01 PM, Jeffrey Zhang <zhang.lei.fly(a)gmail.com<mailto:zhang.lei.fly@gmail.com>> wrote: > hi, openshift origin 3.9 is released already, > when centos-release-openshift-origin39 repo will be GA? it is still using > alpha tag now. > > https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin39/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildlogs.…> > _______________________________________________ users mailing list users(a)lists.openshift.redhat.com<mailto:users@lists.openshift.redhat.com> http://lists.openshift.redhat.com/openshiftmm/listinfo/users<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.opens…>

1 0

Origin package with wrong binaries
by Brigman, Larry 21 Mar '18

21 Mar '18

I had an Engineer attempt to install OpenShift via Ansible playbooks. The package that showed up as available was 3.7.1. The playbook installation failed with an error Error was a <class 'ansible.errors.AnsibleError'>, original message: Unknown short_version 3.10" The following investigation showed this: oc version oc v3.10.0-alpha.0+0a2d6a1-65 kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO The oc binary shows it belongs to the 3.7.1 origin-clients package and the package verifies.

2 1

[Cloud SIG] Updates from Cloudstack
by Rohit Yadav 21 Mar '18

21 Mar '18

All, I may not be able to contribute and join weekly meetings before 12th April due to current/upcoming holidays. I'll share updates here: - CloudStack completed 5yrs with the ASF - I've proposed getting CloudStack bug reporting to move to Github issues, making it easier for developer+users communities to use a single portal. It would be interesting to know how other communities handle bug reporting and PR/code reviews. - We are yet to finish work on our packaging scripts to build redistributable rpms that can go through CentOS bugs/CI as next steps. - We're gathering information on getting CloudStack packages in Debian via their mentors programme. - I'm hoping to resume work after mid April on with CentOS SIG and Debian mentors to get CloudStack packages published via distro repos, targetting 4.11.1.0 (the next LTS version/release). Regards, Rohit Yadav PMC/Committer Apache CloudStack

1 0

debuginfo.centos.org status
by Thomas Oulevey 20 Mar '18

20 Mar '18

Hello folks, I have few remarks about http://debuginfo.centos.org as an user. Lately our debug tools are depending on few debuginfo packages so we depend on them in our production environment. The debuginfo server is structured as following : . ├── 7 │ ├── i386 │ │ └── repodata │ └── x86_64 │ └── repodata └── centos ├── 6 │ └── sclo └── 7 ├── cloud ├── sclo ├── storage └── virt 1/ It seems that the experimental kernel debuginfo are copied in the same directory as the os/updates/extras which confuse a bit users (/7/x86_64/) e.g : http://debuginfo.centos.org/7/x86_64/kernel-debuginfo-4.9.75-204.el7.centos… Is there an official way to enable a repo to use these experimental kernel (http://mirror.centos.org/altarch/7/experimental/x86_64/Packages/) ? In my opinion the debuginfo packages should be in a separate repo too. Could we move them to a better place ? under /altarch as the main packages on mirror ? 2/ Do we want to reorganize the debuginfo server ? I would favor a tree where we can have debuginfo separated per repos as we do for sigs : . ├── 7 │ ├── i386 │ │ └── os │ │ └── updates │ │ └── extras │ │ └── etc... │ └── x86_64 │ │ └── os │ │ └── updates │ │ └── extras │ │ └── etc... What do you think ? -- Thomas Oulevey

2 1

CentOS PaaS SIG meeting (2018-03-14) [DST Time reminder]
by Troy Dawson 14 Mar '18

14 Mar '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 14 March 2018 Where: IRC- Freenode - #centos-devel For those in the United States, remember that we are using UTC time, and so the time is an hour later than it was last week. Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation - Upcomming Committee Member Changes - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/March/centos-devel.2018-03-07-17.02.log…

1 0

Status update: CentOS Community Container Pipeline Service 14-Mar-2018
by Bamacharan Kundu 14 Mar '18

14 Mar '18

Hi, Here is an update on the recent works done in Centos Community Container Pipeline Service * Fixing beanstalk connection initialization method * Gates pep8 on service code before running actual tests * Cleans the log file with redundant queue operational messages * Prevents logging unnecessary recurring queue operational messages Our current focus is: * Fix docker run command for INSTALL labels of scanners * Fix weekly scan to read through all yaml and yml container-index entries * Fix pre-build job entries CI to not check for target file * Enabling automatic garbage collector runs in cron * Fix pipeline scanner image rootfs unmounting Regards Bamacharan Kundu

1 0

[Cloud SIG] meeting reboot
by Rich Bowen 13 Mar '18

13 Mar '18

A reminder to all, that we are trying to reboot the Cloud SIG meetings, now that we have representatives from Cloudstack on board. These meetings are scheduled for Thursdays at 15:00 UTC, on #centos-devel The agenda for the meeting is here: https://etherpad.openstack.org/p/centos-cloud-sig - although there's nothing on it for this week, as we've been out of practice for a long time. --Rich -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

2 1

Re: [CentOS-devel] Two New Committee Members Needed for CentOS PAAS SIG
by Troy Dawson 09 Mar '18

09 Mar '18

Hi Ricardo, I'm so sorry in the delay of replying. I do appreciate the offer to be on the committee. What position(s) were you thinking of filling? Troy On Tue, Feb 27, 2018 at 8:05 AM, Ricardo Martinelli de Oliveira < rmartine(a)redhat.com> wrote: > Awesome! Thanks for the clarification! > > I'm interested in being part of the committee. > > On Tue, Feb 27, 2018 at 12:09 PM, Troy Dawson <tdawson(a)redhat.com> wrote: > >> A few good questions have come up. >> What are the responsibilities I would take on if I joined the committee? >> Can I work on a sub-set of those responsibilities? >> >> Ari was in charge of keeping the jenkins cli working for our Paas. >> He made sure the automatic builds continued building on their appointed >> time. >> He made sure that it was easy to do manual builds. >> When OpenShift Origin code changed and broke the automation he would >> jump in to fix the automation. >> When OpenShift Origin code changed and broke the builds he would jump >> in to fix the automation. >> >> Troy was in charge of orchestrating everything and making sure things >> happened. >> He held the weekly Paas Sig meeting. >> He did the documentation. >> He maintained the package repo's, and koji build targets. >> He was the automation backup, so he helped Ari figure out the broken bits. >> He was the central source of information. So if people had questions, >> or wanted to pass information on, it tended to go through him. This >> could certainly change. >> He was the backup for pretty much everyone. So as people came and >> went from the Paas Sig, he would drop and/or gain new roles. >> >> These roles could certainly be broken up, so that others could take >> certain parts. We could certainly have more than two people take over >> these roles. >> >> >> On Mon, Feb 26, 2018 at 6:52 AM, Troy Dawson <tdawson(a)redhat.com> wrote: >> > Hello, >> > Due to "Real Life" the following CentOS PAAS Sig committee members >> > will be leaving the committee, on the following dates. We will need >> > to get replacements for them by those dates. >> > >> > Ari LiVigni - March 14th >> > Troy Dawson - May 15th >> > >> > Ari is in charge of Automation. >> > Troy is the committee chairman. >> > >> > The CentOS PAAS Sig has been very successful in bringing a free >> > version of OpenShift to everyone. These two people have been a very >> > large part of that. They will be missed. >> > >> > But it's time to look to the future. We need people to step up and >> > not only fill their shoes, but continue to move forward. >> > >> > Take a minute and see if this is something that you would want to do. >> > If it is, please let us know. >> >> _______________________________________________ >> users mailing list >> users(a)lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > > > -- > Ricardo Martinelli de Oliveira > Senior Software Engineer > T: +55 11 3524-6125 <+55%2011%203524-6126> | M: +55 11 9 7069-6531 > Av. Brigadeiro Faria Lima 3900, 8° Andar. São Paulo, Brasil > <https://maps.google.com/?q=Av.+Brigadeiro+Faria+Lima+3900,+8%C2%B0+Andar.+S…> > . > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > Red Hat é reconhecida entre as melhores empresas para trabalhar no Brasil > pelo *Great Place to Work*. >

1 0

Re: [CentOS-devel] Regarding "Two New Committee Members Needed for CentOS PAAS SIG"
by Troy Dawson 09 Mar '18

09 Mar '18

Hi Ogun, Sorry for the delay, I've been crazy busy lately, one of the reasons I need to step down. Thank you very much for offering to support, and especially for talking to your employer about doing so. What role(s) were you thinking of taking on? I do want to point out that Ari has gotten the automation working pretty good. And that while we do need a replacement for him, things aren't going to break the day he leaves. (Hopefully) Troy On Thu, Mar 8, 2018 at 2:50 AM, Ogun HEPER (Dogus Teknoloji) < Ogun.Heper(a)d-teknoloji.com.tr> wrote: > Hello, > > > > Regarding the thread Two New Committee Members Needed for CentOS PAAS SIG > <https://lists.openshift.redhat.com/openshift-archives/dev/2018-February/msg…>, > I’ll be more than happy to be a part of the community. > > > > I’m currently working as a sofware development manager with an experience > over fifteen years in software development. > > > > I have nearly two years of experience in installing/administering > OpenShift clusters on CentOS. > > > > I want to support the community as much as I can. > > > > Best regards, > > Ogün > > > Ogun HEPER > DIJITAL COZUMLER VE TURIZM ‑ YAZILIM GELISTIRME > MUDUR > <http://www.d-teknoloji.com.tr/> > <http://www.dogusgrubu.com.tr/> > Huzur Mah. Maslak‑Ayazağa Cad. Uniq İstanbul Plaza No:4 Kat:3 > <https://maps.google.com/?q=3+B2+Blok&entry=gmail&source=g> > B2 <https://maps.google.com/?q=3+B2+Blok&entry=gmail&source=g> Blok > <https://maps.google.com/?q=3+B2+Blok&entry=gmail&source=g> > Sarıyer / İSTANBUL > T: *+90 533 736 9994* <+90%20533%20736%209994> / Mersis No: 0‑3090‑3430‑ > 1800012 > *Ogun.Heper(a)d-teknoloji.com.tr* <Ogun.Heper(a)d-teknoloji.com.tr> > *www.d-teknoloji.com.tr* <http://www.d-teknoloji.com.tr/> > >

1 0

ETA when PaaS SIG 3.9 will fix the "SerialFileGenerator starts at 2" issue?
by Rich Megginson 08 Mar '18

08 Mar '18

The current 3.9 centos paas repos are at v3.9.0-alpha.4. However, I cannot deploy origin 3.9.0-alpha.4 using ansible (openshift-ansible latest release-3.9 branch) because I run into this issue: TASK [openshift_master : Wait for API to become available] ********************* "* NSS error -8054 (SEC_ERROR_REUSED_ISSUER_AND_SERIAL)", "* You are attempting to import a cert with the same issuer/serial as an existing cert, but that is not the same cert.", This was fixed by 95e262011438642410959914c3db9868c57739ff But that's at commit v3.9.0-alpha.4-426-g95e2620114 I realize the PaaS SIG is trying to stay in sync with official origin tags/releases, but I think that origin 3.9.0-alpha.4 simply isn't deployable using ansible. Alternately, is there a workaround?

2 1

CentOS PaaS SIG meeting (2018-03-07)
by Troy Dawson 07 Mar '18

07 Mar '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 07 March 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building - Upcoming Committee Member Changes - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-28-17.01.…

1 0

Status Update: CentOS Community Container Pipeline Service 07-Mar-2018
by Bamacharan Kundu 07 Mar '18

07 Mar '18

Hi, Here is an update on the recent works done in Centos Community Container Pipeline Service * Fixed bugs in dangling volume cleanup post scan * Update ansible script to install latest docker on all the nodes. * Enable support for yaml in container-index * Make sure jenkins jobs are stopped properly before starting deployment Our current focus is: * Update API with filtering with primary key and names * Fixing container pipeline service API’s for displaying more details on UI. * Fixing beanstalk connection initialization method * Fix pipeline scanner image rootfs unmounting * Prevents logging unnecessary recurring queue operational messages Regards Bamacharan Kundu

1 0

Origin 3.7.1 in testing, please test.
by Troy Dawson 06 Mar '18

06 Mar '18

origin 3.7.1, and openshift ansible 3.7.35 are both available in the testing repository at https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin37/ We need some people to test these and make sure everything is ok. Once they have been tested, we will get them signed and in the released repositories. If you test them, please get back to us so we can release them. Thanks The CentOS Paas SIG

1 0

CentOS Atomic Host 7.1802 Available for Download
by Jason Brooks 06 Mar '18

06 Mar '18

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1802), a lean operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. This release rolls up all package minor updates that shipped through the month of February, including, most significantly, a newer version of rpm-ostree with support for overriding base packages during package layering operations. (see below for more details) CentOS Atomic Host includes these core component versions: * atomic-1.20.1-9.git436cf5d.el7.centos.x86_64 * cloud-init-0.7.9-9.el7.centos.2.x86_64 * docker-1.12.6-71.git3e8e77d.el7.centos.1.x86_64 * etcd-3.2.11-1.el7.x86_64 * flannel-0.7.1-2.el7.x86_64 * kernel-3.10.0-693.17.1.el7.x86_64 * kubernetes-node-1.5.2-0.7.git269f928.el7.x86_64 * ostree-2017.14-2.el7.x86_64 * rpm-ostree-client-2017.11-1.atomic.el7.x86_64 rpm-ostree override While it's been possible to layer new packages onto the base CentOS Atomic tree for some time now, overriding existing base packages with layered alternatives either wasn't possible or was considered experimental. Version 7.1802 now allows for overriding base packages. For example, the origin-clients package that includes OpenShift Origin's "oc" tool conflicts with the kubernetes-client package included in the base tree. You can use package layering and overrides to install the openshift-release rpm, remove the conflicting rpms, and install the origin-clients rpm: # rpm-ostree install centos-release-openshift-origin # rpm-ostree override remove kubernetes-client kubernetes-node -r # rpm-ostree install origin-clients -r # oc cluster up Starting OpenShift using openshift/origin:v3.7.0 ... Pulling image openshift/origin:v3.7.0 ... Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the [CentOS wiki](https://wiki.centos.org/SpecialInterestGroup/Atomic/Download). Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream work from Project Atomic (http://www.projectatomic.io/) If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets every two weeks as part of the Project Atomic community meeting at 16:00 UTC on Monday in the #atomic channel. You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

SIG Chairs: Please file requests for syncing altarch content to mirror.c.o
by Brian Stinson 06 Mar '18

06 Mar '18

Hi Folks, Now that we're syncing content to mirror.centos.org/altarch (thanks KB!) we need to be sure we have all the content you expect there. If you have altarch-enabled koji tags and would like your content signed and pushed to the /altarch location, please file a bug in the normal fashion[0]. FYI: We are reviewing/grooming these bugs at the CBS meetings on Monday at 14h00 UTC in #centos-devel on freenode (though we try to take care of requests as they come in), feel free to stop by and participate in that discussion. [0]: https://wiki.centos.org/SIGGuide/Content/Mirror Cheers! --Brian

1 0

Building a package for RedHat
by dacav 06 Mar '18

06 Mar '18

Hello Centos developers, My company would like to use Red-Hat/Centos as a target system for releasing (proprietary) software. In order to do this properly, I've constructed an infrastructure which allows to build those packages, wrapping mock and other tools. Such infrastructure uses a pool of Centos virtual machines for the building phase. A question that keeps popping in my mailbox is how to build those packages without the 'centos' suffix, as in: %{name}-%{version}.el7.centos.x86_64.rpm Some developers here find that `.centos` tag quite disturbing as we are supposed to release for Red Hat. I think the right thing to do here would be getting a (physical, licensed) Red Hat builder to do the job. But I'm not sure of what this would entail. For instance, is there a mock configuration to use for that? Would that be included in a Red Hat machine?

5 7

A tips page for capturing kernel messages.
by Tetsuo Handa 05 Mar '18

05 Mar '18

Hello. Since I have been encountering kernel problem reports (oops/hangup/slowdown) with incomplete kernel messages, I wrote a page which explains hints for capturing kernel messages for troubleshooting (mainly hangup/slowdown problem) http://akari.osdn.jp/capturing-kernel-messages.html with a utility program named "udplogger". I appreciate if someone can become a maintainer of RPM package for "udplogger". Feedbacks are welcome. Thanks.

1 0

CentOS Storage SIG contribution.
by Javier Romero 02 Mar '18

02 Mar '18

Hi, My name is Javier, live in Buenos Aires, Argentina, and work in the Network Operations Center of an Internet Service Provider as a Linux Sysadmin. I've been working with Linux CentOS Servers for the last 10 years and would like to contribute on the CentOS Storage SIG if there is something where I can be useful. Thanks for your kind attention. Best Regards, *Javier Romero* *E-mail: xavinux(a)gmail.com <xavinux(a)gmail.com>* *Skype: xavinux*

2 13

Bot account for opstools-sig
by Matthias Runge 02 Mar '18

02 Mar '18

Hello, as follow-up on the CentOS dojo in Geneva, I'm hereby requesting a bot account for the Opstools SIG. There are listed two requirements[1]: - the account name is the shortname for the SIG: I'm proposing opstools - The email on the account must be deliverable to someone who can change the certificate on the production environment. The opstools SIG uses RDO gerrit for kicking off builds. So, either we'd need here the email address of someone with such access to RDO gerrit. I currently have no such login. Whatever works here, I'd be fine with it. I did not create an account in ACO yet, since the email question is currently undecided. [1] https://wiki.centos.org/SIGGuide#head-c256691b201cc88e4ffa53f3dee8c78b8cdca… -- Matthias Runge <mrunge(a)matthias-runge.de>

2 2

[Cloud SIG] RDO OpenStack Queens packages available
by Rich Bowen 01 Mar '18

01 Mar '18

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Queens for RPM-based distributions, CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Queens is the 17th release from the OpenStack project, which is the work of more than 1600 contributors from around the world (source - http://stackalytics.com/ ). The release is making its way out to the CentOS mirror network, and should be on your favorite mirror site momentarily. The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Linux and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS Linux users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO, and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. New and Improved Interesting things in the Queens release include: * Ironic now supports Neutron routed networks with flat networking and introduces support for Nova traits when scheduling * RDO now includes rsdclient, an OpenStack client plugin for Rack Scale Design architecture * Support for octaviaclient and Octavia Horizon plugin has been added to improve Octavia service deployments. * Tap-as-a-Service (TaaS) network extension to the OpenStack network service (Neutron) has been included. * Multi-vendor Modular Layer 2 (ML2) driver networking-generic-switch si now available of operators deploying RDO Queens. Other improvements include: * Most of the bundled intree tempest plugins have been moved to their own repository during Queens cycle. RDO has adapted plugin packages for these new model. * In an effort to improve the quality and reduce the delivery time for our users, RDO keeps refining and automating all required processes needed to build, test and publish the packages included in RDO distribution. Note that packages for OpenStack projects with cycle-trailing release models[*] will be created after a release is delivered according to the OpenStack Queens schedule. [*] https://releases.openstack.org/reference/release_models.html#cycle-trailing Contributors During the Queens cycle, we saw the following new contributors: Aditya Ramteke Jatan Malde Ade Lee James Slagle Alex Schultz Artom Lifshitz Mathieu Bultel Petr Viktorin Radomir Dopieralski Mark Hamzy Sagar Ippalpalli Martin Kopec Victoria Martinez de la Cruz Harald Jensas Kashyap Chamarthy dparalen Thiago da Silva chenxing Johan Guldmyr David J Peacock Sagi Shnaidman Jose Luis Franco Arza Welcome to all of you, and thank you so much for participating! But, we wouldn’t want to overlook anyone. Thank you to all 76 contributors who participated in producing this release. This list includes commits to rdo-packages and rdo-infra repositories, and is provided in no particular order: Yatin Karel Aditya Ramteke Javier Pena Alfredo Moralejo Christopher Brown Jon Schlueter Chandan Kumar Haikel Guemar Emilien Macchi Jatan Malde Pradeep Kilambi Luigi Toscano Alan Pevec Eric Harney Ben Nemec Matthias Runge Ade Lee Jakub Libosvar Thierry Vignaud Alex Schultz Juan Antonio Osorio Robles Mohammed Naser James Slagle Jason Joyce Artom Lifshitz Lon Hohberger rabi Dmitry Tantsur Oliver Walsh Mathieu Bultel Steve Baker Daniel Mellado Terry Wilson Tom Barron Jiri Stransky Ricardo Noriega Petr Viktorin Juan Antonio Osorio Robles Eduardo Gonzalez Radomir Dopieralski Mark Hamzy Sagar Ippalpalli Martin Kopec Ihar Hrachyshka Tristan Cacqueray Victoria Martinez de la Cruz Bernard Cafarelli Harald Jensas Assaf Muller Kashyap Chamarthy Jeremy Liu Daniel Alvarez Mehdi Abaakouk dparalen Thiago da Silva Brad P. Crochet chenxing Johan Guldmyr Antoni Segura Puimedon David J Peacock Sagi Shnaidman Jose Luis Franco Arza Julie Pichon David Moreau-Simard Wes Hayutin Attila Darazs Gabriele Cerami John Trowbridge Gonéri Le Bouder Ronelle Landy Matt Young Arx Cruz Joe H. Rahme marios Sofer Athlan-Guyot Paul Belanger Getting Started There are three ways to get started with RDO. To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For a production deployment of RDO, use the TripleO Quickstart and you’ll be running a production cloud in short order. Finally, if you want to try out OpenStack, but don’t have the time or hardware to run it yourself, visit TryStack, where you can use a free public OpenStack instance, running RDO packages, to experiment with the OpenStack management interface and API, launch instances, configure networks, and generally familiarize yourself with OpenStack. (TryStack is not, at this time, running Queens, although it is running RDO.) Getting Help The RDO Project participates in a Q&A service at ask.openstack.org. We also have our users(a)lists.rdoproject.org for RDO-specific users and operrators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailng lists archives are all available at https://mail.rdoproject.org You can also find extensive documentation on the RDO docs site. The #rdo channel on Freenode IRC is also an excellent place to find help and give help. We also welcome comments and requests on the CentOS mailing lists and the CentOS and TripleO IRC channels (#centos, #centos-devel, and #tripleo on irc.freenode.net) however we have a more focused audience in the RDO venues. Getting Involved To get involved in the OpenStack RPM packaging effort, see the RDO community pages and the CentOS Cloud SIG page. See also the RDO packaging documentation. Join us in #rdo on the Freenode IRC network, and follow us at @RDOCommunity on Twitter. If you prefer Facebook, we’re there too, and also Google+. -- Rich Bowen: Community Architect rbowen(a)redhat.com @rbowen // @RDOCommunity // @CentOSProject 1 859 351 9166

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2018