-
Notifications
You must be signed in to change notification settings - Fork 299
Sprint 3
Sprint 2 has been finished. The main highlights of it are shown below:
-
Team: Synchronization with lacChain team was started and during this last sprint we shared backlog. Weekly meetings were set to check the progress done. More important is the fact that the core team of Alastria will be changed from the starting of next year 2019. ioBuilders will not be forming part of it and therefore sprint 3 will be the last one for us.
-
Network: the most important advances done were:
- Bootnodes configuration has been created and tested in a local environment obtaining satisfying results. After these tests, we have started working with the goal of implementing the so said configuration in the new test-net Telsius
- Access point docker container has been created for the Alastria node. The Access log filtering was finished and added to the already existing RPC filtering functionalities
- Arrakis and Telsius Block Explorers have been released with the appropriate Alastria colors/fonts with both blk.io and CouncilBox. (link)
- 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: A new document with details of Telsius test-net and its new configuration with bootnodes has been created. This doc will be posted in the github wiki and will show how to migrate Arrakis nodes to Telsius.
Due to the fact that the current core team is going to finish working on Alastria, the objective of this last sprint is to leave the Telsius test-net as ready as possible for the next team that enters to work. Due to a problem with the geth-client and go-rutine of the eth-netstats, the work on bootnodes configuration was delayed and thus Telsius will not be completely finish before the end of the year.
User Story Title | Description |
---|---|
Access Point functionalities | Add the remaining functionalities to have a robust and secure Access Point for Alastria nodes: Include TLS and black and white lists |
Access Point docker integration | Integrate the Alastria node Docker Composer created in previous sprint with the functionalities of the Access point created in native |
Bootnodes | Update the scripts of reinitialization of nodes to the new configuration with bootnodes. |
Create/update and launch regular, validator and boot nodes under the new configuration and that fulfill the consensus protocol | |
Logs rotation | Continue with the task of logs rotation that was started in previous sprint |
Redirection of netstats from ioBuilders to Alastria | Change the domain of the netstats from ioBuilders to Alastria so that the future team can use it without any problem and ioBuilders is not vinculated to it |
Github follow-through | As in previous sprints, there will be a continuous follow through of the community issues and pull requests |
1. How to set up:
- A regular node in Red T using Docker
- A validator node in Red T using Docker
- A bootnode in Red T using Docker
- Private Smart Contracts in Red T
- Deployment of Smart Contracts in Red T
2. F.A.Q.
3. Netstats and Block explorers