[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #33922 [Internal Services/Services Admin Team]: hardware requirements planning for gitlab launch

#33922: hardware requirements planning for gitlab launch
-------------------------------------------------+-------------------------
 Reporter:  anarcat                              |          Owner:  hiro
     Type:  task                                 |         Status:
                                                 |  reopened
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Services Admin     |        Version:
  Team                                           |
 Severity:  Normal                               |     Resolution:
 Keywords:  tpa-roadmap-may                      |  Actual Points:
Parent ID:  #29400                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by anarcat):

 just to be clear here. we're happy with the gitlab hardware right now,
 pre-launch, that is true.

 but we should have estimates on the hardware requirements of the project
 *after* launch. specifically, we need to take into account the fact that
 we might have way more git repositories on the server during and after
 launch. we should plan to have similar I/O capacity than what cupani *AND*
 troodi currently have, if not more.

 this should be done by looking at Grafana graphs of disk, memory and CPU
 usage and see if we have the capacity to provide for those.

 we should also make it clear that we are not replacing Jenkins in this
 phase, for example. or that we do *not* plan on providing gitlab pages
 services. in fact, it might be worth going through the GitLab feature set
 and make sure we have a yes/no answer for each service, and to make sure
 we have the hardware capacity to respond to the "yes" services.

 i'm particularly concerned about git repositories, in other words, but
 there might be other thing that I'm missing, and this ticket should answer
 that in a definite way, by setting expectations for the team and hardware
 requirements for TPA.

 thanks!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33922#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs