June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2484) SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2484?page=com.atlassian.jira.plugin... ] Bela Ban reopened JGRP-2484: ---------------------------- Unit tests (e.g. ASYM_ENCRYPT_TestKeyExchange) fail > SSL_KEY_EXCHANGE: Add support for WildFly OpenSSL > ------------------------------------------------- > > Key: JGRP-2484 > URL: https://issues.redhat.com/browse/JGRP-2484 > Project: JGroups > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 5.0.0.Final > > > WildFly OpenSSL provides a high-performance implementation of SSLContext. > While SSL_KEY_EXCHANGE supports passing custom SSLContext instances through the programmatic API, this is not possible through the declarative API. > It should be possible to detect the presence of WildFly OpenSSL on the classpath and use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1192) Onboar to One OCP deploy

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1192: ------------------------------------ Summary: Onboar to One OCP deploy Key: SWSQE-1192 URL: https://issues.redhat.com/browse/SWSQE-1192 Project: Kiali QE Issue Type: Story Reporter: Filip Brychta {color:#000000}Onboard doc - [https://docs.google.com/document/d/1y9zEufKQt279dBFEaOIosEs860lC5KYex-Me1... {color:#000000}One OCP Deploy is a container solution for deploying OpenShift, based on the OCP QE team’s Flexy installer. The development team’s goal is to enable 100% of all QE OCP deployment needs with this solution. It can operate both standalone and integrated in Jenkins as a node.{color} {color:#000000}Based on multiple teams requests, the need to smoothen OCP deployment and most importantly help everyone to save time and get some reliability for deployment QE leadership asked that ALL QE teams use One OCP Deploy to deploy OpenShift. The only exception is a team that uses the IPI installer directly, with no additional tooling. {color}{color:#000000}The deadline for onboarding is Oct 4, 2020. {color}{color:#000000}If you have any questions, or feel that your team should have an additional exception, please be in touch with Sim - [sim@redhat.com|mailto:sim@redhat.com].{color} {color:#000000}One OCP Deploy is ready for GA deployment. Because the self-service documentation isn’t fully completed, the One OCP Deploy team will be happy to help teams with onboarding. We will follow the documentation during initial onboarding, and fill in anything missing so that it should be ready for self-onboarding very quickly. The onboarding documentation, including the Jira project can be found here: {color}[+https://docs.google.com/document/d/1y9zEufKQt279dBFEaOIosEs860lC5KYex-Me1BT_1pU/edit+]{color:#000000} {color} {color:#000000}We’re also asking every team that deploys OpenShift using any method to put the details into the following spreadsheet: {color}[+https://docs.google.com/spreadsheets/d/1R6eDSywHxesaoGBrOZmzzE9s5Woe9PNtUQKDhnANOG4/edit#gid=0+] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2482) Check if the largest thread pool is cluster-size + delta

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2482?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2482. ---------------------------- Resolution: Done > Check if the largest thread pool is cluster-size + delta > -------------------------------------------------------- > > Key: JGRP-2482 > URL: https://issues.redhat.com/browse/JGRP-2482 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > When running UPerf in a cluster of 4, we see {{thread_pool_size_largest=39}}. Verify that MaxOneThreadPerSender works as expected: the largest thread pool size should be 4+delta (timer threads, retransmission): ~6. > It looks as if {{MPerf}} behaves (~6 threads), but {{UPerf}} doesn't: ~26 threads -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2482) Check if the largest thread pool is cluster-size + delta

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2482?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2482: -------------------------------- If a message is internal, it will be passed to the internal thread pool, otherwise to the regular thread pool. This avoids overloading the regular pool with internal messages and thus dropping regular ones. When fibers are mainstream, we should revisit this decision and perhaps eliminate the internal thread pool altogether... > Check if the largest thread pool is cluster-size + delta > -------------------------------------------------------- > > Key: JGRP-2482 > URL: https://issues.redhat.com/browse/JGRP-2482 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Final > > > When running UPerf in a cluster of 4, we see {{thread_pool_size_largest=39}}. Verify that MaxOneThreadPerSender works as expected: the largest thread pool size should be 4+delta (timer threads, retransmission): ~6. > It looks as if {{MPerf}} behaves (~6 threads), but {{UPerf}} doesn't: ~26 threads -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} was: {code:java} Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > Add attached pmml(s) to kie-pmml-regression-tests and verify{code} > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > {code:java} > // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: Add attached pmml(s) to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453 {code:java} {code} was: Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > Add attached pmml(s) to kie-pmml-regression-tests and verify > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > {code:java} > // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453 > {code:java} > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: Add attached pmml(s) to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453 {code} was: Add attached pmml(s) to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453 {code:java} {code} > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > Add attached pmml(s) to kie-pmml-regression-tests and verify > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > {code:java} > // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: Add attached pmml(s) to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication ` // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` was: Add order-approval pmml to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > Add attached pmml(s) to kie-pmml-regression-tests and verify > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > ` > // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: {code:java} Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication ` // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` was: Add attached pmml(s) to kie-pmml-regression-tests and verify 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication ` // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > {code:java} > Add attached pmml(s) to kie-pmml-regression-tests and verify{code} > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > ` > // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5453) Add/Fix pmml(s) to kie-pmml-regression tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5453?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5453: ------------------------------------- Description: {code:java} Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication {code:java} // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} was: {code:java} Add attached pmml(s) to kie-pmml-regression-tests and verify{code} 1) it works *without* model name 2) results are equals to the jpmml evaluator ones 3) outputfields are fixed and correctly populated Also fix/verify all tests with the indication ` // TODO \{gcardosi} TO BE FIXED WITH DROOLS-5453` > Add/Fix pmml(s) to kie-pmml-regression tests > -------------------------------------------- > > Key: DROOLS-5453 > URL: https://issues.redhat.com/browse/DROOLS-5453 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: LinearRegressionSampleWithTransformations.pmml, LogisticRegression.pmml, order-approval.pmml > > > {code:java} > Add attached pmml(s) to kie-pmml-regression-tests and verify{code} > 1) it works *without* model name > 2) results are equals to the jpmml evaluator ones > 3) outputfields are fixed and correctly populated > Also fix/verify all tests with the indication > > {code:java} > // TODO {gcardosi} TO BE FIXED WITH DROOLS-5453{code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020