External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-11 12:25:52 +00:00
Code Issues Packages Projects Releases Wiki Activity
f1a950379d
libvirt/tests/nssdata/virbr0.status

33 lines
815 B
Plaintext
Raw Normal View History

nss: Introduce a test A small test to see how is the nss module working. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-02-15 13:02:05 +00:00
[
{
"ip-address": "192.168.122.197",
"mac-address": "52:54:00:a4:6f:91",
"hostname": "fedora",
libvirt_nss: Report newer addresses first Ideally, a software that's translating domain names would iterate over all addresses the NSS returned, but some software does not bother (e.g. ping). What happens is that for instance when installing a guest, it's assigned one IP address but once it's installed and rebooted it gets a different IP address (because client ID used for the first DHCP traffic when installing the guest was generated dynamically and never saved so after reboot the guest generated new ID which resulted in different IP address to be assigned). This results in 'ping $domain' not working properly as it still pings the old IP address. Well, it might - NSS plugin does not guarantee any order of addresses. To resolve this problem, we can sort the array just before returning it to the caller (ping) so that the newer IP addresses come before older ones. Reported-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2019-07-10 12:30:11 +00:00
"expiry-time": 1900000002
nss: Introduce a test A small test to see how is the nss module working. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-02-15 13:02:05 +00:00
},
{
"ip-address": "192.168.122.198",
"mac-address": "52:54:00:a4:6f:92",
"hostname": "fedora",
libvirt_nss: Report newer addresses first Ideally, a software that's translating domain names would iterate over all addresses the NSS returned, but some software does not bother (e.g. ping). What happens is that for instance when installing a guest, it's assigned one IP address but once it's installed and rebooted it gets a different IP address (because client ID used for the first DHCP traffic when installing the guest was generated dynamically and never saved so after reboot the guest generated new ID which resulted in different IP address to be assigned). This results in 'ping $domain' not working properly as it still pings the old IP address. Well, it might - NSS plugin does not guarantee any order of addresses. To resolve this problem, we can sort the array just before returning it to the caller (ping) so that the newer IP addresses come before older ones. Reported-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2019-07-10 12:30:11 +00:00
"expiry-time": 1900000001
nss: Introduce a test A small test to see how is the nss module working. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-02-15 13:02:05 +00:00
},
{
"ip-address": "192.168.122.254",
"mac-address": "52:54:00:3a:b5:0c",
"hostname": "gentoo",
"expiry-time": 2000000000
nss: Introduce libvirt-guest module So far the NSS module looks up only hostnames as provided by guests themselves. However, there are some cases where this is not enough: e.g. when there's a fresh new guest being installed (with some generic hostname) say from a live ISO image; or some (older) systems don't advertise their hostname in DHCP transactions at all. In cases like that it would be helpful if we translate domain name as seen by libvirt too so that users can: # virsh start $dom && ssh $dom In order to achieve that new libvirt-guest module is introduced, while older libvirt module maintains its current behaviour (that is translating guest provided names into IP addresses). Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-11-29 12:48:53 +00:00
},
{
"ip-address": "192.168.122.2",
"mac-address": "52:54:00:11:22:33",
"expiry-time": 2000000000
nss: handle leases with infinite expiry time After v6.3.0-rc1~64 a lease can have infinite expiry time. This means that the expiration time will appear as a value of zero. Do the expiration check only if the expiration time is not zero. Fixes: 97a0aa246799c97d0a9ca9ecd6b4fd932ae4756c Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2020-12-18 15:09:16 +00:00
},
{
"ip-address": "192.168.122.3",
"mac-address": "52:54:00:a4:6f:91",
"hostname": "fedora",
"client-id": "01:52:54:00:a4:6f:91",
"expiry-time": 0
nss: Introduce a test A small test to see how is the nss module working. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-02-15 13:02:05 +00:00
}
]
Reference in New Issue Copy Permalink