[
https://issues.jboss.org/browse/AS7-1415?page=com.atlassian.jira.plugin.s...
]
Rostislav Svoboda commented on AS7-1415:
----------------------------------------
It's great that there is work going on with AS7-1011, related tasks and subtasks.
AS7-1011 is blocker for us.
Karel asked me to add some feedback, so here is comment to expected result:
monitor server - standalone
- we need to know current status - down / starting / up / shutting down
monitor server - domain
- Domain Controller (DC) specified by identifier -- down / starting / up / shutting
down
-- without identifier == use 'master'
- Server instances specified by DC/HC identifier + instance name -- down / starting / up
/ shutting down
-- without DC identifier == use 'master'
deployment status - standalone
- we need to know current status - not deployed / deploying / running / undeploying /
undeployed
deployment status - domain
- On DC level (without DC identifer == use 'master')
-- doesn't exist / prepared for deployment on server instances / deploying / running
/ undeploying / undeployed
-- doesn't matter on how many instances it is deployed
- On server instance level (specified by DC/HC identier + instance name, without DC
identifer == use 'master')
-- not deployed / deploying / running / undeploying / undeployed
Allow Arquillian tests to monitor server and deployment status
explicitly
-------------------------------------------------------------------------
Key: AS7-1415
URL:
https://issues.jboss.org/browse/AS7-1415
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Affects Versions: 7.0.0.CR1
Reporter: Karel Piwko
Assignee: Andrew Rubinger
Deployment can be checked via management API using ArquillianServiceObserver at least.
The AS monitoring should use management API as well. These objects will be fully
accessible in the testsuite.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira