[JBoss JIRA] (RTGOV-654) RT-Gov Analytics not accessible on https due to hardcoded protocol for ElasticSearch URL
by Martin Weiler (JIRA)
Martin Weiler created RTGOV-654:
-----------------------------------
Summary: RT-Gov Analytics not accessible on https due to hardcoded protocol for ElasticSearch URL
Key: RTGOV-654
URL: https://issues.jboss.org/browse/RTGOV-654
Project: RTGov (Run Time Governance)
Issue Type: Bug
Affects Versions: 2.0.0.Final
Environment: RT-Gov 2.0.0 on FSW 6.0.0
Reporter: Martin Weiler
Assignee: Gary Brown
Access via http is working fine (http://<host>:<port>/rtgov-ui/analytics.html#/dashboard) but with https (https://<host>:<port>/rtgov-ui/analytics.html#/dashboard) we run into the following error:
{noformat}
Error Could not reach http://<host>:<port>/rtgov-ui/elasticsearch/_nodes. If you are using a proxy, ensure it is configured correctly
{noformat}
It seems that it is internally redirecting https request to http protocol with https port.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (RTGOV-649) Status handling for Situations
by Werner Müller (JIRA)
[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ]
Werner Müller commented on RTGOV-649:
-------------------------------------
Great. Thanks a lot.
> Status handling for Situations
> ------------------------------
>
> Key: RTGOV-649
> URL: https://issues.jboss.org/browse/RTGOV-649
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Werner Müller
> Assignee: Gary Brown
> Fix For: 2.1.0.Beta2
>
>
> This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed:
> - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED:
> Either remove other values, or provide means to configure the values.
> - The default entry for the Status filter on the Situations page shall be (the new value) OPEN:
> This includes all Status values other than RESOLVED.
>
> - A Situation's Status should be changed only programmatically (see below):
> Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration.
>
> - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'.
> (This is to be consistent with the resubmit behaviour as defined below.)
> - The initial state of a (root) Situation is UNRESOLVED.
> When a Situation is resubmitted:
> (1) 'assignedTo' is set to the current user (overriding the current value)
> (2a) If no failure is encountered (no child situation is created),
> the Status is changed to RESOLVED.
> (2b) If a failure is encountered (and a child situation is created),
> the Status is changed to IN_PROGRESS.
> - A Situation in Status RESOLVED must not be resubmitted anymore:
> (1) The Resubmit button on the "Message" tab is disabled.
> (2) The Situation is excluded from a bulk resubmit.
>
> As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (RTGOV-649) Status handling for Situations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-649:
----------------------------------
No problem - the link is: http://downloads.jboss.org/overlord/tmp/overlord-rtgov-2.0.2-SNAPSHOT-140...
> Status handling for Situations
> ------------------------------
>
> Key: RTGOV-649
> URL: https://issues.jboss.org/browse/RTGOV-649
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Werner Müller
> Assignee: Gary Brown
> Fix For: 2.1.0.Beta2
>
>
> This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed:
> - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED:
> Either remove other values, or provide means to configure the values.
> - The default entry for the Status filter on the Situations page shall be (the new value) OPEN:
> This includes all Status values other than RESOLVED.
>
> - A Situation's Status should be changed only programmatically (see below):
> Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration.
>
> - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'.
> (This is to be consistent with the resubmit behaviour as defined below.)
> - The initial state of a (root) Situation is UNRESOLVED.
> When a Situation is resubmitted:
> (1) 'assignedTo' is set to the current user (overriding the current value)
> (2a) If no failure is encountered (no child situation is created),
> the Status is changed to RESOLVED.
> (2b) If a failure is encountered (and a child situation is created),
> the Status is changed to IN_PROGRESS.
> - A Situation in Status RESOLVED must not be resubmitted anymore:
> (1) The Resubmit button on the "Message" tab is disabled.
> (2) The Situation is excluded from a bulk resubmit.
>
> As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (RTGOV-649) Status handling for Situations
by Werner Müller (JIRA)
[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ]
Werner Müller commented on RTGOV-649:
-------------------------------------
Hi Gary,
I'm having some problems with the build here. I guess it's faster if you could create the build and post it somewhere. I really would appreciate that.
> Status handling for Situations
> ------------------------------
>
> Key: RTGOV-649
> URL: https://issues.jboss.org/browse/RTGOV-649
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Werner Müller
> Assignee: Gary Brown
> Fix For: 2.1.0.Beta2
>
>
> This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed:
> - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED:
> Either remove other values, or provide means to configure the values.
> - The default entry for the Status filter on the Situations page shall be (the new value) OPEN:
> This includes all Status values other than RESOLVED.
>
> - A Situation's Status should be changed only programmatically (see below):
> Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration.
>
> - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'.
> (This is to be consistent with the resubmit behaviour as defined below.)
> - The initial state of a (root) Situation is UNRESOLVED.
> When a Situation is resubmitted:
> (1) 'assignedTo' is set to the current user (overriding the current value)
> (2a) If no failure is encountered (no child situation is created),
> the Status is changed to RESOLVED.
> (2b) If a failure is encountered (and a child situation is created),
> the Status is changed to IN_PROGRESS.
> - A Situation in Status RESOLVED must not be resubmitted anymore:
> (1) The Resubmit button on the "Message" tab is disabled.
> (2) The Situation is excluded from a bulk resubmit.
>
> As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (RTGOV-649) Status handling for Situations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-649.
------------------------------
Fix Version/s: 2.1.0.Beta2
Resolution: Done
Marking resolved - but if any issues are found either re-open or create a bug report.
> Status handling for Situations
> ------------------------------
>
> Key: RTGOV-649
> URL: https://issues.jboss.org/browse/RTGOV-649
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Werner Müller
> Assignee: Gary Brown
> Fix For: 2.1.0.Beta2
>
>
> This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed:
> - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED:
> Either remove other values, or provide means to configure the values.
> - The default entry for the Status filter on the Situations page shall be (the new value) OPEN:
> This includes all Status values other than RESOLVED.
>
> - A Situation's Status should be changed only programmatically (see below):
> Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration.
>
> - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'.
> (This is to be consistent with the resubmit behaviour as defined below.)
> - The initial state of a (root) Situation is UNRESOLVED.
> When a Situation is resubmitted:
> (1) 'assignedTo' is set to the current user (overriding the current value)
> (2a) If no failure is encountered (no child situation is created),
> the Status is changed to RESOLVED.
> (2b) If a failure is encountered (and a child situation is created),
> the Status is changed to IN_PROGRESS.
> - A Situation in Status RESOLVED must not be resubmitted anymore:
> (1) The Resubmit button on the "Message" tab is disabled.
> (2) The Situation is excluded from a bulk resubmit.
>
> As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (RTGOV-649) Status handling for Situations
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-649?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-649:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/291, https://github.com/Governance/rtgov/pull/292 (was: https://github.com/Governance/rtgov/pull/291)
> Status handling for Situations
> ------------------------------
>
> Key: RTGOV-649
> URL: https://issues.jboss.org/browse/RTGOV-649
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Werner Müller
> Assignee: Gary Brown
>
> This relates to https://issues.jboss.org/browse/RTGOV-645. To support the Resubmit feature, the handling of the Situation's Status field shall be changed:
> - Only 3 Status values shall be available: UNRESOLVED, IN PROGRESS, RESOLVED:
> Either remove other values, or provide means to configure the values.
> - The default entry for the Status filter on the Situations page shall be (the new value) OPEN:
> This includes all Status values other than RESOLVED.
>
> - A Situation's Status should be changed only programmatically (see below):
> Either remove the status change buttons on the "Details" tab or provide means to hide them by configuration.
>
> - The "Assign" button shall be available all the time. It potentially overwrites an existing value for 'assignedTo'.
> (This is to be consistent with the resubmit behaviour as defined below.)
> - The initial state of a (root) Situation is UNRESOLVED.
> When a Situation is resubmitted:
> (1) 'assignedTo' is set to the current user (overriding the current value)
> (2a) If no failure is encountered (no child situation is created),
> the Status is changed to RESOLVED.
> (2b) If a failure is encountered (and a child situation is created),
> the Status is changed to IN_PROGRESS.
> - A Situation in Status RESOLVED must not be resubmitted anymore:
> (1) The Resubmit button on the "Message" tab is disabled.
> (2) The Situation is excluded from a bulk resubmit.
>
> As already stated in the requirements for RTGOV-645, assignedTo and Status shall have the same value for all Situations in a "resubmit tree".
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months
[JBoss JIRA] (ARTIF-675) Define new "service" model
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-675:
---------------------------------
Summary: Define new "service" model
Key: ARTIF-675
URL: https://issues.jboss.org/browse/ARTIF-675
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Define a new, generic model to better encapsulate "services", discovery, and re-use.
Ideas (from various sources):
- Provides a catalog of information, what services exist and are available for use
- Presents the condition of the service lifecycle is eg. Implemented, testing, advised against, etc.
- Provides information about the version of the services
- Allows you to record and retrieve multiple versions of the same service
- Allows you to dynamically refer to the latest version of the service
- Allows dynamically at runtime to search and select end-point chosen service
- Collects information who and what services are used
- Provides information that services are repeatedly used and which are not
- Determining the impact of changes the services to existing dependent services
- Providing information to consumers of the services about ongoing or planned changes to of the services
- Automatically publish the new services added to the Bus in the registry service
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 2 months