[GitHub] [trafficcontrol] TaylorCFrey opened a new issue #6546: Cleanup and remove Riak references, issues, and documentation

[GitBox <gi...@apache.org>]

TaylorCFrey opened a new issue #6546:
URL: https://github.com/apache/trafficcontrol/issues/6546


   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
   the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   A proposal to officially remove Riak throughout ATC in major version 7.x.x.
   
   <!-- Do not submit security vulnerabilities or support requests here - see above -->
   ## This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   - Traffic Control Cache Config (T3C, formerly ORT)
   - Traffic Control Client <!-- Please specify which (Python, Go, or Java) -->
   - Traffic Ops
   - Traffic Router
   - Traffic Stats
   - Documentation
   - CDN in a Box
   - Automation (GitHub Actions, Ansible)
   - Other: Github Issues, Wikis
   
   ## Current behavior:
   <!-- Describe how the current features are insufficient. -->
   
   Riak is officially deprecated within Apache Traffic Control as of v6. With official support for ATC currently being versions 5.x and 6.x, the next major release will allow for the full removal of Riak throughout the project. This includes, but is certainly not limited to, the components listed above. Additional consideration 
   
   ## New behavior:
   <!-- Describe how this change would improve Traffic Control -->
   
   Riak will not longer be an option nor even referenced. Outside of the CHANGELOG (and possibly some legacy documentation), there should be effectively no mention of Riak as a possible option for Traffic Vault.
   


-- 
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@trafficcontrol.apache.org

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

[GitHub] [trafficcontrol] ocket8888 commented on issue #6546: Cleanup and remove Riak references, issues, and documentation

[GitBox <gi...@apache.org>]

ocket8888 commented on issue #6546:
URL: https://github.com/apache/trafficcontrol/issues/6546#issuecomment-1034181624


   I'm not sure this would directly impact the Traffic Ops Go or Python client(s), or t3c, Traffic Router, or Traffic Stats. When interacting through the Traffic Ops API, the backend of Traffic Vault is an implementation detail from version 4 onward already. Once APIv3 is removed, we can safely remove Riak support without any changes needed to any of those things. The only API endpoint that actually depends on the back-end isn't used by any code anywhere in the repository (and the clients don't provide methods for it) so there would be no migration effort specifically associated with Riak removal.


-- 
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@trafficcontrol.apache.org

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