Re: [gluster-packaging] [Gluster-Maintainers] 3.7.10 known issue

[Kaushal M]

On Tue, Apr 5, 2016 at 9:23 AM, Atin Mukherjee  wrote:
>
>
> On 04/04/2016 11:10 PM, Niels de Vos wrote:
>> On Mon, Apr 04, 2016 at 08:19:30PM +0530, Atin Mukherjee wrote:
>>>
>>>
>>> On 04/04/2016 07:43 PM, Atin Mukherjee wrote:


 On 04/04/2016 06:53 PM, Kaleb KEITHLEY wrote:
> On 04/04/2016 09:11 AM, Kaleb KEITHLEY wrote:
>> On 04/04/2016 07:41 AM, Niels de Vos wrote:
>>> On Fri, Apr 01, 2016 at 09:56:45AM +0530, Atin Mukherjee wrote:
 Hi Kaushal,

 We hit a regression yesterday where GlusterD fails to restart when the
 volume has snapshots. Refer to [1] for more details. The work around is
 also a bit tedious where each snapshot brick folders have to be created
 manually and I don't think see any other alternative workaround here.
>>> One correction here, the issue is seen only when the node reboots, not
>>> glusterd. Considering that users won't reboot machines often, we can
>>> still live with it for the next scheduled release?
>>
>> No, I do not think that is acceptible. Many users will install updates
>> and do a reboot after that. Even having just a few users rebooting and
>> rendering their deployment unusable is a huge problem.
> Ok, but I was wondering how many users use snapshot? I've seen almost no
> emails related to snapshot issues in gluster-users mailing list. Anyways
> I don't have any issue in releasing 3.7.11 early.

I've got no problem with doing 3.7.11 early.
I've not announced 3.7.10 yet, so we could just announce 3.7.11 instead.

This should serve as a catalyst to get started on our planned
automated release tests.
I did to some manual testing before tagging, but I didn't cover
restarts, or snapshots.
Covering everything, every time in manual testing is not feasible.


>>
>> Niels
>>
>>> I'll be working on
>>> the release note to put down the work around.

 IMO, we should mention this as known issue in the release note for 
 3.7.10.
>>>
>>> This sounds serious enough to not package 3.7.10 and have users update
>>> to it automatically.
>>
>> That djinni is already out of the bottle.
>
> If there's a fix available then it seems (to me) that a better path
> forward is to release 3.7.11 quickly.
 Patch http://review.gluster.org/#/c/13869 is under review.
>
> --
>
> Kaleb
>
>
 ___
 maintainers mailing list
 maintain...@gluster.org
 http://www.gluster.org/mailman/listinfo/maintainers

>>> ___
>>> maintainers mailing list
>>> maintain...@gluster.org
>>> http://www.gluster.org/mailman/listinfo/maintainers
> ___
> maintainers mailing list
> maintain...@gluster.org
> http://www.gluster.org/mailman/listinfo/maintainers
___
packaging mailing list
packaging@gluster.org
http://www.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.7.20 released

[Kaushal M]

On Mon, Jan 30, 2017 at 8:54 PM, Niels de Vos  wrote:
> On Mon, Jan 30, 2017 at 06:30:26AM -0800, Gluster Build System wrote:
>>
>>
>> SRC: 
>> http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.20.tar.gz
>
> Packages for the CentOS Storage SIG are being build and should land in
> the centos-gluster37-test repository shortly.
>
> Let me know when they have been tested a little and I can mark them for
> release.

I did a quick test. The packages install fine and upgrade fine. I did
a rolling upgrade with a replica 3 volume which worked well.
+1 for release.

>
> Niels
>
> ___
> maintainers mailing list
> maintain...@gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
>
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.7.18 released

[Kaushal M]

On Mon, Dec 12, 2016 at 12:35 PM, Niels de Vos  wrote:
> On Thu, Dec 08, 2016 at 04:17:59AM -0500, Kaleb Keithley wrote:
>>
>> Packages for Fedora 23 are queued for testing in Bodhi; will land soon in 
>> Updates-Testing and then Updates repos.
>> Packages for Fedora 24 and Fedora 25 are on download.gluster.org
>> Packages for Fedora 26 (rawhide) will be available soon on 
>> download.gluster.org pending resolution of a build issue.
>>
>> Packages for RHEL/CentOS 5, 6, and 7 are on download.gluster.org, and will 
>> also be available soon in the CentOS Storage SIG.
>
> Packages for the CentOS Storage SIG have been available in the testing
> repository for a couple of days now. I can mark them as released and
> have them pushed to the mirrors if someone agrees with that.

+1 to do this. I'll be making the announcement today.

>
> Thanks,
> Niels
>
>
>>
>> Packages for Debian Wheezy/7, Jessie/8, and Stretch/9 are on 
>> download.gluster.org.
>>
>> Packages for Ubuntu Trusty/14.04, Wily/15/10, and Xenial/16.04 are in the 
>> Ubuntu Launchpad PPA.
>>
>> Packages for SuSE will be available soon.
>>
>> The .../glusterfs/LTM-3.7 and .../glusterfs/3.7/LATEST symlinks on 
>> download.gluster.org have been set to 3.7.18
>>
>>
>>
>>
>> - Original Message -
>> > From: "Gluster Build System" 
>> > To: sbair...@redhat.com, maintain...@gluster.org, packaging@gluster.org
>> > Sent: Wednesday, December 7, 2016 2:01:48 PM
>> > Subject: [gluster-packaging] glusterfs-3.7.18 released
>> >
>> >
>> >
>> > SRC:
>> > http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.18.tar.gz
>> >
>> > This release is made off jenkins-release-178
>> >
>> > -- Gluster Build System
>> > ___
>> > packaging mailing list
>> > packaging@gluster.org
>> > http://www.gluster.org/mailman/listinfo/packaging
>> >
>> ___
>> packaging mailing list
>> packaging@gluster.org
>> http://www.gluster.org/mailman/listinfo/packaging
> ___
> maintainers mailing list
> maintain...@gluster.org
> http://www.gluster.org/mailman/listinfo/maintainers
___
packaging mailing list
packaging@gluster.org
http://www.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.7.19 released

[Kaushal M]

On Mon, Jan 9, 2017 at 9:41 PM, Niels de Vos  wrote:
> On Mon Jan 9 16:57:02 2017 GMT+0100, Kaleb S. KEITHLEY wrote:
>> On 01/09/2017 01:44 AM, Gluster Build System wrote:
>> >
>> >
>> > SRC: 
>> > http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.7.19.tar.gz
>> >
>> > This release is made off jenkins-release-180
>>
>> packages for everything (excepting CentOS Storage SIG) listed at
>> http://gluster.readthedocs.io/en/latest/Install-Guide/Community_Packages/
>> are available now at their respective locations.
>
> Packages for the CentOS Storage SIG are in the "centos-gluster37-test" 
> repository. Let me know when they should be marked for releasing as an update.

They install and upgrade okay. Simple volume IO works. This can be
marked for release.

>
> Niels
>
> --
> Sent from my Jolla w/ the Open Source friendly services from kolabnow.com
> ___
> packaging mailing list
> packaging@gluster.org
> http://www.gluster.org/mailman/listinfo/packaging
___
packaging mailing list
packaging@gluster.org
http://www.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] Release 4.0: Making it happen! (GlusterD2)

[Kaushal M]

On Thu, Jan 11, 2018 at 1:56 AM, Kaleb S. KEITHLEY  wrote:
> comments inline
>
> On 01/10/2018 02:08 PM, Shyam Ranganathan wrote:
>
> 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:
>   - GD2 makes github releases, as in [1]
>
>   - GD2 Releases (tagging etc.) are made in tandem to Gluster releases
> - So, when an beta1/RC0 is tagged for gluster release, this will
> receive a coordinated release (if required) from the GD2 team
> - GD2 team will receive *at-least* a 24h notice on a tentative
> Gluster tagging date/time, to aid the GD2 team to prepare the required
> release tarball in github
>
> This is a no-op. In github creating a tag or a release automatically creates
> the tar source file.

While true, this tarball isn't enough. The GD2 build scripts lookup
versioning from git tags or from a VERSION file (same as glusterfs).
Both of these are not present in the tarball github generates.
The GD2 release script generates tarballs that have everything
required to build a properly versioned GD2.

>
>   - Post a gluster tag being created, and the subsequent release job is
> run for gluster 4.0, the packaging team will be notified about which GD2
> tag to pick up for packaging, with this gluster release
> - IOW, a response to the Jenkins generated packaging job, with the
> GD2 version/tag/release to pick up
>
>   - GD2 will be packaged as a sub-package of the glusterfs package, and
> hence will have appropriate changes to the glusterfs spec file (or other
> variants of packaging as needed), to generate one more package (RPM) to
> post in the respective download location
>
>   - The GD2 sub-package version would be the same as the release version
> that GD2 makes (it will not be the gluster package version, at least for
> now)
>
> IMO it's clearer if the -glusterd2 sub-package has the same version as the
> rest of the glusterfs-* packages.
>

+1. We will follow glusterfs versioning not just for the packages, but
for the source itself.

> The -glusterd2 sub-package's Summary and/or its %description can be used to
> identify the version of GD2.
>
> Emphasis on IMO. It is possible for the -glusterd sub-package to have a
> version that's different than the parent package(s).
>
>   - For now, none of the gluster RPMs would be dependent on the GD2 RPM
> in the downloads, so any user wanting to use GD2 would have to install
> the package specifically and then proceed as needed
>
>   - (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 to additionally build GD2)
>
> 2) Generate a quick start or user guide, to aid using GD2 with 4.0
>
> @Kaushal if this is generated earlier (say with beta builds of 4.0
> itself) we could get help from the community to test drive the same and
> provide feedback to improve the guide for users by the release (as
> discussed in the maintainers meeting)
>
> One thing not covered above is what happens when GD2 fixes a high priority
> bug between releases of glusterfs.
>
> Once option is we wait until the next release of glusterfs to include the
> update to GD2.
>
> Or we can respin (rerelease) the glusterfs packages with the updated GD2.
> I.e. glusterfs-4.0.0-1 (containing GD2-1.0.0) -> glusterfs-4.0.0-2
> (containing GD2-1.0.1).
>
> Or we can decide not to make a hard rule and do whatever makes the most
> sense at the time. If the fix is urgent, we respin. If the fix is not urgent
> it waits for the next Gluster release. (From my perspective though I'd
> rather not do respins, I've already got plenty of work doing the regular
> releases.)
>
> The alternative to all of the above is to package GD2 in its own package.
> This entails opening a New Package Request and going through the packaging
> reviews. All in all it's a lot of work. If GD2 source is eventually going to
> be moved into the main glusterfs source though this probably doesn't make
> sense.
>
> --
>
> Kaleb
>
>
>
>
> ___
> packaging mailing list
> packaging@gluster.org
> http://lists.gluster.org/mailman/listinfo/packaging
>
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] Release 4.0: Making it happen! (GlusterD2)

[Kaushal M]

On Thu, Jan 11, 2018 at 12:38 AM, Shyam Ranganathan  wrote:
> 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:
>   - GD2 makes github releases, as in [1]
>
>   - GD2 Releases (tagging etc.) are made in tandem to Gluster releases
> - So, when an beta1/RC0 is tagged for gluster release, this will
> receive a coordinated release (if required) from the GD2 team
> - GD2 team will receive *at-least* a 24h notice on a tentative
> Gluster tagging date/time, to aid the GD2 team to prepare the required
> release tarball in github

Sounds good.

>
>   - Post a gluster tag being created, and the subsequent release job is
> run for gluster 4.0, the packaging team will be notified about which GD2
> tag to pick up for packaging, with this gluster release
> - IOW, a response to the Jenkins generated packaging job, with the
> GD2 version/tag/release to pick up
>
>   - GD2 will be packaged as a sub-package of the glusterfs package, and
> hence will have appropriate changes to the glusterfs spec file (or other
> variants of packaging as needed), to generate one more package (RPM) to
> post in the respective download location
>
>   - The GD2 package version would be the same as the release version
> that GD2 makes (it will not be the gluster package version, at least for
> now)

I prefer if GD2 follows gluster versioning. Keeps things simpler.
Anyone packaging will have to just pick the same version of GD2.
We already version our perview releases as v4.0dev.

>
>   - For now, none of the gluster RPMs would be dependent on the GD2 RPM
> in the downloads, so any user wanting to use GD2 would have to install
> the package specifically and then proceed as needed

Yes. The glusterfs-server package will not depend on GD2 right now.
This will be changed later when GD2 becomes the default.

>
>   - (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 to additionally build GD2)

The glusterfs spec file can be updated to include building GD2 from
its release tarball. I don't remember exactly but, rpmbuild might have
ways to automatically download sources/dependencies. We can check if
this is true.

>
> 2) Generate a quick start or user guide, to aid using GD2 with 4.0
>
> @Kaushal if this is generated earlier (say with beta builds of 4.0
> itself) we could get help from the community to test drive the same and
> provide feedback to improve the guide for users by the release (as
> discussed in the maintainers meeting).

We will do this.

>
> Thanks,
> Shyam
>
> [1] github GD2 releases: https://github.com/gluster/glusterd2/releases
> ___
> packaging mailing list
> packaging@gluster.org
> http://lists.gluster.org/mailman/listinfo/packaging
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging

[gluster-packaging] GlusterD2 v4.0rc0 tagged

[Kaushal M]

Hi all,

GlusterD2 v4.0rc0 has been tagged and a release made in anticipation
of GlusterFS-v4.0rc0. The release and source tarballs are available
from [1].

There aren't any sepcific release-notes for this release.

Thanks.
~kaushal

[1]: https://github.com/gluster/glusterd2/releases/tag/v4.0rc0
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released

[Kaushal M]

On Tue, Mar 6, 2018 at 8:59 PM, Shyam Ranganathan  wrote:
> 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 outs!
>
> 1) @kaushal GD2 tags for GA need to be created and shared (if not
> already done)

Done. https://github.com/gluster/glusterd2/releases/tag/v4.0.0

>
> 2) @humble Once the packages are created for CentOS SIG, and validated
> (usually by me), you would need to crank out the container images
>
> Thanks!
>
>>
>>
>>
>> ___
>> maintainers mailing list
>> maintain...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/maintainers
>>
> ___
> maintainers mailing list
> maintain...@gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging

Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released

[Kaushal M]

On Tue, Mar 6, 2018 at 9:19 PM, Kaushal M <kshlms...@gmail.com> wrote:
> On Tue, Mar 6, 2018 at 8:59 PM, Shyam Ranganathan <srang...@redhat.com> wrote:
>> 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 outs!
>>
>> 1) @kaushal GD2 tags for GA need to be created and shared (if not
>> already done)
>
> Done. https://github.com/gluster/glusterd2/releases/tag/v4.0.0

Also, kicked off COPR builds at
https://copr.fedorainfracloud.org/coprs/kshlm/glusterd2/build/724903/

>
>>
>> 2) @humble Once the packages are created for CentOS SIG, and validated
>> (usually by me), you would need to crank out the container images
>>
>> Thanks!
>>
>>>
>>>
>>>
>>> ___
>>> maintainers mailing list
>>> maintain...@gluster.org
>>> http://lists.gluster.org/mailman/listinfo/maintainers
>>>
>> ___
>> maintainers mailing list
>> maintain...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/maintainers
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging