Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update fabfile #48

Merged
merged 3 commits into from Mar 7, 2016

Conversation

Projects
None yet
3 participants
@TimoRoth
Copy link
Contributor

commented Mar 7, 2016

Fixes issue #41 by generating a unique identifier for the keyname.

While at it, I added some functions to terminate individual instances/volumes, so we don't have to kill each others instances via cloud_terminate, or leave them running indefinitely.

Also bumped the Ubuntu AMIs to include some of the latest security fixes by default.

After this is merged, connecting to already running instances via fab connect won't work anymore, but manually invoking ssh with the old key file still works(ssh -i ~/.ssh/eu-west-1_oggm.pem ec2-52-50-61-172.eu-west-1.compute.amazonaws.com)

@fmaussion

This comment has been minimized.

Copy link
Member

commented Mar 7, 2016

Thanks! Could you add this new info in the doc also? (i.e.: how to connect, and in particular, how to NOT kill each others instances)

fso42 pushed a commit that referenced this pull request Mar 7, 2016

Felix Oesterle
Merge pull request #48 from TimoRoth/master
Update fabfile. Thanks Timo

@fso42 fso42 merged commit d141ecb into OGGM:master Mar 7, 2016

0 of 2 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
@fmaussion

This comment has been minimized.

Copy link
Member

commented Mar 7, 2016

mh. I guess this will have to be done in a separate PR! :D

@TimoRoth

This comment has been minimized.

Copy link
Contributor Author

commented Mar 7, 2016

In general. nothing about how to connect changed, it's just that already running instances still use the old key, while the updated script will generate and use new ones. The issue will be gone once all currently running instances have been restarted.

@fmaussion

This comment has been minimized.

Copy link
Member

commented Mar 7, 2016

So will fab cloud_terminate still terminate the instances I created?

@TimoRoth

This comment has been minimized.

Copy link
Contributor Author

commented Mar 7, 2016

Yes, it will tear down everything except for the user volumes mounted at /work.
I'll add some owner tags which are printed in the instance/volume listing, so it's easier to see which instance belongs to whom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.