4 #. Log in as an admin user.
5 #. Navigate *Clusters -> Add Cluster*
6 #. Fill out properties and click *save*
8 When the Cluster is imported into Ganeti Web Manager it will
9 automatically synchronize. Virtual Machine objects will be created to
10 match what is found on the Ganeti Cluster. :ref:`permission-tags` will
11 also be parsed to automatically add permissions for virtual machines.
13 A cluster can be added with only its hostname and port, but a username
14 and password for the cluster are required if you want to make changes to
15 it. Clusters added without a valid username and password appear in
16 :ref:`cluster-read-only` where you can only change aspects of the
17 cluster that are local to Ganeti Web Manager's database.
19 If you're logged in as a cluster admin or superuser you can edit
20 properties of a cluster by using the "edit" button on the cluster detail
23 .. warning:: If a cluster is in :ref:`cluster-read-only`, there
24 will be errors if you try to modify virtual machines or
28 Synchronizing Clusters
29 ----------------------
31 Ganeti Web Manager stores some information about clusters in its
32 database. Cluster and virtual machine information will
33 :ref:`refresh automatically <lazy-cache>`, but the list of virtual
34 machines must be synchronized manually. This can be done by via the
37 #. Main Menu -> Orphans
39 Clusters are synchronized when the orphans view is visited.
41 Adding Virtual Machines
42 -----------------------
44 To add a virtual machine, select "Create VM" in the toolbar. Only fields
45 with multiple options will be selectable. For example, if you are unable
46 to change the cluster to which a VM gets added, it means that there is
47 only one valid option and cluster is a mandatory field.
49 - If the user creating the VM has permissions to do so, the owner will
50 be that user. If the user does not have create permissions but is a
51 member of a group that can create VMs, ownership defaults to that
53 - Cluster can be chosen from those that the the user creating the VM
55 - The Hypervisor will generally be dictated by the cluster that you
57 - The instance name must be a fully qualified domain name (FQDN). (e.g.
59 - If you uncheck "Start up after creation", you can start the VM
60 manually on its virtual machine detail page. (click Virtual Machines
61 in the sidebar, then the VM's name)
62 - DNS name check: if checked, sends the name you selected for the VM to
63 the resolver (e.g. in DNS or /etc/hosts, depending on your setup).
64 Since the name check is used to compute the IP address this also
65 enables/disables IP checks (e.g. if the IP is pingable). Uncheck if
67 - Disk Template chooses a layout template from these options:
69 - plain - Disk devices will be logical volumes (e.g. LVM)
70 - drbd - Disk devices will be DRBD (version8.x) on top of LVM
73 - If drbd is selected, a primary and secondary node will need to
74 be chosen unless automatic allocation has been selection. DRBD
75 will allow the virtual machine to use live migration and
76 failover in case one of the nodes goes offline.
78 - file - Disk devices will be regular files (e.g. qcow2)
79 - diskless - This creates a virtual machine with no disks. Its
80 useful for testing only (or other special cases).
82 - Operating system to install on the virtual machine. Your choices are
83 limited to the images configured on the cluster.
87 - Virtual CPUs will be deducted from owner's quota. If the owner field
88 appears blank and is not selectable, the default owner has been
90 - Memory is the amount of RAM to give this VM. If no units are given,
92 - Disk size is the amount of owner's disk quota to allot this VM. If no
93 units are given, megabytes is assumed.
94 - Disk type determines the way the disks are presented to the virtual
95 machine. Options may vary based on cluster's hypervisor settings.
96 - More information about NIC Mode, NIC Link, and NIC Type can be found
97 `here <http://docs.ganeti.org/ganeti/current/html/install.html#configuring-the-network>`_
99 Hypervisor parameters:
101 *TODO finish this part*
105 Orphaned Virtual Machines
106 -------------------------
108 :ref:`permission-tags` are parsed by virtual machine objects, but
109 sometimes virtual machines will have no tags. To quickly identify
110 virtual machines with no admin users, use the orphans view
112 #. Main Menu -> Orphans
114 Visiting the orphans view will force a synchronization of all clusters
115 and display VirtualMachines that do not have any permissions assigned.
116 You only need to grant permissions directly on virtual machines if you
117 are granting access to non-admin users.