NETDEDI Cloud Server

• Data center locations:
  • South Korea, Hong Kong, North America
• Details:
  • Cloud platform: XCP
  • Hypervisor: Xen
  • Storage type: Central SAN
  • Minimum period: Hourly
  • Purchasing model: Server, storage and bandwidth purchased separately
  • Phone support: Yes
  • Online pricing & immediate signup: Yes
  • Free trial: Yes [1 week]
• Features:
  • High Availability: Yes
  • Scalable instances: Yes
  • Guaranteed CPU minimum: No
• Extra functionality:
  • Integrated backup/snapshot: Yes
  • Integrated load balancing: Yes
  • Integrated firewall: Yes
  • API: Yes
• Operative systems:
  • Windows support: Yes
  • Linux support: Yes
  • Custom OS support: Yes

In addition to cloud servers, CDN (Content Delivery Network) services are also offered. To read more about the cloud servers from Renet, please visit their website or check out the other tabs on this page. httts://www.netdedi.com

Monitoring Cloudstack-Zenoss 4.2.5

1. System Requirement.    OS: CentOS 64-bit 6.x (recommended)   Hardware Requirements: Up to 1000 Devices Deployment Size Memory CPU Storage   1 to 250 devices   4GB   2 cores   1x300GB, 10K RPM drive or SSD  250 to 500 devices  8GB  4 cores  1x300GB, 10K RPM drive or SSD  500 to 1000 devices  16GB  8 cores  1x300GB, 15K RPM drive or SSD Auto-deploy Installation Note: Updated for 4.2.5 The simplest way to install Zenoss Core 4.2 on a newly-deployed RHEL/CentOS 64-bit 5/6 system is to use our auto-deploy script, which downloads all required files for you. To use the script, first set up a new server running one of our supported operating systems. Then, as root, run the following commands: # wget https://github.com/zenoss/core-autodeploy/tarball/4.2.5 -O auto.tar.gz # tar xvf auto.tar.gz # cd zenoss-core-autodeploy-* Now, you have the option of editing zenpack_actions.txt, which defines all ZenPacks that will be installed by default (all Core ZenPacks). If you would like to avoid installing certain ZenPacks, then remove the corresponding lines from this file and save it. Now you are ready to install Zenoss Core 4.2.5: # ./core-autodeploy.sh

Start A Xen Server VM that Gives "VDI Not Available"

Recently,Xenserver was working abnormally.
During the reboot, the following messages are displayed and
Cold reboot was necessary.  After the cold reboot, some VMs are not started normally.

 File "/opt/xensource/sm/resetvdis.py", line 155, in ?
    reset_vdi(session, vdi_uuid, force)
  File "/opt/xensource/sm/resetvdis.py", line 56, in reset_vdi
    vdi_ref = session.xenapi.VDI.get_by_uuid(vdi_uuid)
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 245, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 149, in xenapi_request
    result = _parse_result(getattr(self, methodname)(*full_params))
  File "/usr/lib/python2.4/site-packages/XenAPI.py", line 219, in _parse_result
    raise Failure(result['ErrorDescription'])
XenAPI.Failure: ['UUID_INVALID', 'VDI', '--force']



Furthermore, we also received the following error message when we tried to boot the server from the Xev Servers host's console:

[root@xenserver-102-90 log]# xe vm-start vm=vm-name
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=VDI 29ee8765-5556-42e1-a53e-362435f03d38 locked], 

 

To fix this issue , I followed the steps listed below   

1.

[root@]# xe vdi-forget uuid=29ee8765-5556-42e1-a53e-362435f03d38
2.
[root@}# xe vdi-list uuid=29ee8765-5556-42e1-a53e-362435f03d38
uuid ( RO)                : 29ee8765-5556-42e1-a53e-362435f03d38
          name-label ( RW): name
    name-description ( RW): name
             sr-uuid ( RO): dc7d9c04-bc32-cf68-d0c9-954a32257c55
        virtual-size ( RO): 322223484
            sharable ( RO): false
           read-only ( RO): false
3.
[root@]# xe vdi-param-set uuid=29ee8765-5556-42e1-a53e-362435f03d38 name-label=new-name
4.
[root@]# xe vdi-list uuid=29ee8765-5556-42e1-a53e-362435f03d38
uuid ( RO)                : 29ee8765-5556-42e1-a53e-362435f03d38
          name-label ( RW): new-name
    name-description ( RW): new-name
             sr-uuid ( RO): dc7d9c04-bc32-cf68-d0c9-954a32257c55
        virtual-size ( RO): 322122547200
            sharable ( RO): false
           read-only ( RO): false
5. On the VMs storage tab, select “Attach” and proceed to select the VDI on the SR.