一、AbiCloud的版本分類:
1、社區版(community):免費
2、企業版(enterprise):需要付費
3、服務提供商版(xSP):需要付費
3、包含虛擬存儲的私有/公有云
- Hypervisors management
- AbiCloud Agents management
- Hypervisors and Agents events
- Virtual Images cloning and bundling.
- Virtual Storage management
- ISC DHCP Server management
這裏是所有用戶存放虛擬鏡像的位置,每個企業都擁有自己的私有 Appliances Repository. 他們可以從公共Repository中下載虛擬鏡像。
Repository 是一個簡單的 NFS 共享文件夾,被 abiCloud 平臺和所有的節點掛載。
Source | Destination | Ports | Description | Mandatory? |
---|---|---|---|---|
Clients | Tomcat Application Server | HTTP:8080 (Configurable) | Access to the platform user interface | Yes |
Tomcat Application Server | MySQL Database Server | TCP:3306 | Access to the relational database | Yes |
Tomcat Application Server | Internet | HTTP:80 | Access from the platform to the Internet to download public images from third parties | Yes |
Tomcat Application Server | Internet | HTTP:ALL | Access from the platform to the Internet to download public images from third parties. Some providers can publish images in different ports | No |
Tomcat Application Server | NFS Server | TCP:32765-32768 TCP:2049 TCP:111 UDP:32765-32768 UDP:2049 UDP:111 | Access from the Tomcat Application Server to the NFS Server: statd has been started so that it only binds to port 32765 for incoming requests and it must answer on port 32766. mountd is forced to bind to port 32767. lockd's module parameters have been set to bind to 32768. nfsd is on port 2049 portmapper is on port 111. Since the NFS Server is visible ONLY in the management network, may be you don't need to configure your firewall for NFS (can be a complex task). It's possible to configure the NFS Server in the Tomcat Application Server. Then, NFS Server should be considered as Tomcat Application Server | No |
Tomcat Application Server | ISC DHCP Server | TCP:7911 | Access from the Tomcat Application Server to the ISC DHCP Server through OMAPI | No |
Tomcat Application Server | Cloud Nodes Servers | TCP:8889 | Access from the Tomcat Application Server to openwsmand component of AIM. It does not apply for VMware ESXi hypervisors. | Yes |
Tomcat Application Server | KVM Cloud Nodes Servers | TCP:8887 | Access from the Tomcat Application Server to KVM Hypervisor. | Yes |
Tomcat Application Server | XEN Cloud Nodes Servers | TCP:16509 | Access from the Tomcat Application Server to XEN Hypervisor | Yes |
Tomcat Application Server | VirtualBox Cloud Nodes Servers | TCP:18083 | Access from the Tomcat Application Server to VirtualBox Hypervisor | Yes |
Tomcat Application Server | VMware ESXi Cloud Nodes Servers | TCP:443 | Access from the Tomcat Application Server to VMware ESXi Hypervisor | Yes |
Cloud Nodes Servers | Tomcat Application Server | HTTP:8080 (Configurable) | Access to the platform from the Cloud Nodes to send information about their status | Yes |
Cloud Nodes Servers | NFS Server | TCP:32765-32768 TCP:2049 TCP:111 UDP:32765-32768 UDP:2049 UDP:111 | Access from the Cloud Nodes Servers to the NFS Server: statd has been started so that it only binds to port 32765 for incoming requests and it must answer on port 32766. mountd is forced to bind to port 32767. lockd's module parameters have been set to bind to 32768. nfsd is on port 2049 portmapper is on port 111. Since the NFS Server is visible ONLY in the management network, may be you don't need to configure your firewall for NFS (can be a complex task) | No |
Cloud Nodes Servers | iSCSI Storage Server | TCP: 3260 | Access from the Cloud Nodes Servers to the iSCSI Storage Servers | Yes |
Cloud Nodes Virtual Machines | ISC DHCP Server | UDP: 68 UDP: 67 | Access from the Cloud Nodes Virtual Machines to the ISC DHCP Server | No |