]> git.proxmox.com Git - pve-docs.git/blob - pve-gui.adoc
updated tags docs
[pve-docs.git] / pve-gui.adoc
1 [[chapter_gui]]
2 Graphical User Interface
3 ========================
4 ifndef::manvolnum[]
5 :pve-toplevel:
6 endif::manvolnum[]
7
8 {pve} is simple. There is no need to install a separate management
9 tool, and everything can be done through your web browser (Latest
10 Firefox or Google Chrome is preferred). A built-in HTML5 console is
11 used to access the guest console. As an alternative,
12 https://www.spice-space.org/[SPICE] can be used.
13
14 Because we use the Proxmox cluster file system (pmxcfs), you can
15 connect to any node to manage the entire cluster. Each node can manage
16 the entire cluster. There is no need for a dedicated manager node.
17
18 You can use the web-based administration interface with any modern
19 browser. When {pve} detects that you are connecting from a mobile
20 device, you are redirected to a simpler, touch-based user interface.
21
22 The web interface can be reached via https://youripaddress:8006
23 (default login is: 'root', and the password is specified during the
24 installation process).
25
26
27 Features
28 --------
29
30 * Seamless integration and management of {pve} clusters
31
32 * AJAX technologies for dynamic updates of resources
33
34 * Secure access to all Virtual Machines and Containers via SSL
35 encryption (https)
36
37 * Fast search-driven interface, capable of handling hundreds and
38 probably thousands of VMs
39
40 * Secure HTML5 console or SPICE
41
42 * Role based permission management for all objects (VMs, storages,
43 nodes, etc.)
44
45 * Support for multiple authentication sources (e.g. local, MS ADS,
46 LDAP, ...)
47
48 * Two-Factor Authentication (OATH, Yubikey)
49
50 * Based on ExtJS 7.x JavaScript framework
51
52
53 Login
54 -----
55
56 [thumbnail="screenshot/gui-login-window.png"]
57
58 When you connect to the server, you will first see the login window.
59 {pve} supports various authentication backends ('Realm'), and
60 you can select the language here. The GUI is translated to more
61 than 20 languages.
62
63 NOTE: You can save the user name on the client side by selecting the
64 checkbox at the bottom. This saves some typing when you login next
65 time.
66
67
68 GUI Overview
69 ------------
70
71 [thumbnail="screenshot/gui-datacenter-summary.png"]
72
73 The {pve} user interface consists of four regions.
74
75 [horizontal]
76
77 Header:: On top. Shows status information and contains buttons for
78 most important actions.
79
80 Resource Tree:: At the left side. A navigation tree where you can select
81 specific objects.
82
83 Content Panel:: Center region. Selected objects display configuration
84 options and status here.
85
86 Log Panel:: At the bottom. Displays log entries for recent tasks. You
87 can double-click on those log entries to get more details, or to abort
88 a running task.
89
90 NOTE: You can shrink and expand the size of the resource tree and log
91 panel, or completely hide the log panel. This can be helpful when you
92 work on small displays and want more space to view other content.
93
94
95 Header
96 ~~~~~~
97
98 On the top left side, the first thing you see is the Proxmox
99 logo. Next to it is the current running version of {pve}. In the
100 search bar nearside you can search for specific objects (VMs,
101 containers, nodes, ...). This is sometimes faster than selecting an
102 object in the resource tree.
103
104 To the right of the search bar we see the identity (login name). The
105 gear symbol is a button opening the 'My Settings' dialog. There you
106 can customize some client side user interface setting (reset the saved
107 login name, reset saved layout).
108
109 The rightmost part of the header contains four buttons:
110
111 [horizontal]
112 Help :: Opens a new browser window showing the reference documentation.
113
114 Create VM :: Opens the virtual machine creation wizard.
115
116 Create CT :: Open the container creation wizard.
117
118 Logout :: Logout, and show the login dialog again.
119
120
121 [[gui_my_settings]]
122 My Settings
123 ~~~~~~~~~~~
124
125 [thumbnail="screenshot/gui-my-settings.png"]
126
127 The 'My Settings' window allows you to set locally stored settings. These
128 include the 'Dashboard Storages' which allow you to enable or disable specific
129 storages to be counted towards the total amount visible in the datacenter
130 summary. If no storage is checked the total is the sum of all storages, same
131 as enabling every single one.
132
133 Below the dashboard settings you find the stored user name and a button to
134 clear it as well as a button to reset every layout in the GUI to its default.
135
136 On the right side there are 'xterm.js Settings'. These contain the following
137 options:
138
139 [horizontal]
140 Font-Family :: The font to be used in xterm.js (e.g. Arial).
141
142 Font-Size :: The preferred font size to be used.
143
144 Letter Spacing :: Increases or decreases spacing between letters in text.
145
146 Line Height :: Specify the absolute height of a line.
147
148
149
150 Resource Tree
151 ~~~~~~~~~~~~~
152
153 This is the main navigation tree. On top of the tree you can select
154 some predefined views, which change the structure of the tree
155 below. The default view is the *Server View*, and it shows the following
156 object types:
157
158 [horizontal]
159 Datacenter:: Contains cluster-wide settings (relevant for all nodes).
160
161 Node:: Represents the hosts inside a cluster, where the guests run.
162
163 Guest:: VMs, containers and templates.
164
165 Storage:: Data Storage.
166
167 Pool:: It is possible to group guests using a pool to simplify
168 management.
169
170
171 The following view types are available:
172
173 [horizontal]
174 Server View:: Shows all kinds of objects, grouped by nodes.
175
176 Folder View:: Shows all kinds of objects, grouped by object type.
177
178 Pool View:: Show VMs and containers, grouped by pool.
179
180
181 Log Panel
182 ~~~~~~~~~
183
184 The main purpose of the log panel is to show you what is currently
185 going on in your cluster. Actions like creating an new VM are executed
186 in the background, and we call such a background job a 'task'.
187
188 Any output from such a task is saved into a separate log file. You can
189 view that log by simply double-click a task log entry. It is also
190 possible to abort a running task there.
191
192 Please note that we display the most recent tasks from all cluster nodes
193 here. So you can see when somebody else is working on another cluster
194 node in real-time.
195
196 NOTE: We remove older and finished task from the log panel to keep
197 that list short. But you can still find those tasks within the node panel in the
198 'Task History'.
199
200 Some short-running actions simply send logs to all cluster
201 members. You can see those messages in the 'Cluster log' panel.
202
203
204 Content Panels
205 --------------
206
207 When you select an item from the resource tree, the corresponding
208 object displays configuration and status information in the content
209 panel. The following sections provide a brief overview of this
210 functionality. Please refer to the corresponding chapters in the
211 reference documentation to get more detailed information.
212
213
214 Datacenter
215 ~~~~~~~~~~
216
217 [thumbnail="screenshot/gui-datacenter-search.png"]
218
219 On the datacenter level, you can access cluster-wide settings and information.
220
221 * *Search:* perform a cluster-wide search for nodes, VMs, containers, storage
222 devices, and pools.
223
224 * *Summary:* gives a brief overview of the cluster's health and resource usage.
225
226 * *Cluster:* provides the functionality and information necessary to create or
227 join a cluster.
228
229 * *Options:* view and manage cluster-wide default settings.
230
231 * *Storage:* provides an interface for managing cluster storage.
232
233 * *Backup:* schedule backup jobs. This operates cluster wide, so it doesn't
234 matter where the VMs/containers are on your cluster when scheduling.
235
236 * *Replication:* view and manage replication jobs.
237
238 * *Permissions:* manage user, group, and API token permissions, and LDAP,
239 MS-AD and Two-Factor authentication.
240
241 * *HA:* manage {pve} High Availability.
242
243 * *ACME:* set up ACME (Let's Encrypt) certificates for server nodes.
244
245 * *Firewall:* configure and make templates for the Proxmox Firewall cluster wide.
246
247 * *Metric Server:* define external metric servers for {pve}.
248
249 * *Support:* display information about your support subscription.
250
251
252 Nodes
253 ~~~~~
254
255 [thumbnail="screenshot/gui-node-summary.png"]
256
257 Nodes in your cluster can be managed individually at this level.
258
259 The top header has useful buttons such as 'Reboot', 'Shutdown', 'Shell',
260 'Bulk Actions' and 'Help'.
261 'Shell' has the options 'noVNC', 'SPICE' and 'xterm.js'.
262 'Bulk Actions' has the options 'Bulk Start', 'Bulk Shutdown' and 'Bulk Migrate'.
263
264 * *Search:* search a node for VMs, containers, storage devices, and pools.
265
266 * *Summary:* display a brief overview of the node's resource usage.
267
268 * *Notes:* write custom comments in xref:markdown_basics[Markdown syntax].
269
270 * *Shell:* access to a shell interface for the node.
271
272 * *System:* configure network, DNS and time settings, and access the syslog.
273
274 * *Updates:* upgrade the system and see the available new packages.
275
276 * *Firewall:* manage the Proxmox Firewall for a specific node.
277
278 * *Disks:* get an overview of the attached disks, and manage how they are used.
279
280 * *Ceph:* is only used if you have installed a Ceph server on your
281 host. In this case, you can manage your Ceph cluster and see the status
282 of it here.
283
284 * *Replication:* view and manage replication jobs.
285
286 * *Task History:* see a list of past tasks.
287
288 * *Subscription:* upload a subscription key, and generate a system report for
289 use in support cases.
290
291
292 Guests
293 ~~~~~~
294
295 [thumbnail="screenshot/gui-qemu-summary.png"]
296
297 There are two different kinds of guests and both can be converted to a template.
298 One of them is a Kernel-based Virtual Machine (KVM) and the other is a Linux Container (LXC).
299 Navigation for these are mostly the same; only some options are different.
300
301 To access the various guest management interfaces, select a VM or container from
302 the menu on the left.
303
304 The header contains commands for items such as power management, migration,
305 console access and type, cloning, HA, and help.
306 Some of these buttons contain drop-down menus, for example, 'Shutdown' also contains
307 other power options, and 'Console' contains the different console types:
308 'SPICE', 'noVNC' and 'xterm.js'.
309
310 The panel on the right contains an interface for whatever item is selected from
311 the menu on the left.
312
313 The available interfaces are as follows.
314
315 * *Summary:* provides a brief overview of the VM's activity and a `Notes` field
316 for xref:markdown_basics[Markdown syntax] comments.
317
318 * *Console:* access to an interactive console for the VM/container.
319
320 * *(KVM)Hardware:* define the hardware available to the KVM VM.
321
322 * *(LXC)Resources:* define the system resources available to the LXC.
323
324 * *(LXC)Network:* configure a container's network settings.
325
326 * *(LXC)DNS:* configure a container's DNS settings.
327
328 * *Options:* manage guest options.
329
330 * *Task History:* view all previous tasks related to the selected guest.
331
332 * *(KVM) Monitor:* an interactive communication interface to the KVM process.
333
334 * *Backup:* create and restore system backups.
335
336 * *Replication:* view and manage the replication jobs for the selected guest.
337
338 * *Snapshots:* create and restore VM snapshots.
339
340 * *Firewall:* configure the firewall on the VM level.
341
342 * *Permissions:* manage permissions for the selected guest.
343
344
345 Storage
346 ~~~~~~~
347
348 [thumbnail="screenshot/gui-storage-summary-local.png"]
349
350 As with the guest interface, the interface for storage consists of a menu on the
351 left for certain storage elements and an interface on the right to manage
352 these elements.
353
354 In this view we have a two partition split-view.
355 On the left side we have the storage options
356 and on the right side the content of the selected option will be shown.
357
358 * *Summary:* shows important information about the storage, such as the type,
359 usage, and content which it stores.
360
361 * *Content:* a menu item for each content type which the storage
362 stores, for example, Backups, ISO Images, CT Templates.
363
364 * *Permissions:* manage permissions for the storage.
365
366
367 Pools
368 ~~~~~
369
370 [thumbnail="screenshot/gui-pool-summary-development.png"]
371
372 Again, the pools view comprises two partitions: a menu on the left,
373 and the corresponding interfaces for each menu item on the right.
374
375 * *Summary:* shows a description of the pool.
376
377 * *Members:* display and manage pool members (guests and storage).
378
379 * *Permissions:* manage the permissions for the pool.
380
381
382 Tags
383 ----
384
385 [thumbnail="screenshot/gui-qemu-summary-tags-edit.png", float="left"]
386
387 For organizational purposes, it is possible to set `tags` for guests.
388 Currently, these only provide informational value to users.
389 Tags are displayed in two places in the web interface: in the `Resource Tree` and
390 in the status line when a guest is selected.
391
392 Tags can be added, edited, and removed in the status line of the guest by
393 clicking on the `pencil` icon. You can add multiple tags by pressing the `+`
394 button and remove them by pressing the `-` button. To save or cancel the changes,
395 you can use the `✓` and `x` button respectively.
396
397 Tags can also be set via the CLI, where multiple tags are separated by semicolons.
398 For example:
399
400 ----
401 # qm set ID --tags myfirsttag;mysecondtag
402 ----
403
404 Style Configuration
405 ~~~~~~~~~~~~~~~~~~~
406
407 [thumbnail="screenshot/gui-datacenter-tag-style.png"]
408
409 By default, the tag colors are derived from their text in a deterministic way.
410 The color, shape in the resource tree, and case-sensitivity, as well as how tags
411 are sorted, can be customized. This can be done via the web interface under
412 __Datacenter -> Options -> Tag Style Override__. Alternatively, this can be done
413 via the CLI. For example:
414
415 ----
416 # pvesh set /cluster/options --tag-style color-map=example:000000:FFFFFF
417 ----
418
419 sets the background color of the tag `example` to black (#000000) and the text
420 color to white (#FFFFFF).
421
422 Permissions
423 ~~~~~~~~~~~
424
425 [thumbnail="screenshot/gui-datacenter-options.png"]
426
427 By default, users with the privilege `VM.Config.Options` on a guest (`/vms/ID`)
428 can set any tags they want (see
429 xref:pveum_permission_management[Permission Management]). If you want to
430 restrict this behavior, appropriate permissions can be set under
431 __Datacenter -> Options -> User Tag Access__:
432
433 * `free`: users are not restricted in setting tags (Default)
434 * `list`: users can set tags based on a predefined list of tags
435 * `existing`: like list but users can also use already existing tags
436 * `none`: users are restricted from using tags
437
438 The same can also be done via the CLI.
439
440 Note that a user with the `Sys.Modify` privileges on `/` is always able to set
441 or delete any tags, regardless of the settings here. Additionally, there is a
442 configurable list of `registered tags` which can only be added and removed by
443 users with the privilege `Sys.Modify` on `/`. The list of registered tags can be
444 edited under __Datacenter -> Options -> Registered Tags__ or via the CLI.
445
446
447 For more details on the exact options and how to invoke them in the CLI, see
448 xref:datacenter_configuration_file[Datacenter Configuration].
449
450 ifdef::wiki[]
451
452 See Also
453 --------
454
455 * link:/wiki/Central_Web-based_Management
456
457 endif::wiki[]
458