May 2017 - devel - lists.centos.org

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

Request for feedback: CentOS-Atomic container
by Karanbir Singh 25 Sep '17

25 Sep '17

hi Alpha2: registry.centos.org/kbsingh/centos-atomic:7-alpha2 The CentOS Atomic Container is a minimal ( 30MB on disk ) image that can be used to host static content, and small footprint content that does not need the entire CentOS Linux Base image. This is also not meant to replace CentOS Linux Base image as the default, we want to make it available as an additional container base for apps that find it useful. The main highlight is that it does not contain yum, but has microdnf. I am looking for feedback, and some wider testing as well as recommendations on howto further reduce size, before we move to release. You can consume this as : docker run -t -i \ registry.centos.org/kbsingh/centos-atomic:7-alpha2 \ /bin/bash regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

Re: [CentOS-devel] Azure Cloud Images
by Patrick Laimbock 14 Jun '17

14 Jun '17

On 18-05-17 20:02, lkd-centos(a)sky-haven.net wrote: > On 2017-05-18 12:58, Patrick Laimbock wrote: >> On 17-05-17 13:38, Akshay Kumar wrote: >>> Hi, >>> >>> We use the Cloud Generic Images >>> from https://cloud.centos.org/centos/7/images/ as a basis for making >>> custom images for AWS, GCP and Azure. >>> >>> It was great to see an Azure image that includes WALinuxAgent but 1703 >>> and 1704 don't work at all. Here's the bug report: >>> >>> https://bugs.centos.org/view.php?id=13264 >> >> Can you please do the conversion with qemu-img-ev from the Virt SIG >> and try again? The qemu-img-ev repo rpm can be found here: >> >> https://cbs.centos.org/koji/packageinfo?packageID=1950 > > Hi, > > There's nothing wrong with the image proper; the VM actually starts and > one can log in (if the starting image is unwrapped and deliberately > bugged with a hardcoded username/password first), it responds to SSH, etc. > > What doesn't happen is: waagent doesn't start because it hasn't been > `systemctl enable`'ed. Thanks for clarifying that the image boots properly. A new image with a fix will be generated. When it's ready (I don't know when as I'm not involved in that process) it should show up at: http://cloud.centos.org/centos/7/images/ HTH, Patrick

3 3

[opstools] regular meeting June-14 2017
by Matthias Runge 01 Jun '17

01 Jun '17

Hello, we'll have the next opstools SIG meeting on Wed, June 14 2017, 18:00 UTC. The meeting will be held in #centos-devel on freenode. If you're interested in tools for operators, have questions, suggestions,... you're kindly invited to participate. See you then, Matthias -- Matthias Runge <mrunge(a)matthias-runge.de>

2 1

CentOS PaaS SIG meeting (2017-05-31)
by Troy Dawson 31 May '17

31 May '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 31 May 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- separate repo work -- minishift - Find new chairperson for Paas SIG - Open Floor

1 0

CentOS SIG NFV Membership Request
by Billy McFall 31 May '17

31 May '17

I would like to join the CentOS SIG-NFV. I am copying Thomas Herbert, acting chair of the CentOS SIG-NFV, who is wiling to sponsor me. SIG NFV Request bug: https://bugs.centos.org/view.php?id=13338 Thank you, Billy McFall -- *Billy McFall* SDN Group Office of Technology *Red Hat*

2 1

NFV SIG - update
by Dave Neary 30 May '17

30 May '17

Hi, There has been a recent resurgence of interest in the NFV SIG, and in the interest of keeping the momentum going, I would like to step aside as SIG char, and recommend that Tom Herbert take over. Tom has taken on the packaging and building of VPP and DPDK-accelerated OVS for OPNFV, and has been active in the SIG in recent weeks, and I think he will help add the structure that has been sorely lacking from me in recent months. I'm not sure what the process is for replacing a SIG chair - can someone let us know, please? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

4 4

Configuration Management SIG status and new pkg proposal : ARA (Ansible Run Analysis)
by Fabian Arrotin 29 May '17

29 May '17

Hi, While technically speaking a ConfigManagement SIG was approved a long time ago (https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG) it seems that nothing was built at all, and that initial people probably lost interest in that idea (?) The interesting part is that other SIGs that were relying on such config management tools (like puppet or ansible) built it themselves in their own tags : - puppet : https://cbs.centos.org/koji/packageinfo?packageID=390 - ansible : https://cbs.centos.org/koji/packageinfo?packageID=1947 I was myself just the "sponsor" for other community people to join and take care of the pkgs they were interested into, but suddenly I was myself busy rebuilding such tools, and I'd even have a new one as a proposal : ARA ARA (Ansible Run Analysis) is a tool written under the openstack umbrella, and written/maintained by dmsimard (Cloud SIG member) For people not aware of it, it's a callback plugin for ansible that let you store (and so browse) your ansible logs through webui (and it stores those reports into a DB) I initially thought about building that in the infrastructure7-el7 target, but maybe some other people would be interested into using those as pkgs directly in a repo on mirror.centos.org Initially the author wanted to have it in Epel7, but due to two pkgs version that are in [base] (and so that will not be overwritten by Epel), that doesn't seem possible. So my proposal would be to rebuild what's needed through configmgmt SIG , including the two packages (pytest and python-jinja2) For people interested in the ARA in Epel7 story, here is the pkg review : https://bugzilla.redhat.com/show_bug.cgi?id=1426193 Ideas, opinions ? -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

Re: [CentOS-devel] [OpsTools] fluentd packages tagging
by Sandro Bonazzola 29 May '17

29 May '17

On Mon, May 29, 2017 at 12:20 PM, Matthias Runge <mrunge(a)redhat.com> wrote: > On Mon, May 29, 2017 at 10:52:01AM +0200, Sandro Bonazzola wrote: > > On Mon, May 29, 2017 at 10:15 AM, Matthias Runge <mrunge(a)redhat.com> > wrote: > > > > > On Fri, May 26, 2017 at 07:55:32AM -0600, Rich Megginson wrote: > > > > On 05/26/2017 02:59 AM, Sandro Bonazzola wrote: > > > > > Hi, > > > > > I just discovered we have an issue with the package tagging about > > > fluentd. > > > > > fluentd-0.12.26-2.el7 > > > > > > > > $ cbs list-tags |grep opstool|grep release > > > > > opstools7-common-release > > > > > opstools7-elastic-2-release > > > > > opstools7-elastic-common-release > > > > > > > > We should get rid of these elastic tags, or at least ignore them, > and if > > > > there are any packages that we need in those tags, we should add > them to > > > > fluentd-012. > > > > > > > > > opstools7-fluentd-012-release > > > > > opstools7-perfmon-common-release > > > > > opstools7-sensu-023-release > > > > > opstools7-sensu-027-release > > > > > opstools7-sensu-common-release > > > > > > > > > > can we review the mappings in order to get fluentd packages > correctly > > > > > published? > > > > > Personally I would be happy if fluentd and collectd can be in > their own > > > > > repo so they won't require openstack as dependency repo. > > > > > > Packages tagged and not landing somewhere is unfortunate and should be > > > sorted out. > > > Unfortunately, that is nothing we can do, that is something for > > > CentOS infra folks. > > > > > > > Well, we need to tell CentOS infra folks which tags should be published > and > > where :-) > > So, I can open a ticket for adding the mappings for fluentd-012 tags, > where > > the packages should land? > > > > https://buildlogs.centos.org/centos/7/opstools/$basearch/fluentd/ ? > > guessed above because on mirrors we have: > > http://mirror.centos.org/centos/7/opstools/x86_64/fluentd/ > > on buildlogs, the path is https://buildlogs.centos.org/ > centos/7/opstools/x86_64/logging/ > > There is https://bugs.centos.org/view.php?id=12718 > which also requests to publish packages from > opstools7-fluentd-012-release > to https://mirror.centos.org/centos/$releasever/opstools/$basearch/ > > Maybe I've missed something? > Brian, can you please look again at https://bugs.centos.org/view. php?id=12718 ? As Matthias noted, there was already a request for this publishing. > > Matthias > -- > Matthias Runge <mrunge(a)redhat.com> > -- 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

Re: [CentOS-devel] [OpsTools] fluentd packages tagging
by Sandro Bonazzola 29 May '17

29 May '17

On Mon, May 29, 2017 at 10:15 AM, Matthias Runge <mrunge(a)redhat.com> wrote: > On Fri, May 26, 2017 at 07:55:32AM -0600, Rich Megginson wrote: > > On 05/26/2017 02:59 AM, Sandro Bonazzola wrote: > > > Hi, > > > I just discovered we have an issue with the package tagging about > fluentd. > > > fluentd-0.12.26-2.el7 > > > > $ cbs list-tags |grep opstool|grep release > > > opstools7-common-release > > > opstools7-elastic-2-release > > > opstools7-elastic-common-release > > > > We should get rid of these elastic tags, or at least ignore them, and if > > there are any packages that we need in those tags, we should add them to > > fluentd-012. > > > > > opstools7-fluentd-012-release > > > opstools7-perfmon-common-release > > > opstools7-sensu-023-release > > > opstools7-sensu-027-release > > > opstools7-sensu-common-release > > > > > > can we review the mappings in order to get fluentd packages correctly > > > published? > > > Personally I would be happy if fluentd and collectd can be in their own > > > repo so they won't require openstack as dependency repo. > > Packages tagged and not landing somewhere is unfortunate and should be > sorted out. > Unfortunately, that is nothing we can do, that is something for > CentOS infra folks. > Well, we need to tell CentOS infra folks which tags should be published and where :-) So, I can open a ticket for adding the mappings for fluentd-012 tags, where the packages should land? https://buildlogs.centos.org/centos/7/opstools/$basearch/fluentd/ ? guessed above because on mirrors we have: http://mirror.centos.org/centos/7/opstools/x86_64/fluentd/ > > I'm fine with getting rid of opstools7-elastic-* tags, we don't use them > anymore and afaik, we won't do in the future. > Ok, so if nobody objecting, I'll open a ticket tomorrow morning for removing those tags from cbs. > > A while ago, we moved the packages relying on openstack packages to the > cloud sig, and cremoved the dependency of openstack from opstools. > Unfortunately, the resulting centos-release-opstools build[1] > was not tagged and pushed correctly. > > [1] http://cbs.centos.org/koji/buildinfo?buildID=16800 now tagged correctly, not yet in http://mirror.centos.org/centos/7/extras/x86_64/Packages/ but should be just a matter of sign and publish which should hopefully happen soon. > > -- > Matthias Runge <mrunge(a)matthias-runge.de> > -- 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

[OpsTools] fluentd packages tagging
by Sandro Bonazzola 26 May '17

26 May '17

Hi, I just discovered we have an issue with the package tagging about fluentd. fluentd-0.12.26-2.el7 <http://cbs.centos.org/koji/buildinfo?buildID=16789> has been tagged opstools7-fluentd-012-testing and opstools7-fluentd-012-release but never got published. The published package is fluentd-0.12.26-1.el7 <http://cbs.centos.org/koji/buildinfo?buildID=11354> because of opstools7-elastic-common-testing and Now, I don't have a clue on how tagging has been mapped to testing and release repo but I think we need to fix it. Initial request was: https://bugs.centos.org/view.php?id=12718 with following mappings: for opstools SIG, could you please collect packages from opstools7-perfmon-common-release opstools7-common-release opstools7-elastic2-release opstools7-sensu-common-release opstools7-sensu-027-release and sync them to https://mirror.centos.org/centos/$releasever/opstools/$basearch/ Right now we have following tags: $ cbs list-tags |grep opstool|grep release opstools7-common-release opstools7-elastic-2-release opstools7-elastic-common-release opstools7-fluentd-012-release opstools7-perfmon-common-release opstools7-sensu-023-release opstools7-sensu-027-release opstools7-sensu-common-release can we review the mappings in order to get fluentd packages correctly published? Personally I would be happy if fluentd and collectd can be in their own repo so they won't require openstack as dependency repo. Thanks, -- 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>

2 1

CentOS PaaS SIG meeting (2017-05-24)
by Troy Dawson 24 May '17

24 May '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 24 May 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- origin-1.5.1 --- openshift-ansible-3.5.71 --- ansible 2.2.3.0 -- Documentation -- Automated rpm building and Automated testing -- Images and Image building -- Multi-arch -- separate repo work -- minishift --- minishift 1.0.1 has been released. - Open Floor -- Finding new head chairman for PAAS SIG

1 1

Problem logging into cbs.centos.org
by Thomas F Herbert 24 May '17

24 May '17

All: I no longer can log in to https://cbs.centos.org/koji/login I get SSL_ERROR_HANDSHAKE_FAILURE_ALERT Did I forget a procedure along the way after generating new keys as instructed by email? accounts.centos.org works fine. --Tom -- *Thomas F Herbert* Fast Data Planes Office of Technology *Red Hat*

2 2

[storage] ceph-ansible tagged for -testing
by Giulio Fidente 23 May '17

23 May '17

Hi, we have tagged for testing ceph-ansible 2.2 in the jewel repo! Its dependencies, including ansible, are cross-tagged. These can be explored at http://cbs.centos.org/koji/builds?order=nvr&tagID=654 If you wanted to deploy Ceph using ceph-ansible, this is the right time to start testing it! :D -- Giulio Fidente GPG KEY: 08D733BA

1 1

CBS Outage : ppc64/ppc64le builders in offline mode
by Fabian Arrotin 23 May '17

23 May '17

Hi As discussed in CBS meeting today (https://www.centos.org/minutes/2017/may/centos-devel.2017-05-22-14.00.html) and also reflected on https://status.centos.org , we currently suffer from a hardware issue that impacts our connectivity to some nodes, including the ppc64/ppc64le builders. That means that SIG people willing to build against/for those arches will not be able to see their build jobs/tasks running as long as connectivity isn't restored (and no ETA yet) Worth noting that those builders are disabled at the koji level (https://cbs.centos.org/koji/hosts?state=all&order=name) We'll keep you informed when those nodes will be reachable again and so enabled for cbs builds Kind Regards, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 1

Bazel test cases timing out on CentOS 7.
by Atul Sowani 19 May '17

19 May '17

Hi, I have observed that certain Bazel test cases from the test suite are timing out on CentOS 7 (kernel version 3.10.0-123.el7.x86_64). For example, I tried bazel_coverage_test (using command bazel test //src/test/shell/bazel:bazel_coverage_test) and observed that it just hangs. I tried tracing it using strace (log attached). This seems to be CentOS specific behavior as I did not observe this on Ubuntu 16.04. Has anybody observed this? Is this a regression as far as CentOS is concerned? Thanks, Atul.

5 7

Azure Cloud Images
by Akshay Kumar 18 May '17

18 May '17

Hi, We use the Cloud Generic Images from https://cloud.centos.org/centos/7/images/ as a basis for making custom images for AWS, GCP and Azure. It was great to see an Azure image that includes WALinuxAgent but 1703 and 1704 don't work at all. Here's the bug report: https://bugs.centos.org/view.php?id=13264 Thanks, A

2 2

CentOS 7 extras for alternative arches and Koji workflow.
by Thomas Oulevey 18 May '17

18 May '17

Dear All, I'd like to retake a pending issue with -extras on c7 and ask for feedback. I wear two hats : 1/ User, who would like to use altarch-extras packages soon after they are available in c7-extras. 2/ CBS maintainer, who would like to provide his users consistent buildroot across all architecture. Let's start with 1/. The important point here is to be able to rely on altarch-extras and expect it to be in sync with c7-extras in a reasonable time. (days not weeks) As it was always stated c7 (all repositories) cannot and should not be blocked by any alt-arch rebuild and should be independent. However we should at least try to provide these alt-arches packages in a timely manner. A lot of coordination (and motivated contributors) is needed if this effort is not centralized. For 2/ it is very important that we build package with similar buildroots on all arches. As c7-extras is now enabled for everybody, we should be able to have the altarch equivalent in a timely manner. Also all SIGs who are building for all alt-arches will be blocked in case an extras package is needed in the buildroot (we dealt with these issues during 7.2 -> 7.3 cycle and it will come back at next minor release. Additional challenge is the -cr repository which is enabled in CBS by default) However I understand, we need a way not to block official c7 arches for other arches that need fixes. After reviewing the possibilities with different people last year, one way to tackle this issue, would be to have 2 targets in Koji ; 1 including official arches and the other including official arches + alt-arches and allow SIG to bypass alt-arches by changing one target in their config. In this config we could move easily an altarch to an official one and vice versa. Finally, in my opinion, an easy way to have consistent altarch-extras would be to monitor official repository on the mirror.c.o (or buildlogs.c.o) and rebuild automatically extras packages in Koji, which would be picked by a script and so all altarch-extras would be generated directly by Koji itself and the process pretty much automated. The signing process will still be the key to control what is pushed to buildlogs/mirrors. (and close to what we already do) I don't see many disadvantages for this solution but I would like to know if it is possible to move forward and what the community and core contributors think about it. Is altarch-extras important to you ? thank you for your feedback, -- Thomas Oulevey

7 11

Anyone using the serial console from our Vagrant boxes?
by Laurentiu Pancescu 18 May '17

18 May '17

Hi, The default boot parameters of our Vagrant images activate a serial console. The problem is that VirtualBox doesn't enable a serial port by default, and our boxes hang if they really need to use the console, e.g. during relabeling[1] or during the initial configuration required for sealed VM templates (what I'm currently trying for Hyper-V support). Is anyone using the serial console we provide? If not, I can just remove the console=ttyS0 parameter from the kernel command line. Otherwise, a patch for Image Factory is trivial - I can just the set the port to enabled in the XML file, without the cable connected, and probably move console=tty0 on the last position, so it becomes the active console. Libvirt and VMware don't cause this problem, because they either have a serial port by default, or pretend it's there if the guest tries to use it. No idea if Hyper-V or Xen default to having a serial port. I would like to fix this for version 1704, which should be released in the following days. Regards, Laurențiu [1] https://bugs.centos.org/view.php?id=13213

4 6

office hours May 18th
by Karanbir Singh 17 May '17

17 May '17

hi apologies for the short notice, but I am unable to make the office hrs tomorrow. However, if anyone has pending points for the session - please email me and I will aim to reply within a few hrs. regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

[question] audio and realtime SIG
by Markus Seeber 17 May '17

17 May '17

Hello, I remember there has been some interest in creating an audio related SIG a few years ago and I'd like to know if anything has come out of that. Related to that, I wonder if there is a realtime related SIG. From a first quick search over the wiki pages there does not seem to be such a thing. On the other hand I know that CERN has put some effort in maintaining rt-kernels for their rt messaging grid. Is there anything going on the CentOS side in regard to these use cases? best regards Markus

1 0

New CentOS Atomic Host with Optional Docker 1.13
by Jason Brooks 16 May '17

16 May '17

An updated version of CentOS Atomic Host (tree version 7.20170428), is now available, featuring the option of substituting the host’s default docker 1.12 container engine with a more recent, docker 1.13-based version, provided via the docker-latest package. https://wiki.centos.org/SpecialInterestGroup/Atomic/Download CentOS Atomic Host is a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux 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. These images are available for download at cloud.centos.org. The backing ostree repo is published to mirror.centos.org. CentOS Atomic Host includes these core component versions: - atomic-1.15.4-2.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - docker-1.12.6-16.el7.centos.x86_64 - etcd-3.1.3-1.el7.x86_64 - flannel-0.7.0-1.el7.x86_64 - kernel-3.10.0-514.16.1.el7.x86_64 - kubernetes-node-1.5.2-0.5.gita552679.el7.x86_64 - ostree-2017.3-2.el7.x86_64 - rpm-ostree-client-2017.3-1.atomic.el7.x86_64 Containerized kubernetes-master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. Instead, you can run the master kubernetes components (apiserver, scheduler, and controller-manager) in containers, managed via systemd, using the service files and instructions on the CentOS wiki. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline, based on Dockerfiles from the CentOS-Dockerfiles repository. https://wiki.centos.org/SpecialInterestGroup/Atomic/ContainerizedMaster These containers have been tested with the kubernetes ansible scripts provided in the upstream contrib repository, and they work as expected, provided you first copy the service files onto your master. Alternatively, you can install the kubernetes-master components using rpm-ostree package layering using the command: atomic host install kubernetes-master. docker-latest You can switch to the alternate docker version by running: # systemctl disable docker --now # systemctl enable docker-latest --now # sed -i '/DOCKERBINARY/s/^#//g' /etc/sysconfig/docker Because both docker services share the /run/docker directory, you cannot run both docker and docker-latest at the same time on the same system. Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade Images Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box are Vagrant boxes for Libvirt and Virtualbox providers. The easiest way to consume these images is via the Atlas / Vagrant Cloud setup (see https://atlas.hashicorp.com/centos/boxes/atomic-host) For example, getting the VirtualBox instance up would involve running the following two commands on a machine with vagrant installed: $ vagrant init centos/atomic-host && vagrant up --provider virtualbox ISO The installer ISO can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This image allows users to control the install using kickstarts and to define custom storage, networking and user accounts. This is the recommended option for getting CentOS Atomic Host onto bare metal machines, or for generating your own image sets for custom environments. QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2 image is suitable for use in on-premise and local virtualized environments. We test this on OpenStack, AWS and local Libvirt installs. If your virtualization platform does not provide its own cloud-init metadata source, you can create your own NoCloud iso image. Amazon Machine Images Region Image ID ---------------- -------------- ap-south-1 ami-9c7b06f3 eu-west-2 ami-14425570 eu-west-1 ami-a1b9b7c7 ap-northeast-2 ami-e01cc18e ap-northeast-1 ami-2a0d304d sa-east-1 ami-ce7619a2 ca-central-1 ami-8b813def ap-southeast-1 ami-61e36702 ap-southeast-2 ami-84c7cde7 eu-central-1 ami-f970ae96 us-east-1 ami-4a70015c us-east-2 ami-d2cfe8b7 us-west-1 ami-57ba9c37 us-west-2 ami-fbd8bd9b SHA Sums 977c9b6e70dd0170fc092520f01be26c4d256ffe5340928d79c762850e5cedd9 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2 781074c43aa6a6f3cad61a77108541976776eb3cb6fe30f54ca746a8314b5f87 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2.gz aef7fedf01b920ee75449467eb93724405cb22d861311fbc42406a7bd4dbfee2 CentOS-Atomic-Host-7.1704-GenericCloud.qcow2.xz 669c5fd1b97bc2849a7e3dbec325207d98e834ce71e17e0921b583820d91f4f5 CentOS-Atomic-Host-7.1704-Installer.iso b5ef69bff65ab595992649f62c8fc67c61faa59ba7f4ff0cb455a9196e450ae2 CentOS-Atomic-Host-7.1704-Vagrant-Libvirt.box 73757f50ef9cdac2e3ba6d88a216cca23000a32fa96891902feaa86d49147e3f CentOS-Atomic-Host-7.1704-Vagrant-VirtualBox.box 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! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and 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

[storage] Ceph Jewel 10.2.7 now tagged for -testing
by David Moreau Simard 11 May '17

11 May '17

Hi, Please take note that Ceph Jewel 10.2.7 has been tagged for testing after a successful smoke test of an initial build. It should land on the buildlogs CDN shortly. Ceph Jewel in the stable release repository is currently at 10.2.5 since 10.2.6 had not been built. You can find the release notes for the new versions upstream: - 10.2.6 (March 8th): http://ceph.com/releases/v10-2-6-jewel-released/ - 10.2.7 (April 10th): http://ceph.com/releases/v10-2-7-jewel-released/ The Ceph storage SIG rebuilds straight from upstream source RPMs found here [1]. We version spec file differences on GitHub [2] for information purposes only. You can test this new version with the centos-release-ceph-jewel package, like so: === yum -y install centos-release-ceph-jewel yum-config-manager --enable centos-ceph-jewel-test yum -y install ceph === This will remain in -testing until at least April 24th, after which it will be tagged for release if no problems are reported. Thanks, [1]: http://download.ceph.com/rpm-jewel/ [2]: https://github.com/CentOS-Storage-SIG/ceph David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter]

2 5

CentOS PaaS SIG meeting (2017-05-10)
by Troy Dawson 10 May '17

10 May '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 10 May 2017 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing and Automated rpm building -- Images and Image building -- Multi-arch -- separate repo work -- minishift - Open Floor

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2017