devel

devel@lists.centos.org

5 participants
4641 discussions

CentOS-7 / ppc64le System Architectures
by Aaron Sullivan 13 Sep '15

13 Sep '15

This message is intended as follow-up to this thread: https://lists.centos.org/pipermail/centos-devel/2015-September/013792.html Rackspace is building a POWER8 based OpenPOWER server, in an Open Compute form factor. Its codename is Barreleye. Specs and target use cases are as follows: Specs: * CPU / Memory o 2 sockets o 32 DIMM slots o 8 Centaurs * IO o 2 x8 OCP Mezzanine slots o 1 x16 FHFL PCI-E slot o 1 x8 HHFL PCI-E slot o 1 x8 HHHL PCI-E slot * Storage o Systems are currently using LSI / Avago 3108 ROCs (9361-8i), but could support other ROCs o LSI / Avago SAS Expander o 15 x2.5" hot swap drives o 1 internal M.2 SATA card slot * BMC o AST2400 Chip, with internal development targeting OpenBMC ? More here: http://www.datacenterknowledge.com/archives/2015/08/14/facebooks-openbmc-ca… -- there's similar, collaborative work going on for Barreleye. There's a picture of a Barreleye rack, at Rackspace, here: https://twitter.com/Calista_Redmond/status/636367178355245056/photo/1 Use cases: * OpenStack with KVM (for an IaaS platform) * Container Platform (LXC, Docker, etc) * Bare metal host for popular applications like LAMP, Nginx, Wordpress, Go environments, and so forth * Big data apps starting with Mongo, but also including Cassandra, Redis, Hadoop, and Spark * CAPI accelerator environments We believe demand for POWER-based CentOS will be similar to our x86 demand (which is to say, significant). We hope to see it get to launch-grade quality for at least virtual machines, if not bare metal, over the next few months. --Aaron [outlook-signature-distinguished]

3 4

cloud-init - [PATCH] Add power-state-change to cloud_final_modules list
by Sebastiaan Glazenborg 11 Sep '15

11 Sep '15

According to this page: https://wiki.centos.org/Sources, at the end of that page under "Contributing code to existing Git repos" I read that I am supposed to email the centos-devel mailing list with my git patch file as an attachment... I hope this works :) 1 attachment: Add-power-state-change-to-cloud_final_modules-list.patch

2 3

Problem creating CentOS cloud image, selinux bug with cloud-init?
by Sebastiaan Glazenborg 11 Sep '15

11 Sep '15

Hello, I am trying to build my own CentOS cloud image, one reason is to better understand this process and learn from it, but am having troubles completing a fully functional image. I have read various how-to and other documentation but I keep running in to the same issue, maybe a bug? Very interested in how the CentOS cloud images were created and if the people building these ran in to the same issue. I am following these few steps: 1. create new CentOS 7 installation using virt-install and a kickstart to create base_image. nothing special is done, just using the CentOS 7 iso contents to do a minimal install + cloud-init 2. run virt-sysprep on this created base_image 3. create new kvm vm using a copy of the sysprepped disk file Because I do this all locally on my laptop I am using a config-drive iso that cloud-init is using to read meta-data and user-data files. The newly created vm is booted up, console connected, and the arrives at the prompt without having completed the various cloud-init steps. <snip boot messages> [ 6.683676] ip_tables: (C) 2000-2006 Netfilter Core Team [ 6.823284] nf_conntrack version 0.5.0 (7947 buckets, 31788 max) [ 6.885987] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 7.076775] Ebtables v2.0 registered [ 7.099351] Bridge firewalling registered cloud-init[576]: Cloud-init v. 0.7.5 running 'init-local' at Fri, 11 Sep 2015 20:02:31 +0000. Up 7.13 seconds. CentOS Linux 7 (Core) Kernel 3.10.0-229.el7.x86_64 on an x86_64 localhost login: And then nothing.. investigating [root@localhost ~]# systemctl status cloud-init-local.service -l cloud-init-local.service - Initial cloud-init job (pre-networking) Loaded: loaded (/usr/lib/systemd/system/cloud-init-local.service; enabled) Active: activating (start) since Fri 2015-09-11 22:18:45 CEST; 41s ago Main PID: 583 (cloud-init) CGroup: /system.slice/cloud-init-local.service ├─ 583 /usr/bin/python /usr/bin/cloud-init init --local ├─ 879 tee -a /var/log/cloud-init-output.log ├─1114 /bin/bash /etc/sysconfig/network-scripts/ifup-eth ifcfg-eth0 └─4433 /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0 Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Writing to /etc/sysconfig/network-scripts/ifcfg-eth0 - wb: [420] 253 bytes Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /etc/sysconfig/network-scripts/ifcfg-eth0 (recursive=False) Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /etc/sysconfig/network-scripts/ifcfg-eth0 (recursive=False) Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Reading from /etc/sysconfig/network (quiet=False) Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Read 37 bytes from /etc/sysconfig/network Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Writing to /etc/sysconfig/network - wb: [420] 52 bytes Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /etc/sysconfig/network (recursive=False) Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Restoring selinux mode for /etc/sysconfig/network (recursive=False) Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] __init__.py[DEBUG]: Attempting to run bring up interface eth0 using command ['ifup', 'eth0'] Sep 11 22:18:47 localhost.localdomain cloud-init[583]: [CLOUDINIT] util.py[DEBUG]: Running command ['ifup', 'eth0'] with allowed return codes [0] (shell=False, capture=True) [root@localhost ~]# grep denied /var/log/audit/audit.log type=USER_AVC msg=audit(1442002754.912:331): pid=589 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc: denied { send_msg } for msgtype=method_return dest=:1.4 spid=578 tpid=4433 scontext=system_u:system_r:firewalld_t:s0 tcontext=system_u:system_r:cloud_init_t:s0 tclass=dbus exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?' [root@localhost ~]# audit2allow -a -M test module test 1.0; require { type cloud_init_t; type firewalld_t; class dbus send_msg; } #============= firewalld_t ============== allow firewalld_t cloud_init_t:dbus send_msg; Now with SElinux disabled everything works fine; but thats not really something I prefer to do outside of initial testing. Googling: 'Running command ['ifup', 'eth0'] with allowed return codes [0] (shell=False, capture=True)' returned this: https://bugzilla.redhat.com/show_bug.cgi?id=1126096 But that bug report is now 1 year old... Either I am doing something wrong or other people have run in to this same issue no?

1 0

Re: [CentOS-devel] CentOS-7 / powerpc BE bring up
by Lance Albertson 11 Sep '15

11 Sep '15

[I just subscribed to the list, so bare with me and sorry for the top post] I have a lot of interest in getting CentOS ppc64le going for here at the lab. For now I'd prefer having LE over BE as that is where most of the arch seems to be going. If there's anything I can do to help with this process, please let me know. I've had a lot of experience in the past several years with this architecture on Fedora. Thanks! <snip> > does this work for everyone involved here ? What's the outlook for > getting LE VMs so that the this started as well. I'm getting lots of pressure > for LE CentOS from customers, partners, and clients. Perhaps we can get folks who have shown interest in having Power on CentOS to post their preferred architecture here? -- Lance Albertson Director Oregon State University | Open Source Lab

1 0

CentOS 7 on power64 status
by James O'Connor 11 Sep '15

11 Sep '15

Just an email to summarize where we stand with CentOS 7 ppc64le (Little Endian) and ppc64 (Big Endian). We don’t have an official CentOS power64 SIG yet but I am interested in enlisting further community participation and testing when the time is appropriate. I have working proof of concept builds of c7-ppc64le and c7-ppc64. Both ports were done using Fedora 22 based PowerKVM guests. The LE port was done cleanly and involved developing a c7 based Linux From Scratch toolchain to get around a thorny issue with glibc-2.20 in Fedora 21 LE but glibc-2.17 in CentOS 7. This issue further prevents the use of Fedora 21 LE rpms because they all require GLIBC_2.18 and c7 provides GLIBC_2.17. The BE port is much more straightforward as Fedora 19 ppc64/ppc rpms are used to bootstrap the initial CentOS 7 ppc64/ppc rpms. As of yesterday we have IBM POWER8 systems up and running PowerKVM in the CentOS datacenter. Similar development and test systems are available at http://osuosl.org/ Work is underway to get Fedora ppc64le and ppc64 builders up and running and replicate the proof of concept builds. Stay tuned to the centos-devel email list or drop by #centos-ppc on irc.freenode.net to say hello.

2 1

Announcing a New CentOS Atomic Host Release
by Jason Brooks 10 Sep '15

10 Sep '15

Today we’re releasing a significant update to the CentOS Atomic Host (version 7.20150908), 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, as an installable ISO image, as a qcow2 image, or as an Amazon Machine Image. These images are available for download at http://cloud.centos.org/centos/7/atomic/images/. The backing ostree repo is published to http://mirror.centos.org/centos/7/atomic/x86_64/repo. Currently, the CentOS Atomic Host includes these core component versions: - kernel 3.10.0-229 - docker 1.7.1-108 - kubernetes 1.0.0-0.8.gitb2dafda - etcd 2.0.13-2 - flannel 0.2.0-10 - cloud-init 0.7.5-10 - ostree 2015.6-4 - atomic 1.0-108 Upgrading --------- If you’re running the version of CentOS Atomic Host that shipped in June, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade If you’re currently run the older, test version of the CentOS Atomic Host, or if you’re running any other atomic host (from any distro or release in the past), you can rebase to this released CentOS Atomic Host by running the following two commands : $ sudo ostree remote add centos-atomic-host \ http://mirror.centos.org/centos/7/atomic/x86_64/repo $ sudo rpm-ostree rebase \ centos-atomic-host:centos-atomic-host/7/x86_64/standard Images ------ ### Vagrant CentOS-Atomic-Host-7-Vagrant-Libvirt.box (393 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (404 MB) 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 (682 MB) can be used via regular install methods (PXE, CD, USB image, etc.) and uses the Anaconda installer to deliver the CentOS Atomic Host. This allows flexibility to control the install using kickstarts and define custom storage, networking and user accounts. This is the recommended process for getting CentOS Atomic Host onto bare metal machines, or to generate your own image sets for custom environments. ### QCOW2 The CentOS-Atomic-Host-7-GenericCloud.qcow2 (922 MB) 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 (http://www.projectatomic.io/blog/2014/10/getting-started-with-cloud-init/) NoCloud iso image. The Generic Cloud image is also available compressed in gz (389 MB) and xz compressed (303 MB) formats. ### Amazon Machine Images Region Image ID ------ -------- sa-east-1 ami-47ed785a ap-northeast-1 ami-3458d234 ap-southeast-2 ami-05511e3f us-west-2 ami-a5b6ab95 ap-southeast-1 ami-dc99938e eu-central-1 ami-8c111191 eu-west-1 ami-0b6e4d7c us-west-1 ami-69679d2d us-east-1 ami-69c3aa0c ### SHA Sums a132d59732e758012029a646c466227f4ecf0c71cc42f0a10d3672908e463c0c CentOS-Atomic-Host-7.20150908-GenericCloud.qcow2 aad5d39e0683dc997f34902b068c7373aac3f7dc9b2c962a6ac0fe7394e2aa58 CentOS-Atomic-Host-7.20150908-GenericCloud.qcow2.gz c8432175a012e7f13b7005fe9c1fe43e03e47ca433db8230ab6d5d1831d2cbe0 CentOS-Atomic-Host-7.20150908-GenericCloud.qcow2.xz b222702942d02da2204581de6f877cf93289459a99f9080e29016e3b90328098 CentOS-Atomic-Host-7.20150908-Installer.iso 5531fa99429b38c6e6c4aca87672bd5990ab90f6445cc0e55c9121ad62229141 CentOS-Atomic-Host-7.20150908-Vagrant-Libvirt.box bdcf58772117dd3a84100e5902f4f345daeea7c04f057c0ab6e29bfef3c82eab CentOS-Atomic-Host-7.20150908-Vagrant-Virtualbox.box Release Cycle ------------- The rebuild image will follow the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they’ll be rebuild and included in new images. After the images are tested by the SIG and deemed ready, they’ll be announced. If you’d like to help with the process, there’s plenty to do! Getting Involved ---------------- CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream work from Project Atomic (http://www.projectatomic.io/) If you’d like to work on testing images, help with packaging, documentation, or even help define the direction of our releases — 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 (https://lists.projectatomic.io/mailman/listinfo/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 (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic mailing list (https://lists.projectatomic.io/mailman/listinfo/atomic) or find us in the #atomic channel on Freenode.

1 0

Atomic SIG: Joint Test Day with Fedora Atomic Folks
by Dusty Mabe 10 Sep '15

10 Sep '15

Hi All, There has been some discussion of doing a joint test day with Fedora and CentOS atomic folks. Fedora is having a test day for Fedora Cloud base on 9/8 (all are welcome to join us). We were thinking about having the joint Fedora/CentOS test day on the following Tuesday (9/15). Is this something everyone is interested in? To do the test day it would be worth having a test day page like [1] and some test cases for people to execute. These test cases can probably overlap with the one's fedora has. Dusty [1] - https://fedoraproject.org/wiki/Test_Day:2015-05-07_Atomic

1 1

Re: [CentOS-devel] [proposal] Joint meetings between upstream Atomic/Fedora Cloud WG
by Joe Brockmeier 09 Sep '15

09 Sep '15

On 09/09/2015 02:02 PM, Haïkel wrote: > So I suggest that every two weeks, we hold joint meetings as in merging > our weekly meetings not adding a new one. This will enable us to work > together more efficiently. > > Your thoughts? So - we don't do separate Project Atomic meetings - there's the CentOS SIG meeting and Fedora Cloud. I'm amenable to doing just one joint meeting or finding some way to merge them, though. Also cc'ing the CentOS devel list. -- Joe Brockmeier | Community Team, OSAS jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

CentOS Firewall and UTM SIG
by Jim Joomla 08 Sep '15

08 Sep '15

1 0

Possible Corrupt Centos 7 Cloud Image
by Neil Wilson 03 Sep '15

03 Sep '15

Hi, I’ve had complaints from customers that the compressed qcow image on cloud images for CentOS 7 is corrupt - failing with an XFS panic. CentOS-7-x86_64-GenericCloud-20150628_01.qcow2c The raw and the uncompressed qcow2 image appear fine. If I compress the raw image to a qcow2c with qemu-img convert -p -c -O qcow2 CentOS-7-x86_64-GenericCloud-20150628_01.raw CentOS-7-x86_64-GenericCloud-20150628_01.qcow2c then I get the same size as the downloaded file but with binary differences. Could somebody take a look? Rgs Neil Wilson

2 1

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