The world from decentraland

Add IdentityMessage to broker+world comm

The identity message will be something like:

message IdentityTopicMessage {
    MessageType type = 1;
    uint64 from_alias = 2;
    string topic = 3;
    bytes identity = 4;
    Role role = 5;
    bytes body = 6;
}

with message type IDENTITY_TOPIC. The server will override the from_alias, identity and role fields to ensure they are correct. Only role CLIENT will be used right now so the explorer can ignore any message that does not belong to a client. The identity field will be a serialized string with the userid.

I will also change the ProfileData as follows:

message ProfileData {
    Category category = 1;
    double time = 2;
    string profile_version = 3;
}

That is: I'm removing avatar type, displayName and publicKey and adding the profile_version so other clients can determine if they have the latest profile version.

Deploy new version of the world in dev and fix explorer problems

Review friendship docs and update roadmap

[OPS] Kibana everywhere

See: https://docs.google.com/spreadsheets/d/1H8Gq2tBbgQK_738Gi-eh0FlNa-uBvEKoDAOGiiTAQUw/edit#gid=0

Configure Auth0 accounts to handle multiple clients logins

Since we are going to use the same user DB (configure in auth0) for the avatars system and for the Explorer closed beta, we need to identify the users that are allowed to enter the Explorer from the ones that are not:

TODO:

Generate another app (.org. .today maybe .zone should be closed in all cases)
verify that user tokens generated for one clientId wont be valid for the other
Add a flag to the users able to enter the explorer
Investigate how to invalidate user sessions when we remove access to the explorer.

DSP: How does Communications work

[research] comms for preview

What should we do with comms in preview?

Create platform-ephemeral-keys

The new project should be based on the identity package here, but it will be much simpler. AFAICT it will consist solely in the get token endpoint. No login/logout pages, no POST /login, no POST /logoug

Implement world definition API

[OPS] Env Tuning for Auth Service

Load balancer policies
Number of instances
Env health checks.
Analyze the need (or not) of caching requests
Analyze the need (or not) for Nginx or similar to take off some load off the service, filter requests and so on

[research] Store communication metrics for offline processing

Add /version and /status endpoints to identity and profile

Review API

Add comms

Add circuit breaker

At least in the following places:

when requesting pubkey from identity
- in coordinator
- in profile
when comm server connects to coordinator

[Placeholder] Metrics

This is a placeholder issue, we probably need to talk to Miguel to see what's involved. We have a dependency of them but we are probably not blocked, since we need to collect them in our projects

[OPS] Problems with kibana

https://trello.com/c/mdUQYCGm
https://trello.com/c/Yz7Dt9Zw

[OPS] Jenkins tag problem

https://trello.com/c/UERrjbko

[Research] define strategy to test/debug in prod

We need to define a strategy for:

functional test against production (probably the puppeteer work @donequis has been working on)
stress test against production
a way to be able to interact with prod from local (perhaps a set of scripts to call those services) to the be able to debug problems

Deploy world everywhere

Versioning

All APIs should have a versioning schema. Not only the project themselves, but also the standards

We need to decide what's the best way to provide config for the world: command line args, a config file, env vars, etc

Use config module for comms

Report Errors using DD middleware

[OPS] Deploy coturn components

Add
Separate comms server in ECS cluster(s): https://trello.com/c/t3S8hBYv

[Research] TURN server

Those are the requirements:

Be able to be integrated to our identity solution
Support a way to add stats
Support a way to define relay rules (so we relay to our services only)

Error during WebSocket handshake

Gather identity use cases

DSP: How does the Identity System work

[placeholder] Scalability next steps

https://docs.google.com/document/d/1ZcCwPgPCP9EiUWGH3jMZJr_zPrveUUu-TaEasIGdSYc/edit?ts=5d13ff03

Send auth error to caller

Auht0 to Segment:

DEV = DONE
STG = DONE
PROD = PENDING (copy from dev, change segment key)

Dockerize project + add resource metrics everywhere

This will enable people to deploy a world node seamlessly and it will helps us to integrate metrics tools

Expose communications metrics

[Profile] Add test from puppeteer

Finish testing profile service

Remove ID + email from profile schema

ID is the user id, but we take it from the access token

We need a TURN server for communications

[OPS] Deploy Thanos

https://trello.com/c/jCdgj1O7/134-investigate-prometheus-thanos-as-a-monitoring-platform

store user client's settings

We need a way for users to store their client's configuration so it won't be lost between devices.

Add auth to the world project

Create platform-profile

Move profile package to its own project.
It should take auth0 access tokens instead of ephemeral keys. It should be an auth0 API.
We should have a way to filter the returned fields
- maybe by scope
- maybe by providing a fields field
- maybe a combination of both

Research - DCL Identity

Why?

We need to design a solution for identity that solves the use cases described here https://docs.google.com/document/d/19cdMqnNtilCgJGyvNFMZUlnve6ZwDMpfCiC-EiBNMXI/edit?ts=5d040303#

What?
We need to close the discussions exposed here https://docs.google.com/document/d/1GnGjzp3Is0nmSRGZfhlgWAOCeSfJ7GyFshwVhnNLvhA/edit# and come up with a design specification and a list of issues to implement.

created_at should be included in the response, but not on the post

Separate comms server in ECS cluster(s): https://trello.com/c/t3S8hBYv
Add DD to coordinator and server containers
https://trello.com/c/RJRK9FPa

decentraland / world Goto Github PK

world's People

Contributors

Stargazers

Watchers

Forkers

world's Issues

Recommend Projects

Recommend Topics

Recommend Org