[Gluster-devel] Missing Debian packages

2016-10-17 Thread Shane StClair 
Hi all,

Debian packages are missing on download.gluster.org for almost all versions
of Gluster. Examples:

https://download.gluster.org/pub/gluster/glusterfs/LATEST/Debian/
https://download.gluster.org/pub/gluster/glusterfs/3.8/LATEST/Debian/
https://download.gluster.org/pub/gluster/glusterfs/3.8/3.8.5/Debian/
https://download.gluster.org/pub/gluster/glusterfs/3.7/LATEST/Debian/

According to the documentation these apt repo URLs are correct:

https://gluster.readthedocs.io/en/latest/Install-Guide/Install/#for-debian

This is breaking apt updates on our servers with the following errors:

```
$ sudo apt-get update
...
Err http://download.gluster.org jessie/main amd64 Packages

  404  Not Found [IP: 23.253.208.221 80]
...
W: Failed to fetch
http://download.gluster.org/pub/gluster/glusterfs/3.7/LATEST/Debian/jessie/apt/dists/jessie/main/binary-amd64/Packages
 404  Not Found [IP: 23.253.208.221 80]

E: Some index files failed to download. They have been ignored, or old ones
used instead.
$ echo $?
100
```

I believe this problem happened recently because our deployments ran
normally until this morning.

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

Re: [Gluster-devel] [Outreachy] Results of IOZone and smallfile bench tests with some changes.

2016-10-17 Thread Shyam 

On 10/15/2016 09:14 PM, Menaka Mohan wrote:

Hello,


I have been able to successfully run the IOZone bench test on the
Gluster setup. Kindly find the results here [1].


Neat, thanks.




But for the smallfile distributed I/O benchmark, the test fails. Since
we are taking 5 samples in each operation, the " --operation create "
fails reporting that the file already exits from the second
sample [1462.758118, None, None, None, None] . Necessary changes are to
be made such that the --operation create happens only once and others (
--operation read and --operation ls-l ) run as usual. Kindly correct me,
If I am wrong.


I am wondering why [3] is not getting triggered and cleaning up the 
files in your test run. It seems to be doing the job in my setup. 
Possibly something to check/debug when you get a chance.





Assuming that as the reason, I have made the necessary changes to the
code [sample _size for create operation is 1] and ran the bench test.
Kindly find the results here [2].


This should be fine for the exercise. The interest in running a test 
more than once is to ensure we do not have any noise from a single run 
that gives us incorrect numbers as a result. So for now, running this 
once is fine, unless you get some time to debug as above.





I will further work on it as a single script and post the output as
mentioned in the GitHub page. Since this is a very time consuming
process, I will simultaneously work on the next task which is to
investigate the tools to use and analyze the system resource usage
across the setup.


I would encourage looking at the next part (i.e tools to analyze the 
system) of this task, as that can provide some more meaningful data for 
the project.





[1]   https://paste.fedoraproject.org/451045/55349814/
[2]   https://paste.fedoraproject.org/451953/14765795/


[3] GlusterBench line that should cleanup small files: 
https://github.com/gluster/gbench/blob/master/bench-tests/bt--0001/GlusterBench.py#L257

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

Re: [Gluster-devel] Need help in understanding IOZone config file

2016-10-17 Thread Dustin Black 
Hi Menaka,

We test Gluster with something like this using iozone for 4GB file sizes.

iozone -t 6 -s 4g -r 4m -+m clients.ioz -c -e -+z -+n -i 0 && iozone -t 6
-s 4g -r 4m -+m clients.ioz -c -e -+z -+n -i 1


Where the clients.ioz file might look like the below for 6 clients/workers:

c0 /path/to/gluster/client/mount /path/to/binary/iozone
c1 /path/to/gluster/client/mount /path/to/binary/iozone
c2 /path/to/gluster/client/mount /path/to/binary/iozone
c3 /path/to/gluster/client/mount /path/to/binary/iozone
c4 /path/to/gluster/client/mount /path/to/binary/iozone
c5 /path/to/gluster/client/mount /path/to/binary/iozone


Dustin Black, RHCA
Senior Architect, Software-Defined Storage
Red Hat, Inc.


On Mon, Oct 10, 2016 at 3:48 PM, Menaka Mohan  wrote:

> Hi,
>
>
> I am Menaka M. I am new to this open source world. Kindly help me with the
> following query.
>
>
> I have set up the Gluster development environment with two servers and one
> client. I am trying to run the basic bench test on the Gluster cluster from
> this GitHub repo
> .
> I also have IOZone installed. In that, how to generate the clients.ioz
> file (prerequisite 3) ? Does that refer to the file containing (client_name
>   work_dirpath_to_IOZone_on_client) ?
>
>
> I have read multiple blogs on how to analyze the IOZone results and also
> the performance testing section in docs. Kindly help me resolve this
> confusion. If I had asked a very basic thing, apologies. I will quickly
> learn them.
>
>
> Regards,
>
> Menaka M
>
> ___
> 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] Participating in Outreachy for Gluster

2016-10-17 Thread Kanika Murarka 
Hi,

My name is Kanika Murarka(a2batic). I am a final year student pursuing my
B. Tech in Computer Science Engineering. I have contributed in various
opensource projects like Fedora[1], PyDSA[2] and Qutebrowser[3]. I also
share my works and keep my blog updated [4]. Some of my activities with
Fedora and Open Source include [5]. As always , I seek for knowledge and
their functional implementation and hence keep contributing to keep my
skills sharp.Looking forward to contribute to Gluster documentation as it
intrigues me !

As a part of contribution, I have submitted a PR [6] on [7], to enhance the
code.

I will be thankful if someone can guide on how can I contribute more and
review my PR.

[1] Contributing to Fedora:-
Fedora QA
https://badges.fedoraproject.org/user/a2batic

Fedora-hubs project:-
https://pagure.io/fedora-hubs/pull-request/255

Contributing to Fedora-design:-
https://fedorahosted.org/fedora-badges/ticket/204
https://fedorahosted.org/fedora-badges/ticket/464
https://fedorahosted.org/fedora-badges/ticket/489
https://fedorahosted.org/fedora-badges/ticket/490
https://fedorahosted.org/fedora-badges/ticket/491

[2]https://github.com/pydsa/pydsa/pull/72
[3]https://github.com/The-Compiler/qutebrowser/pull/1407
[4]http://a2batic.wordpress.com/
[5]https://communityblog.fedoraproject.org/author/a2batic/
[6]https://github.com/gluster/gbench
[7]https://github.com/gluster/gbench/pull/11

Thanks and Regards
Kanika(a2batic)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Need help in understanding IOZone config file

2016-10-17 Thread Bhaskarakiran 
Hi Menaka,

Yes, you are correct. -+m option is passed to iozone wherein the file
should have the fields mentioned. Here is the brief description of the file
contents.

Used  to  specify  a filename that will be used to specify the clients in a
distributed measurement. The file contains one line for each client. The
fields are space delimited. Field 1 is the client name. Field 2 is the
working directory, on  the  client, where Iozone will run. Field 3 is the
path to the executable Iozone on the client.

If the file does not exist the script prompts to create one and take the
number of threads as input.  Hope this helps.

Thanks,
Bhaskarakiran.


On Tue, Oct 11, 2016 at 1:18 AM, Menaka Mohan  wrote:

> Hi,
>
>
> I am Menaka M. I am new to this open source world. Kindly help me with the
> following query.
>
>
> I have set up the Gluster development environment with two servers and one
> client. I am trying to run the basic bench test on the Gluster cluster from
> this GitHub repo
> .
> I also have IOZone installed. In that, how to generate the clients.ioz
> file (prerequisite 3) ? Does that refer to the file containing (client_name
>   work_dirpath_to_IOZone_on_client) ?
>
>
> I have read multiple blogs on how to analyze the IOZone results and also
> the performance testing section in docs. Kindly help me resolve this
> confusion. If I had asked a very basic thing, apologies. I will quickly
> learn them.
>
>
> Regards,
>
> Menaka M
>
> ___
> 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

Re: [Gluster-devel] Interested in contributing to Gluster Documentation

2016-10-17 Thread Srravya C 
On Wed, Oct 12, 2016 at 3:34 PM, Nigel Babu  wrote:

> On Tue, Oct 04, 2016 at 02:22:35PM +0530, Srravya C wrote:
> > Hi all,
> >
> > I am Srravya. I recently came across Gluster on the list of
> > communities/organisations participating in Outreachy
> > . Upon going
> through
> > the list of projects Gluster has listed for the internship, I noticed
> that
> > one of them is a documentation project. As a new comer to Gluster, I
> > believe this would be a good way for me to get started in understanding
> > Gluster and make my first contributions.
> >
> > I would love to interact with community members including developers and
> > documentation team members to know how best I can begin working on
> Gluster.
> > It would be great if I could be pointed to any documentation bugs/tasks I
> > could pick and also general docs on getting started and initial set up
> > steps.
> >
> > Looking forward to collaborating :)
> >
> > Cheers,
> > Srravya
>
> Hi Srravya,
>
> I suspect you pinged me on IRC over the last week trying to find help.
> Apologies in the delay in getting back to you. We've all been at Gluster
> Developer Summit and was mostly away from our computers.
>
>

> I'm speaking on behalf of Amye and documentation team members here, so you
> can
> get started right way. A good thing to try is the following:
>
> 1. Clone the documentation repo[1].
> 2. Try to build the documentation (Documentation for mkdocs[2]).
>
> The initial contribution we've listed is for you to find something that
> needs
> improvement and fix it. I would recommend taking a look around to see if
> you
> can find something to do. The bugs we have on file aren't very useful for
> initial contributions.
>
> I have a couple of suggestions on something you can start with
> 1. Install aspell[3] and check for spelling mistakes across the
> documentation.
>Submit pull requests for fxing them.
> 2. Install Linkchecker[4] and run it against gluster.readthedocs.org and
> catch
>any links that lead to 404.
>
> If you have questions, please free to ask on the list and we're happy to
> help.
>
> [1] https://github.com/gluster/glusterdocs/
> [2] http://www.mkdocs.org/
> [3] http://aspell.net/
> [4] https://pypi.python.org/pypi/LinkChecker
>
> --
> nigelb
>


Hi Nigel,

Thank you for responding back to me. I am glad I was able to reach out to
all of you.

I cloned the docs repo and have been reading the documentation, also using
it simultaneously to try and understand gluster. I attempted resolving some
of the open issues but I didn't have much luck with it. I guess I should be
more familiar with the project before I work on them. I shall get started
on your suggestions and update my progress here.


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

Re: [Gluster-devel] Check the possibility to incorporate DEBUG info permanently in build

2016-10-17 Thread ABHISHEK PALIWAL 
Hi Vijay,

It is quite difficult to provide the exact instances but below are the two
mostly occurred cases.

1. Get duplicate peer entries in 'peer status' command
2. We lost sync between two boards due to gluster mount point is not
present at one of the board.


Regards,
Abhisehk

On Mon, Oct 17, 2016 at 6:40 AM, Vijay Bellur  wrote:

> On 10/14/2016 04:30 AM, ABHISHEK PALIWAL wrote:
>
>> Hi Team,
>>
>> As we are seeing many issues in gluster. And we are failing to address
>> most of the gluster issues due to lack of information for fault analysis.
>>
>> And for the many issue unfortunately with the initial gluster logs we
>> get a very limited information which is not at all possible to find the
>> root cause/conclude the issue.
>> Every time enabling the LOG_LEVEL to DEBUG is not feasible and few of
>> the cases are very rarely seen.
>>
>> Hence, I request you to check if there is a possibility  to incorporate
>> the debug information in build or check if its possible to introduce a
>> new debug level that can always be activated.
>>
>> Please come back on this!
>>
>
> Abhishek - please provide specific instances of the nature of logs that
> could have helped you better. The query posted by you is very broad based
> and such broad queries seldom helps us in achieving the desired outcome.
>
> Regards,
> Vijay
>



-- 




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