On 2/20/19 7:45 AM, Amar Tumballi Suryanarayan wrote: > > > On Tue, Feb 19, 2019 at 1:37 AM Shyam Ranganathan <srangana@xxxxxxxxxx > <mailto:srangana@xxxxxxxxxx>> wrote: > > In preparation for RC0 I have put up an intial patch for the release > notes [1]. Request the following actions on the same (either a followup > patchset, or a dependent one), > > - Please review! > - Required GD2 section updated to latest GD2 status > > > I am inclined to drop the GD2 section for 'standalone' users. As the > team worked with goals of making GD2 invisible with containers (GCS) in > mind. So, should we call out any features of GD2 at all? This is fine, we possibly need to add a note in the release notes, on the GD2 future and where it would land, so that we can inform users about the continued use of GD1 in non-GCS use cases. I will add some text around the same in the release-notes. > > Anyways, as per my previous email on GCS release updates, we are > planning to have a container available with gd2 and glusterfs, which can > be used by people who are trying out options with GD2. > > > - Require notes on "Reduce the number or threads used in the brick > process" and the actual status of the same in the notes > > > This work is still in progress, and we are treating it as a bug fix for > 'brick-multiplex' usecase, which is mainly required in scaled volume > number usecase in container world. My guess is, we won't have much > content to add for glusterfs-6.0 at the moment. Ack! > > > RC0 build target would be tomorrow or by Wednesday. > > > Thanks, I was testing for few upgrade and different version clusters > support. With 4.1.6 and latest release-6.0 branch, things works fine. I > haven't done much of a load testing yet. Awesome! Helps write out the upgrade guide as well. As this time content there would/should carry data regarding how to upgrade if any of the deprecated xlators are in use by a deployment. > > Requesting people to support in upgrade testing. From different volume > options, and different usecase scenarios. > > Regards, > Amar > > > > Thanks, > Shyam > > [1] Release notes patch: https://review.gluster.org/c/glusterfs/+/22226 > > On 2/5/19 8:25 PM, Shyam Ranganathan wrote: > > Hi, > > > > Release 6 is branched, and tracker bug for 6.0 is created [1]. > > > > Do mark blockers for the release against [1]. > > > > As of now we are only tracking [2] "core: implement a global > thread pool > > " for a backport as a feature into the release. > > > > We expect to create RC0 tag and builds for upgrade and other testing > > close to mid-week next week (around 13th Feb), and the release is > slated > > for the first week of March for GA. > > > > I will post updates to this thread around release notes and other > > related activity. > > > > Thanks, > > Shyam > > > > [1] Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-6.0 > > > > [2] Patches tracked for a backport: > > - https://review.gluster.org/c/glusterfs/+/20636 > > _______________________________________________ > > Gluster-devel mailing list > > Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > > https://lists.gluster.org/mailman/listinfo/gluster-devel > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > https://lists.gluster.org/mailman/listinfo/gluster-devel > > > > > -- > Amar Tumballi (amarts) _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
