search

hackforla / incubator

https://github.com/orgs/hackforla/projects/73/views/5
GNU General Public License v2.0
3 stars 14 forks source link

IBT: Leads #22

Open madcharlie02 opened 12 months ago

madcharlie02 commented 12 months ago

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)

madcharlie02 commented 12 months ago

2023-10-03 Meeting Agenda

New Items

FYIs

Notes from Meeting

Task Items

ExperimentsInHonesty commented 12 months ago

epics:

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 commented 10 months ago

2023-11-14 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items

madcharlie02 commented 10 months ago

2023-11-28 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

-reviewed the apply to add users to the team AWS -reviewed how to create access keys for AWS platform in Terraform

Task Items

robinglov commented 9 months ago

2024-1-9 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items

robinglov commented 8 months ago

image

2024-01-16 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

Relevant Issues

https://github.com/hackforla/ops/issues/72 - Create a “user-management” IAM group

https://github.com/hackforla/ops/issues/60 - Establish IAM Policy

https://github.com/hackforla/devops-security/issues/24 - AWS IAM security improvements

https://github.com/hackforla/incubator/issues/35 - Investigate automating IAM user management with Terraform

https://github.com/hackforla/incubator/issues/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.

Task Items

robinglov commented 8 months ago

2024-1-23 Meeting Agenda

New Items

FYIs

Notes from Meeting

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

Join HfLA and DevOps

  1. 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

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

      Become a mentor across all projects DevOps people

  3. expert level
    1. Ability to do stuff to any project

      Permissions and Resources management

  4. 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
  5. Billing (owner) (is added to the Cost Management Group)

Task Items

nyarly commented 8 months ago

@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 commented 8 months ago

Does that all make sense?

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

chelseybeck commented 8 months ago

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

robinglov commented 8 months ago

2023-01-30 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

Notes from Meeting

  1. 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.
  2. 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.
  3. Invite Chelsey to next week's meeting to talk about Dockerhub.
  4. 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

Create new issues RG

Create new issues (any PM)

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

madcharlie02 commented 7 months ago

Template to Use

Data Engineer (DevOps)

This team member will be responsible for developing data pipelines to clean, transform, and process data. They will ensure data integration between systems, including deployment of machine-learning pipelines where necessary.

Responsibilities

Basic Qualifications

madcharlie02 commented 7 months ago

Draft for Current Open Role

Developer (Terraform)

This team member will develop data pipelines to clean, transform, and process data. They will ensure data integration between systems, including code deployment within Terraform, an Amazon Webservice platform, where necessary. They will design and implement effective database solutions and models to store and retrieve company data. Examine and identify database structural necessities by evaluating client operations, applications, and programming.

Responsibilities

Basic Qualifications

robinglov commented 7 months ago

2024-02-6 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items

robinglov commented 7 months ago

[2024-02-13 ] Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items

ExperimentsInHonesty commented 7 months ago

2024-02-20 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items

madcharlie02 commented 7 months ago

2024-02-27 Meeting Agenda

Prework to prep for meeting

Recurring items

New Items

FYIs

-

Notes from Meeting

Task Items