4 ms·
This. OpenStack seems to fit that role well.
by setq 10y ago
This. OpenStack seems to fit that role well.
- discordianfish 10y agoIntroducing the complexity of OpenStack just because you might want to migrate off from AWS at some point?
- setq 10y agoNo. Use ansible and run simultaneous infrastructure targets in rackspace on openstack and on AWS. Scale one up if the other shits a brick.
- 0x44 10y agoSpeaking as one of roughly fifty founders thereof, and also the founder of a (now acquired) startup in the space, it really isn't. The point the OP made about needing an Ops team is magnified by the introduction of OpenStack, and the existence of Rackspace as a (not-quite) provider of OpenStack won't help because their public cloud is going away and there isn't really a replacement as the field consolidated and the consolidated players have shed their OpenStack investments (or are laying off and trying to get away from it). If your goal is to avoid the lock-in to a particular IaaS vendor while avoiding ops overhead, your better bet is to go up-stack and lock yourself into either Cloud Foundry or OpenShift. At least then you'll be able to migrate from IaaS to IaaS semi-transparently, but you are locking into a platform.