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

Improve pre-flight check to verify all necessary ports are available #480

Closed
3 tasks
dmytro-ndp opened this issue Jul 28, 2016 · 2 comments
Closed
3 tasks

Comments

@dmytro-ndp
Copy link
Contributor

Pre-Flight Checks Specification

The biggest area where new installations are failing is around networking configuration. Sometimes, certain networking elements cannot be verified easily.

  • Verify all necessary ports are open. Another page discussing this. We may need to have a simple bash service which launches a server listening on the port and then launches a client to connect to that port. There is this description of nmap. There is also this description. Since the ephemeral port range is very large, we only need to verify that a couple of the ports are open - a sampling.
  • Output of the pre-flight checks. This will appear after we test access to the repositories.
http://mirrorlist.centos.org                                   [OK]

Verifying ports...
22:           SSH (installation)                               [OK / NOT OK]
80:           HTTP                                             [OK / NOT OK]
81:           HAProxy (workspace routing)                      [OK / NOT OK]
443:          HTTP/s                                           [OK / NOT OK]
444:          HAProxy/s                                        [OK / NOT OK]
32768-65535:  Docker                                           [OK / NOT OK]

If there are checks that fail for the port opening, then:

Some mandatory ports are not open. Codenvy may not work properly.
You can test open ports with ` ... `.  
Proceed with the installation? [y/N]
  • If the --suppress flag is provided, then all checks will be ignored and the installation should proceed normally.
@TylerJewell
Copy link
Contributor

@dmytro-ndp - hi! With this improvement, we no longer need to check port 444.
#869

@TylerJewell
Copy link
Contributor

Replaced with dockerized solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants