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.

Sign up for GitHub

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

Jump to bottom

BOSH-specific docs should be more visible. #2

Closed
PharkMillups opened this issue Apr 11, 2012 · 0 comments
Closed

BOSH-specific docs should be more visible. #2

PharkMillups opened this issue Apr 11, 2012 · 0 comments

Comments

@PharkMillups
Copy link

This tool looks great, but I had trouble finding the BOSH-specific docs [1] . You should put a pointer to these and at least some sort of mention of what BOSH actually is at the top of the README. It might also be a good idea to inclue a copy of the docs in the BOSH repo so that I can clone this and use it on a train with no wifi.

[1] https://github.com/cloudfoundry/oss-docs/blob/master/bosh/documentation/documentation.md
@skaar skaar closed this as completed Apr 28, 2012
olegshaldybin added a commit that referenced this issue Jun 22, 2012
@olegshaldybin
Fixed release upload regression
f533d7c 
Recent package matching optimization required an updated director to
work properly. We tried to make it backward compatible by doing full
matching when talking to the older director but it wasn't enough: the
list of packages fetched from director has no information of which
version a package belongs to, so CLI could delete more packages than
needed trying to repack the tarball. Fixed by making change work exactly
as it was working before: if no package matching can be performed,
exhaustive name/version comparison is performed instead of just sha1
comparison.

This should make it work with both old and new director as advertised.

Test plan:

- uploaded release to older director;
- uploaded release to new director;
- changed release name and retried #1 and #2.

Change-Id: I457c6c399db6b2cea12e4b4ef9c0d93c65c82013
cf-bosh pushed a commit that referenced this issue Apr 23, 2013
WIP #2
ce81b36
pmenglund added a commit to pmenglund/bosh that referenced this issue Apr 24, 2013
@pmenglund
[director] wip: snapshots cloudfoundry#2
9658a69
pmenglund added a commit that referenced this issue May 1, 2013
@pmenglund
[director] wip: snapshots #2
d0b34f6
lukebakken referenced this issue in Tier3/bosh Dec 10, 2013
@lukebakken
Fixes #2. Ensure that bosh_agent does NOT start automatically. It wil…
48cd63f 
…l be up to the platform to enable it at the end of the BP deployment.
lukebakken referenced this issue in Tier3/bosh Dec 10, 2013
@lukebakken @SaintGimp
Fixes #2. Ensure that bosh_agent does NOT start automatically. It wil…
6ef03f7 
…l be up to the platform to enable it at the end of the BP deployment.
@cppforlife cppforlife mentioned this issue Feb 17, 2014
Closed
@adamstegman adamstegman mentioned this issue May 9, 2014
Closed
tylerschultz added a commit that referenced this issue Sep 11, 2015
@tylerschultz
Fix docker image reference, #2.1.6 => #ruby-2.1.6
d275950 
Signed-off-by: Victor Fong <victor.fong@emc.com>
@dpb587 dpb587 mentioned this issue May 16, 2016
Closed
jmcarp pushed a commit to jmcarp/bosh that referenced this issue Jul 6, 2016
@sharms
Merge pull request cloudfoundry#2 from sharms/add-riemann
6931baf 
Tag service
@cppforlife cppforlife mentioned this issue Feb 21, 2017
Closed
dpb587-pivotal pushed a commit that referenced this issue Aug 7, 2017
@mkjelland
Merge pull request #2 from Everlag/pr2
b406d8b 
Introduce GcscliBlobstoreClient Read-Only functional tests
geofffranks pushed a commit to geofffranks/bosh that referenced this issue Jun 22, 2018
@voelzmo
Adapt openstack cpi opsfile
6116c4b 
* Make keystone v3 default (fixes cloudfoundry#2)
* Enable 'human_readable_vm_names' by default
@ishustava ishustava mentioned this issue Nov 7, 2018
Closed
@rluan rluan mentioned this issue Jul 12, 2021
Closed
@klakin-pivotal klakin-pivotal mentioned this issue Dec 2, 2021
Closed
@phong2tran phong2tran mentioned this issue Feb 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@skaar @PharkMillups