Date   
Re: Recreating a bosh vm without losing the data and starting to a new aws vm

Geoff Franks <geoff@...>
 

Take a look at 'bosh recreate <job> <index>' or 'bosh deploy --recreate'. They should do the trick. Just make sure the data you care about is on persistent storage first ;)

Sent from my iPhone

On Dec 9, 2015, at 7:58 AM, Oded Gold <oded(a)nurego.com> wrote:

Hi all

I got an email from AWS saying that one of the instances I am using is depreciated and going to be terminate, When I tired to do a redeploy it does not change the aws instance.
How can I run a deployment that also creates a new aws VM so that when AWS shuts it down I will not lose everything.

The name of the bosh vm is backend/0

I am still very knew to bosh

Thank you

Recreating a bosh vm without losing the data and starting to a new aws vm

Oded Gold
 

Hi all

I got an email from AWS saying that one of the instances I am using is depreciated and going to be terminate, When I tired to do a redeploy it does not change the aws instance.
How can I run a deployment that also creates a new aws VM so that when AWS shuts it down I will not lose everything.

The name of the bosh vm is backend/0

I am still very knew to bosh

Thank you

Re: cf commands failing after bosh deploy

Rahul Gupta
 

This is the exact command and error code when running cf v6:

../cf api --skip-ssl-validation api.52.70.161.122.xip.io
Setting api endpoint to api.52.70.161.122.xip.io...
FAILED
Server error, status code: 503, error code: 0, message:

Re: cf commands failing after bosh deploy

Rahul Gupta
 

All below mentioned cf commands on version 6:

cf api api.1.2.3.4.xip.io
cf api api.myCloudFoundryDomain.com

cf api http://api.1.2.3.4.xip.io
cf api http://api.myCloudFoundryDomain.com

resulted in 503 Service Unavailable.

Re: cf commands failing after bosh deploy

Amit Kumar Gupta
 

Can you say what you mean by "results were same"? For cf version 6+, "cf
target http://..." is not even a valid usage of the target command.

On Tue, Dec 8, 2015 at 7:11 PM, Rahul Gupta <wildnez(a)gmail.com> wrote:

bosh version: BOSH 1.3143.0

cf version: cf 5.4.7

I also tried with cf version 6.14.0+2654a47-2015-11-18 but results were
same.

cf release:
| Name | Versions | Commit Hash |
+------+----------+-------------+
| cf | 224* | 65621dd0+ |

Re: cf commands failing after bosh deploy

Rahul Gupta
 

bosh version: BOSH 1.3143.0

cf version: cf 5.4.7

I also tried with cf version 6.14.0+2654a47-2015-11-18 but results were same.

cf release:
| Name | Versions | Commit Hash |
+------+----------+-------------+
| cf | 224* | 65621dd0+ |

Re: Bosh registry - aws vs vsphere

Dmitriy Kalinin
 

AWS/Openstack uses registry because user-data cannot be modified while the
VM is running. We have future plans to remove registry and change cpi api
so that registry will not be needed (
https://github.com/cloudfoundry/bosh-notes/blob/master/cpi-api-v2.md). We
use dhcp on AWS.

vSphere uses CDROM drive to update data, which can be updated while the the
VM is running. We dont use dhcp on vsphere so IP information is included in
the CDROM drive.

On Tue, Dec 8, 2015 at 11:51 AM, William C Penrod <wcpenrod(a)gmail.com>
wrote:

... it's a bit quiet on this thread, but the general question has been
answered here:


https://lists.cloudfoundry.org/archives/list/cf-bosh(a)lists.cloudfoundry.org/thread/TBOYBOCX74YLUJODQLVWRJPWLQXLBIM2/

Re: Bosh registry - aws vs vsphere

William C Penrod
 

... it's a bit quiet on this thread, but the general question has been answered here:

https://lists.cloudfoundry.org/archives/list/cf-bosh(a)lists.cloudfoundry.org/thread/TBOYBOCX74YLUJODQLVWRJPWLQXLBIM2/

Re: cf commands failing after bosh deploy

CF Runtime
 

There are couple of odd things here. Firstly, the command `bosh show cf attributes` is a valid bosh command; when we run it we see the following:

$ bosh show cf attributes
Unknown command: show cf attributes

Secondly, it looks like your cf CLI is in ruby, based the output you posted in the original message:

$ cf target http://api.cloudXXXX-cfapp.com Setting target to http://api.cloudXXXX-cfapp.com... FAILED CFoundry::BadResponse: 503: 503 Service Unavailable No server is available to handle this request.

The cf CLI was rewritten in golang, and the ruby CLI deprecated some years ago.

Can you confirm what versions of bosh and cf CLI you are using locally, as well as the version of cf-release bosh release you are deploying?

Re: bosh-init + the registry job

William C Penrod
 

I have this same question.

Here is an example of our registry setup in our aws bosh-init deployed
director:

jobs:
templates:
- {name: registry, release: bosh}

properties:
registry:
address: <bound_network_address>
host: <bound_network_address>
db: <db_info>
http: {user: user, password: password, port: 25777}
username: user
password: password
port: 25777

Deployed with bosh 208, aws_cpi 36.

This diagram helped me understand the purpose of the registry:

https://bosh.io/docs/bosh-components.html


On Tue, Dec 8, 2015 at 12:14 PM, Geoff Franks <geoff(a)starkandwayne.com>
wrote:

Looking at the example manifests for bosh-init on AWS (
https://bosh.io/docs/init-aws.html) + vSphere (
https://bosh.io/docs/init-vsphere.html), we found that the registry job
is applied in AWS and not in vSphere. Is this intentional, and there's
something about the vSphere CPI that obviates the need for the registry? If
not, should it be in both examples, or is it no longer necessary for any
BOSH?

Re: bosh-init + the registry job

Geoff Franks <geoff@...>
 

Cool, thanks for the info!

On Dec 8, 2015, at 2:23 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:

It's intentional. vSphere CPI does not need registry and uses CDROM drive for bootstrapping. AWS CPI does use it to keep some state for bootstrapping.

On Tue, Dec 8, 2015 at 11:14 AM, Geoff Franks <geoff(a)starkandwayne.com <mailto:geoff(a)starkandwayne.com>> wrote:
Looking at the example manifests for bosh-init on AWS (https://bosh.io/docs/init-aws.html <https://bosh.io/docs/init-aws.html>) + vSphere (https://bosh.io/docs/init-vsphere.html <https://bosh.io/docs/init-vsphere.html>), we found that the registry job is applied in AWS and not in vSphere. Is this intentional, and there's something about the vSphere CPI that obviates the need for the registry? If not, should it be in both examples, or is it no longer necessary for any BOSH?

Re: bosh-init + the registry job

Dmitriy Kalinin
 

It's intentional. vSphere CPI does not need registry and uses CDROM drive
for bootstrapping. AWS CPI does use it to keep some state for bootstrapping.

On Tue, Dec 8, 2015 at 11:14 AM, Geoff Franks <geoff(a)starkandwayne.com>
wrote:

Looking at the example manifests for bosh-init on AWS (
https://bosh.io/docs/init-aws.html) + vSphere (
https://bosh.io/docs/init-vsphere.html), we found that the registry job
is applied in AWS and not in vSphere. Is this intentional, and there's
something about the vSphere CPI that obviates the need for the registry? If
not, should it be in both examples, or is it no longer necessary for any
BOSH?

bosh-init + the registry job

Geoff Franks <geoff@...>
 

Looking at the example manifests for bosh-init on AWS (https://bosh.io/docs/init-aws.html <https://bosh.io/docs/init-aws.html>) + vSphere (https://bosh.io/docs/init-vsphere.html <https://bosh.io/docs/init-vsphere.html>), we found that the registry job is applied in AWS and not in vSphere. Is this intentional, and there's something about the vSphere CPI that obviates the need for the registry? If not, should it be in both examples, or is it no longer necessary for any BOSH?

Re: When Bosh decide a job requires upgrade when doing bosh deploy? And what's the upgrade steps?

Dmitriy Kalinin
 

Dongfei: you can run `bosh task X --debug|grep changes` to see additional
information why bosh thought it needed to update machines.

On Mon, Dec 7, 2015 at 11:43 PM, Dongfei Wu <wudongfei(a)gmail.com> wrote:

Files in /var/vcap/store, and /var/vcap/data

Re: S3 api/method call

Dr Nic Williams
 

Look in the blobstore_client subfolder for how bosh talks to S3 and other blobstores.

On Mon, Dec 7, 2015 at 11:34 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

Hi Everyone.
There is any documentation about which method or API bosh blobstore is
calling for S3 ??
Every time we say S3 compatible but which exactly API / Method are we
calling ?
Thanks

Re: When Bosh decide a job requires upgrade when doing bosh deploy? And what's the upgrade steps?

Dongfei Wu
 

Files in /var/vcap/store, and /var/vcap/data

Re: When Bosh decide a job requires upgrade when doing bosh deploy? And what's the upgrade steps?

Dongfei Wu
 

Sorry, by "service tile", I mean a bosh release.

S3 api/method call

Gwenn Etourneau
 

Hi Everyone.


There is any documentation about which method or API bosh blobstore is
calling for S3 ??

Every time we say S3 compatible but which exactly API / Method are we
calling ?



Thanks

Re: When Bosh decide a job requires upgrade when doing bosh deploy? And what's the upgrade steps?

Gwenn Etourneau
 

"a few files are changed" which file ?

On Tue, Dec 8, 2015 at 4:02 PM, Dongfei Wu <wudongfei(a)gmail.com> wrote:

Thx Gwenn,
My problem is that, I have a service tile that running for a while(monit
stop/start is invoked, a few files are changed, but no files packages/jobs
are changed), do bosh deploy with same manifest triggers jobs to update. I
don't know why.

Re: When Bosh decide a job requires upgrade when doing bosh deploy? And what's the upgrade steps?

Dongfei Wu
 

Thx Gwenn,
My problem is that, I have a service tile that running for a while(monit stop/start is invoked, a few files are changed, but no files packages/jobs are changed), do bosh deploy with same manifest triggers jobs to update. I don't know why.