My favorites | Sign in
Logo
                
Details: Show all Hide all

Last 7 days

  • Dec 30, 2009
    issue 141 (Warn the user if their app is too large) reported by shatteredNirvana   -   Since the user's application is stored in the database, a problem can arise if the database in question cannot store large objects. Need to warn the user if their app is too large (>1MB) while we move the app out of the database into a different location that can store larger files. Done, will be in next release.
    Since the user's application is stored in the database, a problem can arise if the database in question cannot store large objects. Need to warn the user if their app is too large (>1MB) while we move the app out of the database into a different location that can store larger files. Done, will be in next release.
  • Dec 30, 2009
    issue 135 (Running AppScale with bad ips.yaml not handled correctly) Status changed by shatteredNirvana   -   Fixed, will be in next release.
    Status: Fixed
    Fixed, will be in next release.
    Status: Fixed
  • Dec 30, 2009
    issue 138 (Allow user to upload a directory instead of a tarball) Status changed by shatteredNirvana   -   Done. Tested out the following: python app, tar'ed up python app, directory java app, tar'ed up java app, directory All work fine now. Will be in next release.
    Status: Fixed
    Done. Tested out the following: python app, tar'ed up python app, directory java app, tar'ed up java app, directory All work fine now. Will be in next release.
    Status: Fixed
  • Dec 29, 2009
    issue 140 (Appending to a HDFS file) reported by nlake44   -   Need the ability to append to a HDFS file so that apps can do interesting distributed map reduce jobs. A new API call is needed for appending.
    Need the ability to append to a HDFS file so that apps can do interesting distributed map reduce jobs. A new API call is needed for appending.
  • Dec 29, 2009
    issue 139 (SSL doesn't work) reported by shatteredNirvana   -   If the user specifies that certain pages should be secure, these pages should be only accessed over SSL. Since the SDK doesn't generate SSL certificates or enforce this, neither do we. Need to protect access to these pages correctly.
    If the user specifies that certain pages should be secure, these pages should be only accessed over SSL. Since the SDK doesn't generate SSL certificates or enforce this, neither do we. Need to protect access to these pages correctly.
  • Dec 29, 2009
    issue 138 (Allow user to upload a directory instead of a tarball) reported by shatteredNirvana   -   Many beginning users have reported inconveniences with having to tarball up their application instead of simply pointing to the directory containing their app (as Google does). Will give the user the option to do either.
    Many beginning users have reported inconveniences with having to tarball up their application instead of simply pointing to the directory containing their app (as Google does). Will give the user the option to do either.
  • Dec 28, 2009
    issue 137 (Allow for different placement of critical components) reported by shatteredNirvana   -   Right now AppScale components are laid out as follows: 1 node: Database Master, Load Balancer, Master AppController all other nodes: Database Slaves, AppServers, AppControllers Want to explore other layouts, such as: 1 node: Database Master / Load Balancer / AppController 1 node: Master AppController (shadow master) 1 node: Database Slave / AppController 1 node: AppServer / AppController Will investigate performance tradeoffs as well.
    Right now AppScale components are laid out as follows: 1 node: Database Master, Load Balancer, Master AppController all other nodes: Database Slaves, AppServers, AppControllers Want to explore other layouts, such as: 1 node: Database Master / Load Balancer / AppController 1 node: Master AppController (shadow master) 1 node: Database Slave / AppController 1 node: AppServer / AppController Will investigate performance tradeoffs as well.
  • Dec 28, 2009
    issue 132 (Python memcache API stats differences) Status changed by shatteredNirvana   -   Fixed, will be in next release.
    Status: Fixed
    Fixed, will be in next release.
    Status: Fixed
  • Dec 28, 2009
    issue 61 (simplejson support not available) commented on by nlake44   -   Following justinjools's tip fixes that problem, but then the app complains about not having the elementtree module.
    Following justinjools's tip fixes that problem, but then the app complains about not having the elementtree module.
  • Dec 28, 2009
    issue 136 (Possible issue logging out from tasks) commented on by nlake44   -   This problem is on RC2.
    This problem is on RC2.
  • Dec 28, 2009
    issue 134 (Nginx configuration file) Status changed by nlake44   -  
    Status: Fixed
    Status: Fixed
  • Dec 28, 2009
    issue 134 (Nginx configuration file) commented on by nlake44   -   fixed, do a sed find and replace on the template. "false" => "off"
    fixed, do a sed find and replace on the template. "false" => "off"

Last 30 days

  • Dec 27, 2009
    issue 136 (Possible issue logging out from tasks) reported by shatteredNirvana   -   A user has reported the following problem: For task when I click logout. It doesnt work. When I click logout from the status page, that also does not work. It says "sorry something went wrong and we'll look at it shortly." Will investigate tomorrow morning and try to repro.
    A user has reported the following problem: For task when I click logout. It doesnt work. When I click logout from the status page, that also does not work. It says "sorry something went wrong and we'll look at it shortly." Will investigate tomorrow morning and try to repro.
  • Dec 27, 2009
    issue 135 (Running AppScale with bad ips.yaml not handled correctly) reported by shatteredNirvana   -   If appscale is started with a bad ips.yaml or with incorrect args, and then is run it again, the user is told there is already an instance of appscale running. This forces the user to use the terminate tool, which is unnecessary since AppScale isn't running.
    If appscale is started with a bad ips.yaml or with incorrect args, and then is run it again, the user is told there is already an instance of appscale running. This forces the user to use the terminate tool, which is unnecessary since AppScale isn't running.
  • Dec 21, 2009
    issue 134 (Nginx configuration file) reported by nlake44   -   In RC2 the nginx version is 0.7.64. For this version I get the following error when running appscale: [error]: invalid parameter "false", use "off" instead in /etc/nginx/sites- enabled/load-balancer.conf:24 Using off instead of false needs to be tested for the version of nginx which runs on our ubuntu distribution.
    In RC2 the nginx version is 0.7.64. For this version I get the following error when running appscale: [error]: invalid parameter "false", use "off" instead in /etc/nginx/sites- enabled/load-balancer.conf:24 Using off instead of false needs to be tested for the version of nginx which runs on our ubuntu distribution.
  • Dec 17, 2009
    issue 60 (Set up an AppScale Public Cloud for usage) changed by shatteredNirvana   -   Jonathan is currently working on setting up a new public cloud with AppScale 1.3.
    Status: Started
    Owner: jmkupferman
    Cc: shatteredNirvana
    Labels: Type-Other Type-Enhancement
    Jonathan is currently working on setting up a new public cloud with AppScale 1.3.
    Status: Started
    Owner: jmkupferman
    Cc: shatteredNirvana
    Labels: Type-Other Type-Enhancement
  • Dec 17, 2009
    issue 133 (Java memcache API stats differences) changed by shatteredNirvana   -   The Google App Engine memcache API exposes two statistics to the user that are not found in the memcache(d) stats: total number of items currently in memcache time of the oldest item in memcache The local SDK gets around the first stat by keeping a counter of the live items in memcache, but for the second it simply returns the lifetime of the cache itself. Will change our implementation to just return zero for both values until these are both implemented (currently it returns the total number of items ever in memcache and the time of the cache, respectively).
    Summary: Java memcache API stats differences
    Cc: nicneo925 nlake44 ckrintz
    Labels: Priority-Low Usability Component-Logic Priority-Medium
    The Google App Engine memcache API exposes two statistics to the user that are not found in the memcache(d) stats: total number of items currently in memcache time of the oldest item in memcache The local SDK gets around the first stat by keeping a counter of the live items in memcache, but for the second it simply returns the lifetime of the cache itself. Will change our implementation to just return zero for both values until these are both implemented (currently it returns the total number of items ever in memcache and the time of the cache, respectively).
    Summary: Java memcache API stats differences
    Cc: nicneo925 nlake44 ckrintz
    Labels: Priority-Low Usability Component-Logic Priority-Medium
  • Dec 17, 2009
    issue 133 (PY) reported by shatteredNirvana   -   What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.
    What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.
  • Dec 17, 2009
    issue 132 (Python memcache API stats differences) reported by shatteredNirvana   -   The Google App Engine memcache API exposes two statistics to the user that are not found in the memcache(d) stats: total number of items currently in memcache time of the oldest item in memcache The local SDK gets around the first stat by keeping a counter of the live items in memcache, but for the second it simply returns the lifetime of the cache itself. Will change our implementation to just return zero for both values until these are both implemented (currently it returns the total number of items ever in memcache and the time of the cache, respectively).
    The Google App Engine memcache API exposes two statistics to the user that are not found in the memcache(d) stats: total number of items currently in memcache time of the oldest item in memcache The local SDK gets around the first stat by keeping a counter of the live items in memcache, but for the second it simply returns the lifetime of the cache itself. Will change our implementation to just return zero for both values until these are both implemented (currently it returns the total number of items ever in memcache and the time of the cache, respectively).
  • Dec 16, 2009
    r555 (forgot to add new java sdk) committed by shatteredNirvana   -   forgot to add new java sdk
    forgot to add new java sdk
  • Dec 16, 2009
    r554 (committing changes for 1.3-non-beta) committed by shatteredNirvana   -   committing changes for 1.3-non-beta
    committing changes for 1.3-non-beta
  • Dec 16, 2009
    appscale-1.3.tar.gz (AppScale 1.3 Source) file uploaded by shatteredNirvana   -  
    Labels: Featured Type-Source OpSys-Linux
    Labels: Featured Type-Source OpSys-Linux
  • Dec 16, 2009
    appscale_scratch_install_1.3.sh (Scratch install script for AppScale 1.3) file uploaded by shatteredNirvana   -  
    Labels: Featured Type-Installer OpSys-Linux
    Labels: Featured Type-Installer OpSys-Linux
  • Dec 14, 2009
    Single_Node_AppScale_Deployment (How to deploy AppScale via a single node.) Wiki page edited by shatteredNirvana   -   Revision r553 Edited wiki page through web user interface.
    Revision r553 Edited wiki page through web user interface.
  • Dec 14, 2009
    Single_Node_AppScale_Deployment (How to deploy AppScale via a single node.) Wiki page edited by shatteredNirvana   -   Revision r552 Edited wiki page through web user interface.
    Revision r552 Edited wiki page through web user interface.
  • Dec 14, 2009
    Advanced_Features (Features for AppScale users who are accustomed to AppScale) Wiki page edited by shatteredNirvana   -   Revision r551 Edited wiki page through web user interface.
    Revision r551 Edited wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_via_Eucalyptus (How to deploy AppScale 1.3 on top of a Eucalyptus cloud.) Wiki page added by shatteredNirvana   -   Revision r549 Created wiki page through web user interface.
    Revision r549 Created wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_Beta_via_Xen_or_KVM (How to deploy AppScale 1.3 Beta over Xen or KVM.) Wiki page edited by shatteredNirvana   -   Revision r548 Edited wiki page through web user interface.
    Revision r548 Edited wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_via_Xen_or_KVM (How to deploy AppScale 1.3 over Xen or KVM.) Wiki page added by shatteredNirvana   -   Revision r547 Created wiki page through web user interface.
    Revision r547 Created wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_Beta_via_EC2 (How to deploy AppScale 1.3 Beta on top of Amazon EC2.) Wiki page edited by shatteredNirvana   -   Revision r546 Edited wiki page through web user interface.
    Revision r546 Edited wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_via_EC2 (How to deploy AppScale 1.3 on top of Amazon EC2.) Wiki page edited by shatteredNirvana   -   Revision r545 Edited wiki page through web user interface.
    Revision r545 Edited wiki page through web user interface.
  • Dec 14, 2009
    Deploying_AppScale_1_3_via_EC2 (How to deploy AppScale 1.3 on top of Amazon EC2.) Wiki page added by shatteredNirvana   -   Revision r544 Created wiki page through web user interface.
    Revision r544 Created wiki page through web user interface.
  • Dec 14, 2009
    MapReduce_API_Documentation (A description of the MapReduce API in AppScale) Wiki page edited by shatteredNirvana   -   Revision r543 Edited wiki page through web user interface.
    Revision r543 Edited wiki page through web user interface.
  • Dec 14, 2009
    MapReduce_API_Documentation (A description of the MapReduce API in AppScale) Wiki page edited by shatteredNirvana   -   Revision r542 Edited wiki page through web user interface.
    Revision r542 Edited wiki page through web user interface.
  • Dec 14, 2009
    Troubleshooting (Common problems and solutions when using AppScale.) Wiki page edited by shatteredNirvana   -   Revision r541 Edited wiki page through web user interface.
    Revision r541 Edited wiki page through web user interface.
  • Dec 14, 2009
    Supported_AppEngine_APIs (A list of the AppEngine APIs supported in AppScale.) Wiki page edited by shatteredNirvana   -   Revision r540 Edited wiki page through web user interface.
    Revision r540 Edited wiki page through web user interface.
  • Dec 14, 2009
    Troubleshooting (Common problems and solutions when using AppScale.) Wiki page edited by shatteredNirvana   -   Revision r539 Edited wiki page through web user interface.
    Revision r539 Edited wiki page through web user interface.
  • Dec 14, 2009
    issue 126 (MongoDB - Connection refused) commented on by shatteredNirvana   -   Post-mortem analysis suspects that, similarly to the MySQL issue (http://code.google.com/p/appscale/issues/detail?id=128), an old version of the code may have been tested, which exhibited this problem. However, we have opened a new issue for modifying the prime_* scripts to be able to recover from connection refused errors to prevent this from occurring again. The issue is (http://code.google.com/p/appscale/issues/detail?id=131).
    Post-mortem analysis suspects that, similarly to the MySQL issue (http://code.google.com/p/appscale/issues/detail?id=128), an old version of the code may have been tested, which exhibited this problem. However, we have opened a new issue for modifying the prime_* scripts to be able to recover from connection refused errors to prevent this from occurring again. The issue is (http://code.google.com/p/appscale/issues/detail?id=131).
  • Dec 14, 2009
    issue 131 (Recover from connection refused in prime scripts) reported by shatteredNirvana   -   The prime_* scripts assume the database is up and running before they make a connection to it, and in normal execution environments this is largely true. However, sometimes the database is started and grabs a particular port and yet the prime script cannot yet connect to it, causing it to fail. Need to change the prime scripts to expect a connection refused and try to do so 3 times (failing if it cannot).
    The prime_* scripts assume the database is up and running before they make a connection to it, and in normal execution environments this is largely true. However, sometimes the database is started and grabs a particular port and yet the prime script cannot yet connect to it, causing it to fail. Need to change the prime scripts to expect a connection refused and try to do so 3 times (failing if it cannot).
  • Dec 14, 2009
    issue 128 (Cassandra can fail to come up) commented on by shatteredNirvana   -   Post-mortem indicates that although the PYTHON_EGG environment variable was set in ~/.bashrc, it wasn't being picked up by the protocol buffer server, causing it to revert to an incorrect value. Setting the correct value for this variable in the AppController (who starts the PBServer) allows the env var to be correct in the PBServer and allows for correct execution.
    Post-mortem indicates that although the PYTHON_EGG environment variable was set in ~/.bashrc, it wasn't being picked up by the protocol buffer server, causing it to revert to an incorrect value. Setting the correct value for this variable in the AppController (who starts the PBServer) allows the env var to be correct in the PBServer and allows for correct execution.
  • Dec 14, 2009
    issue 129 (MySQL doesn't work in Eucalyptus) commented on by shatteredNirvana   -   Post-mortem indicates this was because the bundled image put into Eucalyptus and distributed for AppScale 1.3 Beta release had an old, untested version of the protocol buffer server. Updating to the latest, fixed code that was tested on Xen/EC2/KVM fixed this problem.
    Post-mortem indicates this was because the bundled image put into Eucalyptus and distributed for AppScale 1.3 Beta release had an old, untested version of the protocol buffer server. Updating to the latest, fixed code that was tested on Xen/EC2/KVM fixed this problem.
  • Dec 13, 2009
    Getting_Started_Current_Release (Getting Started / Details on the Current AppScale Release) Wiki page edited by shatteredNirvana   -   Revision r538 Edited wiki page through web user interface.
    Revision r538 Edited wiki page through web user interface.
  • Dec 13, 2009
    appscale-tools-1.3.tar.gz (AppScale Tools, Version 1.3) file uploaded by shatteredNirvana   -  
    Labels: Featured Latest Stable Type-Tools OpSys-Linux OpSys-OSX
    Labels: Featured Latest Stable Type-Tools OpSys-Linux OpSys-OSX
  • Dec 13, 2009
    appscale1.3.torrent (AppScale, Version 1.3) file uploaded by shatteredNirvana   -  
    Labels: Featured Stable Type-Torrent OpSys-Linux
    Labels: Featured Stable Type-Torrent OpSys-Linux
  • Dec 11, 2009
    issue 127 (HyperTable - MapReduce API doesn't work on Xen/EC2) commented on by shatteredNirvana   -   Reproduced with newest image, continuing to investigate.
    Reproduced with newest image, continuing to investigate.
  • Dec 11, 2009
    issue 129 (MySQL doesn't work in Eucalyptus) Status changed by shatteredNirvana   -   Pulled newest code and appears to work fine in Euca. Will be in AppScale 1.3.
    Status: Fixed
    Pulled newest code and appears to work fine in Euca. Will be in AppScale 1.3.
    Status: Fixed
  • Dec 11, 2009
    issue 126 (MongoDB - Connection refused) Status changed by shatteredNirvana   -   Pulled newest code, unable to reproduce. Will close for now and keep an eye out for this in the future.
    Status: Invalid
    Pulled newest code, unable to reproduce. Will close for now and keep an eye out for this in the future.
    Status: Invalid
  • Dec 11, 2009
    issue 128 (Cassandra can fail to come up) Status changed by shatteredNirvana   -   Fixed, will be in AppScale 1.3 release.
    Status: Fixed
    Fixed, will be in AppScale 1.3 release.
    Status: Fixed
  • Dec 11, 2009
    Introduction_to_Eucalyptus (An introduction on how to upload images into Eucalyptus) Wiki page edited by shatteredNirvana   -   Revision r537 Edited wiki page through web user interface.
    Revision r537 Edited wiki page through web user interface.
  • Dec 10, 2009
    AppScale (References to AppScale publications) Wiki page commented on by mundrapiyush36   -   NA
    NA
 
Hosted by Google Code