devel

devel@lists.centos.org

4 participants
4592 discussions

[Discussion-CCCP] Pulp/crane story
by Mohammed Zeeshan 02 Mar '16

02 Mar '16

Hi, I just got off a half hour discussion with the pulp guys for the CentOS Container Pipeline registry story. 1. docker save x.tar produces a v1 tarball and not a v2 tarball 2. This tarball doesnt contain metadata such as tags and so on. 3. docker pull from docker 1.6 assumes the registry being pulled from is a v2 registry 4. v1 registry has been depricated. 5. Currently, the only way to get a v2 repo into pulp or any other registry is to first push it to docker registry and then sync our registry to it. I seriously am beginning to hate docker. -- *Mohammed Zeeshan Ahmed, * B.E Computer Science Engineering Certified IT & Cloud Architect & RHCSA +919986458839 Bengaluru, India https://mohammedzee1000.wordpress.com/ <http://mohammed-zeeshan.strikingly.com>

4 8

[Cloud SIG] Meeting Thursday, 15:00 UTC
by Rich Bowen 01 Mar '16

01 Mar '16

A reminder: We will hold our weekly CentOS Cloud SIG meeting on the #centos-devel IRC channel, on Freenode, at 15:00 UTC on Thursday. The agenda for this meeting may be found at https://etherpad.openstack.org/p/centos-cloud-sig -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Experimental systemd repo
by Lukáš Nykrýn 29 Feb '16

29 Feb '16

Hi, I am one of the maintainers of systemd in RHEL/CentOS. We have put together a repository for systemd patches we would like to see in next release of CentOS 7: https://copr.fedorainfracloud.org/coprs/lnykryn/systemd-rhel-staging/ Unpacked source code can be found at github: https://github.com/lnykryn/systemd-rhel/commits/staging To be clear, this repository is not supported by CentOS or Red Hat in any way and it should not be used on production machines. It is really just a test build and it will not correspond to any later official update. But if somebody is interested in testing, I would really appreciate any feedback. For now, there are just some minor fixes, but more will come. Please report any problems via GitHub issues or email us to lnykryn(a)redhat.com or msekleta(a)redhat.com Regards, Lukas

3 3

A short introduction
by Laurentiu Pancescu 29 Feb '16

29 Feb '16

Hello everyone, Could you perhaps use some help? My name is Laurentiu, I'm based in southwestern Germany, and I would like to help with the Vagrant images from the CentOS Cloud Instance SIG. A bit of background information: I started using Linux in 1997, with Red Hat Linux 4.2, switched to Slackware 7.0 a few years later (due to issues with gcc-2.96), then Debian from 2001 until about two years ago, when I switched to Fedora. Unfortunately, my experience with system administration is limited to workstations and running standalone (Debian) servers. I'm more of a software developer: I was a graduate teaching assistant at a University for a couple of years, followed by around 9 years in R&D for an international corporation (where I worked pretty much everywhere in code bases containing tens of millions of lines of code - I spent more than half of the time writing C++ for a couple of real-time operating systems, debugging hardware and turning on boards and ASICs, the rest being Windows development and a bit of Perl for the code generators and the release system), learning just enough system administration to get stuff done. Besides C++, I know Python, as well as some Perl and Bourne shell scripting. Best regards, Laurentiu Pancescu

1 0

Meeting minutes from last week's Cloud SIG meeting
by Kushal Das 29 Feb '16

29 Feb '16

Hi, ======================== #centos-devel: Cloud SIG ======================== Meeting started by rbowen at 15:11:07 UTC. The full logs are available at centos-devel/2016/centos-devel.2016-02-25-15.11.log.html . Meeting summary --------------- * LINK: https://etherpad.openstack.org/p/centos-cloud-sig (chandankumar, 15:13:37) * OpenStack (rbowen, 15:14:08) * Test day planned in RDO land on March 10th, 11th - https://www.rdoproject.org/blog/2016/02/rdo-mitaka-3-test-day-march-10th-11… (rbowen, 15:14:44) * LINK: https://www.youtube.com/watch?v=4O8KvC66eeU (rbowen, 15:15:46) * OpenNebula (rbowen, 15:18:04) * NFV (rbowen, 15:27:32) * Open Floor (rbowen, 15:29:18) * ACTION: Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. (rbowen, 15:31:01) Meeting ended at 15:32:42 UTC. Action Items ------------ * Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. Action Items, by person ----------------------- * **UNASSIGNED** * Kushal will head up getting blog posts out about Cloud SIG, and getting meeting logs sent to the various mailing lists. People Present (lines said) --------------------------- * rbowen (42) * kushal (25) * centbot (4) * chandankumar (3) * trown (1) * Arrfab (1) * dneary (0) * dmsimard (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

1 0

signing a vagrant box
by Karanbir Singh 29 Feb '16

29 Feb '16

hi folks, does anyone have insight into signing a vagrant box, so the origin can be confirmed ? A brief look around seems to indicate there is no such support in vagrant itself ? Surely, I must be missing something. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

New CentOS Atomic Host Images Available for Download
by Jason Brooks 26 Feb '16

26 Feb '16

An updated version of CentOS Atomic Host (version 7.20160224) is now available for download[1]. 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. [1] https://wiki.centos.org/SpecialInterestGroup/Atomic/Download 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: - kernel-3.10.0-327.10.1.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.x86_64 - atomic-1.6-6.gitca1e384.el7.x86_64 - kubernetes-1.2.0-0.6.alpha1.git8632732.el7.x86_64 - etcd-2.2.2-5.el7.x86_64 - ostree-2016.1-2.atomic.el7.x86_64 - docker-1.8.2-10.el7.centos.x86_64 - flannel-0.5.3-9.el7.x86_64 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 (421 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (435 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 (742 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 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 (1 GB) 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-e6d5e88c us-west-2 ami-3fb05d5f us-west-1 ami-fd62129d eu-west-1 ami-451ea236 eu-central-1 ami-ce8663a1 ap-southeast-1 ami-6c4c850f ap-northeast-1 ami-c74644a9 ap-southeast-2 ami-bae8ced9 ap-northeast-2 ami-5732fc39 sa-east-1 ami-059d1f69 SHA Sums d4e43826fc9f641272e589dfb8d979cd592809b34cdbdaee8b7abc9a09ff30d2 CentOS-Atomic-Host-7.1602-GenericCloud.qcow2 33bd4f732c2857c698bd00bc6db29ae2a4d7d0b768f0353d4e28a5c5ab1c999e CentOS-Atomic-Host-7.1602-GenericCloud.qcow2.gz ee9d9b4d78906ea9c33b0b87c8ad3387e997b479626e64ffedfd3f415a84cded CentOS-Atomic-Host-7.1602-GenericCloud.qcow2.xz 39a548f95022a9ab100d64dbf3579d40c66add1bc56ca938b7dba38b73c2ea87 CentOS-Atomic-Host-7.1602-Installer.iso 2f965b2a502c3839b6be84dee5ee4e60328d9f074e1494ded58b418a309df060 CentOS-Atomic-Host-7.1602-Vagrant-Libvirt.box bc976d197cac629fd68a6d8faf6bcfaeca8afd0020bf573ef343622a7ae1581b CentOS-Atomic-Host-7.1602-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

[StorageSIG] ceph on centos6
by daniel.vanderster＠cern.ch 26 Feb '16

26 Feb '16

Hi all, I've been directed here by ktdreyer in the ceph-devel irc. Today we learned that ceph hammer is no longer being built for centos6, so we won't be getting 0.94.6 or newer. AFAICT, it was dropped due to complications in their build system: https://github.com/ceph/ceph-build/commit/42c7cb3f412e9fc1f525a037f07697fc8… Would it make sense for the Storage-SIG to build hammer on centos6? Technically it should be doable -- but would you guys need some help getting this going? Eventually (client only) builds of jewel on el6 would be really nice to have, but I don't yet know if that's even possible. Cheers, Dan van der Ster CERN IT Storage Group Ceph Community "Academic Liaison"

3 2

Cloud images: what's current / release notes / hashes?
by Beni Paskin-Cherniavsky 26 Feb '16

26 Feb '16

Hi. [Follow up from https://github.com/openshift/openshift-ansible/issues/1384] I did not RTFM, this is a fresh-eyes-I-just-want-to-download-an-image perspective... Looking at http://cloud.centos.org/centos/7/images/, I see -1602 is latest version. - If for some reason I want to use the unversioned CentOS-7-x86_64-GenericCloud.* files, it's hard to be sure what I'll get (other than by downloading => I am getting 1602). - sha256sum.txt{,.asc} contain no hashes for the unversioned files. File size does suggest it's 1602. Ideally the file listing would actually show them as "name -> target" symlink, and/or downloading would return an HTTP redirect to the current version. Currently it returns the content directly, only identifying headers are `Last-Modified: Tue, 23 Feb 2016 17:53:08 GMT` and `ETag: "fcc0480-52c739f3d2900"` (for the .xz). [Be careful with redirect: some scripts/libraries by default don't follow them, e.g. any script using `curl` without `-L` would break :-(] - http://cloud.centos.org/centos/7/images/sha256sum.txt{,.asc} are not available over HTTPS. I can verify the hash but I can't trust the hash itself. That's what .asc is signed for, but lazy folks like me don't necessery know which key to trust... (`gpg --search-keys F4A80EB5` worked but then `gpg --verify` says "WARNING: This key is not certified with a trusted signature!". No idea what that means - I'm clueless with GPG; trusting https://cloud.centos.org would be trivial for me.) Looking at https://wiki.centos.org/Download: - It only links to the unversioned cloud images, doesn't say it's 1602 (other places on that page give the impression everything 7 is 1511), and doesn't list hashes. - I don't see a link to release notes for cloud images; https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 is for 1511 and only talks of the regular ISOs. https://wiki.centos.org/Cloud doesn't mention any specific versions, release notes or hashes either. Googling "centos cloud 1602" didn't lead me to any "official" announcement. Nothing on centos-announce this February. Is -1602 "officially" released? (I personally don't really care, but "what changed" is the first natural question people ask beyond "I just want the latest"...) Hope this is useful feedback.

3 4

Automated build failures on dockerhub
by Jim Perrin 25 Feb '16

25 Feb '16

Those of you using the automated build functionality of docker's hub may have been experiencing some build failures lately. It appears that docker has migrated to something using a different graph driver on the back-end or have otherwise limited the capabilities available during the build process. The result is that builds with packages like httpd will fail, because they require the cap_set_file privilege as part of the install process. There have been a few bugs filed with the Docker folks for this, but I don't know what the end result of this will be. For now, if you use the automated build framework on dockerhub, be aware that your builds may fail, and it's outside our control. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

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