Next weekend, CentOS will be sponsoring Ohio LinuxFest, and will have a
table there. If you expect to be at OLF, and can spare an hour, or even
a half hour, to sit at the table and answer questions, it would be a
great help to me.
Please have a look at the schedule - https://ohiolinux.org/schedule/ -
and let me know what time(s) you might be able to spend at the table.
For your convenience, I've made a list of available times here:
https://docs.google.com/spreadsheets/d/1TqTqaLoswMYzyfvQCnzjkVazlQkP87CCKBS…
Thanks, and I hope to see some of you in Columbus.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
Hi,
Since last few months, we were working on re-architecturing the
CentOS Community Container Pipeline Service to make
https://registry.centos.org as a stable and reliable source for CentOS
based container images.
We are now done with the changes for better throughput and stability.
We are working on deploying the new service in production in coming
weekend (between 28th Sep 2018- 1st Oct 2018). During this time service
will be in maintenance mode. We will not be building new images for
registry.centos.org. Existing images will not be updated based on RPM,
or git source updates.
However, during this migration registry.centos.org will be available
to pull images from. We are trying to make sure the down time for CentOS
Community Container pipeline service is minimal.
Service: https://registry.centos.org
Maintenance window: Service will not have downtime
Impact: Users will be able to pull images from https://registry.centos.org
Service: CentOS Container Community Pipeline Service
Maintenance window: 28th Sep 2018 to 1st Oct 2018 (We are working on to
make it minimal)
Impact: PRs to https://github.com/centos/container-index will not be
merged and no image updates are pushed to registry.centos.org.
Sorry for the inconvenience, we will keep posted.
Regards
Bama Charan Kundu
The Call for Presentations for the FOSDEM Dojo -
https://wiki.centos.org/Events/Dojo/Brussels2019 - closes next weekend.
And, so far, it's looking pretty grim, with only THREE submissions.
If you anticipate being at FOSDEM, and would like to present at our
annual FOSDEM Dojo on topics relevant to CentOS or Fedora, please
consider submitting a talk: https://goo.gl/forms/XkXbC2AZBgKvfDNF2
Please see https://wiki.centos.org/Events/Dojo/Brussels2018 for some
idea of what kind of talks we had last year. But we're also asking the
Fedora community to submit talks this year.
--Rich
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166
Hello everyone,
we switched from using qemu-img from CentOS 7.x to qemu-img-ev from the
Virt SIG several months ago, to allow us to generate Hyper-V images.
My attempts to build Vagrant images are failing the automated tests
since the beginning of July, apparently due to corrupt filesystems. I
see XFS metadata corruption in the CentOS 7 images when using
qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6
images.[1]
The distro installer runs just once and the resulting disk image is
converted by Image Factory to different formats, depending on the
virtualization target. Since the VirtualBox images are working as
expected, while the libvirt images don't even boot due to filesystem
corruption, I would assume that the installation produces a valid image,
but the conversion of the disk images for libvirt-kvm fall prey to bugs
in qemu-img-ev and the stock qemu-img. If anyone has the possibility to
test with VmWare or Hyper-V, please write me off-list.
I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has
version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real,
were already fixed upstream - would it be possible to use a newer
version than what qemu-img-ev provides? We reverted to using the EL7
qemu-img, but this still produces broken libvirt images and wețd have to
drop the Hyper-V images as well.
Any help or suggestions are appreciated.
Best regards,
Laurențiu
[1] https://people.centos.org/bstinson/vagrant/c6-vagrant.png
I've begun to draft the October newsletter on blog.centos.org If your
SIG would like to report anything to the broader CentOS community,
please do let me know what you'd like to say.
Or, if you'd like to edit it yourself, please go right ahead and make
your edits directly in my draft.
If there's other content you'd like to contribute to the newsletter,
please do let me know. The centos-promo list is the best place to
discuss your newsletter ideas.
The deadline for content is end of day, October 1st.
If you've not edited anything in the blog before: Blog logins are tied
to your CentOS account. After you've logged into the blog editing
interface once - https://blog.centos.org/wp-admin - just let me know,
and I can add you to the Editors group.
Thanks!
--
Rich Bowen - rbowen(a)redhat.com
@CentOSProject // @rbowen
859 351 9166