SemVer2 Deployment

[xavierdecoster]

V3 Deployment Remaining work.

• Create new Lucene index for SemVer 2.0.0 (using db2lucene) Create new Lucene index for SemVer 2.0.0 (using db2lucene) #3756
• Verify that SemVer2 aware registration blobs for prod have been created. If they have not, create these, (approx 5 hours when split into 2 jobs according to @joelverhagen 's last timing). Create all registration hives (original + gz + SemVer 2.0.0) using lightning #3683
• Deploy a new catalog2registration job that updates all three containers (ie, there will be one job that writes updates to reg1, reg1-gz, and reg2).
• Redeploy search service and update semVer2RegistrationBaseAddress variable to point to SemVer2 Registration. SemVer 2.0.0 search service should use SemVer 2.0.0 registration URLs SemVer 2.0.0 search service should use SemVer 2.0.0 registration URLs #3743
• Update v3/index.json to mention the new SemVer 2.0.0 registration hive Update v3/index.json to mention the new SemVer 2.0.0 registration hive #3684

Gallery Deployment Remaining Work

• FI Merge from NuGetGallery master into dev [ReleasePrep][2017.06.09]FI of master into dev #4030
• Merge Version validation should happen on the full string #4031 into semver2 feature branch
• Merge SemVer feature branch into dev
• Merge dev-nuget430 shims branch into dev
• Update version to 4.3.0
• Test deploy DEV gallery branch to DEV environment using DEV shims branch
• run EF Migrations on DEV
• Merge dev branch into master for NuGetGallery
• Merge dev shims branch to master
• Test deploy MASTER gallery branch to DEV environment using MASTER shims branch
• set SemVerLevel=2 for semver2 package versions on DEV
• deploy Gallery to DEV and run all tests
• run EF Migrations on INT
• set SemVerLevel=2 for semver2 package versions on INT
• deploy Gallery to INT and run all tests
• run EF Migrations on PROD
• set SemVerLevel=2 for semver2 package versions on PROD
• deploy Gallery to PROD and run all tests
• promote deployment of Gallery to secondary PROD environment

[skofman1]

A few questions:

• Regarding V3 catalog2registration job to update SemVer 2.0 container - I was under the impression we only need one job to update all containers.
• Shims work - perhaps it's part of the plan and just not written: you can test the Shims integration locally without deployment to DEV as a sanity check. Instructions are in OneNote: https://microsoft.sharepoint.com/teams/NuGet/_layouts/OneNote.aspx?id=%2Fteams%2FNuGet%2FTeam%2FNugetServer%2FNugetServerTeamNote&wd=target%28QA.one%7CE377F191-30A2-46CE-9869-A187F139EB06%2FRunning%20Gallery%20with%20Shims%7C32FD4B99-51F8-4CE4-9E89-E649C18A21B1%2F%29
  onenote:https://microsoft.sharepoint.com/teams/NuGet/Team/NugetServer/NugetServerTeamNote/QA.one#Running%20Gallery%20with%20Shims&section-id={E377F191-30A2-46CE-9869-A187F139EB06}&page-id={32FD4B99-51F8-4CE4-9E89-E649C18A21B1}&object-id={CBC820D0-5041-0DFF-2A2E-90AA2858E1C8}&2B

[ryuyu]

You are correct. we just have to point it to all containers. I'll update the step.

[xavierdecoster]

shims work: i know :) just need it merged in the right order, been using those shims for weeks now, they work fine ^^