July 01, 2020 -
Triage - https://pulp.plan.io/projects/pulp/issues?query_id=157 - 3 months planning - https://hackmd.io/bEXtPmroSMSHFyGRNO6QYg - CentOS 8.2: - Vagrant registry <https://app.vagrantup.com/centos/boxes/8> not updated, but cloud.centos.org <https://cloud.centos.org/centos/8/vagrant/x86_64/images/> is - RH IRC #centos response on 6/3: we're in touch with the folks who have access to vagrant cloud trying to get the proper ACLs to update those - Agreed: Live with the pulplift limitation of the hardcoded libvirt URL for now. - SELinux and EL8: - https://pulp.plan.io/issues/7043#note-3 - Raising question about whether or not we should import/compile and upgrade path considerations - Zuul: Gating PR with VM installation testing - https://github.com/ansible/project-config/pull/535 - https://github.com/ansible/ansible-zuul-jobs/pull/583 - https://github.com/ansible/project-config/pull/534 - An admin member of the team needs to: - Enable zuul on pulp/pulp_installer: https://github.com/apps/ansible-zuul/installations/new - Provide user pabelanger (ansible employee and zuul instance owner) with admin credentials so zuul can get configured properly (it is a playbook that his being run with his account id) - How to refer to 3rd-party services? https://github.com/pulp/pulp_installer/pull/350#discussion_r447955281 - Agreed, PR to define the terms “first-party services” and “third-party services”. We can change terminology later if we can pick better terms. - [mikedep333] plan to do a blog post about the meta roles, and their use cases, and the direction of the installer, to supplement the release announcement. -- Mike DePaulo He / Him / His Service Reliability Engineer, Pulp Red Hat <https://www.redhat.com/> IM: mikedep333 GPG: 51745404 <https://www.redhat.com/>
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
