Hi all,
The oVirt project is looking at using some of the tools worked on by
the OpsTools SIG.
More details can be found at [1].
We are currently looking at ElasticSearch and Logstash, and at Kibana
and Grafana.
This effort is lead by Shirly Radco, our BI engineer. I am a member of
the integration-development team, and can try helping with packaging
etc. I'll have a look at the current status of packaging of these
tools and might send more emails with specific questions/issues as
needed.
[1] http://www.ovirt.org/develop/release-management/features/engine/metrics-sto…
Best regards,
--
Didi
In working with the fluentd packaging from the opstools sig, I think
we need to make at least two changes:
- For type=tail sources, fluentd really wants a pos_file parameter to
track the file position. It would be helpful if we created
/run/fluentd via /etc/tmpfiles.d as a common location for storing
these files.
- I think that the *_secure_forward plugins (which permit using ssl
for communication between a fluentd client and a collector) are
going to be a necessity for just about everybody, so these should
probably be packaged in manner similar to the elasticsearch plugin.
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
Are there any plans for enabling single-sign-on between the different
centos.org subdomains? Perhaps at least between accounts and bugs, if
not also cbs or others?
I remember seeing how SSO can work seamlessly in a big company - the
Windows login and a client cert enabled access to pretty much
everything, from web apps like HR, to different servers, even unlocking
the LAN port you were connected to. This is highly practical when it
works. Then again, I was in R&D (not in IT, which had to configure the
whole thing). :)
Regards,
Laurențiu
Hi,
I'm working on openstack/puppet-ceph module to deploy Ceph Jewel for
OpenStack TripleO and Red Hat Director (OpenStack installers).
I'm very interested to know when I'll be able to download Jewel
packages from SIG on x84_64:
buildlogs.centos.org/centos/7/storage/x86_64/ceph-jewel/ currently
does not contain Ceph packages.
Using ceph.com repositories for us is not optimal as we try to use a
maximum of CentOS supported repositories, like we do for OpenStack.
Thanks,
--
Emilien Macchi
We occasionaly get complaints from users that our official Vagrant
images do not include the VirtualBox Guest Additions. We do not include
them because the CentOS repositories do not have any package for
VirtualBox. Packaging it would probably require a significant amount of
work - the Debian source package shows quite a number of first-level
dependencies, probably not all already available in CentOS. [1] I'm
also not sure if packaging the full VirtualBox is even desirable. [2]
The alternative would be to package just the Guest Additions (which have
considerably fewer build dependencies), to be able to include them in
the Vagrant images. Two VirtualBox developers told me in #vbox-devel
that the source code already supports building just the Guest Additions,
and it's actually used for generating the official download images: one
should simply invoke "kmk VBOX_ONLY_ADDITIONS=1", or, I quote: 'kmk
VBOX_ONLY_ADDITIONS=1 packing to produce the ISO, which will only be for
one platform and bit count.' They also believe we should be able to get
away with simply providing the binary modules, since our kernels have a
stable ABI (the upstream Guest Additions ISO, as well as the Debian
packages, require DKMS and the development tools and kernel headers,
which would considerably increase the size of our Vagrant images). We
would probably need to incorporate some functionality from their
installer at RPM build time, to get just the binary modules.
Regards,
Laurențiu
[1] https://packages.debian.org/sid/virtualbox
[2] https://lkml.org/lkml/2011/10/6/317
Hello Folks,
Please note that next week on Monday cbs.centos.org will be upgraded to
support newer features.
What does that mean for you ?
Next Monday, we will upgrade imagefactory to latest version.
The change is scheduled to be implemented on Monday August 22nd 7:00 am
UTC time
You can convert to local time with $(date -d '2016-08-22 7:00 UTC')
What will be the impact ?
During the update it will not be possible to build packages or images.
Please note that temporary repositories served on cbs.centos.org will be
available (Mostly used for CI).
Please let us know before Thursday August 18th if it could impact
dramatically your work/releases schedule.
--
Thomas Oulevey on behalf of the infrastructure team
A question came up on the OpenShift-Ansible issue[1], that I would
like to discuss with a broader, CentOS based community.
"With OpenShift Origin, running yum update or yum upgrade will include
any updated OpenShift packages, potentially causing issues."
With Origin 1.3 getting ready for release candidate, this is a very
valid concern.
I've already put this on the next PaaS SIG meeting agenda, but I
wouldn't mind hearing opinions before the meeting. Feel free to state
problems, worries, solutions, or overall comments by replying to this
email and/or adding to the issue.
Thank You
Troy
[1] - https://github.com/openshift/openshift-ansible/issues/2293
Security updates for the sclo-ror42 software collection, which provides
Ruby on Rails 4.2, are now available in the CentOS SCLo SIG testing
repository.
To apply the updates:
yum upgrade --enablerepo=centos-sclo-sclo-testing --nogpgcheck sclo-ror42\*
These fix:
a) CVE-2016-6316: Possible XSS Vulnerability in Action View
https://groups.google.com/forum/#!topic/ruby-security-ann/8B2iV2tPRSE
b) CVE-2016-6317: Unsafe Query Generation Risk in Active Record
https://groups.google.com/forum/#!topic/ruby-security-ann/WccgKSKiPZA
The packages updated are (both el6/7):
sclo-ror42-rubygem-actionpack-4.2.5.1-2.el7
sclo-ror42-rubygem-activerecord-4.2.5.1-3.el7
sclo-ror42-rubygem-actionview-4.2.5.1-3.el7
I'll push them to stable in a week or so's time, but would appreciate
any feedback.
--
Dominic Cleal
dominic(a)cleal.org