On 08/13/2016 03:59 AM, Niels de Vos wrote:
In addition to Vijays request to submit talks, I would like to see some
very specific topics presented/demo'd. Anyone attending the Summit and
willing to take these on is very much encouraged to do so. To do so,
reply to this (or Vijays) email with your name and a description of the
topic.
If others would like to see other topics, please add them to the list.
Many thanks,
Niels
Practical Glusto example
- show how to install Glusto and dependencies
- write a simple new test-case from scratch (copy/paste example?)
- run the new test-case (in the development environment?)
Debugging (large) production deployments
- tools that can be used for debugging on non-development systems
- filtering logs and other data to identify problems
- coming up with the root cause of the problem
- reporting a useful bug so that developers can fix it
Making troubleshooting easier
- statedumps, how code tracks allocations, how to read the dumps
- io-stats, meta and other xlators
- useful, actionable log messages
Squashing the above 2 topics and throwing in monitoring, I would even
propose a BoF, to understand what are the current challenges and
proposed/applied solutions to the problem of "monitoring and
troubleshooting distributed systems at scale" and specifically Gluster.
For example I have some thoughts on performance monitoring at scale,
that we need to improve in Gluster. Identifying more such problems would
enable Gluster to become more easier to manage and tune.
Another problem area is in the container world, where we possibly lose
some ability to influence/troubleshoot clients and hence we may need
alternative for the same (centralized logging? server side state dump
collection from clients? server side monitoring/collection of client
performance (and other) metrics? What else). This could also be factored
into the discussions.
Long-Term-Maintenance, Short-Term-Maintanance, releases and backports
- explanation of the new release schedule
- when/how are releases made, branching, stability phase etc...
- the kind of backports that are acceptible and safe for minor updates
Documentation update
- new Documentation Tooling based on ASCIIbinder
- how to migrate different documentation sites for many of the projects
- best location to report issues, submit fixes etc...
_______________________________________________
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