F OpenNebula/one#6723: Remove 'onehost importvm'

OpenNebula · Sep 18, 2024 · 711490d · 711490d
1 parent 7910146
commit 711490d
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 25 deletions.
diff --git a/...ce/integration_and_development/infrastructure_drivers_development/devel-vmm.rst b/...ce/integration_and_development/infrastructure_drivers_development/devel-vmm.rst
@@ -63,7 +63,7 @@ These arguments are specified in the :ref:`oned.conf file <oned_conf>`, ``argume
         default    = "vmm_exec/vmm_exec_kvm.conf",
         ...
 
-Each driver can define a list of supported actions for :ref:`imported VMs <import_wild_vms>`. Please note that in order to import VMs, your monitoring drivers should report the :ref:`IMPORT_TEMPLATE variable <devel-im_vm_information>`. The complete list of actions is:
+Each driver can define a list of supported actions for :ref:`imported VMs <import_wild_vms>`. The complete list of actions is:
 
 .. _devel_actions:
 

diff --git a/source/intro_release_notes/release_notes/whats_new.rst b/source/intro_release_notes/release_notes/whats_new.rst
@@ -7,7 +7,7 @@ What’s New in |version|
 OpenNebula Core
 ================================================================================
 
-- Feature 1
+- Removed `onehost importvm` command for importing wild VMs. (todo add more info)
 - Feature 2
 
 Storage & Backups

diff --git a/source/management_and_operations/host_cluster_management/hosts.rst b/source/management_and_operations/host_cluster_management/hosts.rst
@@ -107,7 +107,7 @@ To display information about a single Host, use the ``show`` command:
 
     WILD VIRTUAL MACHINES
 
-    NAME                                                      IMPORT_ID  CPU     MEMORY
+    NAME                                                      DEPLOY_ID  CPU     MEMORY
 
     VIRTUAL MACHINES
 
@@ -120,7 +120,7 @@ The information of a Host contains:
 * **Capacity** (*Host Shares*) for CPU and memory.
 * **Local datastore information** (*Local System Datastore*) if the Host is configured to use a local datastore (e.g. in SSH transfer mode).
 * **Monitoring Information**, including PCI devices and NUMA information of the node. You can also find hypervisor specific information here.
-* **Virtual Machines** allocated to the Host. *Wild* are virtual machines running on the Host but not started by OpenNebula, and can be imported.
+* **Virtual Machines** allocated to the Host. *Wild* are virtual machines running on the Host but not started by OpenNebula.
 
 To see a list of all the Hosts:
 
@@ -324,10 +324,10 @@ You can also select which Hosts you want to upgrade by naming them or selecting
 
 .. _import_wild_vms:
 
-Importing Wild VMs
+Wild VMs
 ================================================================================
 
-The monitoring mechanism in OpenNebula reports all VMs found in a hypervisor, even those not launched through OpenNebula. These VMs are referred to as Wild VMs and can be imported to be managed through OpenNebula. The Wild VMs can be spotted through the ``onehost show`` command:
+The monitoring mechanism in OpenNebula reports all VMs found in a hypervisor, even those not launched through OpenNebula. These VMs are referred to as Wild VMs. The Wild VMs can be spotted through the ``onehost show`` command:
 
 .. prompt:: bash $ auto
 
@@ -339,20 +339,13 @@ The monitoring mechanism in OpenNebula reports all VMs found in a hypervisor, ev
       STATE                 : MONITORED
       [...]
       WILD VIRTUAL MACHINES
-                          NAME                            IMPORT_ID  CPU     MEMORY
+                          NAME                            DEPLOY_ID  CPU     MEMORY
                  Ubuntu14.04VM 4223f951-243a-b31a-018f-390a02ff5c96    1       2048
                        CentOS7 422375e7-7fc7-4ed1-e0f0-fb778fe6e6e0    1       2048
 
-And imported using the ``onehost importvm`` command:
+The VM import feature was removed in release 7.0, you can still use VMs imported in previous OpenNebula releases.
 
-.. prompt:: bash $ auto
-
-      $ onehost importvm 0 CentOS7
-      $ onevm list
-      ID USER     GROUP    NAME            STAT UCPU    UMEM HOST               TIME
-       3 oneadmin oneadmin CentOS7         runn    0    590M MyAWSHost  0d 01h02
-
-After a Virtual Machine is imported, its life-cycle (including creation of snapshots) can be controlled through OpenNebula. However, some  operations *cannot* be performed on an imported VM, including: poweroff, undeploy, migrate or delete-recreate.
+Life-cycle of imported Virtual Machine (including creation of snapshots) can be controlled through OpenNebula. However, some  operations *cannot* be performed on an imported VM, including: poweroff, undeploy, migrate or delete-recreate.
 
 .. warning:: Wild VMs’ support and limitations may differ depending on the virtualization driver used (e.g KVM or LXC). In order to find more specific information for the virtualization driver you’re using, please check the corresponding driver guide.
 

diff --git a/source/open_cluster_deployment/kvm_node/kvm_node_installation.rst b/source/open_cluster_deployment/kvm_node/kvm_node_installation.rst
@@ -134,15 +134,6 @@ To add a node to the cloud, run this command as ``oneadmin`` in the Front-end (r
       ID NAME            CLUSTER   RVM      ALLOCATED_CPU      ALLOCATED_MEM STAT
        0 node01          default     0       0 / 400 (0%)     0K / 7.7G (0%) on
 
-.. _kvm_wild:
-
-Step 8. Import Existing VMs (Optional)
-======================================
-
-Optionally, you can import virtual machines already running on the Host. You'll be able to control such virtual machines from OpenNebula, although the set of operations is vastly reduced (when compared to the virtual machines started from OpenNebula). Follow the :ref:`Importing Wild VMs <import_wild_vms>` guide.
-
-You can import wild VMs anytime later.
-
 .. _kvm_next:
 
 Next steps