I manage the devops for a small team of developers (15-20), and we’ve been using Nexus 2 since maybe 2017. I inherited ownership of the Nexus server and in an effort to keep us up to date, have done weekly updates of our various applications. Last month I finally migrated our server from Nexus 2 to Nexus 3.76.
I saw the announcement changing from Community to OSS, but I missed the enforcement of the 200,000 requests limit. The hosted application is gigantic with more than 50 maven modules and because of the number of api calls, reporting, and proxies, we were at around 300k requests per day. I’ve made some efficiency changes (removing some proxied repositories, running some builds in offline mode) and gotten those values close to the limit.
The announcement indicated Community Edition indicated that we can opt to return to OSS edition.
“It’s important to note that our open source EPL core (OSS) is not and has not changed. You can still benefit from the exact same core functionality and formats (apt, Maven, raw) that have been available for more than a decade. Most free users will likely transition to the more feature-rich Community Edition, but those who prefer to use the OSS tier are welcome to do so. We simply want to provide a clear path to additional capabilities and a greater degree of reliability for those seeking it.”
Can we stitch back to OSS version without the limit without downgrading back to before 3.77? We will not have the budget for a pro license this fiscal year, so I want to find out my options. It’s possible we’ll be able to upgrade in the next fiscal year, but if we need to migrate to another maven host in the next 44 days that won’t be an option.
Thank you so much for any help or advice. My team loves Nexus, but it is difficult to justify sudden new software purchases in our industry at this time.
We don’t formally support migrating across to the open source Core edition, but it is possible. However, before you go through the trouble of figuring that out, I’d encourage you to click the link in your usage dashboard and get a quote.
Our goal with Community Edition’s limits is to ensure that larger users are properly supported, and we’ve got promotional pricing in place to make it as painless as possible. Since you’re only very slightly above the limits, the cost might not be as much as you’re expecting.
After changes I’ve made to reduce unnecessary calls, it seems we’ve gotten our usage down to around 66,000 per day. We only use maven and don’t use any of the other Community Edition features so I would still appreciate any information on setting our instance to OSS.
From a risk compliance standpoint, suddenly losing write access to the nexus repository for a full day if someone misconfigures a repository or a script runs an API call in an infinite recursive loop doesn’t seem tenable for our organization.
Community Edition and Pro are part of the same binary, as was the case in prior versions with OSS and Pro. The open source core, on the other hand, is distributed as code. To use it, you need to compile it, deploy it, and move your content over. We don’t have a step-by-step guide for that at this point, but the high-level steps would be:
Create matching configuration in your Core edition deployment (e.g. your repositories, permissions). With a small number of exceptions, configuration settings are accessible via REST API.
Use wget or something similar to pull down your content from your existing deployment, and re-upload it into your new Core deployment.