4 ms·
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 o
by voidlogic 11y ago
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.
Blog post: http://www.walmartlabs.com/2016/01/oneops-now-available/ http://www.walmartlabs.com/2016/01/oneops-now-available/
- rodgerd 11y agoThe same space as ManageIQ/CloudForms and vCAC.
- ultramancool 11y agoThank you. Now that you've summarized this, this sounds like a great idea, a good way to kill lock-in on cloud platforms. I don't know why they couldn't write something so simple and concise...
- vacri 11y agoDoes that not mean that you can then only use the common aspects from the various cloud providers, and miss out on the additional features each supports?
- dsl 11y agoThe general rule of thumb for building big things that work long term is build anything in-house that you can't source from multiple vendors.
- brianwawok 11y ago* Or get source code for the big thing, so at least if it breaks in 5 years you can fix it if you need to.
- voidlogic 11y agoThis 1000x
- Spooky23 11y agoThat's the difference between startup and big environment. Bells and whistles are nice, but handcuff you. If you need a 10 year business plan for a service, you need to limit your choices. I have systems with 40 year history that need to retain data for 30 year into the future. Different thinking.
- Tenhundfeld 11y agoHonest questions, if you don't mind: - What types of systems are these? - When you say "40 year history", do you mean the system was originally written in the 70's, or do you mean it has data going back to then? - Why do you need to keep data for 30 years? Regulatory reasons? Reporting? Or just long-lived data? I'm not doubting anything you're saying. It's easy to imagine systems with those attributes, say, in banking, insurance, legal records, etc. I'm just curious about your specific case. :) Long after the logic of your system has been replaced, the data will live on. It's something I think people tend to undervalue.
- Spooky23 11y agoNo problem -- I'm really passionate about this topic! .gov stuff. Every state in the union has social services systems that were stood up in the 60s and 70s, and have or are being transitioned over time from whatever mainframe they were in to modern stuff. Usually the long term stuff is retained. These folks deal with situations like disabled children who become wards of the state. Their records need to exist well until those children are in their 40s. Thats just one example -- Public works projects are built with 50+ year lifespans, and many of those records are expected to exist for at least that long. There's also a whole historical responsibility thing that I think will become more important. You can develop a deep understanding of how a governor or Mayor made certain decisions going back to the American revolution (my county has records of the legislative body from the Dutch colonial period). Digitalization has erased a lot of that -- in many cases we cannot read data from the 1980s. I think issues like this are already starting to appear on a small/personal scale -- when my grandfather died in 1980s, all of his business records, personal records, pictures, etc were on paper somewhere in his home. You could sift through and keep important things. What do you do when the only protection your data in Dropbox/et al is one missed credit card transaction away from oblivion?
- stonogo 11y ago...kill lock-in, as long as everyone in the whole world acts like an OpenStack interface. Not interested.
- voidlogic 11y agoSo their is no standard on how to present your cloud to the world ATM. I think you would be happy that widely used open-source project like OpenStacks interface is being adopted. I'm sure if you want OneOps to support a non-OpenStack interface that should be possible too, they already support Microsoft Azure for example.
- noja 11y agoThey have to start somewhere don't they?
- giancarlostoro 11y agoThanks, they really need to write a simple summary at the very top that anyone could understand. I guess it's really their first time trying to share something (as far as I know) so they must be accustomed to speaking business lingo.
- rwmj 11y agoSo it's like Deltacloud? (https://deltacloud.apache.org/ https://deltacloud.apache.org/)
- voidlogic 11y agoDoes delta cloud have a UI and mange the business side of things? (When it safe to deploy, when deploys are blocked, etc).
- rwmj 11y agoI actually have no idea. After posting that, I looked at deltacloud git, and there haven't been any new commits since 2013, so it doesn't seem too active.
- moondowner 11y agoProbably more like Apache Brooklyn https://brooklyn.apache.org/ https://brooklyn.apache.org/
- sciurus 11y agoSounds similar to https://www.redhat.com/en/technologies/cloud-computing/cloudforms https://www.redhat.com/en/technologies/cloud-computing/cloud...
- uremog 11y agoThey should probably hire you.
- codemac 11y agoThis page is broken on firefox? https://i.imgur.com/wxSi05R.png https://i.imgur.com/wxSi05R.png