Date
1 - 6 of 6
BOSH Manifest and directory_uuid
|
Alberto A. Flores
Team,
After reviewing the bosh.io site and other email list, I can't find a good reason on why does the manifest YAML file needs to have the director_uuid in the manifest. According to the docs found here: http://bosh.io/docs/deployment-manifest.html#deployment It is a "required" field. Is this so? Keeping manifests in version control will create a dependency on a single Director running. Is this by design? Just looking for clarification more than a rant... :) -- View this message in context: http://cf-bosh.70367.x6.nabble.com/BOSH-Manifest-and-directory-uuid-tp45.html Sent from the CF BOSH mailing list archive at Nabble.com. |
|
|
|
Dmitriy Kalinin
It's a safety feature so that people do not accidentally deploy deployment
toggle quoted message
Show quoted text
with a same name to a wrong environment. For example if you have staging and prod environments and both have cf deployment. On Wed, May 20, 2015 at 10:30 AM, albertoaflores <aaflores(a)gmail.com> wrote:
Team, |
|
|
|
Alberto A. Flores
Thanks Dmitriy, so if I “version control” a manifest, I’d have to keep a different version for “prod” and another one for “staging”? Is there a way to override it in the command line?
toggle quoted message
Show quoted text
-- Alberto Flores Twitter: @albertoaflores From: Dmitriy Kalinin <dkalinin(a)pivotal.io> Reply: Dmitriy Kalinin <dkalinin(a)pivotal.io>> Date: May 20, 2015 at 3:05:41 PM To: albertoaflores <aaflores(a)gmail.com>> Cc: CF BOSH Mailing List <cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] BOSH Manifest and directory_uuid It's a safety feature so that people do not accidentally deploy deployment with a same name to a wrong environment. For example if you have staging and prod environments and both have cf deployment. On Wed, May 20, 2015 at 10:30 AM, albertoaflores <aaflores(a)gmail.com> wrote:
Team, After reviewing the bosh.io site and other email list, I can't find a good reason on why does the manifest YAML file needs to have the director_uuid in the manifest. According to the docs found here: http://bosh.io/docs/deployment-manifest.html#deployment It is a "required" field. Is this so? Keeping manifests in version control will create a dependency on a single Director running. Is this by design? Just looking for clarification more than a rant... :) -- View this message in context: http://cf-bosh.70367.x6.nabble.com/BOSH-Manifest-and-directory-uuid-tp45.html Sent from the CF BOSH mailing list archive at Nabble.com. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Dr Nic Williams
Try this idea https://github.com/concourse/concourse/blob/master/manifests/bosh-lite.yml#L4
On Wed, May 20, 2015 at 2:25 PM, Alberto Flores <aaflores(a)gmail.com> wrote: Thanks Dmitriy, so if I “version control” a manifest, I’d have to keep a different version for “prod” and another one for “staging”? Is there a way to override it in the command line? |
|
|
|
Alberto A. Flores
Awesome idea, Dr. Nic..! That works!
toggle quoted message
Show quoted text
I appreciate the feedback! -- Alberto Flores Twitter: @albertoaflores From: Dr Nic Williams <drnicwilliams(a)gmail.com> Reply: Dr Nic Williams <drnicwilliams(a)gmail.com>> Date: May 20, 2015 at 5:28:52 PM To: Alberto Flores <aaflores(a)gmail.com>> Cc: Dmitriy Kalinin <dkalinin(a)pivotal.io>>, CF BOSH Mailing List <cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] BOSH Manifest and directory_uuid Try this idea https://github.com/concourse/concourse/blob/master/manifests/bosh-lite.yml#L4 On Wed, May 20, 2015 at 2:25 PM, Alberto Flores <aaflores(a)gmail.com> wrote:
Thanks Dmitriy, so if I “version control” a manifest, I’d have to keep a different version for “prod” and another one for “staging”? Is there a way to override it in the command line? -- Alberto Flores Twitter: @albertoaflores From: Dmitriy Kalinin <dkalinin(a)pivotal.io> Reply: Dmitriy Kalinin <dkalinin(a)pivotal.io>> Date: May 20, 2015 at 3:05:41 PM To: albertoaflores <aaflores(a)gmail.com>> Cc: CF BOSH Mailing List <cf-bosh(a)lists.cloudfoundry.org>> Subject: Re: [cf-bosh] BOSH Manifest and directory_uuid It's a safety feature so that people do not accidentally deploy deployment with a same name to a wrong environment. For example if you have staging and prod environments and both have cf deployment. On Wed, May 20, 2015 at 10:30 AM, albertoaflores <aaflores(a)gmail.com> wrote: Team, After reviewing the bosh.io site and other email list, I can't find a good reason on why does the manifest YAML file needs to have the director_uuid in the manifest. According to the docs found here: http://bosh.io/docs/deployment-manifest.html#deployment It is a "required" field. Is this so? Keeping manifests in version control will create a dependency on a single Director running. Is this by design? Just looking for clarification more than a rant... :) -- View this message in context: http://cf-bosh.70367.x6.nabble.com/BOSH-Manifest-and-directory-uuid-tp45.html Sent from the CF BOSH mailing list archive at Nabble.com. _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Tammer Saleh
We've had this problem as well, and discussed a couple of features in bosh
toggle quoted message
Show quoted text
that could help: 1. Allow the user to tell the director what its name is, and use that in the UUID field. and/or... 2. Allow the operator to mark a deployment as "protected," and only require the UUID field in the deploy manifest when targeting such a deployment. Cheers, Tammer Saleh Director of Product, Pivotal CF, London http://pivotal.io | http://tammersaleh.com | +44 7463 939332 On Wed, May 20, 2015 at 10:31 PM, Alberto Flores <aaflores(a)gmail.com> wrote:
Awesome idea, Dr. Nic..! That works! |
|
|