Making the ip non mandatory in the opsi backend plugin when people don 't manage dns and dhcp with opsi
Making the ip non mandatory in the opsi backend plugin when people don 't manage dns and dhcp with opsi
Description
opsi way of working
on opsi you can create client without ip and without mac foolowing the configuration of your opsi server.
as the mac is not mandatory in FusionDirectory, the only aspect that is divergent from opsi is the forced ip address in FusionDirectory
Description of the Change
look for the draft specs and ideas here https://gitlab.fusiondirectory.org/fusiondirectory/fd-plugins/wikis/OPSI-ip-issues
Cheers
Activity
added technical discussion label
OPSI needs the FQDN. What we are doing now is we search for an A record matching the IP of the system in a DNS zone. If the system has no IP, Argonaut will need some other way to guess the FQDN. My proposition is to use the cn and the DNS zone linked in the DNS tab. If the computer has cn foo and is linked to DNS zone example.com the fqdn will be foo.example.com.
ok this mean we could always use the method described here, for argonaut opsi to work.
My proposition is to use the cn and the DNS zone linked in the DNS tab. If the computer has cn foo and is linked to DNS zone example.com the fqdn will be foo.example.com.
we will only need then
- A system with opsi tab
- A link to dns for the system
did i understand right ?
Edited by bmortierokay, so we use the new methode with the dns linked zone in case with and without ip
Edited by bmortier
-
It bugs me is having the IP field mandatory only in some cases, we should put it either mandatory for all systems or none, or have an option in the configuration back-end. If it’s non-mandatory by default we can make it mandatory when some tabs are activated (argonautClient for instance needs it).
What do you think?
hello,
you are right its historical and we never go a good solution. I propose :
- Make it non mandatory by default, code wise.
- Have an option in configuration back-end for each of the plugin thats need ip address.
- Active the option by default, to not change the fonctional usage of people already using it but allowing people to change it if needed.
What do you think ?
-
I agree to make it a configuration option since we changed this too many times already. Do you think we should have one option for each type having the IP field? (server/workstation/terminal and so on?) I would go for a multi-valuated configuration field listing the types for which IP is mandatory.
Note that ipHost have the field ipHostNumber as mandatory so we’ll need to add code to remove this objectClass when the field is empty. This is already what we are doing for phones.
Edited by Côme Chilliet Hello,
system change have been moved to #5705 (closed)
added plugin-systems and removed plugin-opsi labels
added plugin-opsi label
removed plugin-systems label
added Changed and removed technical discussion labels
