Page MenuHomeSoftware Heritage

Opam support
Closed, MigratedEdits Locked

Description

That means developing:

  • 1 lister to actually list opam origins
  • 1 loader to actually ingest those listed origins
  • actually make those run within the docker dev environment to lift the paper cuts

When that part is done, this implies packaging and deployment work :

  • first on staging infrastructure (which will pull the necessary packaging work)
  • then deploy it on production

Note that the underlying tool (the opam cli) requires internal state to work (in its OPAMROOT folder).
That could pull some more internal work to manage/sync such state to stay consistent between workers (lister and loader).

[1] http://opam.ocaml.org/doc/Manual.html#opam-root

Event Timeline

ardumont triaged this task as Normal priority.Jul 7 2021, 11:01 AM
ardumont created this task.
ardumont added a subtask: T3358: Opam lister.
ardumont updated the task description. (Show Details)
ardumont updated the task description. (Show Details)

Heads up on this, both opam lister and loader have been deployed on the staging infra.
More details on the dedicated task [1].

Expectedly, there are errors but that's outside the scope of the deployment. Those can
be browsed in the associated dashboard [2] and filtering by priority = 3 to eventually
chase and fix.

@aleo, for information ;)

[1] T3438#68306

[2] http://kibana0.internal.softwareheritage.org:5601/goto/e0611ba609daa546347d59935e416232

Expectedly, there are errors but that's outside the scope of the deployment. Those can
be browsed in the associated dashboard [2] and filtering by priority = 3 to eventually
chase and fix.

Since it's not opened publicly, that does not help much, i've synthesized the
errors from our sentry instance instead in T3468.

@aleo if you feel like fixing those, feel free to open either diff related to this
task or dedicated tasks if you prefer (as you wish). Thanks in advance by the way ;)

ardumont changed the task status from Open to Work in Progress.Sep 29 2021, 9:01 AM
ardumont closed subtask T3358: Opam lister as Resolved.
ardumont closed subtask T3425: Opam loader as Resolved.
ardumont added a subscriber: anlambert.

Remains to add the origin show up on the main archive page.
@anlambert I've asked antoine to do it.

ardumont claimed this task.

And it's now deployed.
Closing.

gitlab-migration changed the status of subtask T3468: staging: current opam loading issues from Resolved to Migrated.
gitlab-migration changed the status of subtask T3568: Deploy opam lister/loader to production from Resolved to Migrated.
gitlab-migration changed the status of subtask T3358: Opam lister from Resolved to Migrated.Jan 8 2023, 4:34 PM