On Wed, Nov 14, 2018 at 7:08 PM Nathan Stratton Treadway <[email protected]> wrote:
> On Wed, Nov 14, 2018 at 15:35:50 -0500, Chris Nighswonger wrote: > > Can anyone point me to "good" documentation that describes Amanda's DB? > > Things like schema, field descriptions and/or uses, etc. > > [snip] > > > I notice that the later versions of ZWC use SQL. > > I saw that the Amanda source repository master branch includes the > following commit: > > commit ea4dd29d265b44a914e794d5150e53bce9d9435d > Author: Jean-Louis Martineau <[email protected]> > Date: Thu Jan 4 12:52:28 2018 +0000 > > Use a database (SQLite, MySQL or ProstgreSQL) to replace the tapelist > and log.* file > Read the Amanda-Catalog file > * perl/*, server-src/*, common-src/conffile.c: Major changes > * installcheck/*: Fix tests > * Amanda-Catalog: New documentation document > > Jan 2018 is after Amanda 3.5 was released so this is still > work-in-progress, and I don't know how "mature" this transition got > before Jean-Louis left.... > Digging a bit in the new Catalog code.... The style makes for difficult reading. Clearly what docs there are show that work was being done on SQLite. The DB schema is not readily apparent. It seems to me that Amanda is heavily dependent upon its logs to coordinate and keep it running. It would be very nice to have a solid set of docs outlining the log syntax for each log and describing the various roles of each log in the overall scheme of Amanda's operation. Without some sort of understanding of the larger picture of how things operate, its going to be mighty difficult picking up and moving forward with development. I have been involved in development (thousands of lines of code) and project management of another large OSS package written primarily in Perl. I am certainly willing to contribute to Amanda, but the "activation energy" (aka learning curve) appears way too high at the moment. I think when Dustin left, the end of true open development in Amanda left with him. My $0.02 worth. Kind regards, Chris
