Re: [atomic-announce] New CentOS Atomic Host release available for download

[Jason Brooks <jbrooks redhat com>]

We had a mix-up with our EC2 images. These are the correct AMIs for
this release:


Region           Image ID
------           --------
us-east-1        ami-114f5c7b
us-west-2        ami-f0e01790
us-west-1        ami-e03e4180
eu-west-1        ami-0b8a0878
eu-central-1     ami-d8f919b7
ap-southeast-1   ami-3b598c58
ap-northeast-1   ami-1386947d
ap-southeast-2   ami-19e7c57a
ap-northeast-2   ami-49dd1527
sa-east-1        ami-c7e16fab


On Thu, Apr 7, 2016 at 8:27 AM, Jason Brooks <jbrooks redhat com> wrote:
> 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.