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

Research and decide on hosting #8

Closed
Tracked by #608
thekaveman opened this issue Sep 29, 2021 · 2 comments
Closed
Tracked by #608

Research and decide on hosting #8

thekaveman opened this issue Sep 29, 2021 · 2 comments
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc)

Comments

@thekaveman
Copy link
Member

thekaveman commented Sep 29, 2021

Background

The eligibility server needs to be hosted somewhere such that it can receive and respond to HTTP requests from a Benefits client instance.

The owner of the hosting environment is not as important as are the agreement(s) in place that allow for sharing of (hashed) Courtesy Card data with said hosting environment.

Decision needed

The main decision point for hosting of the Eligibility Server:

Will the server be co-located with the Benefits client app deployment (CDT/Azure), or will the server be deployed to a new environment?

Co-locating with Benefits client app

The server would just be another Azure App Service.

  • Simplest approach, no new cloud accounts / environments to build out
  • Reuse deployment strategy from Benefits app
  • Need CDT hosting contract signed
  • Need CDT approval to store hashed data

Deploy in a new cloud environment

  • Adds 1-2 weeks of build/configure time
  • Compiler would set this up and manage it (likely GCP, Google Cloud Endpoints looks like one option)
  • Could also setup Azure on behalf of MST
  • Should probably have agreement between Compiler <> MST
@thekaveman thekaveman added this to the October 2021 milestone Oct 7, 2021
@thekaveman thekaveman modified the milestones: December 2021, January 2022, Q1 2022 maintenance, Hosting and deployment Jan 5, 2022
@thekaveman thekaveman moved this to Backlog in Digital Services Jan 18, 2022
@thekaveman thekaveman changed the title Research hosting in GCP Research and decide on hosting May 20, 2022
@thekaveman thekaveman moved this from Backlog to Next Sprint (Month) in Digital Services May 20, 2022
@machikoyasuda machikoyasuda added the deliverable Work that ends with a non-code deliverable (e.g. Google doc) label May 24, 2022
@afeld
Copy link
Contributor

afeld commented Jul 11, 2022

Intersects with cal-itp/benefits#774

@thekaveman thekaveman moved this from Next Sprint (Month) to This Sprint (Month) in Digital Services Aug 1, 2022
@thekaveman
Copy link
Member Author

See #158 - we're going to deploy to MST's Azure

Repository owner moved this from This Sprint (Month) to Done in Digital Services Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc)
Projects
Archived in project
Development

No branches or pull requests

3 participants