Page MenuHomePhabricator

Create thirdparty/opensearch13 repo for bullseye and remove thirdparty/opensearch1 repo
Closed, DeclinedPublic

Description

Per T380752, we are migrating Relforge to Opensearch. During this process, we've noticed a discrepancy between the repo that holds our home-grown plugins (component/opensearch13) and the repo that repackages the upstream Opensearch 1 release (thirdparty/opensearch1).

While there are a few ways to accomplish this, I would prefer to follow Search Platform tradition and name the repo thirdparty/${MAJVERSMINORVERS}. If anyone would prefer to do things a different way, please respond here and we can discuss this. Update: I've changed my mind! I've noticed that upstream OpenSearch moves very quickly. As such, I think it makes more sense to use the major version only.

Creating this ticket to:

  • Create the thirdparty/opensearch13 repo
  • Copy the packages from thirdparty/opensearch1 to thirdparty/opensearch13 .
  • Remove the thirdparty/opensearch1 repo.

Event Timeline

bking changed the task status from Open to In Progress.Feb 18 2025, 7:46 PM
bking claimed this task.
bking triaged this task as Medium priority.
bking updated Other Assignee, added: brouberol.
bking renamed this task from Create thirdparty/opensearch13 repo for bullseye to Create thirdparty/opensearch13 repo for bullseye and remove thirdparty/opensearch1 repo.Feb 18 2025, 10:27 PM
bking updated the task description. (Show Details)
bking changed the task status from In Progress to Open.Apr 30 2025, 4:47 PM
bking removed bking as the assignee of this task.
bking updated Other Assignee, removed: brouberol.
bking updated the task description. (Show Details)

We haven't been able to work on this ticket for awhile, so I'm unassigning it. We'll pick it back up as time allows.

This ticket is now affected by the plans outlined in T403301: Discuss OpenSearch 3 roadmap/future improvements.

I believe that the plan is to mirror the upstream opensearch repositories, so that would mean that we would have the following components in our apt servers:

  • thirdparty/opensearch1
  • thirdparty/opensearch2
  • thirdparty/opensearch3

Each of these repositories will then contain all of the minor and patch releases relevant to that major version.

However, we will need to be very careful about how we roll this out, particularly with respect to our home-grown plugin packages.

Adding T403301 as a parent, so that we can discuss what to do in the context of that ticket.

bking updated the task description. (Show Details)

I'm going to be bold and decline this one for now. We'll still need to do something about the repository layouts, but I no longer agree with the specific AC I defined above. If anyone does feel like that's still a valid strategy, feel free to reopen.