repo speed

[b-iten]

Are there any plans on increasing the repo download speed and adding ipv6 or is broadcom trying to destroy this product as well?
We are already in process to migrate to proxmox and I don't want to replace salt as well.

It's unbelievable frustrating.

[dmurphy18]

@b-iten The IPv6 support is an issue with using Artifactory, cannot speak as to speed. @scriptautomate-bc any idea why speed would be an issue

[bdrx312]

Looks like you need an artifactory version update: https://jfrog.com/help/r/jfrog-installation-setup-documentation/ipv6-support

[scriptautomate-bc]

For the IPv6 support via Artifactory, there was an issue we have closed in relation to the issue

• packages.broadcom.com has no AAAA record / IPv6 support #67051

This has to do with JFrog Artifactory SaaS, not self-hosted JFrog Artifactory. Aspects of their SaaS infra, with the way they are using AWS for backend, don't have IPv6 support enabled.

Our last updates in that issue:

• After further investigation, found that JFrog SaaS infra is not configured to support IPv6 - leaving Broadcom dependent on changes via JFrog
• Confirmed with JFrog, through support contact, that they indeed do not currently support IPv6 as an option but are aware of the need (already had an internal backlog item for it). Though, they have no ETA on implementation and will be providing no estimate
• Best recommendation for users would be to see whether able to create a reachable mirror in the IPv6-only environments, after pulling/pushing mirrors of the repo from an IPv4-capable host: https://docs.saltproject.io/salt/install-guide/en/latest/topics/other-install-types/air-gap-install.html
• For those that are Broadcom / VMware by Broadcom customers: we recommend opening a ticket with Broadcom support about this issue, as that will help raise further awareness as they track impacted customers

Since the Salt Project Team is unable to take further action at this time, we are going to close this ticket as not planned / won't fix.

---

Speaking of IPv6 support: I'm sharing here in this issue thread a link to a feature request I've submitted for GitHub since there have been users reporting problems using some services/endpoints/features of GitHub. Sharing for awareness.

• Feature Request: Provide a centralized resource and GitHub Public Roadmap tracking of IPv6-support for GitHub Services #151477

As @bdrx312 has said in a separate response in this discussion, the air-gap install recommendation guidance linked above should help @b-iten with download speed issues, too, since the packages would then be available internally for production infra. Not relying on the external hosting should help address both the IPv6 issues and any download speed issues your environments may be experiencing.

[bdrx312]

Are there any plans on increasing the repo download speed and adding ipv6 or is broadcom trying to destroy this product as well? We are already in process to migrate to proxmox and I don't want to replace salt as well.

It's unbelievable frustrating.

There are not many artifacts in the repo, just download them once and host them from your own production mirror. I would not depend on externally controlled repos for production use; we make sure to always have our own copies of any resources we depend on for production.

[b-iten]

Are there any plans on increasing the repo download speed and adding ipv6 or is broadcom trying to destroy this product as well? We are already in process to migrate to proxmox and I don't want to replace salt as well.
It's unbelievable frustrating.

There are not many artifacts in the repo, just download them once and host them from your own production mirror. I would not depend on externally controlled repos for production use; we make sure to always have our own copies of any resources we depend on for production.

Thanks, I did mirror the repo now. It's a nice workaround.

[b-iten]

There was a workaround I didn't think of earlier.
Mirroring the repo helps for the two mentioned technical problems.