Prepare first release of code annotation

[dpordomingo]

Blocker things

technical stuff

• loading initial data, options:
  • put the internal.db inside a volume, that will be kubectl cped by Rafa
    • adding example.db https://github.com/src-d/issues-infrastructure/issues/129
    • adding our real data
  • deliver the database inside of the image
  • Rafa access the container, pull the data and run the export
• Server should bootstrap the DB if it's empty #69 make sure that the server won't panic if it is launched without a DB
  • (nice to have) the server will init the DB if it does not exist
• the server will use the db inside the volume:
  • the path of the DB will be a default value, and should point to /var/...
  • that path should be hardcoded in the charts, to let them mount the volume properly
• deployment (Rafa tested and it works), but there are missing things:
  • fix the Docker image Single binary #36 → Prepare the project to be deployed #85
    • env values, urls...
  • Rafa: configure drone Setup release process #30 (review)
• fix x509 error in /oauth-callback Unhandled error in /oauth-callback  #98
• tag 0.0.1 release and publish a binary at GH release Update: publishing artefacts it tracked under Release process: publish more artefacts #159

PRs that needs to be merged

• docs Documentation improvements #29
• db part Connect the frontend UI with the backend API #56
• acl control Restrict access of authenticated users #60
• single binary Single binary #36
• deploy Prepare the project to be deployed #85

GitHub configurations needed

• Alex: Create Application, generate OAuth tokens, communicate the secrets to infra team
• Alex: Create the new organization and teams (reviewers and workers), and add users to the teams.

Next steps

• Add a button to export data into volume
  (nice to have: serve the data right away) Implement a way to download DB exports #73
• reviewer part
• let's decide how to rollback in the future, options:
  • kubectl command
  • tag a new version with old code
• being able to access the logs:
  • @rporres should explain how to proceed
• improve logging errors Logg original errors #50

[rporres]

adding the internal db inside a volume, that will be kubectl cped by Rafa

Please don't tell me the application will be writing in a db inside the container 😱

And that does not play well with CI/CD. Why don't we create a volume and attach it to the container? I can give you advise on that.

[rporres]

As for the logs, @dpordomingo should have access. Please let me know if I'm right

[dpordomingo]

Why don't we create a volume and attach it to the container?

That's the idea de purposed when we wrote:

adding the internal db inside a volume

So our proposal is to mount a volume in the container, and put there the sqlite file. So the app won't write inside the container, but in the db that will be in the volume.

If we do so, the pending thing would be how to put there the initial dataset. That's because we suggested to scp it.

[rporres]

The chart doesn't have any volume attached, hence I didn't understand correctly. Happy to see that we're aligned 😄 Since we're in GCP, it's easy to add a volume using a Persistent Volume Claim

Another important thing is to avoid creating deployments with more than 1 pod, for obvious reasons 😅

Depending on the size of the dataset it can be a good or a bad idea to copy it through kubectl. What are we talking about?

[bzz]

@rporres

Depending on the size of the dataset it can be a good or a bad idea to copy it through kubectl. What are we talking about?

1.6 Gb

[rporres]

Then it's fine to copy it using kubectl

[bzz]

Took liberty of updating the PR description to the best of my knowledge of the current status.

Do we also need a separate issue for adding our real data for kubectl cp of 1.6 Gb under https://github.com/src-d/issues-infrastructure ?

[ricardobaeta]

@bzz Can I have the opportunity to do "Arte-Final" before the release? It would be work on less if need be. I need one hour to do this.

[dpordomingo]

@bzz the issue is prepared, but not opened (it's closed)
https://github.com/src-d/issues-infrastructure/issues/131

I'll re-open it once I ensured that authentication is working.
(I'm trying to debug why did it failed, and I could access with a non src-d user)

[bzz]

@ricardobaeta

Can I have the opportunity to do "Arte-Final" before the release?

we are rushing to have a deployment ASAP, but I would guess that making proper release would take at least 1 day more, so please take your time!

[bzz]

@dpordomingo any reason not to tag a release and 🍾 and close this guy?