ec-release / sdk

The Agent SDK

The Agent SDK

The Enterprise-Connect SDK Repo.

• Design
• Issue trackers
• Features/Projects
• Usage
• Load-Balancer
• OCI images usage

Dependency Matrix

Mode	Avaialble Releases	CF Service	Docker	OAuth
Client	v1, v1beta	Service 1.x	Optional	UAA
Gateway	v1, v1beta	Service 1.x	Optional	UAA
Server	v1, v1beta	Service 1.x	Optional	UAA
GW:Client	v1, v1beta	Service 1.x	Optional	UAA
GW:Server	v1, v1beta	Service 1.x	Optional	UAA

Revision Matrix

Rev.	Decrypt Binary	Download/Release	CF Instance	CF Service	CF Broker	SDK/Plugins	Tools	Build	QA
v1	1.2-rc.0.reiwa	hokkaido.213 Release Note	Predix CF1, GovCloud, Frankfurt	kyushu.145 project access	okinawa.8 [project access]	v1.hokkaido.212	Cloud Foundry Only	Gitlab-CI	Integration
v1	N/A	hokkaido.212 Release Note	Predix CF1, GovCloud, Frankfurt	kyushu.145 project access	okinawa.8 [project access]	v1.hokkaido.212	Cloud Foundry Only	Gitlab-CI	Integration
v1beta	N/A	fukuoka.1727 Release Note	Predix CF3	sendai.1079 [project access]	okayama.49 [project access]	v1beta.fukuoka.1725	[e-mail].80	Gitlab-CI	Integration
v1beta	N/A	fukuoka.1725 Release Note	Predix CF3	sendai.1079 [project access]	okayama.49 [project access]	v1beta.fukuoka.1725	[e-mail].80	Gitlab-CI	Integration

x509 Certificates, RSA keypair, licensing, security

Please contact [email protected] for detais.

Validation

## Verify the checksum
### Linux
```bash
$ sha256 ./path/to/file/ecagent_linux_sys
b3bf9cd9686e
$ awk 's=index($0,"b3bf9cd9686e") { print "line=" NR, "start position=" s}' checksum.txt
line=2 start position=1

Mac OS

$ shasum -a 256 ./path/to/file/ecagent_linux_sys
b3bf9cd9686e
$ awk 's=index($0,"b3bf9cd9686e") { print "line=" NR, "start position=" s}' checksum.txt
line=2 start position=1

Windows

c: \> CertUtil -hashfile C:\path\to\file\ecagent_windows.exe sha256
b3bf9cd9686e (find the checksum in the checksum.txt)

Release History

Please verify the Release History for previous releases.

Be Social with the team

• Slack Usergroup Channel
• Weekly Google Meeting

Disclaimer

^{Predix, Cloud Foundry, and all subsidiary software products are the DT/RT copyrights all rights reserved by GE Digital LLC. EC Cloud Foundry Service (including the CF Broker) are the products owned by GE Corp, currently maintained by Enterprise-Connect R&D Team. Components that DO NOT associate with Predix, Cloud Foundry, are all under the MIT license, and actively developed and being authored by the Enterprise Connect R&D team. The team (Enterprise Connect R&D Team) is sponsored by GE Corp. Enterprise Connect R&D Team CA is the highest Certificate Authority of its security ECO system, under its own terms.}

sdk's Issues

What is the Problem(s) to solve for GE Capital?

Could not able to make EC connection with beta agent

We were using beta 1676 agent version for making VLAN connection and could not able to make it connection successful.

Test AWS gateway connectivity with On Prem agents

Test the EC connectivity with following scenario -

• Deploy gateway in customer VPC
• Run server agent in 'on prem'
• Run client in VPC

Documentation Missing: VLN Plug-in Flush

Issue: Please Document a way to make sure VLN IPs are loaded/flushed from local loopback interface

Solution: : To check the list IPs that are loaded into 'lo' interface. Run the following command.

 ###  "sudo ip addr show"

1. To Flush the IPs loaded onto the 'lo' interface

   "sudo ip addr flush dev lo"

2. Add 127.0.0.1 back loopback by this command

   "sudo ip addr add 127.0.0.1/8 dev lo"

Note: These commands require root access on the server

3. Re-run the ecagent client again as root

- Make file transfer available in the gateway single mode

Currently file transfer (FT) is only available to fuse mode topology. User requests the FT be available across all modes in the usage.

What is the Problem(s) to solve for GE Power?

As a solution engineer, what is the problem I would like to solve and the solution I would like to contribute to the GE Power business?

- Multiple Proxy Settings

Recent deployment indicate several use cases for different proxy settings. E.g. Connecting to a gateway deployed onprem without a HTTP proxy, but still need to be able to access any external CF UAAs/EC Services with separate proxy settings.

Agent+TLS Container Usage

Need usage examples for platforms using Mody (linux cgroup)

- Invalid Client Access for GE Power

Deploy a client agent onprem. However, in the case with Power, the access is not available with the internal-facing LBer due to the client proxy setting. Need to deploy a external-facing LBer for the interim.

Documentation: Provide a document to test connectivity

Provide a document to test the connectivity between agents e.g. file transfers etc - This will help people be able to test the connectivity with the need for accessing the resources ID/password

Bug: EC server health and super connection exists but connectivity breaks

[EC Server] 2019/09/27 12:48:27 [gateway connection{host=wss://capital-preprod-ec-gateway.run.aws-usw02-pr.ice.predix.io/agent, session=9AXjuhf9xg,gatewayId=dd058d65-56bb-4fa2-bb7c-f365f16f9b41} established for client# Huzils with bindId#YvNk2g7TPf, to VLAN address: 127.0.0.1:7987 if -vln is enabled.]
[EC Server] 2019/09/27 12:48:27 [websocket is found in the pool for clientId#Huzils]
[EC Server] 2019/09/27 12:48:27 [successful added resource (alpi2cosbsvn02.corporate.ge.com:7201) for clientId# with bindId#]
[EC Server] 2019/09/27 12:48:27 [session# 9AXjuhf9xg created. client has been picked from the pool. Beginning two-way piping.]
[EC Server] 2019/09/27 12:48:27 [connection has been picked up and removed from the pool with bindId#YvNk2g7TPf]
[EC Server] 2019/09/27 12:48:31 [client#Huzils requests connection with the bind id#s1WvAC5XLC.]
[EC Server] 2019/09/27 12:48:31 [proxy serivce (10.114.19.201) is found.]
[EC Server] 2019/09/27 12:48:31 [server has been successfully created for clientId#Huzils with bindId#s1WvAC5XLC]
[EC Server] 2019/09/27 12:48:31 [gateway connection{host=wss://capital-preprod-ec-gateway.run.aws-usw02-pr.ice.predix.io/agent, session=KIUoYO7gKy,gatewayId=dd058d65-56bb-4fa2-bb7c-f365f16f9b41} established for client# Huzils with bindId#s1WvAC5XLC, to VLAN address: 127.0.0.1:7987 if -vln is enabled.]
[EC Server] 2019/09/27 12:48:31 [websocket is found in the pool for clientId#Huzils]
[EC Server] 2019/09/27 12:48:31 [successful added resource (alpi2cosbsvn02.corporate.ge.com:7201) for clientId# with bindId#]
[EC Server] 2019/09/27 12:48:31 [session# KIUoYO7gKy created. client has been picked from the pool. Beginning two-way piping.]
[EC Server] 2019/09/27 12:48:31 [connection has been picked up and removed from the pool with bindId#s1WvAC5XLC]
[EC Server] 2019/09/27 12:48:32 [exception occurred in wsocket client reading. err: websocket: close 1006 (abnormal closure): unexpected EOF (session# GS2arkRwT0 bind# ZiF55QnrXU )]
[EC Server] 2019/09/27 12:48:32 [exception occurred in tcp server reading. err: read tcp 10.93.64.244:44938->10.93.64.244:7201: use of closed network connection (session# GS2arkRwT0 bind# ZiF55QnrXU )]
[EC Server] 2019/09/27 12:48:32 [session#: GS2arkRwT0 has been deleted.]
[EC Server] 2019/09/27 12:48:32 [session#: GS2arkRwT0 has been deleted.]
[EC Server] 2019/09/27 12:48:34 [client#Huzils requests connection with the bind id#t6iqGR4moB.]
[EC Server] 2019/09/27 12:48:35 [exception occurred in wsocket client reading. err: websocket: close 1006 (abnormal closure): unexpected EOF (session# I5WCj1NOML bind# WJc7l0RUTu )]
[EC Server] 2019/09/27 12:48:35 [exception occurred in tcp server reading. err: read tcp 10.93.64.244:44946->10.93.64.244:7201: use of closed network connection (session# I5WCj1NOML bind# WJc7l0RUTu )]
[EC Server] 2019/09/27 12:48:35 [session#: I5WCj1NOML has been deleted.]
[EC Server] 2019/09/27 12:48:35 [session#: I5WCj1NOML has been deleted.]
[EC Server] 2019/09/27 12:48:37 [exception occurred in wsocket client reading. err: websocket: close 1006 (abnormal closure): unexpected EOF (session# QFknMS4JBt bind# RUgJdmx6hF )]
[EC Server] 2019/09/27 12:48:37 [exception occurred in tcp server reading. err: read tcp 10.93.64.244:44952->10.93.64.244:7201: use of closed network connection (session# QFknMS4JBt bind# RUgJdmx6hF )]
[EC Server] 2019/09/27 12:48:37 [session#: QFknMS4JBt has been deleted.]
[EC Server] 2019/09/27 12:48:37 [session#: QFknMS4JBt has been deleted.]
[EC Server] 2019/09/27 12:48:44 [exception occurred in wsocket client reading. err: websocket: close 1006 (abnormal closure): unexpected EOF (session# YfTLZYH90w bind# mnSsohlc2a )]
[EC Server] 2019/09/27 12:48:44 [exception occurred in tcp server reading. err: read tcp 10.93.64.244:44972->10.93.64.244:7201: use of closed network connection (session# YfTLZYH90w bind# mnSsohlc2a )]

Can't start EC client after pushing gateway and server

Hi Support Team,

We tried to configure the gateway, server and client for a new Enterprise Connect service. We have followed the latest documentations (https://enterprise-connect.github.io/documentation/docs/agents.html).

Here is the configuration with quotes.

Gateway Script

#!/bin/bash
./ecagent_linux_sys -mod "gateway" -gpt "${PORT}" -zon "zone_id" -sst "https://zone_id.run.aws-usw02-pr.ice.predix.io" -tkn "admin_token"

Server Script

./ecagent_linux_sys -mod "server" -aid "vzLQ3I" -grp "zone_id" -cid "client_id" -csc "client_secret" -dur "84000" -oa2 "uaa_uri" -hst "wss://gateway-zone_id.run.aws-usw02-pr.ice.predix.io/agent" -zon "zone_id" -sst "https://zone_id.run.aws-usw02-pr.ice.predix.io" -rht "postgres_uri" -rpt "5432" -hca "${PORT}"

Client Script

./ecagent_darwin_var -mod "client" -aid "5Igjns" -tid "vzLQ3I" -grp "zone_id" -cid "client_id" -csc "client_secret" -dur "84000" -oa2 "uaa_uri" -hst "wss://gateway-zone_id.run.aws-usw02-pr.ice.predix.io/agent" -lpt "5432"

Predix support suggests us to try configurations without quotes but it still doesn't work.

Gateway Script

#!/bin/bash
./ecagent_linux_sys -mod gateway -gpt ${PORT} -zon zone_id -sst https://zone_id.run.aws-usw02-pr.ice.predix.io -tkn admin_token

Server Script

./ecagent_linux_sys -mod server -aid vzLQ3I -grp zone_id -cid client_id -csc client_secret -dur 84000 -oa2 uaa_uri -hst wss://gateway-zone_id.run.aws-usw02-pr.ice.predix.io/agent -zon zone_id -sst https://zone_id.run.aws-usw02-pr.ice.predix.io -rht postgres_uri -rpt 5432 -hca ${PORT}

Client Script

./ecagent_darwin_var -mod client -aid 5Igjns -tid vzLQ3I -grp zone_id -cid client_id -csc client_secret -dur 84000 -oa2 uaa_uri -hst wss://gateway-zone_id.run.aws-usw02-pr.ice.predix.io/agent -lpt 5432

Here is the error when we start the client.

[
▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄
▐░░░░░░░░░░░▌▐░░░░░░░░░░░
▐░█▀▀▀▀▀▀▀▀▀ ▐░█▀▀▀▀▀▀▀▀▀
▐░▌ ▐░▌
▐░█▄▄▄▄▄▄▄▄▄ ▐░▌
▐░░░░░░░░░░░▌▐░▌
▐░█▀▀▀▀▀▀▀▀▀ ▐░▌
▐░▌ ▐░▌
▐░█▄▄▄▄▄▄▄▄▄ ▐░█▄▄▄▄▄▄▄▄▄
▐░░░░░░░░░░░▌▐░░░░░░░░░░░▌
▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀▀▀▀ @digital Connect
]
[EC Client] 2019/12/03 16:30:04 [cleaned up logging file(s). connectivity.log plugin.log]
[EC Client] 2019/12/03 16:30:04 [Rev: v1.hokkaido.212]
[EC Client] 2019/12/03 16:30:04 [Agent websocket compression is being negotiated at level 0]
[EC Client] 2019/12/03 16:30:04 [refresh duration is specified. Token auto-refresh is set.]
[EC Client] 2019/12/03 16:30:04 [Fetching new token..]
[EC Client] 2019/12/03 16:30:06 [Token refreshed. The token will be expired in 1399 minutes. Approx. 1400 minutes to the next auto-refresh.]
[EC Client] 2019/12/03 16:30:06 [[VLAN] client is listening on port# 5432]
[EC Client] 2019/12/03 16:30:16 [error while adding the client inst.]
[EC Client] 2019/12/03 16:30:16 [github.build.ge.com/212359746/wzcore.(*Client).Hire.func6.2.1 websocket: bad handshake]

Any help would be really appreciated!
Xiaoyan

Jobs are getting stuck post v210 binaries upgrade on production

Team has recently upgraded the libraries on below path and post that the jobs are getting stuck, team need to manually push the adhoc frequently.

Go\src\github.build.ge.com\BHGE-RealTrack\rt-dataIngestion-develop\ec-sdk

ecagent_linux_var
ecagent_darwin_var
ecagent_linux_sys

Services:
rt_bhge_dataloader_prod
rt-dataingestion-jobs_ONG

Kindly help us to address this issue.

Predix ticket raised: Ticket #INC0094247

Thanks and Regards,
Harshada Gawde

Can the TLS plugin utilised for HTML Browsing?

The TLS plugin may not be fitting as a HTTP Proxy for browsing purpose, specifically not for HTML asynchronous-loading. it was designed to simulate the HTTP channel based on one-request-one-response model.

Some usage reports that users are able to browse pages with single HTML file loading, however, the plugin is not responsible for translating any subsequent HTML linkage, which may graduate into broken links during browsing.

EC Connectivity Issue for QA2 Instance of PowerPLM

When we are trying to connect to QA2 Instance from EC we are facing below issue.

Actions Performed:

1. Instead of load balancer URL , Tried connecting to IP - 10.93.224.23
2. Tried with IP and Port – 80 and 443
3. Tried with removing existing QA2 Certificates and re-installation of the certificates provided by Andrew

invokehttp.request.url
http://10.242.49.126:7220/powerplminternal/resources/external/governance/eccn/update
No value set
invokehttp.status.code
502
No value set
invokehttp.status.message
Bad Gateway

Actual URL:https://qa2-powerplm.pw.ge.com/powerplminternal/resources/external/governance/eccn/update

Idea: End to end health probe across EC Agent layers

Issue:
There is NO quick Health Check to know complete communication between all Client-> Gateway -> Server agents

Description:
Typically EC Client only makes a call when the requester makes a call to the resource. But it has a potential to fail because of several reasons(network between client and EC Gateway or backend EC Server issues etc). This put all the burden of connectivity on the requester to handle EC failures.

• Idea is to provide the frequent (5 minutes interval ) health probe connection between all agents EC Client initiated health check between all agents EC-Client > EC GW > EC Server etc
• Health probe refresh interval value can be configured on EC Client side in the future
• This information is stored in an API on the EC Client side - e.g. /connection-health
• Health probe could be as simple as small payload data( sending a timestamp, agentid etc to the other side) that can be sent using file-upload then down-load functionality
• This health information can be used to send proactive alert notifications

Custom DB EC connection issue on IBS TC instance

We are trying to connect an oracle DB via EC where the client agent is running on IBS TC instance and server agent is running on Dev CCL servers.

We are trying to hit EC port 8495 from the TC instance on the same machine where EC client is running but getting nothing in the logs.

We have got port 8495 open from the infra team and are able to telnet it.
When we telnet to the port we are getting an incoming connection request in the logs but not when trying to hit from TC.

We are using 10.0.0.4 : 8495 to hit the EC. This hostname solved the issue previously in one another similar setup but currently we are not able to solve this. Kindly help.
PFA the error message from TC

Unstable connection with 1725 beta agent

Looks to me system is taking more time for connection and client request getting timed out.

Here is the details -

Scenario: Connecting to 'on prem' mysql database from EC2 in power EU VPC

Client logs:

[EC Debug] 2020/01/14 20:59:00 []interface {}=>[ECClientIP:7979]
 [EC Debug] 2020/01/14 20:59:01 []interface {}=>[p_fielSize 0xc000052cb0]
 [EC Client] 2020/01/14 20:59:01 [client#nH8Qe0 connection is pending for a confirmation from the gateway]
 [EC Debug] 2020/01/14 20:59:01 []interface {}=>[entering thread# 16]
 [EC Debug] 2020/01/14 20:59:01 []interface {}=>[d {"a1":"b1","a2":"MgdnmgeS76"}]
 [EC Client] 2020/01/14 20:59:01 [connection request has been received by the gateway with the bindId#MgdnmgeS76]
 [EC Debug] 2020/01/14 20:59:13 []interface {}=>[EOF received whilst reading from the gateway.]
 [EC Client] 2020/01/14 20:59:13 [agent exiting TCP_REQUEST.]
 [EC Debug] 2020/01/14 20:59:13 []interface {}=>[exiting thread# 16]
 [EC Client] 2020/01/14 20:59:13 [bind#: MgdnmgeS76 has been removed from the pool.]

Gateway logs:

[EC Debug] 2020/01/14 20:59:00 []interface {}=>[ECClientIP]
 [EC Gateway] 2020/01/14 20:59:00 [the request port might not be specified. continuing validation..]
 [EC Gateway] 2020/01/14 20:59:00 [ip passed filtering with x-forward-for.]
 [EC Debug] 2020/01/14 20:59:00 []interface {}=>[[127.0.0.1 ECClientIP]]
 [EC Gateway] 2020/01/14 20:59:00 [ip passed filtering with ec-options header.]
 [EC Debug] 2020/01/14 20:59:00 []interface {}=>[_rconf.GatewayHost.Host ec-gateway.power.ge.com GatewayHost:Host {wss   ec-gateway.power.ge.com /agent  false  }]
 [EC Debug] 2020/01/14 20:59:00 []interface {}=>[https://d985acd4-806a-4679-9441-cd6ebc211c22.run.aws-usw02-dev.ice.predix.io/v1beta/api/token/validate]
 [EC Gateway] 2020/01/14 20:59:01 [a superconn is identified for server agent#jhOcAx]
 [EC Debug] 2020/01/14 20:59:01 []interface {}=>[https://d985acd4-806a-4679-9441-cd6ebc211c22.run.aws-usw02-dev.ice.predix.io/v1beta/admin/accounts/validate?agtId1=nH8Qe0&agtId2=jhOcAx]
 [EC Gateway] 2020/01/14 20:59:01 [client acknowledged the connection. requesting server callback with bindId: MgdnmgeS76, clientId: nH8Qe0, gatewayKey: 0e:c5:3d:65:0c:c1:0]
 [EC Debug] 2020/01/14 20:59:10 []interface {}=>[keepalive sent for agent# jhOcAx type: admin]
 [EC Gateway] 2020/01/14 20:59:13 [client (bind# MgdnmgeS76) pending longer than expected, is now being removed from the pool.]
 [EC Gateway] 2020/01/14 20:59:13 [exception occurred in client reading. err: read tcp 10.229.253.91:7990->10.229.253.235:55620: use of closed network connection  (session#   bind# MgdnmgeS76 )]
 [EC Debug] 2020/01/14 20:59:13 []interface {}=>[Data transmitting done at total  0  bytes.]
 [EC Gateway] 2020/01/14 20:59:13 [client with bindId:MgdnmgeS76has been removed from the pools.]
 [EC Gateway] 2020/01/14 20:59:13 [[client with bindId:MgdnmgeS76has been removed from the pools.]]
 [EC Gateway] 2020/01/14 20:59:13 [Both sessionId:  and bindId: MgdnmgeS76 have been removed from the pools.]
 [EC Debug] 2020/01/14 20:59:24 []interface {}=>[ECServerIP]
 [EC Gateway] 2020/01/14 20:59:24 [the request port might not be specified. continuing validation..]
 [EC Gateway] 2020/01/14 20:59:24 [ip passed filtering with x-forward-for.]
 [EC Debug] 2020/01/14 20:59:24 []interface {}=>[[127.0.0.1 ::1 fe80::1 ECServerIP fe80::6046:75ff:fe8f:4c30 fe80::4c3:9e37:686c:6dca]]
 [EC Gateway] 2020/01/14 20:59:24 [ip passed filtering with ec-options header.]
 [EC Debug] 2020/01/14 20:59:24 []interface {}=>[_rconf.GatewayHost.Host ec-gateway.power.ge.com GatewayHost:Host {wss   ec-gateway.power.ge.com /agent  false  }]
 [EC Debug] 2020/01/14 20:59:24 []interface {}=>[https://d985acd4-806a-4679-9441-cd6ebc211c22.run.aws-usw02-dev.ice.predix.io/v1beta/api/token/validate]
 [EC Gateway] 2020/01/14 20:59:24 [received server# jhOcAx request]
 [EC Debug] 2020/01/14 20:59:31 []interface {}=>[error sending KeepAlive frame with agent# nH8Qe0 type: client err: write tcp 10.229.253.91:7990->10.229.253.235:55620: use of closed network connection]
 [EC Gateway] 2020/01/14 20:59:32 [reporting usage..]
 [EC Debug] 2020/01/14 20:59:32 []interface {}=>[{"cfRoutingURL":"wss://ec-gateway.power.ge.com/agent","data":"wI7pmp/bOtXT6AWGOBXquIkSJ4Y3ZwIDF/kfiA+owCMAb3Rh2ou/j+vZB7s8zYu2XqnxJzRtD+n6ojtwxrAdbSK+Uph2UJWORN9mQ7E47XY3oFDG5PnuP/3WN3D7vK3MelsEUy44WFNpIgcvsDAikg2HRQT6Dl3x4PnIkJ8z+OhbOt3/6SFiHzptOIfJQ9/2VYCKOnAbHt+PAUJMPnAZyanDCUOEEzpOGLo8URKyLvqTbMc9OAMzlfq533iVsC5jb5opuhbZfLsK+0Yxqmts6FwHUuef9g+3rliit6L+jQIKkkGPabxL4lbM4inTaM5qEgrxN5xYUoJGIf2ZLdlEFQ==","gtwId":"0e:c5:3d:65:0c:c1","lastUsage":0,"refId":"0","zone":"d985acd4-806a-4679-9441-cd6ebc211c22"}]
 [EC Debug] 2020/01/14 20:59:33 []interface {}=>[map[cfRoutingURL:wss://ec-gateway.power.ge.com/agent data:dm1ad0JyTw== gtwId:0e:c5:3d:65:0c:c1 lastUsage:0 refId:0 status:EC_GRANT zone:d985acd4-806a-4679-9441-cd6ebc211c22]]
 [EC Gateway] 2020/01/14 20:59:33 [usage reported.]
 [EC Debug] 2020/01/14 20:59:40 []interface {}=>[keepalive sent for agent# jhOcAx type: admin]
 [EC Gateway] 2020/01/14 20:59:40 [websocket: close 1006 (abnormal closure): unexpected EOF]
 [EC Gateway] 2020/01/14 20:59:40 [support connection for Server Agent Id#jhOcAx has been deleted.]
 [EC Debug] 2020/01/14 20:59:40 []interface {}=>[keepalive terminated for agent# jhOcAx type: admin]

Server logs:

 [EC Debug] 2020/01/14 15:59:02 []interface {}=>[{"glist":{"0e:c5:3d:65:0c:c1:0":{"gtwId":"0e:c5:3d:65:0c:c1","zone":"d985acd4-806a-4679-9441-cd6ebc211c22","refId":"0","timeCreated":1579035452613,"active":true,"CFRoutingURL":"","CFURL":"wss://ec-gateway.power.ge.com/agent"}},"data":"ca9/AuUwsmATP2pL1TvG7QyWHDqGLvsHvvnK5zdwt2wDwvWMKv8JQZ8OYma5WcyCcAtrWSzrxRxnQBKU7wg9ERVsvd3JpW9AGHdpILzWCvhM6oyi2YF8UiPcBW1PdJ8feSiObVew1OidjEz82bSt1K1dMnbVYZA1yc8P8lehBK2dyL2at7+eqC50t5ZE6lspgCgia6UGjHN/SCxRSvGhQWCS3O5vANCWswkYs+Ih+WrVHGVF6Kwyt1/G53I9vquiGpCvNBhk6n5mYmRH5nuo08OBCNf+eA9GvRNGGNB4+XmnUtaCwRnMGAyubRB5957/s9/tE/ysVRb1koL9OEb/JA=="}]
 [EC Server] 2020/01/14 15:59:02 [client#nH8Qe0 requests connection with the bind id#MgdnmgeS76.]
 [EC Debug] 2020/01/14 15:59:02 []interface {}=>[map[a1:b4 a2:MgdnmgeS76 a4:nH8Qe0 a5:0e:c5:3d:65:0c:c1:0] map[0e:c5:3d:65:0c:c1:0:0xc000118c60] "gwKey" 0e:c5:3d:65:0c:c1:0]
 [EC Debug] 2020/01/14 15:59:02 []interface {}=>[[0e:c5:3d:65:0c:c1:0]]
 [EC Debug] 2020/01/14 15:59:02 []interface {}=>[gateway list exchange called.]
 [EC Debug] 2020/01/14 15:59:02 []interface {}=>[CFRoutingURL:HostName ec-gateway.power.ge.com Server:hst ec-gateway.power.ge.com]
 [EC Debug] 2020/01/14 15:59:12 []interface {}=>[{"glist":{"0e:c5:3d:65:0c:c1:0":{"gtwId":"0e:c5:3d:65:0c:c1","zone":"d985acd4-806a-4679-9441-cd6ebc211c22","refId":"0","timeCreated":1579035452613,"active":true,"CFRoutingURL":"","CFURL":"wss://ec-gateway.power.ge.com/agent"}},"data":"CJA3xIhlokfHVoVlfQdNeS64PCYyWLtZN3VXA7it5fI3Pz9wxPi52IcpVb4MZ2+bAY2eFgOLJeIO0k8Wek3JTqzJE6gjRJSkt8aJSxnsXsDfPpsleDdx5IgjLg2jAQQgvpDZBGtGeODUw7lpRIk0Dqw4xx3KGkEptm0YDTc2vcN5mUn3jjs6LvAkiek+A045VGV6xWYSrZOv+dz+gk//XkXMkGU7hg7jyCQ0EIBHtNuw5RRuXePrUWXOzwpc5JtaVeLMYpdB6zR4sHiI7cAuYxUewqItxYSW0nz2L1Xm5sV8500Iu8azMNPFsr3ITKfjNIQbqhXT57e7SPjqzuggrA=="}]
 [EC Debug] 2020/01/14 15:59:13 []interface {}=>[gateway list exchange called.]
 [EC Debug] 2020/01/14 15:59:13 []interface {}=>[CFRoutingURL:HostName ec-gateway.power.ge.com Server:hst ec-gateway.power.ge.com]
 [EC Debug] 2020/01/14 15:59:23 []interface {}=>[{"glist":{"0e:c5:3d:65:0c:c1:0":{"gtwId":"0e:c5:3d:65:0c:c1","zone":"d985acd4-806a-4679-9441-cd6ebc211c22","refId":"0","timeCreated":1579035452613,"active":true,"CFRoutingURL":"","CFURL":"wss://ec-gateway.power.ge.com/agent"}},"data":"cPXvXJuDo2GOZNNJk8RLYrQqogCpnpSEVUAqUjISVxYU6XoDkE+nTA7hwqZH+wySIsu97CAPaQNUfXyiOPwkQmDmrCLYmWWNnHR4vgNupxDBg7XASnA8DSJvWfA41OvRJX6By0Gk+4og3Yh/iUuNiv+PtSwcQNqoUA3NVAxVfelR0PGDfEasq96oVHcgmQs/+htPa8CnRqW4/753WIexf8XupzPbHm66gXwEKQGywQdWE5x8iEBRCRzZ0rH8G0A26dN6UYXhr4GG+XO1fL0sp2Mkp1KbQH6Ahr9GcJ41PSDDyqBrrl3sl1CtTPKw5nirJx/BXqcg259HD4+onQMwNw=="}]
 [EC Debug] 2020/01/14 15:59:24 []interface {}=>[gateway list exchange called.]
 [EC Debug] 2020/01/14 15:59:24 []interface {}=>[CFRoutingURL:HostName ec-gateway.power.ge.com Server:hst ec-gateway.power.ge.com]
 [EC Server] 2020/01/14 15:59:25 [server has been successfully created for clientId#nH8Qe0 with bindId#MgdnmgeS76]
 [EC Server] 2020/01/14 15:59:25 [server standby in the gateway with session#]
 [EC Server] 2020/01/14 15:59:25 [[server standby in the gateway with session#]]
 [EC Debug] 2020/01/14 15:59:34 []interface {}=>[{"glist":{"0e:c5:3d:65:0c:c1:0":{"gtwId":"0e:c5:3d:65:0c:c1","zone":"d985acd4-806a-4679-9441-cd6ebc211c22","refId":"0","timeCreated":1579035452613,"active":true,"CFRoutingURL":"","CFURL":"wss://ec-gateway.power.ge.com/agent"}},"data":"YNoMrQZZq7N/OZvIMSuv3QIt3dIbKuBOs6lDapeyphAdWRDgAspT+MoDcSjRzllXiLRnhG6vwg0rmRROoYORqq4B1zA/aV21ZVjiVCgwl5ONtxLtZnX7lf2tO0YJTYfItqaeRDyIghBINOAvJnM0J2pbrjBm4vhhSInG5ode5yZWW/0q8vdmA4q2OGCXMduPhBIQhRrYcx/FH7A5zHCIxCn7B9nihGqtdHvs50YvOkSK8n6DonjtPKxWtu7bvzcnFpNQ7+KoF3RAj++QuxSDdG4kWtQZE9dYwRuyD7zvH5k0Svxu84eb+LTUOi02S0nTAbSyJ5Sl4Bzi3KIFO6gVfQ=="}]
 [EC Debug] 2020/01/14 15:59:34 []interface {}=>[gateway list exchange called.]
 [EC Debug] 2020/01/14 15:59:34 []interface {}=>[CFRoutingURL:HostName ec-gateway.power.ge.com Server:hst ec-gateway.power.ge.com]

Client tool:

$ mysql -h ECClientIP -P 7979 -u root -p
Enter password: 
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Please let me know, if I can provide any details.

Genpact performs about 40 sec to execute a single query via a client agent in CF (predix)

use-case:
[java app <---> client (cf)] <---> gateway (cf) <---> server (aws)

Suggestion:

• Test the query without agents just to see the performance of the query.
• Test Connection state (Connect/close) without a query.

Follow up:

• How long it takes to send the request from client to server agents
• Execution time for query in HIVE database
• Size of result set from query
• Time taken to send the response data back to client application from target system

Status: Investigating.

x509 certificate issue from UAA in predix CF3

Recent agent cloud foundry deployment indicated an invalid certificate from UAA in the Predix Cloud Fooundry instance (CF3) that it has been causing failures in agent deployment.

Please contact https://www.predix.io/support/ @support group for further details.

Issue: Windows CF Push does not work (unknown port error)

Issue: Windows users experience issues for assigning dynamic port through cf push (GC gateway)

Solution::
You may be able to get a successful GW Agent connection by skipping bash entirely, and executing the Agent directly as the yml command. I suspect this is worthy of note as a work-around when ecagent gives an “unknown port” error while attempting to creating EC GW

---

applications:

• name: Application_Name
  memory: 1G
  instances: 1
  stack: cflinuxfs2
  path: .
  command: ./ecagent_linux_sys -mod <> -rht "<>" -aid <> -grp <> -tkn <> -gpt "${PORT}" -zon <> -sst "<>" -rpt "<>"
  buildpacks:
  • https://github.com/cloudfoundry/binary-buildpack.git
    service: econnect-test4

AWS gateway with 1725 beta version with proxy settings

Agent new beta version 1725 released to handle proxy settings for connecting to gateway URL, EC Service URL and UAA service from agent binary.

Scenario to use the 1725 beta version -

• Subscribe to EC and UAA services in CF3
• Run the AWS gateway in EC2 instance provisioned in US VPC
• Run the server agent in GE on prem machine
• Run the client agent in EC2 instance, provisioned in EU VPC

Where are the internal/external reference docs link for GE Power Engaging?

As a solution engineer I would like to access all links/resources as follows-

1. Rally Stories.
2. AHA Features/Ideas.
3. Repos (Gitlab/Github)
4. Automation (CI/CD)
5. Box.
6. Confluence.
7. Others. etc.

Please advise.

EC Server TLS plug-in loading is not correct

Couple of scenarios

1. When EC server loading for the first time it should check for success of all plug-ins and log that message correctly into EC server logs - when TLS plugin have issues it is still logging a successful TLS plug-in loading message.
   Steps to reproduce: Load TLS normally, Kill EC Server process, then TLS process will remain there for some time, when you restart EC Server with TLS plugin, old TLS and new EC Server is not able to handshake because they do not share the same encryption key. eventually old TLS dies, but the log shows every thing was fine, logs should clearly show there is a problem with the TLS not able to start.

2. if the TLS plug-in process got killed for some reason the parent EC Server process should be monitor/watch frequently and log that information and also should try reloading the TLS plugin
   Steps to reproduce: Load TLS normally, Kill EC Server process, then TLS process will remain there for some time, when you restart EC Server with TLS plugin, old TLS and new EC Server is not able to handshake because they do not share the same encryption key. eventually old TLS dies, then there has to be an attempt from parent process to start the TLS.

3. EC server/health should show there is a plugin loaded as well

FDM POC EC connection Issue

We are trying to connect to an onprem Oracle DB using a common setup used for many oracle connections.While connecting its giving an "EOF while reading from the gateway" and closed network connection.

Steps taken till Now:

1. Checked the VLAN plugin and it is working fine.
2. The target IPs are being added to the local loopback

As seen till now the target server is rejecting the connection.

Certificate Renewal but Why?!

If the earlier certificate valid (April 1 2019 – September 30 2019) can work with all the EC versions, may I know, what is so special about this new certificate? As more than missing cert expiry timing, this new certificate caused more issues.

- How to run Agent in AWS HA

How to deploy the latest gateway agent #212 to a AWS EC2 to achieve HA (High-Availability)? What are the steps/instruction.

Unable to make connections with VLAN

Following is the scenario, I am trying to test with VLAN -

• Run mysql database server in my mac machine
• Deploy gateway in CF3
  • Health
• Run server agent in my mac machine and below is the script -

./ecagent_darwin_sys -mod server \
-aid AFQFVT -grp 4926a01d-c68a-4229-a09c-5b48be117422 \
-cid ###### -client -csc ###### 3000 \
-oa2 https://capitalpoc.predix-uaa.run.aws-usw02-dev.ice.predix.io/oauth/token \
-hst wss://capital-poc-gateway.run.aws-usw02-dev.ice.predix.io/agent \
-zon 4926a01d-c68a-4229-a09c-5b48be117422 -sst https://4926a01d-c68a-4229-a09c-5b48be117422.run.aws-usw02-dev.ice.predix.io \
-rht 172.23.0.72 -rpt 3306 -vln -dbg  

• Run client agent in AWS EC2 linux machine with root user. Here is the client script -

./ecagent_linux_sys -mod client \
-aid Rm0n5s -tid AFQFVT \
-grp 4926a01d-c68a-4229-a09c-5b48be117422 \
-cid ###### -client -csc ######  -dur 3000 \
-oa2 https://capitalpoc.predix-uaa.run.aws-usw02-dev.ice.predix.io/oauth/token \
-hst wss://capital-poc-gateway.run.aws-usw02-dev.ice.predix.io/agent \
-lpt 7979 -rpt 3306  \
-dbg -plg -vln

plugins.yml -

--- 
ec-plugin: 
  vlan: 
    command: ./vln_linux_sys
    ips: 172.23.0.72/32
    status: active

• Using the version 1724 for all agents (Gateway, server and client)
• Installed mysql client in AWS EC2
• Server logs -

[EC Debug] 2019/12/17 13:27:39 []interface {}=>[gateway list exchange called.]
 [EC Debug] 2019/12/17 13:27:39 []interface {}=>[CFRoutingURL:HostName capital-poc-gateway.run.aws-usw02-dev.ice.predix.io Server:hst capital-poc-gateway.run.aws-usw02-dev.ice.predix.io]
 [EC Server] 2019/12/17 13:27:43 [client#Rm0n5s requests connection with the bind id#wn4SWiLH1N.]
 [EC Debug] 2019/12/17 13:27:43 []interface {}=>[map[a1:b4 a2:wn4SWiLH1N a4:Rm0n5s a5:6142a473-7be1-4d51-b69f-ba91e7d20b8d:0] map[6142a473-7be1-4d51-b69f-ba91e7d20b8d:0:0xc000060120] "gwKey" 6142a473-7be1-4d51-b69f-ba91e7d20b8d:0]
 [EC Debug] 2019/12/17 13:27:43 []interface {}=>[[6142a473-7be1-4d51-b69f-ba91e7d20b8d:0]]
 [EC Server] 2019/12/17 13:27:43 [server has been successfully created for clientId#Rm0n5s with bindId#wn4SWiLH1N]
 [EC Server] 2019/12/17 13:27:43 [gateway connection{host=wss://capital-poc-gateway.run.aws-usw02-dev.ice.predix.io/agent, session=SJ6Q2wmoCV,gatewayId=6142a473-7be1-4d51-b69f-ba91e7d20b8d} established for client# Rm0n5s with bindId#wn4SWiLH1N, to VLAN address: 172.23.0.72:3306 if -vln is enabled.]
 [EC Server] 2019/12/17 13:27:43 [websocket is found in the pool for clientId#Rm0n5s]
 [EC Server] 2019/12/17 13:27:43 [successful added resource (172.23.0.72:3306) for clientId#Rm0n5s with bindId#wn4SWiLH1N]
 [EC Server] 2019/12/17 13:27:43 [session# SJ6Q2wmoCV created. client has been picked from the pool. Beginning two-way piping.]
 [EC Server] 2019/12/17 13:27:43 [[successful added resource (172.23.0.72:3306) for clientId#Rm0n5s with bindId#wn4SWiLH1N]]
 [EC Server] 2019/12/17 13:27:43 [connection has been picked up and removed from the pool with bindId#wn4SWiLH1N]
 [EC Server] 2019/12/17 13:27:43 [EOF occurred in tcp server reading. (session# SJ6Q2wmoCV  bind# wn4SWiLH1N )]
 [EC Server] 2019/12/17 13:27:43 [exception occurred in wsocket client reading. err: read tcp 172.23.0.72:63313->52.39.65.162:443: use of closed network connection  (session# SJ6Q2wmoCV  bind# wn4SWiLH1N )]
 [EC Server] 2019/12/17 13:27:43 [session#: SJ6Q2wmoCV has been deleted.]
 [EC Server] 2019/12/17 13:27:43 [session#: SJ6Q2wmoCV has been deleted.]

• Client logs -

[EC Debug] 2019/12/17 18:27:42 []interface {}=>[172.23.0.72:3306]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[p_fielSize 0xc0004e0000]
 [EC Client] 2019/12/17 18:27:43 [client#Rm0n5s connection is pending for a confirmation from the gateway]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[entering thread# 40]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[d {"a1":"b1","a2":"wn4SWiLH1N"}]
 [EC Client] 2019/12/17 18:27:43 [connection request has been received by the gateway with the bindId#wn4SWiLH1N]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[d {"a1":"b3","a3":"SJ6Q2wmoCV","a2":"wn4SWiLH1N"}]
 [EC Client] 2019/12/17 18:27:43 [connection is established with the session Id#SJ6Q2wmoCV]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[begining two-way binding for bind# wn4SWiLH1N session# SJ6Q2wmoCV]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[entering thread# 23]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[EOF occurred whilst reading from the requestor. (session# SJ6Q2wmoCV bind# wn4SWiLH1N )]
 [EC Client] 2019/12/17 18:27:43 [agent exiting TCP_REQUEST.]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[exiting thread# 23]
ERROR 1044 (42000):  [EC Client] 2019/12/17 18:27:43 [bind#: wn4SWiLH1N has been removed from the pool.]
Access denied for user 'root'@'172.23.0.72' to database '3306' [EC Debug] 2019/12/17 18:27:43 []interface {}=>[exception occurred whilst reading from the gateway. mType: -1 err: read tcp 172.31.252.136:54336->52.34.94.2:443: use of closed network connection]
 [EC Client] 2019/12/17 18:27:43 [agent exiting TCP_REQUEST.]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[exiting thread# 40]
 [EC Client] 2019/12/17 18:27:43 [bind#: wn4SWiLH1N has been removed from the pool.]
 [EC Debug] 2019/12/17 18:27:43 []interface {}=>[exiting two-way binding for bind# wn4SWiLH1N session# SJ6Q2wmoCV]
 [EC Client] 2019/12/17 18:27:43 [session#: SJ6Q2wmoCV has been removed from the sessions list.]

Where are the internal/external reference docs link for the GE Capital Engaging?

Can't deploy gateway app to cloud

Hi Support Team,

When I try to push the gateway app with the latest release hokkaido.212, it through the following errors.

Is hokkaido.212 not compatible with our EC service?

Any help would be really appreciated!

2019-11-25T09:49:46.50-0700 [APP/PROC/WEB/0] OUT [EC Agent] main pacakge exception: EC Service is invalid. Contact your EC Service administrator for more detail.

2019-11-25T09:53:18.18-0700 [APP/PROC/WEB/0] OUT [EC Gateway] 2019/11/25 16:53:18 [usage reported.]
2019-11-25T09:53:20.01-0700 [CELL/0] ERR Failed to make TCP connection to port 8080: connection refused
2019-11-25T09:53:20.01-0700 [CELL/0] ERR Timed out after 1m0s: health check never passed.

Connectivity check with beta 1725 version

Following are the scenarios to test with beta 1725 version -

Traditional
Fuse mode server
Fuse mode client
VLAN
TLS

EC Gateway logs doesnt show the correct information on super connection

Super connection is available, however the gateway logs shows the connection is not available.

It would be nice if it would have said tha super connection is established but the agentids or groupId is misconfigured

Gateway Health: https://power-prod-ec-gateway.run.aws-usw02-pr.ice.predix.io/health

2019-03-21T14:55:28.13-0400 [APP/PROC/WEB/1] OUT  [EC Gateway] 2019/03/21 18:55:28 [github.build.ge.com/212359746/wzcore.(*Gateway).ECRequest.func1 superconn associated with server agent#eaiLdj could not be found.]

Agent+VLAN Container Usage

Need usage examples for platforms using Mody (linux cgroup)

Agent websocket compression negotiation failed in file transfer

Usage reported by Simran (Simran- please provide your public github id) the websocket compression -cps setting failed during the file transfer. Investigating the cause.

Gateway and server agents are not reachable after agent migration

Gateway, server and client agents are migrated to new version (212). After migration, Gateway started giving the error "Superconn associated with server agent#XXXXX could not be found". Similarly server agent is unable to find the gateway app and showing empty glist.

When deploy a client agent in a EC2 instance inside Power VPC, Will it work?

GE Capital VLAN Use case PoC

Help the team to establish end-to-end connectivity for Oracle SCAN db, based on this README

Test EC connectivity with AWS gateway between VPC to VPC

Test the EC connectivity with following scenario -

Deploy EC gateway in VPC1. Run the EC server and connected to a RDS database in the same or different VPC

Deploy EC client and in EC2 instance from another VPC and test the connectivity

Genpact Connectivity Usecase between AWS FDL Database and Predix SCx application

Latest-

1. The deployment script has been provided to the team.
2. The team is working on testing the script.

EC Logs understanding

Hi Team,

We experienced EC for Digital Prod went down this weekend and the error we received in EC Server logs as below.

[github.build.ge.com/212359746/wzcore.(*Server).Hire.func2.1 interface conversion: interface {} is nil, not string].

Just FYI we also has Cloud foundary outage this weekend. Please help us understand when do we receive such errors because with this error EC Server went down.

Regards.,
Simran

Who is involved in this Engagement? What are the contacts?

As a potential customer, who are the contacts of interest upon this project?

Agent OCI Container Usage

Need usage examples for platforms using Mody (linux cgroup)

Bug: Inability to run pprof in agents

We are not able to run pprof with the agent in Client/Server/GW mode.
Provide documentation on how to run this

Scripts: Provide an easy way to generate all scripts required for EC connectivity (GW , Server, Client) with a simple bash/python script

Provide a Bash/Python script to generate the standard scripts after service creation to make it easy for customer to adapt EC

- Create separate AWS subnets and security group comps for deployment purpose

Moving the xcalr auto-deployment to the us-east-1. Need the ability to demonstrate the deployment in the designated az.

Current status:

• all subordinated AWS comps from the automation were still with a wrong az (ohio east)
• Updated aws subnets/security group for the "us-east-1" deployment purpose.

links to build.ge

there are links to build.ge github

- Usage Validation Enhancement

Current validation process is painfully long.

Create a background validation process to 1) fetch the group information 2) persist the group information in memory.

Failed in Restage/Restart Agents deployed in Predix Cloud Foundry CF1

Some reports indicate as of today (Oct-10-2019) that when restarting agents, the Cloud Foundry would raise exception as following-

Our initial assessment is that the Cloud Foundry stack may not be compatible with the latest binary servicepack. This is an ongoing issue.

Procure hardware for testing EC connections

Follow up with Power team to acquire following hardware and software -

• EC2 instances for running the EC agents in different VPC's
• Install mysql client in one VPC
• Information to test the connection

Procure hardware for testing EC connections

Connection requests may stuck with the client/gw:client mode when an unknown issue takes place

A recent report indicates that whilst launch agent as the client mode, requestor app/software may become dormant when an unexpected exception received, resulting the request prematurely left the TCP->HTTP binding, subsequently immobilise the requestor.