Meeting notes

Jump to bottom Edit New page

Ben Ford edited this page Mar 11, 2020 · 5 revisions

2020-03-11

Priorities discussion

In no specific order...

Dependency resolution
- First pass: lockfile generation
- Second pass: automatic resolution on installation
- See also: reidmv may have some work in this space, we should sync with them.
  - (Let's have a meeting with Reid to chat about this)
  - adrienthebo has discussed generating artifacts for Puppet code, does this intersect?
  - filesync/code manager might touch this
- Design this feature in another wiki page?
Performance/parallelization
- Shallow clones (see also: puppetlabs-stdlib)
- Fast checking for Puppetfile module status - checking if an on-disk module takes 80ms, some PE customers have 1000+ modules. There should be opt-in functionality for skipping this check.
- Two phase plan/apply update process
  - Phase 1: fetch sources, download modules, check versions, see what sources/environments/modules need to be changed
  - Phase 2: apply all environment/module changes in parallel
- DNS queries and overly aggressive module deprecation checking
- Overly aggressive file purge checking

Not yet prioritized

Windows support?
- Does puppetserver support Windows?
  - No, but puppet apply works on windows
  - Some workflows use puppetfile install, eg editors like RubyMine
- How many people need this? How difficult will this be? (Probably high cost)
  - it looks like it currently mostly works except for the weird fiddly windows things that take forever to resolve properly.
- Willing to prioritize this if there's demand, but won't immediately jump this to the front of the queue