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

Request for feedback: CentOS-Atomic container
by Karanbir Singh 25 Sep '17

25 Sep '17

hi Alpha2: registry.centos.org/kbsingh/centos-atomic:7-alpha2 The CentOS Atomic Container is a minimal ( 30MB on disk ) image that can be used to host static content, and small footprint content that does not need the entire CentOS Linux Base image. This is also not meant to replace CentOS Linux Base image as the default, we want to make it available as an additional container base for apps that find it useful. The main highlight is that it does not contain yum, but has microdnf. I am looking for feedback, and some wider testing as well as recommendations on howto further reduce size, before we move to release. You can consume this as : docker run -t -i \ registry.centos.org/kbsingh/centos-atomic:7-alpha2 \ /bin/bash regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

Release notes of centos genericcloud image?
by 杨成伟 05 Aug '17

05 Aug '17

Hi list, I found centos genericcloud image for openstack at https://docs.openstack.org/image-guide/obtain-images.html#centos but I didn't found any release note for these images, so I didn't known what's difference between genericcloud image and the official centos release, e.g. centos 6.8, 7.2 release and etc. Is there any wiki/doc/releasenote? -- Thanks, Chengwei

7 9

LinchPin on opensource.com
by Clint Savage 04 Jul '17

04 Jul '17

An article I wrote on LinchPin project has been posted on opensource.com. https://opensource.com/article/17/6/linchpin It covers many of the new features and improvements over the past 10 months. Cheers, herlo

2 1

Broken hyperthreading on Intel Skylake and Kaby Lake processors
by Laurentiu Pancescu 30 Jun '17

30 Jun '17

Hi there, I stumbled upon a thread on debian-devel, regarding hyperthreading problems on Intel Skylake and Kaby Lake processors (discovered in Q2 2016 by the OCaml developers, fixed by Intel in microcode updates in May 2017 - for some, but not all processors [1]). The "safe" solution is to disable hyperthreading in the BIOS, but there's a Perl script telling you if you CPU is affected, or affected and patched in microcode. [2] Considering that (probably) not all processors are fixed, would this warrant notifying our users via the centos-announce mailing list? Best regards, Laurențiu [1] https://lists.debian.org/debian-devel/2017/06/msg00308.html [2] https://lists.debian.org/debian-user/2017/06/msg01011.html

4 5

[Minutes] RDO meeting (2017-06-28)
by Chandan kumar 28 Jun '17

28 Jun '17

============================== #rdo: RDO meeting - 2017-06-28 ============================== Meeting started by chandankumar at 15:03:04 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_06_28/2017/rdo_m… . Meeting summary --------------- * LINK: https://etherpad.openstack.org/p/RDO-Meeting (chandankumar, 15:04:18) * Enabling DLRN API on public instance (chandankumar, 15:07:38) * ACTION: jpena to communicate planned downtime for DLRN public instance on Jun 29 morning (jpena, 15:12:39) * Enabling RDO contribution through low hanging fruits (chandankumar, 15:16:59) * LINK: https://review.rdoproject.org/etherpad/p/rdo_low_hanging_fruits (chandankumar, 15:18:14) * ACTION: jruzicka to label low hanging rdopkg issues/RFEs (jruzicka, 15:32:19) * ACTION: chandankumar to add README for redhat-openstack/easyfix (chandankumar, 15:43:33) * Upcoming Events (chandankumar, 15:51:39) * chair for next meeting (chandankumar, 15:53:15) * ACTION: jpena to chair for next week (chandankumar, 15:57:27) * open floor (chandankumar, 15:57:47) * LINK: http://rdoproject.org/stats (rbowen, 15:59:46) * LINK: https://rdo.biterg.io/app/kibana#/dashboard/Git (rbowen, 16:00:20) Meeting ended at 16:01:14 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to add README for redhat-openstack/easyfix * jpena * jpena to communicate planned downtime for DLRN public instance on Jun 29 morning * jpena to chair for next week * jruzicka * jruzicka to label low hanging rdopkg issues/RFEs * openstack * chandankumar to add README for redhat-openstack/easyfix People present (lines said) --------------------------- * chandankumar (83) * rbowen (44) * apevec (42) * jpena (21) * openstack (11) * jruzicka (7) * Duck (7) * dmsimard (4) * coolsvap (2) * rdogerrit (2) * tosky (1) * EmilienM (1) Generated by `MeetBot`_ 0.1.4

1 0

CentOS PaaS SIG meeting (2017-06-28)
by Troy Dawson 28 Jun '17

28 Jun '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 28 June 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch --- Should we do aarch64 on general builds -- minishift (marcindulak and lalatenduM) - Open Floor

1 0

CentOS/AArch64 image for Docker needs update
by Marcin Juszkiewicz 27 Jun '17

27 Jun '17

Hi There is 'centos/aarch64' image in hub.docker.com repository. The problem with it is that there is only "latest" tag while one for x86-64 has both "7" and "latest" tags (and several other which I can ignore). Someone say "so use centos/aarch64:latest instead". But this is not a solution. There are moments when you have to convince some upstream developer that patch like "tag=7;if arch == aarch64 then tag=latest" is crucial for your work. I do not remember who created previous image (Jim may know) but it would be nice to get them recreated with proper tags. Some kind of updates would be extras ;D

2 1

Re: [CentOS-devel] Using atomic-openshift-installer to upgrade from origin 1.4 to 1.5
by Troy Dawson 27 Jun '17

27 Jun '17

I have built one of the later 3.5 openshift-ansibles, and applied this patch to it. openshift-ansible-3.5.82-1.git.1.f658b01.el7 I've tagged it into testing, that might take up to 2 hours to get there. But when it does, you should be able to do yum --enablerepo=centos-openshift-origin15-testing clean all yum --enablerepo=centos-openshift-origin15-testing update atomic-openshift-utils openshift-ansible\* After that, give it a try and let us know if allowed you to update. Troy On Tue, Jun 20, 2017 at 8:01 AM, Scott Dodson <sdodson(a)redhat.com> wrote: > Can you try this? > > https://github.com/openshift/openshift-ansible/pull/4508 > > On Tue, Jun 20, 2017 at 10:01 AM, Troy Dawson <tdawson(a)redhat.com> wrote: >> >> On Tue, Jun 20, 2017 at 6:53 AM, Jean-Francois Chevrette >> <jchevret(a)redhat.com> wrote: >> > Hi, >> > >> > 3 months ago I have used atomic-openshift-utils/installer to setup two >> > OpenShift origin 1.4 clusters. Today I discovered that I am unable to >> > upgrade from 1.4 to 1.5 because atomic-openshift-installer states that >> > "No >> > upgrades available for origin 1.4" >> > >> > atomic-openshift-utils-3.5.71-1.git.1.640cb7d.el7.noarch >> > centos-release-openshift-origin15-1-1.el7.centos.noarch >> > openshift-ansible-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-callback-plugins-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-docs-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-filter-plugins-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-lookup-plugins-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-playbooks-3.5.71-1.git.1.640cb7d.el7.noarch >> > openshift-ansible-roles-3.5.71-1.git.1.640cb7d.el7.noarch >> > >> > 1.5 is in the list of supported install variants here: >> > /usr/lib/python2.7/site-packages/ooinstall/variants.py >> > >> > However the UPGRADE_MAPPINGS list in >> > /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py only has >> > upgrade >> > paths for 3.4 and 3.5 >> > >> > Is upgrading between origin releases simply not supported/possible? >> > >> > >> > Thanks, >> > Jean-Francois C. >> > >> >> Sounds like a bug to me. >> Maybe we need to do a few more tweeks to atomic-openshift than I thought. >> I'm cc'ing Scott Dodson on this to see what the official stance is on >> this. >> >> Troy > >

2 2

atomic7-testing repo content vanished?
by Colin Walters 27 Jun '17

27 Jun '17

https://cbs.centos.org/repos/atomic7-testing/ used to have content, but no longer does. I tried doing a new build: https://cbs.centos.org/koji/taskinfo?taskID=187981 But it hasn't shown up there.

2 1

[PATCH] Update API path in centos.git.repolist.py
by Pat Riehecky 26 Jun '17

26 Jun '17

--- centos.git.repolist.py | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/centos.git.repolist.py b/centos.git.repolist.py index 75122ae..e135ca7 100755 --- a/centos.git.repolist.py +++ b/centos.git.repolist.py @@ -13,7 +13,7 @@ import requests import simplejson as json import sys -RPCURL = "https://git.centos.org/rpc?req=LIST_REPOSITORIES" +RPCURL = "https://git.centos.org/rpc/?req=LIST_REPOSITORIES" def read_args(): ''' @@ -48,6 +48,11 @@ def get_repo_list(url, branch, projectpath): print err_msg sys.exit(1) + if req.status_code != 200: + print "Unable to access gitblit api at " + url + sys.exit(1) + + payload = req.text repos = json.loads(payload) branchname = 'refs/heads/' + branch @@ -68,6 +73,6 @@ def main(): repos = get_repo_list(url=options.url, branch=options.branch, projectpath=options.project) if repos: print '\n'.join(repos) - + if __name__ == "__main__": main() -- 1.8.3.1

4 5

git.centos.org maint 19th June 15:00 UTC
by Karanbir Singh 23 Jun '17

23 Jun '17

hi going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today. 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

5 11

Stack Clash kernel source patches for CentOS 5
by Simon Matter 23 Jun '17

23 Jun '17

Hi, I'm looking for the "Stack Clash" patches which have been included in the kernel-2.6.18-420.el5.src.rpm package. Would be nice if someone could make them available, thanks! Regards, Simon

3 5

wrong symbol for strings(") in vagrant box description
by Rafal Skolasinski 22 Jun '17

22 Jun '17

Hi, I just noticed that in https://seven.centos.org/2017/06/updated-centos-vagrant-images-available-v1… line that reads about sync folders config.vm.synced_folder “.”, “/vagrant”, type: “virtualbox” uses the wrong symbol for strings (") and after copying into Vagrantfile causes a cryptic error message. Cheers, Rafal

3 6

[Meeting] RDO meeting - 2017-06-21
by Chandan kumar 21 Jun '17

21 Jun '17

============================== #rdo: RDO meeting - 2017-06-21 ============================== Meeting started by chandankumar at 15:01:03 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_06_21/2017/rdo_m… . Meeting summary --------------- * tripleo-common adding a dependency from a package in the Ceph SIG repo (chandankumar, 15:05:06) * LINK: https://review.openstack.org/#/c/469644/14//COMMIT_MSG@16 (fultonj, 15:10:39) * LINK: https://cbs.centos.org/repos/storage7-ceph-jewel-candidate/ (fultonj, 15:16:00) * LINK: https://cbs.centos.org/repos/storage7-ceph-common-candidate/ (fultonj, 15:16:05) * LINK: http://paste.openstack.org/show/613306/ (amoralej, 15:18:23) * LINK: https://review.rdoproject.org/r/#/c/6809 (fultonj, 15:19:44) * LINK: https://review.openstack.org/#/c/469644/14//COMMIT_MSG@16 (fultonj, 15:21:26) * Package naming convention for RDO packages (chandankumar, 15:36:42) * LINK: https://review.rdoproject.org/etherpad/p/rdo_packages_naming (chandankumar, 15:38:12) * ACTION: chandankumar to drop an email for inputs on RDO packages naming conventions (chandankumar, 15:47:14) * RDO Cloud scheduled maintenance on June 22, 1:00 UTC (1 hour) (chandankumar, 15:50:27) * ACTION: jpena to send outage mail to rdo list (chandankumar, 15:52:16) * RDO Cloud scheduled maintenance on June 22, 1:00 UTC (1 hour) (chandankumar, 15:52:26) * chair for next meeting (chandankumar, 15:54:59) * ACTION: ykarel to chair for next meeting. (chandankumar, 15:55:44) * open floor (chandankumar, 15:55:57) Meeting ended at 16:00:30 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to drop an email for inputs on RDO packages naming conventions * jpena * jpena to send outage mail to rdo list * ykarel * ykarel to chair for next meeting. People present (lines said) --------------------------- * chandankumar (58) * fultonj (35) * amoralej (27) * dmsimard (23) * jpena (13) * openstack (10) * jruzicka (8) * trown (4) * number80 (3) * jschlueter (3) * ykarel (2) * rdobot (2) * Duck (1) * jistr (1) * EmilienM (1) Generated by `MeetBot`_ 0.1.4

1 0

CentOS PaaS SIG meeting (2017-06-21)
by Troy Dawson 21 Jun '17

21 Jun '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 21 June 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch -- minishift (marcindulak and lalatenduM) - Open Floor

1 0

CentOS Linux images for Vagrant updated to address "stack clash"
by Laurentiu Pancescu 21 Jun '17

21 Jun '17

Hi there, we have just released version 1705.02 of the official CentOS Linux images for Vagrant (centos/6 and centos/7) on Atlas. This update contains the security fixes for the "stack clash" vulnerability. https://access.redhat.com/security/vulnerabilities/stackguard https://blog.qualys.com/securitylabs/2017/06/19/the-stack-clash Existing images can be upgraded in-place via "sudo yum update". Best regards, Laurențiu

2 1

CentOS Atomic Host upgrade for CESA-2017:1484 kernel Security Update
by Jason Brooks 21 Jun '17

21 Jun '17

We've upgraded the ostree repo for CentOS Atomic Host (v7.1705.1) to include the packages affected by this advisory. You can upgrade your CentOS Atomic Host to this version with the command: atomic host upgrade --reboot Upgraded: ca-certificates 2017.2.11-70.1.el7_3 -> 2017.2.14-70.1.el7_3 glibc 2.17-157.el7_3.2 -> 2.17-157.el7_3.4 glibc-common 2.17-157.el7_3.2 -> 2.17-157.el7_3.4 kernel 3.10.0-514.21.1.el7 -> 3.10.0-514.21.2.el7 python-perf 3.10.0-514.21.1.el7 -> 3.10.0-514.21.2.el7 rpcbind 0.2.0-38.el7_3 -> 0.2.0-38.el7_3.1 ---------- Forwarded message ---------- From: Johnny Hughes <johnny(a)centos.org> Date: Tue, Jun 20, 2017 at 8:31 AM Subject: [CentOS-announce] CESA-2017:1484 Important CentOS 7 kernel Security Update To: centos-announce(a)centos.org CentOS Errata and Security Advisory 2017:1484 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1484.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5bf01ddf86b01221e0958422ec627961d035551e0474ac10245dc4958800705f kernel-3.10.0-514.21.2.el7.x86_64.rpm 232a0f622143e55d9011f3808471aad219396cccd156f24687b156b6d432a608 kernel-abi-whitelists-3.10.0-514.21.2.el7.noarch.rpm 967dc375e96b08d16737aad6d9630e6b47903dd02ce6d7a916c741eee78afc51 kernel-debug-3.10.0-514.21.2.el7.x86_64.rpm e68aa2a3377cdf058843658dbf4447d0091538891b0fa1bcd79c1a0dd2c9ce34 kernel-debug-devel-3.10.0-514.21.2.el7.x86_64.rpm 5000ca51295103b942c4941a5d2e53a6a78aadc08708d32c2ace22c227a58c4d kernel-devel-3.10.0-514.21.2.el7.x86_64.rpm ad28e256a053af55c9167e6d4ef737bf334b128df16cddc023e845c9f6a94480 kernel-doc-3.10.0-514.21.2.el7.noarch.rpm 62b49e8818f09e2833753e8bd1d861aa36a05b1f8982adcb80bf7f5cc9c8af24 kernel-headers-3.10.0-514.21.2.el7.x86_64.rpm 4a5b113ba6761d64045250d364470007c8961d8f374d4321bd3db24c629c4a9b kernel-tools-3.10.0-514.21.2.el7.x86_64.rpm 2c4d3a43385253a681618b4d0135753d893bd312fb82f19eb4d958c713d28bb9 kernel-tools-libs-3.10.0-514.21.2.el7.x86_64.rpm 7bc126ec06ffde55cf2217eb43cc44fdf96628131a5806f6303faad8e6b63252 kernel-tools-libs-devel-3.10.0-514.21.2.el7.x86_64.rpm 9d55662dadce103200676da60fce559da8d9bacea7fc38930e461c2a52665a7b perf-3.10.0-514.21.2.el7.x86_64.rpm d9ef263dba6b41ad7d4e1282a63ae04a1614788a1988485455448c0cf0034eb8 python-perf-3.10.0-514.21.2.el7.x86_64.rpm Source: 3235af92f1e1681e86df0c33bf822a56c7f9f54bdb88746dffb8764cf8bc7db5 kernel-3.10.0-514.21.2.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce

1 0

Using atomic-openshift-installer to upgrade from origin 1.4 to 1.5
by Jean-Francois Chevrette 20 Jun '17

20 Jun '17

Hi, 3 months ago I have used atomic-openshift-utils/installer to setup two OpenShift origin 1.4 clusters. Today I discovered that I am unable to upgrade from 1.4 to 1.5 because atomic-openshift-installer states that "No upgrades available for origin 1.4" atomic-openshift-utils-3.5.71-1.git.1.640cb7d.el7.noarch centos-release-openshift-origin15-1-1.el7.centos.noarch openshift-ansible-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-callback-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-docs-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-filter-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-lookup-plugins-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-playbooks-3.5.71-1.git.1.640cb7d.el7.noarch openshift-ansible-roles-3.5.71-1.git.1.640cb7d.el7.noarch 1.5 is in the list of supported install variants here: /usr/lib/python2.7/site-packages/ooinstall/variants.py However the UPGRADE_MAPPINGS list in /usr/lib/python2.7/site-packages/ooinstall/cli_installer.py only has upgrade paths for 3.4 and 3.5 Is upgrading between origin releases simply not supported/possible? Thanks, Jean-Francois C.

2 1

Please allow me to introduce myself...
by Al Stone 20 Jun '17

20 Jun '17

Howdy. I've recently had the desire to get more involved in the CentOS community -- both from professional and personal interests. So, please allow me to introduce myself to both CentOS folks, and to storage folks in particular. I have two goals, really: (1) make sure that Ceph upstream builds from scratch on aarch64 and ppc64le; that also means making sure that initial tests (i.e., make check) pass and that ultimately the full test suite passes; (2) make sure that the CentOS packages are as close to upstream as possible. For the first goal, the idea would be to work with upstream or anyone else to fully support more than just x86, even for development work. That's going to take a while since I'm new to the Ceph community but eager to join in; I've spent several years working with file systems and look forward to growing that knowledge. For the second goal, I would hope to be able to assist the current maintainer for Ceph packages and broaden the availability of Ceph. Since I'm really just getting started on the upstream work, I haven't jumped into this part yet. By the same token, though, I do have some experience as a Debian Developer and as a Fedora Packager that could be of use. I've also got the same goals for Fedora (eventually), and I am approaching it the same way -- make sure upstream is solid and stable on all architectures, and then make sure the packages are as up-to-date as they can be. As far as my personal background goes, I was literally a rocket scientist for a while, working on guidance algorithms for the flight systems. I've also been involved with Linux on some level for about two decades. The last few years have seen a lot of kernel work on ARMv8 (I drove the implementation of the ACPI subsystem for servers), and before that a port of the BSD file system to a proprietary OS that had to support asynchronous operations but had no real concept of processes or even tasks. Before that was a smattering of all sorts of things -- compiler work, tech support, technical consulting, the Andrew file system, the NCS (Network Computing System -- that probably dates me some :), and even some management (I swear I have fully recovered from that). Thanks for your time and patience in getting this far; I look forward to working with the community and helping to build a better CentOS. -- ciao, al ----------------------------------- Al Stone Software Engineer Red Hat, Inc. ahs3(a)redhat.com -----------------------------------

3 2

HPC SIG: IT4Innovations Ostrava - Supercomputer visit notes
by Jan Chaloupka 20 Jun '17

20 Jun '17

Sharing notes from a visit in IT4Innovations center in Ostrava. Supercomputer parameters info are available at [1] - mixture of Xeon, Xeon Phi and graphic card cores. Two clusters - Anselm runs RHEL 6, Salomon runs CentOS 6. Each node runs on a specific piece of a hardware. If a project is built on a builder of a different hardware, it is built with different flags and configuration and the resulting binaries are not properly optimized. Some projects need special features of compilers in order to run efficiently. Some of the features are available only in the latest versions of compilers. By the time the latest versions get into builders, it is usually to late. Or a project needs to be built with a proprietary compiler that is not publicly available. Or given each project needs different version of system libraries in general, the HPC infrastructure needs to offer various versions of the same library. The software needs to be available in many flavors. It means the same software to be built with multiple compilers and multiple versions. Different versions have different properties/features. Different compilers accent/provide different optimizations. Thus, a matrix of software to provide the users with. At the end a software needs to be built for the end-system architecture so it can use all the available instructions not to slow down the computation. For that reason (and many others) all the projects need to be built locally inside the cluster. That makes most of the binary packages in CentOS distribution unusable for the HPC use cases.Only usecase for rpm as proof of concepting on devel laptops is useful, not for final deployments.Currently, the EasyBuild project [2] is used as a replacement for rpm based spec files.Operators use Fedora upstream monitoring tool to monitor latest&greatest software (atm. ~400+ projects). Infiniband is usedfor connection of the nodes, sometimes issues with 3rd party SW drivers (Bull/Atos and/or HPE). Other notes: - Lot of service providers are still running on CentOS 6, which blocks upgrade to CentOS 7- shutdown of cluster not possible, infra for clusters changed between RHEL 6 and RHEL 7. - Puppet and Ansible used to deploy clusters (Ansible for disk-free nodes, Puppetfor nodes with disks). Still, each deployment is unique (e.g. unexpected situations) and thus not fully automated.For Ansiblepart,there is no roleusedfromthe AnsibleGalaxy - just Core modules and custom roles and playbooks - Experiments with containers as well via Singularity [3] (Docker is not fully supported on CentOS 6, needs privileged user account) - Demand on packaging and providing tooling for HPC rather than libraries themselves. If possible, provide full HPC stack that is upstream and distribution supported/maintained (including full stack upgrades). CI/CD supported as well. - HPC community is unfortunately security free, security fix deployment can take several months, dependencies on specific minor releases or kernel versions. Kernel KABI whitelist should be advised to 3rd party vendors of drivers to prevent hard version deps - Each assigned set of nodes is expected to be vanilla new. Given it takes some time before a node is rebooted (order of minutes), all the tooling running inside a node must clean everything a user task left. Thus, minimize a number of times a node is really rebooted. [1] https://docs.it4i.cz/salomon/hardware-overview/ [2] https://github.com/hpcugent/easybuild [3] http://singularity.lbl.gov/

4 3

New CentOS Atomic Available for Download
by Jason Brooks 19 Jun '17

19 Jun '17

An updated version of CentOS Atomic Host (tree version 7.1705), is now available[1]. CentOS Atomic Host is a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org. CentOS Atomic Host includes these core component versions: - atomic-1.17.2-4.git2760e30.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.6-28.git1398f24.el7.centos.x86_64 - etcd-3.1.7-1.el7.x86_64 - flannel-0.7.0-1.el7.x86_64 - kernel-3.10.0-514.21.1.el7.x86_64 - kubernetes-node-1.5.2-0.6.gitd33fd89.el7.x86_64 - ostree-2017.5-1.el7.x86_64 - rpm-ostree-client-2017.5-1.atomic.el7.x86_64 Containerized kubernetes-master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. Instead, you can run the master kubernetes components (apiserver, scheduler, and controller-manager) in containers, managed via systemd, using the service files and instructions on the CentOS wiki. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline, based on Dockerfiles from the CentOS-Dockerfiles repository. These containers have been tested with the kubernetes ansible scripts provided in the upstream contrib repository, and they work as expected, provided you first copy the service files onto your master. Alternatively, you can install the kubernetes-master components using rpm-ostree package layering using the command: atomic host install kubernetes-master. Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade Images Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box are Vagrant boxes for Libvirt and Virtualbox providers. The easiest way to consume these images is via the Atlas / Vagrant Cloud setup (see https://atlas.hashicorp.com/centos/boxes/atomic-host) For example, getting the VirtualBox instance up would involve running the following two commands on a machine with vagrant installed: $ vagrant init centos/atomic-host && vagrant up --provider virtualbox ISO The installer ISO can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This image allows users to control the install using kickstarts and to define custom storage, networking and user accounts. This is the recommended option for getting CentOS Atomic Host onto bare metal machines, or for generating your own image sets for custom environments. QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2 image is suitable for use in on-premise and local virtualized environments. We test this on OpenStack, AWS and local Libvirt installs. If your virtualization platform does not provide its own cloud-init metadata source, you can create your own NoCloud iso image. Amazon Machine Images Region Image ID ---------------- -------------- us-east-1 ami-90e7c686 ap-south-1 ami-2ba1de44 eu-west-2 ami-2b44524f eu-west-1 ami-a6c5dbc0 ap-northeast-2 ami-87ba65e9 ap-northeast-1 ami-64868e03 sa-east-1 ami-f9197295 ca-central-1 ami-66e55a02 ap-southeast-1 ami-850a88e6 ap-southeast-2 ami-caf7e6a9 eu-central-1 ami-42e84f2d us-east-2 ami-89bb9dec us-west-1 ami-245b7644 us-west-2 ami-68818a11 SHA Sums 46082267562f9eefbc4b29058696108f07cb0ceb2dafe601ec5d66bb1037120a CentOS-Atomic-Host-7.1705-GenericCloud.qcow2 1bd6dfbe360be599a45734f03b34e08cc903630327e1c54534eb4218bf18d0da CentOS-Atomic-Host-7.1705-GenericCloud.qcow2.gz aa4a3ac057d3ea898bea07052aa9fd20c7ca7ea3c8a5474bca9227622915e5e2 CentOS-Atomic-Host-7.1705-GenericCloud.qcow2.xz d99c2e9d1d31907ace3c1e54fc3087ebb9d627ca46168f7e65b469789cd39739 CentOS-Atomic-Host-7.1705-Installer.iso cfd6a29e26e202476b6a2dc54b1b31321688270a6cc6a9ef4206ac0ebd0e309c CentOS-Atomic-Host-7.1705-Vagrant-Libvirt.box d9b5f965f637a909efa15cd43063729db002c012c81a8cde0de588ea0932f970 CentOS-Atomic-Host-7.1705-Vagrant-VirtualBox.box 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, based on upstream work from Project Atomic. If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the 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 mailing list. Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

1 0

[SCLo SIG] new sclo-php*-php-pecl-amqp packages available for testing
by Remi Collet 16 Jun '17

16 Jun '17

Yet another package available in centos-sclo-sclo-testing (requested by some users) This extension can communicate with any AMQP spec 0-9-1 compatible server, such as RabbitMQ, OpenAMQP and Qpid, giving you the ability to create and delete exchanges and queues, as well as publish to any exchange and consume from any queue. https://pecl.php.net/package/amqp For rh-php56 * sclo-php56-php-amqp-1.9.1-1 For rh-php70 * sclo-php70-php-amqp-1.9.1-1 Notice: this package doesn't requires "librabbitmq" which is not available in base repository (only in EPEL), but use a static library instead. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Setting up CentOS Container-Pipeline to build AArch64 images
by Bamacharan Kundu 15 Jun '17

15 Jun '17

Hi, We are planning to build AArch64 images in centos community container pipeline[1]. We were trying to setup one POC on this today. We got stuck in few points. 1. We could not find openshift-orgin RPM or container to use for pipeline. 2. Docker complains with go panic to build ARM64 images in X86_64 box or X86 image in Aarch64 box. how could we get openshift-origin (either on package or as container) running in Aarch64? Any thoughts please. Regards Bamacharan [1] https://github.com/CentOS/container-pipeline-service

3 4

Boot aarch64 VM on x86_64 host
by Dharmit Shah 15 Jun '17

15 Jun '17

I'm trying to $subject using CentOS 7.3 system. I took a cue from the blog [0] on https://seven.centos.org and tried doing it with virt-install. However, the installation process doesn't really begin and I don't see any error either. Here's [1] the stdout when I run virt-install. And the list of packages [2] related to libvirt, qemu, kvm, arm. Can someone help me understand what I'm doing wrong? [0] https://seven.centos.org/2016/07/running-virtual-machines-on-aarch64/ [1] http://pastebin.centos.org/108011/ [2] http://pastebin.centos.org/108021/ Regards, Dharmit.

2 1

Re: [CentOS-devel] Azure Cloud Images
by Patrick Laimbock 14 Jun '17

14 Jun '17

On 18-05-17 20:02, lkd-centos(a)sky-haven.net wrote: > On 2017-05-18 12:58, Patrick Laimbock wrote: >> On 17-05-17 13:38, Akshay Kumar wrote: >>> Hi, >>> >>> We use the Cloud Generic Images >>> from https://cloud.centos.org/centos/7/images/ as a basis for making >>> custom images for AWS, GCP and Azure. >>> >>> It was great to see an Azure image that includes WALinuxAgent but 1703 >>> and 1704 don't work at all. Here's the bug report: >>> >>> https://bugs.centos.org/view.php?id=13264 >> >> Can you please do the conversion with qemu-img-ev from the Virt SIG >> and try again? The qemu-img-ev repo rpm can be found here: >> >> https://cbs.centos.org/koji/packageinfo?packageID=1950 > > Hi, > > There's nothing wrong with the image proper; the VM actually starts and > one can log in (if the starting image is unwrapped and deliberately > bugged with a hardcoded username/password first), it responds to SSH, etc. > > What doesn't happen is: waagent doesn't start because it hasn't been > `systemctl enable`'ed. Thanks for clarifying that the image boots properly. A new image with a fix will be generated. When it's ready (I don't know when as I'm not involved in that process) it should show up at: http://cloud.centos.org/centos/7/images/ HTH, Patrick

3 3

CentOS PaaS SIG meeting (2017-06-14)
by Troy Dawson 14 Jun '17

14 Jun '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 14 June 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch -- minishift (marcindulak and lalatenduM) - Open Floor -- Finding new head chairman for PAAS SIG Minutes from last meeting: https://www.centos.org/minutes/2017/june/centos-devel.2017-06-07-17.00.log.… Meeting:

1 0

Running openshift on arm64
by Mohammed Ahmed 14 Jun '17

14 Jun '17

Hi, I was wondering if it was possible to deploy openshift on arm64. We need this for building containers on the CentOS Container Pipeline. I am aware that there was some talk around rpms for the same, and it would be helpful if someone could point us to any resources. -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mohammedzee1000.wordpress.com https://mojo.redhat.com/people/moahmed RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat. Trusted | Red Hat <https://www.redhat.com/en/about/trusted>

2 1

LinchPin v1.0.1 (bugfix) has been released
by Clint Savage 13 Jun '17

13 Jun '17

Hi all, We are happy to announce that LinchPin v1.0.1 has been released. This is a bugfix release, which fixed the following issues: #263 - linchpin destroy duffy error after 1.0 upgrade #264 - 1.0 error with linchpin init/linchpin up #267 - linchpin rise/up error since upgrade to 1.0.0 #269 - libvirt provisioning does not work on centos/rhel machines #271 - Unable to get topology file to pass schema validation #274 - Authorization failing with linchpin 1.0.0 #275 - Inventory generation fails as resource outputs are not generated One enhancement was included: #280 - Make a default path for credentials The official release notes are available at https://github.com/CentOS- PaaS-SIG/linchpin/blob/develop/docs/source/release/RELEASE_1_0_1.rst This update is available via PyPi and packages will be available as soon as possible. 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

1 0

CentOS PaaS SIG meeting (2017-06-07)
by Troy Dawson 07 Jun '17

07 Jun '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 07 June 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch -- separate repo work -- minishift - Open Floor -- Finding new chairman for PAAS SIG

1 0

CentOS PaaS SIG needs a new Chairman
by Troy Dawson 07 Jun '17

07 Jun '17

Hi, My day job has changed. [1] I no longer have the ties, and information with the OpenShift stack that I used to have. Because of this I feel we need a new chairman for the PaaS SIG. This has been on the agenda for our weekly meeting, but that's having limited responses. Thus this email. Does anyone want to be the PaaS SIG Chairman? Does anyone know of someone who you think would be good? Ideas, input welcomes. Troy [1] - I'm still working at Red Hat. I'm now on the RHEL team.

1 0

[storage] Ceph (alt/multi)arch rebuild
by Haïkel 06 Jun '17

06 Jun '17

Hi, I'm currently trying to enable OpenStack on ppc64le architecture and it requires Ceph on ppc64le. So I applied to join to the Storage SIG (sponsor needed!) so I can help with the Ceph bootstrap and maintenance. Regards, H.

4 4

LinchPin v1.0.0 has been released
by Clint Savage 02 Jun '17

02 Jun '17

Hi all, We are happy to announce that LinchPin v1.0.0 has been released. This release includes many new features and improvements: Code and Configuration ------------------------------- * A basic Python API, with an implementation in the improved command-line interface * Improved python packaging, the library is under the linchpin namespace * Converted from linchpin_config.yml to linchpin.conf * Added tooling to load configurations from linchpin.conf * LinchPin Context to manage environment * Provides logging to a centralized log file, console (stdout/stderr), or both * Initial Unit Testing * CLI/API mostly covered * dummy provisioning provider to perform testing * Hooks - Allow external scripts to run at certain states during execution * pre / post hooks for both up and destroy actions * Direct credential management * All core cloud providers (gce, ec2, openstack) can authenticate using their traditional method, or be overridden with creds_path variable * Customizable workspace in the CLI/API * The PinFile, topology, layout and hooks live here. New Providers --------------------- * Beaker provider * OpenShift provisioning provider * Libvirt Documentation Improvements ---------------------------------------- * New Getting Started Guide * Beaker topology coverage * Python API reference * Glossary of items, and Ansible extravars used by LinchPin The official release notes are available at https://github.com/CentOS-PaaS-SIG/linchpin/blob/develop/docs/source/releas… This update is available via PyPi and packages will be available as soon as possible. If you discover any errors, or if you see any regressions which work on 0.9.x and prior, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues) I'd like to thank those that have contributed to this project. It's a success because you were here to help and make LinchPin grow as a community. Here's to another great year of hybrid cloud provisioning and a great community! If you feel this announcement would benefit any other groups or individuals not addressed here, please forward this announcement along. Cheers, and enjoy! Clint Savage LinchPin Maintainer/Senior Software Engineer Red Hat twitter: @herlo, github: herlo, IRC: herlo

1 0

[opstools] regular meeting June-14 2017
by Matthias Runge 01 Jun '17

01 Jun '17

Hello, we'll have the next opstools SIG meeting on Wed, June 14 2017, 18:00 UTC. The meeting will be held in #centos-devel on freenode. If you're interested in tools for operators, have questions, suggestions,... you're kindly invited to participate. See you then, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2017