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

Show HN: Your DevOps Control Plane, in Slack

cto.ai

Post reply on HN
Print view View original

21–30 of 38 posts

Re: Show HN: Your DevOps Control Plane, in Slack

#21

Post by ruxandrafediuc »

jasonpeacock wrote: post #16

What happens when Slack is down? Does DevOps also stop, or is there a way to do the same commands/workflows outside of Slack? You don't want two separate run books, as they'll never stay in sync. It'll already be enough of an efficiency hit just switching to an alternative interface when Slack is down, let along switching to different tools/processes.

Hey Jason, Ruxandra here from the CTO.ai team!

You have the freedom to build your DevOps workflows as you please, by leveraging our SDKs to interact with the tools and platform you use daily for DevOps. The Slack interface allows you to customize the inputs and trigger these workflows as you desire, but--once triggered--you will not necessarily depend on Slack being up. Hope that makes sense!

Also, the workflows you automate using our platform work in the CLI as well. So you build once, you get a containerized automation which you can use either locally in your CLI, or in Slack. For running these locally, you have to install our `ops` CLI on your machine (more on this here: https://cto.ai/docs/start-building-ops).

Let me know if that helps clarify your questions or if you have any other questions. Thanks!

Re: Show HN: Your DevOps Control Plane, in Slack

#22

Post by stevehiehn »

jacksonpollock wrote: post #20

@slajax - what are some of your favorite use cases for the platform?

(cto.ai employee here) The obvious ones are any basic CICD operation that you might want to trigger from Slack, i.e: pull code, build code, deploy code. The second use case that comes to mind is treating the platform as a very quick way to build an all purpose SlackBot.

Re: Show HN: Your DevOps Control Plane, in Slack

#24

Post by ruxandrafediuc »

jacksonpollock wrote: post #20

@slajax - what are some of your favorite use cases for the platform?

Ruxandra here from the engineering team at CTO.ai. Thought I'd jump in and say we have some cool examples in our registry, covering automations with various products offered by the popular cloud providers, as well as workflows around creating, managing and destroying Kubernetes clusters, and so much more: https://cto.ai/registry.

I certainly have a soft spot for the K8s ones especially as I helped build them :-)

Re: Show HN: Your DevOps Control Plane, in Slack

#25

Post by markandrewj »

dvohro wrote: post #2

How does this compare to GitHub Actions for Slack?

Maybe I am misunderstanding what CTO.ai does. GitHub actions are for CI/CD pipelines. Where as CTO is a bot for interfacing with webhooks over chat. The broader term would be ChatOps. Something more comparable in the Github world would Hubot. Jesse Newland has some good lectures about why you would want to do this. Many of the examples come down to visibility of work in remote teams, and creating cleaner interfaces to useful products. There are a number of tools, many people use day to day because they are useful, that have terrible interfaces. You also see some organizations consolidating things like knowledge bases. Apologies if I have generalized CTO.ai in a way that is incorrect.

Re: Show HN: Your DevOps Control Plane, in Slack

#27

Post by leosantana »

stevehiehn wrote: post #22
jacksonpollock wrote: post #20

@slajax - what are some of your favorite use cases for the platform?

(cto.ai employee here) The obvious ones are any basic CICD operation that you might want to trigger from Slack, i.e: pull code, build code, deploy code. The second use case that comes to mind is treating the platform as a very quick way to build an all purpose SlackBot.

Why in my conscious mind would I ever wanna do something like this?

Especially that lately Slack has proven to be so unstable (lots of intermittent downtime). Meaning I would just lock my infra automation code in CTO.ai servers for... what?

Re: Show HN: Your DevOps Control Plane, in Slack

#28

Post by mistedissetanti »

leosantana wrote: post #27
stevehiehn wrote: post #22

Earlier quoted context omitted.

(cto.ai employee here) The obvious ones are any basic CICD operation that you might want to trigger from Slack, i.e: pull code, build code, deploy code. The second use case that comes to mind is treating the platform as a very quick way to build an all purpose SlackBot.

Why in my conscious mind would I ever wanna do something like this? Especially that lately Slack has proven to be so unstable (lots of intermittent downtime). Meaning I would just lock my infra automation code in CTO.ai servers for... what?

That's an interesting question and I was wondering the same thing.

Sounds like if we set Slack aside, all that CTO.ai is really offering is buy-in into their platform w/ no clear value beyond the initial slackbot-like integration

Re: Show HN: Your DevOps Control Plane, in Slack

#29

Post by [deleted] »

mistedissetanti wrote: post #28
leosantana wrote: post #27

Earlier quoted context omitted.

Why in my conscious mind would I ever wanna do something like this? Especially that lately Slack has proven to be so unstable (lots of intermittent downtime). Meaning I would just lock my infra automation code in CTO.ai servers for... what?

That's an interesting question and I was wondering the same thing. Sounds like if we set Slack aside, all that CTO.ai is really offering is buy-in into their platform w/ no clear value beyond the initial slackbot-like integration

[deleted]

Re: Show HN: Your DevOps Control Plane, in Slack

#30

Post by mistedissetanti »

Slack as a "control plane" is quite the concept, giving operational power to more people around the company through Slack can be a two-edged sword though.

Now, aside from the implicit risk that this might offer, if Slack acts as the "Control plane" for DevOps, what's the platform's "Data plane"?

Is it right to assume that in order to be independent from Slack we'd need to rely on CTO.ai's own infrastructure and resources? I.e. the data plane where DevOps "effectively happens"

Post reply on HN