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

1.12.65: an undefined IP address should be valid for a virtual host in a cluster #127

Open
jouvin opened this issue Nov 2, 2018 · 2 comments

Comments

@jouvin
Copy link
Contributor

jouvin commented Nov 2, 2018

Currently, it is required that an address is declared (either directly or indirectly) for any host. It is not always appropriate, in particular for virtual host hosted by a cluster representing a cloud where the actual address allocation will occur according to the cloud policy defined. It would be good to allow an undefined IP address in this case. It would be up to the user not to configure the network with Quattor in this situation (for example, at LAL we disable ncm-network in virtual machines).

@ned21
Copy link
Contributor

ned21 commented Nov 2, 2018

We might have an upcoming requirement for this too, although we probably want to generalise it to be any host not just a VM. I wasn't aware that the standard schemas allowed it, but if you are using it that way I guess that means AII, et al. will work?

@jouvin
Copy link
Contributor Author

jouvin commented Nov 4, 2018

@ned21 no, we are not using it that way and I am not sure the schema allows it... I need to check. What we do currently, as we always did with VM, is that we disable ncm-network. I think that if ncm-network is disabled, we don't really care if an Ip address is defined, Even for AII it should work if a DHCP address is obtained. But in our case, we don't care about AII with VMs as we don't install them this way.

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

No branches or pull requests

2 participants