You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2025/11/03 19:41:04 UTC

[I] Build ATR production server (tooling-trusted-releases)

dave2wave opened a new issue, #284:
URL: https://github.com/apache/tooling-trusted-releases/issues/284

   A new version of the rsync server needs to be built which will also host ATR.
   
   We need enough disk space to have a full checkout of `svn.apache.org/dist/release` along with room to grow ATR's immutable storage.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Build ATR production server (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #284:
URL: https://github.com/apache/tooling-trusted-releases/issues/284#issuecomment-4938448137

   It would be safer to have no votes under way when we migrate the server. This may mean that we have to disable starting a vote for a few days beforehand. I can't find any places where this would definitely break, but it's the highest risk part, and e.g. the expected vote publication directory on SVN would be changed without notifying the PMC.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Build ATR production server (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #284:
URL: https://github.com/apache/tooling-trusted-releases/issues/284#issuecomment-3482355763

   Current method of synchronizing releases from svn: https://dist.apache.org/repos/dist/release/zzz/checkrev.py


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Build ATR production server (tooling-trusted-releases)

Posted by "asf-tooling (via GitHub)" <gi...@apache.org>.
asf-tooling commented on issue #284:
URL: https://github.com/apache/tooling-trusted-releases/issues/284#issuecomment-4410389031

   <!-- gofannon-issue-triage-bot v2 -->
   
   **Automated triage** — analyzed at `main@2da7807a`
   
   **Type:** `discussion`  •  **Classification:** `no_action`  •  **Confidence:** `high`  •  ⚠️ **Possibly stale**
   **Application domain(s):** `shared_infrastructure`, `artifact_upload`
   
   ### Summary
   This issue is an infrastructure/operations planning task about provisioning a new production server to host ATR alongside the rsync distribution server. It requires enough disk space for a full SVN release checkout plus ATR's immutable storage. @dave2wave referenced the current SVN synchronization method (checkrev.py). This does not map to any specific code change in the repository — it is about server hardware/VM provisioning and deployment.
   
   ### Proposed approach
   This is an infrastructure provisioning issue, not a code change request. The work involves building or provisioning a server (physical or virtual) with sufficient disk space to host both ATR's application and a full mirror of svn.apache.org/dist/release. This would typically be handled by ASF infrastructure team operations (e.g., Puppet manifests, Ansible playbooks, or manual provisioning) rather than changes to this application repository.
   
   If any code changes were needed, they might involve deployment configuration (Dockerfile, docker-compose, or systemd service files), rsync daemon configuration, or storage path configuration — but none of that is requested or implied by this issue beyond the high-level planning.
   
   ### Open questions
   - Has this server already been provisioned outside of this repository's tracking?
   - Is there a separate infrastructure repository (e.g., ASF Puppet/Ansible) where this work is tracked?
   - What is the current size of svn.apache.org/dist/release and expected growth rate for ATR storage?
   
   ### Staleness assessment
   
   _opened 186 days ago; last human comment 186 days ago._
   
   The issue was created 186 days ago with only one comment on the same day and no subsequent activity. It is an operational planning task that may have been completed out-of-band (server already built) or may be tracked in ASF infrastructure channels. The 180-day threshold is exceeded with zero activity in the last 90 days.
   
   _The agent reviewed this issue and is not proposing patches in this run. Review the existing-code citations and open questions above before deciding next steps._
   
   ### Files examined
   - `.asf.yaml`
   - `.github/PULL_REQUEST_TEMPLATE.md`
   - `.github/dependabot.yml`
   - `.github/labeler.yml`
   - `.github/linters/.markdown-lint.yml`
   - `.github/workflows/allowlistchecker.yml`
   - `.github/workflows/analyze.yml`
   - `.github/workflows/build.yml`
   
   ---
   *Draft from a triage agent. A human reviewer should validate before merging any change. The agent did not run tests or verify diffs apply.*


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Build ATR production server (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #284:
URL: https://github.com/apache/tooling-trusted-releases/issues/284#issuecomment-4971110043

   Include logrotate in puppet.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Build ATR production server (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #284: Build ATR production server
URL: https://github.com/apache/tooling-trusted-releases/issues/284


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org