[JBoss JIRA] (WFLY-10172) Add support for JSR-375 EE Security as required for Java EE 8
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10172?page=com.atlassian.jira.plugin... ]
Stuart Douglas moved EAP7-980 to WFLY-10172:
--------------------------------------------
Project: WildFly (was: EAP 7 Planning Pilot)
Key: WFLY-10172 (was: EAP7-980)
Issue Type: Feature Request (was: Requirement)
Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0)
Component/s: Security
(was: Security)
Target Release: (was: 7.2.0.GA)
> Add support for JSR-375 EE Security as required for Java EE 8
> -------------------------------------------------------------
>
> Key: WFLY-10172
> URL: https://issues.jboss.org/browse/WFLY-10172
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Labels: JavaEE8
>
> This depends on EAP7-649
> In general at the outset this RFE should be the minimal required on top of EAP7-649 to be compliant with EE security most likely using a much from the RI as possible meaning this feature should be more about integration. If issues are found using the RI we can always choose to address those later.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo edited comment on SWSQE-116 at 4/4/18 4:38 PM:
-----------------------------------------------------------------------
For 1,2 and 3, we have viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart)
I think SWSQE-111 can solve item 4.
Any other thoughts [~fbrychta]?
was (Author: gbaufake):
For 1,2 and 3, we have @viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart)
I think SWSQE-111 can solve item 4.
Any other thoughts [~fbrychta]?
> Reinstall openshift production cluster
> --------------------------------------
>
> Key: SWSQE-116
> URL: https://issues.jboss.org/browse/SWSQE-116
> Project: Kiali QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Guilherme Baufaker Rêgo
>
> Currently there are following problems with our OS cluster:
> * docker on nodes is using loopback devices which is strongly discouraged for production use
> * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs"
> * different root passwords
> We need to:
> # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade)
> # reinstall RHELs with recommended partitions
> # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/...
> # install OS 3.9
> # create mojo documentation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo edited comment on SWSQE-116 at 4/4/18 4:38 PM:
-----------------------------------------------------------------------
For 1,2 and 3, we have @viet quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart)
I think SWSQE-111 can solve item 4.
Any other thoughts [~fbrychta]?
was (Author: gbaufake):
For 1,2 and 3, we have Viet's quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart)
I think SWSQE-111 can solve item 4.
Any other thoughts [~fbrychta]?
> Reinstall openshift production cluster
> --------------------------------------
>
> Key: SWSQE-116
> URL: https://issues.jboss.org/browse/SWSQE-116
> Project: Kiali QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Guilherme Baufaker Rêgo
>
> Currently there are following problems with our OS cluster:
> * docker on nodes is using loopback devices which is strongly discouraged for production use
> * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs"
> * different root passwords
> We need to:
> # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade)
> # reinstall RHELs with recommended partitions
> # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/...
> # install OS 3.9
> # create mojo documentation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-116) Reinstall openshift production cluster
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-116?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo commented on SWSQE-116:
-----------------------------------------------
For 1,2 and 3, we have Viet's quickstart script that I've updated to Openshift 3.9 (I don't have too much experience using kickstart so I might need some help with RHEL with quickstart)
I think SWSQE-111 can solve item 4.
Any other thoughts [~fbrychta]?
> Reinstall openshift production cluster
> --------------------------------------
>
> Key: SWSQE-116
> URL: https://issues.jboss.org/browse/SWSQE-116
> Project: Kiali QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Guilherme Baufaker Rêgo
>
> Currently there are following problems with our OS cluster:
> * docker on nodes is using loopback devices which is strongly discouraged for production use
> * small partition for imagefs and nodefs which is causing issues "The node was low on resource: imagefs"
> * different root passwords
> We need to:
> # investigate recommended partitioning for production OS clusters (also think about RAID versions available on each blade)
> # reinstall RHELs with recommended partitions
> # Configuring Docker Storage as described in https://docs.openshift.com/container-platform/3.9/install_config/install/...
> # install OS 3.9
> # create mojo documentation
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2451) Manage empty relation cell as null
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-2451:
--------------------------------------
Summary: Manage empty relation cell as null
Key: DROOLS-2451
URL: https://issues.jboss.org/browse/DROOLS-2451
Project: Drools
Issue Type: Enhancement
Components: DMN Editor
Reporter: Matteo Mortari
Assignee: Michael Anstis
Following [DROOLS-2439] convention to adopt an empty cell inside a Relation has the same semantic of a null LiteralExpression.
The wb converters/marshaller should take this into account while transforming from the kie-dmn-model to the WB model.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (SWSQE-93) Create internal git repository
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-93?page=com.atlassian.jira.plugin.s... ]
Guilherme Baufaker Rêgo commented on SWSQE-93:
----------------------------------------------
In my opinion: I prefer Gitlab, it is possible to use the same resources that we have on Github
> Create internal git repository
> ------------------------------
>
> Key: SWSQE-93
> URL: https://issues.jboss.org/browse/SWSQE-93
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
>
> We need internal git repository for things like:
> * dockerfiles for jenkins docker slaves
> * openshift templates
> * installation scripts
> Part of this task is to investigate options we have for internal git repositories (there is not just one)
--
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 Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo resolved SWSQE-113.
-------------------------------------------
Resolution: Done
> 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: Guilherme Baufaker Rêgo
>
> 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] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images
by Guilherme Baufaker Rêgo (JIRA)
[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo edited comment on SWSQE-113 at 4/4/18 1:12 PM:
-----------------------------------------------------------------------
In order to document things for elastic search
- Executed {code:shell} oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins {code}
- Executed {code:shell} oc adm policy add-role-to-user cluster-admin system:serviceaccount:jaeger-test:jenkins {code}
- Disabled Selinux ({code:shell} vi /etc/selinux/config{code} Set to disable then reboot
- And executed {code:shell} sudo sysctl -w vm.max_map_count=262144 {code}
was (Author: gbaufake):
In order to document things for elastic search
- Executed {code:shell} oc adm policy add-role-to-user admin system:serviceaccount:jaeger-test:jenkins {code}
- Executed {code:shell} oc adm policy add-role-to-user cluster-admin system:serviceaccount:jaeger-test:jenkins {code}
- Disabled Selinux
- And executed {code:shell} sudo sysctl -w vm.max_map_count=262144 {code}
> 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: Guilherme Baufaker Rêgo
>
> 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