Eric Evans started today on the services team. He has a lot of Cassandra and ops experience (long-time Debian Developer), and will probably find a lot of things to improve about our cassandra setup.
The access he needs is basically what we discussed in T89366.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| add eevans to restbase/cassandra roots and deployers | operations/puppet | production | +10 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | RobH | T91134 RESTBase deploy access and shell on Cassandra cluster for eevans | |||
| Restricted Task |
adding @fgiunchedi because he worked on this on T89366 and @RobH because he will be on Clinic Duty next week
do you guys know which admin groups specifically?
seems we currenlty have: restbase-roots and cassandra-test-roots but not cassandra-roots. are we talking about one of these groups or do we need a new one? do you know already?
@Dzahn, restbase-roots and cassandra-test-roots are fine, that's what mobrovac & I have as well. Can reshuffle the groups some other time, there's no functional need for it.
Change 194987 had a related patch set uploaded (by Dzahn):
add eevans to restbase/cassandra roots and deployers
@Eevans Hi! We are preparing your shell access request. Please read and sign L3 and provide us with a SSH public key (but not the same that you already use for labs, please). Thank you
Here is my public key:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDdE3SnW3e2DxOwJ9iclnbne01cjmoyp6irLeolPpMLcyKXx44eaK44qqhyfRnEoM3TYAeye/YBDB/CL33idRLT7iq1lbIQD7QY9pyf1dp2UBKhJv5FkjViveEe+g69XMcTQdoaPZySHJxHhPkVRVH1ZyfIEZYFWgCIWU1P7T6iiJ7aiBygKq7pKcCSSu6adm2Y+ATFZNqYW5+IryKAiJE87U+YOIY95FusKE4CxovIV363KqXsOQmJ+zr9kSDOlbfv9ILcrkHe8Dp5jeVLFye/dZPE8AEM7S6cXVQbkEvgb4ahpxZo5eEulVjLZdjaZEh/sDGK8++DQObaGKzeRmEP wmf
his sudo for cassandra test roots has been approved in the operations weekly meeting.
Should this also apply to the test cluster? I have no access there (and need it). Should I submit a separate issue?