Original: https://etherpad.wikimedia.org/p/kubecon-2017-offsite-agenda

Archived on office wiki: https://office.wikimedia.org/wiki/Wikimedia_Cloud_Services/Offsite_Notes/kubecon-2017

Decided:

- Stick with Trusty through Neutron migration (for now as we think we are making enough progress on this to ensure Trusty sunset by April 2019.  Xenial seems to have Mitaka so if we have to potentially we can match mitaka there with Trusty for a migration of OpenStack releases across releases but that's work we don't want to do and we need to settle on a distro (see: figure out deployment methodology))
https://phabricator.wikimedia.org/T166845 to be done via cumin for now (long term prometheus?)
- draw.io is a canonical tool
- Dumps work is a carry over goal
- Neutron will be a carry over goal but hopefully not a literal one


Open Near Term:

 - Neutron Plan: talk about the naming of deployents

- Need to do hard capacity thinking on storage scaling and budgeting

- icon templates for draw.io


Open Long(er) Term:
- Need to figure out openstack components deploy methodology (containers, source, distro packaging...)
- Is SLURM viable?
- kubeadm for Kubernetes deploy?
- Tools Bastion and resource issues
- Is there an upstream alternative that is viable for Quarry?
- How much do we fold into cloud-init?
- Do we use puppet standalone and virtualize the main cloud masters?
- Hiera for instances is a mess and  needs to be rethought.
- Trial of paging duty cycles (while still taking advantage of our time spread)
- How much of labtest is ready for parity testing?
- Document undoing standalone puppetmaster setup


Missed because of time:

  • FUTURE IDEAS: NOT EXISTING
  • - new TLDs for public and internal addresses: when and how to deploy
  • - new ingress for HTTPS in VPS and Toolforge?
  • - monitoring sanely
  • - thinking about ceph


I would like to talk about the missed items if we can find a few minutes at all hands (over dinner?)

--
Chase Pettet
chasemp on phabricator and IRC