Local installation: hostenames should be configurable

[stefanlack]

Is your feature request related to a problem? Please describe. I want to use other hostnames when running the installation locally, e.g. okd instead of openshift

Describe the solution you'd like

• Ask hostnames for all hosts at startup (defaults to hostnames used so far)
• store hostnames in ods-configuration

Describe alternatives you've considered none

Additional context Hostname are configured in vagrant-file as well.

How can we manage that hostname from env-configuration is in sync with hostnames in Vagrantfile?

[metmajer]

Can this also include external services, such as Jenkins, Bitbucket and Nexus so we can run them in containers?

[metmajer]

@stefanlack since we'll depend on local installations internally in the near future, it would be great if you could share some thoughts. Also, did you consider a completely hands-free installation that takes installation parameters either from some slim parameters file or the ods-configuration?

[rattermeyer]

Depends on what you want to install. Completely hands-free is currently not possible due to Atlassian. Or we need to think about if we want to use python-mechanize to drive the UI. It depends on how stable we think the Atlassain UI is. Otherwise it would be possible today. And also see #93 that further addresses the issues.

[metmajer]

Thanks for chiming in @rattermeyer. We‘re currently looking into the Atlassian problem you‘re mentioning since we need to automatically test self-written Jira Plugins. Here, Jira would run in an ephemeral container. I would assume Bitbucket to work similarly once we have a solution. Web UI automation could be one path forward, although, as you state yourself, not the most stable one. I‘ll keep you posted!