congrats cli team! i've been looking forward to the private docker repository support. the plugins management and other features are also a nice improvement. i've already got it installed. thanks for

congrats on the new release dies and team. tab completion is a nice touch.

congrats to everyone that contributed to diego along the way! i'm personally very impressed with how scalable it is and how many users it has running in production.

congrats container networking team on this important milestone! thanks to everyone that contributed with code and feedback thus far. wrote:

danny, thank you for your stewardship of buildpacks. they've been a reliable part of cloud foundry these last few months and i appreciate your contributions. stephen, congrats on your new role, i'm su

you can tell when you're on DEAs by comparing the notes that dan referred to here [1]. for example, if you have the env variable VCAP_APP_PORT then you're likely on a DEA container. [1] https://github

impressive list of new stuff ben and team!

nic, if you look at this section of the doc [1] it discusses "Reattachable Volumes" which are similar to EBS volumes attaching to EC2 instances without allowing multiple instances to be bound to the s

cool. thanks for sharing this john! wrote:

congrats mysql team! the arbitrator is a nice touch to save resources yet still result in high availability even when losing an entire AZ.

when running an app in CF based on a docker image, the service discovery mechanism is expected to be either through bound services which are expressed as environment variables, or using DNS to reach a

congrats CLI team! i know many customers waiting for these features.

nic, some clients require a particular port number to work, so just allocating any of the available ones won't be enough if a client needs to specify a particular port and wants to express that. in th

looks like staging failed with an unknown error after the app was successfully uploaded. how did you deploy your cf? are there buildpacks listed in "cf buildpacks"? perhaps you could look at the logs

it works the same for docker apps as it does for buildpack apps. when you push a docker image: cf push docker-app -o cloudfoundry/diego-docker-app -m 256m this runs a single instance of the diego-dock

that looks pretty good. i'd probably change the following: 8) Stop jobs on old database cluster 9) Validate CF is working and connected to new database 10) Validate old database files are not changed

dieu, i thought i remember dmitriy indicating there are some packages he wants to remove from the stemcell for NFS. would the "bring your own NFS server" approach still allow the stemcell changes dmit

depending on how urgent this is or whether you'd want to allow database access, i've also see people write scripts that use the CF REST API to go through all orgs, then all spaces, then all apps, and

emccode rexray seems to be a relevant project that works with docker and mesos: http://rexray.readthedocs.org/en/stable/ here's the blog post where i found out about it showing how it works with vagra

i'm happy to see the new debug, profiling and jmx functionality and all of the community contributions. also happy to see spring boot 1.3 support picked up so quickly. the link to the release in your