bosh-gen v0.22 - thanks to James, Quinn & Long


Dr Nic Williams
 

The latest and greatest way to create new releases for BOSH is now even
greater.

https://github.com/cloudfoundry-community/bosh-gen/releases/tag/v0.22.0

Thanks to James Hunt, Quintessence Anx, and Long Nguyen for this version!

- Fixed stemcell URLs from `bosh public stemcells` to https://bosh.io
- Randomize Warden Network definitions so they don't always clash
- Unify stdout/stderr log files everywhere
- Fixed issue where dir cpi was found as `warden_cpi' not`warden'

gem install bosh-gen
bosh-gen new my-new-thing

Thanks for playing!
Nic

--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic


Marco Voelz
 

Thanks, that looks like some really nice changes included there!

One thing I'm not so sure about is how stdout and stderr are redirected to the same file now. Shouldn't we try to harmonize this somehow with the way cf-release is doing it [1]? My guess is that most people using boshreleases are also deploying and maintaining CF at some point in time, so having different conventions doesn't seem like a good idea. I'm not saying one way or the other is better, I just don't like thinking about which "kind" of boshrelease this is before figuring out where to find my error logs.

What do you think?

Warm regards
Marco

[1] https://github.com/cloudfoundry/cf-release/blob/master/src/common/utils.sh#L4-L5

On 21/11/15 01:36, "Dr Nic Williams" <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:

The latest and greatest way to create new releases for BOSH is now even greater.

https://github.com/cloudfoundry-community/bosh-gen/releases/tag/v0.22.0

Thanks to James Hunt, Quintessence Anx, and Long Nguyen for this version!

- Fixed stemcell URLs from `bosh public stemcells` to https://bosh.io
- Randomize Warden Network definitions so they don't always clash
- Unify stdout/stderr log files everywhere
- Fixed issue where dir cpi was found as `warden_cpi' not`warden'

gem install bosh-gen
bosh-gen new my-new-thing

Thanks for playing!
Nic

--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com<http://drnicwilliams.com/>
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic


Dr Nic Williams
 

Aside from "cf-release is doing it" what are the pros/cons for maintaining two log files vs a single file?

On Sun, Nov 22, 2015 at 10:27 PM, Voelz, Marco <marco.voelz(a)sap.com>
wrote:

Thanks, that looks like some really nice changes included there!
One thing I'm not so sure about is how stdout and stderr are redirected to the same file now. Shouldn't we try to harmonize this somehow with the way cf-release is doing it [1]? My guess is that most people using boshreleases are also deploying and maintaining CF at some point in time, so having different conventions doesn't seem like a good idea. I'm not saying one way or the other is better, I just don't like thinking about which "kind" of boshrelease this is before figuring out where to find my error logs.
What do you think?
Warm regards
Marco
[1] https://github.com/cloudfoundry/cf-release/blob/master/src/common/utils.sh#L4-L5
On 21/11/15 01:36, "Dr Nic Williams" <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:
The latest and greatest way to create new releases for BOSH is now even greater.
https://github.com/cloudfoundry-community/bosh-gen/releases/tag/v0.22.0
Thanks to James Hunt, Quintessence Anx, and Long Nguyen for this version!
- Fixed stemcell URLs from `bosh public stemcells` to https://bosh.io
- Randomize Warden Network definitions so they don't always clash
- Unify stdout/stderr log files everywhere
- Fixed issue where dir cpi was found as `warden_cpi' not`warden'
gem install bosh-gen
bosh-gen new my-new-thing
Thanks for playing!
Nic
--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com<http://drnicwilliams.com/>
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic


Gwenn Etourneau
 

Thanks @ Dr Nic one of the tools I am using a lot :)

On Tue, Nov 24, 2015 at 12:18 AM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Aside from "cf-release is doing it" what are the pros/cons for maintaining
two log files vs a single file?




On Sun, Nov 22, 2015 at 10:27 PM, Voelz, Marco <marco.voelz(a)sap.com>
wrote:

Thanks, that looks like some really nice changes included there!

One thing I'm not so sure about is how stdout and stderr are redirected
to the same file now. Shouldn't we try to harmonize this somehow with the
way cf-release is doing it [1]? My guess is that most people using
boshreleases are also deploying and maintaining CF at some point in time,
so having different conventions doesn't seem like a good idea. I'm not
saying one way or the other is better, I just don't like thinking about
which "kind" of boshrelease this is before figuring out where to find my
error logs.

What do you think?

Warm regards
Marco

[1]
https://github.com/cloudfoundry/cf-release/blob/master/src/common/utils.sh#L4-L5

On 21/11/15 01:36, "Dr Nic Williams" <drnicwilliams(a)gmail.com> wrote:

The latest and greatest way to create new releases for BOSH is now even
greater.

https://github.com/cloudfoundry-community/bosh-gen/releases/tag/v0.22.0

Thanks to James Hunt, Quintessence Anx, and Long Nguyen for this version!

- Fixed stemcell URLs from `bosh public stemcells` to https://bosh.io
- Randomize Warden Network definitions so they don't always clash
- Unify stdout/stderr log files everywhere
- Fixed issue where dir cpi was found as `warden_cpi' not`warden'

gem install bosh-gen
bosh-gen new my-new-thing

Thanks for playing!
Nic

--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic




Marco Voelz
 

As I said: It is not so much about which way is better, it is more about having less things to think about. With the right arguments you might be able to convince the MEGA team to accept a PR to log it all into a single file. Until then, I'd argue for trying to follow closely these conventions with all other boshreleases.

Warm regards
Marco

On 23/11/15 16:18, "Dr Nic Williams" <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:

Aside from "cf-release is doing it" what are the pros/cons for maintaining two log files vs a single file?





On Sun, Nov 22, 2015 at 10:27 PM, Voelz, Marco <marco.voelz(a)sap.com<mailto:marco.voelz(a)sap.com>> wrote:

Thanks, that looks like some really nice changes included there!

One thing I'm not so sure about is how stdout and stderr are redirected to the same file now. Shouldn't we try to harmonize this somehow with the way cf-release is doing it [1]? My guess is that most people using boshreleases are also deploying and maintaining CF at some point in time, so having different conventions doesn't seem like a good idea. I'm not saying one way or the other is better, I just don't like thinking about which "kind" of boshrelease this is before figuring out where to find my error logs.

What do you think?

Warm regards
Marco

[1] https://github.com/cloudfoundry/cf-release/blob/master/src/common/utils.sh#L4-L5

On 21/11/15 01:36, "Dr Nic Williams" <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:

The latest and greatest way to create new releases for BOSH is now even greater.

https://github.com/cloudfoundry-community/bosh-gen/releases/tag/v0.22.0

Thanks to James Hunt, Quintessence Anx, and Long Nguyen for this version!

- Fixed stemcell URLs from `bosh public stemcells` to https://bosh.io
- Randomize Warden Network definitions so they don't always clash
- Unify stdout/stderr log files everywhere
- Fixed issue where dir cpi was found as `warden_cpi' not`warden'

gem install bosh-gen
bosh-gen new my-new-thing

Thanks for playing!
Nic

--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com<http://drnicwilliams.com/>
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic