Skip to content
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

Open
chirangaalwis opened this issue Feb 4, 2018 · 3 comments
Open

Improving notes on Origins of Blobs section #42

chirangaalwis opened this issue Feb 4, 2018 · 3 comments

Comments

@chirangaalwis
Copy link

chirangaalwis commented Feb 4, 2018

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 the config/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.

@drnic
Copy link
Contributor

drnic commented Feb 5, 2018 via email

@chirangaalwis
Copy link
Author

@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.

@drnic
Copy link
Contributor

drnic commented Feb 14, 2018

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.

@drnic drnic reopened this Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants