deleting experiments

[remcinerney]

deleting experiments

[dconathan]

You can delete all experiments with a docker rm $(docker ps -aq) (this will delete all docker containers on your machine... note that this doesn't mean you have to rebuild the images). There is a remove_experiment method of the Helper class, but as of right now there are no user-friendly scripts/utils for running it.

[remcinerney]

OK great, I'll use the helper class... thanks.

[stsievert]

You can also remove your experiments with docker-compose rm. I recommend this method.

If you're launching via AMI, launching a new machine via the AMI will (effectively) remove all experiments. You can restore any experiments you wish to keep by downloading/restoring as mentioned at the bottom of the experiment list.

Not providing an interface to remove data is a design goal of NEXT.

[remcinerney]

Is there a convenient way to ssh into an AWS cluster using the next_ec2 script? (I'm trying to do this so I can play around with the docker containers as discussed in this thread....

Thanks

[lalitkumarj]

Yes. python next_ec2.py --identity-file={location to pem key} --key-pair={name of pem key} docker_login MACHINE_NAME You should also have the appropriate environment keys set: AWS_SECRET_ACCESS_KEY AWS_ACCESS_KEY_ID AWS_BUCKET_NAME See the following for more detail: https://github.com/nextml/NEXT/blob/master/README.md Note that to use this above procedure, the machine should have been launched by the next_ec2 script as well as described on that page. So basically using a python next_ec2.py launch command. You can also SSH into the AMI using a PEM key. Make sure that you become superuser (su -) and then go to the /usr/local/next-discovery directory. I hope that helps!

…

On Wed, Apr 12, 2017 at 7:33 AM, remcinerney ***@***.***> wrote: Is there a convenient way to ssh into an AWS cluster using the next_ec2 script? (I'm trying to do this so I can play around with the docker containers as discussed in this thread.... Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#177 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABWhGI9R1bjNWjSn8ufZ2prt910hs9i8ks5rvLaCgaJpZM4M1hsy> .

[remcinerney]

Ok great - I now have access to the server through that method - but not sure which container I should be removing to delete experiments?
Is each experiment's data stored in a separate container?

[lalitkumarj]

The idea is that you delete all the containers which deletes ALL the experiments. Then you do docker-compose up to fire up NEXT again. There is no way to really delete one experiment - this was done on purpose to ensure that experiments don't get deleted by mistake. Lalit

…

On Wed, Apr 12, 2017 at 8:33 AM, remcinerney ***@***.***> wrote: Ok great - I now have access to through that method - but not sure which container I should be removing to delete experiments? Is each experiment operating in a separate container? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#177 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABWhGASzH9fPW6mGsq7JB4Vh1Ebbu9snks5rvMSmgaJpZM4M1hsy> .

[remcinerney]

Ok got it, makes sense

In that case is there a difference between using docker and docker-compose when doing this?

[lalitkumarj]

Yes. You should always use docker-compose (unless bad things happen and you need to do a reset). docker-compose stop docker-compose start docker-compose up docker-compose rm docker-compose log are all the commands you probably need.

…

On Wed, Apr 12, 2017 at 8:37 AM, remcinerney ***@***.***> wrote: Ok got it, makes sense In that case is there a difference between using docker and docker-compose when doing this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#177 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABWhGFuoOXW9jEnvW0GZMQ1QTO0sCPi4ks5rvMWHgaJpZM4M1hsy> .