[JBoss JIRA] (SWSQE-80) Automated deployment of Istio Traffice Management
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-80?page=com.atlassian.jira.plugin.s... ]
Matt Mahoney updated SWSQE-80:
------------------------------
Description:
As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration.
Istio documentation reference: [link title|https://istio.io/docs/tasks/traffic-management/]
was:
As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration.
> Automated deployment of Istio Traffice Management
> -------------------------------------------------
>
> Key: SWSQE-80
> URL: https://issues.jboss.org/browse/SWSQE-80
> Project: Swift Sunshine QE
> Issue Type: Story
> Reporter: Matt Mahoney
> Assignee: Michael Foley
>
> As a test engineer I want an automated way to deploy Istio Traffic Management such as Route Rules and Circuit Breakers into my test configuration.
> Istio documentation reference: [link title|https://istio.io/docs/tasks/traffic-management/]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2253:
---------------------------
Fix Version/s: 4.0.12
> FD_SOCK is not working in AWS environment
> -----------------------------------------
>
> Key: JGRP-2253
> URL: https://issues.jboss.org/browse/JGRP-2253
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.10
> Environment: AWS - EC2
> Reporter: Sibin Karnavar
> Assignee: Bela Ban
> Fix For: 4.0.12
>
>
> We have our failure detection defined like below.
> <FD_SOCK external_port="7804" />
> <FD timeout="3000" max_tries="3" />
> <VERIFY_SUSPECT timeout="3000" />
> Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing.
> In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK.
> We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port.
> Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS.
> Thanks,
> Sibin
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
by Miroslav Novak (JIRA)
Miroslav Novak created WFLY-10094:
-------------------------------------
Summary: [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
Key: WFLY-10094
URL: https://issues.jboss.org/browse/WFLY-10094
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
Priority: Blocker
LibAIO does not get loaded on RHEL 6 x86_64:
{code}
[hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /tmp/jboss-eap
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
...
10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging)
10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal
...
{code}
libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month