Differences

This shows you the differences between two versions of the page.

--- cluster:cluster_config:cisco_vcenter_management [2024/10/27 20:16] – created benedikt
+++ cluster:cluster_config:cisco_vcenter_management [2024/11/04 15:52] (current) – benedikt
@@ Line 1: / Line 1: @@
 ====== Vcenter ======
-The Vcenter is a management tool for the three nodes, it effectively combines the individual nodes (see [[cluster:cluster_administration:the_paper|The paper]]) into 1 converged cluster
+The Vcenter is a management tool for the three nodes, effectively combining the individual nodes (see [[cluster:cluster_administration:the_paper|The paper]]) into a single converged cluster.
+Before working with the Vcenter, **please, please, please** refer to the documentation. A good starting point is the [[https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-A618EF76-638A-49DA-991D-B93C5AC0E2B1.html|VMware Docs]]. Be aware that these resources are very detailed and in-depth.
+The Vcenter is hosted at [[http://vcenter.sleep.ru.is|vcenter.sleep.ru.is]].
-Before playing with the Vcenter, please, please please please refer to the documentation.
+The Vcenter is delicate, and the level of expertise required to manage the VMs and maintain the system cannot be overstated. Any misconfigurations can lead to severe issues, often necessitating intervention from Netters or Cisco for debugging, updates, and general maintenance.
-This is a good starting point [[https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-A618EF76-638A-49DA-991D-B93C5AC0E2B1.html|vmware Docs]], but this is very detailed and in depth.
+<wrap lo>"I cannot emphasize how badly it can go for us if this thing is misconfigured. We've already spent hours and hours trying to figure out licensing, which finally had to be fixed by a Netters technician who himself had to spend hours doing it."
+- Benedikt</wrap>
-The Vcenter itself is hosted on [[http://vcenter.sleep.ru.is|vcenter.sleep.ru.is]].
+====== Who should have access to the Vcenter ======
+Only people whose work is administrating the cluster.
+====== Best practices ======
+Scheduling maintenance should be done considering 2 main issues, usage patterns (make sure that a minimal amount of work is disturbed), and ongoing projects (if a big data collection project is ongoing, maintenance should probably be delayed for the system itself.
-The Vcenter is very delicate, and the level of expertise required to manage the VMs and maintain it is not to be understated.
-This is equipment that generally will require someone from Netters or Cisco to debug and debug, update, and generally maintain it.
-"I cannot emphasize how badly it can go for us if this thing is misconfigured, we've already spent hours and hours and hours trying to figure out licensing, which finally had to be fixed by a netters technician who himself had to spent hours doing it"
-- Benedikt