-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Conversation
…highlight syntax Update to the latest AMIs, tie the Master and Workers to the same AvailabilityZone to reduce the network latency Add detailed Readme to setup a Deep Learning CloudFormation stack
we need a better solution than updating code everytime ... |
do we need to change the ids for every update? i think we have secret weapons to update ami while keeping the id |
@mli Make it use module instead of model while you are at it? |
@mli Also I think we should put some of the logic into functions and move them into the main repo. Here is an idea:
|
I agree, it is not feasible to keep updating everytime a new AMI is made Thanks for your patience. -Naveen On Mon, Nov 14, 2016 at 10:32 AM, Eric Junyuan Xie <notifications@github.com
|
* Rename deeplearning.template to deeplearning.json so that github can highlight syntax Update to the latest AMIs, tie the Master and Workers to the same AvailabilityZone to reduce the network latency Add detailed Readme to setup a Deep Learning CloudFormation stack * Update Authors in Readme.md * Update Authors in Readme.md * rename deeplearning.json to deeplearning.template * rename deeplearning.json to deeplearning.template * update template with latest AMI * update new public AMI Ids
No description provided.