devel

devel@lists.centos.org

2 participants
4591 discussions

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

CentOS PaaS SIG meeting (2018-02-28)
by Troy Dawson 28 Feb '18

28 Feb '18

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

1 0

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

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