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.

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

Migrate dotnetbuilds CDN from edgeio to Azure FD #15336

Open
mmitche opened this issue Dec 13, 2024 · 3 comments
Open

Migrate dotnetbuilds CDN from edgeio to Azure FD #15336

mmitche opened this issue Dec 13, 2024 · 3 comments
Labels
Needs Triage A new issue that needs to be associated with an epic.

Comments

@mmitche
Copy link
Member

mmitche commented Dec 13, 2024

We need to migrate dotnetbuilds over to AzureFD due to the Edgio CDN going away. Unlike dotnetcli, we can change the hostname in the places it is referenced (dotnetbuilds.azureedge.net). dotnetbuilds is not intended for general public consumption of .NET bits, though it is referenced in our official install scripts.

Execution Steps

The plan for migration off of dotnetbuilds is as follows:

  1. Create a new CDN that points to the dotnetbuilds storage account. This CDN will have the same settings as the previous CDN. Note that azurefd FQDNs include a hash and are less friendly to work with.
  2. Determine and create a short form URL that should point to the new dotnetbuilds CDN. This short form could be a subdomain of dot.net, or an aka.ms link, etc.
  3. Generate an announcement and corresponding issue on https://github.com/dotnet/core/discussions detailing the following:
  • Old name that is going away
  • Timeline that it may go away (sometime after 15th Jan)
  • New URI to update to.
  1. Update all referenced locations that point to the existing CDN URI. This includes:
  • Existing aka.ms links
  • SDK daily builds table
  • aka.ms link targets in publishing (I think?)
  • Some yaml files that specify download locations for dotnet-install
  • eng/common scripting across all in support .NET versions
  • install-dotnet.ps1
  • ...

When the old URI dies, the announcement should be updated to indicate that this is the case.

@mmitche
Copy link
Member Author

mmitche commented Dec 13, 2024

@dotnet/dnceng

@missymessa missymessa added the Needs Triage A new issue that needs to be associated with an epic. label Dec 13, 2024
@lbussell
Copy link
Contributor

.NET Dockerfiles reference dotnetbuilds for nightly builds and some other releases. Today only the Aspire Dashboard Dockerfile references it. We would add more references when we add .NET 10 nightly Dockerfiles, but obviously we will just point that at wherever the new build location is. We can update these at any time, but historical nightly Dockerfiles will fail to build.

/cc @mthalman @joperezr

@mthalman
Copy link
Member

mthalman commented Dec 16, 2024

This also affects WinGet packages: https://github.com/microsoft/winget-pkgs/blob/09f04f8a043740386e3db3ae7f71cad5277b59ea/manifests/m/Microsoft/DotNet/SDK/9/9.0.101/Microsoft.DotNet.SDK.9.installer.yaml#L14

Sorry, this issue is for dotnetbuilds, which WinGet packages is not referencing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Triage A new issue that needs to be associated with an epic.
Projects
None yet
Development

No branches or pull requests

4 participants