Purpose of instance_states in manifest?


Jones, Daniel
 

Hi all,

Two questions:

1. What is the intended use of `bosh download manifest`?

2. What is the purpose of instance_states in a manifest?

I ask as I did a `bosh download manifest` because I was too lazy to go and find where the actual deployment manifest was kicking around on a server. I knew there had been no changes, so was expecting it to return an identical manifest to that which was used to create the deployment originally.

It was only upon closer inspection I noticed some "instance_states" fields for particular jobs, where some of the values were "recreate". This figures, as I'd done at least one `bosh recreate` before the `bosh download manifest`.

Is the intention of `bosh download manifest` to express the internal desired state of a deployment in YAML form? Or is it intended to give one a means to access a manifest for a deployment if the original is lost?

What does the "instance_states" field do? It seems a bit odd to have a verb like "recreate" in a declarative configuration file. The source code says<https://github.com/cloudfoundry/bosh/blob/master/bosh-director/lib/bosh/director/deployment_plan/job.rb> that these are virtual states, and I'm not really sure what the purpose of them is.

Any and all information gratefully appreciated!


Regards,
Daniel Jones

Daniel Jones I 723 6362 I +44 (0)1732 776362 I Cell: +44 (0)79 8000 9153
Fidelity Worldwide Investment I 130 Tonbridge Road, Hildenborough, Kent, TN11 9DZ

The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Fidelity only gives information on products and services and does not give investment advice to retail clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142) and Financial Administration Services Limited (Reg. No. 1629709) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg. No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ.


Dmitriy Kalinin
 

`bosh download manifest` is meant to return what was send to the Director
at the time of the deploy. Certain values will be resolved such as release
and stemcell versions.

There was a bug that accidentally exposed instance_states key which is
internal to the Director. It was fixed in latest version of the Director.

On Wed, Aug 5, 2015 at 3:43 AM, Jones, Daniel <Daniel.Jones3(a)fil.com> wrote:

Hi all,



Two questions:

1. What is the intended use of `bosh download manifest`?

2. What is the purpose of instance_states in a manifest?



I ask as I did a `bosh download manifest` because I was too lazy to go and
find where the actual deployment manifest was kicking around on a server. I
knew there had been no changes, so was expecting it to return an identical
manifest to that which was used to create the deployment originally.



It was only upon closer inspection I noticed some “instance_states” fields
for particular jobs, where some of the values were “recreate”. This
figures, as I’d done at least one `bosh recreate` before the `bosh download
manifest`.



Is the intention of `bosh download manifest` to express the internal
desired state of a deployment in YAML form? Or is it intended to give one a
means to access a manifest for a deployment if the original is lost?



What does the “instance_states” field do? It seems a bit odd to have a
verb like “recreate” in a declarative configuration file. The source code
says
<https://github.com/cloudfoundry/bosh/blob/master/bosh-director/lib/bosh/director/deployment_plan/job.rb>
that these are virtual states, and I’m not really sure what the purpose of
them is.



Any and all information gratefully appreciated!





Regards,

Daniel Jones



*Daniel Jones* I 723 6362 I +44 (0)1732 776362 I *Cell*: +44 (0)79 8000
9153

*Fidelity Worldwide Investment* I 130 Tonbridge Road, Hildenborough,
Kent, TN11 9DZ



The information transmitted is intended for the person or entity to which
it is addressed and may contain confidential, privileged or copyrighted
material. If you receive this in error, please contact the sender and
delete the material from any computer. Fidelity only gives information on
products and services and does not give investment advice to retail clients
based on individual circumstances. Any comments or statements made are not
necessarily those of Fidelity. All e-mails may be monitored. FIL
Investments International (Reg. No.1448245), FIL Investment Services (UK)
Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142) and
Financial Administration Services Limited (Reg. No. 1629709) are authorised
and regulated in the UK by the Financial Conduct Authority. FIL Life
Insurance Limited (Reg. No. 3406905) is authorised in the UK by the
Prudential Regulation Authority and regulated in the UK by the Financial
Conduct Authority and the Prudential Regulation Authority. Registered
offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge,
Kent TN11 9DZ.





Ning Fu
 

Be careful to use the downloaded manifest. As the release and stemcell
version numbers will be resolved to a specific number, instead of "latest".
You may end up using an old version.

On Wed, Aug 5, 2015 at 6:43 PM, Jones, Daniel <Daniel.Jones3(a)fil.com> wrote:

Hi all,



Two questions:

1. What is the intended use of `bosh download manifest`?

2. What is the purpose of instance_states in a manifest?



I ask as I did a `bosh download manifest` because I was too lazy to go and
find where the actual deployment manifest was kicking around on a server. I
knew there had been no changes, so was expecting it to return an identical
manifest to that which was used to create the deployment originally.



It was only upon closer inspection I noticed some “instance_states” fields
for particular jobs, where some of the values were “recreate”. This
figures, as I’d done at least one `bosh recreate` before the `bosh download
manifest`.



Is the intention of `bosh download manifest` to express the internal
desired state of a deployment in YAML form? Or is it intended to give one a
means to access a manifest for a deployment if the original is lost?



What does the “instance_states” field do? It seems a bit odd to have a
verb like “recreate” in a declarative configuration file. The source code
says
<https://github.com/cloudfoundry/bosh/blob/master/bosh-director/lib/bosh/director/deployment_plan/job.rb>
that these are virtual states, and I’m not really sure what the purpose of
them is.



Any and all information gratefully appreciated!





Regards,

Daniel Jones



*Daniel Jones* I 723 6362 I +44 (0)1732 776362 I *Cell*: +44 (0)79 8000
9153

*Fidelity Worldwide Investment* I 130 Tonbridge Road, Hildenborough,
Kent, TN11 9DZ



The information transmitted is intended for the person or entity to which
it is addressed and may contain confidential, privileged or copyrighted
material. If you receive this in error, please contact the sender and
delete the material from any computer. Fidelity only gives information on
products and services and does not give investment advice to retail clients
based on individual circumstances. Any comments or statements made are not
necessarily those of Fidelity. All e-mails may be monitored. FIL
Investments International (Reg. No.1448245), FIL Investment Services (UK)
Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142) and
Financial Administration Services Limited (Reg. No. 1629709) are authorised
and regulated in the UK by the Financial Conduct Authority. FIL Life
Insurance Limited (Reg. No. 3406905) is authorised in the UK by the
Prudential Regulation Authority and regulated in the UK by the Financial
Conduct Authority and the Prudential Regulation Authority. Registered
offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge,
Kent TN11 9DZ.