October 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7081) Console Typescript Refactoring

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7081?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7081: ------------------------------------ Merged with Master: https://github.com/infinispan/infinispan-management-console/compare/52525... > Console Typescript Refactoring > ------------------------------ > > Key: ISPN-7081 > URL: https://issues.jboss.org/browse/ISPN-7081 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > In order to improve the extensibility of the existing console code (vanilla javascript), it is necessary for the angular services which drive the console to be refactored. Consequently, this means that the majority of the angular controllers and directives also need to be refactored to incorporate the aforementioned service changes. Therefore, as extensive changes to the code are already required, this is an ideal opportunity for the console code to be rewritten in Typescript. > The advantages of porting to Typescript are as follows: > * Statically typed - errors can be discovered at compile time and improved IDE support. > * Utilises ES6 modules, which allows for better adherence to DRY principles > * Typescript is the basis of Angular 2.x, which we hope to migrate to eventually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7081) Console Typescript Refactoring

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7081?page=com.atlassian.jira.plugin.... ] Work on ISPN-7081 started by Ryan Emerson. ------------------------------------------ > Console Typescript Refactoring > ------------------------------ > > Key: ISPN-7081 > URL: https://issues.jboss.org/browse/ISPN-7081 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > In order to improve the extensibility of the existing console code (vanilla javascript), it is necessary for the angular services which drive the console to be refactored. Consequently, this means that the majority of the angular controllers and directives also need to be refactored to incorporate the aforementioned service changes. Therefore, as extensive changes to the code are already required, this is an ideal opportunity for the console code to be rewritten in Typescript. > The advantages of porting to Typescript are as follows: > * Statically typed - errors can be discovered at compile time and improved IDE support. > * Utilises ES6 modules, which allows for better adherence to DRY principles > * Typescript is the basis of Angular 2.x, which we hope to migrate to eventually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5820) Add JMX notification support for cluster events

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5820?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-5820: ------------------------------------- Assignee: Vladimir Blagojevic (was: Dan Berindei) > Add JMX notification support for cluster events > ----------------------------------------------- > > Key: ISPN-5820 > URL: https://issues.jboss.org/browse/ISPN-5820 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5820) Add JMX notification support for cluster events

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5820?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5820: ---------------------------------- Labels: (was: jdg7) > Add JMX notification support for cluster events > ----------------------------------------------- > > Key: ISPN-5820 > URL: https://issues.jboss.org/browse/ISPN-5820 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Dan Berindei > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7114) Consistency checker

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7114: ------------------------------------- Summary: Consistency checker Key: ISPN-7114 URL: https://issues.jboss.org/browse/ISPN-7114 Project: Infinispan Issue Type: Feature Request Components: Core Reporter: Tristan Tarrant We should implement a consistency checker that can either be run on demand via management (e.g. JMX) or triggered by a merge or a topology change caused by abrupt leavers. It should perform per-segment analysis of each key/value pair between primary and backup. The design should incorporate pluggable repair strategies (e.g. latest wins, primary wins, discard, degrade segment, custom) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7113) Create a Zeppelin connector

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7113?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7113: ------------------------------------- Assignee: Gustavo Fernandes > Create a Zeppelin connector > --------------------------- > > Key: ISPN-7113 > URL: https://issues.jboss.org/browse/ISPN-7113 > Project: Infinispan > Issue Type: Feature Request > Components: Analytics, Integration > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > > http://zeppelin.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7113) Create a Zeppelin connector

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7113: ------------------------------------- Summary: Create a Zeppelin connector Key: ISPN-7113 URL: https://issues.jboss.org/browse/ISPN-7113 Project: Infinispan Issue Type: Feature Request Components: Analytics, Integration Reporter: Tristan Tarrant http://zeppelin.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7083) Prepare Node Affinity example for Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7083?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7083: ------------------------------------------- Blogged about the solution: http://blog.infinispan.org/2016/10/openshift-and-node-affinity.html > Prepare Node Affinity example for Kubernetes > -------------------------------------------- > > Key: ISPN-7083 > URL: https://issues.jboss.org/browse/ISPN-7083 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > Fix For: 9.0.0.Final > > > Infinispan supports Node Affinity but it requires setting {{rackId}} and {{machineId}}. This fits perfectly into {{region}} and {{zone}} in Kubernetes. > Now we need to figure out, how to combine those two together. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7083) Prepare Node Affinity example for Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7083?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec resolved ISPN-7083. --------------------------------------- Fix Version/s: 9.0.0.Final Resolution: Done > Prepare Node Affinity example for Kubernetes > -------------------------------------------- > > Key: ISPN-7083 > URL: https://issues.jboss.org/browse/ISPN-7083 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > Fix For: 9.0.0.Final > > > Infinispan supports Node Affinity but it requires setting {{rackId}} and {{machineId}}. This fits perfectly into {{region}} and {{zone}} in Kubernetes. > Now we need to figure out, how to combine those two together. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7111) Avoid using InetAddress.getLocalHost() in the tests

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7111?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-7111: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Avoid using InetAddress.getLocalHost() in the tests > --------------------------------------------------- > > Key: ISPN-7111 > URL: https://issues.jboss.org/browse/ISPN-7111 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1 > > > Depending on the network, {{InetAddress.getLocalHost()}} can be quite slow. Some tests use it in a loop, via the {{org.jgroups.stack.IpAddress(port)}} constructor, and the core test suite can spend a lot of time doing this: > {noformat} > "testng-VersionAwareMarshallerTest" #17 prio=5 os_prio=0 tid=0x00007f8b54eb8000 nid=0x4300 runnable [0x00007f8ad9236000] > java.lang.Thread.State: RUNNABLE > at java.net.Inet4AddressImpl.getLocalHostName(Native Method) > at java.net.InetAddress.getLocalHost(InetAddress.java:1474) > at org.jgroups.stack.IpAddress.setAddressToLocalHost(IpAddress.java:69) > at org.jgroups.stack.IpAddress.<init>(IpAddress.java:90) > at org.jgroups.stack.IpAddress.<init>(IpAddress.java:84) > at org.infinispan.marshall.VersionAwareMarshallerTest.testMapMarshalling(VersionAwareMarshallerTest.java:164) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2016