devel June 2016

devel@lists.centos.org

42 participants
42 discussions

[opstools] next steps
by Matthias Runge 29 Jun '16

29 Jun '16

Hello, it looks like the OpsTools SIG was approved[1]. *yay*! So, the next steps should be to create a build target, tags. I would like to rebuild or to retag builds already built under a tag of the cloud SIG. What would be the preferred way here? Rebuild? Just tag? Best, Matthias [1] https://wiki.centos.org/SpecialInterestGroup/OpsTools -- Matthias Runge <mrunge(a)matthias-runge.de>

4 5

Update on status of CentOS Container Pipeline
by Bamacharan Kundu 29 Jun '16

29 Jun '16

Hi All, Update on recent work done for the CentOS Container Pipeline. - We went through building the openshift origin images in Container Pipeline and published them to registry.centos.org successfully. We faced many issues with the upstream dockerfiles and moved to rpm based dockerfiles for building the images. - We have got almost all the monitoring pieces set up in production, now if there is any change in the system (i.e. openshift is down, jenkins is not communicating, or other changes) we get an alert notifying the change in the system. - We added multiple cron jobs for monitoring and communicating with zabix to get notifications on changes in system level parameters. -We got test suite set up for pipeline. Now all the images built through pipeline, goes through a set of tests for ensuring the container is runnable. For now we are testing containers based on CentOS 7. - We got atomic scan set up. This checks the container for rpm update or any other system update required for the container image. For now this process only sends notification to the user, stating the changes required in container, but does not update the container. - We noticed that all the source repos do not want the Dockerfile to be built for building centos based images. (i.e. for openshift origin we built the dockerfiles with name Dockerfile.centos7). To get these type of repos built in the pipeline, we added one more parameter dockerfile-name to index.yml which allows user to provide name of the dockerfile to be built. -We saw we are bringing up multiple independent stages (like polling source repo, build, test, delivery, notification) together to work sequentially as well as scale rapidly. Keeping this in mind we came up with beanstalkd tubes for managing communication point between all the independent phases and synchronizing with necessary information provided through job details. -We got Atomic Registry built in registry.centos.org with all its dependent containers available in registry.c.o. Even though we got all the dependency containers built in registry.co atomic registry is pulling origin-deployer and origin-pod from docker.io as this is hard coded to be pulled from docker.io. Our immediate next focus is : - implement firewall rules in production machines. - write a wiki page for wiki.centos.org for atomic registry. - work on setting up sanity checks for verifying project entries in index.yml Regards Bamacharan Kundu -- Bamacharan Kundu IRC Nick- bamachrn http://bamacharankundu.wordpress.com/

3 3

No CentOS Paas SIG meeting today (June 29)
by Troy Dawson 29 Jun '16

29 Jun '16

Hello, No PaaS SIG sync-up meeting this week Next meeting will be July 6th Time: 1700 UTC - Wedensdays Date: Today Wedensday, 6 July 2016 Where: IRC- Freenode - #centos-devel Last meeting minutes: https://www.centos.org/minutes/2016/june/centos-devel.2016-06-20-14.00.log.…

1 0

Need package signed and pushed before the weekend
by Troy Dawson 24 Jun '16

24 Jun '16

Hi, I've tried being patient, but the weekend is coming, and Summit is next week, and I need a package signed and pushed to the mirrors yesterday (literaly). I'm looking at the timezones in despair as it's getting late for everyone I know that has key signing authority. Is there anyone still online with authority to sign and push packages to release. If so, would you be able to do origin-1.2.0-4.el7 which is tagged with paas7-openshift-origin-release Thank You Troy Dawson

2 3

[Atomic SIG] Atomic Developer Bundle 2.2.1 is released
by Lalatendu Mohanty 23 Jun '16

23 Jun '16

We have released the Atomic Developer Bundle (ADB) 2..2.1 through CentOS Atomic SIG. The ADB release also includes release of following ecosystem projects: * adb-utils 1.8: A set of utility scripts and configuration files for ADB Thisrelease adds several bugfixesand enhancemnets , including: * Mounting users home directory into VM using vagrant-sshfs * Allow an user to access the OpenShift docker registry and use as a local docker registry. * New Jenkins templates for OpenShift This release also includes many changes and bugfixes, which are detailed in the release changelog of adb-utils [1]andADB [2]. Please update the ADB Vagrant box [3] and the vagrant-service-manager ($ vagrant plugin update vagrant-service-manager) and give the new ADB version a spin. [1] https://github.com/projectatomic/adb-utils/releases/tag/v1. <https://github.com/projectatomic/adb-utils/releases/tag/v1.8>8 <https://github.com/projectatomic/adb-utils/releases/tag/v1.8> [2] https://github.com/projectatomic/adb-atomic-developer-bundle/tree/v2. <https://github.com/projectatomic/adb-atomic-developer-bundle/tree/v2.2.1>2.1 <https://github.com/projectatomic/adb-atomic-developer-bundle/tree/v2.2.1> [3] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do…

1 0

CentOS PaaS SIG meeting (2016-06-22)
by Troy Dawson 22 Jun '16

22 Jun '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 22 June 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- origin --- should we build the origin 1.3 in the openshift-futures target? --- openshift-ansible -- Automated testing -- images / image building -- Documentation -- Automated rpm building - Open Floor mzee1000 can't make it for the time of the meeting, he is going to record a demo on image building.

1 0

CentOS Atomic Host test images
by Эдуард Искандаров 21 Jun '16

21 Jun '16

Hi Jason, Is there any change to release CentOS Atomic Host? Last release was made more than 2 month ago and consist of alpha version of kubernetes/ Regards, Eduard

2 3

sclo-vagrant1: new OpenStack provider available for testing
by Dominic Cleal 21 Jun '16

21 Jun '16

A new OpenStack provider for the sclo-vagrant1 collection is available for testing in the centos-sclo-sclo-testing repository. To install it, run: yum install centos-release-scl yum install --enablerepo=centos-sclo-sclo-testing sclo-vagrant1-vagrant-openstack-provider It can be used by running: scl enable sclo-vagrant1 "vagrant up --provider=openstack" and documentation is available for the provider in the -doc RPM or from https://github.com/ggiamarchi/vagrant-openstack-provider. Please provide feedback if you have it, else I'll push to the stable repo in a week or so. Kind regards, -- Dominic Cleal dominic(a)cleal.org

1 0

sclo-php5*: new packages available for testing
by Remi Collet 21 Jun '16

21 Jun '16

New packages built and tagged: sclo-php54-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm sclo-php55-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm sclo-php56-php-pecl-uploadprogress-1.0.3.1-1.el6.x86_64.rpm sclo-php54-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm sclo-php55-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm sclo-php56-php-pecl-uploadprogress-1.0.3.1-1.el7.x86_64.rpm These packages extend the php54, php55 and rh-php56 collections, and are available now in centos-sclo-sclo-testing repostiory. Feedback welcome. These packages will be push in stable repository in a few weeks if no bugs are reported. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 1

Update on status of CentOS Community Container Pipeline.
by Mohammed Ahmed 21 Jun '16

21 Jun '16

Hi all, Here is the update for work recently done for the CentOS Community Container Pipeline. - Docker builds in the CCCP-Service were taking a long time for building each images. We tracked down the issue and got in conclusion of building the images sequentially. This increase the performance as the other option of creating docker lvm pool is already in place. - - For getting the builds sequential we created beanstalkd tubes managing the builds from jenkins. Jenkins pushes all the builds to beankstalkd tube. beanstalk client starts the build one after another is complete. - We were checking with the facts to include OSBS as build client for CCCP. After analyzing different facts of benefits of osbs and our current issues for the system, we are postponing OSBS adoption till our first release. We will be looking for adopting this after that. - - We got atomic registry built from CCCP-Service with proper namespace. This is also demoed as end to end user story to the team. Currently we are taking the origin base images from outside of registry.centos.org In the coming days, we will be focusing on : - Getting Openshift origin completely built from registry.centos.org with all its base images (also indirectly solving problem with dependent container images) - Write a wiki page on wiki.centos.org for atomic registry. - Setting up end to end delivery with test suites (container scanning etc) and build sequence. *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) IRC : mzee1000 mohammedzee1000.wordpress.com Old PGP Public Key : http://pgp.mit.edu/pks/lookup?op=get&search=0x726A119E62847E37 (REVOKED) New PGP Public Key : https://pgp.mit.edu/pks/lookup?op=get&search=0x147A8569AFC5E9ED

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2016