devel

devel@lists.centos.org

10 participants
4617 discussions

Status Update: CentOS Community Container Pipeline Service 28-Feb-2018
by Bamacharan Kundu 28 Feb '18

28 Feb '18

Hi All, Here is an update on the recent works done in Centos Community Container Pipeline * https://registry.centos.org is updated with new UI allowing users * search through the content * shows the dockerfile from which the image is built * Shows the Readme from the repo which mostly talks about the usage of the image * We have refactored garbage collector to get proper diff in container-index and registry.centos.org for removing extra images pushed to registry in build time. * We have disable the centos/centos:* base images to be excluded in RPM repo tracking. This will make sure these images are only updated in case of changes pushed to source repo. Our recent focus is: * We are developing API for exposing the build data from back end to show more details in registry UI. * Fixing beanstalk connection initialization method * Fix pre-build job entries CI to not check for target file * Fixes bug in dangling volume cleanup post scan * Prevents logging unnecessary recurring queue operational messages Regards Bamacharan Kundu

1 0

Email alias for SIG members?
by Matthias Runge 28 Feb '18

28 Feb '18

Hello, I recently thought about the possibility of getting an email alias for SIG members. That should not be forwarded to a mailing list. Would something like that be possible? Idea is to spam people in charge directly. It can contain sensitive data, or data not belonging to mailing lists, like certificates, build failures, that kind of thing. Other than that, all communication should be kept public, IMHO. So: would it be possible to get an email alias like <sig-name>@centos.org to forward emails? If yes, what would be the process? Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

1 0

Re: [CentOS-devel] CentOS for IBM Mainframes.
by David Edelsohn 27 Feb '18

27 Feb '18

>>>>> Javier Romero writes: > Is there any chance that IBM donate this hardware for the CentOS > project? Think that will be also useful for that company to have > another Linux distro running on their Z Systems. IBM can and does provide raw z/VM VMs at Marist or Syracuse for other Linux distros, such as Debian. That is what you really need, not "hardware". The discussion about donating hardware is off track. The Debian support is completely community driven and maintained. If there is a group of CentOS developers who want to bootstrap and maintain it, the resources probably can be made available. If this is a request for IBM to enable CentOS on IBMz, that is an orthogonal discussion about IBM resources and likely would require IBM customer demand. Thanks, David

4 10

Two New Committee Members Needed for CentOS PAAS SIG
by Troy Dawson 27 Feb '18

27 Feb '18

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.

1 1

New sclo-php##-phpiredis 1.0.0 packages available for testing
by Remi Collet 23 Feb '18

23 Feb '18

New packages available in centos-sclo-sclo-testing Phpiredis is an extension for PHP 5.x and 7.x based on hiredis that provides a simple and efficient client for Redis and a fast incremental parser / serializer for the RESP protocol. For rh-php56 * sclo-php56-php-phpiredis-1.0.0-1 For rh-php70 * sclo-php70-php-phpiredis-1.0.0-1 For rh-php71 * sclo-php71-php-phpiredis-1.0.0-1 This extension is also an accelerator used by the Predis pure-PHP library (https://packagist.org/packages/predis/predis) Sometime ago I wrote a blog entry about Redis access from PHP: https://blog.remirepo.net/post/2016/11/13/Redis-from-PHP Feedback welcome. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

Fwd: [Arm-dev] Kubernetes support on ARM32
by Fabian Arrotin 23 Feb '18

23 Feb '18

Forwarding this to centos-devel, as that's where other discussions around kubernetes rebuild[s] takes place too. What would be the best way to to have people from armhfp world discussing with the people managing/maintaing k8s on cbs.centos.org ? Just opening a thread about this, but it's good to know that : - people are willing to (re)build it for armhfp - and that it works with just rebuilding the src.rpm from cbs.centos.org (covering so far x86_64, while aarch64, ppc64le are also other available target arches in koji/cbs) BTW, kudos to Wagner Sartori (trunet) for the rebuild ! :-) -------- Forwarded Message -------- Subject: {Disarmed} [Arm-dev] Kubernetes support on ARM32 Date: Fri, 23 Feb 2018 06:13:48 -0300 (BRT) From: Trunet <trunet-centos(a)wsartori.com> Reply-To: Conversations around CentOS on ARM hardware <arm-dev(a)centos.org> To: arm-dev <arm-dev(a)centos.org> Hey, what's up! I finished building all needed packages to bring kubernetes to ARM. All of them were brought by simply copying src packages from CBS and doing minor or no changes at all. To my surprise, kubeadm ran perfectly fine, it got the correspondent arm image for each component. I went with weave for pod network layer, as it have network policy and ARM support. Manual changes, was to symlink all files under /opt/cni/bin into /usr/libexec/cni, otherwise the pods will not find the cni plugins and doesn't start (like kube-dns stuck at containercreating). And kubernetes-dashboard, you need to change tha image to be arm instead of amd64. Repo is here: https://armv7.dev.centos.org/repodir/community-kubernetes-testing/ =================================== # kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"archive", BuildDate:"2018-02-22T14:26:58Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} # kubectl cluster-info Kubernetes master is running at https://192.168.x.x:6443 KubeDNS is running at *MailScanner warning: numerical links are often malicious:* https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn… <https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn…> To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. =================================== Thanks for Arrfab for setting up the build environment and repository. Best regards, Wagner Sartori Junior

1 0

Kubernetes support on ARM32
by Trunet 23 Feb '18

23 Feb '18

Hey, what's up! I finished building all needed packages to bring kubernetes to ARM. All of them were brought by simply copying src packages from CBS and doing minor or no changes at all. To my surprise, kubeadm ran perfectly fine, it got the correspondent arm image for each component. I went with weave for pod network layer, as it have network policy and ARM support. Manual changes, was to symlink all files under /opt/cni/bin into /usr/libexec/cni, otherwise the pods will not find the cni plugins and doesn't start (like kube-dns stuck at containercreating). And kubernetes-dashboard, you need to change tha image to be arm instead of amd64. Repo is here: https://armv7.dev.centos.org/repodir/community-kubernetes-testing/ =================================== # kubectl version Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"archive", BuildDate:"2018-02-22T14:26:58Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/arm"} # kubectl cluster-info Kubernetes master is running at https://192.168.x.x:6443/ KubeDNS is running at https://192.168.x.x:6443/api/v1/namespaces/kube-system/services/kube-dns:dn… To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. =================================== Thanks for Arrfab for setting up the build environment and repository. Best regards, Wagner Sartori Junior

1 0

[Cloud SIG] meeting minutes, Feb 22, 2018
by Rich Bowen 22 Feb '18

22 Feb '18

Thanks to those that attended today's Cloud SIG meeting. We were particularly pleased to welcome Rohit Yadav, from the Apache CloudStack community, and we look forward to the Cloud SIG no longer being a monoculture. Minutes: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Minutes (text): https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Log: https://www.centos.org/minutes/2018/February/centos-devel.2018-02-22-15.02.… Next week's meeting will be at the same time - 15:00 UTC, Thursday March 1, on #centos-devel on Freenode (I will be traveling, and thus absent, so if someone else can step up to chair this meeting, that would be greatly appreciated.) -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

1 0

[Cloud SIG] CloudStack publishing effort in CentOS
by Rohit Yadav 22 Feb '18

22 Feb '18

Hi all, (/cc cloudstack-dev) I'm Rohit Yadav, committer/pmc from the Apache CloudStack [1] community. Apache CloudStack is an IaaS cloud computing platform. I've been maintaining and publishing the CloudStack noredist repos [3][4] for few years now, and I would like to get them published to the official CentOS (and other distros) repositories. I met Rich during Fosdem yesterday and he suggested to reach out to the cloud-sig/list [2] to discuss how we can get CloudStack rpms into CentOS. I understand in the past we were not very successful at that, but I want to make a second attempt especially since we've introduced the concept of LTS releases in CloudStack. I'm not sure if the devel list is the right place or if an explicit cloud-sig list exists [2], so please advise -- - Where may I start? - What is the packaging/release process and how can one help become a package maintainer? - Advise on legal stuff around publishing of rpms (the noredist repositories bundle non-oss jar dependencies such as those from Vmware vim sdk etc)? - How can the packages also be available for Fedora, may RHEL and derivatives? - Thoughts, comments? Thanks. Regards. [1] https://cloudstack.apache.org/ [2] https://wiki.centos.org/SpecialInterestGroup/Cloud [3] packages.shapeblue.com/cloudstack/upstream [4] CloudStack packaging, spec files etc: https://github.com/apache/cloudstack/tree/master/packaging

3 4

[Cloud SIG] Reboot weekly Cloud SIG meetings
by Haïkel 22 Feb '18

22 Feb '18

Hi, since we have a newer group (CloudStack) joining us, we decided to reboot our weekly meetings. In order to find a timeslot that suits everyone, I suggest that we use a whenisgood poll: http://whenisgood.net/bpqn4fn Please don't forget to set your timezone when answering the poll. I'll publish results asap Regards, H.

4 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel