19:01:22 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:01:22 Meeting started Mon Mar 2 19:01:22 2020 UTC. 19:01:22 This meeting is logged and archived in a public location. 19:01:22 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:22 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:01:22 #chair cverna mboddu nirik relrod smooge 19:01:22 Current chairs: cverna mboddu nirik relrod smooge 19:01:22 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:01:22 #info agenda is at https://board.net/p/fedora-infra-daily 19:01:22 #topic Tickets needing review 19:01:37 sorry browser froze 19:01:44 .ticket 8701 19:01:46 nirik: Issue #8701: Bugzilla Editing Permissions Issue - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8701 19:02:01 this is a dupe. let me fix that one user and close it as a duplicate to fix the script... 19:02:05 hello o/ 19:03:04 zodbot: fasinfo imcinerney 19:03:05 nirik: User: imcinerney, Name: Ian McInerney, email: ian.s.mcinerney@ieee.org, Creation: 2019-06-16, IRC Nick: None, Timezone: UTC, Locale: en, GPG key ID: None, Status: active 19:03:08 nirik: Approved Groups: fedorabugs packager cla_done cla_fpca 19:04:36 pagure.issue.edit -- kevin edited the close_status and status fields of ticket fedora-infrastructure#8701 https://pagure.io/fedora-infrastructure/issue/8701 19:04:37 pagure.issue.comment.added -- kevin commented on ticket fedora-infrastructure#8701: "Bugzilla Editing Permissions Issue" https://pagure.io/fedora-infrastructure/issue/8701#comment-629856 19:04:44 .ticket 8702 19:04:45 nirik: Issue #8702: Renew or Retire Certificate for *.id.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8702 19:04:54 .ticket 8703 19:04:55 nirik: Issue #8703: Renew or Retire Certificate for *.stg.id.fedoraproject.org - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8703 19:05:10 I guess these just need moving to waiting on assignee and done? 19:05:29 yes 19:05:31 as long as we support openid, we need these I think 19:06:08 smooge: you got those changes? or want me or cverna to? 19:06:13 i am making them 19:06:21 thanks smooge 19:06:24 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8702: websites-general https://pagure.io/fedora-infrastructure/issue/8702 19:06:25 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8702 https://pagure.io/fedora-infrastructure/issue/8702 19:06:31 cool. thanks 19:06:37 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8703: websites-general https://pagure.io/fedora-infrastructure/issue/8703 19:06:38 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8703 https://pagure.io/fedora-infrastructure/issue/8703 19:06:46 .ticket 8704 19:06:47 nirik: Issue #8704: Need to backup/copy data from equallogics to storinator - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8704 19:07:03 I guess we need to @ the copr folks here and find out exactly what they want. 19:07:30 I can add questions, or smooge you want to take care of it? 19:07:45 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8704: "Need to backup/copy data from equallogics to storinator" https://pagure.io/fedora-infrastructure/issue/8704#comment-629861 19:07:54 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8704 https://pagure.io/fedora-infrastructure/issue/8704 19:08:07 that cover the question you wanted nirik ? 19:08:19 yep. exactly it. :) 19:09:06 .ticket 8705 19:09:08 nirik: Issue #8705: Rebuild fed-cloud12 to virthost-os01 (fed-cloud-13 to virthost-os02) - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8705 19:09:11 ok 8705 I need to rewrite 19:09:30 it is move stuff off of virthost-os01 to virthost-cloud01 19:09:35 so I guess this becomes: move os-proxy01/02 to virthost-cloud01? 19:10:10 we could rebuild fed-cloud15 to be a virthost-cloud02 19:10:25 what did you want to do with virthost-os03? 19:10:39 I have it that it is going to RDU 19:11:08 ok. 19:11:14 it is an R630 19:11:15 is 15 a 630? 19:11:28 12/13/15 are all 630's 19:11:36 well, were... 19:11:55 anyhow. 19:12:13 so 15 could become cloud02 or os02 19:12:17 and cloud01 could be os01 19:12:26 I'm fine rebuilding 15 to cloud02, or rebuilding virthost-os03 to cloud03 19:12:28 i wasn't sure how those names needed to be mapped 19:12:33 ok I can do that 19:12:39 I will alter the ticket to match that 19:12:55 I called those two for 'openshift' but if we want to make them more generic for other stuff... 19:13:06 cloud of course is a bit of a misnomer. 19:13:12 naming things is hard 19:13:45 virthost-nz01 and virthost-nz02... the neutral zone! 19:14:36 pagure.issue.edit -- smooge edited the content and title fields of ticket fedora-infrastructure#8705 https://pagure.io/fedora-infrastructure/issue/8705 19:14:39 anyhow, moving on I guess? 19:14:47 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8705 https://pagure.io/fedora-infrastructure/issue/8705 19:15:05 will rename them for new zealand 19:15:15 whats the virthost-cloud01 box now? is that a 630? 19:15:28 it is the r630 which was for the koji-s390 19:15:35 it is 19:15:38 ah, ok 19:15:52 so it would be made into virthost-cc-rdu04/05/06 19:15:57 we need really only 2 of them there... if we want communishift HA 19:16:06 after we move stuff to CC 19:16:24 yeah, would some of those better go to iad2? 19:16:35 quite likely 19:16:57 I was confused that the openshift needed hardware control for those proxies 19:17:03 so we have 1 extra r630 right? 19:17:09 so I had assumed they needed to be full access 19:17:14 yeah, they can be/are vm's 19:17:38 I just wanted them on different boxes in case one died. 19:17:48 ok in that case, one can go on virthost-cc-rdu01 one can go on virthost-cc-rdu03 and virthost-cloud can become virthost-cc-rdu04 19:18:29 fed-cloud12/13/15 and virthost-os03 can then go to IAD 19:18:42 ok. sounds good. 19:18:59 will make the changes to the email I was going to send out shortly 19:19:28 next ticket? 19:19:43 +1 19:20:12 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8705 https://pagure.io/fedora-infrastructure/issue/8705 19:20:13 yeah... 19:20:13 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8705: "Rebuild old R630 cloud boxes to be virthost-cloud boxes" https://pagure.io/fedora-infrastructure/issue/8705#comment-629865 19:20:25 .ticket 8706 19:20:27 nirik: Issue #8706: Enable auto signing on f32-gnome side tag - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8706 19:20:37 I can do this, will need a freeze break... 19:20:54 however, we could also just ask kalev to tag it into the pending tag and get it all signed at the end. 19:21:05 I guess that makes it slow to be able to make the update. 19:21:11 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8706: koji https://pagure.io/fedora-infrastructure/issue/8706 19:21:12 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8706 to kevin https://pagure.io/fedora-infrastructure/issue/8706 19:21:13 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8706 https://pagure.io/fedora-infrastructure/issue/8706 19:21:14 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8706: "Enable auto signing on f32-gnome side tag" https://pagure.io/fedora-infrastructure/issue/8706#comment-629867 19:21:36 .ticket 8707 19:21:37 nirik: Issue #8707: Find all old retired components in bugzilla and mark them 'closed to new bugs' - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8707 19:21:44 oh, I guess pingou already got this one 19:22:02 .ticket 8708 19:22:03 nirik: Issue #8708: Wipe autocloud-aarch64-01 and make into builder - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8708 19:22:26 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8708 https://pagure.io/fedora-infrastructure/issue/8708 19:22:29 just needs doing. It's a mustang. I don't know where it stands in the move pile 19:22:50 nirik: I think it's fine if the update creation is slow and everything is signed then, no need to enable autosigning for the side tag if it's difficult right now 19:22:58 well you wanted all the mustangs moved to IAD2 so I have been trying to do that 19:23:39 kalev: ok, basically it means justtagging them into pending tag and it will sign them all then, and after they are signed you can make the update... 19:23:46 if that delay is ok, no need to autosign 19:24:04 smooge: yeah. Just hard to keep track of what mustang is what 19:24:23 there's two in the 'cloud' racks also that we never setup. ;( 19:24:40 yeah.. I expect that when they pull some to move over it is going to drop things we thought were something else 19:24:54 I have those to move over.. we could kill them if you want 19:25:06 .ticket 8709 19:25:08 nirik: Issue #8709: Permissions update to github.com/fedora-infra for Fedora Badges - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8709 19:25:17 I can do that 19:25:27 pagure.issue.assigned.added -- cverna assigned ticket fedora-infrastructure#8709 to cverna https://pagure.io/fedora-infrastructure/issue/8709 19:25:28 smooge: naw, would be good to have them in rdu2 I think... 19:25:33 cverna: cool 19:26:44 cverna: don't forget to change to waiting on asignee. ;) 19:26:50 ok, thats it for needs review. 19:26:53 ha yeah :) 19:26:54 anything else we want to discuss? 19:27:01 pagure.issue.edit -- cverna edited the priority fields of ticket fedora-infrastructure#8709 https://pagure.io/fedora-infrastructure/issue/8709 19:27:13 ok I have one thing 19:27:18 would be nice to have a zodbot alias to setup the priority 19:27:50 https://paste.centos.org/view/77b48688 is my list of what is moving in the first 2 waves of hardware to either IAD2 or RDU Community Cage 19:27:53 since I am done with old cloud retirement I was going to try and focus on tickets this week... unless there's any urgent fires I should work on. 19:28:38 my fires are mostly paperwork of what ports are open where, what ips we need, what our networks at each site should look like 19:28:57 does not sound fun :( 19:29:29 smooge: one thing I noticed just now... 19:29:45 so nirik I will probably be needing to ask you some 'how do you want this architected when you have no idea what it will be' questions 19:30:18 we have 2 sets of 1g switches for the cloud now.. do both of those need to go to rdu2? 19:30:37 well, 5 of them for 3 racks 19:31:25 we will need to send 5 switches. 1 10gig switch, 2 lowend 1 gig switches for mgmt ports and 2 1 gig switches for prod. 19:31:29 yeah, happy to try and come up with arch/help any way I can 19:31:42 ok, there's a extra then... 19:32:33 smooge: are you ok with all machines we setup in the new dc using uefi/secureboot? I still need to try and see if I can get encryption working transparently. 19:32:36 i am going to request this so we do not have to buy switches at RDU which may not get there til May 19:33:11 I am going to assume we will just be typing in passwords a lot from mgmt consoles 19:33:36 if we cannot get encryption working transparently, we will not do it. 19:33:43 (for most everything) 19:34:35 also bare metal should be rhel8 (unless it has to be newest fedora) 19:34:43 anyhow... shall we close out? or anything else? 19:34:44 actually I am ok with it being needed as long as the password is not over 32 characters long :) 19:34:49 #endmeeting