Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Package Renames] Unblock deployments to existing search instances #7977

Closed
9 tasks done
loic-sharma opened this issue May 4, 2020 · 0 comments
Closed
9 tasks done

[Package Renames] Unblock deployments to existing search instances #7977

loic-sharma opened this issue May 4, 2020 · 0 comments
Assignees
@loic-sharma
Milestone
Sprint 170 - 2020...

Comments

@loic-sharma
Copy link
Contributor

loic-sharma commented May 4, 2020 •
edited
Loading

We will be running two search instances side-by-side:

  • 011 - The existing search service used to serve production traffic, without popularity transfers
  • 012 - The new search service used to A/B test popularity transfers

Deployments to the exising search service will be blocked by the following:

  1. NuGet.Services.Metadata#774 requires the popularity transfer auxiliary file to exist. Merging this will block deployments to auxiliary2azuresearch and the search service.
  2. Updating the 011 instance of auxiliary2azuresearch will apply popularity transfers to production traffic.

We should be able to deploy the latest bits to both of these instances:

  • Add a configuration to disable popularity transfers on a specific search instance
  • Add the popularity transfers auxiliary file to all existing search deployments
    • DEV
    • INT
    • PROD
  • Validate all jobs and services work on the existing 011 instance
    • auxiliary2azuresearch
    • catalog2azuresearch
    • Search service
@loic-sharma loic-sharma added this to the Sprint 170 - 2020.05.04 milestone May 4, 2020
@loic-sharma loic-sharma self-assigned this May 4, 2020
This was referenced May 4, 2020
Open
Closed
Merged
loic-sharma added a commit to NuGet/NuGet.Services.Metadata that referenced this issue May 5, 2020
@loic-sharma
[Package Renames] Add config to disable popularity transfers (#775)
1f589f2 
We will be running two search instances side-by-side:

* `011` - The existing search service used to serve production traffic, without popularity transfers
* `012` - The new search service used to A/B test popularity transfers

Currently, updating the `011` instance of `auxiliary2azuresearch` will apply popularity transfers to the production traffic. This is not desirable, so this change adds a config to disable transfers on `011` but enable them on `012`.

Configs PR: https://nuget.visualstudio.com/NuGetMicrosoft/_git/NuGetDeployment/pullrequest/1414
Addresses NuGet/NuGetGallery#7977
joelverhagen pushed a commit to NuGet/NuGet.Jobs that referenced this issue Oct 26, 2020
@loic-sharma
[Package Renames] Add config to disable popularity transfers (#775)
48d7fb3 
We will be running two search instances side-by-side:

* `011` - The existing search service used to serve production traffic, without popularity transfers
* `012` - The new search service used to A/B test popularity transfers

Currently, updating the `011` instance of `auxiliary2azuresearch` will apply popularity transfers to the production traffic. This is not desirable, so this change adds a config to disable transfers on `011` but enable them on `012`.

Configs PR: https://nuget.visualstudio.com/NuGetMicrosoft/_git/NuGetDeployment/pullrequest/1414
Addresses NuGet/NuGetGallery#7977
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@loic-sharma loic-sharma

Labels
None yet
Projects
None yet
Milestone
Sprint 170 - 2020.05.04
Development

No branches or pull requests
1 participant
@loic-sharma