Current Behavior:
Starting OpenTOSCA inside docker containers on openstack vms takes up to 35min (wso2server.sh).
If the user starts provisioning new instances before all OpenTOSCA components are ready org.opentosca.container.connector.bps.BpsConnector.login fails.
Expected Behavior:
The user should be informed about the status of all OpenTOSCA components and provisioning new instances of applications must be blocked until all components are ready.
Steps to Reproduce:
- ssh user@openstackVM
- git clone https://github.com/OpenTOSCA/opentosca-dockerfiles.git && cd opentosca-dockerfiles
- sudo docker-compose build
- sudo docker-compose up
- open :8088
- Upload New Application
- Provision New Instance
- Error
Other Information:
- Possible Solution: Analyze log files
StartupFinalizerServiceComponent - WSO2 Carbon started in 64 sec or test org.opentosca.container.connector.bps.BpsConnector.login
- Block
Provision New Instance until all OpenTOSCA components are ready
- Additional: Test if components work properly (BSP server available + Docker-Container-component can create new container with dns working)
System Information:
- Openstack VM:
- image: ubuntu-16.04-LTS-xenial-server-cloudimg
- flavor: m1-lager( 8VCPUs, 16Gb RAM)
Current Behavior:
Starting OpenTOSCA inside docker containers on openstack vms takes up to 35min (wso2server.sh).
If the user starts provisioning new instances before all OpenTOSCA components are ready
org.opentosca.container.connector.bps.BpsConnector.loginfails.Expected Behavior:
The user should be informed about the status of all OpenTOSCA components and provisioning new instances of applications must be blocked until all components are ready.
Steps to Reproduce:
Other Information:
StartupFinalizerServiceComponent - WSO2 Carbon started in 64 secor testorg.opentosca.container.connector.bps.BpsConnector.loginProvision New Instanceuntil all OpenTOSCA components are readySystem Information: