# 2021-11-01 - 2021-11-05

## David Mason
* Still have lots of ad-hocs coming in, trying to keep up with them, but sacrificing velocity on planned work to do so
* Q4 Big Rock VPN Replacement still being tested
* tested various client OSes
* began planning and testing for kubernetes integration
* Obtained pricing, quotes, reviewing
* Some forward progress on anaconda.com migration, planning a ready date of 11/10
* Updated Kandji profile settings to increase employee contentment, eliminate krufty settings
* New Hire Cohort for 11/1 processed and onboarded
* Monthly tech expense report
* Working through Meraki license changes
* Intake and level set for systems engineer role

## Ryan Houle
* MacOS integration - Met with Jannis to get his perspective
* Navigator CD - Met with Yaroslav to go over current state
* Helping Clients team work through potential split
* ZTA testing and learning
* Researching of Windows/Mac adhoc/automated deployment

## Peter Wilson
* Mostly work on standardizing a flexible deployment of EC2 instances - built out the branch, ready for review next week
* Progress on other big rock items:
* Finished up tagging standard, put in confluence
* Getting started on SSL certs

## Ximena R Rogers
* Scheduler instance for Europe/Berlin done (7to7), working modifying the actual documentation of this. It will be automatically applied by terraform using the EC2 template that Peter is working on. :slightly_smiling_face: I can tell we’re saving money with this at least only regarding with EC2
* short doc about how terraform works locally and use with aws sso (I thought it might be worth to create one about it)

## Agustín García Flores
* Nucleus
* @Maurice (Berlin - CEST) is hard at work with the refactoring of the Terraform code (this used to be just about the EKS cluster but have mutated, by necessity, not choice, into a much bigger effort). We should have a first operational EKS cluster deployed with the new code next week.
* Nucleus community is live! From the infra team we have help with setting up communication between Discourse SaaS and our infra and also doing some changes to our GitHub Action runners so QA automation can run tests against Discourse.
* Legacy data pipeline to AWS move:
* We identified a couple of issues that were preventing the current AWS data to work with data coming from repo.anaconda.com.
* The BI team did some changes to the pipeline that we have deployed and tested updating a full day of data from repo.anaconda.com.
* Once BI validates the output of that tests, the next step will be plumbing our dev environment in AWS to the live data coming from Cloudflare to validate that we have enough throughput.

## Carl Anderson
* Lots of learning this week.
* Package Mirroring with help from Crystal, Alan, Cheng
* learned about the scheduled cloning process
* learned about the different package destinations
* saw how cloudflare serves s3 for some repos
* DataDog
* spent more time creating 3x scavenger hunts
* updated an alert for distro with better hints
* DataPipeline
* met again with Agustin, Stan, Fabio, Albert, et al
* SBOM
* started code review for new `sbomtool` which will run on zeus
* TODO
* start The Life of a Package presentation / story
* update monitoring for the cloning process (still getting daily alerts)
* Tag stale confluence pages as stale and start cleaning them
* [How To....](https://anaconda.atlassian.net/wiki/spaces/AD/pages/107217034/How+to....) is a good starting point of pages to read / review
* [Say you wanna...](https://anaconda.atlassian.net/wiki/spaces/AD/pages/16450715/Say+you+wanna+build+a+package+for+the+distribution+team) needs TLC
* [Distro Mirroring](https://anaconda.atlassian.net/wiki/spaces/AD/pages/67076889/Distro+Mirroring) has outdated steps shown in diagram - gets vague about the clone process
* propose changes for `sbomtool` to minimize risk to zeus