February 2015 - devel - lists.centos.org

Atomic ostree update for 16th Feb 2015
by Karanbir Singh 16 Feb '15

16 Feb '15

Hi, Fixing for : http://bugs.centos.org/view.php?id=8200 implies major ostree version update in tonights ostree repos. I've done a couple of basic tests and it seems to work fine, but test before deploying onsite as well please. 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

1 0

CBS/Infra Meeting 16-Feb-2015 14:00 UTC
by Brian Stinson 16 Feb '15

16 Feb '15

Hi All, We're going to get started again with our fortnightly meetings to talk about the Community Build System. Join us in #centos-devel on Freenode Monday, February 16th at 14:00 UTC Here's our agenda: #info Topic: Status Updates #info Subtopic: Centralized Authentication #info Subtopic: Koji/Repos #info Subtopic: Centpkg #info Topic: Document user stories identify missing parts of the workflow #info Topic: Open Floor Cheers! Brian -- Brian Stinson bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

1 0

The correct way to compile module
by Edison Figueira Junior 14 Feb '15

14 Feb '15

Hi, I need to build the module attached but do not know the right way to do, I do not want to change the original kernel, just run this module I downloaded the kernel.src and applied the patch and went back to generate the RPM through SPEC, but got the following error. CC [M] net/sched//act_connmark.o *net/sched//act_connmark.c:* In function ‘*tcf_connmark_init*’: *net/sched//act_connmark.c:112:2:* *error: *too few arguments to function ‘ *tcf_hash_check*’ if (!tcf_hash_check(parm->index, a, bind)) { * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:93:20:* *note: *declared here struct tcf_common *tcf_hash_check(u32 index, struct tc_action *a, * ^* *net/sched//act_connmark.c:113:3:* *error: *too few arguments to function ‘ *tcf_hash_create*’ ret = tcf_hash_create(parm->index, est, a, sizeof(*ci), bind); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:95:20:* *note: *declared here struct tcf_common *tcf_hash_create(u32 index, struct nlattr *est, * ^* *net/sched//act_connmark.c:121:3:* *warning: *passing argument 1 of ‘ *tcf_hash_insert*’ from incompatible pointer type [enabled by default] tcf_hash_insert(a); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:99:6:* *note: *expected ‘*struct tcf_common **’ but argument is of type ‘*struct tc_action **’ void tcf_hash_insert(struct tcf_common *p, struct tcf_hashinfo *hinfo); * ^* *net/sched//act_connmark.c:121:3:* *error: *too few arguments to function ‘ *tcf_hash_insert*’ tcf_hash_insert(a); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:99:6:* *note: *declared here void tcf_hash_insert(struct tcf_common *p, struct tcf_hashinfo *hinfo); * ^* *net/sched//act_connmark.c:127:3:* *warning: *passing argument 1 of ‘ *tcf_hash_release*’ from incompatible pointer type [enabled by default] tcf_hash_release(a, bind); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:87:5:* *note: *expected ‘*struct tcf_common **’ but argument is of type ‘*struct tc_action **’ int tcf_hash_release(struct tcf_common *p, int bind, * ^* *net/sched//act_connmark.c:127:3:* *error: *too few arguments to function ‘ *tcf_hash_release*’ tcf_hash_release(a, bind); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:87:5:* *note: *declared here int tcf_hash_release(struct tcf_common *p, int bind, * ^* *net/sched//act_connmark.c:* In function ‘*connmark_init_module*’: *net/sched//act_connmark.c:179:2:* *error: *too many arguments to function ‘ *tcf_register_action*’ return tcf_register_action(&act_connmark_ops, CONNMARK_TAB_MASK); * ^* In file included from *net/sched//act_connmark.c:23:0*: *include/net/act_api.h:101:5:* *note: *declared here int tcf_register_action(struct tc_action_ops *a); * ^* make[1]: *** [net/sched//act_connmark.o] Error 1 make: *** [_module_net/sched/] Error 2 Kernel patch module diff --git a/include/net/tc_act/tc_connmark.h b/include/net/tc_act/tc_connmark.h new file mode 100644 index 0000000..5c1104c --- /dev/null +++ b/include/net/tc_act/tc_connmark.h @@ -0,0 +1,14 @@ +#ifndef __NET_TC_CONNMARK_H +#define __NET_TC_CONNMARK_H + +#include <net/act_api.h> + +struct tcf_connmark_info { + struct tcf_common common; + u16 zone; +}; + +#define to_connmark(a) \ + container_of(a->priv, struct tcf_connmark_info, common) + +#endif /* __NET_TC_CONNMARK_H */ diff --git a/include/uapi/linux/tc_act/tc_connmark.h b/include/uapi/linux/tc_act/tc_connmark.h new file mode 100644 index 0000000..994b097 --- /dev/null +++ b/include/uapi/linux/tc_act/tc_connmark.h @@ -0,0 +1,22 @@ +#ifndef __UAPI_TC_CONNMARK_H +#define __UAPI_TC_CONNMARK_H + +#include <linux/types.h> +#include <linux/pkt_cls.h> + +#define TCA_ACT_CONNMARK 14 + +struct tc_connmark { + tc_gen; + __u16 zone; +}; + +enum { + TCA_CONNMARK_UNSPEC, + TCA_CONNMARK_PARMS, + TCA_CONNMARK_TM, + __TCA_CONNMARK_MAX +}; +#define TCA_CONNMARK_MAX (__TCA_CONNMARK_MAX - 1) + +#endif diff --git a/net/sched/Kconfig b/net/sched/Kconfig index 4669435..475e35e 100644 --- a/net/sched/Kconfig +++ b/net/sched/Kconfig @@ -549,6 +549,17 @@ To compile this code as a module, choose M here: the module will be called act_police. +config NET_ACT_CONNMARK + tristate "Netfilter Connection Mark Retriever" + depends on NET_CLS_ACT && NETFILTER && IP_NF_IPTABLES + ---help--- + Say Y here to allow retrieving of conn mark + + If unsure, say N. + + To compile this code as a module, choose M here: the + module will be called act_connmark. + config NET_ACT_GACT tristate "Generic actions" depends on NET_CLS_ACT diff --git a/net/sched/Makefile b/net/sched/Makefile index 7ca2b4e..7ca7f4c 100644 --- a/net/sched/Makefile +++ b/net/sched/Makefile +++ b/net/sched/Makefile @@ -16,6 +16,7 @@ obj-$(CONFIG_NET_ACT_SIMP) += act_simple.o obj-$(CONFIG_NET_ACT_SKBEDIT) += act_skbedit.o obj-$(CONFIG_NET_ACT_CSUM) += act_csum.o +obj-$(CONFIG_NET_ACT_CONNMARK) += act_connmark.o obj-$(CONFIG_NET_SCH_FIFO) += sch_fifo.o obj-$(CONFIG_NET_SCH_CBQ) += sch_cbq.o obj-$(CONFIG_NET_SCH_HTB) += sch_htb.o diff --git a/net/sched/act_connmark.c b/net/sched/act_connmark.c new file mode 100644 index 0000000..8e47251 --- /dev/null +++ b/net/sched/act_connmark.c @@ -0,0 +1,192 @@ +/* + * net/sched/act_connmark.c netfilter connmark retriever action + * skb mark is over-written + * + * Copyright (c) 2011 Felix Fietkau <nbd(a)openwrt.org> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version. +*/ + +#include <linux/module.h> +#include <linux/init.h> +#include <linux/kernel.h> +#include <linux/skbuff.h> +#include <linux/rtnetlink.h> +#include <linux/pkt_cls.h> +#include <linux/ip.h> +#include <linux/ipv6.h> +#include <net/netlink.h> +#include <net/pkt_sched.h> +#include <net/act_api.h> +#include <uapi/linux/tc_act/tc_connmark.h> +#include <net/tc_act/tc_connmark.h> + +#include <net/netfilter/nf_conntrack.h> +#include <net/netfilter/nf_conntrack_core.h> +#include <net/netfilter/nf_conntrack_zones.h> + +#define CONNMARK_TAB_MASK 3 + +static int tcf_connmark(struct sk_buff *skb, const struct tc_action *a, + struct tcf_result *res) +{ + const struct nf_conntrack_tuple_hash *thash; + struct nf_conntrack_tuple tuple; + enum ip_conntrack_info ctinfo; + struct tcf_connmark_info *ca = a->priv; + struct nf_conn *c; + int proto; + + spin_lock(&ca->tcf_lock); + ca->tcf_tm.lastuse = jiffies; + bstats_update(&ca->tcf_bstats, skb); + + if (skb->protocol == htons(ETH_P_IP)) { + if (skb->len < sizeof(struct iphdr)) + goto out; + + proto = NFPROTO_IPV4; + } else if (skb->protocol == htons(ETH_P_IPV6)) { + if (skb->len < sizeof(struct ipv6hdr)) + goto out; + + proto = NFPROTO_IPV6; + } else { + goto out; + } + + c = nf_ct_get(skb, &ctinfo); + if (c) { + skb->mark = c->mark; + /* using overlimits stats to count how many packets marked */ + ca->tcf_qstats.overlimits++; + nf_ct_put(c); + goto out; + } + + if (!nf_ct_get_tuplepr(skb, skb_network_offset(skb), + proto, &tuple)) + goto out; + + thash = nf_conntrack_find_get(dev_net(skb->dev), ca->zone, &tuple); + if (!thash) + goto out; + + c = nf_ct_tuplehash_to_ctrack(thash); + /* using overlimits stats to count how many packets marked */ + ca->tcf_qstats.overlimits++; + skb->mark = c->mark; + nf_ct_put(c); + +out: + skb->nfct = NULL; + spin_unlock(&ca->tcf_lock); + return ca->tcf_action; +} + +static const struct nla_policy connmark_policy[TCA_CONNMARK_MAX + 1] = { + [TCA_CONNMARK_PARMS] = { .len = sizeof(struct tc_connmark) }, +}; + +static int tcf_connmark_init(struct net *net, struct nlattr *nla, + struct nlattr *est, struct tc_action *a, + int ovr, int bind) +{ + struct nlattr *tb[TCA_CONNMARK_MAX + 1]; + struct tcf_connmark_info *ci; + struct tc_connmark *parm; + int ret = 0; + + if (!nla) + return -EINVAL; + + ret = nla_parse_nested(tb, TCA_CONNMARK_MAX, nla, connmark_policy); + if (ret < 0) + return ret; + + parm = nla_data(tb[TCA_CONNMARK_PARMS]); + + if (!tcf_hash_check(parm->index, a, bind)) { + ret = tcf_hash_create(parm->index, est, a, sizeof(*ci), bind); + if (ret) + return ret; + + + ci = to_connmark(a); + ci->tcf_action = parm->action; + ci->zone = parm->zone; + + tcf_hash_insert(a); + ret = ACT_P_CREATED; + } else { + ci = to_connmark(a); + if (bind) + return 0; + tcf_hash_release(a, bind); + if (!ovr) + return -EEXIST; + /* replacing action and zone */ + ci->tcf_action = parm->action; + ci->zone = parm->zone; + } + + return ret; +} + +static inline int tcf_connmark_dump(struct sk_buff *skb, struct tc_action *a, + int bind, int ref) +{ + unsigned char *b = skb_tail_pointer(skb); + struct tcf_connmark_info *ci = a->priv; + + struct tc_connmark opt = { + .index = ci->tcf_index, + .refcnt = ci->tcf_refcnt - ref, + .bindcnt = ci->tcf_bindcnt - bind, + .action = ci->tcf_action, + .zone = ci->zone, + }; + struct tcf_t t; + + if (nla_put(skb, TCA_CONNMARK_PARMS, sizeof(opt), &opt)) + goto nla_put_failure; + + t.install = jiffies_to_clock_t(jiffies - ci->tcf_tm.install); + t.lastuse = jiffies_to_clock_t(jiffies - ci->tcf_tm.lastuse); + t.expires = jiffies_to_clock_t(ci->tcf_tm.expires); + if (nla_put(skb, TCA_CONNMARK_TM, sizeof(t), &t)) + goto nla_put_failure; + + return skb->len; +nla_put_failure: + nlmsg_trim(skb, b); + return -1; +} + +static struct tc_action_ops act_connmark_ops = { + .kind = "connmark", + .type = TCA_ACT_CONNMARK, + .owner = THIS_MODULE, + .act = tcf_connmark, + .dump = tcf_connmark_dump, + .init = tcf_connmark_init, +}; + +static int __init connmark_init_module(void) +{ + return tcf_register_action(&act_connmark_ops, CONNMARK_TAB_MASK); +} + +static void __exit connmark_cleanup_module(void) +{ + tcf_unregister_action(&act_connmark_ops); +} + +module_init(connmark_init_module); +module_exit(connmark_cleanup_module); +MODULE_AUTHOR("Felix Fietkau <nbd(a)openwrt.org>"); +MODULE_DESCRIPTION("Connection tracking mark restoring"); +MODULE_LICENSE("GPL"); + -- cgit v0.10.2

1 0

etcd and kubernetes on virt7-testing
by Lokesh Mandvekar 13 Feb '15

13 Feb '15

I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD

1 0

No Storage SIG Meeting for 13th Feb 2015
by Lalatendu Mohanty 13 Feb '15

13 Feb '15

Hi Folks, The Storage SIG meeting was planned for today i.e. 13th Feb. But I somehow missed to send an announcement for it yesterday as I was travelling. So I think we should cancel the meeting today and have it next week. Here are the action items we had in the last meeting. Action item. 1. lalatenduM to document the process of pkg building and moving them to storage sig repos 2. billings to try out reimzul's way of kmod building and yum priorities stuff for openafs repo 3. alphacc to validate the storage7 koji targets and setup new tags as needed for openafs 4. lalatenduM and billings will discuss about the current targets and tags for storage sig 5. kbsingh to see if openafs is GPL compatible or not 6. lalatenduM will help deason to get standard policy or guidance on packaging selinux rules 7. alphacc to give cbs access to scuttlemonkey refer https://bugs.centos.org/view.php?id=8095 8. lalatenduM going to send a mail to centos devel and gluster MLs abt glusterfs test repo availability Thanks, Lala

1 0

Building projects that use Maven
by Dave Neary 13 Feb '15

13 Feb '15

Hi all, One project we would like to have in scope for the NFV SIG is OpenDaylight. It's a project that builds from source code using Maven, and this pulls a number of 3rd party dependencies from Maven Central. What gets pulled in during the build process is a jar, for which Maven Central has source jars. How do other CentOS projects/SIGs which build with Maven handle these dependencies? Is it possible to set Maven up to pull source RPMs and rebuild the Jars to ensure that everything has been built with CentOS signed packages? 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

1 0

Centos 7 - gnome-initial-setup with uid < 500
by Olivier Delhomme 12 Feb '15

12 Feb '15

Hi there, I install Centos 7 machines through kickstart + a post install script. I do not need the gnome-initial-setup to run at all. My post install script create a user and deletes the guest account. When the uid of the newly created user is > 500 everything is fine but when the uid is < 500 the gnome-initial-setup still shows up. Can anyone tell me how to disable/configure gnome-initial-setup for users with uid < 500 ? Cheers, Olivier DELHOMME.

3 7

Gluster testing on CentOS CI
by Justin Clift 12 Feb '15

12 Feb '15

Hi KB, We're interested in the offer to have our CI stuff (Jenkins jobs) run on the CentOS CI infrastructure. We have some initial questions, prior to testing things technically. * Is there a document that describes the CentOS Jenkins setup (like provisioning of the slaves)? * Is it possible for Gluster Community members to log into a Jenkins slave and troubleshoot specific failures? eg if something fails a test, can one of the Community members log into the slave node to investigate (with root perms) * We also want to be sure that our Community members (developers) will have access in the Jenkins interface to do stuff for our jobs. eg create new jobs + editing existing ones (so our tests improve over time), rerunning failed jobs, and so on. We don't need full admin access, but we do need the ability to do stuff for our jobs Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift

2 1

SCL's from softwarecollections.org repos to SIG
by Karanbir Singh 12 Feb '15

12 Feb '15

Hi, Do we have a list of things that need to get done before the repos hosted at SoftwareCollections.org can go away to be replaced with properly maintained content from centos.org ? crossposting, - KB -- 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

5 9

Request to provide/include a -debuginfo repo for the Storage SIG (and others?)
by Niels de Vos 11 Feb '15

11 Feb '15

Hi guys, with the Storage SIG (and its Gluster packages) available for testing, I wanted to run some debugging tests against them. For this, I need the -debuginfo (to make gdb/systemtap work). It seems that there is no -debuginfo repository for in the CentOS-Gluster.repo file that gets provided by the centos-release-gluster package. Could someone look into this? I guess other SIGs could benefit from providing -debuginfo packages as well. Thanks, Niels

5 10

No CentOS SCLo SIG meeting today by hhorak
by Honza Horak 11 Feb '15

11 Feb '15

Guys, I'm very sorry, especially for the late announcement, but I'm not able to hold today's SIG meeting.. If anybody else wants to hold the meeting, feel free to do so. Honza

1 0

GSoC and SIGs
by Karanbir Singh 10 Feb '15

10 Feb '15

hi As a part of the project we are going to try and get onto the GSoC program again this year. Jeff Sheltren and Karsten Wade have offered to do the work needed towards that goal. I've offered to help in short bursts with specific things as and when they need anything. One thing that would be good to get is : a list of the top 3 things every SIG would like to see done as a part of the GSoC effort; These are just idea, concepts and pending ToDo's SIG specific. Please send them to this list, and we can co-ordinate from there. When trying to put tasks together, try and estimate how long these are going to take and then divide them upto 4 to 6 weeks worth of a junior developers typical velocity. Typically, getting an accurate idea of task-time involves actually starting to do the work - but please dont go down that route as yet. A reasonable process for now would be to think about how long it might take you, just off the top of your head - and then multiply that by 3. That should cover the time it takes folks to get familiar with our process' and also the relative velocity of someone much junior doing the same piece of work. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 2

conversations around CI.centos.org
by Karanbir Singh 10 Feb '15

10 Feb '15

hi, as we start onramping the initial projects into ci.centos.org, we are going to need a place to talk about the infra, the process, the actual testing and a find a place to send conversaitons where people need more info around the CICO effort. for now, I suggest we use the centos-devel list, and if volume of traffic grows - or if conversations become too site / role specific, we can move them to its own list as needed. regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Suggestions for topics for the 16-Feb CBS/Infra Meeting (No meeting this week)
by Brian Stinson 10 Feb '15

10 Feb '15

Hi All, Our next scheduled Community Build System meeting is Monday 16-February 2015. Here is our usual agenda: #info Topic: Status Updates #info Subtopic: Centralized Authentication #info Subtopic: Koji/Repos #info Subtopic: Centpkg #info Topic: Open Floor If anyone has suggestions for topics, please let me know. I'll send an updated agenda before the meeting. If there's anything more urgent, we can get going here on the list or in #centos-devel on Freenode. Cheers! Brian -- Brian Stinson bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

2 1

infrastructure for doing C7 builds?
by Fred Smith 10 Feb '15

10 Feb '15

Hi all! I think I remember seeing postings about there being som infrastructure where people not officially affiliated with the project could submit jobs to be run, that would build C7 RPM packages for them. Am I all wet, do I misremember? I can't find, right now, emails on that subject, nor anything that leaps out at me on centos.org or seven.centos.org, which now seems outdates. Where else should I be looking? thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

3 2

setting up an emergency update route
by Karanbir Singh 08 Feb '15

08 Feb '15

Hi, At the end of the Dojo in Brussels, I had the chance to field the question to our contributor audience : how can we get security updates out to the user machines faster. At the moment, things are setup like any other distro or large open source content network is : we rsync in stages, and external mirrors pickup every 4 to 6 hours, some external mirrors pickup from other external mirrors. Net result is that for a given update, it can be upto 16 to 18 hours before we get a majority content sync in front of most users. In cases like the recent Glibc issue, 18 hrs can be a long time since the release ( remember, we already lag RHEL releases since our process starts once theirs ends ). There were a couple of ideas that came up in the conversation at the Dojo, and then in the following conversations over the entire Fosdem weekend. The two that seemed most likely, easiest to implement and perhaps most robust, involved a chunk of the load moving to mirror.centos.org for some period of time. These are : A) we setup a rapid update repo, that would be hosted on and run from mirror.centos.org exclusively. The yum repo definitions would still point at mirrorlist, however they would only expect centos.org urls in the baseurl stack from mirrorlist.centos.org; This would allow us to reduce the overall to-user-visibility in default centos linux installs to under an hour for content upto 250MB in size. B) integrate the mirrorlist backend with the release mechanism in centos linux, so when there is a new updates pushed, all updates are then delivered via mirror.centos.org for the next 24 hrs. After this period, traffic reshapes to be delivered from the external mirrors by default. The Key issue to note with (A) is that while we might push something to this rapid update repo, the same content will also be available in the regular updates/ repo. So once its starts showing up externally, traffic will naturally switch to using the updates repo from local mirrors ( using repo names and cost etc, we can influence repo priority where there is common content ). The second important thing to note here is traffic capacity : we can deliver upto 20 Gbit/sec in the US and EU from centos.org - and around 8 Gbit/sec for everywhere else. Given that we prefer to offload traffic to external mirrors at the moment, its hard to estimate what the overall capacity requirements will be. Ideally, drpms should/would help. Depending on how everyone feels around this, I'd like to go ahead and kick off implementation around this. Lets get it done before the next big security update comes through. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

11 26

a mainline kernel in centos repos
by Karanbir Singh 08 Feb '15

08 Feb '15

Hi, lots of people in various SIGs and user side projects are keen on bringing up a mainline kernel, that tracks upstream closer than the distro kernel does. I'd like to start a conversation around which kernel we might be able to maintain as a group, that also helps most people solve the problems they are looking at. 3.18 seems to be the stable-release at the moment, but given that 3.19 is just around the corner, should we try and aim for that ? regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 6

RFC: CentOS Extras & Plus SIG
by Tim Verhoeven 07 Feb '15

07 Feb '15

Hi, This is just a idea that I'm having and I'm looking for feedback. So that is why the RFC tag is in the subject ;) So the idea is to create a SIG that plays the role of coordinater/janitor for the CentOS Extras and Plus repos. With 2 goals in mind: 1. Allow people to contribute packages and patches to the mentioned repo's. Ideally people would own a package, but the SIG would also take on one-offs. I personally would like to contribute updated haproxy and python-spynner packages. 2. It the other SIG's want to this SIG can be the place to hand off common packages between the SIG's and do some coordination between the SIG's to make sure nothing breaks. So what do you think? Good idea, bad idea, suggestions, ... Kind regards, Tim -- Tim Verhoeven - tim.verhoeven.be(a)gmail.com - 0479 / 88 11 83 Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. (Linus Torvalds)

2 1

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2015