rename resource nitb_iface to ip_address
I would like to use the IP addresses also for OsmoBSC processes, so it is more
than clear now that 'nitb_iface' was the wrong naming choice.
The only distinction we may need in the future is public versus loopback
interface. To add that, we may add a trait to the 'ip_address' resource
like:
ip_address:
- addr: 10.42.42.1
type: public
- addr: 127.0.0.1
type: loopback
This way we can substitute public vs loopback addresses flexibly (e.g. using
scenarios).
Change-Id: I3ad583ae7a33f7a7bb56fe78a125f73c56a0e860
diff --git a/selftest/template_test.ok b/selftest/template_test.ok
index 449bae0..0f896ee 100644
--- a/selftest/template_test.ok
+++ b/selftest/template_test.ok
@@ -12,11 +12,11 @@
!
line vty
no login
- bind val_nitb_iface_addr
+ bind val_ip_address_addr
!
e1_input
e1_line 0 driver ipa
- ipa bind val_nitb_iface_addr
+ ipa bind val_ip_address_addr
network
network country code val_mcc
mobile network code val_mnc
@@ -135,14 +135,14 @@
timeslot 3
phys_chan_config val_phys_chan_config_3
smpp
- local-tcp-ip val_nitb_iface_addr 2775
+ local-tcp-ip val_ip_address_addr 2775
system-id test
policy closed
esme test
password test
default-route
ctrl
- bind val_nitb_iface_addr
+ bind val_ip_address_addr
- Testing: expect to fail on invalid templates dir
sucess: setting non-existing templates dir raised RuntimeError