#office-hours (2019-04)
“Office Hours” are every Wednesday at 11:30 PST via Zoom. It’s open to everyone. Ask questions related to DevOps & Cloud and get answers! https://cloudposse.com/office-hours
Public “Office Hours” are held every Wednesday at 11:30 PST via Zoom. It’s open to everyone. Ask questions related to DevOps & Cloud and get answers!
https://cpco.io/slack-office-hours
Meeting password: sweetops
2019-04-01

I won’t be able to make this Wednesday’s Office Hours

thanks for the heads up

actually, I should update it now to announce to #announcements
2019-04-03

Yeah, no conference rooms available

I dislike open offices~

ah bummer

any questions I can monologue to you?

Yeah, I pitched the idea of hiring y’all to help bootstrap a bunch of projects we don’t have time for

Could you explain how you might go through getting started with us and basic costs

I can hear, just can’t talk

Yeah, we need line cooks

Yeah, I like the aws account arch + kubernetes + release engineering + all that

I built out our roadmap long before I found y’all, and they almost exactly match

kubecost sounds awesome

I hadn’t worked out the details on a lot of stuff, just the general arch

we’re moving towards a services architecture

When you say 8 sprints, is that 8 weeks?

ah, okay, so 16 weeks

Right now we have a bunch of legacy crap, about 8 or so services, that need a bunch of code work to split up

and has a data monolith behind the app/code monolith

and we have about 6 new services

that are all containered / 12factor etc.

You can thank me for that

I pushed hard lol

Then on top of that, we have another company we bought that i need to fold in to this at some point

so you basically have a prod / preprod / unlimited-staging environments clusters?

okay, so, 2 there, plus shared

got it

yeah, 100%

my concern there with unlimited staging though is, then that differs from prod

i don’t quite understand the technical way to set that up, but i love the idea

yeah, mock sqs, eg.

so with unlimited staging, are you still mocking stuff like SQS?

Yeah, slick

So, how would you approach a customer who has an existing production environment?

Would you use that as your root account, and build org out from there?

Yeah, I was looking at doing that completely fresh thing, but the logistics of migrating 8ish years of data boggled my mind

DMS doesn’t work for us, we tried =(

It doesn’t support some postgres features we use

That it is not But downtime is frowned upon

I’m pushing separate down to RDS, all new services are working that way

But, maybe I can make a case for it yet. I’m trying, we just don’t have enough dudes to do the work

I don’t disagree

I understand the value add

I briefly looked at it

I guess lastly, how do you approach helping a dev team learn and adopt new ways to develop services? We’ve got a lot of old school dudes who are still using vagrant boxes and stuff

doggo stream!

Grats!


I have to tap out. Thanks for the time @Erik Osterman (Cloud Posse); enlightening as always. I’m excited to see updates to the ref archs. Hopefully I can dedicate time to geodesic and getting my stuff off the ground here soon Or talk someone in to spending more money
2019-04-10

@jober has joined the channel

A getting-started guide for Cloud Posse’s Geodesic. - osulli/geodesic-getting-started

Example Terraform Reference Architecture that implements a Geodesic Module for an Automated Testing Organization in AWS - cloudposse/testing.cloudposse.co


terraform init -from-module=....

@raehik has joined the channel


@Josh Larsen has joined the channel


Wrap up your bash scripts into a modern CLI today. Graduate to a full-blown golang app tomorrow. - mumoshu/variant

I tuned in late, are these office hours recorded by zoom where I could rewatch it later?

Thanks all, especially @Erik Osterman (Cloud Posse) for hosting and @oscarsullivan_old for the demo



Sad I couldn’t join in at the beginning, sprint planning ran long

happy to answer Qs on the flow or show again

Thanks so much for the time it was very helpful!

big thanks for that! lot of stuff I can discuss with the team & hopefully get using the newer Geodesic versions (we’re using a ver older than my PR T_T)

My boilerplate terraform.tf – saves a lot of repetition across projects and took a long time to build up.

I think the confusion I have in adopting it is what goes in Dockerfile vs what might go in an .envrc and what/how do i split up my terraform in to digestable chunks. I haven’t really dug in in earnest yet, though. It keeps getting bumped in sprint planning and I haven’t had time to just get started outside work hours

Have just added comments to the terraform.tf

Dockerfile Vs .envrc/tfvars == Public Vs Private

I have a little debate with myself here https://github.com/osulli/geodesic-getting-started/blob/master/docs/getting-started.md#geodesic-usage-variables-and-terraform

Yeah, but what is local
to you - a specific app/service? a whole environment inside an account?

a terraform project

Examples:
Global variables: AWS_REGION, BUCKET_NAME, and STAGE
Local variables: JENKINS_INSTANCE_SIZE, API_NODE_COUNT, and CLUSTER_NAME

Example variables set in the Dockerfile AKA public variables:
ENV TF_VAR_stage="sandbox"
ENV TF_BUCKET_REGION="${AWS_REGION}"
ENV TF_BUCKET="${NAMESPACE}-${TF_VAR_stage}-terraform-state"
ENV TF_DYNAMODB_TABLE="${NAMESPACE}-${TF_VAR_stage}-terraform-state-lock"

Yeah, my issue is, what does that terraform project represent? looks like to you it means a service? Jenkins in that example

Example .envrc AKA ‘local variables’
# Set JENKINS specific variables and export them to Terraform, Atlantis, and env
export JENKINS_INSTANCE_SIZE="t2.large"
export JENKINS_DOMAIN_NAME="[jenkins.domain.com](http://jenkins.domain.com)"

Yes I usually break down a TF project into a service

If I did a whole stack it’d be a nightmare IMO

That would just become a monolithic infrastructure project

Yeah, that’s what I’m trying to avoid

It’s like.. a micro-service but infrastructure

that’s how I go about it

or maybe just a service, not a micro-service.. key point is that my project called jenkins only contains jenkins related stuff

As much as I’d love to be able to go “aws, give me a new account, run terraform on it, hey look my new environment is done” I’m not sure that’s as useful as it sounds.


I’m sure I shared a project I use

ah damn not merged and its about a month old

already changed a fair bit

I mean, I’m working my boss, I’m hoping I can just hire Erik and the team to jumpstart the whole process, this becomes a moot-ish point that I don’t have to decide alone

haha thanks @Alex Siegman

On that thread, what’s the best way to have a more formal discussion with y’all about that?

@Alex Siegman let’s jump on a call later this week. Find a time here that works for you: https://calendly.com/cloudposse

2019-04-17





apk add tmate@testing
tmate-session --start # | --stop | --server
2019-04-22

@dalekurt has joined the channel
2019-04-23

@fernando.alvan has joined the channel
2019-04-25

@mohamed.naseer has joined the channel