Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide status information about OpenTOSCA components #29

Open
kleinech opened this issue Jul 6, 2017 · 0 comments
Open

Provide status information about OpenTOSCA components #29

kleinech opened this issue Jul 6, 2017 · 0 comments

Comments

@kleinech
Copy link
Contributor

kleinech commented Jul 6, 2017

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:

  1. ssh user@openstackVM
  2. git clone https://github.com/OpenTOSCA/opentosca-dockerfiles.git && cd opentosca-dockerfiles
  3. sudo docker-compose build
  4. sudo docker-compose up
  5. open :8088
  6. Upload New Application
  7. Provision New Instance
  8. 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant