Re: Can someone shed some light

Gabriel Rosenhouse <grosenhouse@...>

Hi Mario,

First off, I don't believe that XenServer is a supported for bosh-lite, so
you're kind of on your own here. That said:

bosh upload release https://.... is notoriously slow on bosh-lite on
virtualbox. I highly recommend that you first download the release tarball
to your local machine ( and then

bosh upload release /path/to/local/tarball/cf-release-246.tgz

my interpretation of the boshlite doc page you linked to (, is
that the contents of the stub file are simply the three lines

system_domain: # Replace with your system domain

but it also says that bosh-lite doesn't need a stub file unless you want to
change the system domain. the bosh deployment manifest can be generated
without the stub.

In the case of a full deployment to a real IaaS (not bosh-lite), one needs
to write a stub files that is larger, specifying IPs, database connection
strings, passwords, certificates, keys, etc that are needed to configure
that installation. Since bosh-lite isn't meant for production use, the
manifest generation scripts just use default values.


On Sun, Nov 13, 2016 at 7:21 PM, Mario Jauvin <marioja(a)> wrote:

I am trying to use bosh-lite with couldfoundry.

I have copied the virtualbox VM used by bosh-lite and imported it to a
XenServer resource pool. I am able to use the 'vagrant up --provider
xenserver' command and target the bosh directory to the VM. However, I do
not understand what is the manifest stub being referred to in the second
paragraph of the following page:

If I ignore this comment and proceed to:

upload the stemcell
bosh upload release

The process takes forever (I tried for almost 24 hours and the bosh task
status became 'timeout'.

Some notes, I uploaded the latest stable release because there were errors
when compiling. The manifest cf.yml has over 4,000 lines.

I don't understand everything clearly about cloudfoundry so I would
appreciate any help. I know my using XenServer throws a spin in the

I think that the manifest stub is where I could select a domain that could
redirect my request to the proper VM but frankly I really do not understand
this fully. My specific questions are:

1. what is the stub manifest referred to in the page? Where is it located
and what should it look like? Where is the documentation about it?

2. when and why should I defined this stub manifest and how should I use

3. Am I doing something totally wrong in how I am going about it
(especially using XenServer)?


Join to automatically receive all group messages.