devel June 2018

devel@lists.centos.org

35 participants
33 discussions

CentOS Atomic Host 7.1805 Available for Download
by Jason Brooks 15 Jun '18

15 Jun '18

The CentOS Atomic SIG has released an updated version of CentOS Atomic Host (7.1805), a lean operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. CentOS Atomic Host includes these core component versions: atomic-1.22.1-3.git2fd0860.el7.x86_64 cloud-init-0.7.9-24.el7.centos.x86_64 docker-1.13.1-63.git94f4240.el7.centos.x86_64 etcd-3.2.18-1.el7.x86_64 flannel-0.7.1-3.el7.x86_64 kernel-3.10.0-862.3.2.el7.x86_64 ostree-2018.1-4.el7.x86_64 rpm-ostree-client-2018.1-1.atomic.el7.x86_64 Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki [1]. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG, based on upstream work from Project Atomic. If you'd like to work on testing images, help with packaging, documentation -- join us! You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel mailing list. Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

1 0

Docker daemon not respecting the insecure registry which is part of /etc/containers/registry.conf
by Praveen Kumar 14 Jun '18

14 Jun '18

Hi, I spun up a fresh centos-7.5 VM on Digital ocean and tried to do oc cluster up which require to have insecure registry `172.30.0.0/16` when I am trying to add this in the /etc/containers/registry.conf this is not picked up by docker daemon even after restart:( I can see we have `/run/containers/registries.conf` as env file in the `/usr/lib/systemd/system/docker.service` which even not present on the system :( Not sure where we messed up or I made some mistake here. ``` # rpm -qa | grep docker docker-common-1.13.1-63.git94f4240.el7.centos.x86_64 docker-1.13.1-63.git94f4240.el7.centos.x86_64 docker-client-1.13.1-63.git94f4240.el7.centos.x86_64 ``` Note: Same addition of insecure registry working as expected in the fedora28. -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

1 0

Latest podman installation broken in CentOS
by Praveen Kumar 13 Jun '18

13 Jun '18

Hi, Looks like there might be issue with spec file of the podman for CentOS because of wrongly put the "Requires" version for *conmon* but this is what I am getting now when trying to install podman :( $ sudo yum install podman [...] --> Finished Dependency Resolution Error: Package: podman-0.5.3-7.gitc54b423.el7.x86_64 (virt7-container-common-candidate) Requires: conmon >= 2:1.10.0-3.gitb0f6d98 Installed: conmon-1.11.0-1.git55a3daa.el7.x86_64 (@virt7-container-common-candidate) conmon = 1.11.0-1.git55a3daa.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

3 4

SIG Meeting notes
by Karanbir Singh 12 Jun '18

12 Jun '18

hi everyone, Can I request that when you are attending or running a SIG meeting in #centos-devel, please use the #info command to the bot to record interesting events/objects/releases/information - these can then be collected and used for the Newsletter that Rich is putting together. It would dramatically increase the audience you can get this information out to as well. Regards and thanks, -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

1 0

[centos-devel] Ceph Storage SIG packages for Ceph Mimic
by Tobias Urdin 12 Jun '18

12 Jun '18

Hello Ceph Storage SIG, I'm researching support for Ceph Mimic for implementations in OpenStack projects. Is anybody working on CentOS packages for Ceph Mimic? i.e not the upstream EL7 packages on download.ceph.com Best regards

4 7

Status of Ansible within CentOS 7 and SIGs
by Thomas Oulevey 09 Jun '18

09 Jun '18

Hello Folks, Starting with CentOS 7.5, ansible package will no be available in CentOS -extras anymore as Red Hat decided to ship Ansible on a separate channel. Looking at ansible package in CBS [1] I see that Troy, Fabian, Sandro and Alan are rebuilding it. Can we get better at that task ? My proposal would to initiate a rebuild of the new Ansible channel[2](within the Config Management SIG) and follow a better release cycle. What do you think ? Would it be a solution from all SIG, or should we continue to ship Ansible within each SIG ? I would be happy to contribute the rebuild/debranding of existing source rpms (all available versions) if we all agree. Please note that EPEL is shipping again Ansible 2.5 as it was removed from Extras [3] -- Thomas Oulevey [1]: http://cbs.centos.org/koji/packageinfo?packageID=1947 [2]: http://ftp.redhat.com/pub/redhat/linux/enterprise/7Server/en/Ansible/SRPMS/ [3]: https://koji.fedoraproject.org/koji/packageinfo?packageID=13842

8 14

[Cloud SIG] Rocky Milestone 2 RDO Test Days June 14-15
by Rain Leander 07 Jun '18

07 Jun '18

Who’s up for a rematch? Rocky Milestone 2 is here and we’re ready to rumble! Join RDO [0] on June 14 & 15 for an awesome time of taking down bugs and fighting errors in the most recent release [1]. We certainly won’t be pulling any punches. Want to get in on the action? We’re looking for developers, users, operators, quality engineers, writers, and, yes, YOU. If you’re reading this, we think you’re a champion and we want your help! We’ll have packages for the following platforms: * RHEL 7 * CentOS 7 You’ll want a fresh install with latest updates installed so that there’s no hard-to-reproduce interactions with other things. We’ll be collecting feedback, writing up tickets, filing bugs, and answering questions. Even if you only have a few hours to spare, we’d love your help taking this new version for a spin to work out any kinks. Not only will this help identify issues early in the development process, but you can be the one of the first to cut your teeth on the latest versions of your favorite deployment methods like TripleO, PackStack, and Kolla. Interested? We’ll be gathering on #rdo (on Freenode IRC) for any associated questions / discussions, and working through the “Does it work?” tests [2]. Like Rocky said, “The world ain’t all sunshine and rainbows,” but with your help, we can keep moving forward and make the RDO world better for those around us. Hope to see you on the 14th & 15th! [0] https://www.rdoproject.org/ [1] https://www.rdoproject.org/testday/ [2] https://www.rdoproject.org/testday/tests/ -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

1 0

SIG Day @ CERN, October 18th
by Rich Bowen 06 Jun '18

06 Jun '18

Dear SIG members, As you've no doubt seen, we have a CentOS Dojo scheduled at CERN on October 19th. CERN has also generously offered us a meeting room on the day before, Thursday, October 18th, for SIG meetings. If your SIG is interested in taking advantage of this opportunity, please contact me with: * SIG Name * Primary contact for coordination * List of those likely to be in attendance Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Untag golang-1.9.4 from Centos PaaS Sig 3.7 Candidate Repo
by Daniel Comnea 06 Jun '18

06 Jun '18

I'll take care Scott in the next few hours, will update once is done. ---------- Forwarded message ---------- > From: Scott Dodson <sdodson(a)redhat.com> > To: Troy Dawson <tdawson(a)redhat.com>, "The CentOS developers mailing > list." <centos-devel(a)centos.org> > Cc: Steve Kuznetsov <skuznets(a)redhat.com> > Bcc: > Date: Mon, 4 Jun 2018 11:06:44 -0400 > Subject: [CentOS-devel] Untag golang-1.9.4 from Centos PaaS Sig 3.7 > Candidate Repo > Our CI team makes use of the centos paas sig repos and they've noticed > that we've got golang-1.9 tagged into the 3.7 repo where as Origin 3.7 > should be built with golang 1.8. > > Can we get golang-1.9.2-4.el7 untagged from paas7-openshift-origin37-candidate > ? > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > >

3 2

how to disable nscd and nm-dispatcher logs from centos console.
by Veetil, Vyshnav 06 Jun '18

06 Jun '18

Hi, After upgraded to CentOS7.4 we are getting some logs printed on the console. nscd logs are getting printed after executing the command service nscd restart. Nm-dispatcher logs are getting printed on the console after every restart. Can you please suggest any solution for disabling this logs. NetworkManager-1.8.0-9.el7.x86_64 nscd-2.17-196.el7.i686 Please find the attached config files using for nscd and NetworkManager.(/etc/NetworkManager/NetworkManager.conf) ----------------------------------------------------------------------------------------------------------------- Also please find the nscd logs getting printed on the console after executing service nscd restart nscd: 4220 monitoring file '/etc/passwd' nscd: 4220 monitoring directory '/etc/(2) nscd: 4220 monitoring file '/etc/group'(3) nm-dispatcher logs are getting printed on the console after every reboot. localhost login:nm-dispatcher:req:1 'hostname':new request (4 scripts) nm-dispatcher: req:2 'up' [eth0]: new request (4 scripts) nm-dispatcher: req:2 'up' [eth0]: start running ordered scripts... nm-dispatcher: req:3 'connectivity-change': new request (4 scripts) nm-dispatcher: req:4 'hostname':new request (4 scripts) nm-dispatcher: req:4 'hostname':start running ordered scripts... Can you please provide a solution for disabling this logs from console ? Thanks and Regards, Vyshnav

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2018