Classes are groupings derived from common use cases. If you're an AWS user, this will seem pretty familiar. Packet organizes servers into the following classes:
- Tiny (t) - Smaller instances, aimed at dev/test, controller nodes, etc.
- Compute (c) - Compute focused, with a modest RAM footprint.
- GPU (g) - GPU focused with generous RAM
- Memory (m) - Memory heavy, with a generous RAM to core ratio.
- Network (n) - Focused on network use cases, such as ingress / load balancing.
- Storage (s) - Scale out boxes for storage scenarios.
- Accelerator (x) - FPGA and other specialty accelerator focused servers.
Server Naming Convention
All instances have a name that follows a formula to help you understand its purpose and broad specifications: class + generation + size + architecture (optional)
By piecing these features together, we arrive at a name, such as c1.small.x86 - indicating a small compute class server, in its 1st generation with an x86 processor. Since most of our systems are x86 currently, we'll provide nicknames so you can use "c1.small" for shorthand.
What are Generations?
Generations are updated when we significantly upgrade or change the components.
This is usually around a major processor refresh, but often also relates to the underlying hardware configuration / chassis. As such, a "1st" generation system is not necessarily outdated, it is simply our first iteration of a particular configuration.
What About Previous Server Names and API Calls?
Packet previously labeled servers using Types, such as "Type 1" which was represented in the API as "baremetal_1".
These will still work--we have simply made an alias in which baremetal_1 translates to its new name: "c1.small.x86".
Was it helpful?