devel

devel@lists.centos.org

5 participants
4641 discussions

influence and impact instead of packagers
by Karanbir Singh 07 Feb '15

07 Feb '15

hi One key aspect to the proper functioning of our SIGs is the ability for people to reach out in user, contributor and advisor roles ( each of those is key, in decreasing levels of impact ). However, the way we are setting up right now is still very much driven by the idea of packagers and rpms in repos. For example, $project working off their github repo - delivering sources for a centos userbase should also have some level of influence over what goes in and out of the repos and how the repos are lined up ; just like any other SIG might. And components in a SIG should be able to impact components in other SIG resources. A more specific example locally within the ecosystem might be that Cloud SIG should have some expectation around what the VirtSIG is doing and the StorageSIG is doing without needing to be co-authors on packages. The same would be true for EPEL and other external repos that we might want to rope into a common pool at some point. Folks doing the consumption part of the components should have the ability to assert influence and impact on the providers backing the content. I have some ideas on how we can make this happen, but nothing that is simple nor straightforward in a complete cycle. The biggest challenge is in mindset down the contributor path. Maybe as a first step, we should consider having a common criteria on what is considered stable and what is considered releasable - without removing the ability for the SIG's and their hosted projects to still deliver a user story they want ( and ideally, in line with their ultimate upstream desires ). Thoughts ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Gluster Updates for Storage SIG
by Karanbir Singh 06 Feb '15

06 Feb '15

The CentOS Storage SIG, has updated Gluster to 3.6.2 in the community testing repos. You can find more information on howto get started with this repo at : http://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart The Following rpms have been updated: CentOS-6 i386/glusterfs-3.6.2-2.el6.i386.rpm i386/glusterfs-api-3.6.2-2.el6.i386.rpm i386/glusterfs-api-devel-3.6.2-2.el6.i386.rpm i386/glusterfs-cli-3.6.2-2.el6.i386.rpm i386/glusterfs-devel-3.6.2-2.el6.i386.rpm i386/glusterfs-extra-xlators-3.6.2-2.el6.i386.rpm i386/glusterfs-fuse-3.6.2-2.el6.i386.rpm i386/glusterfs-geo-replication-3.6.2-2.el6.i386.rpm i386/glusterfs-libs-3.6.2-2.el6.i386.rpm i386/glusterfs-rdma-3.6.2-2.el6.i386.rpm i386/glusterfs-resource-agents-3.6.2-2.el6.noarch.rpm i386/glusterfs-server-3.6.2-2.el6.i386.rpm x86_64/glusterfs-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-api-3.6.2-2.el6.i386.rpm x86_64/glusterfs-api-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-api-devel-3.6.2-2.el6.i386.rpm x86_64/glusterfs-api-devel-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-cli-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-devel-3.6.2-2.el6.i386.rpm x86_64/glusterfs-devel-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-extra-xlators-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-fuse-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-geo-replication-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-libs-3.6.2-2.el6.i386.rpm x86_64/glusterfs-libs-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-rdma-3.6.2-2.el6.x86_64.rpm x86_64/glusterfs-resource-agents-3.6.2-2.el6.noarch.rpm x86_64/glusterfs-server-3.6.2-2.el6.x86_64.rpm CentOS-7 x86_64/glusterfs-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-api-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-api-devel-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-cli-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-devel-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-extra-xlators-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-fuse-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-geo-replication-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-libs-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-rdma-3.6.2-2.el7.x86_64.rpm x86_64/glusterfs-resource-agents-3.6.2-2.el7.noarch.rpm x86_64/glusterfs-server-3.6.2-2.el7.x86_64.rpm This release fixes the following bugs. Below containt copied from GlusterFS upstream release mail [1]. 1184191 - Cluster/DHT : Fixed crash due to null deref 1180404 - nfs server restarts when a snapshot is deactivated 1180411 - CIFS:[USS]: glusterfsd OOM killed when 255 snapshots were browsed at CIFS mount and Control+C is issued 1180070 - [AFR] getfattr on fuse mount gives error : Software caused connection abort 1175753 - [readdir-ahead]: indicate EOF for readdirp 1175752 - [USS]: On a successful lookup, snapd logs are filled with Warnings "dict OR key (entry-point) is NULL" 1175749 - glusterfs client crashed while migrating the fds 1179658 - Add brick fails if parent dir of new brick and existing brick is same and volume was accessed using libgfapi and smb. 1146524 - glusterfs.spec.in - synch minor diffs with fedora dist-git glusterfs.spec 1175744 - [USS]: Unable to access .snaps after snapshot restore after directories were deleted and recreated 1175742 - [USS]: browsing .snaps directory with CIFS fails with "Invalid argument" 1175739 - [USS]: Non root user who has no access to a directory, from NFS mount, is able to access the files under .snaps under that directory 1175758 - [USS] : Rebalance process tries to connect to snapd and in case when snapd crashes it might affect rebalance process 1175765 - USS]: When snapd is crashed gluster volume stop/delete operation fails making the cluster in inconsistent state 1173528 - Change in volume heal info command output 1166515 - [Tracker] RDMA support in glusterfs 1166505 - mount fails for nfs protocol in rdma volumes 1138385 - [DHT:REBALANCE]: Rebalance failures are seen with error message " remote operation failed: File exists" 1177418 - entry self-heal in 3.5 and 3.6 are not compatible 1170954 - Fix mutex problems reported by coverity scan 1177899 - nfs: ls shows "Permission denied" with root-squash 1175738 - [USS]: data unavailability for a period of time when USS is enabled/disabled 1175736 - [USS]:After deactivating a snapshot trying to access the remaining activated snapshots from NFS mount gives 'Invalid argument' error 1175735 - [USS]: snapd process is not killed once the glusterd comes back 1175733 - [USS]: If the snap name is same as snap-directory than cd to virtual snap directory fails 1175756 - [USS] : Snapd crashed while trying to access the snapshots under .snaps directory 1175755 - SNAPSHOT[USS]:gluster volume set for uss doesnot check any boundaries 1175732 - [SNAPSHOT]: nouuid is appended for every snapshoted brick which causes duplication if the original brick has already nouuid 1175730 - [USS]: creating file/directories under .snaps shows wrong error message 1175754 - [SNAPSHOT]: before the snap is marked to be deleted if the node goes down than the snaps are propagated on other nodes and glusterd hungs 1159484 - ls -alR can not heal the disperse volume 1138897 - NetBSD port 1175728 - [USS]: All uss related logs are reported under /var/log/glusterfs, it makes sense to move it into subfolder 1170548 - [USS] : don't display the snapshots which are not activated 1170921 - [SNAPSHOT]: snapshot should be deactivated by default when created 1175694 - [SNAPSHOT]: snapshoted volume is read only but it shows rw attributes in mount 1161885 - Possible file corruption on dispersed volumes 1170959 - EC_MAX_NODES is defined incorrectly 1175645 - [USS]: Typo error in the description for USS under "gluster volume set help" 1171259 - mount.glusterfs does not understand -n option [1] http://www.gluster.org/pipermail/gluster-devel/2015-January/043617.html -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 7

Adding the NFV SIG to the wiki?
by Dave Neary 06 Feb '15

06 Feb '15

Hi, I noticed that the NFV SIG is not mentioned anywhere on the SIG page wiki: http://wiki.centos.org/SpecialInterestGroup What is involved in getting it added? I think it fits best in "Proposals not yet onboarded" - I am in the process of recruiting initial committers and working through potential issues packaging a key project, and expect to be in a position to propose builds very soon now. Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

2 1

No CentOS SCLo SIG meeting this week
by Honza Horak 06 Feb '15

06 Feb '15

I'm sorry but this week is too busy for me and I have another meeting at the same timeslot. If anybody else wants to hold the meeting, feel free to do so. Honza

3 5

Off - Convert centos instaled to iso or .tar
by Marcos Carraro 05 Feb '15

05 Feb '15

The scenario: - Centos 6.5 perfectly running as a network gateway. doubt Is there any way that I can create some Linux iso installed for later installations? Or create some of the tar / and then transfer it to disk "Create partition, create mbr, create grub, restore files"? Thanks, *--* Att Marcos Carraro about.me/marcoscarraro

3 3

404 - broken redirect?
by Dariusz Lisiak 05 Feb '15

05 Feb '15

Hi there, I think http://mirrorlist.centos.org/?release=6.5&arch=x86_64&repo=os should point to: http://mirror.centos.org/centos/6/os/x86_64/ instead of: http://mirror.centos.org/centos/6.5/os/x86_64/ which returns 404. I noticed the same problem for updates, extras, centosplus, contrib also. Unfortunatelly it breaks down updates on some of our servers based on custom image, that has 6.5 in /etc/yum/vars/releasever. -- regards, D.

2 1

Re: [CentOS-devel] Publish Errata for CentOS
by Somers-Harris, David | David | OPS 05 Feb '15

05 Feb '15

On 01/21/2015 05:41 PM, Jim Perrin wrote: > > > On 01/21/2015 10:06 AM, Tony Coffman wrote: >> On Wed, Jan 21, 2015 at 6:28 AM, Karanbir Singh <mail-lists at karan.org> wrote: >>> >>> the question isnt 'how' its just a xml file, you can write it by hand if >>> you wish. the question is what do we put inside it and how do we make >>> sure what we put inside it is accurate. >>> >> >> >> Why not do a minimal version that simply includes the information from >> the centos-announce mailing list and no external data? There are a >> few other errata fields that can simply be filled in with "not >> available". This minimal solution is nearly there using existing open >> source scripts tied together. > > If someone from the community would be willing to script something up > for this we can take a look at it. Is this the kind of script you are envisioning? Input: Announcement data input by author or CentOS announcement. Output: Announcement email text updateinfo.xml patch > I've been toying with the idea of > adding an rss feed to www.centos.org for the repositories in place of > updateinfo, mostly since Johnny is quite correct, we don't validate > cve closure, so providing that info as if we do seems a bit wrong. I don't see anything wrong with filling errata fields with "not available" as Tony suggested, at least to start with.

1 1

SIG members for State of CentOS panel at OSCON?
by Karsten Wade 04 Feb '15

04 Feb '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: I've proposed a panel for OSCON in Portland, OR this year that is the second annual State of the CentOS Project. Are there any SIG members planning to attend OSCON who would be interested in being on the panel? The idea is to be able to give a short update on your SIG and answer questions from the audience about Virt, Storage, Cloud, et al. I got the proposal in under the deadline and indicated to the organizers that I'm seeking additional panelists. Let me know if you plan to attend and would like to represent your SIG. I think it's OK if we have up to 2 people per SIG, unless we really fill out and need to pare down to 1-per-SIG. 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 v1 iEYEARECAAYFAlTSbPcACgkQ2ZIOBq0ODEE5PwCgqpwmRc+OQRDJqjn6lIjuzWh2 bi0AoJMkFji1Ij19haEGy09yWtDvjWMY =sxny -----END PGP SIGNATURE-----

3 2

CentOS Bug Tracker and ABRT
by Jakub Filak 04 Feb '15

04 Feb '15

Hello everyone, I want to briefly introduce myself. I am a Red Hat employee working on ABRT[1]. We have recently added support for CentOS on the ABRT server[2] and we would like continue in these integration efforts. First of all, I want to submit a pair of patches improving ABRT's UX on CentOS: - do not offer users to report to Red Hat Portal - offer users to send an email to upstream - stop wasting of resources by running sos, because its output is useless for CentOS users In the near future, we would like to integrate ABRT with CentOS Bug Tracker in the same way as ABRT integrates with Red Hat Bugzilla[3]. We are done with the analysis phase[4] and, now, we are working on a testsuite[5]. Unfortunately, MantisBT misses more advanced searching what prevents us from implementing a tool similar to one we have for Bugzilla. At least we need to search by DUPHASH (an unique identifier of a crash, something like tag). Would you be willing to run a MantisBT plugin adding the things we need, if we develop it? Best regards, Jakub http://wiki.centos.org/JakubFilak 1: https://github.com/abrt 2: https://abrt.fedoraproject.org/ 3: https://github.com/abrt/libreport/issues/272 4: https://github.com/abrt/libreport/wiki/MantisBT 5: https://github.com/abrt/abrt/tree/reporter-mantisbt

4 12

Xfce for CentOS group
by Anders F Björklund 02 Feb '15

02 Feb '15

Hi list! Since the Alternative Desktop SIG didn't happen, we thought we would make a more focused effort and improve the Xfce desktop environment experience on CentOS. That might end up being a dedicated CentOS SIG, or just a couple of improvements to the existing packages from EPEL. Once upon a time, or more precisely: back in the CentOS 5.0 days, Xfce 4.4 was available in Extras and it was a pretty simple install that just worked "out of the box". Now, there's the newer versions available via EPEL - but the experience is nowhere near painless... Going to try to meet up with other interested parties during FOSDEM, to see if we can't improve upon that and at least fix the low hanging issues. And get some better Xfce testing and feedback going, as well. A more long-term goal is make it an alternative to GNOME (Workstation). I've rounded up some of the issues, that currently exist: * The theme and icons are wrong, either missing or just ugly * The background image is wrong, ending up with a single color * X11 and Fonts are missing, so just adding the group doesn't work * Some bugs need backporting or fixing, like in Terminal or Xfwm. See http://afb.users.sourceforge.net/xfce/centos/centos-xfce.html Right now, one starts with a Minimal (or Server) install of CentOS. Then adds Base, X11 (including fonts), and finally Xfce (from EPEL). Once the aforementioned problems are taken care of, that should be it. Eventually, it might even end up being a "spin" or available image ? As mentioned earlier, here are the applicable versions of each: * CentOS 5 - Xfce 4.4 (in CentOS Extras) * CentOS 5 - Xfce 4.6 (based on Fedora 6) * CentOS 6 - Xfce 4.8 (based on Fedora 12) * CentOS 7 - Xfce 4.10 (based on Fedora 18) To replace GNOME PackageKit there's the Yum Extender, and to replace GDM there's LightDM (more work is needed, to make a CentOS-6 version). The GNOME icons and GNOME themes will probably "work" to start with, but one can probably improve upon that as well (as a lower priority). Something like http://afb.users.sourceforge.net/xfce/xfce-brave.png If you are interested in helping out with testing, packaging or developing (backporting, fixing the upstream issues, and so on) then please say so. I'll try to have some more detailed lists and updated packages with me, for the FOSDEM meetup in the weekend... * http://wiki.centos.org/Events/Fosdem2015 --anders

5 10

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