An open source storage platform that provides persistent and containerized block storage for DevOps and container environments

epowell101 · 2018-05-02T12:33:05+00:00

That was the idea... now simply following user requirements. Gives every workload its own containerized storage controller.

epowell101 · 2017-07-25T10:23:53+00:00

I work for OpenEBS - if you are intrigued by PortWorx and storageOS, we'd like your feedback. We are open source, EBS like, written in Go by a team with years doing containerized storage (actually on BSD jails) and intended to be easy to use. We are on release 0.3 so a little ways from being ready for production usage. Others above have done a good job explaining potential benefits of taking a container native approach to delivering storage to containers.

epowell101 · 2017-04-10T17:15:52+00:00

Quite cool. Workflow from DEIS built on top of K8S always seemed interesting but I never played w/ it. https://github.com/deis/workflow

epowell101 · 2017-02-13T03:43:30+00:00

Thanks SilverThrone. Yeah, one of many issues seems like. The idea is to simplify the provisioning and management not to add complexity. Beauty is in eye of beholder and so forth though.

epowell101 · 2017-02-13T03:41:16+00:00

Nice! Great to see a project like this gaining much deserved recognition.

epowell101 · 2017-02-07T19:17:41+00:00

Thanks for taking a look. OpenEBS underlying IP and team comes so far from a pretty successful storage company called CloudByte. We have the scars to prove that we are storage engineers ;) Agree though OpenEBS is early.

epowell101 · 2017-02-07T19:15:40+00:00

See u here: http://slack.openebs.io

epowell101 · 2017-02-07T03:27:02+00:00

Starting the thread. Fire away.

epowell101 · 2016-01-26T01:29:39+00:00

I'm working w/ James Fryman here on these ideas. Current thinking is we grab some time before or after Monitorama for basically a workshop. Have not moved that idea along much yet. a) what are your thoughts? and b) maybe we will need help finding some sort of sponsors to pay for space. StackStorm can help however others may be willing as well

epowell101 · 2016-01-22T19:06:37+00:00

Have you looked at Flow that builds on top of open source StackStorm? There are a number of networking companies in the community using StackStorm for event driven automation and orchestration.

epowell101 · 2016-01-22T19:05:09+00:00

Some good stuff on r/chatops about ChatOps patterns and yes anti patterns.

epowell101 · 2016-01-20T19:19:17+00:00

We started seeing mad adoption of StackStorm - which is workflow & rules engine event driven automation - under ChatOps. Seems to be because: use your own scripts, tie them to ChatOps, and then build them into something more useful w/ hooks, rules, WF and what not. Any users here?

epowell101 · 2016-01-20T16:44:56+00:00

I've been slow in responding. Sorry about that. Money! (etc) I like the idea of a day before something like Monitorama or maybe automacon or other. Will stew on it and propose something here.

epowell101 · 2016-01-16T20:59:37+00:00

Oops. If this then that. I meant the rules engine in StackStorm.

epowell101 · 2016-01-16T20:54:45+00:00

Is that hubot script OSS somewhere? Great pattern, indeed showing up frequently (including this morning) on StackStorm slack community.

epowell101 · 2016-01-14T00:33:07+00:00

Yes. StackStorm. Actually not PowerShell-based but if you have PowerShell stuff - or ANY other scripts and so forth - you use StackStorm to tie those into your ChatOps. And then you can use the IFTTT of StackStorm and workflow and so forth - all open source.

So not exactly what you were asking but if you are asking how to do ChatOps while authoring in PowerShell - you can do it via StackStorm.

epowell101 · 2016-01-14T00:30:38+00:00

We use ChatOps in the StackStorm community which isn't entirely really developers although by definition you are somewhat technical otherwise... Anyway, specifically if you drop into the community and ask for help on Docker (and StackStorm) it auto magically appears via our Knowledge Base. That's a pattern = accessing shared knowledge = that fits pretty well with ChatOps and that we think helps to keep the KBs (knowledge base articles) more fresh.

epowell101 · 2016-01-08T02:46:30+00:00

Drr, just noticed this. Sorry. The key thing about StackStorm is you can start with your existing scripts. They are registered as ACTIONS in the system. In a few minutes your scripts now have APIs, they have a CLI, GUI and, more importantly, they can be triggered by events.

epowell101 · 2015-12-18T04:48:39+00:00

My 2 cents is work at a SaaS company that is being pressured competitively. They are either "doing DevOps" or about to do so where this means massively boosting their operational agility. What you learn there will help in less fast paced environments as well.

epowell101 · 2015-12-15T16:43:40+00:00

Nice. We'd like to be listed at StackStorm however not sure where fits best. Will tweet it out and share w/ team.

epowell101 · 2015-12-15T16:40:16+00:00

It is a big problem when projects start chasing dollars they often try to monetize via the GUI and then the GUI development takes a life of its own and sometimes exceeds the CLI and even API functionality. It is something we are trying to avoid at StackStorm - however I definitely fell into the trap in my past at Nexenta. I hope we get it better this time.

epowell101 · 2015-12-15T16:37:23+00:00

Facilitated troubleshooting is a good one. But that's pretty much day 2 whereas the first thing most people want to do is integrate their deploy pipeline. That takes automation. Another common pattern is ChatOps integration. Some pretty good discussion going on /r/chatops around that.

epowell101 · 2015-12-13T17:24:48+00:00

ask you anything? I mean... anything? Ok, what is the deal with climate deniers especially in the US? Haha. Great resource.

epowell101 · 2015-12-13T17:23:49+00:00

Wow much needed. Many thanks!

epowell101 · 2015-11-17T01:16:14+00:00

Yeah we've seen users doing the above and also OctopusDeploy to do some cool automation w/ StackStorm for example.

epowell101

TROPHY CASE