[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney resolved SWSQE-107.
--------------------------------
Resolution: Done
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline (Production=PR-Testing + Overnight-Testing).
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney commented on SWSQE-107:
------------------------------------
Team selected b21 as the Production Openshift cluster.
We will migrate our testing and prototyping off of b21 and on to other clusters b111/b12/OSOOS-Clusters
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline (Production=PR-Testing + Overnight-Testing).
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Kevin Earls moved KIALI-468 to SWSQE-113:
-----------------------------------------
Project: Kiali QE (was: Kiali)
Key: SWSQE-113 (was: KIALI-468)
Workflow: classic default workflow (was: SWS Workflow)
> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
> Key: SWSQE-113
> URL: https://issues.jboss.org/browse/SWSQE-113
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Filip Brychta
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet.
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2421) Unexpected response from rule engine for windowing rules
by Bishnu Shankar Pandey (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2421?page=com.atlassian.jira.plugi... ]
Bishnu Shankar Pandey updated DROOLS-2421:
------------------------------------------
Attachment: DroolsTest.zip
> Unexpected response from rule engine for windowing rules
> --------------------------------------------------------
>
> Key: DROOLS-2421
> URL: https://issues.jboss.org/browse/DROOLS-2421
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Bishnu Shankar Pandey
> Assignee: Mario Fusco
> Attachments: DroolsTest.zip
>
>
> Here the sample code of my window rule :
> rule "Sliding window test1"
> agenda-group "g0"
> when
> exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A0") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A0") over window:time(2m) , sum($t))
> then
> globalList.add("2 Minute Sum of parameter2 of Source A0 is " + $number );
> end
> rule "Sliding window test2"
> agenda-group "g0"
> when
> exists Fact( (facts["parameter2"] ) != null && facts["source"] == "A1") && $number: Number() from accumulate(Fact(facts["parameter2"] != null && $t : Double.valueOf(facts["parameter2"]) && facts["source"] == "A1") over window:time(2m) , sum($t))
> then
> globalList.add("2 Minute Sum of parameter2 of Source A1 is " + $number );
> end
> I am sending request from 2 different sources. I am getting response as 0.0 after some time. I check the values in the working memory by using collect as List for the parameter values. I have found that the previous values got deleted when the response is 0.0. I need immediate help.
> Some important info:
> Fact is the class Object and it has a Hashmap(facts) as class variable. The factmap contains the variable name as key and its value as variable value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-112) Document configuration of openshift production cluster
by Filip Brychta (JIRA)
Filip Brychta created SWSQE-112:
-----------------------------------
Summary: Document configuration of openshift production cluster
Key: SWSQE-112
URL: https://issues.jboss.org/browse/SWSQE-112
Project: Kiali QE
Issue Type: Task
Reporter: Filip Brychta
Assignee: Michael Foley
We need mojo page with full description of our openshift production cluster which should include:
* used blades
* OS version
* description of all necessary accounts and permissions (for jenkins, jenkins slaves,...)
* ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months