hi,
the CentOS Atomic Host repo is now getting nightly updates. These are
done automatically, and pushed to the repo location on
buildlogs.centos.org/centos/7/atomic/x86_64/repo
In order to apply the updates, login to your atomic host and run :
sudo rpm-ostree upgrade
You can also see the Atomic history and rollback options via:
sudo atomic status
In order to compare available rollback options, you can use the 'atomic
rpm diff' and 'atomic rpm list' commands.
Finally, you can rollback the changes using this atomic command; details
on the process are mentioned in the man page available via 'man atomic'
on the machine instance.
-------
The repo is updated with all devel components going into the Atomic
host, including docker, cockpit, flannel, kubernetes and rpm-ostree
itself. Additionally, all CentOS Linux 7 updates are included as well.
Highlights from todays update include:
cockpit 0.27
docker 1.4
kubernetes 0.7.0
ostree 2014.13
kernel 3.10.0-123.13.2.el7
and added to the collect is :
flannel 0.1.0
--------
Getting Started with CentOS Atomic Host is easy, the image is shipped as
a qcow2.xz file ( 270MB in size ) and can be downloaded from
http://buildlogs.centos.org/rolling/7/isos/x86_64/CentOS-7-x86_64-AtomicHos…
this image includes cloud-init, and therefore expects cloud metadata to
be available when the instance is booted up. You can find details on
howto setup an iso file with this informat at :
http://www.projectatomic.io/blog/2014/10/getting-started-with-cloud-init/
Enjoy!
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
===============================
#centos-devel: CentOS Cloud SIG
===============================
Meeting started by kushal at 15:02:20 UTC. The full logs are available
at centos-devel/2015/centos-devel.2015-01-15-15.02.log.html .
Meeting summary
---------------
* Last meeting's action items. (kushal, 15:05:15)
* tstclair thinks mesos may be a better fit for EPEL. (kushal,
15:08:19)
* ACTION: rbowen will write to the RDO community about helping us on
Juno on EL6 and for future releases. (kushal, 15:22:24)
* LINK:
https://www.redhat.com/archives/rdo-list/2015-January/msg00066.html
<-- there it is. (rbowen, 15:22:26)
* LINK: https://www.redhat.com/mailman/listinfo/rdo-list (kushal,
15:25:49)
* ACTION: kbsingh will find some box for number80 for a RDO install
(kushal, 15:32:01)
* ACTION: number80 will do the RDO install on that box (number80,
15:32:22)
Meeting ended at 15:42:26 UTC.
Action Items
------------
* rbowen will write to the RDO community about helping us on Juno on EL6
and for future releases.
* kbsingh will find some box for number80 for a RDO install
* number80 will do the RDO install on that box
Action Items, by person
-----------------------
* kbsingh
* kbsingh will find some box for number80 for a RDO install
* number80
* kbsingh will find some box for number80 for a RDO install
* number80 will do the RDO install on that box
* rbowen
* rbowen will write to the RDO community about helping us on Juno on
EL6 and for future releases.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* kushal (55)
* kbsingh (38)
* rbowen (25)
* number80 (16)
* centbot (2)
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
Hello,
Earlier today I tried to build the SCST source RPM via the CentOS
Community Build System (CBS). The first attempt failed because kernel
headers under /lib/modules/%{kver} were missing. So I added
"BuildRequires: kernel-devel" in the SCST spec. However, this caused the
build server to install the kernel-debug-devel RPM instead of the
kernel-devel RPM (see also
https://cbs.centos.org/koji/taskinfo?taskID=6041 for the logs). Does
anyone know whether I am doing something wrong or whether this is an
issue with the build system ?
An attempt to build against the bananas6-el6 target also failed. In the
logs generated for this target I found the following:
http://mirror.rdu2.centos.org/centos/6/os/x86_64/Packages/audit-libs-2.2-2.…:
[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not
Found". See also https://cbs.centos.org/koji/taskinfo?taskID=6043. Is
this error message expected ?
Is this the right mailing list for such questions ?
Thanks,
Bart.
Hello all,
Thanks to Thomas' (alphacc) work last Friday, we now have the image
building features enable on the CBS koji instance. I'll give a very
brief summary of how to use it. The general form of the koji command is:
koji -p cbs image-build <image_name> <image_version> <build_target>
<install_tree_url> <arch>
--release <image_release>
--distro <distro_name_version>
--kickstart <local_kickstart_file>
--format <format_type>
--disk-size <disk_size_in_gb>
--repo <repo_url> (optional)
--scratch (optional)
--nowait (optional)
The image build must be given a name, version and release. These
function in much the same way as they do in RPM. In particular, the
name must be added as an allowed package in the output tag for the
<build_target> provided on the command line.
You can specify more than one --format option. The most useful options are:
'raw-xz' - xz compressed raw file
'qcow2' - qcow2
'rhevm-ova' - A single file OVF image (aka OVA) for RHEV-M
'vsphere-ova' - An OVA for vSphere/VMWare
'docker' - A docker base image, suitable for "docker load"
Any "url" or "repo" lines in your input kickstart file will be removed.
The "url" line is replaced by whatever <install_tree_url> you give
above. You can, optionally, provide additional repos to Anaconda by
giving one or more "--repo <url>" arguments.
Until we sort out how exactly we want kickstart files store in RCM
(likely git.centos.org) we will be restricted to doing scratch builds,
indicated with a "--scratch" option above.
Here is the exact command I used to do initial testing of the feature:
koji image-build \
centos-7-imcleod-test 1 atomic7-el7.centos \
http://mirror.centos.org/centos/7/os/x86_64/ x86_64 \
--release=1 \
--distro RHEL-7.0 \
--kickstart=/tmp/RHEL7.auto \
--format=qcow2 \
--scratch \
--nowait \
--disk-size=10
The "RHEL7.auto" kickstart is the minimal/JEOS RHEL7 kickstart from Oz,
available here:
https://raw.githubusercontent.com/clalancette/oz/master/oz/auto/RHEL7.auto
In order for this to work I had to ask alphacc to add me to the "image"
permission in the CBS.
I then had to add the centos-7-imcleod-test "package" to the
"atomic7-testing" tag (which is the destination for the
"atomic7-el7.centos" build target). The command to do this was:
koji add-pkg --owner=imcleod atomic7-testing centos-7-imcleod-test
Please follow up with questions, thoughts, RFEs, etc.
-Ian
Meeting minutes from last week's meeting. Note that our meeting has been
moved to Thursdays at 15:30 UTC.
Meeting started by jzb at 14:33:48 UTC. The full logs are available at
http://centos.org/minutes/2015/january/centos-devel.2015-01-06-14.33.log.ht….
Meeting summary
---------------
* ACTION: imcleod discuss building Vagrant boxes / add Vagrant building
feature (jzb, 14:36:41)
* "Fleet" features (jzb, 14:43:49)
* ACTION: walters to carry discussion on tools / Ansible to lists
(jzb, 15:19:44)
* open floor (jzb, 15:20:05)
Meeting ended at 15:27:36 UTC.
Action Items
------------
* imcleod discuss building Vagrant boxes / add Vagrant building feature
* walters to carry discussion on tools / Ansible to lists
Action Items, by person
-----------------------
* imcleod
* imcleod discuss building Vagrant boxes / add Vagrant building
feature
* walters
* walters to carry discussion on tools / Ansible to lists
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jzb (80)
* nzwulfin (43)
* kbsingh (18)
* walters (18)
* imcleod (8)
* centbot (4)
* Evolution (3)
* lalatenduM (2)
* jbrooks (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
Hi all,
Tuesdays have become an increasingly bad day for meetings for many of
the folks working with the CentOS Atomic SIG.
Starting this week, I'm moving the IRC meeting to Thursday at 15:30 UTC.
It will still be held in #centos-devel.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
Hi,
After installing a service on centos 7 the shutdown/reboot takes 5 minutes.
I would like to debug the shutdown process and see where it hangs. Where
could I find the log files of the shutdown process?
-sgb