Closed utgarda closed 14 years ago
Try:
rudy machines --clean
Nope, no luck:
> rudy --version
Rudy version: 0.9.8.001
> rudy machines --clean
> Unknown option: --clean
>
> Another try:
> > rudy machines clean
> m-eu-west-1a-stage-stash-01; i-c675f4b1; ec2-79-125-60-193.eu-west-1.compute.amazonaws.com
> etsvigun@linux-k6ka:~/devenv/CloudDemos> rudy startup
> Executing routine: startup
authorize port 22 access for: 194.186.67.200
Rudy::Metadata::DuplicateRecord: Rudy::Metadata::DuplicateRecord: m-eu-west-1a-stage-stash-01
(S)kip (A)bort:
Oops, my bad! The option is --wash
rudy machines -h
USAGE: rudy
USAGE: rudy machines
USAGE: rudy machines -l
USAGE: rudy machines -U
USAGE: rudy machines -A [static ip address]
USAGE: rudy machines -N
USAGE: rudy machines -T
USAGE: rudy machines -P
USAGE: rudy machines -O
ABOUT: View Machines
-W, --wash Wash machine metadata
-T, --available Test availablity
-U, --update Update machines based on configuration
-A, --associate Associate static IP addresses or display existing ones
-N, --disassociate Disassociate static IP addresses
-P, --password Display admin password (Windows only)
-O, --console Display console output
-l, --all Display machines for all environments and roles
Yep, that works.
If I clean all created keypairs and security groups from AWS account, next launch of a project that was once started and not shutdown properly, fails with errors. How do I fix that?