devel

devel@lists.centos.org

2 participants
4653 discussions

New CentOS Atomic Host release available for download
by Jason Brooks 12 Apr '16

12 Apr '16

An updated version of CentOS Atomic Host (version 7.20160404) is now available for download[1], featuring significant updates to docker (1.9.1) and to the atomic run tool. Version 1.9 of the atomic run tool now includes support for storage backend migration, for downloading and deploying specific atomic tree versions, and for displaying process information from all containers running on a host. [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: - docker-1.9.1-25.el7.centos.x86_64 - kubernetes-1.2.0-0.9.alpha1.gitb57e8bd.el7.x86_64 - kernel-3.10.0-327.13.1.el7.x86_64 - atomic-1.9-4.gitff44c6a.el7.x86_64 - flannel-0.5.3-9.el7.x86_64 - ostree-2016.1-2.atomic.el7.x86_64 - etcd-2.2.5-1.el7.x86_64 - cloud-init-0.7.5-10.el7.centos.1.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 (414 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box (426 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 (731 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-22617648 us-west-2 ami-65659005 us-west-1 ami-68710d08 eu-west-1 ami-bb9616c8 eu-central-1 ami-f03fde9f ap-southeast-1 ami-2da6734e ap-northeast-1 ami-100f1f7e ap-southeast-2 ami-b284a7d1 ap-northeast-2 ami-7a1dd414 sa-east-1 ami-0668e76a SHA Sums 10e024927636863fd11e9a9427f9b552b6c67661f695f418b1228dda33bc6ed5 CentOS-Atomic-Host-7.1603-GenericCloud.qcow2 00a3c556e11094a996f7e688609158aa6909181d34cc767a26a43e41d39a00a2 CentOS-Atomic-Host-7.1603-GenericCloud.qcow2.gz 1ea638075f41f87751d123cc8cfe8860f6987e009b83d9692161209e2c2ce4af CentOS-Atomic-Host-7.1603-GenericCloud.qcow2.xz 9f7717da7b6813b1b7a1f87c577c8977915a8c350c36fb64b1f26dcc60bf21eb CentOS-Atomic-Host-7.1603-Installer.iso f227bcb447f3de1800faf08e453920fd739330cc942ba331467b2099026477f2 CentOS-Atomic-Host-7.1603-Vagrant-Libvirt.box bc451f55a53e1df83b7556a123a99922ffd867c35eaba2dfc6bfd8aecc748472 CentOS-Atomic-Host-7.1603-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 1

[release] Mitaka stable packaged for RDO
by Andrey Groshev 12 Apr '16

12 Apr '16

Hi ALL! Why swift 2.6.0 version? Version 2.7.0 contains significant improvements.

2 1

Config Mgmt SIG Meeting
by Ben Hosmer 12 Apr '16

12 Apr '16

Julien has asked for some help with the configuration management SIG. I'll be happy to take lead for the meeting tomorrow, 16:00 UTC. I'll be getting off a plane so I could possibly be late or delayed. I'll also volunteer to join the committee. Up for the agenda tomorrow: - SCL Prefix I'd vote for shorter, maybe '/opt/centos-cfgmgt' ? - CBS Builds I haven't had a chance to test this yet myself

2 1

RFC on PR againt CentOS Dockerfiles.
by Mohammed Zeeshan 11 Apr '16

11 Apr '16

Hi, Check out the PR https://github.com/CentOS/CentOS-Dockerfiles/pull/51 and comment on the same please. -- *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>

1 0

[done] cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 11 Apr '16

11 Apr '16

Dear All, Please note that cbs.centos.org has been upgraded successfully. Please let us know through bugs.centos.org if you find any issues/regressions. -- Thomas & Fabian

1 0

Atomic Developer Bundle 1.8.0 released
by Lalatendu Mohanty 11 Apr '16

11 Apr '16

We have released the Atomic Developer Bundle 1.8.0 through CentOS Atomic SIG. The ADB release also includes release of following ecosystem projects: * vagrant-service-manager 1.0.0 : A Vagrant plugin designed to provide an interface between ADB and the user's development environment and for easier access to the features and services provided by the ADB. * adb-utils 1.4 : A set of utility scripts and configuration files for ADB. ADB 1.8.0 release release adds new feature and several bugfixes, including: - Added fuse-sshfs to the ADB box. This adds the support for vagrant-sshfs to ADB [5]. - Enhancement to ansible playbook for Mesos Vagrantfile. adb-utils 1.4 release includes several bugfixes, including - Create OpenShift sample-project as vagrant user without $KUBECONFIG set. - Fixes to OpenShift image stream. - Changes to use new OpenShift Origin docker images i.e. tag 1.1.3. vagrant-service-manager 1.0.0 release adds several new features, including: - New sub-command `restart` for restarting services in the box - Shows correct command for exporting env variables in cygwin environment - New IP detection routine fixing IP detection for libvirt provider - Simplified help text and help option per sub-command - Plugin is backward compatible with docker 1.8.2 - Fixed defaults for configuring OpenShift service in CDK box Known issues: * Running AtomicApp in ADB fails. Refer: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/329 * Following workaround can be used till the above issue is fixed. $ sudo -E atomic run projectatomic/helloapache This release also includes many smaller changes and bugfixes, which are detailed in the release changelog from adb-utils [1], vagrant-service-manager [2] and ADB [3] Please update the ADB Vagrant box [4] and the vagrant-service-manager to 1.0.0 ($ vagrant plugin update vagrant-service-manager) and give the new ADB a spin. [1] https://github.com/projectatomic/adb-utils/releases/tag/v1.4 [2] https://github.com/projectatomic/vagrant-service-manager/releases/tag/v1.0.0 [3] https://github.com/projectatomic/adb-atomic-developer-bundle/releases/tag/v… [4] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do… [5] https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/do… _______________________________________________ Container-tools mailing list Container-tools(a)redhat.com https://www.redhat.com/mailman/listinfo/container-tools

1 0

[release] Mitaka stable packaged for RDO
by Haïkel 08 Apr '16

08 Apr '16

Hi, the RDO community has packages available for Mitaka Stable in its testing repositories. Official RDO release will be announced after we validate this release with our CI. Regards, H.

2 1

sig-configmanagement git workflow
by Julien Pivotto 07 Apr '16

07 Apr '16

Hi, here is a proposal regarding the way we could enable cooperation around the centos SIG: https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG/Git The idea is to link github to CBS and ci.c.o to provide quick and secure builds/feedback. -- (o- Julien Pivotto //\ Config Management SIG V_/_ https://frama.link/cfgmgmt

1 0

sig-configmanagement CBS tag requests
by Julien Pivotto 07 Apr '16

07 Apr '16

Hi, It is now time for sig-configmanagement member to discuss and open bug requests on bugs.centos.org about CBS tag requests. CBS: https://wiki.centos.org/HowTos/CommunityBuildSystem How to: https://wiki.centos.org/HowTos/CentosPackager Bug requests to create new tags need to be open under the buildsys category. This is the bug request I opened for Puppet and common tags: https://bugs.centos.org/view.php?id=10604 I would also like that any member plays with CBS by trying to make scratch builds to CBS. I encourage you to make scratch builds in the "bananas" tags. ! Please ask for help it anything is not clear. It would be great if as much people could test CBS before the next meeting and ask for tags. -- (o- Julien Pivotto //\ Config Management SIG V_/_ https://frama.link/cfgmgmt

1 0

sig-configmanagement SCL prefix
by Julien Pivotto 07 Apr '16

07 Apr '16

Hi all, For the Config Management SIG, we will need to rebuild some EPEL packages. However, we do not want to rebuild them 'as it' because we do not want to depend on EPEL version etc. EPEL is not always "stable" and we do not want our users to be in troubles regarding EPEL decisions (https://lists.centos.org/pipermail/centos-devel/2015-December/014101.html) Some projects use Python or Ruby librairies that we could also put in a SCL. What prefix should we use for those SCL? Some ideas: /opt/centos/ /opt/centos-sig-configmanagement /opt/centos/sig-configmanagement Thanks for your feedback. -- (o- Julien Pivotto //\ Config Management SIG V_/_ https://frama.link/cfgmgmt

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