devel

devel@lists.centos.org

1 participants
4605 discussions

CBS/Infra Meeting 29-Sep-2014 13:00 UTC
by Brian Stinson 06 Oct '14

06 Oct '14

Hi All, It's time for another CBS/Infra meeting: Monday 29-Sep-2014 at 13:00 UTC in #centos-devel on freenode. Agenda: #topic Greetings #topic Old Business - Status updates - Auth for git.c.o #topic New Business - Sig branch/build-target naming scheme #topic Open Floor Cheers! Brian -- Brian Stinson bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

4 4

yum-plugin-security and shellshock
by Nux! 06 Oct '14

06 Oct '14

Hello, Since Shellshock I have looked at using automated updates via yum-cron, but I only want them in case of critical issues. I expected that yum-plugin-security would at least update bash when this command was used: yum --security update-minimal Does this work on RHEL only? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

9 30

CentOS 7 Amazon AMI?
by Francisco A. Lozano 06 Oct '14

06 Oct '14

CentOS 7 was released in July and, 3 months later, there's not an AMI yet. Is it coming anytime soon - or maybe not coming at all? Is there any blocking issue for this to happen? I'm asking because someone recently said in issue tracker http://bugs.centos.org/view.php?id=6228: > (...) > In the near future we also want to migrate to CentOS 7 and am hearing there may no longer be AMIs for that. > > Could you possibly: > * Discuss possibilities for HVM and CentOS 6.5 or 7 and possible workarounds > * Discuss current thinking on AWS and CentOS 7 Francisco A. Lozano

3 4

Centos-7 32 Bit Questions
by Bob Lightfoot 03 Oct '14

03 Oct '14

Dear Johnny Hughes and others: I've spent the morning ereading thru the mailing list archives from June and July while my Centos 7 machine mock user ran a mock --init using the mock.cfg found in the 7.00.02 kernel folder. I have a server running C6 at this time that won't support 64 bit, it was built before Y2K believe it or not. I saw some reference to a git repository and the need to rebuild some packages. I've used mock a fair amount recently and would love to assiste if there is work needing done. Sincerely, Bob Lightfoot

5 4

[DISCUSS] Atomic-specific key for signing
by Joe Brockmeier 03 Oct '14

03 Oct '14

Hi all, During last week's meeting I agreed to bring this up (sorry for the delay). KB asked "do we care and how much, if at all, that the key used to sign the content is the real distro key?" (Because at the outset, it's going to be more difficult to use the distro key for Atomic host.) IMO, we don't so long as we have a SIG key that is publicized. I don't see any reason it has to be the main CentOS / distro key. Any objections/thoughts/comments? Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

2 1

Atomic SIG Meeting minutes 2014-09-30
by Joe Brockmeier 02 Oct '14

02 Oct '14

========================== #atomic: CentOS Atomic SIG ========================== Meeting started by jzb at 14:39:36 UTC. The full logs are available at http://meetbot.fedoraproject.org/atomic/2014-09-30/atomic.2014-09-30-14.39.… . Meeting summary --------------- * SIG proposal is posted on wiki page (quaid, 14:41:24) * ACTION: jzb ping SIG members on wiki access. (jzb, 14:43:02) * LINK: http://wiki.centos.org/Contribute#head-42b3d8e26400a106851a61aebe5c2cca54dd… (quaid, 14:43:14) * SIG members should ask on centos-docs as per http://wiki.centos.org/Contribute#head-42b3d8e26400a106851a61aebe5c2cca54dd… (quaid, 14:43:34) * ACTION: jzb open discussion on how Atomic should be listed in bugs.centos.org (jzb, 14:44:03) * ACTION: jzb to follow up with quaid on getting hardware for bare metal work under *centos.org (jzb, 14:55:51) * ACTION: bexelbie put out docs workflow to mailing list to see if there's any dissent/better ideads. (jzb, 15:07:43) * new business (jzb, 15:08:05) * ACTION: jzb get Atomic definition out by end of week to Project Atomic (SIG will want to review) (jzb, 15:21:00) Meeting ended at 15:23:16 UTC. Action Items ------------ * jzb ping SIG members on wiki access. * jzb open discussion on how Atomic should be listed in bugs.centos.org * jzb to follow up with quaid on getting hardware for bare metal work under *centos.org * bexelbie put out docs workflow to mailing list to see if there's any dissent/better ideads. * jzb get Atomic definition out by end of week to Project Atomic (SIG will want to review) Action Items, by person ----------------------- * bexelbie * bexelbie put out docs workflow to mailing list to see if there's any dissent/better ideads. * jzb * jzb ping SIG members on wiki access. * jzb open discussion on how Atomic should be listed in bugs.centos.org * jzb to follow up with quaid on getting hardware for bare metal work under *centos.org * jzb get Atomic definition out by end of week to Project Atomic (SIG will want to review) * quaid * jzb to follow up with quaid on getting hardware for bare metal work under *centos.org * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jzb (66) * quaid (19) * bexelbie (17) * walters (16) * jbrooks (5) * centbot (3) * zodbot (3) * scollier (0) * kbsingh (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/

1 0

Atomic SIG in bugs.centos.org
by Joe Brockmeier 02 Oct '14

02 Oct '14

Hi - I'd like to get a Atomic Instance SIG Project in bugs.centos.org (similar to Cloud Instance SIG). Thanks, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Request to join the Atomic SIG
by Colin Walters 02 Oct '14

02 Oct '14

Hi, I'd like to join the Atomic SIG. I am upstream author of one of the components (rpm-ostree), and have contributed to others like systemd, and SELinux, as well as work on packaging Kubernetes in http://copr.fedoraproject.org/coprs/walters/atomic-next/. I'm particularly interested in how we maintain the atomic host ostree composes and integrating it with the CentOS infrastructure.

3 3

Storage SIG Meeting minutes (OpenAFS only)
by Andrew Deason 01 Oct '14

01 Oct '14

Here are my notes from the Storage SIG Meeting from 01 Oct 2014, just for the OpenAFS parts. There were some communication difficulties near the end of the meeting, but what I gathered is that I/Jonathan/Ross would handle the minutes for the OpenAFS section, and Lalatendu would write up notes for the rest. Karanbir was distracted or absent for the last few points, I believe. There were a few sections where I had trouble hearing/understanding, so it is entirely possible some of the information here is wrong. But this is what I could remember and understand. Attending: Andrew Deason Jonathan Billings Karanbir Singh Lalatendu Mohanty Ross Smith - Current status: Ross has created an initial spec file for packaging the userspace portions of OpenAFS, based on the spec file from upstream OpenAFS 1.6.9. - Next step: We need to figure out what to do about the kernel modules. - Andrew asks about the system for triggering builds based on kernel uploads. Karanbir says the old system (this is maybe the 'distro buildsystem'?) supported these triggers/hooks, but the new buildsystem with Koji does not (yet?). The old system is being phased out and SIGs should only submit packages via Koji, so this 'triggers' approach is not usable yet. Karanbir mentioned a possible workaround, which I think is just what was mentioned on the list (a hook in the distro buildsystem calls out to Koji). - Andrew raises the issue that such 'triggers' would only cause kmods to be built with new kernel versions; it does not cause new OpenAFS versions to be built against old kernels. Doing so requires building OpenAFS against all older kernel versions upon a new release of OpenAFS. Karanbir explains that while the extra load caused by this is not a problem, you can't just build "foreach" kernel version, and in fact many of the older kernel releases get deleted, so they will not be available to build against. One way of moving forward is to just not build kmods for kernels older than the current openafs release, but this will be a problem for sites that want to upgrade OpenAFS without upgrading their kernel. - Jonathan notes that if we restrict this to EL7 and newer, at least for now, the number of kernels is much smaller. Since in addition to just having fewer kernel revisions, there are fewer variants (x86, PAE, etc). - Karanbir suggests that for now, we just go with the easiest thing that at least minimally works (e.g. just akmods or DKMS). Working out how to handle plain kmods can be deferred and based on user feedback. - Jonathan raises the question of akmods vs DKMS; why do akmods seem more popular? Karanbir's answer involved something about the dependencies, but I did not catch (or have forgotten) the details. - Karanbir asks if he should start pushing the existing packaging into the buildsystem and into CentOS. Andrew suggests we should wait until at least something with the kernel modules is figured out, and a little more testing with the server components. Ross mentions he just tested the client portions, using an upstream kmod. - Andrew solicits opinions on the existence of the 'compat' and/or 'transarc' packages (at least for now); no objections, and no strong opinions on whether these remain as two separate packages or as one. The names openafs-compat and openafs-transarc may not be clear for new users, but their meanings are clear for older users of OpenAFS (who are the only people that care about them). - Andrew asks about what the 'Packager' should be set to in the spec file. Lalatendu I think mentioned we can just set it to the Storage SIG, and we don't need to specify an email address. - Andrew asks about obtaining access to try building packages through Koji. I think the response was that this is pretty open and easy to obtain (at least for sandbox testing), and I just need to go look at it. [I'm sure more specific information was given to me here, but I didn't hear it, sorry.] So, based on that meeeting, here is what I think the next actions are: - Ross is to try a pass at packaging the kernel module via a separate spec file, without worrying about regular kmods; just dynamically building the modules on the client machine is fine for now. - Andrew is to test and try out the servers in the existing packages. - Andrew will create 'compat' and 'transarc' packages (I'll submit pull requests). (Or if Ross or anyone else wants to, go ahead, but I assume I am to do this if I don't hear anything else.) -- Andrew Deason adeason(a)sinenomine.net

1 0

openafs userspace packages
by ross smith 01 Oct '14

01 Oct '14

Hello Everyone, I have been working on reworking the upstream spec file to work with centos. I've been keeping track of my progress on my github page [1] and I welcome pull requests if you find a problem. I have pulled out all of the code related to the building the kmod, as I think that should at least be rewritten from scratch and quite possibly should live in it's own spec file. I did turn off the transarch paths configure option, which will break external scripts that expect the legacy paths. Turning off the transarch paths also meant I had to put moved files back into subpackages and I might have misplaced some files and not noticed. Finally, I've gotten the userspace packages building in koji [2] with minimal testing. Use at your own risk; they might kick kittens. Note that these are only userspace packages. You'll need the kmod from some other source to make the client work. Ross Smith [1] https://github.com/gaurdro/openafs [2] http://koji.fedoraproject.org/koji/taskinfo?taskID=7703952

4 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel