From rkanade at redhat.com Thu Nov 2 15:47:27 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Thu, 2 Nov 2017 21:17:27 +0530 Subject: [Tendrl-devel] Fwd: tendrl-release v1.5.4 is available In-Reply-To: References: Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.4 Install docs: https://github.com/Tendrl/documentation/wiki/ Tendrl-release-v1.5.4-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics From mbukatov at redhat.com Thu Nov 2 16:14:39 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Thu, 2 Nov 2017 17:14:39 +0100 Subject: [Tendrl-devel] Fwd: tendrl-release v1.5.4 is available In-Reply-To: References: Message-ID: Hi Rohan, On 11/02/2017 04:47 PM, Rohan Kanade wrote: > The Tendrl team is happy to present tendrl-release v1.5.4 > > Install docs: https://github.com/Tendrl/documentation/wiki/ > Tendrl-release-v1.5.4-(install-guide) > > Metrics: https://github.com/Tendrl/documentation/wiki/Metrics I noticed one problem with the docs: the v1.5.4 install guide is based on previous guide for v1.5.3, but it should be based on current state of Tendrl-release-latest instead, becase I did all my changes to Tendrl-release-latest.md file to not distrupt already released 1.5.3 docs. Using v1.5.3 docs as a based for v1.5.4 will miss all the updates I did there. Could you review Tendrl-release-latest and use it as a base for Tendrl-release-v1.5.4-(install-guide)? I haven't done this myself for tendrl-core group to have a chance to review Tendrl-release-latest before this change. -- Martin Bukatovic USM QE team Red Hat From tjeyasin at redhat.com Thu Nov 2 18:33:59 2017 From: tjeyasin at redhat.com (Timothy Asir Jeyasingh) Date: Fri, 3 Nov 2017 00:03:59 +0530 Subject: [Tendrl-devel] OOO: I will be leaving early around 5:30 PM tomorrow Message-ID: Hi All, I will be traveling to my native place tomorrow evening. I will not be available after 5:30 PM tomorrow. I will be available from 7:30 AM to 5:30 PM tomorrow. Regards, Tim From mbukatov at redhat.com Mon Nov 6 09:55:59 2017 From: mbukatov at redhat.com (Martin Bukatovic) Date: Mon, 6 Nov 2017 10:55:59 +0100 Subject: [Tendrl-devel] Fwd: tendrl-release v1.5.4 is available In-Reply-To: References: Message-ID: <339a2365-0dd2-13e2-da21-254f05318772@redhat.com> On 11/02/2017 05:14 PM, Martin Bukatovic wrote: > Could you review Tendrl-release-latest and use it as a base for > Tendrl-release-v1.5.4-(install-guide)? I haven't done this myself > for tendrl-core group to have a chance to review Tendrl-release-latest > before this change. Thanks for the fix, the guide here: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.4-(install-guide) is now up to date. -- Martin Bukatovic USM QE team Red Hat From rkanade at redhat.com Fri Nov 10 11:05:14 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Fri, 10 Nov 2017 16:35:14 +0530 Subject: [Tendrl-devel] tendrl-release v1.5.4 (bugfixes) is available Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.4 (bugfixes) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.4-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics From dnarayan at redhat.com Fri Nov 10 11:10:44 2017 From: dnarayan at redhat.com (Darshan Narayana Murthy) Date: Fri, 10 Nov 2017 06:10:44 -0500 (EST) Subject: [Tendrl-devel] List of Alerts and Notifications in Tendrl In-Reply-To: <997398073.29506056.1510312013240.JavaMail.zimbra@redhat.com> Message-ID: <1294436468.29506708.1510312244756.JavaMail.zimbra@redhat.com> Hi all, Here https://github.com/Tendrl/documentation/wiki/List-of-Alerts-and-Notifications-in-Tendrl is the document that captures list of alerts and notifications that are raised by tendrl. Regards, Darshan N From rkanade at redhat.com Tue Nov 14 08:15:58 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Tue, 14 Nov 2017 13:45:58 +0530 Subject: [Tendrl-devel] Changes to Tendrl Governance and Community Message-ID: Hello, Tendrl is growing at a fast pace.To ensure consistent progress, we would like to announce few changes related to Tendrl components and their maintainers. - tendrl-monitoring-integration will be maintained by Shubhendu and Gowtham from now on. - tendrl-gluster-integration will be maintained by Darshan and Shubhendu - tendrl-node-agent will be maintained by Me (Rohan) and Darshan. No changes to other components. For more details: https://github.com/Tendrl/documentation/wiki/Tendrl-Governance-and-Community Regards, Rohan Kanade From anbabu at redhat.com Tue Nov 14 08:20:11 2017 From: anbabu at redhat.com (Anmol Babu) Date: Tue, 14 Nov 2017 13:50:11 +0530 Subject: [Tendrl-devel] Changes to Tendrl Governance and Community In-Reply-To: References: Message-ID: Congratulations Gowtham, Darshan and Shubhendu !!! Thanks and Regards, ANMOL BABU SOFTWARE ENGINEER Red Hat India Pvt Ltd M: 8884245644 On Tue, Nov 14, 2017 at 1:45 PM, Rohan Kanade wrote: > Hello, > > Tendrl is growing at a fast pace.To ensure consistent progress, we would > like to announce few changes related to Tendrl components and their > maintainers. > > - tendrl-monitoring-integration will be maintained by Shubhendu and Gowtham > from now on. > > - tendrl-gluster-integration will be maintained by Darshan and Shubhendu > > - tendrl-node-agent will be maintained by Me (Rohan) and Darshan. > > > No changes to other components. > > > For more details: > https://github.com/Tendrl/documentation/wiki/Tendrl- > Governance-and-Community > > Regards, > Rohan Kanade > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From rkanade at redhat.com Tue Nov 14 08:20:41 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Tue, 14 Nov 2017 13:50:41 +0530 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 Message-ID: Hello, Please join me for the Tendrl planning meeting. Date: 15-Nov-2017 Time: 1415-1615 hrs (Indian standard time) Agenda: - Tendrl beyond 1.5.x, project roadmap - Per component roadmap discussion - Open discussion From rkanade at redhat.com Tue Nov 14 11:35:34 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Tue, 14 Nov 2017 17:05:34 +0530 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 In-Reply-To: References: Message-ID: To join the Tendrl planning meeting, please use link : https://bluejeans.com/223603813 On Tue, Nov 14, 2017 at 1:50 PM, Rohan Kanade wrote: > Hello, > > Please join me for the Tendrl planning meeting. > > Date: 15-Nov-2017 > Time: 1415-1615 hrs (Indian standard time) > > Agenda: > - Tendrl beyond 1.5.x, project roadmap > - Per component roadmap discussion > - Open discussion > From jefbrown at redhat.com Tue Nov 14 12:19:18 2017 From: jefbrown at redhat.com (Jeff Brown) Date: Tue, 14 Nov 2017 07:19:18 -0500 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 In-Reply-To: References: Message-ID: Hi Rohan, I'd like to be a part of this and have quite a few recommendations moving forward. Can we make his a bit later in your day. 3:45 is a bit early. Even 6:00am EST is OK. Thanks, Jeff On Tue, Nov 14, 2017 at 6:35 AM, Rohan Kanade wrote: > To join the Tendrl planning meeting, please use link : > https://bluejeans.com/223603813 > > On Tue, Nov 14, 2017 at 1:50 PM, Rohan Kanade wrote: > > > Hello, > > > > Please join me for the Tendrl planning meeting. > > > > Date: 15-Nov-2017 > > Time: 1415-1615 hrs (Indian standard time) > > > > Agenda: > > - Tendrl beyond 1.5.x, project roadmap > > - Per component roadmap discussion > > - Open discussion > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From julim at redhat.com Tue Nov 14 12:23:12 2017 From: julim at redhat.com (Ju Lim) Date: Tue, 14 Nov 2017 07:23:12 -0500 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 In-Reply-To: References: Message-ID: Rohan: A later start would be preferable for me too if possible as I'd like to participate. I'm okay with it from 5am EST (3:30pm IST) onwards. Thank you, Ju On Tue, Nov 14, 2017 at 7:19 AM, Jeff Brown wrote: > Hi Rohan, > > I'd like to be a part of this and have quite a few recommendations moving > forward. Can we make his a bit later in your day. 3:45 is a bit early. > Even 6:00am EST is OK. > > Thanks, > > Jeff > > > On Tue, Nov 14, 2017 at 6:35 AM, Rohan Kanade wrote: > > > To join the Tendrl planning meeting, please use link : > > https://bluejeans.com/223603813 > > > > On Tue, Nov 14, 2017 at 1:50 PM, Rohan Kanade > wrote: > > > > > Hello, > > > > > > Please join me for the Tendrl planning meeting. > > > > > > Date: 15-Nov-2017 > > > Time: 1415-1615 hrs (Indian standard time) > > > > > > Agenda: > > > - Tendrl beyond 1.5.x, project roadmap > > > - Per component roadmap discussion > > > - Open discussion > > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From rkanade at redhat.com Tue Nov 14 12:59:02 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Tue, 14 Nov 2017 18:29:02 +0530 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 In-Reply-To: References: Message-ID: To accommodate participants from EST The Tendrl planning meeting will be held from *1630-1830 hrs IST on 15-Nov-2017* To join the Tendrl planning meeting, please use link : https://bluejeans.com/223603813 On Tue, Nov 14, 2017 at 5:53 PM, Ju Lim wrote: > Rohan: > > A later start would be preferable for me too if possible as I'd like to > participate. I'm okay with it from 5am EST (3:30pm IST) onwards. > > Thank you, > Ju > > > On Tue, Nov 14, 2017 at 7:19 AM, Jeff Brown wrote: > > > Hi Rohan, > > > > I'd like to be a part of this and have quite a few recommendations moving > > forward. Can we make his a bit later in your day. 3:45 is a bit early. > > Even 6:00am EST is OK. > > > > Thanks, > > > > Jeff > > > > > > On Tue, Nov 14, 2017 at 6:35 AM, Rohan Kanade > wrote: > > > > > To join the Tendrl planning meeting, please use link : > > > https://bluejeans.com/223603813 > > > > > > On Tue, Nov 14, 2017 at 1:50 PM, Rohan Kanade > > wrote: > > > > > > > Hello, > > > > > > > > Please join me for the Tendrl planning meeting. > > > > > > > > Date: 15-Nov-2017 > > > > Time: 1415-1615 hrs (Indian standard time) > > > > > > > > Agenda: > > > > - Tendrl beyond 1.5.x, project roadmap > > > > - Per component roadmap discussion > > > > - Open discussion > > > > > > > _______________________________________________ > > > Tendrl-devel mailing list > > > Tendrl-devel at redhat.com > > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > > > _______________________________________________ > > Tendrl-devel mailing list > > Tendrl-devel at redhat.com > > https://www.redhat.com/mailman/listinfo/tendrl-devel > > > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel > From mrugesh at brainfunked.org Tue Nov 14 12:59:18 2017 From: mrugesh at brainfunked.org (Mrugesh Karnik) Date: Tue, 14 Nov 2017 18:29:18 +0530 Subject: [Tendrl-devel] Tendrl planning meeting 15-Nov-2017 In-Reply-To: References: Message-ID: Now that the foundations have been laid, there are a few areas where I'd like to see tendrl improve in. Moving forward, I propose maintaining the current line of 1.x codebase for the gluster 3.x releases and in parallel starting work on the 2.x codebase for gluster 4.x releases. However, the latter needs more clarity and conversations with gluster at this point and so, for this particular planning phase, I propose that we focus on the following: Enhancements to the currently supported deployment scenarios: * Standard deployments: bare-metal or virtualised. This is the currently supported default scenario. However, we should look at how we can make the deployment composable by properly modularising our existing components and formalising some interfaces (monitoring-integration especially) by allowing custom integrations with other infrastructure components for monitoring, logging etc. * Co-located deployments. In this scenario, we need to be able to co-locate the tendrl server components with gluster nodes. The architecture already supports this, but we need to explicitly test out co-location scenarios. This scenario may require additional performance optimisation as well. Additionally, in a gluster deployment, all gluster nodes are treated as equal in terms of their role in the cluster. We need to specifically support and test out scenarios for being able to dynamically relocate tendrl components from a failed gluster node to another. General feature additions: * Improve the monitoring and alerting functionality. We need to look at whether we can shave off some latency from the notifications. We also need to support more granular configuration of the alert destination and the corresponding filtering of the alerts based on the metadata. As mentioned above, monitoring-integration could use some modulerisation to be able to support different types of monitoring systems such as prometheus. Prometheus' alert manager also needs to be re-considered as a (stand-alone) replacement for our notifier since it seems to already provide some of the functionality we'd like to in our notifier. * Bringing back the provisioning and management features. We had coded and (partially?) tested these. Would this be a good time to start re-incorporating these old features back into the 1.5.x codebase? This time, however, it would be good to focus on a specific use case and make the features available to support that use case fully. This leads to the next point.. * Supporting networked file system protocols such as NFS and Samba. We could look at supporting a use case for Windows administrators who would want to be able to consume gluster volumes mounted via Samba. We need to expand on this use case with details that enable us to plan the re-incorporation of the management features. User interface: * In terms of the UI, one critical part missing is the complete lack of health and deployment information about the tendrl components themselves. * Our current UI caters to an end user who wants to manually look at and manage the nitty-gritties of a gluster, including volume and brick configuration. If we are to serve a user such as a Windows admin, we need to look at providing a storage management UI, rather than a gluster management UI. This means that we need to shift our focus to be able to cater to 'how do I provide to be consumed over for quickly and painlessly.' This involves a higher level management view that takes away the necessity to micro-manage the deployment via our current cluster context. -- Mrugesh On 14 November 2017 at 13:50, Rohan Kanade wrote: > Hello, > > Please join me for the Tendrl planning meeting. > > Date: 15-Nov-2017 > Time: 1415-1615 hrs (Indian standard time) > > Agenda: > - Tendrl beyond 1.5.x, project roadmap > - Per component roadmap discussion > - Open discussion > _______________________________________________ > Tendrl-devel mailing list > Tendrl-devel at redhat.com > https://www.redhat.com/mailman/listinfo/tendrl-devel From rkanade at redhat.com Fri Nov 17 19:19:36 2017 From: rkanade at redhat.com (Rohan Kanade) Date: Sat, 18 Nov 2017 00:49:36 +0530 Subject: [Tendrl-devel] tendrl-release v1.5.4 (bugfixes-2) is available Message-ID: Hello, The Tendrl team is happy to present tendrl-release v1.5.4 (bugfixes-2) Install docs: https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.5.4-(install-guide) Metrics: https://github.com/Tendrl/documentation/wiki/Metrics From ndevos at redhat.com Wed Nov 22 17:01:48 2017 From: ndevos at redhat.com (Niels de Vos) Date: Wed, 22 Nov 2017 18:01:48 +0100 Subject: [Tendrl-devel] Fwd: FOSDEM Call for Participation: Software Defined Storage devroom In-Reply-To: <20171018104246.GD2476@ndevos-x240.usersys.redhat.com> References: <20171018104246.GD2476@ndevos-x240.usersys.redhat.com> Message-ID: <20171122170148.GD5346@ndevos-x270> Reminder! The Call for Participation ends later this week. There is still time to propose talks. A Tendrl demonstration would be most awesome too! On Wed, Oct 18, 2017 at 12:42:46PM +0200, Niels de Vos wrote: > ----- Forwarded message from Jan Fajerski ----- > > > Date: Thu, 12 Oct 2017 12:55:28 +0200 > > From: Jan Fajerski > > To: ceph-devel at vger.kernel.org, ceph-users at ceph.com, gluster-users at gluster.org > > Cc: devroom-managers at lists.fosdem.org, fosdem at lists.fosdem.org > > Subject: [Gluster-users] FOSDEM Call for Participation: Software Defined Storage devroom > > > > > > CfP for the Software Defined Storage devroom at FOSDEM 2018 > > (Brussels, Belgium, February 4th). > > > > FOSDEM is a free software event that offers open source communities a place to > > meet, share ideas and collaborate. It is renown for being highly developer- > > oriented and brings together 8000+ participants from all over the world. It > > is held in the city of Brussels (Belgium). > > > > FOSDEM 2018 will take place during the weekend of February 3rd-4th 2018. More > > details about the event can be found at http://fosdem.org/ > > > > ** Call For Participation > > > > The Software Defined Storage devroom will go into it's second round for > > talks around Open Source Software Defined Storage projects, management tools > > and real world deployments. > > > > Presentation topics could include but are not limited too: > > > > - Your work on a SDS project like Ceph, GlusterFS or LizardFS > > > > - Your work on or with SDS related projects like SWIFT or Container Storage > > Interface > > > > - Management tools for SDS deployments > > > > - Monitoring tools for SDS clusters > > > > ** Important dates: > > > > - 26 Nov 2017: submission deadline for talk proposals > > - 15 Dec 2017: announcement of the final schedule > > - 4 Feb 2018: Software Defined Storage dev room > > > > Talk proposals will be reviewed by a steering committee: > > - Leonardo Vaz (Ceph Community Manager - Red Hat Inc.) > > - Joao Luis (Core Ceph contributor - SUSE) > > - Jan Fajerski (Ceph Developer - SUSE) > > > > Use the FOSDEM 'pentabarf' tool to submit your proposal: > > https://penta.fosdem.org/submission/FOSDEM18 > > > > - If necessary, create a Pentabarf account and activate it. > > Please reuse your account from previous years if you have > > already created it. > > > > - In the "Person" section, provide First name, Last name > > (in the "General" tab), Email (in the "Contact" tab) > > and Bio ("Abstract" field in the "Description" tab). > > > > - Submit a proposal by clicking on "Create event". > > > > - Important! Select the "Software Defined Storage devroom" track > > (on the "General" tab). > > > > - Provide the title of your talk ("Event title" in the "General" tab). > > > > - Provide a description of the subject of the talk and the > > intended audience (in the "Abstract" field of the "Description" tab) > > > > - Provide a rough outline of the talk or goals of the session (a short > > list of bullet points covering topics that will be discussed) in the > > "Full description" field in the "Description" tab > > > > - Provide an expected length of your talk in the "Duration" field. Please > > count at least 10 minutes of discussion into your proposal. > > > > Suggested talk length would be 15, 20+10, 30+15, and 45+15 minutes. > > > > ** Recording of talks > > > > The FOSDEM organizers plan to have live streaming and recording fully working, > > both for remote/later viewing of talks, and so that people can watch streams > > in the hallways when rooms are full. This requires speakers to consent to > > being recorded and streamed. If you plan to be a speaker, please understand > > that by doing so you implicitly give consent for your talk to be recorded and > > streamed. The recordings will be published under the same license as all > > FOSDEM content (CC-BY). > > > > Hope to hear from you soon! And please forward this announcement. > > _______________________________________________ > > Gluster-users mailing list > > Gluster-users at gluster.org > > http://lists.gluster.org/mailman/listinfo/gluster-users > > ----- End forwarded message ----- From sarumuga at redhat.com Wed Nov 29 14:03:30 2017 From: sarumuga at redhat.com (Saravanakumar Arumugam) Date: Wed, 29 Nov 2017 19:33:30 +0530 Subject: [Tendrl-devel] Monitoring support in Container Native Storage(CNS) using Tendrl Message-ID: Hi, Tendrl provides monitoring and many other features for GlusterFS. (more here: http://tendrl.org) In order to get monitoring support for CNS, I have integrated tendrl-node-agent as part of gluster containers. You can see the Dockerfile changes in this PR: https://github.com/gluster/gluster-containers/pull/60 There are two main components in Tendrl - 1. Tendrl Server 2. Tendrl Storage node More here : https://github.com/Tendrl/documentation/wiki/Tendrl-release-latest #1 First setup Tendrl Server in a separate node. Refer above link for installation. This consists of multiple services like: etcd tendrl-monitoring-integration tendrl-api tendrl-notifier carbon-cache grafana-server tendrl-node-agent httpd #2 Then, you can build and run the Tendrl Storage node docker container as below: // Build cd Centos/ docker build -t gluster-centos-tendrl *.* // Run docker run -v /etc/glusterfs:/etc/glusterfs: z -v /var/lib/glusterd:/var/lib/glusterd:z -v /var/log/glusterfs:/var/log/glusterfs:z -v /sys/fs/cgroup:/sys/fs/cgroup:ro -d --privileged=true --net=host -v /dev/:/dev -v /etc/localtime:/etc/localtime:ro *gluster-centos-tendrl* #3 Now, You can view the entire Gluster cluster using Tendrl Server's IP address. You can monitor the Gluster volume, bricks, using the Dashboard link present. Thanks to Nishanth, Darshan and Tendrl team for their help. Thanks, Saravana