June 2016 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

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

Re: [CentOS-devel] [rdo-list] [centos-ci] Artifacts server does not support ranges / resume of downloads?
by Haïkel 18 Aug '16

18 Aug '16

2016-06-28 4:25 GMT+02:00 Gerard Braad <me(a)gbraad.nl>: > Hi all, > > > Usually I download the undercloud images using: > > https://gist.github.com/gbraad/45cbe30415b0dc631f5e8d20beaffebf > > which targets: 'artifacts.ci.centos.org' but now get > > "HTTP server doesn't seem to support byte ranges. Cannot resume." > > I need to resume a download about 10 times on the office connection > (China), so what happened? I have a workaround by storing the files at > another server first in Japan or the west-coast which supports > resuming. > > Although, being able to resume the download of these files is preferable. > > regards, > > > Gerard > Since this part of infrastructure is managed by CentOS Core Team, CC'ing centos-devel list. > > -- > > Gerard Braad | http://gbraad.nl > [ Doing Open Source Matters ] > > _______________________________________________ > rdo-list mailing list > rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list > > To unsubscribe: rdo-list-unsubscribe(a)redhat.com

6 9

Ceph Jewel packaging in CentOS Storage SIG
by Emilien Macchi 16 Aug '16

16 Aug '16

Hi, I'm working on openstack/puppet-ceph module to deploy Ceph Jewel for OpenStack TripleO and Red Hat Director (OpenStack installers). I'm very interested to know when I'll be able to download Jewel packages from SIG on x84_64: buildlogs.centos.org/centos/7/storage/x86_64/ceph-jewel/ currently does not contain Ceph packages. Using ceph.com repositories for us is not optimal as we try to use a maximum of CentOS supported repositories, like we do for OpenStack. Thanks, -- Emilien Macchi

4 10

Re: [CentOS-devel] ConfigMgmt SIG Status
by Ben Hosmer 15 Jul '16

15 Jul '16

I'm having a hard time getting my bearings. Where can I help out?

4 3

Interest in a SIG for logging and monitoring?
by Steve Huston 12 Jul '16

12 Jul '16

Apologies for not being able to use a proper reply, since I only just joined the list today; came here to say that I too would be interested in such a SIG. -- Steve Huston - W2SRH - Unix Sysadmin, PICSciE/CSES & Astrophysical Sci Princeton University | ICBM Address: 40.346344 -74.652242 345 Lewis Library |"On my ship, the Rocinante, wheeling through Princeton, NJ 08544 | the galaxies; headed for the heart of Cygnus, (267) 793-0852 | headlong into mystery." -Rush, 'Cygnus X-1'

6 6

How to build maven packages in CBS?
by Rich Megginson 04 Jul '16

04 Jul '16

Are there any instructions/examples about how to use `cbs maven-build/maven-chain`?

8 19

[Virt SIG] status of virt7-docker repository?
by Haïkel 30 Jun '16

30 Jun '16

Hi, I'm considering to add virt7-docker repository as a dependency for the openstack repo from Cloud SIG. It seems that it's not consumable yet and some packages like Kubernetes are outdated. Could you update me with the current status and if there is anything we can do to help? Regards, H.

6 9

[Cloud SIG]Build noarch pkgs fail
by Hao Ran HR Hu 30 Jun '16

30 Jun '16

Hello, I tried to rebuild the some noarch pkgs from Openstack Mitaka repo, but some of them got issues in both x86 and ppc64le platform. For example, for python-oslo-config( http://vault.centos.org/7.2.1511/cloud/Source/openstack-mitaka/python-oslo-… ） When the build process went to check, Some unit tests were failed. For my point of view, the source code in srpm need some update or my build environment may have some issues. Did any buddy face the same situation before? some log from build: running test running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --list running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpFiPlSa running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpbdPzKX running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpz2uYD0 running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpCc_Hq1 running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmp7EWf0P running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpwRRCEI running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpPO60Tc running=OS_STDOUT_CAPTURE=1 OS_STDERR_CAPTURE=1 OS_TEST_TIMEOUT=60 $ {PYTHON:-python} -m subunit.run discover -t ./ . --load-list /tmp/tmpq5UuZk ====================================================================== FAIL: oslo_config.tests.test_cfg.SadPathTestCase.test_conf_file_permission_denied tags: worker-0 ---------------------------------------------------------------------- Empty attachments: stderr stdout Traceback (most recent call last): File "oslo_config/tests/test_cfg.py", line 3120, in test_conf_file_permission_denied self.conf, ['--config-file', path]) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 422, in assertRaises self.assertThat(our_callable, matcher) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: <oslo_config.tests.test_cfg.TestConfigOpts object at 0x24e3750> returned None ====================================================================== FAIL: oslo_config.tests.test_generator.IgnoreDoublesTestCase.test_list_ignores_doubles tags: worker-3 ---------------------------------------------------------------------- Empty attachments: stderr stdout Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "oslo_config/tests/test_generator.py", line 857, in test_list_ignores_doubles for _, listing in generator._list_opts(None): File "oslo_config/generator.py", line 336, in _list_opts _update_defaults(namespaces) File "oslo_config/generator.py", line 320, in _update_defaults for update in _get_opt_default_updaters(namespaces): File "oslo_config/generator.py", line 314, in _get_opt_default_updaters invoke_on_load=False) File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 55, in __init__ verify_requirements) File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 171, in _load_plugins self._on_load_failure_callback(self, ep, err) File "/usr/lib/python2.7/site-packages/stevedore/extension.py", line 163, in _load_plugins verify_requirements, File "/usr/lib/python2.7/site-packages/stevedore/named.py", line 119, in _load_one_plugin if ep.name not in self._names: TypeError: argument of type 'NoneType' is not iterable Ran 769 tests in 0.548s FAILED (id=0, failures=2) error: testr failed (1) error: Bad exit status from /var/tmp/rpm-tmp.44whJa (%check) Thanks & Regards, Hu Haoran (Vern) ------------------------------------------------------------------------- IBM China Systems & Technology Lab huhaoran(a)cn.ibm.com 86-21-60928179 "Let us use our own hardworking and determination to decide our destiny!" - Jose Mourinho

1 0

[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

ConfigMgmt SIG Status
by Ben Hosmer 20 Jun '16

20 Jun '16

What's the status of this group? What do we need to do to move things along?

4 3

Re: [CentOS-devel] [scl.org] Obsolete centos-release-SCL in CentOS-6 with centos-release-scl-rh
by Dominic Cleal 16 Jun '16

16 Jun '16

On 16/06/16 10:14, Honza Horak wrote: > I've tried the new package and it looks good, it does everything it > should from my PoV. Thanks for testing, I've tagged it for release. -- Dominic Cleal dominic(a)cleal.org

2 1

Rebuilding OpenStack for AArch64
by Marcin Juszkiewicz 15 Jun '16

15 Jun '16

There were discussions on irc about it but I lost track of who I should speak with etc so decided to write to mailing list instead. The goal is to rebuild OpenStack 'mitaka' packages for AArch64 (AltArch) in CBS (there is one builder for this architecture). Question is how to make it in best way? One of ideas was: 1. create new tag (cloud7-openstack-mitaka-candidate-aarch64?) 2. import all 'noarch' builds from cloud7-openstack-mitaka-* tags 3. send all required packages to the builder 4. test resulting packages 5. import/merge all of them to proper cloud7-openstack-mitaka-* tag Other was about doing scratch builds and merging them with x86-64 ones. How we can proceed? I think that first idea is good as it allows us to do builds without touching x86-64 tag before we are ready for merging. But I do not have koji experience so may be wrong.

4 5

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

15 Jun '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 15 June 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- origin 1.2.0 - now in stable repo -- Automated testing -- images / image building -- Documentation --- Need openshift-ansible in centos repo for quickstart - progress? - Automated rpm building - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/may/centos-devel.2016-05-25-17.00.log.h…

1 0

Obsolete centos-release-SCL in CentOS-6 with centos-release-scl-rh
by Johnny Hughes 14 Jun '16

14 Jun '16

Honza, Can you set centos-release-scl-rh (or if more appropriate, centos-release-scl) to obsolete centos-release-SCL in CentOS-6. I have removed the old SCL/ repo in 6.8 and you have newer versions of all packages. Thanks, Johnny Hughes

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 2016