Hey folks! To test AAA we'd like to bring back mailman / postorius / hyperkitty in staging. The current set of packages will do, I don't think it's worth waiting for updated ones. Also, we don't need a lot of space as it's just for testing that logging in works in both UIs.
Currently the file inventory/host_vars/mailman01.stg.phx2.fedoraproject.org needs to be renamed to .iad2 and the values need to be adjusted, but I'm not sure what to pick. I've already uncommented mailman01.stg in inventory/inventory.
inventory/host_vars/mailman01.stg.phx2.fedoraproject.org
.iad2
mailman01.stg
inventory/inventory
There is a dns entry for mailman01.stg.iad2.fedoraproject.org already so we can use that for the eth0_ip: 10.3.166.40
Then the standard for that subnet is: nm: 255.255.255.0 gw: 10.3.166.254
Our dns server is available at: dns: 10.3.163.33
There is only 4 vms on vmhost-x86-03.stg.iad2.fedoraproject.org so I think we can use that as the host
The kickstart is for rhel7 and I'm not sure if there is anything blocking upgrade to rhel8 so we'll leave it as is for now.
The below PR should cover it: https://pagure.io/fedora-infra/ansible/pull-request/426#request_diff
Metadata Update from @mobrien: - Issue assigned to mobrien
So I tried to do this back during the IAD2 bringup and there seemed to be a lot of 'missing' items in getting it built again.
Metadata Update from @smooge: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: high-gain, high-trouble, lists
So, do we want/need this anymore?
IMHO, perhaps we just nuke it and re-add it once we have new mailman packages to test deploying?
Following through with the last post. Going to nuke this until people can work on mailman as an initiative.
Metadata Update from @smooge: - Issue close_status updated to: Initiative Worthy - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.