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

feat(test) Staging Environment #515

Open
andrewrisse opened this issue May 15, 2024 · 1 comment
Open

feat(test) Staging Environment #515

andrewrisse opened this issue May 15, 2024 · 1 comment
Labels
enhancement ✨ New feature or request

Comments

@andrewrisse
Copy link
Contributor

User Story

As a LFAI product manager
I want a staging environment
So that I have a stable environment with the latest features off main for demos and release testing

Acceptance Criteria

Features merged into main are auto-released into staging environment.

Must not be publicly accessible, only internal to LF team

Additional context

Should this be non GPU to save on cost?

@andrewrisse andrewrisse added the enhancement ✨ New feature or request label May 15, 2024
@andrewrisse andrewrisse added this to the v0.8.0 milestone May 15, 2024
@barronstone barronstone changed the title Staging Environment feat(test) Staging Environment May 31, 2024
@barronstone
Copy link
Collaborator

I think we're currently using a p3.8xlarge instance for burning.boats and (eventually) uds.is. While tackling this issue, we should investigate if another cheaper instance type would work for us, with key limitations being the GPU needs to be a new enough architecture and the instance needs to be available in GovCloud regions.

The g4dn.12xlarge seems like it might be a viable contender with 4 NVIDIA T4 Tensor Core GPUs. It's roughly 1/3 the cost of the p3.8xlarge we're currently using.

References:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement ✨ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants