What about xip.io ? or dnsmasq to avoid such change into your dns config. Do you have DEA ? Staging is done into the DEA (runner) VM. wrote:

Agree you need more space.. wrote:

Yes it is possible, you can colocate job. flavio.schuindt(a)gmail.com> wrote:

It seems that your local machine is running out of space. wrote:

I brought up the VM that I used to issue boch micro command to AWS. I was able to proceed. Now i am hitting a different issue when i execute bosh upload

Hello, We are new to cloud foundry. This is our first attempt to deploy cloud foundry on openstack using BOSH. We are following the instructions in this

Update; ha_proxy_z1 updating job completes successfully after I changed stemcell to bosh-vsphere-esxi-ubuntu-trusty-go_agent and using version cf-210, deployment completes and was able to create org

I succesfully deployed CF on aws using this tutorial: http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html But this tutorial is kind of expensive...It creates 13 machines (one for each cf

Hi folks, I am reposting this email which I earlier sent out to cf-dev group. This is also something we briefly discussed during the recent PMC Bosh meeting. As suggested by Dmitriy (PMC leader for

CVE-2015-1328Severity: High Vendor: Canonical Ubuntu Versions Affected: Canonical Ubuntu 14.04 LTS with 3.16 kernel Description: Philip Pettersson discovered a privilege escalation when using

Ok, some thoughts: 1) Aristoteles Neto, did you have to set this property even using c3.large? I ask it because your manifest is using c3.large and I didn't have any kind of problem using c3.large or

Thanks Gwenn and Pablo. I have attached bosh-registry.log and bosh_micro_deploy.log herewith. Thanks for your time. Sincerely, Dulanjalie wrote: -- Dulanjalie

Thanks a lot Pablo Alonso for your response and for your analysis that microbosh DNS is always placed at end of the resolv.conf and hence should not harm bosh resolution w.r.t. explicitly configured

Hi. If you are trying to unset dns properties, maybe this might work (at least, DNS properties should not be set at director.yml): apply_spec: properties: dns: null However, as far as I have

Hi, I understand that by default the micro-bosh has DNS enabled (i.e. hosts a powerDNS servers that gets injected by default in all VMs it manages). If the dns entry [1] is specified, additional DNS

I'm creating some bosh jobs and in one of them i need to overwrite and customize these files what is the best option to do so in all the other examples i have seen i see that they set a config file

Yes sorry, I forgot that you file a the micro bosh deployment, so you can use the log file generated by bosh.

Hi. You won't get any information from bosh tasks while troubleshooting a bosh micro deployment, because bosh micro plugin (used to deploy microbosh) does not perform a regular BOSH deployment. There

Hi Gwenn, I executed "cfoundry(a)c-foundry:~/micro-deployment$ bosh tasks recent --no-filter" to get the task number but i get "Please choose target first" as the output. I am unable to get any logs

The stemcells are ubuntu, and /etc/resolvconf/resolv.conf.d/head does not exist. $bosh stemcells +------------------------------------------+---------+-----------------------------------------+ |