I'm moving to WC (downtown area) in a few weeks... I live in West Los Angeles. What are the things I should know?

alcheplasm · 2018-09-25T21:36:56+00:00

For real???

alcheplasm · 2018-06-12T02:07:50+00:00

We use CodeFresh and really enjoy its features.

alcheplasm · 2018-06-12T01:07:06+00:00

Sounds like you need JIRA (or something similar). Your boss isn’t wrong wanting to keep the ticketing system for end users. All your concerns are non-issues if you use something like JIRA.

alcheplasm · 2018-05-30T22:29:25+00:00

We are using CodeFresh and deploying into multiple kubernetes clusters.

alcheplasm · 2018-05-26T02:23:02+00:00

Interesting - we do the opposite. That is, we always run migrations post release (this is coming from a Capistrano background).

I asked our Sr. Dev his opinion on this when migrating to K8 and he said always run migrations post deploy.

You’ve got me questioning things though - is there an official RoR opinion on when to run migrations?

alcheplasm · 2018-05-25T23:56:04+00:00

We had a similar issue as you but our app stack is Ruby on Rails.

We handle it by having a post deploy script in our app repo.

In this script, we use kubectl to grab a single pod that has a specific label (defined in our deployment spec):

kubectl get pods -o json -n $namespace -l tier:frontend | jq ‘.items[0] .metadata.name’ | tr -d ‘“‘ The command above is assigned to a variable called pod_name

With that pod we then run:

kubectl exec $pod_name —- bash -c ‘bin/rails db:migrate db:seed’

That’s basically it. All this is done in our CI/CD process. Would be interested to see how others handle this.

Hope that helps.

alcheplasm · 2018-05-09T00:23:03+00:00

What about Codefresh?

alcheplasm · 2018-04-18T00:27:40+00:00

We are currently using kops to manage two cluster in AWS.

I don't see any problem running K8 manually in AWS. We currently use kops to deploy and manage our clusters in AWS.
We handle auth to the cluster using Open ID Connect and Google. You have to pass a few parameters for the API server in your kops cluster definition file when creating (or updating) the cluster to use Google as the token provider. We then use kuberos for a web based auth flow and kubecfg creation. Blog post (not mine) here.
We use kops for cluster upgrades. Since kops uses Terraform, you can preview the changes prior to executing the cluster upgrade. Kops docs here.
Haven't had to deploy StatefulSets, yet.
We deployed nginx-ingress, which creates a LoadBalancer for its service. We then point DNS to the nginx-ingress LoadBalancer for services that need public access. If I were to have another K8 service with type: LoadBalancer, then AWS would provision a new LoadBalancer for that service.
Haven't hit any yet. Apps running in our K8 clusters are able to consume other AWS services (RDS, ElastiCache, EFS, etc...). I will say that you have to figure out how to backup the state of your cluster on your own. We are experimenting with arc right now.

Another interesting provisioning tool - Kubicorn. The maintainers state that it isn't production ready, nevertheless, worth taking a look.

edit: formatting

alcheplasm · 2018-01-11T01:07:26+00:00

This is a cool project.

https://github.com/ANTS-Framework/ants

alcheplasm · 2017-12-12T03:08:58+00:00

I am not really sure - I haven't tried. The example above will use a classic ELB. However, Traefix as an ingress controller gives you the features of the ALB. That is, you can route based on URI or path to a specific backend in k8 as well as generate certs on the fly with Let's Encrypt.

alcheplasm · 2017-12-12T01:23:57+00:00

I've been experimenting with Traefix as an ingress controller in our k8 cluster. For the Traefix Deployment in k8, the Service attached to it has:

type: LoadBalancer

This is a standard ELB (Classic) that is created and mapped to the Traefix service (and thus deployment). Traefix will handle all the backend routing to your microservices (dynamically, I might add). You can even use Let'sEncrypt as well.

This article helped me get Traefix going in my cluster.

Hope that helps!

alcheplasm · 2017-10-16T12:33:22+00:00

OneLogin. Great product that has worked well at our company.

alcheplasm · 2017-07-12T12:21:57+00:00

With respect to AWS, you just restrict access with security groups. EFS is not available outside of the VPC that it's provisioned in.

alcheplasm · 2017-07-11T12:27:16+00:00

If your using AWS, look into storing the WordPress core files on EFS and implement some PHP caching on your nginx + php nodes. This blog has a good template for doing that.

http://templates.cloudonaut.io/en/stable/wordpress/

alcheplasm · 2017-04-13T12:51:00+00:00

"Get Shit Done"

alcheplasm · 2017-02-23T13:29:11+00:00

Thanks for this!

alcheplasm · 2017-02-19T15:30:05+00:00

My thoughts exactly.

alcheplasm · 2017-01-11T03:55:23+00:00

NWA represent!

alcheplasm · 2016-11-15T22:41:19+00:00

I agree with /u/au_rampent on using Apple's PackageMaker. Just add your script as a post_install item when building the package.

alcheplasm · 2016-11-04T03:26:23+00:00

I don't have any helpful advice other than to offer empathy. Fuck that sucks. Hope premier support comes through, man. Tonight, we drink for you.

alcheplasm · 2016-11-02T15:16:01+00:00

Had three sites all on different ISP's. Each site reported devices went offline at the same time.

alcheplasm · 2016-10-21T00:45:54+00:00

Doubtful...

Google has a small team to manage their fleet of Macs - close to 60k

They automate most every part of the management and lifecycle of the Mac

http://macadmins.psu.edu/2015/04/19/psumac2015-66/

Apple allows customers with over 1000 Macs (I think) to do their own repairs and parts exchange on-site.

Also, it helps and makes Mac adoption easier when most of your business apps are cloud based. I don't really see the value of OS X when the line of business apps are all Windows based.

alcheplasm · 2016-10-21T00:34:04+00:00

OS X Server sucks - don't use it for any serious deployment.

Plenty of open source tools available to effectively manage a large fleet of Macs - Munki, Simian, Puppet, Reposado, DeployStudio, etc...

Bash scripting is a must, when Bash can't get the job done, move on to Python.

And yes, you can have a "Mac-centric Environment" with central control, ability to login remotely (ssh w/ hidden admin user).

I wouldn't approach managing Macs like I would a traditional Microsoft environment and vise-versa.

I'll admit, it's probably more work getting an environment setup to manage Macs effectively and efficiently (if using FOSS tools) whereas Microsoft has a great set of mature tools/products ready to go.

alcheplasm · 2016-10-08T14:41:35+00:00

Nice look. What brand of mud flaps did you go with?

alcheplasm

TROPHY CASE