Bug 1567880 - Grant Deepshikha access to all CI-related infrastructure
Summary: Grant Deepshikha access to all CI-related infrastructure
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-16 10:39 UTC by Nigel Babu
Modified: 2018-06-20 18:04 UTC (History)
4 users (show)

Fixed In Version: glusterfs-v4.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-06 23:54:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Nigel Babu 2018-04-16 10:39:36 UTC
Deepshikha has been doing excellent work and has demonstrated the ability to not just do day-to-day work but also design and ownership of the CI module. This bug is being used for granting her maintainer access and also the infra piece of granting her access to all the Jenkins infrastructure.

Comment 1 M. Scherer 2018-04-16 10:47:25 UTC
So, in practice, what access does that entail ?
(cause we just have "all access" and "no access" :/ )

Comment 2 Worker Ant 2018-04-16 10:50:03 UTC
REVIEW: https://review.gluster.org/19880 (maintainers: promote Deepshikha to maintainer) posted (#2) for review on master by Nigel Babu

Comment 3 Nigel Babu 2018-04-16 11:06:14 UTC
Yeah, we have the option of either setting two levels or giving all access and depending on trust.

Right now, I'm looking for all Jenkins nodes, build.gluster.org, and the associated servers like ci-logs.gluster.org. I'm okay with all access if that's easier.

Comment 4 Worker Ant 2018-04-16 11:43:47 UTC
COMMIT: https://review.gluster.org/19880 committed in master by "Nigel Babu" <nigelb@redhat.com> with a commit message- maintainers: promote Deepshikha to maintainer

Deepshikha has been doing excellent work across the CI system. She is
now ready to co-maintain the Continuous Integration module and be
responsible for the CI ecosystem in its entirety.

Fixes: bz#1567880
Change-Id: If204301d26731f93b2dccfe8b6571ee748a47b26
Signed-off-by: Nigel Babu <nigelb@redhat.com>

Comment 5 M. Scherer 2018-04-16 12:32:22 UTC
I am also ok with all access, if someone explain the best practice regarding ssh security and stuff like this. (ideally, key on a smartcard/yubikey, but at minima, password protected ssh key, and up to date system, not running anything on it, etc)

Comment 6 Deepshikha khandelwal 2018-05-02 10:22:38 UTC
Here's the public key:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCuCz0Uc6gRdnwt7M8c2RAzfq3dKOek1RuFmpb7srs0MlRZpxAUUBgLYUS3hvQUdUaa5PIK9mmfc2cAt9JbCru1YVmHuA+0Dii3G7Tb93cRUjS8Ca75dMcD4j/8MXEW7U/zikrpV7MDLYzfZ+SzCatrQRjtC8DWuIk39OhEf/knHG7iAtQ79vkDj67AGGNuB4S5a6mmCSvf+3O+4cROx9hIKAzw7YyWBN5G07JTMjNbottZErOtzBbBm5gpD05ARKy2S4eI8oAWlDEoxBywf9tAGJcbku7MvphBTiaikwMljDWiBdN7ww3A11SkivupBa/SVRwNSXpOBx0aNAiLKCk7c3w+ryFfb4+1w6FBBWsZdkSgssyOtC05B1J03X/L8S8KtxplTFtKIhGZFMUBlOZTZfPkgI6sJfsZtGiTHpFCplkVq8IxZFu4Z0VkAxIoQInfPIIMzVuUpWm1ONdMrJ9KSLzkTMmfqHXVkEu2QRmVsJTO8tlghIV4HPbCWiE4oFo7zcAyfpPu8od526706UL/TWSXFAul/uprYvrsLSz7tHb1dgJEzc+l8GhG1HUvgXjepoMGoMNFgubpLsff8RoeIdjwuqFAyvdowLHxRdPbZqY3QGDsESZOoBa0AvQlC/6dBb0C9zNj3A/1hbBMu9BZxxPqMkyDD7dOGrCTa7vnzQ== dkhandel@localhost.localdomain

Comment 7 M. Scherer 2018-05-05 21:06:59 UTC
I have added the access 2 days ago, seems I forgot to announce on this bug

Comment 8 Nigel Babu 2018-05-06 23:54:33 UTC
Can confirm this is now done for the most commonly needed hosts. Resolving the bug.

Comment 9 Shyamsundar 2018-06-20 18:04:29 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.

glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html
[2] https://www.gluster.org/pipermail/gluster-users/

Note You need to log in before you can comment on or make changes to this bug.