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

onPremise requirements #3

Open
dderichswei opened this issue Feb 21, 2022 · 5 comments
Open

onPremise requirements #3

dderichswei opened this issue Feb 21, 2022 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@dderichswei
Copy link
Contributor

dderichswei commented Feb 21, 2022

With onPremise deployments like Baremetal, oVirt, VMware, HyperV we also need to support existing infrastructure components like AD/LDAP/PROXY/DNS/NTP...., right?

@dderichswei dderichswei added the enhancement New feature or request label Feb 21, 2022
@erdincka
Copy link
Contributor

I'd go with the most common scenario; assume there is DHCP/DNS, use AD/LDAP with optional selection (deploy your own or provide the server and DNs) and use public NTP (assuming internet access possible).

@erdincka
Copy link
Contributor

Making everything as option/selection will make the scripts complicated, instead I'd try to keep these as variables so making them options becomes easier later.

@dderichswei
Copy link
Contributor Author

I understand that we want to make it as simple as possible, on the other hand we also need a way to customize the different environments and parameters.

At the moment I have no idea how to implement this easily, ex. I found some hardcoded information like LDAP in Ansible!
I would recommend that we outsource these things in a separate config folder/config file and make it configurable for the deployment if required.

@erdincka
Copy link
Contributor

I totally agree to make these parameterised. Let me know what is the best way and I can work on that. Or if you already had these separated, we can replace them in place.

@erdincka
Copy link
Contributor

I am testing a way to provide additional parameters directly into the ansible inventory file, and it works for VMWare deployment now. We can expand this to all targets.
So the playbooks can check if a variable exist (such as http_proxy) and then run the necessary tasks.

@erdincka erdincka self-assigned this May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants