here issue encountering. trying deploy wso2 api manager open source.
can find documenation on how here: https://github.com/wso2/kubernetes-artifacts/tree/master/wso2am
dockerfiles: https://github.com/wso2/dockerfiles/tree/master/wso2am
what did take build docker images required kuberenetes. take these docker images , deploy them ec2 container service.
i update wso2 kuberenetes spec files (controllers) use image pushed ec2 container service.
i go kubernetes: kubernetes-artifacts/wso2am , run "./deploy -d"
it runs wait launch script keeps looping , never "finds" up.
root@aw-kubernetes:~/wso2kubernetes/kubernetes-artifacts/wso2am# ./deploy.sh -d deploying mysql governance db service... service "mysql-govdb" created deploying mysql governance db replication controller... replicationcontroller "mysql-govdb" created deploying mysql user db service... service "mysql-userdb" created deploying mysql user db replication controller... replicationcontroller "mysql-userdb" created deploying apim database service... service "mysql-apim-db" created deploying apim database replication controller... replicationcontroller "mysql-apim-db" created deploying wso2am api-key-manager service... have exposed service on external port on nodes in cluster. if want expose service external internet, may need set firewall rules service port(s) (tcp:32013,tcp:32014,tcp:32015) serve traffic. see http://releases.k8s.io/release-1.3/docs/user-guide/services-firewalls.md more details. service "wso2am-api-key-manager" created deploying wso2am api-store service... have exposed service on external port on nodes in cluster. if want expose service external internet, may need set firewall rules service port(s) (tcp:32018,tcp:32019) serve traffic. see http://releases.k8s.io/release-1.3/docs/user-guide/services-firewalls.md more details. service "wso2am-api-store" created deploying wso2am api-publisher service... have exposed service on external port on nodes in cluster. if want expose service external internet, may need set firewall rules service port(s) (tcp:32016,tcp:32017) serve traffic. see http://releases.k8s.io/release-1.3/docs/user-guide/services-firewalls.md more details. service "wso2am-api-publisher" created deploying wso2am gateway-manager service... have exposed service on external port on nodes in cluster. if want expose service external internet, may need set firewall rules service port(s) (tcp:32005,tcp:32006,tcp:32007,tcp:32008) serve traffic. see http://releases.k8s.io/release-1.3/docs/user-guide/services-firewalls.md more details. service "wso2am-gateway-manager" created deploying wso2am api-key-manager replication controller... replicationcontroller "wso2am-api-key-manager" created waiting wso2am launch on http://172.20.0.30:32013 ....... i tried comment out "/wait-until-server-starts.sh" script , have start everything. still not able access api manager.
could use insight on stuck. have tried can think of.
if on wso2 team or has done out appreciated. theory right maybe never tested deploying aws local setup? wrong.
any appreciated!
edit: adding outputs kubectl logs etc while in loop waiting server come see these things:
root@aw-kubernetes:~# kubectl pods name ready status restarts age mysql-apim-db-b6b0u 1/1 running 0 11m mysql-govdb-0b0ud 1/1 running 0 11m mysql-userdb-fimc6 1/1 running 0 11m wso2am-api-key-manager-0pse8 1/1 running 0 11m also doing kubectl logs shows started properly:
[2016-07-21 18:46:59,049] info - startupfinalizerservicecomponent server : wso2 api manager-1.10.0 [2016-07-21 18:46:59,049] info - startupfinalizerservicecomponent wso2 carbon started in 34 sec [2016-07-21 18:46:59,262] info - carbonuiservicecomponent mgt console url : https://wso2am-api-key-manager:32014/carbon/ [2016-07-21 18:46:59,262] info - carbonuiservicecomponent api publisher default context : http://wso2am-api-key-manager:32014/publisher [2016-07-21 18:46:59,263] info - carbonuiservicecomponent api store default context : http://wso2am-api-key-manager:32014/store
@alex issue in wso2 kubernetes artifacts v1.0.0 release. have fixed in master branch [1].
the problem deployment process trying verify wso2 api-m server sockets using private ip addresses of kubernetes nodes. updated scripts use public/external ip address if available via kubernetes cli. work, may need setup kubernetes on aws according [2].
[1] https://github.com/wso2/kubernetes-artifacts/commit/53cc6979965ebed8800b803bb3454f3b758b8c05 [2] http://kubernetes.io/docs/getting-started-guides/aws/
Comments
Post a Comment