I will have a look at the other tickets over this week/weekend and close them as well, and make a list of tickets that needs to be actioned to reach completion on the dbbackups kanban board.

Hi @Gopavasanth, while the GSoC MVP is finished, there is a "lot" of work that needs to be done in order for this to be even considered production ready. The future of this project is something that I need to discuss with my mentors.
I will close some of the resolved tasks and make some new tasks which needs to be done in order to get this piece of work to be ready for it's intended use for the team.
With regards to this ticket, what do you think @jcrespo and @Marostegui -- should I close this task and create some new tasks for future work?

Over the next few days, I will review what needs to be fixed and raise tickets and tag them into the Kanban board for this dashboard

Documenting the entirety of my experience in GSoC in one post

Thank you @mmodell :-)

Thanks @Marostegui for your input and feedback.
I think that sound like a good plan @jcrespo -- some of the features might need to go into a stretch goal. First I need to analyse and see how hard it is to implement features (so that I get an idea of whether we have enough time to implement them by end of GSoC).
Let me have a look at which features are a definite yes. I think the only feature that needs to be refined further was the mention of "event" logs (eg. S3 entered RED state due to X, due to backup freshness which was caused by failing backups")
With regards to measuring size issues, there was a mention of how we can use past data to come up with an average change, obviously this sounds like it takes a lot of effort and might have to put this as a stretch goal.

@Marostegui @jcrespo feel free to add your thoughts and suggestions and what you would like to see for the final evaluations :-)

So I've tried using the method suggested by the documentation
This is what a normal query looks like in my MariaDB logs when executed

Investigating into how we use the databases library to write queries in a way that we avoid SQL injection, I followed the advice provided here as my original query used string interpolation and was susceptible to SQL injection attacks.
https://realpython.com/prevent-python-sql-injection/

The above patch lacks unit tests with SQLite, need to sort that one out still. Have a look at the SQL (I have updated it with the recommended Here document style as you have suggested)
The files with the SQL are in crud.py python file
Let me know what you think of the patch when possible :-)

Thank you @jcrespo
I have not used indexes much before, so I will do a bit of learning on this.

Sprint 1 complete (7th June to 21st June)

Perfect, sounds great, no worries and thanks again for your guidance

Thank you, will have a look and will design it accordingly.

Ah very good spot, I will be a bit careful with that next time, thanks @Aklapper

Looks like Gerritbot hasn't posted it here due to some reason but I've uploaded a different patchset for the backend skeleton code (I wonder if I am doing something wrong)
https://gerrit.wikimedia.org/r/c/operations/software/bernard/+/699915
Please have a look when you have the time, and let me know your thoughts
Alternatively we can go through it during the planned meeting this week

Okay, that sounds good. Once we have some unit tests in, I will start the work to setup tox for our projects. Thanks for the information

Putting the 2nd bi-weekly Wikimedia GSoC report here -- hopefully this is helpful for future candidates to see the story gathering/system design mocks process :)

Thank you @jcrespo
I have made amendments to the commit message - let me know if that's okay
Do we need approval from jenkins-bot as well to merge? (I would have to setup tox config first)
How would one merge the changes? (I've got another patchset coming soon with the code skeleton)

Just putting this here for awareness and for any future candidates
Links to my GSoC bi-weekly report/blog can be found here
https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021/Bi-weekly_Reports

A reminder for myself, some more tickets to be made and I need to update the ticket task with new stories, I've made a few basic ones (for tox and code skeleton) but I'll think of some more and add them this week as we go.
Based on our conversation of story priorities, this is some of the non functional requirements (must haves)

Second iteration of feedback, and design

@Marostegui @jcrespo
I wonder if we should stick to using tox for code style validations/unit tests just to maintain consistency with the rest of the DBA codebase? Or is there another better way?

First iteration of front-end mockup and presentation slides for the associated meeting

Thanks @jcrespo -- I have managed to successfully load it into local MariaDB with phpmyadmin -- very useful to see the pattern of the data

That's useful, thank you. I will have a think about the columns for the project -- would be nice to have a kanban board :)

Thanks @jcrespo, Sounds like a plan, will prioritise and make things more clearer and have a think about the scopes and timeframes. (will edit the task and add it in)

First iteration of system design (as discussed on Thursday 27th May -- highly abstract!)