-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving notes on Origins of Blobs section #42
Comments
I’m sorry if I was confusing - I mean the original blob prior to it being added into a bosh release’s blobstore
…________________________________
From: Chiranga Alwis <[email protected]>
Sent: Sunday, February 4, 2018 3:55:50 AM
To: starkandwayne/ultimate-guide-to-bosh
Cc: Subscribed
Subject: [starkandwayne/ultimate-guide-to-bosh] Improving notes on Origins of Blobs section (#42)
The current notes<https://ultimateguidetobosh.com/releases/#origins-of-blobs> (article) on Origins of Blobs state that the information on how to determine the source location(s) of the blobs used in a release is not possible through the available meta data in a BOSH release.
IMO, this is not always true. The later section<https://ultimateguidetobosh.com/releases/#discovering-the-source-of-a-bosh-release> on Discovering the Source of a BOSH Release defines we can determine the source of the BOSH release.
We can obtain much clearer information of the exact source of the blobs (meaning the blobstore) by checking the config/final.yml file (please see BOSH documentation<https://bosh.io/docs/release-blobstore.html> on this topic for detailed information) available in the source repository of the BOSH release. It is true that we cannot obtain the exact information as the config/private.yml is checked into the Git repository. Please see the sample zookeeper release<https://github.com/cppforlife/zookeeper-release/blob/master/config/final.yml> for a better understanding.
Please correct me if I am wrong (as I am new to this area of knowledge) but AFAIU, we can greatly improve these notes by directing to appropriate guidelines (from BOSH documentation).
Your suggestions and concerns are highly appreciated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#42>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAAAbAJoQ4029i9R3VxavHuFcfp946c3ks5tRXCWgaJpZM4R4fzu>.
|
@drnic got it. But still I think the above information could be included in the particular article in order to be much clearer. It turned out that information about blobstores was not easy to find. |
Sorry I haven’t replied. I haven’t gotten back to the issues on this repo for a bit. I’ll reopen the issue so I give it some proper attention in future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current notes (article) on Origins of Blobs state that the information on how to determine the source location(s) of the blobs used in a release is not possible through the available meta data in a BOSH release.
IMO, this is not always true. The later section on Discovering the Source of a BOSH Release defines that we can determine the source of the BOSH release.
We can obtain much clearer information of the exact source of the blobs (meaning the blobstore) by checking the
config/final.yml
file (please see BOSH documentation on this topic for detailed information) available in the source repository of the BOSH release. It is true that we cannot obtain the exact information as theconfig/private.yml
is checked into the Git repository. Please see the sample zookeeper release for a better understanding.Please correct me if I am wrong (as I am new to this area of knowledge) but AFAIU, we can greatly improve these notes by directing to appropriate guidelines (from BOSH documentation).
Your suggestions and concerns are highly appreciated.
The text was updated successfully, but these errors were encountered: