IBT: Leads #22

madcharlie02 · 2023-10-01T19:39:43Z

Overview

This issue tracks the agenda for our weekly meetings

Issue Template

## [Date ]  Meeting Agenda

### Prework to prep for meeting

### Recurring items
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/incubator/projects/1#column-19648741)
 - [ ] reviewing any issues in the [questions and review column](https://github.com/hackforla/incubator/projects/1#column-19648744)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team member
       - [ ] [Charles](https://github.com/hackforla/incubator/issues/assigned/madcharlie02)
       - [ ] [Bonnie](https://github.com/hackforla/incubator/issues/assigned/ExperimentsInHonesty)
       - [ ] [Jason](https://github.com/hackforla/incubator/issues/assigned/JasonEb)
       - [ ] [Judson](https://github.com/hackforla/incubator/issues/assigned/nyarly)
       - [ ] [Robin](https://github.com/hackforla/incubator/issues/assigned/robinglov)
       - [ ] [Jenny](https://github.com/hackforla/incubator/issues/assigned/jennyc910)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label](https://github.com/hackforla/incubator/issues?q=is%3Aopen+is%3Aissue+label%3Aepic) and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ]  hackforla/ops#27 hackforla/ops#47

### New Items
- [ ] 
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items

Links to other agenda issues for your team

(so that you can easily post on their agendas items that come up at yours)

Previous Meetings (link to each comment with the date)

The text was updated successfully, but these errors were encountered:

madcharlie02 · 2023-10-04T01:20:34Z

2023-10-03 Meeting Agenda

New Items

How many members are in each project, and their tasks
review all issues that are in the [new issue approval column]
finish adding labels to the issue
review issues with [epic label] and define how to break down further
Recruiting Terraform people
Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

Disect open issues and their updates

ExperimentsInHonesty · 2023-10-04T01:37:52Z

epics:

migration to terraform
~~Standards setting (arguably not)~~
documentation and templates (wiki)
- docs/ md files
  - inline templates (aprox 40 lines of code)
deployment for projects
- people depo
- civic tech jobs
- Access the Data
enhancements (new features, requested, approved, denied)

Judson says CI/CD is outside of the scope of incubator and should be handled by GitHub Actions. Bonnie says the responsibility should land with Devops

madcharlie02 · 2023-11-15T02:32:32Z

madcharlie02 · 2023-11-29T02:21:27Z

robinglov · 2024-01-03T02:27:00Z

robinglov · 2024-01-15T02:33:37Z

2024-01-16 Meeting Agenda

Prework to prep for meeting

Create Ops Roadmap ops#24

Recurring items

review any issues that are in the new issue approval column

- [ ] reviewing any issues in the questions and review column

New Items

RG: Jason, (This is a test) GHPAGES-DOCKER needs to be updated ops#37 seems to be dependent on (This is a test) GHPAGES-DOCKER needs to be updated ops#36 but it doesn't show a dependency.
RG: Jason, you wrote this draft for Create a Penetration Testing plan ops#40. Can you break it up or do we need to?
Carry over Items to next meeting that don't get addressed

Relevant Issues

hackforla/ops#72 - Create a “user-management” IAM group

hackforla/ops#60 - Establish IAM Policy

hackforla/devops-security#24 - AWS IAM security improvements

#35 - Investigate automating IAM user management with Terraform

#79 - Create Adding and Managing IAM Permissions to Users with Wiki

From last week's ops meeting

Join HfLA and DevOps
Fundamentals and Concepts
Deploy a Terraform hello world project
Get read access to infrastructure organization (see resources)
Get assigned to project as their DevOps person
Administration
get access to do stuff to that projects' deployment
Become a mentor across all projects DevOps people
expert level
Ability to do stuff to any project
Permissions and Resources management
IAM supervisor / Services Supervisor
Dispenses new permissions and removes permissions for user
Add new services in partnership with Owner
Billing (owner)

Notes from Meeting

Level 1 - Current ‘Ops-group’ minus write access is a good starting point
Level 2 - most common services read and write + exclusion list.

Users are not able to make resources in the portal
make it where we will only accept code from GitHub, (or a specific account from GitHub like Hack for LA, or a specific repository...etc)
- this can make things easier when creating level 2 groups

Task Items

robinglov · 2024-01-24T00:53:16Z

2024-1-23 Meeting Agenda

New Items

RG: Discuss candidates to pilot GHPAGES-DOCKER Build Was Successful ops#45 . Discuss potential dependency on IAM progress.
Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Revised the Create Levels List to add new steps to 1. Fundamentals and Concepts
Create Levels

Join HfLA and DevOps

Fundamentals and Concepts
1. Learn Terraform
  1. Setup personal AWS (we need to find a tutorial for that)
  2. Do HashiCorp Tutorials
2. Deploy a Terraform hello world project to our GitHub Repo
  1. clone the incubator repo, which will contain a sample hello world project and all the necessary files (we will need to create and write instructions for). The incubator will need to
    1. be dockerized.
    2. contain generic (versions.tf, main.tf) in a hello-world directory (for the newbies to copy)
  2. create a new directory called hello-world-name (where name is their name)
  3. copy the tf files
  4. Customize the tf files
  5. make a PR
  6. Your PR will be reviewed and merged and added to our AWS temporarily, probably in a sandbox for reviewing PRs (https://docs.aws.amazon.com/pdfs/solutions/latest/aws-innovation-sandbox/aws-innovation-sandbox.pdf) (Terraform apply won’t work - only able to plan and write code to see that it works and then committed to Github and turn it into PR)
  7. AWS sandbox contents are torn down.
3. Get read access to infrastructure organization (see resources)

Get assigned to project as their DevOps person

Administration
1. get access to do stuff to that projects' deployment

Become a mentor across all projects DevOps people

expert level
1. Ability to do stuff to any project

Permissions and Resources management

IAM supervisor / Services Supervisor (is added to the
Management Group on AWS)
1. Dispenses new permissions and removes permissions for user
2. Add new services in partnership with Owner
Billing (owner) (is added to the Cost Management Group)

Task Items

nyarly · 2024-01-24T17:29:52Z

@robinglov "The incubator will need to be dockerized."

There are two misconceptions here. I'm not 100% clear where they arise, so forgive me from covering all the bases, which for sure means I'll be saying things you already know.

First, Incubator is a) the AWS project where we host HfLA projects before they're ready for their own deployments, and b) this whole Git repo, where the Terraform code to manage that project lives. New HfLA volunteers won't be creating incubators, but adding projects to Incubator.

Second, it's won't be dockerized. "Dockerizing" is the process of taking an application that runs conventionally - e.g. a developer executes it locally, or sets it up to run directly on the host system, and creating a Dockerfile for it in order to build and publish a Docker image. Incubator code doesn't run that way, so dockerizing it isn't sensible. I wouldn't expect the Incubator project to ever include a Dockerfile.

In general no one in the Ops CoP should be dockerizing anything as part of their Ops responsibilities. Each project's developers knows their application better than Ops could, and should be responsible for writing their Dockerfile and publishing the docker image. Ops will provide them with a repo name to publish to. That said, because that's the handoff between Dev and Ops (and having a clear handoff that's the same for every project is hugely valuable), Ops should understand that process, so it makes sense for there to be some training about how to create a Docker image - so that Ops engineers can help train Dev in doing it.

Does that all make sense? I know it's a lot to come out of one sentence, but I think it's important to all be aligned early in the project. Please feel free to @ me in Slack, or schedule some time to go over it.

robinglov · 2024-01-24T19:56:26Z

Does that all make sense?

Thank you @nyarly . This will be immensely helpful to have us all aligned in future discussions.

chelseybeck · 2024-01-24T21:54:59Z

@robinglov I created a Google Doc to store this stuff and track versions

robinglov · 2024-01-30T20:45:00Z

2023-01-30 Meeting Agenda

Prework to prep for meeting

Create Ops Roadmap ops#24

Recurring items

New Items

AWS sign-in
Incubator PR process
Onboarding flow
IAM read-only access
- BW ended up meeting with Chelsey, and I have notes in IAM Groups and Policies.
discuss the remainder of Judson's comment IBT: Leads #22 (comment)

FYIs

PRs ready for review
Chelsey won't be coming this week since BW got all the questions answered, but will come if asked for something specific any other week we need her.

Notes from Meeting

We need to grow our own terraform skilled team, that can review PRs. In the meantime, We should be recruiting at Ops meeting for who on the Ops team is qualified to review the outstanding incubator PRs. See the issue we will be creating for adding an open role to the DevOps board.
We talked about the onboarding and offboarding issue template, and BW fixed the wiki on the product-management repo to point to the correct place.
- Onboard & Offboard: Product #47
- https://github.com/hackforla/product-management/wiki/Onboard-Offboard
Invite Chelsey to next week's meeting to talk about Dockerhub.

We reviewed the new, shorter list of items for Level 1 from the IAM Groups and Policies document that Bonnie revised in consultation with Chelsey.

### Level 1: Fundamentals and Concepts
- Learn Terraform
  - Setup personal AWS (we need to find a tutorial for that)
 - Do [HashiCorp Tutorials](https://developer.hashicorp.com/terraform/tutorials/aws-get-started?ajs_aid=7fca1289-6e29-4e26-8e02-a4e898dad031&product_intent=terraform)
- Get Access and Submit your first PRs
  - Create a PR to Create user account
  - Add your user to the read-only-group to get read access to infrastructure organization (see resources)

and the tasks to make it happen (as defined in prior meetings), and who will do the tasks

- Make or revise existing issues for the following
   - Ops: Create an issue template for new members who are onboarding.
   - Ops: Find a tutorial for setting up personal AWS sandbox
- Make it so that only Merge team members can Merge PRs on both the
   - CB-ops: Devops-security
   - BW-incubator:  incubator repos
- CB-ops: Add examples of terraform file templates for new member to use to create the following prs (How will the instructions change on this [Incubator usage](https://github.com/hackforla/incubator/wiki/Incubator-usage) wiki page)
   - Create a PR to Create user account
   - Add your user to the read-only-group to get read access to infrastructure organization (see resources)

Task Items

add the following to the next Ops agenda 2024-01-31

Notes for the project support section of the meeting

Project Name: website-wiki

Hack for LA has a Docker Hub account (https://hub.docker.com/u/hackforlaops).

Will Ops CoP be managing that resource (i.e., should I make issues for it in the ops repo)?

The current need for this project is to copy an image from a volunteer's Docker Hub to our Docker Hub. https://hub.docker.com/r/vraer/hfla-website-wiki

Create new issues RG

Create contributing file with streamlined instructions on how to download the repository, edit it, and make a PR. Daniel Ridge Bot updates requested ops#52

1. fork the repo to your own github
2. Clone the forked repository into local hackforla directory
```
https://github.com/[YOUR GITHUB NAME/incubator.git
```
cd incubator
 ```
3. Create a branch and change to the branch
```
git checkout -b [CREATE A BRANCH NAME]
```
4. Setup Docker, build and serve the website locally
5. Add or edit files (if setting up a new project on incubator, see those instructions here
6. Commit files to your repo
9. Make a PR to incubator repo

Create new issues (any PM)

Create a recruitment issue to publicize the open roles we have Recruit new DevOps Engineer - Merge Team #51

### Overview
We need to recruit some developers who can review pull requests using terraform on the incubator repo. 
#### Details.  In future we will be growing people on the team to do this, but in the meantime, we need someone to review the PRs that are coming in now.
### Action Items
- [ ] Copy the template on the Ops repo open roles board to a comment on this issue and add the following title
```
# Template to use
```
- [ ] Copy it again to another comment and give it the following title
```
### Draft for current open role
```
- [ ] Edit the draft to customize it for what we need done
- [ ] Get signoff from whomever we think should weigh in on this

### Resources
- [Instructions for how to post a volunteer opportunity on the ops board](https://github.com/hackforla/UI-UX/projects/3#card-53874282)
- [Ops open role board](https://github.com/hackforla/ops/projects/1)
- [Link to the new card we create on the board]
- Currently there are no specific general team meetings, however there is a Team leads meeting on Tuesdays at 6:30pm pst, and tech leads attend on an as needed basis.

Create Branch rules so that only Merge team members can merge PRs on the incubator repo Slack Alternatives: Pumble ops#48

Create template files for the setting up a new project on incubator Create Figma document from Incubator System Design #78

### Action Items
- [ ] Set up a folder called sample-project as a child folder of https://github.com/hackforla/incubator/tree/main/terraform-incubator
- [ ] Write template versions.tf and main.tf file templates
- [ ] Add tf templates to the sample-project folder

Create a simple guide for how to set up a new project on incubator.
Notes for the issue

1. Create a folder called [NAME OF YOUR PROJECT] as a child folder of `/terraform-incubator`
1. Create copies of the files inside /terraform-incubator/sample-project to your new folder
1. Edit files to customize to your project details.

Bonnie create these issues in the ops repo

Consider the CI/CD pipeline product Run Atlantis

### Action items 
- [ ] Review the below potential issues and see how  https://www.runatlantis.io/guide/#getting-started fits into our CI/CD plan.
  - Answer it can be used later once projects are moving out of incubator if we even need it.

Items to add to next agenda, either because we carried them forward or they newly came up.

robinglov · 2024-02-07T02:24:36Z

robinglov · 2024-02-14T02:08:13Z

[2024-02-13 ] Meeting Agenda

Prework to prep for meeting

Create Ops Roadmap ops#24

Recurring items

review any issues that are in the new issue approval column
reviewing any issues in the questions and review column
finish adding labels to the issue that are still missing them (see audit links above)

New Items

[ ]
Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

Add below issues to future leads meeting to ask ops leadership if these are ops issues.
- Make issues from Agenda Task Items (never closes) ops#17
- Create a Guide/Template: Story Points for your project ops#18
Create issue to define processes and responsibilities for upgrading Terraform to newer versions.
- Add dependency to GHPAGES-DOCKER Build Was Successful ops#38

ExperimentsInHonesty · 2024-02-19T03:03:55Z

madcharlie02 · 2024-02-28T02:18:11Z

madcharlie02 assigned JasonEb and madcharlie02 Oct 1, 2023

ExperimentsInHonesty assigned nyarly Oct 1, 2023

ExperimentsInHonesty pinned this issue Oct 4, 2023

madcharlie02 mentioned this issue Oct 9, 2023

Create Milestones for Incubator Project #23

Closed

3 tasks

madcharlie02 added this to the 05 - Team Workflow milestone Oct 11, 2023

ExperimentsInHonesty mentioned this issue Oct 23, 2023

IBT: PM #21

Open

ExperimentsInHonesty mentioned this issue Nov 13, 2023

IBT: Onboard & Offboard: Team Members #27

Open

madcharlie02 assigned robinglov Nov 14, 2023

robinglov assigned chelseybeck Jan 30, 2024

This comment was marked as off-topic.

Sign in to view

robinglov unassigned JasonEb Feb 14, 2024

robinglov assigned jennyc910 Feb 28, 2024

ExperimentsInHonesty self-assigned this Feb 28, 2024

ExperimentsInHonesty mentioned this issue Sep 27, 2024

2024 DevOps CoP Leads Agendas hackforla/ops#118

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

IBT: Leads #22

IBT: Leads #22

madcharlie02 commented Oct 1, 2023 •

edited by ExperimentsInHonesty

Loading

madcharlie02 commented Oct 4, 2023 •

edited by ExperimentsInHonesty

Loading

ExperimentsInHonesty commented Oct 4, 2023 •

edited

Loading

madcharlie02 commented Nov 15, 2023 •

edited by robinglov

Loading

madcharlie02 commented Nov 29, 2023 •

edited

Loading

robinglov commented Jan 3, 2024 •

edited

Loading

robinglov commented Jan 15, 2024 •

edited

Loading

robinglov commented Jan 24, 2024 •

edited by ExperimentsInHonesty

Loading

nyarly commented Jan 24, 2024

robinglov commented Jan 24, 2024

chelseybeck commented Jan 24, 2024

robinglov commented Jan 30, 2024 •

edited

Loading

Notes for the project support section of the meeting

This comment was marked as off-topic.

This comment was marked as off-topic.

robinglov commented Feb 7, 2024 •

edited

Loading

robinglov commented Feb 14, 2024 •

edited

Loading

ExperimentsInHonesty commented Feb 19, 2024 •

edited

Loading

madcharlie02 commented Feb 28, 2024 •

edited by ExperimentsInHonesty

Loading

IBT: Leads #22

IBT: Leads #22

Comments

madcharlie02 commented Oct 1, 2023 • edited by ExperimentsInHonesty Loading

Overview

Issue Template

Links to other agenda issues for your team

Previous Meetings (link to each comment with the date)

madcharlie02 commented Oct 4, 2023 • edited by ExperimentsInHonesty Loading

2023-10-03 Meeting Agenda

New Items

FYIs

Notes from Meeting

Task Items

ExperimentsInHonesty commented Oct 4, 2023 • edited Loading

madcharlie02 commented Nov 15, 2023 • edited by robinglov Loading

2023-11-14 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

Notes from Meeting

Task Items

madcharlie02 commented Nov 29, 2023 • edited Loading

2023-11-28 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

Notes from Meeting

Task Items

robinglov commented Jan 3, 2024 • edited Loading

2024-1-9 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

Notes from Meeting

Task Items

robinglov commented Jan 15, 2024 • edited Loading

2024-01-16 Meeting Agenda

Prework to prep for meeting

Recurring items

- [ ] reviewing any issues in the questions and review column

New Items

Relevant Issues

Notes from Meeting

Task Items

robinglov commented Jan 24, 2024 • edited by ExperimentsInHonesty Loading

2024-1-23 Meeting Agenda

New Items

FYIs

Notes from Meeting

Join HfLA and DevOps

Get assigned to project as their DevOps person

Become a mentor across all projects DevOps people

Permissions and Resources management

Task Items

nyarly commented Jan 24, 2024

robinglov commented Jan 24, 2024

chelseybeck commented Jan 24, 2024

robinglov commented Jan 30, 2024 • edited Loading

2023-01-30 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

Notes from Meeting

Task Items

Notes for the project support section of the meeting

Create new issues RG

Create new issues (any PM)

Bonnie create these issues in the ops repo

Items to add to next agenda, either because we carried them forward or they newly came up.

This comment was marked as off-topic.

This comment was marked as off-topic.

robinglov commented Feb 7, 2024 • edited Loading

2024-02-6 Meeting Agenda

Prework to prep for meeting

Recurring items

madcharlie02 commented Oct 1, 2023 •

edited by ExperimentsInHonesty

Loading

madcharlie02 commented Oct 4, 2023 •

edited by ExperimentsInHonesty

Loading

ExperimentsInHonesty commented Oct 4, 2023 •

edited

Loading

madcharlie02 commented Nov 15, 2023 •

edited by robinglov

Loading

madcharlie02 commented Nov 29, 2023 •

edited

Loading

robinglov commented Jan 3, 2024 •

edited

Loading

robinglov commented Jan 15, 2024 •

edited

Loading

robinglov commented Jan 24, 2024 •

edited by ExperimentsInHonesty

Loading

robinglov commented Jan 30, 2024 •

edited

Loading

robinglov commented Feb 7, 2024 •

edited

Loading

robinglov commented Feb 14, 2024 •

edited

Loading

ExperimentsInHonesty commented Feb 19, 2024 •

edited

Loading

madcharlie02 commented Feb 28, 2024 •

edited by ExperimentsInHonesty

Loading