devel

devel@lists.centos.org

2 participants
4591 discussions

LinchPin v1.0.3 (bugfix) has been released
by Clint Savage 12 Sep '17

12 Sep '17

Hi all, We are happy to announce that LinchPin v1.0.3 has been released. This is a bugfix release, which has the following updates: * remove gce2 module and use the standard module from ansible * requirements.txt to use Ansible >= 2.3.1 (this means we can package it for Fedora) * remove other requirements from requirements.txt that are not necessary * improved documentation around clouds.yaml and --creds-path * CLI exits with proper exit codes (with tests to verify) * linchpin fetch (download local/remote workspaces) * flake8 testing * ovirt support with docs! * linchpin.conf supports overriding specific sections from previous config * os_server module updated to handle multiple provisioning properly * remove cruft from api framework * upgrade setuptools and pip in tests * move lp_init into api and cli to work together * workspace set and get methods * other miscellany The official release notes are available at https://github.com/CentOS-PaaS-SIG/linchpin/releases/tag/v1.0.3 This update is available via PyPi - https://pypi.python.org/pypi/linchpin If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues). Cheers and enjoy! Clint Savage LinchPin Maintainer Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin

1 0

CentOS 7.4.1708 as basic el7 buildroot in CBS
by Fabian Arrotin 11 Sep '17

11 Sep '17

Hi, As discussed on the list, we wanted to push 7.4.1708 first to CBS/Koji and at the same time to CI (so that what's built against a specific tree can be tested against the same set of pkgs in CI) We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS. That means that we'll switch (before it's pushed to external mirrors and so be announced) the buildroots to start using the following repositories: 7.4.1708/{os,updates,extras} That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le . We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks for this as Koji will have to rebuild internal metadata for those mirrors, aka "koji regen-repo $buildroot") We'll post an update here when it will be switched and so active. That will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days) Hope this will help -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 4

No Paas SIG meeting this week
by Troy Dawson 11 Sep '17

11 Sep '17

I forgot that I was going to be at a conference this week and not be able to make the Paas SIG meeting. If someone else wants to run the meeting this week, they can. I currently don't know of anything new this week, but if you have an announcement that can't wait an extra week, feel free to sent it to centos-devel. Sorry about cancelling this week. Troy

1 0

oVirt 4.2 preparations - ppc64le repository closure
by Sandro Bonazzola 08 Sep '17

08 Sep '17

Hi, I'm checking what's missing for repository closure on ppc64le for the future oVirt 4.2 and I've this: echo "Checking Virt SIG 4.2 candidate ppc64le" dnf --quiet --refresh repoclosure --arch=ppc64le \ --repofrompath=42candidate_ppc, https://cbs.centos.org/repos/virt7-ovirt-42-candidate/ppc64le/os/ --check=42candidate_ppc \ --repofrompath=common_candidate_ppc, https://cbs.centos.org/repos/virt7-ovirt-common-candidate/ppc64le/os --check=common_candidate_ppc \ --repofrompath=base_ppc,http://mirror.centos.org/altarch/7/os/ppc64le/ --repo=base_ppc \ --repofrompath=extra_ppc, http://mirror.centos.org/altarch/7/extras/ppc64le/ --repo=extra_ppc \ --repofrompath=c7updates_ppc, http://mirror.centos.org/altarch/7/updates/ppc64le/ --repo=c7updates_ppc \ --repofrompath=qemu_ppc, https://cbs.centos.org/repos/virt7-kvm-common-candidate/ppc64le/os/ --check=qemu_ppc \ --repofrompath=fluent_ppc, https://cbs.centos.org/repos/opstools7-fluentd-012-candidate/ppc64le/os/ --repo=fluent_ppc \ --repofrompath=gluster_ppc, https://cbs.centos.org/repos/storage7-gluster-310-candidate/ppc64le/os/ --repo=gluster_ppc \ --repofrompath=collectd_ppc, https://cbs.centos.org/repos/opstools7-perfmon-common-candidate/ppc64le/os/ --repo=collectd_ppc Checking Virt SIG 4.2 candidate ppc64le package: gperftools-2.4-7.el7.ppc64le from common_candidate_ppc unresolved deps: pprof = 2.4-7.el7 package: openvswitch-ovn-central-1:2.7.2-3.1fc27.el7.ppc64le from 42candidate_ppc unresolved deps: firewalld-filesystem package: openvswitch-ovn-docker-1:2.7.2-3.1fc27.el7.ppc64le from 42candidate_ppc unresolved deps: python2-openvswitch package: openvswitch-ovn-host-1:2.7.2-3.1fc27.el7.ppc64le from 42candidate_ppc unresolved deps: firewalld-filesystem package: python2-twisted-16.1.1-3.el7.ppc64le from 42candidate_ppc unresolved deps: python-service-identity pyserial python-pyasn1 package: qemu-kvm-ev-10:2.6.0-28.el7.10.1.ppc64le from qemu_ppc unresolved deps: SLOF >= 20160223-1.gitdbbfda4 ipxe-roms-qemu >= 20160127-4 seavgabios-bin >= 1.9.1-4 package: vdsm-4.20.2-1.el7.ppc64le from 42candidate_ppc unresolved deps: selinux-policy-targeted >= 3.13.1-60.el7 ovirt-imageio-common ovirt-imageio-daemon python-inotify python-six >= 1.9.0 vdsm-python = 4.20.2-1.el7 python-ipaddress python-dateutil sos vdsm-http = 4.20.2-1.el7 python-netaddr python-ioprocess >= 0.16.1-1 vdsm-hook-vmfex-dev = 4.20.2-1.el7 vdsm-jsonrpc = 4.20.2-1.el7 python-requests python-decorator mom >= 0.5.8 ovirt-vmconsole >= 1.0.0-0 python-pthreading >= 0.1.3-3 There are some noarch packages which aren't in ppc64le resolution tree, can you help debugging why they are missing? -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

Running openshift cluster on aarch64
by Bamacharan Kundu 08 Sep '17

08 Sep '17

Hi, I am trying to setup openshift allinone cluster in aarch64. I tried few ways. 1. RPM: a. I installed the origin RPMs from the centos cbs [1]. started origin and while trying run the registry with pods it pulls the x86_64 origin-pod and deployer. so fails with go panic. b. tried running origin start, dockerregistry with config. pods are running but builds are not starting saying invalid registry endpoints (as it is trying to push the built image to internal registry) 2. Container based: Built all the images (origin, origin-pod, origin-deployer,origin-docker-registry) in aarch64 from the origin dockerfiles[2]. started origin. then while deploying registry using `oadm registry --config`, deployer fails with `serviceaccount/token` file not found. any suggestion on how I can get this running on RPM based/ container based? or is it possible to run a hybrid arch openshift cluster? I meant running few nodes on x86_64 and few on aarch64/ppc64le. [1] https://cbs.centos.org/repos/paas7-openshift-multiarch-candidate/aarch64/os/ [2] https://github.com/openshift/origin Regards Bamacharan Kundu

2 1

CentOS PaaS SIG meeting (2017-09-06)
by Troy Dawson 06 Sep '17

06 Sep '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 06 September 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building -- minishift (marcindulak and lalatenduM) -- kompose (cdrage (candate) pradeepto (india) and tkral (brno)) - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2017/august/centos-devel.2017-08-23-17.01.lo…

1 0

rpmbuild failure when extracting debuginfo
by Thomas F Herbert 06 Sep '17

06 Sep '17

I get the following failure in cbs builds during the extraction of debug info. --------------------------snip--------------------------------- + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/vpp-17.10 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libvlib.so.0.0.0 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libjvpp_common.so.0.0.0 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libsvmdb.so.0.0.0 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libvlibsocket.so.0.0.0 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libvnet.so.0.0.0 extracting debug info from /builddir/build/BUILDROOT/vpp-17.10-rc0~267_ge1a0ab3.x86_64/usr/lib64/libvppinfra.so.0.0.0 /usr/lib/rpm/debugedit: -b arg has to be either the same length as -d arg, or more than 1 char longer error: Bad exit status from /var/tmp/rpm-tmp.n1k50O (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.n1k50O (%install) Child return code was: 1 EXCEPTION: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/vpp.spec Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 88, in trace result = func(*args, **kw) File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 547, in do raise exception.Error("Command failed. See logs for output.\n # %s" % (command,), child.returncode) Error: Command failed. See logs for output. # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/vpp.spec LEAVE do --> EXCEPTION RAISED -----------------------------snip---------------------------------------- Incidentally, the same problem occurs in Fedora-review and in Brew RHEL builds. It does not occur in local builds with rpmbuild on Centos, RHEL brew or Fedora 25. Notice comment 55 in this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=304121 about a fixed bug in debugedit. Can we get cbs upgraded with rpm-build package version 4.13.0.1-24 Should I submit a ticket to get that package installed in cbs for my tag? -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat*

1 0

Question about building python with python2 macros
by Thomas F Herbert 05 Sep '17

05 Sep '17

I have come upon a problem building python packages. The upstream spec file I am using makes heavy use of %py2_build macro which causes builds to fail in cbs because this macro is provided by python2-rpm-macros. That macro is in EPEL and not available for cbs builds. Should I just replace py2_build with its expansion as found in python2-rpm-macros? --TFH -- *Thomas F Herbert* NFV and Fast Data Planes Office of Technology *Red Hat*

2 2

kick starting duffy2 dev on github
by Karanbir Singh 02 Sep '17

02 Sep '17

hi everyone, I've started working on duffy2 here : https://github.com/kbsingh/duffy2 - there is a base framework in place there that should give you an idea on how this all comes together, I will keep pushing bits - but this will likely get major momentum once we are done with 7.1708 Everyone is welcome to come join the effort, but I would highly recommend joining the ci-users list to track what is going on. We will have no private meetings about this, all conversation to be kept to the ci-users list, bugs.centos.org and the github repo itself. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 3

[Cloud SIG] RDO Pike released
by Rich Bowen 01 Sep '17

01 Sep '17

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Pike for RPM-based distributions, CentOS Linux 7 and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Pike is the 16th release from the OpenStack project, which is the work of more than 2300 contributors from around the world. 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 Pike release include: * Ironic now supports booting from Cinder volumes, rolling upgrades and Redfish protocol. * We added OVN support to Packstack. * We added support to install the Horizon plugins for several services in Packstack. Added/Updated packages The following packages and services were added or updated in this release: * Kuryr and Kuryr-kubernetes: an integration between OpenStack and Kubernetes networking. * Senlin: a clustering service for OpenStack clouds. * Shade: a simple client library for interacting with OpenStack clouds, used by Ansible among others. * python-pankoclient: a client library for the event storage and REST API for Ceilometer. * python-scciclient: a ServerView Common Command Interface Client Library, for the FUJITSU iRMC S4 - integrated Remote Management Controller. Other additions include: Python Libraries * os-xenapi * ovsdbapp (deps) * python-daiquiri (deps) * python-deprecation (deps) * python-exabgp * python-json-logger (deps) * python-netmiko (deps) * python-os-traits * python-paunch * python-scciclient * python-scrypt (deps) * python-sphinxcontrib-actdiag (deps) (pending) * python-sphinxcontrib-websupport (deps) * python-stestr (deps) * python-subunit2sql (deps) * python-sushy * shade (SDK) * update XStatic packages (update) * update crudini to 0.9 (deps) (update) * upgrade liberasurecode and pyeclib libraries to 1.5.0 (update) (deps) Tempest Plugins * python-barbican-tests-tempest * python-keystone-testst-tempest * python-kuryr-tests-tempest * python-patrole-tests-tempest * python-vmware-nsx-tests-tempest * python-watcher-tests-tempest Puppet-Modules * puppet-murano * puppet-veritas_hyperscale * puppet-vitrage OpenStack Projects * kuryr * kuryr-kubernetes * openstack-glare * openstack-panko * openstack-senlin * OpenStack Clients * mistral-lib * python-glareclient * python-pankoclient * python-senlinclient Contributors During the Pike cycle, we started the EasyFix initiative, which has resulted in several new people joining our ranks. These include: * Christopher Brown * Anthony Chow * T. Nicole Williams * Ricardo Arguello But, we wouldn't want to overlook anyone. Thank you to all 172 contributors who participated in producing this release: Aditya Prakash Vaja, Alan Bishop, Alan Pevec, Alex Schultz, Alexander Stafeyev, Alfredo Moralejo, Andrii Kroshchenko, Anil, Antoni Segura Puimedon, Arie Bregman, Assaf Muller, Ben Nemec, Bernard Cafarelli, Bogdan Dobrelya, Brent Eagles, Brian Haley, Carlos Gonçalves, Chandan Kumar, Christian Schwede, Christopher Brown, Damien Ciabrini, Dan Radez, Daniel Alvarez, Daniel Farrell, Daniel Mellado, David Moreau Simard, Derek Higgins, Doug Hellmann, Dougal Matthews, Edu Alcañiz, Eduardo Gonzalez, Elise Gafford, Emilien Macchi, Eric Harney, Eyal, Feng Pan, Frederic Lepied, Frederic Lepied, Garth Mollett, Gaël Chamoulaud, Giulio Fidente, Gorka Eguileor, Hanxi Liu, Harry Rybacki, Honza Pokorny, Ian Main, Igor Yozhikov, Ihar Hrachyshka, Jakub Libosvar, Jakub Ruzicka, Janki, Jason E. Rist, Jason Joyce, Javier Peña, Jeffrey Zhang, Jeremy Liu, Jiří Stránský, Johan Guldmyr, John Eckersberg, John Fulton, John R. Dennis, Jon Schlueter, Juan Antonio Osorio, Juan Badia Payno, Julie Pichon, Julien Danjou, Karim Boumedhel, Koki Sanagi, Lars Kellogg-Stedman, Lee Yarwood, Leif Madsen, Lon Hohberger, Lucas Alvares Gomes, Luigi Toscano, Luis Tomás, Luke Hinds, Martin André, Martin Kopec, Martin Mágr, Matt Young, Matthias Runge, Michal Pryc, Michele Baldessari, Mike Burns, Mike Fedosin, Mohammed Naser, Oliver Walsh, Parag Nemade, Paul Belanger, Petr Kovar, Pradeep Kilambi, Rabi Mishra, Radomir Dopieralski, Raoul Scarazzini, Ricardo Arguello, Ricardo Noriega, Rob Crittenden, Russell Bryant, Ryan Brady, Ryan Hallisey, Sarath Kumar, Spyros Trigazis, Stephen Finucane, Steve Baker, Steve Gordon, Steven Hardy, Suraj Narwade, Sven Anderson, T. Nichole Williams, Telles Nóbrega, Terry Wilson, Thierry Vignaud, Thomas Hervé, Thomas Morin, Tim Rozet, Tom Barron, Tony Breeds, Tristan Cacqueray, afazekas, danpawlik, dnyanmpawar, hamzy, inarotzk, j-zimnowoda, kamleshp, marios, mdbooth, michaelhenkel, mkolesni, numansiddique, pawarsandeepu, prateek1192, ratailor, shreshtha90, vakwetu, vtas-hyperscale-ci, yrobla, zhangguoqing, Vladislav Odintsov, Xin Wu, XueFengLiu, Yatin Karel, Yedidyah Bar David, adriano petrich, bcrochet, changzhi, diana, djipko, dprince, dtantsur, eggmaster, eglynn, elmiko, flaper87, gpocentek, gregswift, hguemar, jason guiditta, jprovaznik, mangelajo, marcosflobo, morsik, nmagnezi, sahid, sileht, slagle, trown, vkmc, wes hayutin, xbezdick, zaitcev, and zaneb. 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. https://www.rdoproject.org/install/packstack/ For a production deployment of RDO, use the TripleO Quickstart and you'll be running a production cloud in short order. https://www.rdoproject.org/tripleo/ 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 Pike, although it is running RDO.) http://packstack.org/ Getting Help The RDO Project participates in a Q&A service at ask.openstack.org, for more developer-oriented content we recommend joining the rdo-list mailing list. Remember to post a brief introduction about yourself and your RDO story. 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 tooi ( http://facebook.com/RDOCommunity ), and also Google+ ( http://tm3.org/rdogplus )

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