tapis-pods 0.3.1

The Pods Service is a web service and distributed computing platform providing pods-as-a-service (PaaS). The service implements a message broker and processor model that requests pods, alongside a health module to poll for pod data, including logs, status, and health. The primary use of this service is to have quick to deploy long-lived services based on Docker images that are exposed via HTTP or TCP endpoints listed by the API. **The Pods service provides functionality for two types of pod solutions:** * **Templated Pods** for run-as-is popular images. Neo4J is one example, the template manages TCP ports, user creation, and permissions. * **Custom Pods** for arbitrary docker images with less functionality. In this case we will expose port 5000 and do nothing else. The live-docs act as the most up-to-date API reference. Visit the [documentation for more information](https://tapis.readthedocs.io/en/latest/technical/pods.html).
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44

/*
 * Tapis Pods Service
 *
 *  The Pods Service is a web service and distributed computing platform providing pods-as-a-service (PaaS). The service  implements a message broker and processor model that requests pods, alongside a health module to poll for pod data, including logs, status, and health. The primary use of this service is to have quick to deploy long-lived services based on Docker images that are exposed via HTTP or TCP endpoints listed by the API.  **The Pods service provides functionality for two types of pod solutions:**  * **Templated Pods** for run-as-is popular images. Neo4J is one example, the template manages TCP ports, user creation, and permissions.  * **Custom Pods** for arbitrary docker images with less functionality. In this case we will expose port 5000 and do nothing else.   The live-docs act as the most up-to-date API reference. Visit the [documentation for more information](https://tapis.readthedocs.io/en/latest/technical/pods.html). 
 *
 * The version of the OpenAPI document: 1.9.0
 * Contact: cicsupport@tacc.utexas.edu
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct ModelsPodsResources {
    /// CPU allocation pod requests at startup. In millicpus (m). 1000 = 1 cpu.
    #[serde(rename = "cpu_request", skip_serializing_if = "Option::is_none")]
    pub cpu_request: Option<i32>,
    /// CPU allocation pod is allowed to use. In millicpus (m). 1000 = 1 cpu.
    #[serde(rename = "cpu_limit", skip_serializing_if = "Option::is_none")]
    pub cpu_limit: Option<i32>,
    /// Memory allocation pod requests at startup. In megabytes (Mi)
    #[serde(rename = "mem_request", skip_serializing_if = "Option::is_none")]
    pub mem_request: Option<i32>,
    /// Memory allocation pod is allowed to use. In megabytes (Mi)
    #[serde(rename = "mem_limit", skip_serializing_if = "Option::is_none")]
    pub mem_limit: Option<i32>,
    /// GPU allocation pod is allowed to use. In integers of GPUs. (we only have 1 currently ;) )
    #[serde(rename = "gpus", skip_serializing_if = "Option::is_none")]
    pub gpus: Option<i32>,
}

impl ModelsPodsResources {
    pub fn new() -> ModelsPodsResources {
        ModelsPodsResources {
            cpu_request: None,
            cpu_limit: None,
            mem_request: None,
            mem_limit: None,
            gpus: None,
        }
    }
}