Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 24 posts

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#11

Post by moondev »

techcofounder wrote: post #6
moondev wrote: post #4

spinnaker as a service. pretty cool idea. what is your planned pricing look like? spinnaker is not cheap to run yourself. Also I tried the "try spinnaker" link and it looks like it timed out at armory.formstack.com

I'm one of the cofounders of Armory. Thanks for letting us know of the timeout - we're looking into that now. Today, our enterprise version of Spinnaker is hosted within your AWS account, not truly hosted Spinnaker as a service, although we def plan to offer that down the road. Our current customers have told us they prefer to run Spinnaker inside their own accounts b/c they fear data leakage.

I see, so it's a centralized control plane for spinnaker installation/upgrades. looking forward to trying it out! I've done a bunch of spinnaker + kubernetes integrations myself. Exciting space for sure.

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#12

Post by georgeaf99 »

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that makes them effective at handling botched deployments and bugs in production.

How y'all are planning to approach the cultural changes companies will have to adopt in order to leverage faster deployments?

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#13

Post by [deleted] »

georgeaf99 wrote: post #12

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that ma…

[deleted]

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#14

Post by imosquera »

georgeaf99 wrote: post #12

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that ma…

We believe that DevOps encompasses 3 areas that must change: people, processes, & technology. We’re seeing evidence that the people/culture is already changing organically because companies must change in order to compete in the software era, and the velocity at which we see software-first companies entering traditional spaces like banking/finance, real-estate, hotel is also accelerating.

That said, in order to make this rate of change to happen faster, instead of trying to convince people through debates, we have to show proof that moving towards a true DevOps model is successful, not just because you get to deploy more, but because it matters to the business. We want to show that CI/CD helps meet SLAs, new valuable features are added and allows the business to address new markets.

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#15

Post by danielodio »

imosquera wrote: post #14
georgeaf99 wrote: post #12

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that ma…

We believe that DevOps encompasses 3 areas that must change: people, processes, & technology. We’re seeing evidence that the people/culture is already changing organically because companies must change in order to compete in the software era, and the velocity at which we see software-first companies entering traditional spaces like banking/finance, real-estate, hotel is also accelerating. That said, in order to make…

To add on to that: The best way we've found to work with large enterprises (aka Global 2000) is to start w/ just one team & app, show success with that, and then expand from there.

We've found that big companies need to see one team achieving success before they'll adopt it throughout the organization.

We've employed this approach successfully with our first several customers. They're going from from one app --> 5 apps --> "GA" rollout internally.

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#16

Post by techcofounder »

georgeaf99 wrote: post #12

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that ma…

We’ve seen a few fundamental changes in culture across the board.

1. Product engineers are embracing ownership, and despite being on-call, they are excited at the prospect of being able to deploy their apps whenever they want.

2. Ops teams are transforming into engineering teams. When you start to automate everything (monitoring, deployments, testing, etc), it frees up ops folks to work on more interesting problems within an organization.

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#17

Post by imosquera »

moondev wrote: post #11
techcofounder wrote: post #6

Earlier quoted context omitted.

I'm one of the cofounders of Armory. Thanks for letting us know of the timeout - we're looking into that now. Today, our enterprise version of Spinnaker is hosted within your AWS account, not truly hosted Spinnaker as a service, although we def plan to offer that down the road. Our current customers have told us they prefer to run Spinnaker inside their own accounts b/c they fear data leakage.

I see, so it's a centralized control plane for spinnaker installation/upgrades. looking forward to trying it out! I've done a bunch of spinnaker + kubernetes integrations myself. Exciting space for sure.

As of today, that is main value prop, however over time we hope to add other microservices to Spinnaker that will provide value on top of the control plane.

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#18

Post by IgorPartola »

danielodio wrote: post #7

Here's a deeper dive on Spinnaker, and on how Armory is commercializing it for enterprises: http://go.Armory.io/Evaluate

I love that there is a service named Igor. Could never find my name on a keychain or a door sign, but now I have a service named after me :)

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#19

Post by danielodio »

IgorPartola wrote: post #18
danielodio wrote: post #7

Here's a deeper dive on Spinnaker, and on how Armory is commercializing it for enterprises: http://go.Armory.io/Evaluate

I love that there is a service named Igor. Could never find my name on a keychain or a door sign, but now I have a service named after me :)

ahaha nice -- you can learn more about Igor here: https://github.com/spinnaker/igor/blob/master/README.md

Re: Launch HN: Armory.io (YC W17) – We Make Deployments Boring and Self-Service

#20

Post by nodesocket »

georgeaf99 wrote: post #12

Hey y'all, I recently started working on a CI/CD product at an organization where the number of deployments per month is in the same ballpark as Netflix. In my experience, adopting systems for rapid deployments also requires adopting new processes. For example, products that are deployed frequently need to have developers on call during deployment windows. These developers tend to have a specialized skill set that ma…

I just founded my third startup Elastic Byte (https://elasticbyte.net), which is a DevOps and infrastructure consulting company operating as SaaS (public monthly pricing plans).

Indeed culture is a big part of the DevOps puzzle besides software. This mentality shift is also a part of what we offer (training and advice). Individual ownership, moving fast, are all parts of the greater strategy. I've found the talk "You shipped it, you fix it" [1] by Ron Cohen (CTO of Opbeat) a great source of solid ideas.

https://opbeat.com/community/posts/you-shipped-it-you-fix-it...

The old model where developers hand off their code to the ops department is fundamentally a bad strategy because it leads to:

   "It worked fine in test... Ops problem now!"
There is no accountability. If your code causes problems when deployed to production, ops is the one getting a call/page in the middle of the night, and trying to fix the problem for which they have no domain experience or understanding. However, if you deploy your own code at your own pace, then there is accountability.
Post reply on HN