3 ms·
64 gb memory for a vsphere deployment is what you would call small? Also I have had a hard time with bosh (and bosh-lite) I liked the lattice approach, but stil
by merb 12y ago
64 gb memory for a vsphere deployment is what you would call small?
Also I have had a hard time with bosh (and bosh-lite)
I liked the lattice approach, but still no proper support for vsphere and openstack.
As already said its simple to do something on aws and gcloud.
We run a lot of things in the cloud especially software for updating our customer software and it is really straight to deal with that.
However we still have some problems in our on-premise software, its really hard to manage that. as you said support for non-cloud or own-cloud environments is hard and thats where our toolset struggles, where everyones toolset struggles.
- parasubvert 12y agoYes, 64 GB for vsphere is "small", mainly because of VM overhead for various pieces. Bosh-lite shrinks that down a lot by using Linux containers. Lattice shrinks it more. Lattice is nice because it strips out the security layer, multi tenant controller, and BOSH ...but no other configuration framework has a rich Vmware/Openstack support. It suppose it's possible to whip up some Chef recipes / Ansible play books with Fog scripts, as BOSH really is a wrapper around Fog. I found BOSH hard to learn at first but now I love it, it's my favorite config framework AND supports Vsphere/Openstack. The Pivotal version of CF wraps BOSH with a web GUI to make it easy (no bosh-lite sadly), barring that I'd suggest looking at some of Dr. Nic Williams' blog posts and github repos for learning: https://github.com/drnic/bosh-getting-started/blob/master/README.md https://github.com/drnic/bosh-getting-started/blob/master/RE...