Date   

Courier was unable to deliver the parcel, ID00000499392

FedEx Standard Overnight <joe.frey@...>
 

Dear Customer,

We could not deliver your item.
Shipment Label is attached to this email.

Regards,
Joe Frey,
Station Agent.


Re: Bosh-init Deployment but can't use bosh micro command anymore

Dmitriy Kalinin
 

Is there any reason to deploy bosh after deploying micro-bosh using
bosh-init?

Not in my opinion regardless if you are using bosh-init or micro CLI plugin.

Regarding error from bosh-init, you can try turning on verbose logging:
export BOSH_INIT_LOG_LEVEL=debug

On Tue, Oct 13, 2015 at 1:59 PM, Satya Thokachichu <tsnraju(a)yahoo.com>
wrote:

I was able to resolve issue by changing dns host to 10.0.0.2..Please
ignore my first question.


Failed to get email notification during health monitoring

Guangcai Wang <guangcai.wang@...>
 

Hi all,

I configured the email notification for health monitor. and I checked the
configure file “jobs/health_monitor/config/health_monitor.yml" in bosh
director.
plugins:
- name: logger
events:
- alert
- name: email
events:
- alert
options:
recipients:
- georgew(a)fast.au.fujitsu.com
smtp:
from: georgew(a)fast.au.fujitsu.com
host: ess-smtp.cloud.nifty.com
port: 587
domain: fast.au.fujitsu.com
auth: plain
user: UQLNCCPCVEAMURC1JC7K
password: ArgrTBpMs65IFLjzH6N/RsbjI/oa2qCtIHS84rZ0lbf7

Then, I stopped one cf VM. BOSH can detect it and recreate that VM itself.
However, I did not get email notification. Anything wrong? it is not enough
to stop one VM? How to test it? Thanks.


Re: Bosh-init Deployment but can't use bosh micro command anymore

Satya Thokachichu
 

I was able to resolve issue by changing dns host to 10.0.0.2..Please ignore my first question.


Re: Bosh-init Deployment but can't use bosh micro command anymore

Satya Thokachichu
 

I am getting confused here...Is there any reason to deploy bosh after deploying micro-bosh using bosh-init? Doesn't it serve same purpose as bosh ? Really appreciate if someone can educate me..


Re: Bosh-init Deployment but can't use bosh micro command anymore

Satya Thokachichu
 

Hi ,

We've been using microbosh -> bosh -> CF model in AWS.. I tried to use bosh-init and able to deploy microbosh successfully..When I am trying to upload stemcell (As part of deploying bosh) ,I am getting following error..

Started update stemcell > Uploading stemcell bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3012 to the cloud. Failed: Unknown CPI error 'Unknown' with message 'execution expired' (00:01:12)

Error 100: Unknown CPI error 'Unknown' with message 'execution expired'
..
Seems like dns issue..I used same manifest as mentioned above..My AWS security groups looks good
When I login to microbosh, nslookup doesnt work..
My resolv.conf says, nameserver 10.0.1.2 ( I am using 10.0.1.0/24 subnet),which seems correct..

Did anyone encounter similar issue? Appreciate any inputs..


Re: UAA integration for the Director

Gwenn Etourneau
 

Sweety !

On Tue, Oct 13, 2015 at 3:33 AM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Congrats on shipping this!




On Mon, Oct 12, 2015 at 11:27 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

Hey all,

Starting with version bosh-release v209+ colocated with uaa v1+ you can
use the UAA for authentication and authorization of the Director users.
This means that you can have read-only users and attach your own
authentication source such as LDAP.

See http://bosh.io/docs/director-users.html &
http://bosh.io/docs/director-users-uaa.html

BOSH team


Backup of persistent storage in vSphere

Jo Stockley
 

Hi,
We have a number of BOSH deployed applications that use persistent disks. My understanding is that these are what VMware terms "independent disks".
I'm looking for ideas on how to efficiently back these up for restoration in the event of failure or disaster.

Any suggestions welcome.

Cheers,
Jo


Re: UAA integration for the Director

Dr Nic Williams
 

Congrats on shipping this!

On Mon, Oct 12, 2015 at 11:27 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

Hey all,
Starting with version bosh-release v209+ colocated with uaa v1+ you can use
the UAA for authentication and authorization of the Director users. This
means that you can have read-only users and attach your own authentication
source such as LDAP.
See http://bosh.io/docs/director-users.html &
http://bosh.io/docs/director-users-uaa.html
BOSH team


UAA integration for the Director

Dmitriy Kalinin
 

Hey all,

Starting with version bosh-release v209+ colocated with uaa v1+ you can use
the UAA for authentication and authorization of the Director users. This
means that you can have read-only users and attach your own authentication
source such as LDAP.

See http://bosh.io/docs/director-users.html &
http://bosh.io/docs/director-users-uaa.html

BOSH team


Re: Add https://github.com/logsearch/logsearch-for-cloudfoundry to bosh.io/releases

Dr Nic Williams
 

Currently an email to Dmitriy works a treat.




Nic

On Mon, Oct 12, 2015 at 7:06 AM, David Laing <david(a)stayup.io> wrote:

Hi all
I'd like to get the next release of the logsearch-for-cloudfoundry boshrelease added to bosh.io/releases
Could someone give me some pointers as to what I need to do?
Thanks!
David


Add https://github.com/logsearch/logsearch-for-cloudfoundry to bosh.io/releases

David Laing
 

Hi all

I'd like to get the next release of the logsearch-for-cloudfoundry boshrelease added to bosh.io/releases

Could someone give me some pointers as to what I need to do?

Thanks!

David


Re: Can one CF instance be backed by two platform containers?

Prysmakou Aliaksandr <aliaksandr.prysmakou@...>
 

Hi Jim,
You are right, Garden is platform neutral API and in one CF/Diego DEPLOYMENT it is possible to have both backends.
You may have many cell INSTANCES, but one cell INSTANCE may contain only one backend.

- Alex Prysmakou /Altoros

On Oct 12, 2015, at 8:13 AM, jinsenglin <jinsenglin(a)iii.org.tw<mailto:jinsenglin(a)iii.org.tw>> wrote:

Hi all

With Diego, Garden-Linux , and Garden-Windows, does it mean that I can deploy one Cloud Foundry instance which is backed by both Linux and Windows containers at the same time?

Sincerely,

Jim @ III > Data Analytics Technology & Applications Research Institute (DATA)


Re: Can one CF instance be backed by two platform containers?

Dmitriy Kalinin
 

Correct, you can have linux and windows cells managed by the same CF
deployment.

(Btw for more detailed CF answers you can try cf-dev mailing list)

On Sun, Oct 11, 2015 at 11:13 PM, jinsenglin <jinsenglin(a)iii.org.tw> wrote:

Hi all



With Diego, Garden-Linux , and Garden-Windows, does it mean that I can
deploy one Cloud Foundry instance which is backed by both Linux and Windows
containers at the same time?



Sincerely,



Jim @ III > Data Analytics Technology & Applications Research Institute
(DATA)


Can one CF instance be backed by two platform containers?

Jim
 

Hi all



With Diego, Garden-Linux , and Garden-Windows, does it mean that I can
deploy one Cloud Foundry instance which is backed by both Linux and Windows
containers at the same time?



Sincerely,



Jim @ III > Data Analytics Technology & Applications Research Institute
(DATA)


Re: bosh depoy - Issues with ssh

Dmitriy Kalinin
 

bosh.pem should contain private key. machines will be provisioned with
associated public key.

did you use aws generated key from the console? also make sure you are
using correct key pair name.

On Sun, Oct 11, 2015 at 11:39 AM, Riaan Labuschagne <zapmanandroid(a)gmail.com
wrote:
Hi,

I am trying to deploy to AWS and everything goes fine until the " Waiting
for the agent on VM.." step has to happen.

I have tried to login to the VM with my pvt key (ssh -i bosh.pem
vcap(a)10.0.0.6) but that also fails.

I mounted the volume of the bosh VM on another VM to check the
/home/vcap/.ssh/authorized_key file and it seems the public key in the
authorized_keys file differs from the pvt key I extract from bosh.pem.

I just cant seem to get past the "Waiting for the agent on VM.." step.

Is the public vcap file sipposed to be the public key form the bosh.pem
file? (I cant see where else it comes from)

Regards.

============================ My deploy output==================


Started deploying
Waiting for the agent on VM 'i-c5aa9563'... Failed (00:00:30)
Deleting VM 'i-c5aa9563'... Finished (00:00:36)
Creating VM for instance 'bosh/0' from stemcell 'ami-89c1f7fe light'...
Finished (00:00:43)
Waiting for the agent on VM 'i-24a79882' to be ready... Failed (00:02:33)

Waiting for the agent on VM 'i-24a79882' to be ready... Failed (00:02:33)
Failed deploying (00:04:29)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Waiting until instance is ready:
Starting SSH tunnel:
Failed to connect to remote server:
ssh: handshake failed: ssh: unable to authenticate, attempted
methods [none publickey], no supported methods remain


Re: bosh micro deploy stuck at Started deploy micro bosh > Waiting for the agent

Gwenn Etourneau
 

Can you try with ubuntu instead of vcap ?

On Mon, Oct 12, 2015 at 4:54 AM, Riaan Labuschagne <zapmanandroid(a)gmail.com>
wrote:

I have the same issue.

I can get through to the VM but it seems like the certificate based login
fails, not comms to the machine.

I get this response when I try to connect manually:

ssh -i ./bosh.pem vcap(a)10.0.0.6

and the response

root(a)gw:/data/CloudFoundry/my-bosh# ssh -i ./bosh.pem
vcap(a)10.0.0.6
Ubuntu 14.04.3 LTS \n \l

Permission denied (publickey).


Re: bosh micro deploy stuck at Started deploy micro bosh > Waiting for the agent

Riaan Labuschagne <zapmanandroid@...>
 

I have the same issue.

I can get through to the VM but it seems like the certificate based login fails, not comms to the machine.

I get this response when I try to connect manually:

ssh -i ./bosh.pem vcap(a)10.0.0.6

and the response

root(a)gw:/data/CloudFoundry/my-bosh# ssh -i ./bosh.pem vcap(a)10.0.0.6
Ubuntu 14.04.3 LTS \n \l

Permission denied (publickey).


Re: bosh micro deploy stuck at Started deploy micro bosh > Waiting for the agent

Riaan Labuschagne <zapmanandroid@...>
 

Hi,

I have the exact same issue but have not heard back from anyone. Glad to see Im not the only one stuck on this issue.


bosh depoy - Issues with ssh

Riaan Labuschagne <zapmanandroid@...>
 

Hi,

I am trying to deploy to AWS and everything goes fine until the " Waiting
for the agent on VM.." step has to happen.

I have tried to login to the VM with my pvt key (ssh -i bosh.pem
vcap(a)10.0.0.6) but that also fails.

I mounted the volume of the bosh VM on another VM to check the
/home/vcap/.ssh/authorized_key file and it seems the public key in the
authorized_keys file differs from the pvt key I extract from bosh.pem.

I just cant seem to get past the "Waiting for the agent on VM.." step.

Is the public vcap file sipposed to be the public key form the bosh.pem
file? (I cant see where else it comes from)

Regards.

============================ My deploy output==================


Started deploying
Waiting for the agent on VM 'i-c5aa9563'... Failed (00:00:30)
Deleting VM 'i-c5aa9563'... Finished (00:00:36)
Creating VM for instance 'bosh/0' from stemcell 'ami-89c1f7fe light'...
Finished (00:00:43)
Waiting for the agent on VM 'i-24a79882' to be ready... Failed (00:02:33)

Waiting for the agent on VM 'i-24a79882' to be ready... Failed (00:02:33)
Failed deploying (00:04:29)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Command 'deploy' failed:
Deploying:
Creating instance 'bosh/0':
Waiting until instance is ready:
Starting SSH tunnel:
Failed to connect to remote server:
ssh: handshake failed: ssh: unable to authenticate, attempted
methods [none publickey], no supported methods remain