devel June 2017

devel@lists.centos.org

42 participants
33 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2017