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

EAM: Change RequiredResources numCPU to allow fractional cpus #253

Open
gainsley opened this issue Jun 7, 2024 · 0 comments · May be fixed by #280
Open

EAM: Change RequiredResources numCPU to allow fractional cpus #253

gainsley opened this issue Jun 7, 2024 · 0 comments · May be fixed by #280
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines

Comments

@gainsley
Copy link
Collaborator

gainsley commented Jun 7, 2024

Problem description
The Edge-Application-Management's current RequiredResources' numCPU field is an integer, which restricts vcpu resource allocation to whole vcpus. Notably Kubernetes allows for fractional vcpu allocation down to the millivcpu, to allow for very lightweight containers/microservices that do not use a lot of compute.

Expected behavior
Being able to specify required vcpus in milli-vcpu increments.

Alternative solution
None.

Additional context
The GSMA Federation EWBI already allows for this:

    Vcpu:
      type: string
      pattern: ^\d+((\.\d{1,3})|(m))?$
      description: Number of vcpus in whole, decimal up to millivcpu, or millivcpu format.
      example:
        whole:
          value: 2
        decimal:
          value: 0.500
        millivcpu:
          value: 500m

For VM-based deployments, fractional vcpus may not be allowed, but that should be implementation dependent. For example a VM deployed via Kata-containers (kube-virt) on a Kubernetes cluster may allow for fractional vcpus.

@gainsley gainsley added the correction Suggesting corrections of API specification or indicating misalignment with API design guidelines label Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction Suggesting corrections of API specification or indicating misalignment with API design guidelines
Projects
None yet
1 participant