search

opendevstack / ods-core

The core of OpenDevStack - infrastructure setup based on Atlassian tools, Jenkins, Nexus, SonarQube and shared images
Apache License 2.0
47 stars 34 forks source link

Local installation: hostenames should be configurable #205

Open stefanlack opened 4 years ago

stefanlack commented 4 years ago

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

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 commented 4 years ago

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

metmajer commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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!