This change replaces the use of remote_file with cf_remote_file to
work around two limitations in Chef 0.10:
- Chef shares its downloading logic of remote_file with its REST
client. The REST client decompresses archives when it sees the
header "Content-Encoding: gzip", which is an undesirable behavior
for remote_file.
- Chef only uses the specified checksum to trigger update, but it does
no validation after new remote files are downloaded.
Our requirement of cf_remote_file:
- Don't do content decoding magic
- checksum required and *always* validates the checksum
Test plan: remove locally compiled ruby and the cached tarballs, run
dev_setup.
Change-Id: Ifb91188ec7ec2f77fafc671d128625ec0f8f1c77
Change-Id: Ib81996a84b0283fd6afc7bb0109d12c620bbcce8
- Add neo4j support
- Save the last deployment in a deployment target file under $HOME
- Change service name i.e. make mysql => mysql_node etc
- Point out the profile file at the end of a deployment, has paths to run vmc
- Audit admin list
- Remove some packages from essentials list
- Increase timeout in bin/vcap that checks if a component is started
patch 3 - Fixed olegs comments.
Testing Done:
Ran Neo4j feature bvt test
Ran single host deployment
Ran multi host mongodb deployment
Change-Id: Id96757bfe109af2f89b9a25e35a669a41c2d259c
Jesse Zhang
Cliff Wang
Mahesh