On 08/12/2017 11:56 AM, Niels de Vos wrote:
On Sat, Aug 12, 2017 at 12:49:14PM +, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.5.tar.gz
This release is made off v3.10.5
Packages for the CentOS Storage SIG are available for testing.
On 08/31/2017 10:11 AM, Niels de Vos wrote:
* RHEL/CentOS el6 and el7 are in CentOS Storage SIG staging at [4].
Please test and give feedback on #gluster-devel on freenode or the
gluster-devel mailing list so they can be moved to the staging area.
ok, so I just tested the above, we now need to
On 08/31/2017 11:06 AM, Shyam Ranganathan wrote:
On 08/31/2017 10:11 AM, Niels de Vos wrote:
* RHEL/CentOS el6 and el7 are in CentOS Storage SIG staging at [4].
Please test and give feedback on #gluster-devel on freenode or the
gluster-devel mailing list so they can be moved to the staging area
On 10/31/2017 04:41 AM, Niels de Vos wrote:
On Mon, Oct 30, 2017 at 05:28:35PM +, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.7.tar.gz
This release is made off v3.10.7
Packages are available in the testing repository of the CentOS
On 10/31/2017 04:41 AM, Niels de Vos wrote:
On Mon, Oct 30, 2017 at 05:28:35PM +, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.7.tar.gz
This release is made off v3.10.7
Packages are available in the testing repository of the CentOS
Hi,
2 New releases have been packaged that address the CVE [1].
Request packaging team to get the packages out for testing, so that we
can publish the versions at the earliest.
Thanks,
Shyam
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10841
On 01/11/2018 02:04 AM, Kaushal M wrote:
> On Thu, Jan 11, 2018 at 1:56 AM, Kaleb S. KEITHLEY <kkeit...@redhat.com>
> wrote:
>> comments inline
>>
>> On 01/10/2018 02:08 PM, Shyam Ranganathan wrote:
>>
>> Hi, (GD2 team, packaging team, please read)
>&
On 01/11/2018 02:01 AM, Kaushal M wrote:
>> - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs
>> will not build GD2 (as the source is not available) and will continue as
>> is (which means there is enough spec file magic here that we can specify
>> during release packaging
Hi, (GD2 team, packaging team, please read)
Here are some things we need to settle so that we can ship/release GD2
along with Gluster 4.0 release (considering this is a separate
repository as of now).
1) Generating release package (read as RPM for now) to go with Gluster
4.0 release
Proposal:
Hi Packaging team,
Preparation for RC0 is ongoing, I am waiting on scores for this patch
[1] (removing experimental code from the release branch) to go through,
and the following items to be resolved before tagging RC0.
Devel/maintainers,
1) https://review.gluster.org/#/c/18785/ needs a
On 01/31/2018 09:28 AM, Kaleb S. KEITHLEY wrote:
> On 01/30/2018 02:08 PM, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/39/artifact/glusterfs-3.10.10.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/39/artifact/glusterfs-3.10.10.sha512sum
>>
On 01/31/2018 09:42 AM, Niels de Vos wrote:
> On Wed, Jan 31, 2018 at 09:13:26AM -0500, Kaleb S. KEITHLEY wrote:
>> On 01/31/2018 09:02 AM, Shyam Ranganathan wrote:
>>> Hi,
>>>
>>> In the gluster maintainers meeting last week, one of the topics touched
>>
Hi,
In the gluster maintainers meeting last week, one of the topics touched
upon was, should we build CentOS6 client packages for 4.0?
The reasoning being, upgrading servers to 4.0 requires moving from
CentOS6 (for installations on this base OS version) to CentOS7 and then
moving to 4.0 bits on
All pending actions as noted in the mail are complete, and 4.0.0rc0 has
been tagged.
This brings us to the most important phase of 4.0 which is testing out
things that are not covered in our automated regression runs and such.
For now, let's get some packages (as soon as I trigger the release
On 02/26/2018 01:53 PM, jenk...@build.gluster.org wrote:
> SRC:
> https://build.gluster.org/job/release-new/42/artifact/glusterfs-4.0.0rc0.tar.gz
> HASH:
> https://build.gluster.org/job/release-new/42/artifact/glusterfs-4.0.0rc0.sha512sum
>
> This release is made off jenkins-release-42
Please
On 07/26/2018 03:22 AM, Niels de Vos wrote:
> On Wed, Jul 25, 2018 at 02:48:22PM -0400, Shyam Ranganathan wrote:
>> On 07/24/2018 10:10 AM, Niels de Vos wrote:
>>> On Tue, Jul 24, 2018 at 01:04:39PM +, jenk...@build.gluster.org wrote:
>>>> SRC:
>>>>
On 01/23/2018 07:51 AM, Niels de Vos wrote:
> On Tue, Jan 23, 2018 at 11:56:04AM +0100, Niels de Vos wrote:
>> On Mon, Jan 22, 2018 at 12:22:37PM -0500, Shyam Ranganathan wrote:
>>> On 01/20/2018 08:32 AM, Niels de Vos wrote:
>>>> On Sat, Jan 20, 2018 at 11:55:33AM +0
On 01/20/2018 08:32 AM, Niels de Vos wrote:
> On Sat, Jan 20, 2018 at 11:55:33AM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.tar.gz
>> HASH:
>>
On 03/12/2018 08:35 AM, Niels de Vos wrote:
> On Mon, Mar 12, 2018 at 04:41:02PM +0530, Humble Devassy Chirammal wrote:
>> Hi Shyam,
>>
>> I was asking for centos release rpm for glusterfs 4 release. Any way I have
>> figured it out
>> https://github.com/CentOS-Storage-SIG/centos-release-gluster40
On 03/12/2018 12:59 AM, Humble Devassy Chirammal wrote:
> What would be the release rpm for glusterd4 in centos storage sig?
I assume glusterd2 is the question? @kaushal, can you help out here?
>
> --Humble
>
>
> On Mon, Mar 12, 2018 at 6:31 AM, Shyam Ranganathan &l
On 03/12/2018 03:40 PM, Shyam Ranganathan wrote:
>> Please test the CentOS packages and give feedback so that packages can
>> be tagged for release.
> Tested and the test passes! We are good to publish.
Humble, are the container images done and published?
Further, I am thin
On 03/02/2018 04:50 PM, Shyam Ranganathan wrote:
>> * RHEL/CentOS el6 and el7 are built in CentOS Storage SIG and tagged for
>> testing, but they have not appeared at [4] at the time of this writing.
>> In the mean time they can be downloaded from [5]. Please test and give
>&
On 03/06/2018 10:25 AM, jenk...@build.gluster.org wrote:
> SRC:
> https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.tar.gz
> HASH:
> https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.sha512sum
>
> This release is made off jenkins-release-45
Some call
On 04/24/2018 04:12 PM, Niels de Vos wrote:
> On Tue, Apr 24, 2018 at 02:26:27PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/52/artifact/glusterfs-3.10.12.tar.gz
>> HASH:
>>
On 04/24/2018 04:11 PM, Niels de Vos wrote:
> On Tue, Apr 24, 2018 at 02:16:05PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/50/artifact/glusterfs-3.12.9.tar.gz
>> HASH:
>>
On 03/21/2018 02:45 PM, Kaleb S. KEITHLEY wrote:
> * RHEL and CentOS el7 and el6 (el6 client-side only) in CentOS Storage
> SIG at [4].
>
> All the LATEST and STM-4.0 symlinks have been created or updated to
> point to the 4.0.1 release.
>
> Please test the CentOS packages and give feedback so
Term Maintenance)
Date: Wed, 17 Oct 2018 09:18:25 -0400
From: Shyam Ranganathan
To: Dmitry Melekhov , gluster-us...@gluster.org
On 10/17/2018 12:21 AM, Dmitry Melekhov wrote:
> #1637989 <https://bugzilla.redhat.com/1637989>: data-self-heal in
> arbiter volume results in stale locks.
&
Hi,
3.12 goes EOL with release-5, which is in about a week as most things
are settled at present.
We have the following open patches against 3.12:
https://review.gluster.org/q/project:glusterfs+branch:release-3.12+status:open
My thinking is that we do a final bug fix release for 3.12 (as the
On 10/10/2018 03:58 AM, Niels de Vos wrote:
> On Fri, Oct 05, 2018 at 03:04:41PM -0400, Kaleb S. KEITHLEY wrote:
>> On 10/5/18 12:44 PM, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/release-new/71/artifact/glusterfs-5.0rc1.tar.gz
>>> HASH:
>>>
On 09/25/2018 05:36 PM, Niels de Vos wrote:
> On Tue, Sep 18, 2018 at 11:55:46AM -0400, Kaleb S. KEITHLEY wrote:
>> On 09/17/2018 08:44 PM, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/release-new/69/artifact/glusterfs-5.0rc0.tar.gz
>>> HASH:
>>>
On 09/21/2018 10:55 AM, Niels de Vos wrote:
> On Fri, Sep 21, 2018 at 02:14:45PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/70/artifact/glusterfs-4.1.5.tar.gz
>> HASH:
>>
On 1/17/19 11:09 AM, Niels de Vos wrote:
> On Wed, Jan 16, 2019 at 08:48:16PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/77/artifact/glusterfs-5.3.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/77/artifact/glusterfs-5.3.sha512sum
>
On 1/17/19 11:08 AM, Niels de Vos wrote:
> On Wed, Jan 16, 2019 at 08:49:38PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/78/artifact/glusterfs-4.1.7.tar.gz
>> HASH:
>>
On 12/13/18 6:05 AM, Niels de Vos wrote:
> On Thu, Dec 13, 2018 at 02:42:17AM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/76/artifact/glusterfs-5.2.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/76/artifact/glusterfs-5.2.sha512sum
>
On 12/13/18 2:13 PM, Lindolfo Meira wrote:
> Links for OpenSUSE Leap packages never work :/
I assume you are trying the link at [3]
IOW,
http://download.opensuse.org/repositories/home:/glusterfs:/Leap15-5/openSUSE_Leap_15/
That did not take me anywhere as well, but on backtracking the right
We need the following projects tagged as well,
1) Glusterd2:
@Kaushal I see https://github.com/gluster/glusterd2/tree/v5.0.0-rc0 is
this the one?
We need to version this 5.0rc0 as we are now in a different versioning
scheme for GlusterFS.
2) gfapi-python: This needs to be py3 compliant as
e, Mar 19, 2019 at 10:58 AM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote:
>
> On 3/16/19 2:03 AM, Kaleb Keithley wrote:
> > Packages for the CentOS Storage SIG are now available for testing.
> > Please try them out and report test results on this l
On 3/28/19 8:05 AM, Niels de Vos wrote:
> On Wed, Mar 27, 2019 at 10:12:28PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/84/artifact/glusterfs-4.1.8.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/84/artifact/glusterfs-4.1.8.sha512sum
On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
> Hi,
>
> We had a critical bug [1], that got introduced in gluster release 5.
> There are users waiting on an update with the fix. Hence requesting for
> an out of band release for 5.6. Myself and jiffin, volunteer to do some
> tasks of the
d
> attached to the release tracker, otherwise we'll regress!
>
> On Tue, Feb 26, 2019 at 5:00 PM Milind Changire <mailto:mchan...@redhat.com>> wrote:
>
> On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan
> mailto:srang...@redhat.com>> wrote:
>
&g
On 2/27/19 5:19 AM, Niels de Vos wrote:
> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>
On 3/5/19 10:10 AM, Sanju Rakonde wrote:
>
>
> On Tue, Mar 5, 2019 at 7:29 PM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote:
>
> On 2/27/19 5:19 AM, Niels de Vos wrote:
> > On Tue, Feb 26, 2019 at 02:47:30PM +,
> jenk.
Du/Milind/Nithya?
3) Title: flooding of "dict is NULL" logging & crash of client process
https://bugzilla.redhat.com/show_bug.cgi?id=1671603
Still in NEW state, Du/Amar, do we have a date for resolution?
Thanks,
Shyam
On 2/18/19 10:13 AM, Shyam Ranganathan wrote:
> We have mo
out as usual.
NOTE: As some users have picked up 5.4 the announce would also carry a
notice, that they need to do a downserver upgrade to the latest bits
owing to the patches that have landed in addition to the existing content.
Thanks,
Shyam
On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> On 2/27/1
We need to tag different commit may be? So the 'git checkout
> v5.4' points to the correct commit?
>
> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan,
> mailto:srang...@redhat.com>> wrote:
>
> Niels, Kaleb,
On 4/11/19 9:58 AM, Patrick Matthäi wrote:
>
> Am 08.04.2019 um 16:04 schrieb Shyam Ranganathan:
>> On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
>>> Hi,
>>>
>>> We had a critical bug [1], that got introduced in gluster release 5.
>>> There ar
On 4/11/19 9:57 AM, Shyam Ranganathan wrote:
> On 4/9/19 9:37 AM, Niels de Vos wrote:
>> On Tue, Apr 09, 2019 at 11:56:31AM +, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/release-new/85/artifact/glusterfs-5.6.tar.gz
>>> HASH
On 4/18/19 3:40 AM, Niels de Vos wrote:
> On Wed, Apr 17, 2019 at 06:30:46PM +, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/86/artifact/glusterfs-6.1.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/86/artifact/glusterfs-6.1.sha512sum
>
On 3/13/19 10:44 AM, Shyam Ranganathan wrote:
> On 3/13/19 9:09 AM, Kaleb Keithley wrote:
>> The v5.4 tag was made and a release job was run which gave us
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz.
>> If the v5.4 tag is moved then there's
49 matches
Mail list logo
