Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: Abiquo-1.6.0
-
Fix Version/s: Abiquo-1.7.0
-
Component/s: Server
-
Labels:None
Description
Now the script abiquoServerCheckState.sh always assume that the remote services are in localhost.
Since the actual recommended architecture is remote services in other machine than server, should be logical separate these scripts:
1) abiquoServerCheckState should include:
-JNDI
-Server database credentials
-MTA
-SELinux
-Event sync address
-...
2) abiquoRScheckState should include:
-BPM database credentials
-BPM external dependencies
-NFS (should be taken in /opt/abiquo/config/am.xml)
-Samba
-DHCP
-AM, virtualfactory, Monitor Manager, storage system monitor, nodecollector...
Since the actual recommended architecture is remote services in other machine than server, should be logical separate these scripts:
1) abiquoServerCheckState should include:
-JNDI
-Server database credentials
-MTA
-SELinux
-Event sync address
-...
2) abiquoRScheckState should include:
-BPM database credentials
-BPM external dependencies
-NFS (should be taken in /opt/abiquo/config/am.xml)
-Samba
-DHCP
-AM, virtualfactory, Monitor Manager, storage system monitor, nodecollector...
1. abiquoServerCheckState
2. abiquoRSCheckState
3. abiquoV2VCheckState
Rational:
Abiquo components can span 3 or more physical host in a production environment (1 server, 1 rs, 1 V2V). Each script should go into the right server.
Some services, such as the NFS, should be checked by more than one script. i.e. NFS should be checked by all of them, the abiquoRS, the abiquoServer and the abiquoV2V check scripts.
We should write a formal specification for this sanity check scripts IMHO, something like:
http://community.abiquo.com/display/Abiquo/Sanity+Check+Scripts+-+Requirements+SPEC
In particular:
1. Which scripts do we need.
2. Where should they be installed.
3. What is covered by each script.
4. How do we perform each of the checks.
My 2cents.