-
Notifications
You must be signed in to change notification settings - Fork 13
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
Set up experiment around mapping with open machine learning #124
Comments
We can either setup on a single machine (EC2) using docker-compose or on a Kubernetes cluster. It's not clear what the infrastructure requirements will be from the OSM Seed stack docs but we can compare differences and our own needs here. Using Kubernetes on AWS has a base cost of $0.10/hr and then each pod (ec2/container/Fargate) has certain base costs. It may take some time to architect an optimized stack if they haven't been already. It is however possible to run some pods but not all, if we only need certain resources. OTOH, a single EC2 instance may need to be quite large to handle the workload of an entire OSM stack. I am currently reaching out to some developers to try to get a better idea on the differences in workload requirements. |
I have almost everything working for osm-seed. You can now:
What's left:
|
We have a fix for running iD as part of the rails app instead of a separate container. This should land in master in a few days.
For OpenHistoricalMap, we use SES and it works really well.
That's weird. Did you use https://github.com/developmentseed/osm-seed/tree/develop/populate-apidb to populate the api database with a planetfile?
Do you use Route53? I'd recommend that. You can get an SSL and setup a loadbalancer to route requests to the ec2. |
We need two similar setups to map empty databases with the Tasking Manager. Such stacks can potentially being created by using the OSM Seed stack. One stack should use iD and the other one RapiD. They can be linked in the Tasking Manager as custom editors.
ping @bopercival-hot @dakotabenjamin @ramyaragupathy @willemarcel
The text was updated successfully, but these errors were encountered: