Vadim, thanks for your response. To clarify my thoughts:
1. I did not quite realize that BOSH is not only a deployment tool
(with release management capabilities), but also serves monitoring
purposes. Given the said, I was wondering why not just design BOSH as
a standalone application (which I can run whenever there is a need to
manage my deployments) instead of deploying and let it running within
my target deployment environment. Once I discovered BOSH's monitoring
capabilities, I understand it is not quite possible. From this point
of view also the components provided by BOSH makes sense and so does
the nature of BOSH's architecture. Am I right to assume it is
perfectly legit to deploy all BOSH's components within a single VM?
What are the drawbacks of doing so? Why would you put the components
on separate VMs?
2. I was having (and still have!) troubles to get my head wrapped
around the concept of MicroBOSH. The whole bootstrap process seemed to
me a bit more complex than it could be. What's the purpose of having
MicroBOSH? Why not just move its functionality into the BOSH Deployer
and let it be the 'puppet master' responsible for actual BOSH
deployment. I can easily install the BOSH Deployer on my local machine
(or dedicated VM within the target deployment environment if I wish
to), provide a BOSH deployment manifest and do the actual deployment.
Does the MicroBOSH serve the same purpose to BOSH as does the BOSH to
the actual deployed system (CF, WordPress, etc.)? Am I missing
On Jul 12, 8:28 am, Vadim Spivak wrote:
What specifically do you consider to be complex?
The main components:
Director - API endpoint and orchestrator
Blobstore - where the bits go
Redis - used for coordination
NATS - tiny message bus for Director to VM communication
Was your problem having these individual components? Or more with the
bootstrap process that we have today?
We would love to hear your about experience installing BOSH to see what we
can simplify and improve.
On Wed, Jul 11, 2012 at 2:59 AM, Misiak wrote:
some of you may consider this to be a stupid question, but I am glad
to hear your explanation. I kind of miss the reasons why should be
such a tool as BOSH distributed. If someone can get me a solid
reasoning why is BOSH designed in a way it is (i.e. quite complex
distributed system with lots of moving parts), I would really
(I have successfully installed BOSH in my lab environment (vSphere 5
within vCD) and found the process a bit more complex than I had
expected at the beginning. I think BOSH's architecture has something
to do with that complexity.)