18 ms·

So are we. And so is another department in our org. Frankly, we're doing a piss poor job of it. Migrations don't happen even if manually ran, the compute nodes

by kefka 9y ago

So are we. And so is another department in our org. Frankly, we're doing a piss poor job of it. Migrations don't happen even if manually ran, the compute nodes are already at capacity, even with the meagre VMs we use. I have kept pushing for Mesos myself. I see it as a good way forward. Openstack may be a technical good body of code... But in the end its too convoluted codebase and many moving parts to be effective in most deployments.

benley 9y ago
Mesos isn't really a direct replacement for Openstack, but you're probably still right to be pushing for it. If you roll with Mesos you will still need to solve a bunch of lower-level infrastructure challenges: machine provisioning, basic system config management, storage management (if you want persistent volumes), fancy networking (if you want ip-per-container or any sort of network isolation), and so on. Like Openstack, Mesos brings its own set of new complications. Unlike Openstack, Mesos almost always increases efficiency of operations once it's in use. Openstack always seems to result in more and more effort spent on just operating Openstack...
- kefka 9y ago
  Too true that Mesos isn't a drop-in replacement. Far from it. There is quite a lot of complexity as well in Mesos.. But looking at it, there are also less moving parts with Mesos compared to OpenStack. As a test, I set up a Mesos Cluster in 3 VM's. It wasn't terribly hard at all. But at work, we had an alarm thrown in nagios about critical ram consumption on a node. So I go and do the migrate. It works.... And it doesn't. It migrated the VM to the same node. I had to do 2 extra flags to tell OpenStack to migrate the node properly. That's just ridiculous, and dumb. And not to mention, but Mesos supports proper handling of VMs and migration. It frustrates me to no end the amount of hand-holding I have to do with anything OpenStack based. Whereas Mesos was "Install, configure, run".. With a large amount of work on Configure.

by kefka 9y ago

benley 9y ago

Mesos isn't really a direct replacement for Openstack, but you're probably still right to be pushing for it. If you roll with Mesos you will still need to solve a bunch of lower-level infrastructure challenges: machine provisioning, basic system config management, storage management (if you want persistent volumes), fancy networking (if you want ip-per-container or any sort of network isolation), and so on. Like Openstack, Mesos brings its own set of new complications. Unlike Openstack, Mesos almost always increases efficiency of operations once it's in use. Openstack always seems to result in more and more effort spent on just operating Openstack...

kefka 9y ago
Too true that Mesos isn't a drop-in replacement. Far from it. There is quite a lot of complexity as well in Mesos.. But looking at it, there are also less moving parts with Mesos compared to OpenStack. As a test, I set up a Mesos Cluster in 3 VM's. It wasn't terribly hard at all. But at work, we had an alarm thrown in nagios about critical ram consumption on a node. So I go and do the migrate. It works.... And it doesn't. It migrated the VM to the same node. I had to do 2 extra flags to tell OpenStack to migrate the node properly. That's just ridiculous, and dumb. And not to mention, but Mesos supports proper handling of VMs and migration. It frustrates me to no end the amount of hand-holding I have to do with anything OpenStack based. Whereas Mesos was "Install, configure, run".. With a large amount of work on Configure.