devel June 2016

devel@lists.centos.org

42 participants
39 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2016