3.3 instances (Instances)

VirtOn The Instant Management Screen ofSo, the life cycle of individual instances(Lifecycle) And it's a key feature of real-time resource control.

Before use

3.3.1 Virtual machine & container list management

3.3.1.1 Instant listing

• You can see the instances lists of all the nodes in the cluster that we're currently building. (ID, name, type, status, allocated resources)

3.3.1.2 Instant search and filtering

• You can search by entering the instance name in the top right of the main page, and you can filter the nodes of the cluster that you're currently building.

3.3.1.3 is the power factor.

• If you click the task list button on the right side of the virtual machine & container you want to control, the control menu will appear. (Start, stop, restart)
• Start / connect / stop: Activate or securely close the console session with the instances.
• The console: It runs the console from a separate browser window and supports a multitasking environment.
• Set it up: CPU It's like, "Memory" and so on.

• VM/CT When the shutdown is in → start, restart, deactivate
• VM/CT When the run is on → Stop, restart activate
• If the power management fails, the target VM/CT The current state of Proxmox API Check the connection status, the account permissions.

3.3.2 Instantaneous generated (VM/CT It's generated)

• Up on the right. VM/CT If you click on the Create button, you'll see a window where you can choose to create a virtual machine or a container.

3.3.2.1 VM It's generated (Virtual Machine)

1. Basic information

• I'm not going to lie. It selects the physical server location for the virtual machine to create and run.
• VM Name: English alphabets, numbers, hyphen(-) It's only available, and the creation of any other special characters or hangers is limited when you type in.

2. Setup of the OS

• OS type: The type of operating system to install on a virtual machine(Linux, Windows, and so on.) It's the default for the virtualization optimization driver.
• OS version: It specifies the specific kernel version that matches the selected OS type. (For example, Linux is the case. 6.x - 2.6 Kernel) Proxmus Hypervisor helps you provide the most optimized hardware profile for your OS.

Three, the system. (System)

• BIOS: It determines how the virtual machine boots firmware. SeaBIOS (Legacy compatibility) Using the latest OS specifications or specific requirements(Security booting and so on.) You can change it to UEFI firmware.
• SCSI Controller: Data input from a virtual disk(I/O) It's the controller that's responsible for the communication. VirtIO SCSI single It offers the fastest and most stable I/O performance in the latest virtualization environment.
• Qemu Agent (Recommended): When activated, the host server(Proxmus, please.) And the virtual machine.(Guest OS) It opens up a dedicated communication channel in the liver. VM You can check the real-time IP addresses of the power supply, and not force the power to shut down, but 'safe shutdown'.(Graceful Shutdown)'It becomes possible.
• Auto Start: When activated, host(The node.) After rebooting, the virtual machine will start automatically. VM We recommend activating this option for troubleshooting and uninterrupted operation.

4. Resource setting (CPU - The memory.)

• CPU Core/socket: It specifies the number of physical and logical processes to be assigned to a virtual machine.
• CPU Type: What is it? CPU Select the command set of. (Yes, I know. x86-64-v2-AES It supports encryption acceleration, which improves security performance.)
• Memory: It's a virtual machine. RAM We recommend setting a minimum of 512 MiB or more for system stability.

5th, the Resource List (The disk / the network / ISO)

• ISO Image: This is the first time Select the original image file for the operating system installation. [It's uploaded to the storage by pressing the Add button. ISO You can specify the file.
• Network: Bridges to be used by virtual machines.(Bridge) Come on, you know what? VLAN Add the settings. [You can create a multisite network interface with the Add button.
• The disc: It creates storage space for virtual machines. [You can add multiple virtual disks with the +Add] button, and the details are as follows:
  • Device: Just the type of bus that connects the disk.(Yes, I know. scsi0) It's going to show.
  • Storage: It selects the physical/logical storage location where the virtual disk files are actually stored.
  • Disk size (GiB): It specifies the maximum capacity of the disk to be allocated to the virtual machine.
  • Format: It determines the format of the disk image. QEMU image format (qcow2) The first step is to create snapshots and manage the flexible capacity(I'm the scene provider.) It's a recommended format that fully supports the(However, if the selected storage is block-based, this setting is ignored and automatically generated for maximum performance. raw It can be fixed in a format.)*

VM Summary of the input values generated

3.3.2.2 VM Set it up (Change the boot order.)

• VM The setting brings in the values that are already set and sets the boot order(Correction) You can only change it on the page.
• The boot order: The virtual machine.(VM) When the power goes on, What device?(Disc, CD-ROM, network, and so on.) From the operating system(OS) The ability to determine the search order of the first to readIt's the same as the BIOS/UEFI boot setting on a physical PC.

3.3.2.3 CT It's generated (LXC Container)

• I'm not going to lie. The physical server where the container is created and the resources are allocated(The node.) I'm going to choose.
• Hostname: English, the alphabet, the numbers, the hyphen.(-) Only available, and other input generated is limited.
• Password / Password verified: The top manager of the container.(root) Set the initial password for your account to use. To strengthen security, the content of the two input fields must match, and a strong password setting is required according to the policy.
• OS template:
  • Storage: You select the storage where the template file is stored.
  • Template:This is the first time. The operating system image that will be the basis for the container distribution(Ubuntu, CentOS, and more.) If you don't have a template available, you need to upload or download it in advance.
• System settings:
  • CPU I'm going to tell you. I'm going to use the container. CPU So we're going to set the number of cores.
  • Memory / Swap: I'm going to assign it to the container. RAM Capacity and virtual memory(Swap) Set the capacity.
• List of names (Disk, Network):
  • The disc: It's a storage space inside the container. [+Add] You can set up a mount point or additional disk space by clicking on the button.
  • Network: It's a virtual interface and network bridge. [+Add] You can set up a multisite network environment with a button.
• DNS settings:
  • Domain / DNS server: The container specifies the domain name and name server addresses that it uses to communicate with an external network or interpret names.

CT Summary of the input values generated

3.3.3 Detailed information of the instances

• That's right. VM/CT Click on the name and you'll see the details page.

3.3.3.1 System information

• The details of the page VM/CT System information (OS, boot order) You can see the resources, the network, the disk.
• Instant control button: You can control the status of the instances with the button in the top right.
  • Stop and restart: It controls the power of the instances.
  • Set it up: CPU It's like, "Memory" and so on.
  • The console: It calls the terminal environment to connect to the inside of the instance.
  • Delete: You permanently remove the instances and the resources that are associated with them.
• The system: Operating system(OS) Type and boot order.(Boot Order) So, we're going to show you the basic information.
• So what's the problem? It's assigned CPU Core number, vCPU number, processor type(Example: AES encryption speed support or not) And it shows the memory capacity.
• Network: The name of the network interface that connects to the instances, Bridge.(vmbr) It gives you unique MAC address information.
• The disc: The ID of the virtual disk(Scsi0 and so on.) It shows the capacity, the interface type.

3.3.3.2 Resource use and trends (Monitoring)

• Real-time resource use (Gauges):
  • CPU Usage rate: The total allocation of the current use of the CPU The core weighting percentage(%) So I'm going to show you.
  • Memory usage: It's a real-time verification of the current capacity of allotted memory.
  • State of play: If the resource usage is stable, it's marked "normal", which helps the manager make quick decisions.
• Resource trends are on the rise. (Historical Charts):
  • Read/write the disk (MB/s): Time-based disk input and output(I/O) It's a graph of the speed, and it shows the phenomenon of the canopy.
  • Network traffic (MB/s): The Input(In) and leakage(Out) It monitors the flow of traffic.
  • Set the visit time: The drop-down on the top right allows you to filter the data you want, like the last hour.

3.3.3.3 Console connection (Console)

• VNC console connection: Standard VNC(Virtual Network Computing) Using the protocol, you call the desktop or terminal screen of a virtual instance within a web browser.
• Key control functions:
  • Connect / shut down: Activate or securely close the console session with the instances.
  • Reboot: What is it? I'm rebooting the instances.
  • So, in terms of the whole thing: It's a full-screen workflow that increases the visibility.
  • New window: It runs the console from a separate browser window and supports a multitasking environment.

• Key transmission: A combination of special keys that are difficult to enter directly in a virtual environment(Ctrl + Alt + Del) It sends and executes system commands.

• Show the real-time status: Running status of the instance through the console bottom bar(Status), type of virtualization(KVM/LXC) You can check the associated nodes and the unique ID information in real time.
• If the console connection fails, VM/CT Check for running status, console access permissions, browser pop-up blocking.

I'm going to go back to the computer.

Backup functionThe virtual machine(VM) Or containers.(CT) The current state of the data and the data are stored in separate storage space, Key features for rapid recovery of systems in case of a malfunctionThat's it.

1. Backup created

• Storage: The physical location where the backup file is stored(For example, local, nfs-storage, etc.) I'm going to choose.
• Mods. (Mode): Choose a way to perform the backup.
  • Snapshot: It does backup in real time without interrupting the instances.
  • Suspend/Stop: You pause or shut down the instances and then you back them up to maximize the data integration.
• Protect (Protection): Selecting the checkbox will prevent the backup from being deleted by mistake.
• Notes (Note): We type in the identification information or description of the backup file and use it as a reference when we recover it.
• Select the instance type: Type of backup object(VM(QEMU) Or container.(LXC)) You can select an object from the filtered list by specifying the filtered list.

1. Backup list and status management

• I'm going to check the backup list. Backup file name, subject VM I'll check the ID, the nodes and the storage information at a glance.
• Search and filter: Search window:* I don't know the file name. VM You type in the ID and you quickly find the specific backup.
  • The state filter: It's sorting the list by "completed", "failed", "in progress", and it's improving management efficiency.
  • Type filter: VM Or we can sort out the backup portions of each container and then we can look at them.

• The progress indicator: If the backup is being performed, the real-time progress rate is(%) You can track the expected completion time of the task through the status bar, and if necessary, you can stop the task immediately by pressing the 'Cross' button.
• If the backup fails, the target storage capacity, the backup mode, VM/CT The state, Proxmox I'm going to check the workload.

I'm going to take a snapshot of this.

The snapshot feature is a virtual machine at a specific point in time.(VM) Or containers.(CT) It preserves the status quo, providing a feature that can be immediately returned to the stored time when a setup error or system failure occurs.

1. Creating a snapshot

• Name of the snapshot: You type a name to identify the snapshot. (Yes, I know. before_update, stable_config Back to the office.)
• Explanation (The Choice): It records additional information about why the snapshot was created or the system's state at the time, which makes it easier to manage.
• RAM Includes: If you choose this option, you can not only access the disk data of the virtual machine, but also the data of the virtual machine. The memory that's running now(RAM) It's in the air.And we're going to keep it together.
  • Check time: After recovery, it runs immediately as it was without the need to turn off the power.
  • MICHAEL: It only saves the disk state, and after recovery, you have to reboot the system.

1. List of snapshots and controls

• I'm going to take a look at the list of snapshots. Check the snapshot name, the creation time, the associated nodes and the description information.
• State of play: You can visually see where the instances are at the moment, or how much they've changed since the snapshot was created.
• Main work button:
  • Roll back. (Rollback): It returns the status of the virtual resource at the selected snapshot point, and all the changes that are currently made disappear and are overlaid with snapshot data.
  • Delete it (Remove): You permanently remove the saved snapshot files, which gives you storage space.

How to solve problems