The operations/use-compiled-releases.yml file in cf-deployment references stemcell version 1.423 for all compiled releases, even though newer stemcells are available. This is due to how the CI pipeline is configured to only recompile all releases on major stemcell version bumps.
Both PRs address NVMe device discovery challenges but for different cloud providers with fundamentally different approaches.
| Aspect | PR #396 (AWS) | PR #402 (Azure) |
|---|---|---|
| URL | cloudfoundry/bosh-agent#396 | cloudfoundry/bosh-agent#402 |
| Cloud Provider | AWS | Azure |
- Name: Domain-Scoped mTLS for GoRouter
- Start Date: 2026-02-16
- Author(s): @rkoster, @beyhan, @maxmoehl
- Status: Draft
- RFC Pull Request: community#1438
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| use nix |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| https://packages.ubuntu.com/xenial/linux-aws-source-4.4.0 ixgbevf 2.12.1-k | |
| ❯ diff ubuntu/linux-4.4/drivers/net/ethernet/intel/ixgbevf upstream/ixgbevf-2.12.1/src | wc -l | |
| 3424 | |
| ❯ diff ubuntu/linux-4.4/drivers/net/ethernet/intel/ixgbevf upstream/ixgbevf-4.1.2/src | wc -l | |
| 3897 | |
| ❯ diff ubuntu/linux-4.4/drivers/net/ethernet/intel/ixgbevf upstream/ixgbevf-4.6.3/src | wc -l | |
| 5348 | |
| ❯ diff ubuntu/linux-4.4/drivers/net/ethernet/intel/ixgbevf upstream/ixgbevf-4.8.1/src | wc -l | |
| 5475 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Verifying my Blockstack ID is secured with the address 1NVzvRRTvvoQ6UgngVVarthwGkpqLNy3uM https://explorer.blockstack.org/address/1NVzvRRTvvoQ6UgngVVarthwGkpqLNy3uM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Verifying my Blockstack ID is secured with the address 1NVzvRRTvvoQ6UgngVVarthwGkpqLNy3uM https://explorer.blockstack.org/address/1NVzvRRTvvoQ6UgngVVarthwGkpqLNy3uM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "receiver": "default-receiver", | |
| "status": "resolved", | |
| "alerts": [ | |
| { | |
| "status": "resolved", | |
| "labels": { | |
| "alertname": "BOSHJobProcessUnhealthy", | |
| "bosh_deployment": "cf", | |
| "bosh_job_index": "0", |
Usage:
fly -t ${target} set-pipeline -n -p docker-broker \
-c <(bosh int docker-broker-pipeline.yml --vars-file vars.yml)
I hereby claim:
- I am rkoster on github.
- I am rkoster (https://keybase.io/rkoster) on keybase.
- I have a public key whose fingerprint is 5865 815F 7085 2981 6343 DCC1 F6A8 BA05 268F 177D
To claim this, I am signing this object:
NewerOlder