[Gluster-devel] volfile init/reconfigure have been working by accident?

[Pranith Kumar Karampuri]

hi,
I wanted to remove 'get_new_dict()', 'dict_destroy()' usage through
out the code base to prevent people from using it wrong. Regression for
that patch http://review.gluster.org/13183 kept failing and I found that
the 'xl->options' dictionary is created using get_new_dict() i.e. it
doesn't have any refs. And in xlator_members_free() we try to destroy it
using dict_unref() i.e. ref count becomes '-1' and the dictionary doesn't
get destroyed. so every reconfigure is leaking dictionaries. So all the
options which use string options actually point to the values in these
dictionaries. Initially I thought we can have latest reconfigured options
dictionary also stored in new member 'xl->reconfigured_options' but the
problem is reconfigure can partially succeed leading to dilemma about which
options succeeded/failed and which dictionary to keep around. Failing in
reconfigure doesn't stop the brick. At the moment the only way out I see is
to perform [de]allocation of the string, bool(we can prevent for bool)
options, may be there are more, I need to check. But this becomes one more
big patch('fini' should GF_FREE all these options), so wondering if anyone
has any other thoughts on fixing this properly without a lot of code
changes.

-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster's Public Social Media Accounts

[Amye Scavarda]

In an effort to expand our community reach, we're going to implement a
few changes with the Gluster social media accounts. We've got some
great tools that we're not using that will help us reach more people.

Starting July 20th, we'll be moving to using HootSuite to schedule
posts exclusively on Twitter, which is good in a number of ways: We'll
be able to track our analytics more effectively, we'll be able to
schedule posts at high traffic times in timezones we want to reach,
and we'll get an understanding of where our growth areas are for
engagement. Facebook posts will tie into Twitter posts, and we'll be
able to track that as well.

Google+ community pages will remain unchanged, as will our LinkedIn accounts.
Thanks all!

-- amye

-- 
Amye Scavarda | a...@redhat.com | Gluster Community Lead
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Setting up NFS ganesha using gdeploy

[Atin Mukherjee]

Great going, Sac!

On Wednesday 13 July 2016, Sachidananda URS  wrote:

> Hi,
>
> I've fixed nfs-ganesha module in gdeploy and merged in master.
> Now we will be able to setup NFS-Ganesha on a freshly installed RHEL 7
> machines end-to-end
> (Including subscribing to channels and installing the necessary packages)
> quite smoothly.
>
> We have two prerequisites:
>
> 1. Setup hostnames for the nodes.
> 2. Setup passwordless ssh from your laptop to the NFS ganesha nodes.
>
> I've tested this end-to-end on RHEL-7 machine. And works pretty good.
> I request to test this extensively.
>
> I'll now test and fix any issues in adding/deleting nodes to the existing
> cluster.
>
> The fixes are available in master [1] I'll build RPMs a couple of weeks
> from now.
> And install instructions at [2]
>
> Attaching sample configuration file which I used for my deployment. Let me
> know if help is needed
> in tweaking the config file.
>
> [1] https://github.com/gluster/gdeploy
> [2]
> http://gdeploy.readthedocs.io/en/latest/installation.html#installing-from-source
>
> Note:
> 1. gdeploy is ported to Ansible 2.1, update to latest ansible.
> 2. If running on RHEL6 make sure to install the necessary packages
>


-- 
--Atin
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Setting up NFS ganesha using gdeploy

[Sachidananda URS]

Hi,

I've fixed nfs-ganesha module in gdeploy and merged in master.
Now we will be able to setup NFS-Ganesha on a freshly installed RHEL 7
machines end-to-end
(Including subscribing to channels and installing the necessary packages)
quite smoothly.

We have two prerequisites:

1. Setup hostnames for the nodes.
2. Setup passwordless ssh from your laptop to the NFS ganesha nodes.

I've tested this end-to-end on RHEL-7 machine. And works pretty good.
I request to test this extensively.

I'll now test and fix any issues in adding/deleting nodes to the existing
cluster.

The fixes are available in master [1] I'll build RPMs a couple of weeks
from now.
And install instructions at [2]

Attaching sample configuration file which I used for my deployment. Let me
know if help is needed
in tweaking the config file.

[1] https://github.com/gluster/gdeploy
[2]
http://gdeploy.readthedocs.io/en/latest/installation.html#installing-from-source

Note:
1. gdeploy is ported to Ansible 2.1, update to latest ansible.
2. If running on RHEL6 make sure to install the necessary packages
[hosts]
server1
server2

[backend-setup]
devices=/dev/vdb
vgs=vg1
pools=pool1
lvs=lv1
mountpoints=/mnt/brick

# Subscribe to necessary channels
[RH-subscription1]
action=register
username=@redhat.com
password=
pool=

[RH-subscription2]
action=disable-repos
repos=

[RH-subscription3]
action=enable-repos
repos=rhel-7-server-rpms,rh-gluster-3-for-rhel-7-server-rpms,rh-gluster-3-nfs-for-rhel-7-server-rpms,rhel-ha-for-rhel-7-server-rpms

[firewalld]
action=add
ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp
services=glusterfs

[yum]
action=install
repolist=
gpgcheck=no
update=no
packages=glusterfs-ganesha

[volume]
action=create
volname=ganesha
transport=tcp
replica_count=2
force=yes

[nfs-ganesha]
action=create-cluster
ha-name=ganesha-ha-360
cluster-nodes=server1,server2
vip=10.70.44.121,10.70.44.122
volname=ganesha
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-Maintainers] Gluster Events API - Help required to identify the list of Events from each component

[Vijay Bellur]

On 07/13/2016 10:23 AM, Aravinda wrote:

Hi,

We are working on Eventing feature for Gluster, Sent feature patch for
the same.
Design: http://review.gluster.org/13115
Patch:  http://review.gluster.org/14248
Demo: http://aravindavk.in/blog/10-mins-intro-to-gluster-eventing

Following document lists the events(mostly user driven events are
covered in the doc). Please let us know the Events from your components
to be supported by the Eventing Framework.

https://docs.google.com/document/d/1oMOLxCbtryypdN8BRdBx30Ykquj4E31JsaJNeyGJCNo/edit?usp=sharing




Thanks for putting this together, Aravinda! Might be worth to poll 
-users ML also about events of interest.


-Vijay
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster Events API - Help required to identify the list of Events from each component

[Aravinda]

Hi,

We are working on Eventing feature for Gluster, Sent feature patch for 
the same.

Design: http://review.gluster.org/13115
Patch:  http://review.gluster.org/14248
Demo: http://aravindavk.in/blog/10-mins-intro-to-gluster-eventing

Following document lists the events(mostly user driven events are 
covered in the doc). Please let us know the Events from your components 
to be supported by the Eventing Framework.


https://docs.google.com/document/d/1oMOLxCbtryypdN8BRdBx30Ykquj4E31JsaJNeyGJCNo/edit?usp=sharing

--
regards
Aravinda

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Expect Gerrit and Jenkins issues: Network outage in RDU

[Nigel Babu]

This issue is now fixed. It's my end of day, so I won't be able to do much
to fix the bustages we have on CI. I'll dive in tomorrow morning.

On Wed, Jul 13, 2016 at 12:35 PM, Nigel Babu  wrote:

> Hello
>
> There's an ongoing network outage in the RDU datacenter. This means we
> will have issues with Gerrit and Jenkins until this issue is fixed. When we
> have an update, we'll reply to this thread.
>
> --
> nigelb
>



-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Gluster weekly community meeting minutes 13-Jul-2016

[Kaleb S. KEITHLEY]

Minutes:
https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00.html
Minutes (text):
https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00.txt
Log:
https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00.log.html

Next weeks meeting will be held at 12:00 UTC  20 July 2016 in
#gluster-meeting on freenode.  See you all next week.

===
#gluster-meeting: Community Meeting
===


Meeting started by kkeithley at 12:00:27 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/gluster-meeting/2016-07-13/community_meeting.2016-07-13-12.00.log.html
.



Meeting summary
---
* roll call  (kkeithley, 12:00:56)

* GlusterFS 4.0  (kkeithley, 12:03:50)

* next week's host  (kkeithley, 12:04:27)

* GlusterFS 4.0  (kkeithley, 12:07:17)

* GlusterFS 3.9  (kkeithley, 12:11:42)

* GlusterFS 3.8  (kkeithley, 12:14:48)
  * LINK:
https://download.gluster.org/pub/gluster/glusterfs/download-stats.html
(kkeithley, 12:17:04)

* GlusterFS 3.7  (kkeithley, 12:17:51)
  * ACTION: kshlm and ndevos to respond to
http://www.gluster.org/pipermail/maintainers/2016-July/001063.html
(kkeithley, 12:23:49)
  * problem with the order in which packages are installed, geo-rep
package is installed after server, but server call gsyncd provided
by geo-rep resulting in using older version binary.  (kkeithley,
12:30:11)

* next week's meeting chair  (kkeithley, 12:31:19)

* GlusterFS 3.6  (kkeithley, 12:34:45)

* Infrastructure  (kkeithley, 12:37:42)

* NFS-Ganesha  (kkeithley, 12:42:08)

* Samba  (kkeithley, 12:42:51)

* AIs from last week  (kkeithley, 12:44:00)
  * ACTION: kshlm, csim to chat with nigelb about setting up faux/pseudo
user email for gerrit, bugzilla, github  (kkeithley, 12:47:43)
  * ACTION: rastar to look at 3.6 builds failures on BSD  (kkeithley,
12:48:32)
  * ACTION: kshlm will start a mailing list discussion on EOLing 3.6
(kkeithley, 12:49:58)
  * ACTION: kshlm to setup GD2 CI on centos-ci  (kkeithley, 12:53:02)

* chair for next week's meeting  (kkeithley, 12:53:17)

* Open Floor  (kkeithley, 12:55:20)
  * IDEA: quick summary of our release - what went well, what we can
improve, what we did improve this time.  (kkeithley, 12:59:30)

Meeting ended at 13:00:55 UTC.




Action Items

* kshlm and ndevos to respond to
  http://www.gluster.org/pipermail/maintainers/2016-July/001063.html
* kshlm, csim to chat with nigelb about setting up faux/pseudo user
  email for gerrit, bugzilla, github
* rastar to look at 3.6 builds failures on BSD
* kshlm will start a mailing list discussion on EOLing 3.6
* kshlm to setup GD2 CI on centos-ci




Action Items, by person
---
* nigelb
  * kshlm, csim to chat with nigelb about setting up faux/pseudo user
email for gerrit, bugzilla, github
* rastar
  * rastar to look at 3.6 builds failures on BSD
* **UNASSIGNED**
  * kshlm and ndevos to respond to
http://www.gluster.org/pipermail/maintainers/2016-July/001063.html
  * kshlm will start a mailing list discussion on EOLing 3.6
  * kshlm to setup GD2 CI on centos-ci


People Present (lines said)
---
* kkeithley (113)
* nigelb (16)
* post-factum (16)
* atinm (8)
* jdarcy (6)
* kotreshhr (6)
* aravindavk (6)
* rastar (6)
* partner (4)
* skoduri (3)
* zodbot (3)
* ira (2)
* msvbhat (1)
* Saravanakmr (1)
* karthik_ (1)
* ramky (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



-- 

Kaleb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Expect Gerrit and Jenkins issues: Network outage in RDU

[Nigel Babu]

Hello

There's an ongoing network outage in the RDU datacenter. This means we will
have issues with Gerrit and Jenkins until this issue is fixed. When we have
an update, we'll reply to this thread.

-- 
nigelb
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Snapshot Scheduler

[Avra Sengupta]

On 07/13/2016 02:37 AM, Niels de Vos wrote:

On Wed, Jul 13, 2016 at 12:37:17AM +0530, Avra Sengupta wrote:

Thanks Joe for the feedback. We are aware of the following issue, and we
will try and address this by going for a more generic approach, which will
not have platform dependencies.

I'm mostly in favour of using the standard functionalities that other
components already provide. Use systemd-timers when available, and cron
as fallback would have my preference. Not sure how much my opinion
counts, but I hope you'll take it into consideration. Writing a bug-free
scheduler from scratch is difficult :-)

Niels

Neils,

Thanks for the suggestion. I have been an advocate of having one single 
scheduler for Gluster from the beginning, such as it is not strictly 
tied to snapshots, but can be used by other components. Such a scheduler 
would be policy based and modular enough in both functionality and 
implementation to support any component's requirement, preferably in a 
plug and play fashion without much hassle to be needed from the other 
components end.


We were suggested to use cron back then, with the same argument as to 
not re-invent the wheel. While it makes perfect sense not to re-do 
what's already done, I would this time around try to aim at achieving 
the above mentioned goal first, irrespective of the underlying infra. 
That being said, we have not ruled out the use of either systemd-timers 
or cron, and we are currently estimating the scope of the feature in 
respect of the time in hand, and the resources at disposal, and hence 
asking for feedback. :)


Regards,
Avra





On 07/12/2016 11:59 PM, Joe Julian wrote:

cron isn't installed by default on Arch rather scheduling is done by
systemd timers. We might want to consider using systemd.timer for
systemd distros and crontab for legacy distros.


On 07/08/2016 03:01 AM, Avra Sengupta wrote:

Hi,

Snaphsots in gluster have a scheduler, which relies heavily on
crontab, and the shared storage. I would like people using this
scheduler, or for people to use this scheduler, and provide us
feedback on it's experience. We are looking for feedback on ease of
use, complexity of features, additional feature support etc.

It will help us in deciding if we need to revamp the existing
scheduler, or maybe rethink relying on crontab and re-writing our
own, thus providing us more flexibility. Thanks.

Regards,
Avra
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel