Use fakeDbDriver when no cmdb/database support

Author: lowang-bh

README.md

@@ -1,7 +1,6 @@
 # ReadME
 
-
-## Env Setting Up:
+## Env Setting Up
 
     1). create a virtual env with python2.7
 
@@ -20,6 +19,8 @@
 
         export DB_HOST=127.0.0.1:8000
 
+      If you don't have a cmdb now, just let DB_HOST not set. It will do nothing with database.
+
     5). setup the platform env: Xen for xenserver or KVM for KVM platform, the default is Xen
 
         export PLATFORM=KVM
@@ -28,10 +29,13 @@
         start the log server in case of no permission to the directory /var/log
 
         sudo nohup python ~/dev_virt/lib/Log/logging_server.py &
+
 ## Xenserver API Architecture
+
  ![highlevel](XenserverApi-Architecture.png)
 
-## Some phrase:
+## Some phrase
+
 - PIF: physical interface, the eth on server
 - VIF: virtual  interface, the eth on VM
 - SR:  storage repository, the storage pool on server
@@ -55,17 +59,18 @@
     }
   ```
 
-##  1. Auto schedual the target vm to a available server
+## 1. Auto schedual the target vm to a available server
 
   > schedule_node.py --role=rolename --cluster=<dev|test|prod>
-  
+
   > Note: user can define the vm-name rule at function `generate_vmname_key(role, cluster)` in file `lib/Utils/schedule.py`
 
-##  2. manually given the target vm-name, host and vm-ip.
+## 2. manually given the target vm-name, host and vm-ip
 
   > schedule_node.py --role=rolename --name=new_vm_name --host=hostip --ip=vm_ip
   
 # Create multiple VMs from xml config
+
 - `setup_vms.py --validate xmlFile`     Validate the given xml file
 - `setup_vms.py --create   xmlFile`     Do the create up according to the xml file
 
@@ -108,32 +113,33 @@ Create VMs with xml just need to write a xml config following the xml-example. B
 </servers>
 ```
 
-
-# Scripts:
+# Scripts
 
 ## 1. Sync information from exist server to database
 
-   - `sync_server_info.py`          will sync both server and VM information to DB, and create a record in DB if not exist
-   - `sync_server_info.py --update` Just update information to DB
+- `sync_server_info.py`          will sync both server and VM information to DB, and create a record in DB if not exist
+- `sync_server_info.py --update` Just update information to DB
 
 ## 2. create_vm.py
 
-  - `--list-vm`             List all the vms in server.
-  - `--list-templ`          List all the templates in the server.
-  - `--list-network`        List the bridge/switch network in the host
-  - `--list-SR`             List the storage repository infor in the host
+- `--list-vm`             List all the vms in server.
+- `--list-templ`          List all the templates in the server.
+- `--list-network`        List the bridge/switch network in the host
+- `--list-SR`             List the storage repository infor in the host
 
-#####  2.1). <b>**Create a new VM with a template:**<b>
-  - `-c VM_NAME, --create=VM_NAME`                        Create a new VM with a template.
-  - `-t TEMPLATE, --templ=TEMPLATE`                       Template used to create a new VM.
+##### 2.1). <b>**Create a new VM with a template:**<b>
+
+- `-c VM_NAME, --create=VM_NAME`                        Create a new VM with a template.
+- `-t TEMPLATE, --templ=TEMPLATE`                       Template used to create a new VM.
 
     > create_vm.py -c "test_vm" -t "CentOS 7.2 Template"
 
-#####  2.2). <b>**Create a new VM with a given IP: if a IP specified**<b>
-  - `--vif=VIF_INDEX`      The index of virtual interface on which configure will be
-  - `--device=DEVICE`      The target physic NIC name with an associated network VIF attach(ed) to
-  - `--network=NETWORK`    The target bridge/switch network which VIF connect(ed) to
-  - `--ip=VIF_IP`          The ip assigned to the virtual interface
+##### 2.2). <b>**Create a new VM with a given IP: if a IP specified**<b>
+
+- `--vif=VIF_INDEX`      The index of virtual interface on which configure will be
+- `--device=DEVICE`      The target physic NIC name with an associated network VIF attach(ed) to
+- `--network=NETWORK`    The target bridge/switch network which VIF connect(ed) to
+- `--ip=VIF_IP`          The ip assigned to the virtual interface
 
     **a VIF index(*--vif*) is needed and a PIF name(*--device*) or a bridge name(*--network*) is needed**
     > create_vm.py -c "test2" -t "CentOS 7.2 template" --ip=192.168.1.100 --vif=0 --device=eth0
@@ -143,98 +149,110 @@ Create VMs with xml just need to write a xml config following the xml-example. B
     **neither *--device* nor *--network*, the default manage network will be used**
     > create_vm.py -c "test2" -t "CentOS 7.2 template" --ip=192.168.1.100 --vif=0
 
-#####  2.3). <b>**Create a new VM with given max cpu cores and current cpu cores:**<b>
-  - `--cpu-max=MAX_CORES`   Config the max VCPU cores.
-  - `--cpu-cores=CPU_CORES` Config the number of startup VCPUs for the new created VM
+##### 2.3). <b>**Create a new VM with given max cpu cores and current cpu cores:**<b>
+
+- `--cpu-max=MAX_CORES`   Config the max VCPU cores.
+- `--cpu-cores=CPU_CORES` Config the number of startup VCPUs for the new created VM
 
     > create_vm.py -c "test2" -t "CentOS 7.2 template" --cpu-core=2 --cpu-max=4
 
     The max cpu cores can be configured when VM is power off only, and it affect the upper limit when set the cpu cores lively
 
-#####  2.4). <b>**Create a new VM with memory size:**<b>
-  - `--memory=MEMORY_SIZE`  Config the target memory size in GB.
-  - `--min-mem=MIN_MEMORY`  Config the min static memory size in GB.
-  - `--max-mem=MAX_MEMORY`  Config the max static memory size in GB.
+##### 2.4). <b>**Create a new VM with memory size:**<b>
+
+- `--memory=MEMORY_SIZE`  Config the target memory size in GB.
+- `--min-mem=MIN_MEMORY`  Config the min static memory size in GB.
+- `--max-mem=MAX_MEMORY`  Config the max static memory size in GB.
 
      <b>There are static memory and dynamic memory. The static memory can be set only when VM is power off, and dynamic memory
   can be set when VM is running or stop. Memory limits must satisfy: *min_static_memory <= min_dynamic_memory <= max_dynamic_memory <= max_static_memory*. The max_static_memory will affect the upper limit when set the dynamic memory lively when VM is running.<b>
 
-
-  - `--memory will set the min dynamic memory and max dynamic memory to the target one, when VM power on, it runs at that memory size`
-  - `--min-mem will set the min static memory `
-  - `--max-mem will set the max static memory `
+- `--memory will set the min dynamic memory and max dynamic memory to the target one, when VM power on, it runs at that memory size`
+- `--min-mem will set the min static memory`
+- `--max-mem will set the max static memory`
     > create_vm.py -c "test2" -t "CentOS 7.2 template" --memory=2 --max-mem=4
 
 ##### 2.5).Add new disk to VM, the storage_name is choosed from *--list-SR*
-  - `--add-disk=DISK_SIZE`  The disk size(GB) add to the VM
-  - `--storage=STORAGE_NAME` The storage location where the virtual disk put
+
+- `--add-disk=DISK_SIZE`  The disk size(GB) add to the VM
+- `--storage=STORAGE_NAME` The storage location where the virtual disk put
     > create_vm.py "test1"--add-disk=2 --storage=data2
 
     **if no *--storage*, will use the storage which has a largest free volume**
     > create_vm.py "test1"--add-disk=2
 
 ## 3. delete_vm.py
+
   To delete a vm, please use *delete_vm.py --vm=vm_to_delete*, this will ask user to input 'yes' or 'no' to confirm
-  - `delete_vm.py  --vm=vm_name [--host=ip --user=user --pwd=passwd]`
+
+- `delete_vm.py  --vm=vm_name [--host=ip --user=user --pwd=passwd]`
 
   if `--force` is set, then the additional disk on vm will also be deleted, this feature is only support on kvm now.
 
 ## 4. config_vm.py
-#### The IP and memory configuration is same as that in create VM.
-  - `--list-vif`            List the virtual interface device in guest VM
-  - `--list-pif`            List the interface device in the host
-  - `--list-network`        List the bridge/switch network in the host
-  - `--list-SR`             List the storage repository information in the host
+
+#### The IP and memory configuration is same as that in create VM
+
+- `--list-vif`            List the virtual interface device in guest VM
+- `--list-pif`            List the interface device in the host
+- `--list-network`        List the bridge/switch network in the host
+- `--list-SR`             List the storage repository information in the host
 
 ##### 4.1). <b>**Config a VM's interface, add a VIF, delete a VIF, config a VIF(will delete old one if exist, otherwise create it newly), and the *--ip*, *--device*, *--network* is same as that when create vm**<b>
-  - `--add-vif=ADD_INDEX`   Add a virtual interface device to guest VM
-  - `--del-vif=DEL_INDEX`   Delete a virtual interface device from guest VM
-  - `--vif=VIF_INDEX`      Configure on a virtual interface device
+
+- `--add-vif=ADD_INDEX`   Add a virtual interface device to guest VM
+- `--del-vif=DEL_INDEX`   Delete a virtual interface device from guest VM
+- `--vif=VIF_INDEX`      Configure on a virtual interface device
 
     > config_vm.py "test1"  --vif=0 --ip=192.168.1.200 --device=eth0
 
     > config_vm.py "test1"  --add-vif=1 --device=eth1 --ip=192.168.1.200 --netmask=255.255.255.0
 
 ##### 4.2). <b>**config a VM' cpu when it is running**<b>
-  - `--cpu-cores=CPU_CORES` Config the VCPU cores lively for a running VM or the number of startup VCPUs for a halted VM
+
+- `--cpu-cores=CPU_CORES` Config the VCPU cores lively for a running VM or the number of startup VCPUs for a halted VM
 
       > config_vm.py "test1" --cpu-core=4
 
 ##### 4.3). <b>**config a VM' memory when it is running**<b>
-  - `--memory=MEMORY_SIZE`  Config the target memory size in GB.
+
+- `--memory=MEMORY_SIZE`  Config the target memory size in GB.
 
     > config_vm.py "test1" --memory=1
 
 ##### 4.4).Add new disk to VM, the storage_name is choosed from *--list-SR*
-  - `--add-disk=DISK_SIZE`  The disk size(GB) add to the VM
-  - `--storage=STORAGE_NAME` The storage location where the virtual disk put
+
+- `--add-disk=DISK_SIZE`  The disk size(GB) add to the VM
+- `--storage=STORAGE_NAME` The storage location where the virtual disk put
     > config_vm.py "test1"--add-disk=2 --storage=data2
 
     **if no *--storage*, will use the storage which has a largest free volume**
     > config_vm.py "test1"--add-disk=2
 
-
 ## 5. power_on.py, power_off.py
- - power_on.py vm1 vm2 \[--host=ip --user=user --pwd=passwd\]
- - power_off.py vm1 vm2 \[--host=ip --user=user --pwd=passwd\]
+
+- power_on.py vm1 vm2 \[--host=ip --user=user --pwd=passwd\]
+- power_off.py vm1 vm2 \[--host=ip --user=user --pwd=passwd\]
 
 ## 6. dump_vm.py, ist the memory, CPU, Disk, and system information of VM
-  - `--list`                List the cpu and memory information
-  - `--list-disk`           List the virtual disk size
-  - `--list-vifs`           List all the VIFs information
+
+- `--list`                List the cpu and memory information
+- `--list-disk`           List the virtual disk size
+- `--list-vifs`           List all the VIFs information
 
     **if no options, will list all basic informations, include, cpu, memory, os, disk, interface mac and IP**
 
     **Note: a problem is that the VIF index given to xenserver, but it is not always the index of eth in VM guest, it depend on the create sequence of virtual interface.**
 
 ## 7. dump_host.py, list the memory, CPU, Disk, and system information of server
-  - `--list-sr`             List all the storage information
-  - `--list-pif`            List all the interface information
-  - `--list-bond`           List all the bond information
-  - `--list-vm`             List all the vms
-  - `--list-templ`          List all the templates in the server.
-  - `--list-network`        List the network in the host (in Xenserver, it is same as bridge)
-  - `--list-bridge`         List the bridge/switch names in the host
+
+- `--list-sr`             List all the storage information
+- `--list-pif`            List all the interface information
+- `--list-bond`           List all the bond information
+- `--list-vm`             List all the vms
+- `--list-templ`          List all the templates in the server.
+- `--list-network`        List the network in the host (in Xenserver, it is same as bridge)
+- `--list-bridge`         List the bridge/switch names in the host
 
     > dump_host.py    \[--host=ip --user=user --pwd=passwd\]
 

app/cmdb/fake_db_driver.py

@@ -0,0 +1,37 @@
+#!/usr/bin/env python
+# -*- coding: utf-8 -*-
+"""
+ File  Name: fake_db_driver.py
+ Author: longhui
+ Created Time: 2021-6-26 18:24:47
+"""
+
+
+from lib.Db.db_driver import DatabaseDriver
+
+
+class FakeDBDriver(DatabaseDriver):
+    def __init__(self, user="admin", passwd="admin"):
+        pass
+
+    def __nonzero__(self):
+        """
+        rewrite this so that the instance support value test
+        :return:
+        """
+        return True
+
+    def close(self):
+        return True
+
+    def create(self, **kwargs):
+        return True
+
+    def delete(self, id=None):
+        return True
+
+    def update(self, id=None, data=None):
+        return True
+
+    def query(self, id=None):
+        return True

lib/Db/db_factory.py

@@ -7,17 +7,26 @@
  Descriptions: The factory class for Database crud
 '''
 
+import os
 from app.cmdb.hosts import HostDriver, VirtualHostDriver
+from app.cmdb.fake_db_driver import FakeDBDriver
+
 
 class DbFactory(object):
 
     @classmethod
     def get_db_driver(cls, table_class):
         """
         return the relative database driver class
+        If DB_HOST enviroment is not configure, return fake db driver that will do nothing
         :param table_class: the table class define in app folder
         :return:
         """
+
+        DB_HOST = os.getenv("DB_HOST", None)
+        if DB_HOST is None:
+            return FakeDBDriver()
+
         if table_class == "Host":  # Physical server
             return HostDriver()
         elif table_class == "VirtHost":  # Virtual machine