The jump.ci VM that lets some projects interact with their Jenkins workspace is running on a CentOS 6 VM (and .el6 going EOL soon) so we need to replace that with a different VM under new ci ansible inventory.
@bstinson @arrfab @siddharthvipul1 I think this is still valid, but not sure if the work was already completed? If not yet done and still valid, can we discuss a sizing/gain for this work.
Metadata Update from @dkirwan: - Issue tagged with: need-more-info
Metadata Update from @arrfab: - Issue untagged with: need-more-info - Issue tagged with: high-gain, medium-trouble
Metadata Update from @arrfab: - Issue assigned to arrfab
Per discussion with @siddharthvipul1 and @dkirwan , we have decided to announce in advance and do the switch later (time for projects to digest the info and plan accordingly). Here is the announce : https://lists.centos.org/pipermail/ci-users/2020-August/002111.html
Everything is ready and node is already available as jumphost.ci.centos.org (but only list of users/projects needs to be reviewed by @siddharthvipul1 , especially for ssh-dss keys and option to trim that list)
Tagging so as "groomed" as now waiting
Metadata Update from @arrfab: - Issue priority set to: Waiting on External - Issue tagged with: groomed
Announced for next monday : https://lists.centos.org/pipermail/ci-users/2020-September/002112.html . After that we'll close this ticket
Metadata Update from @arrfab: - Issue untagged with: groomed - Issue priority set to: Waiting on Assignee (was: Waiting on External)
Migration done, and jump.ci is now a CNAME in both public and internal DNS zones. Also pushed change to have the old c6 gateway internal IP added as VIP on the ha-gateway nodes (through keepalived).
The following nodes are now decommissioned (powered off) :
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.