[JBoss JIRA] (ISPN-8401) Investigate if we can create ServiceAccount and Role Binding in OpenShift Online
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8401?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-8401:
-------------------------------------------
On [OpenShift Online Staging|https://console.free-stg.openshift.com/console] environment creating {{RoleBinding}} is prohibited.
{code}
make test-ephemeral
oc process infinispan-ephemeral | oc create -f -
serviceaccount "infinispan-app" created
secret "infinispan-app" created
service "infinispan-app-http" created
service "infinispan-app-hotrod" created
service "infinispan-app-management" created
configmap "infinispan-app-configuration" created
route "infinispan-app-management" created
deploymentconfig "infinispan-app" created
Error from server (Forbidden): rolebindings "infinispan-app-view" is forbidden: rolebindings to ServiceAccount "infinispan-app" are not allowed in project "slaskawi"
make: *** [Makefile:47: test-ephemeral] Error 1
{code}
An interesting thing is that I can create it by hand:
{code}
oc policy add-role-to-user view system:serviceaccount:$(oc project -q):my-new-sa -n $(oc project -q)
{code}
> Investigate if we can create ServiceAccount and Role Binding in OpenShift Online
> --------------------------------------------------------------------------------
>
> Key: ISPN-8401
> URL: https://issues.jboss.org/browse/ISPN-8401
> Project: Infinispan
> Issue Type: Task
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
>
> The {{KUBE_PING}} JGroups protocol (the one that performs discovery) queries Kubernetes API to obtain a list of {{Pods}}. This in turn requires {{view}} permissions (see [Service Accounts on OpenShift User Guide|https://docs.openshift.com/container-platform/3.6/dev_guide/service...]) and a binding object (it's called {{RoleBinding}} and it provides mapping between {{ServiceAccout}} that is used by the {{Pod}} and {{view}} permissions).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services
by Emmanuel Bernard (JIRA)
[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ]
Emmanuel Bernard commented on ISPN-8400:
----------------------------------------
[~ryanemerson] with reads/writes not accepted once the split brain is detected, do you think that prefer non null is in anyway shape or form better than remove all conflicting entries ?
My concern with prefer non null is that it can resurrect old entries it seems.
> Adjust merge policies for JDG Online Services
> ---------------------------------------------
>
> Key: ISPN-8400
> URL: https://issues.jboss.org/browse/ISPN-8400
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
>
> Both Shared Memory and Caching Service require custom merge policies.
> In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ISPN-8344) DSL queries filtering only on type are always executed without index
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-8344?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-8344:
--------------------------------
Fix Version/s: 9.2.0.Alpha2
9.1.2.Final
(was: 9.2.0.Beta1)
(was: 9.1.3.Final)
> DSL queries filtering only on type are always executed without index
> --------------------------------------------------------------------
>
> Key: ISPN-8344
> URL: https://issues.jboss.org/browse/ISPN-8344
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 9.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.4.Final, 8.2.9.Final, 9.1.2.Final, 9.2.0.Alpha2
>
>
> This happens if the WHERE clause is empty or a tautology (true). In this case the query is wrongly executed unindexed even though the index should be at least used for filtering on type.
> The query
> {code}
> FROM org.infinispan.test.Person
> {code}
> or
> {code}
> qf.from(Person.class).build();
> {code}
> is such a case
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months