Nice idea this would also would be a required step in order to get rid of
the inception vm (uploading big releases faster over internal network).
On Thursday, April 11, 2013 7:50:21 AM UTC+2, Dr Nic Williams wrote:


In chatting with Elizabeth the other day, the question arose: "which of
the files in cf-release are actually required to upload a final release?"

Now to upload a dev release you first need to create the dev release. So
you need the whole cf-release repo, with all its submodules (run:
./update), and then you run "bosh create release".

But cf-release comes ready for you to upload a final release. Just clone
it and run "bosh upload release releases/appcloud-131.yml".

So which are the files that are important? And instead of having to clone
any repos, could a Bosh director just go and fetch the minimum set of files
itself and then self-upload the release? Or could we ship "light releases"
- small tarballs that contain the very minimum number of files to upload a
single release (say appcloud-131).

I put the answer in a small repo

If you have a bosh running, try this:

git clone https://github.com/StarkAndWayne/cf-release-only.git
cd cf-release-only
bosh upload release releases/appcloud-131.yml

In summary, its only 2 folders of yaml files and the appcloud-131.yml file

I like Martin's idea that I've put at the bottom. Something like:

bosh add remote release https://github.com/cloudfoundry/cf-release
bosh add remote release https://github.com/cloudfoundry/cf-release --name

If you're interested in adding awesome new features to bosh, perhaps you'd
like to build this one!


Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
cell +1 (415) 860-2185
twitter @drnic


Have an innovative day

*Innovation Factory *De Lairessestraat 180* *1075 HM Amsterdam* *+31
20 7787008 www.innovationfactory.eu

*The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer. Innovation Factory does not accept
liability for any errors, viruses or omissions in the contents of this
message, which may arise as a result of e-mail transmission. No employee or
agent is authorized to conclude any binding agreement on behalf of
Innovation Factory with another party by email.*

Search Discussions

Discussion Posts


Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 2 | next ›
Discussion Overview
groupbosh-dev @
postedApr 11, '13 at 5:50a
activeApr 16, '13 at 8:48p

2 users in discussion

Ruben Koster: 1 post Dr Nic Williams: 1 post



site design / logo © 2021 Grokbase