August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10462) Drop the infinispan-cloud module and merge config files to core

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10462?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10462: ----------------------------------- Status: Open (was: New) > Drop the infinispan-cloud module and merge config files to core > --------------------------------------------------------------- > > Key: ISPN-10462 > URL: https://issues.jboss.org/browse/ISPN-10462 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR1 > > > The infinispan-cloud module contains three configuration files which can be merged to core. > Such configurations have optional dependencies on specific jgroups modules. These should be called out in the configuration comments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10462) Drop the infinispan-cloud module and merge config files to core

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10462: -------------------------------------- Summary: Drop the infinispan-cloud module and merge config files to core Key: ISPN-10462 URL: https://issues.jboss.org/browse/ISPN-10462 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR1 The infinispan-cloud module contains three configuration files which can be merged to core. Such configurations have optional dependencies on specific jgroups modules. These should be called out in the configuration comments. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10461) Server creates sslcontext even without an identity

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10461?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10461: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7184 > Server creates sslcontext even without an identity > -------------------------------------------------- > > Key: ISPN-10461 > URL: https://issues.jboss.org/browse/ISPN-10461 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR1 > > > If the server has a security realm without a server identity, the server instantiates a SSLContext and configures the endpoints to use it. This makes unencrypted access impossible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10461) Server creates sslcontext even without an identity

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10461?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10461: ----------------------------------- Status: Open (was: New) > Server creates sslcontext even without an identity > -------------------------------------------------- > > Key: ISPN-10461 > URL: https://issues.jboss.org/browse/ISPN-10461 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR1 > > > If the server has a security realm without a server identity, the server instantiates a SSLContext and configures the endpoints to use it. This makes unencrypted access impossible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10461) Server creates sslcontext even without an identity

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10461: -------------------------------------- Summary: Server creates sslcontext even without an identity Key: ISPN-10461 URL: https://issues.jboss.org/browse/ISPN-10461 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.0.0.Beta5 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR1 If the server has a security realm without a server identity, the server instantiates a SSLContext and configures the endpoints to use it. This makes unencrypted access impossible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10439) Exposing endpoints info via REST

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10439?page=com.atlassian.jira.plugin... ] Work on ISPN-10439 started by Gustavo Fernandes. ------------------------------------------------ > Exposing endpoints info via REST > --------------------------------- > > Key: ISPN-10439 > URL: https://issues.jboss.org/browse/ISPN-10439 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > > Exposes serverNG endpoints information via REST: > Type: Hot Rod/REST/Memcached > Port: 11222 > Security: authentication/encryption -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10439) Exposing endpoints info via REST

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10439?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10439: ------------------------------------- Status: Open (was: New) > Exposing endpoints info via REST > --------------------------------- > > Key: ISPN-10439 > URL: https://issues.jboss.org/browse/ISPN-10439 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > > Exposes serverNG endpoints information via REST: > Type: Hot Rod/REST/Memcached > Port: 11222 > Security: authentication/encryption -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes resolved ISPN-8535. ------------------------------------- Resolution: Done The API foundation and main REST resources were created, covering caches, cache managers, configs, health, counters. All further work will be done on separate JIRAs > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > * Stop individual servers and the full cluster > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Work on ISPN-8535 started by Gustavo Fernandes. ----------------------------------------------- > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > * Stop individual servers and the full cluster > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8535: ------------------------------------ Status: Open (was: New) > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > * Stop individual servers and the full cluster > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2019