"Accelerating product delivery in the Digital Economy through Continuous Application Lifecycle Management of Cloud-based Workload, backed by @WalmartLabs"
I think you could work on that elevator pitch a little - it seems like it's been workshopped by a committee, and doesn't really tell me anything.
So walmart thought this startup was worth buying to manage all their different applications running in different clouds. Fast forward a couple years and they've now open sourced the entire product. That's pretty cool.
Its a Multi-Cloud Orchestrator. It lets you abstract multiple cloud providers, so you can say use Azure, S3 , Rackspace Openstack, your own openstack and your own VMware all at the same time, and have unified management.
At the moment it supports any cloud with a OpenStack endpoint/integration.
The chef code that deploys all the apps is pretty old skool, copy pasta'd from opensource cookbooks in alot of places, will never pass food critic or rubocop, and has no tests. I wouldn't really want to run that code on anything.
Because opensource cookbooks are unreliable or people should only rely on your cookbooks? Or old skool isn't new skool so it should be wholly disregarded?
It's a multi-cloud application orchestrator. OneOps lets you design your application in a cloud agnostic way (by abstracting multiple cloud providers). It manages your application's design, deployments, operations & monitoring. At the moment these cloud providers are supported - http://oneops.com/integrations.html#clouds
It's great to see established companies experiment with OSS. The issue I see is that they make their projects go live/public a little bit late to be usable 'as is'. By the time they open source their tooling, the stack maybe out of synch with the latest and greatest. Just the fact OneOps is using nagios checks for monitoring tells you a lot.
Has anyone seen anything talking about resource requirements for deploying this? The fact that Cassandra, ElasticSearch, PostgreSQL are all involved plus much more makes me think the requirements must be quite high.
I'm not sure my brain is up to wading through the site trying to figure out what this is. Can someone break this down into it's purpose and components? Is it a code deployment system, container manager, open-stack, chef/puppet/fabric?
It's a multi-cloud application orchestrator. OneOps lets you design your application in a cloud agnostic way (by abstracting multiple cloud providers). It manages your application's design, deployments, operations & monitoring.
At the moment these cloud providers are supported - http://oneops.com/integrations.html#clouds
I'm kinda surprised by this. My impression was that Walmart Labs had great success in deploying a pure-openstack private cloud in record time which was immense in scale. Why would they want to deploy to other clouds?
As your business grows at some point it may be cheaper to run your own cloud (OpenStack or something else), and you can start migrating your workloads with a PaaS layer like this.
At my previous employer the loaded TCO for running in-house OpenStack was 45-50% of AWS (the company used both).
IMO, it is more than that. It allows you to model your application (currently supports these software stacks http://oneops.com/integrations.html#software) in a cloud agnostic way and manages it's life-cycle
You might want to take a look at https://github.com/StackStorm/st2 if you want python support, chatops, UI, a GUI editor for writing workflows and a strong community.
Disclaimer: I am a programmer at StackStorm. I'd be happy to help.
[+] [-] bitdeveloper|10 years ago|reply
I think you could work on that elevator pitch a little - it seems like it's been workshopped by a committee, and doesn't really tell me anything.
[+] [-] arturadib|10 years ago|reply
[+] [-] dang|10 years ago|reply
[+] [-] bdcravens|10 years ago|reply
[+] [-] corpophobic|10 years ago|reply
[+] [-] glup|10 years ago|reply
[+] [-] shanemhansen|10 years ago|reply
[+] [-] willyk|10 years ago|reply
[+] [-] dubcanada|10 years ago|reply
[+] [-] voidlogic|10 years ago|reply
At the moment it supports any cloud with a OpenStack endpoint/integration.
Blog post: http://www.walmartlabs.com/2016/01/oneops-now-available/
[+] [-] willejs|10 years ago|reply
[+] [-] workitout|10 years ago|reply
[+] [-] ealexhudson|10 years ago|reply
[+] [-] SureshG|10 years ago|reply
[+] [-] msisk6|10 years ago|reply
Looks fairly complete and extensible, though.
[+] [-] mansilladev|10 years ago|reply
And by the way, it's not just OpenStack. Looks like it's also tooled for AWS.
[+] [-] cubano|10 years ago|reply
[+] [-] rodionos|10 years ago|reply
[+] [-] phildougherty|10 years ago|reply
Has anyone seen anything talking about resource requirements for deploying this? The fact that Cassandra, ElasticSearch, PostgreSQL are all involved plus much more makes me think the requirements must be quite high.
Edit: nevermind http://oneops.github.io/admin/prerequisites/
[+] [-] mey|10 years ago|reply
http://oneops.github.io/admin/key-concepts/#oneops-system-ar...
Side note, every-time I see an enterprise message bus, I throw up in my mouth a little.
[+] [-] SureshG|10 years ago|reply
[+] [-] unknown|10 years ago|reply
[deleted]
[+] [-] sithadmin|10 years ago|reply
It's the cloud equivalent of a Super Wal*Mart
[+] [-] pm90|10 years ago|reply
https://www.openstack.org/summit/vancouver-2015/summit-video...
[+] [-] voidlogic|10 years ago|reply
You might also want to quickly gain a presence in a geographical region you don't have hardware in (ever or yet).
[+] [-] protomyth|10 years ago|reply
Christmas / Thanksgiving shopping in the US would be my guesses.
[+] [-] detaro|10 years ago|reply
* cloud bursting during high load
* disaster recovery
* putting things in geographic regions where they don't have their own hardware
[+] [-] perseusprime11|10 years ago|reply
[+] [-] ashayh|10 years ago|reply
They should have put up a blog post with an overview like this one: http://techblog.netflix.com/2015/11/global-continuous-delive...
[+] [-] thoughtpalette|10 years ago|reply
[+] [-] frik|10 years ago|reply
[+] [-] pjc50|10 years ago|reply
[+] [-] serg33v|10 years ago|reply
[+] [-] antongribok|10 years ago|reply
At my previous employer the loaded TCO for running in-house OpenStack was 45-50% of AWS (the company used both).
[+] [-] SureshG|10 years ago|reply
[+] [-] wyclif|10 years ago|reply
[+] [-] dschiptsov|10 years ago|reply
Why, for the love of God, why?
[+] [-] brento|10 years ago|reply
[+] [-] lnkmails|10 years ago|reply
Disclaimer: I am a programmer at StackStorm. I'd be happy to help.
[+] [-] gmtgmt|10 years ago|reply
[+] [-] phildougherty|10 years ago|reply
Edit: Full disclosure, I am the founder of ContainerShip.
[+] [-] sciurus|10 years ago|reply