Sprint 2

Summary of previous sprint and state of the team

Sprint 1 has just been completed. The sprint planning presented in sprint 1 has been faithfully followed and most of the user stories have been accomplished. The main highlights during these two weeks are:

• Team: a new member with a devops profile has been onboarded in Alastria core and is already working in automation, security tasks. Sync meetings have been started with Latam Alastria team and it has been agreed to share backlog for next Sprint #2 so that we join forces, share knowledge and work towards the same goals.
• Network: the most important advances done were:
  • Telsius testnet has been deployed in a closed environment for the core team.
  • RPC filter Access Point has been developed and tested in a native environment.
  • Netstats and Block explorer have been released for both Arrakis and Telsius testnets for its monitoring and visualization
  • Community issues and pull requests have been attended as soon as possible highlighting the addition of new requested nodes and dealing with problems detected in the network. (reinitialization of nodes, update of certificates etc.)
• Documentation: The wiki documentation has been extended and updated, now including a private smart contracts creation step by step guide. Gitlab internal documentation has been created to share ADRs and approaches as well as to keep step by step guides of repetitive tasks such as adding a new node, so that any member of the core team can do it.

Backlog for Sprint 2

The main goals for this sprint are to advance as much as possible in the implementation of the Alastria Access Point and changing the configuration of Telsius network adding bootnodes. This sprint will last 3 weeks instead of the usual 2 due to the bank holidays that shortens one of the weeks and therefore it will finish the 11th of december.

User Story Title	Description
Alastria Access Point*	This user story has been divided into two main blocks of tasks: Native environment: Continue with the functionalities proposed. First, add TLS and access log to the filter. If there is still enough time include black and white lists and DDOS rules Docker: Create an Alastria node docker container and integrate the access point
Bootnodes*	A plan with the following tasks has been designed for the completion of this user story: In a local environment in Telsius network, test the functionalities of bootnodes Create and modify the needed scripts so that to count with bootnodes in the network configuration Create and update Telsius validator, boot and regular nodes so that they are compliant with the new scripts.
Logs rotation	If there is enough time,as a nice to have, include logs rotation in the operation of the nodes so that there is not a big accumulation of them
Alastria Github follow-through	As in previous sprints, there will be a continuous follow through of the community issues and pull requests

*User story planned to not be finished and to be continued in next sprint