[JBoss JIRA] (RTGOV-164) Deploying the wars
by Nick Cross (JIRA)
Nick Cross created RTGOV-164:
--------------------------------
Summary: Deploying the wars
Key: RTGOV-164
URL: https://issues.jboss.org/browse/RTGOV-164
Project: RTGov (Run Time Governance)
Issue Type: Enhancement
Affects Versions: 1.0.0.M4
Reporter: Nick Cross
Assignee: Gary Brown
Fix For: 1.0.0.M5
Allow those artifacts that generate war files (content/epn, content/acs, release/jbossas/war-*) to deploy i.e. remove maven-deploy-plugin skip=true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-163) Simulation support
by Gary Brown (JIRA)
Gary Brown created RTGOV-163:
--------------------------------
Summary: Simulation support
Key: RTGOV-163
URL: https://issues.jboss.org/browse/RTGOV-163
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1
Provide simulation capabilities related to an end-to-end SOA implemented business flow.
Source information for the simulation could be savara scenarios, or information captured from previous executions of the business transaction.
Purpose will be to profile how individual parts of the system react under different load with different performance profiles. Where some parts of the system are resource constrained, this information should also be recorded, to understand where bottlenecks may occur. If those resources are people, then need to model the groups/sizes/calendars etc.
If there is a financial consequence of the business transaction, this should be monitored, to enable different simulation profiles to reflect the impact on the financial situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-160) Specify interface type in SOA activity events
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-160?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-160:
-----------------------------
Summary: Specify interface type in SOA activity events (was: Report activity events for switchyard bindings)
> Specify interface type in SOA activity events
> ---------------------------------------------
>
> Key: RTGOV-160
> URL: https://issues.jboss.org/browse/RTGOV-160
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Currently when an exchange is processed, where the consumer or provider is a binding, then only activity events for the receiving or sending side is created. However the serviceType is currently defined by the service component.
> Once switchyard exposes the interface type via the consumer/provider metadata, then the activity events should include the interface type of the binding, rather than the internal interface used by the implementing component.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-162) SLA report based on historic analysis of Situations
by Gary Brown (JIRA)
Gary Brown created RTGOV-162:
--------------------------------
Summary: SLA report based on historic analysis of Situations
Key: RTGOV-162
URL: https://issues.jboss.org/browse/RTGOV-162
Project: RTGov (Run Time Governance)
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M5
Need to determine what information should be stored in the Situation to enable a report to be compiled based on service performance and availability.
The criteria for what constitutes a violation of a particular customer's SLA needs to be defined. For example, the SLAs may only apply within particular day/time periods - which will also need to take into account timezones.
Need to see whether this per customer information can be stored in SRAMP repo, and also reported via Polymita, as requires further analysis of the underlying information - and possibly needs to be presented in a tabular form.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-151) Persist event processor derived results
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-151?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-151.
------------------------------
Resolution: Done
> Persist event processor derived results
> ---------------------------------------
>
> Key: RTGOV-151
> URL: https://issues.jboss.org/browse/RTGOV-151
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Support the ability to persist results derived from event processor networks.
> The initial usecase is situations, where service level agreement based analysis may detect violations. Historic analysis of the violations may be required for reporting purposes.
> However there may be other cases where facts derived from this event analysis may be required in historic contexts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RTGOV-153) Define ootb EPN for persisting Situation events
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-153?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-153.
------------------------------
Resolution: Done
> Define ootb EPN for persisting Situation events
> -----------------------------------------------
>
> Key: RTGOV-153
> URL: https://issues.jboss.org/browse/RTGOV-153
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> Use the JPA event processor to persist Situation events in a database.
> This should be defined in a separate EPN, to enable other user supplied EPNs that create Situation objects to also publish them to a well-defined subject to be picked up by the common Situation persisting EPN.
> This means that the current SLA monitor example would need to be updated to distribute the Situation derived events to this well-defined subject.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months