July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7973: ------------------------------------------- Based on [YouTube presentation|https://www.youtube.com/watch?v=BaPMFZZ5lsc]: A bit of a history: * The proper name is Service Broker API. It's a successor of Cloud Foundry Service Broker API Glossary: * A {{Service}} is just a capability or class that has a plan (a tier of that service). E.g. {{Database as a Service}}. * A {{Service Instance}} is provisioned instance of that capability. E.g. {{My Database}}. * A {{Binding}} is a relationship between a service instance and an application. E.g. Credentials for an application to access a {{My Database}}. [Service Catalog|https://github.com/kubernetes-incubator/service-catalog]: * Currently at Beta stage * The Service Catalog requires: ** Service Broker to talk to. It is defined by URL and optional Secret with credentials. The Catalog may operate on many Brokers at the same time. ** The Catalog connects to the Broker, downloads a list of Services and creates a {{Service Class}} based on it. ** In order to provision any of those Services we create an {{Instance}} Kubernetes resource ({{Service Class}}, {{Plan}} and {{Parameters}}). ** After the instance is provisioned we create a {{Binding]} (a provisioned instance, a secret to inject credentials to, and {{PodPresetTemplate}}). Service Catalog integrations done through Service Broker API: * OpenShift Templates - We will be able to use OpenShift templates inside Kubernetes * Ansible - * Messaging as a Service - it uses [En Masse|https://enmasseproject.github.io] How to integrate with Service Brokers API? * The easiest way - write an OpenShift template * If this is not enough, write Ansible script * If you want full control, write your own Broker using the [SDK|https://github.com/openshift/open-service-broker-sdk] How to use Ansible Service Broker? * Supports reusing existing images (both standard and S2I) * Ansible Service Broker boostraps a container with Ansible Execution Environment and loads playbooks we defined. * A user can define 4 playbooks (1 per each event: provision, deprovision, bind, unbind). Each playbook may leverage {{oc}} command tool to do its stuff. * We can provision multiple services using playbooks (e.g. a web application with a database and a cache, everything nicely configured). > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8039) Remove action menu for cache container in standalone mode

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-8039?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-8039: -------------------------------------- Status: Open (was: New) > Remove action menu for cache container in standalone mode > --------------------------------------------------------- > > Key: ISPN-8039 > URL: https://issues.jboss.org/browse/ISPN-8039 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.1.0.CR1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.1.0.Final > > > We should not display actions burger menu for cache containers page in standalone mode as those actions are not available in standalone mode -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8039) Remove action menu for cache container in standalone mode

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-8039: ----------------------------------------- Summary: Remove action menu for cache container in standalone mode Key: ISPN-8039 URL: https://issues.jboss.org/browse/ISPN-8039 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.1.0.CR1 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Priority: Minor Fix For: 9.1.0.Final We should not display actions burger menu for cache containers page in standalone mode as those actions are not available in standalone mode -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7971: ------------------------------------------- [~sebastian.laskawiec] What kind of warning did you have in mind? Once a user logs in? > Display a warning that changes in standalone mode are not persisted > ------------------------------------------------------------------- > > Key: ISPN-7971 > URL: https://issues.jboss.org/browse/ISPN-7971 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > > The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic edited comment on ISPN-7971 at 7/10/17 7:07 AM: -------------------------------------------------------------------- [~sebastian.laskawiec] What kind of warning did you have in mind? A dialog displayed once a user logs in for the first time? was (Author: vblagojevic): [~sebastian.laskawiec] What kind of warning did you have in mind? Once a user logs in? > Display a warning that changes in standalone mode are not persisted > ------------------------------------------------------------------- > > Key: ISPN-7971 > URL: https://issues.jboss.org/browse/ISPN-7971 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > > The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8038) java.lang.ClassCastException with compatibility mode and text content

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8038?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-8038: --------------------------------------- Assignee: Gustavo Fernandes > java.lang.ClassCastException with compatibility mode and text content > --------------------------------------------------------------------- > > Key: ISPN-8038 > URL: https://issues.jboss.org/browse/ISPN-8038 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.1.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.1.0.Final > > > Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: > {noformat} > org.infinispan.client.hotrod.exceptions.HotRodClientException: > Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8038) java.lang.ClassCastException with compatibility mode and text content

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8038?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8038: ------------------------------------ Affects Version/s: 9.1.0.Alpha1 (was: 9.1.0.CR1) > java.lang.ClassCastException with compatibility mode and text content > --------------------------------------------------------------------- > > Key: ISPN-8038 > URL: https://issues.jboss.org/browse/ISPN-8038 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.1.0.Alpha1 > Reporter: Gustavo Fernandes > Fix For: 9.1.0.Final > > > Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: > {noformat} > org.infinispan.client.hotrod.exceptions.HotRodClientException: > Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8038) java.lang.ClassCastException with compatibility mode and text content

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8038?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-8038: ----------------------------------------- This is a regression introduced by the rework of the rest server > java.lang.ClassCastException with compatibility mode and text content > --------------------------------------------------------------------- > > Key: ISPN-8038 > URL: https://issues.jboss.org/browse/ISPN-8038 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.1.0.Alpha1 > Reporter: Gustavo Fernandes > Fix For: 9.1.0.Final > > > Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: > {noformat} > org.infinispan.client.hotrod.exceptions.HotRodClientException: > Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7991) Improve Compatibility between Rest and HotRod for text content

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7991?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-7991 at 7/10/17 6:26 AM: ------------------------------------------------------------------ The custom marshaller deployment works for 8.2.x and 9.0.x, but not for master. I'll open another JIRA to fix it. https://issues.jboss.org/browse/ISPN-8038 was (Author: gustavonalle): The custom marshaller deployment works for 8.2.x and 9.0.x, but not for master. I'll open another JIRA to fix it. > Improve Compatibility between Rest and HotRod for text content > -------------------------------------------------------------- > > Key: ISPN-7991 > URL: https://issues.jboss.org/browse/ISPN-7991 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 8.2.7.Final, 9.0.3.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 8.2.8.Final > > > When dealing with text based content, writing via Hot Rod and reading via Rest works fine out of the box, but not the other way around: it requires deploying a modified StringMarshaller in the server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8038) java.lang.ClassCastException with compatibility mode and text content

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8038?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8038: ------------------------------------ Description: Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: {noformat} org.infinispan.client.hotrod.exceptions.HotRodClientException: Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String {noformat} was: Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: {noformat} org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String {noformat} > java.lang.ClassCastException with compatibility mode and text content > --------------------------------------------------------------------- > > Key: ISPN-8038 > URL: https://issues.jboss.org/browse/ISPN-8038 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.1.0.CR1 > Reporter: Gustavo Fernandes > Fix For: 9.1.0.Final > > > Setting compat mode with a string marshaller in the server, the same marshaller in the hot rod client, writing text content via rest and reading via Hot Rod yields: > {noformat} > org.infinispan.client.hotrod.exceptions.HotRodClientException: > Request for messageId=3 returned server error (status=0x85): java.lang.ClassCastException: [B cannot be cast to java.lang.String > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017