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

Refactor ec2 startup script (potentially into a new project into a scripting language) #289

Open
evansiroky opened this issue Mar 16, 2020 · 0 comments

Comments

@evansiroky
Copy link
Contributor

Observed behavior

When deploying to an ELB instance, at least the 2 following items could be improved:

  1. The download of all assets for the bundle occurs on the datatools-server instance and then needs to be uploaded to s3 and then downloaded again to the graph-building instance.
  2. There isn't great error reporting in the user data startup script. IE, if something fails, the failure reason can't be immediately be derived.

Expected behavior

  1. The graph-building instance could create the bundle instead to decrease the amount of time it takes to wait for the bundle to be uploaded and then downloaded.
  2. It may be best to have a separate project that has a startup script that can be downloaded onto the ec2 instance and then perform all of the startup tasks.

Steps to reproduce the problem

n/a

Any special notes on configuration used

A datatools-server with ec2 deployments enabled.

Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)

f49d482

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant