[FOLIO-896] Create a demo start-up/tear-down system for FOLIO Created: 13/Oct/17 Updated: 03/Jan/24 Resolved: 21/Dec/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P4 |
| Reporter: | Peter Murray | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | for-next-sprint, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2 hours, 15 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||
| Description |
|
To effectively explore FOLIO, one needs the root-level authentication for the system. Publicizing the root-level login for http://folio-stable.aws.indexdata.com/ leaves it susceptible to accidental and malicious configuration changes that make it unstable for its intended purpose. What we need is a way to have individual demo sites that are provisioned and recovered after a short period of time. One proposed method:
A couple of advantages to this method: 1. Every demo site a fresh copy of the system/data in a known state. A disadvantage is that there will need to be a budget for the spot instances. AWS has all of the tools to do this; the tools just need to be arranged to make it happen. |
| Comments |
| Comment by Peter Murray [ 13/Oct/17 ] |
|
Cate Boerema: Could you consider this for an upcoming sprint cycle? |
| Comment by Cate Boerema (Inactive) [ 16/Oct/17 ] |
|
I have tagged it as for-next-sprint and will discuss with Jakub Skoczen when he gets back |
| Comment by Jakub Skoczen [ 25/Oct/17 ] |
|
I'd like to get some input from John Malconian and Wayne Schneider on the perceived set up and maintenance complexity of this. I know we are stretched thin on the CI/CD front. |
| Comment by Peter Murray [ 08/Dec/17 ] |
|
Cate Boerema: I'm guessing this isn't on the critical path for the alpha release. Do you have a sense as to when this will be added to a sprint? |
| Comment by Cate Boerema (Inactive) [ 08/Dec/17 ] |
|
I don't. Per Jakub Skoczen, the next step was to get John Malconian and Wayne Schneider to provide input. What do you think, guys? Maybe we should put in a research spike for investigating? How do we move this forward? |
| Comment by John Malconian [ 08/Dec/17 ] |
|
I think one simple idea is to create regular EC2 AMIs from the most recent folio-snapshot-stable builds and make those images publicly available via the AWS AMI marketplace. That way, anyone with an AWS account can spin up the image and do what they want for however long they want. |
| Comment by Peter Murray [ 11/Dec/17 ] |
|
Creating EC2 AMIs is a good step, but I think we need to take it further because I don't think we can ask the average SME to go through the complexity of creating an AWS account and managing EC2 instances in order to show demos and do testing. EC2 AMIs are a good answer, though, for technical folks that want to exercise the platform but don't want to download the Vagrant image. |