search

pombreda / appscale

Automatically exported from code.google.com/p/appscale
0 stars 0 forks source link

Fix remove-app #101

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Need to have remove-app do delete-instances on all running instances. We
already kill the appserver on all boxes but the kill command sent to the
soap server should soft-delete the data (which it does) and delete
instances in its memory (which it does not).

Original issue reported on code.google.com by shattere...@gmail.com on 2 Nov 2009 at 8:57

GoogleCodeExporter commented 9 years ago 
Necessary changes have been made to the soap/uaserver and tested. Need to clean 
up
text on appscale-tools to better clarify certain use cases.

Original comment by shattere...@gmail.com on 7 Nov 2009 at 1:06

GoogleCodeExporter commented 9 years ago 
Done. Will be in next release of AppScale.

Original comment by shattere...@gmail.com on 8 Nov 2009 at 11:14

GoogleCodeExporter commented 9 years ago 
Re-opened. Having problems with remove app in new testing from scratch install.

Original comment by shattere...@gmail.com on 19 Nov 2009 at 10:52

GoogleCodeExporter commented 9 years ago 
remove-app now appears to work fine as far as the actual removing of apps goes, 
but
isn't correctly setting the enabled flag. In the example below, the app 
'admintest'
was uploaded, removed, then uploaded again, yet has enabled=false instead of
enabled=true:

app_name:admintest
language:python
version:3
app_owner:a@a.a
num_admins:0
admins:
num_hosts:2
hosts:128.111.55.225:128.111.55.225
num_ports:2
ports: 8080:8081
creation_date:1259612066.0
last_update_date:1259612173.0
check_sum:0
num_entries:0
enabled:false
classes:
indexes:0

Database used here is mongodb. Will try out others to see if the problem is db 
specific.

Original comment by shattere...@gmail.com on 30 Nov 2009 at 8:19

GoogleCodeExporter commented 9 years ago 
Furthermore, as the above data shows, there still is instance info about the 
first
time the app was uploaded (to port 8080). This isn't being cleaned out 
correctly and
may be presumed to be a cross-DB problem since it is confirmed with both 
Cassandra
and MongoDB.

Original comment by shattere...@gmail.com on 30 Nov 2009 at 8:35

GoogleCodeExporter commented 9 years ago 
Has this been fixed with all the bug fixes to the soap server?

Original comment by nlak...@gmail.com on 6 Dec 2009 at 12:11

GoogleCodeExporter commented 9 years ago 
yes

Original comment by nlak...@gmail.com on 6 Dec 2009 at 12:15