devel

devel@lists.centos.org

3 participants
4591 discussions

Missing GlusterFS in 32-bit
by Zdenek Sedlak 20 Apr '17

20 Apr '17

Hi, do you know why gluster* packages are excluded in i386 as mentioned here: http://people.centos.org/hughesjr/missing-actual-i686-filenames.txt //Zdenek

3 4

CentOS PaaS SIG meeting (2017-04-19)
by Troy Dawson 19 Apr '17

19 Apr '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 19 April 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 0

[Cloud SIG] RDO contributor survey
by Rich Bowen 12 Apr '17

12 Apr '17

If you have participated in the RDO project, please consider filling out our contributor survey - https://goo.gl/forms/SYVo9gbacsMfe8Ov2 - as we try to improve the contributor experience. The survey should take about 10 minutes. -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

New CentOS Atomic Host with Updated Kubernetes, Etcd and Flannel
by Jason Brooks 12 Apr '17

12 Apr '17

An updated version of CentOS Atomic Host (tree version 7.20170405), is now available[1], including significant updates to kubernetes (version 1.5.2), etcd (version 3.1) and flannel (version 0.7). [1] 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-11.el7.centos.x86_64 - etcd-3.1.0-2.el7.x86_64 - flannel-0.7.0-1.el7.x86_64 - kernel-3.10.0-514.10.2.el7.x86_64 - kubernetes-node-1.5.2-0.2.gitc55cf2b.el7.x86_64 - ostree-2017.1-3.atomic.el7.x86_64 - rpm-ostree-client-2017.1-6.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[2]. 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. [2] 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. 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 ---------------- -------------- us-east-1 ami-a50d85b3 ap-south-1 ami-13f6857c eu-west-2 ami-42233726 eu-west-1 ami-49063c2f ap-northeast-2 ami-d1c81abf ap-northeast-1 ami-7b1c3e1c sa-east-1 ami-914f2dfd ca-central-1 ami-2de75b49 ap-southeast-1 ami-53328c30 ap-southeast-2 ami-6d929c0e eu-central-1 ami-dca270b3 us-east-2 ami-18bc987d us-west-1 ami-b22a0fd2 us-west-2 ami-2e2bbb4e SHA Sums b337bc56a71b6b25237a5c0c06c9f48a33973b4e41c648288bcfaf5a494af98c CentOS-Atomic-Host-7.1703-GenericCloud.qcow2 707db9907a850816fca7782da1dca3584fa0d8be821d0ee95525b688aaa0cc6d CentOS-Atomic-Host-7.1703-GenericCloud.qcow2.gz c4ef91cc801777e214106522f848f8b388fb92699d67ed4fe86cc942a361f7a2 CentOS-Atomic-Host-7.1703-GenericCloud.qcow2.xz 5e41a0306a8c1c212117c68eae10f0f59b25cb6c57dec9629bf3ac760bca54bc CentOS-Atomic-Host-7.1703-Installer.iso f509eb482a614d2eb047009aaa6c37c125b66cdd483e7015983cae5f72d9f041 CentOS-Atomic-Host-7.1703-Vagrant-Libvirt.box 2c0ba7dda2f4f249aa6c31cfcb36df1a17913b9d8786afb7b340a24b15b404f1 CentOS-Atomic-Host-7.1703-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

[Meeting] RDO meeting (2017-04-12) Minutes
by Chandan kumar 12 Apr '17

12 Apr '17

============================== #rdo: RDO meeting - 2017-04-12 ============================== Meeting started by chandankumar at 15:02:17 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_04_12/2017/rdo_m… . Meeting summary --------------- * rollcall (chandankumar, 15:02:26) * pike Milestone 1 test days (chandankumar, 15:05:45) * LINK: https://www.rdoproject.org/testday/tests/ (rbowen, 15:08:40) * python-tempestconf (chandankumar, 15:13:23) * LINK: https://github.com/redhat-openstack/python-tempestconf/tree/1.1.0 (chandankumar, 15:14:22) * rdoinfo parser from rdoinfo/rdopkg into a separate module (chandankumar, 15:16:54) * rdoinfo data format is stable enough, it's time to release rdoinfo parser as a proper module (jruzicka, 15:17:23) * ACTION: jruzicka will merge rdoinfo parser and rdopkg.actionmods.rdoinfo into a separate module (jruzicka, 15:18:05) * Contributor survey (chandankumar, 15:23:12) * Mitaka EOL (chandankumar, 15:27:07) * ACTION: apevec to draft Mitaka EOL annoucement for Cloud SIG repos (apevec, 15:34:08) * TryStack FreeIPA (leanderthal, 15:34:44) * ACTION: leanderthal email rdo-list re: trystack freeipa (leanderthal, 15:52:14) * chair for next meeting (chandankumar, 15:52:58) * ACTION: trown to chair for next meeting. (chandankumar, 15:55:26) * Open Floor (chandankumar, 15:55:41) Meeting ended at 16:01:35 UTC. Action items, by person ----------------------- * apevec * apevec to draft Mitaka EOL annoucement for Cloud SIG repos * jruzicka * jruzicka will merge rdoinfo parser and rdopkg.actionmods.rdoinfo into a separate module * leanderthal * leanderthal email rdo-list re: trystack freeipa * trown * trown to chair for next meeting. People present (lines said) --------------------------- * chandankumar (80) * rbowen (39) * leanderthal (30) * apevec (27) * wfoster (12) * openstack (11) * jruzicka (10) * trown (6) * dmsimard (6) * rdogerrit (2) * alphacc (1) * number80 (1) * DrBacchus (1) Generated by `MeetBot`_ 0.1.4

1 0

CentOS PaaS SIG meeting (2017-04-12)
by Troy Dawson 12 Apr '17

12 Apr '17

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 12 April 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

Updated sclo-php* packages available for testing
by Remi Collet 10 Apr '17

10 Apr '17

As, new RHSCL 2.4beta is available for testing, and as point release can be used for new features, a set of php extensions have been updated and pushed to testing repository: For rh-php56: * sclo-php56-php-pecl-http-2.6.0-1.el6 * sclo-php56-php-pecl-mongodb-1.2.8-1.el6 For rh-php70: * sclo-php70-php-pecl-http-3.1.0-1.el6 * sclo-php70-php-pecl-mongodb-1.2.8-1.el6 * sclo-php70-php-pecl-xdebug-2.5.1-1.el6 I plan to push to stable only when RHSCL 2.4 will be GA. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

I would like to help with CentOS/EPEL i686
by Zdenek Sedlak 10 Apr '17

10 Apr '17

Hi, I have an interest to keep some i686 hardware running with CentOS 7 installed. However there are some packages in EPEL I need so I am willing to help with maintaning/building the i686 packages for both CentOS and EPEL. Could you point me what I can do to join the effort? Thanks //Zdenek

2 3

how to use livecd-creator to create my own livecd iso which is same as offical release iso？
by wqlxx007＠gmail.com 10 Apr '17

10 Apr '17

Hi Fabian >Just to be sure : are you using livecd-tools-21.4-2.el7.x86_64 (and >corresponding python-imgcreate) packages that are on >http://mirror.centos.org/centos/7/extras/x86_64/Packages/ and so on a >CentOS 7 node to build your livecd ? I use CentOS-7-x86_64-Minimal-1511.iso to install the system on my pc. I have check the version of livecd-creator is 21.4, and release number is 2.el7 >Also, that ks file isn't updated as only LiveGnome/LiveKDE are >maintained so maybe compare with the other ks files located on >https://git.centos.org/tree/sig-core!livemedia.git/4c99f5ea4fa3399f533cd223… >(for example that old ks still points to outdated and non existing >repositories) As you say, the centos-7-livecd.cfg is out of date. I try the centos-7-live-gnome.cfg, the command is: livecd-creator -v --config=centos-7-live-gnome.cfg --fslabel=centos-7-live-gnome --cache=/var/cache/live but finally the ISO which i build with centos-7-live-gnome.cfg is also the same structure like: centos-7-live-gnome.iso |+++EFI |+++BOOT |+++fonts |+++BOOTX64.EFI |+++grub.cfg |+++grubx64.cfg |+++isolinux |+++boot.cat |+++initrd0.img |+++vmlinuz0 .... |+++LiveOS |+++osmin.img |+++squashfs.img I guess the maybe the different of config file for livecd-tools cause the different ISO. Would you please provide the Kickstart config file which used to build CentOS-7-x86_64-Minimal-1511.iso or other version of offical distro iso. Best Regards Qiang Wang

2 1

Re: [CentOS-devel] how to use livecd-creator to create my own
by wqlxx007＠gmail.com 10 Apr '17

10 Apr '17

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