From peers working with CentOS on Power8,
/"I am trying to install OPAL-PRD on cent-os. Do you know where to get
opal-prd package ?"/
Presently opal-prd is not available in the CentOS repos or in EPEL, but
is expected in a future release of RHEL.
In the meantime, it is possible to build the rpm from source and install
on CentOS.
Latest source rpm :
https://hegdevasant.fedorapeople.org/opal-prd/v5/opal-prd-5.1.13-1.fc22.src…
Thanks to Vasant Hegde for pointer to files.
hi
We have seven.centos.org which runs more or less as an announcement and
community blog - but the word 'seven' in there highlights its focus
around CentOS Linux 7.
As we promote that, this mindset goes with it.
Am wondering if we need a better worded name for the blog, or to move it
under www.centos.org/blog/ ( yet retain the lose'ish perms for
contributors.ie. SIGs are welcome too ) ?
Regards
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Hello,
Let me briefly re-introduce my self. I work on ABRT and I was involved in the integration of ABRT with CentOS Bug Tracker.
I want to let you know that we are re-working ABRT reporting workflow in order to reduce the number of opened bug reports. Our current mission is to encourage users to open "full bug report" (i.e. issue in CentOS Bug Tracker) only if they want to participate in bug resolving process and submit anonymous crash statics [1][2] otherwise.
We are going to let users choose from reporting options similar the following ones:
* [Submit anonymous crash details] - [I do not want to participate in bug resolution process]
* [Enter new bug report] - [I want to help to fix this bug and I need to have it fixed as soon as possible]
These changes should land in CentOS 7 too.
Ideas and suggestions are more than welcome.
Best regards,
Jakub
1: https://github.com/abrt/faf/wiki/uReport
2: https://retrace.fedoraproject.org/faf/summary/?opsysreleases=71
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Last year we had mixed success with Google Summer of Code.
On one side, we had successful projects and some happy students and
satisfied mentors.
However, on the back end (often not visible to others here) we were
plagued with inefficiencies and mistakes that made the experience a
bit of a PITA all around.
The good thing is we now have a good idea of what it would take to run
a successful program:
* Keep it as a year long process, so the post-review leads right in to
planning for the next year.
* Have Admins and Mentors who are strongly engaged from early on.
* Improve the process to bring in students doing work.
Bottom line is that it's only worth doing if we do it right.
That is the consensus from many discussions I've been involved in over
the last six months or so.
So the deadline for proposing being a mentoring org is approaching
next week, and there is no way we can sanely put together a bid.
Instead, I'd like us to ponder if there is value for us, what that
value is, and get ourselves prepared for a run in the future ... if
that is what we decide makes sense.
Regards,
- - Karsten
- --
Karsten 'quaid' Wade .^\ CentOS Doer of Stuff
http://TheOpenSourceWay.org \ http://community.redhat.com
@quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAla+JhIACgkQ2ZIOBq0ODEEttACgo1P8GKi8AE5dAfePUvlC7nhd
y5EAn3L/HMzc2y1+Oy/BhSsjrTB9roT5
=CDJG
-----END PGP SIGNATURE-----
Hey all,
Discussed at a meeting a few weeks ago, but I failed to send email on
this. (And hence another good reason for the change...)
Jason Brooks has been heavily active in keeping the rebuilds going and
generally moving things forward. I proposed that he take over as chair,
and he didn't run screaming - nor did anyone else object. So, I'd like
this to be officially official, officially.
Lazy consensus rules, so unless there's a -1 from one of the members of
the SIG, this should be effective in 72 hours.
Apologies again for tardiness in sending this email.
Best,
jzb
--
Joe Brockmeier | Community Team, OSAS
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
hi,
according to this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1142311
rh silently replace iputils with the same version with a fixed capabilities.
unfortunately official base centos-7 (ie. latest 7.2) docker images are
build with the wrong version, so these images should have to be rebuild
with the proper version.
currently in the official centos7 docker images:
-------------------------------------
# rpm -qi iputils
Name : iputils
Version : 20121221
Release : 7.el7
Architecture: x86_64
Install Date: Wed 23 Dec 2015 06:09:24 PM UTC
Group : System Environment/Daemons
Size : 368577
License : BSD and GPLv2+
Signature : RSA/SHA256, Wed 25 Nov 2015 02:43:41 PM UTC, Key ID
24c6a8a7f4a80eb5
Source RPM : iputils-20121221-7.el7.src.rpm
Build Date : Fri 20 Nov 2015 07:12:19 PM UTC
Build Host : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager : CentOS BuildSystem <http://bugs.centos.org>
Vendor : CentOS
URL : http://www.skbuff.net/iputils
Summary : Network monitoring tools including ping
Description :
The iputils package contains basic utilities for monitoring a network,
including ping. The ping command sends a series of ICMP protocol
ECHO_REQUEST packets to a specified network host to discover whether
the target machine is alive and receiving network traffic.
-------------------------------------
while in the centos repo:
-------------------------------------
# rpm -qi iputils
Name : iputils
Version : 20121221
Release : 7.el7
Architecture: x86_64
Install Date: Tue 15 Dec 2015 03:15:22 PM CET
Group : System Environment/Daemons
Size : 368577
License : BSD and GPLv2+
Signature : RSA/SHA256, Wed 25 Nov 2015 03:43:41 PM CET, Key ID
24c6a8a7f4a80eb5
Source RPM : iputils-20121221-7.el7.src.rpm
Build Date : Fri 20 Nov 2015 08:12:19 PM CET
Build Host : worker1.bsys.centos.org
Relocations : (not relocatable)
Packager : CentOS BuildSystem <http://bugs.centos.org>
Vendor : CentOS
URL : http://www.skbuff.net/iputils
Summary : Network monitoring tools including ping
Description :
The iputils package contains basic utilities for monitoring a network,
including ping. The ping command sends a series of ICMP protocol
ECHO_REQUEST packets to a specified network host to discover whether
the target machine is alive and receiving network traffic.
-------------------------------------
imho it's a bug! without it ping not working from any docker container
based on centos7.
--
Levente "Si vis pacem para bellum!"
An updated version of CentOS Atomic Host (version 7.20160203) is now
available for 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 7.2.
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(http://cloud.centos.org/centos/7/atomic/images/). The
backing ostree repo is published to
mirror.centos.org(http://mirror.centos.org/centos/7/atomic/x86_64/repo).
CentOS Atomic Host includes these core component versions:
* kernel-3.10.0-327.4.5.el7.x86_64
* cloud-init-0.7.5-10.el7.centos.1.x86_64
* atomic-1.6-6.gitca1e384.el7.x86_64
* kubernetes-1.0.3-0.2.gitb9a88a7.el7.x86_64
* etcd-2.1.1-2.el7.x86_64
* ostree-2015.9-2.atomic.el7.x86_64
* docker-1.8.2-10.el7.centos.x86_64
* flannel-0.5.3-8.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
(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Vagrant
-Libvirt.box) (416 MB) and CentOS-Atomic-Host-7-Vagrant-Virtualbox.box
(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Vagrant
-Virtualbox.box) (428 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
(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Install
er.iso) (737 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 allows flexibility to control the install using kickstarts and
define custom storage, networking and user accounts. This is the
recommended process for getting CentOS Atomic Host onto bare metal
machines, or to generate your own image sets for custom environments.
### QCOW2
The CentOS-Atomic-Host-7-GenericCloud.qcow2
(http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-Generic
Cloud.qcow2) (1 GB) 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(http://www.projectatomic.io/blog/2014/10/getting-started-with-cloud-init
/) NoCloud iso image.
### Amazon Machine Images
Region Image ID
------ --------
us-east-1 ami-896653e3
us-west-2 ami-1f94747f
us-west-1 ami-dae791ba
eu-west-1 ami-430aba30
eu-central-1 ami-40d6cd2c
ap-southeast-1 ami-4319d720
ap-northeast-1 ami-b54d4adb
ap-southeast-2 ami-27123544
ap-northeast-2 ami-961fd1f8
sa-east-1 ami-238d0e4f
### SHA Sums
4062ef213eed698ac8ec03b32a55dd6903721a44dc8d54a18513644f160ca7d4
CentOS-Atomic-Host-7.20160130-GenericCloud.qcow2
a7dd91736f45101e95e7d9a80c2eede9164eb0392c8c4748b08c98a42d3eda39
CentOS-Atomic-Host-7.20160130-GenericCloud.qcow2.gz
9eca81d3638e4e00fc734d7233b47a3af803237cc82e5a66b3a587552232dcdc
CentOS-Atomic-Host-7.20160130-GenericCloud.qcow2.xz
be3c1a3326c04026f37bd6b6c2fccca3a285ea40ac663230624854abeaaee135
CentOS-Atomic-Host-7.20160130-Installer.iso
90942c3599e15ae21cdc0b1682b8e0d3fa88f8db2f6fdca0ece28c2bffdbb34f
CentOS-Atomic-Host-7.20160130-Vagrant-Libvirt.box
ce674573f6d7020b3d04c51f070d7172e71b6a4316c1495c238a7eac0260cb5a
CentOS-Atomic-Host-7.20160130-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
(http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream
work from Project Atomic (http://www.projectatomic.io/) 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
(https://lists.projectatomic.io/mailman/listinfo/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
(http://lists.centos.org/mailman/listinfo/centos-devel) mailing list.
Have questions about using Atomic? See the atomic
(https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or
find us in the #atomic channel on Freenode.
---
Jason Brooks
Red Hat Open Source and Standards
@jasonbrooks | @redhatopen
http://community.redhat.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Guys,
Zeeshan has offered to look at the wider state of registries and do a
short briefing on them ( oci/docker specific as a place to start ) at
the next centos buildsystems irc meeting.
Brian: what would be the best way to host this ?
regards
- --
Karanbir Singh, Project Lead, The CentOS Project
+44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS
GnuPG Key : http://www.karan.org/publickey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWu0VjAAoJEI3Oi2Mx7xbtzq4H/36aBI4WM1Nmu73xcEzhiC7M
t3tMsPK7/N9AqckjFQFSe00mJmIVE9ibzNIxmlTzzreHzlxjaKdDaMDES26+Op3e
hOPWqsMoQ44wEJ6b7T6t7oP7pnOHo/dIdBwU+KirRfTHDKS/AcMH50GjrleqBIAm
Ff7WluJQFwIO1CXH2jLYqbYCNCDdMxG932VnOgCZU0mOSPHS7cZ4VkzvDXnPdey8
VIwZKZwXYl+MBQDqohYJcSmUobiWYeEXlBOKNu6Q9J1+lYrfnrQq6/cpW6ETtpjB
NdZfDf2bh7E1h88TpB0N93zPyel30Qkp9Pbe/uKF+fzP0jw6QdFQJLkiTSDUaW0=
=Y6hq
-----END PGP SIGNATURE-----