-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feat: FRIKA integrated & roadmap (#2)
* feat: frika integrated & roadmap Signed-off-by: Iztok Lebar Bajec <[email protected]> * feat: nxt & amd go live Signed-off-by: Iztok Lebar Bajec <[email protected]> * fix: k8s text and wording Signed-off-by: Iztok Lebar Bajec <[email protected]> --------- Signed-off-by: Iztok Lebar Bajec <[email protected]>
- Loading branch information
Showing
7 changed files
with
1,684 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# About FRIKA | ||
|
||
FRIKA consists of three NVIDIA HGX Redstone GPU servers specifically dedicated to inferencing. The principal goal is to provide infrastructure for researchers and laboratories that want to offer their solutions (models/applications) as web services and thus promote their research/development work at UL FRI. | ||
|
||
FRIKA is currently running as a system of individual nodes that provide resources via Incus virtual machines and/or containers. Depending on requirements it is planned to be progressively further expanded. A long-term plan is to port all services to a Kubernetes-based cluster. | ||
|
||
Research labs that own and manage their inferencing systems themselves, may inquire about the possibility of integrating their infrastructure into FRIKA. Cofunding of future FRIKA expansions is also possible. All inquiries should be addressed to the UL FRI Management Board, the technical details will be coordinated by the FRIKA technical committee. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
# Obtaining resources | ||
|
||
Access to the FRIKA infrastructure may be granted (upon request) to all employees of UL FRI. Applications should be addressed to the UL FRI Management Board. They should briefly explain the services that are to be deployed on the allocated VM and the amount of resources needed (number of vCPUs, amount of VM memory, amount of memory on the GPU, amount of disk), together with a justification of the scope. The maximum amount of RAM per GPU requested is 40GB (systems are based on A100 40GB SMX4). The application should also list the expected level of utilization, i.e. the expected number of users, and how this fits in with the promotion of UL FRI. All websites and/or services deployed on FRIKA are expected to announce that they are running on the UL FRI FRIKA infrastructure (exposure of a UL FRI logo is sufficient). | ||
|
||
Once access is granted by the UL FRI Management Board, the technical questions should be directed to [email protected]. | ||
|
||
Resource usage is monitored and in case of higher numbers of applications, the allocated quota may be reduced depending on utilization history. | ||
|
Oops, something went wrong.