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

Move front end to App Engine #22

Open
5 tasks
mina86 opened this issue Sep 11, 2021 · 0 comments
Open
5 tasks

Move front end to App Engine #22

mina86 opened this issue Sep 11, 2021 · 0 comments

Comments

@mina86
Copy link
Contributor

mina86 commented Sep 11, 2021

The front end is almost in a state where it could be easily moved to App Engine. This would save us from having to maintain the process on a virtual machine and bring other benefits of App Engine such as auto-scaling. There are a few issues to sort out:

  • Figure out how to read nearcore git repository. When scheduling runs, the front end needs to access the nearcore repository. More specifically, the commit message and contents of the nightly directory of a given sha / head of master branch. Currently this is easy; the repository is cloned and updated whenever new run needs to be scheduled. If front end was moved to App Engine we’d need to figure out how to deal with that. Cloning the entire repository each time new run is scheduled would introduce latency to the call and keeping the repository isn’t that great of an option when storage is ephemeral.
  • Migrate from apsscheduler to App Engine Cron service. This shouldn’t be too complicated.
  • Use App Engine credentials to access Cloud Storage.
  • Use App Engine credentials to access Cloud SQL. If I understand App Engine correctly each app automatically gets credentials to authenticate as itself and those can be used to gain access to other Google Cloud services. This would simplify configuration.
  • Make the switch.
@mina86 mina86 added T-nodeX P-Low Low priority labels Sep 11, 2021
@gmilescu gmilescu added the T-node label Aug 9, 2022
@mina86 mina86 removed their assignment May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants