ngcpcfg

Commit Graph

Author	SHA1	Message	Date
Guillem Jover	a4dd0365ef	TT#17650 Switch to use YAML::XS instead of YAML::Tiny The latter does not support YAML 1.1, nor many parts of the specification. Use the more compliant implementation, in addition to try to converge to a single one, so that we do not get serialization delta surprises. Change-Id: Ie51f1c79859d40ef0877fc0ab75f86ee72e14ea4	9 years ago
Guillem Jover	0999539d9c	TT#15450 Further fix POD sections, markup and content Change-Id: I50cce7ac3a967a983ffeafc21409b405b1effe4b	9 years ago
Guillem Jover	a0bdff8ac8	TT#15450 Fix POD sections, markup and content Change-Id: I2527dc3a83e2779250869b1fa2cdd61875745df8	9 years ago
Michael Prokop	4e3703660e	MT#16239 Avoid duplicate IP records (shared_ip/shared_v6ip/advertised_ip) Configuring the identical shared IP once again shouldn't cause duplicate IP records, since e.g. nginx receives two "listen" lines with the same IP and fails hard then. New behaviour with this change is to avoid duplicates: \| root@spce:~# ngcp-network --verbose --set-interface=eth0 --shared-ip=1.2.3.4 \| [...] \| adding IP entry shared_ip: 1.2.3.4 \| [...] \| root@spce:~# ngcp-network --verbose --set-interface=eth0 --shared-ip=1.2.3.4 \| [...] \| not setting shared_ip to 1.2.3.4 to avoid duplicates \| [...] Change-Id: Iee3ff1e7a27bc3298128835468e1e888c327d13d	10 years ago
Michael Prokop	14dbc9d0b8	MT#16719 Support cloning of host sections When setting up carrier environments we have to deal with many similar nodes, often involving >10 proxy pairs. By default we create prx01a and prx01b sections only. Provide --clone-from=<HOST> --clone-to=<HOST> options as convenience helpers so the operator can clone a specific host definition and just needs to adapt IP addresses accordingly afterwards. Use example to clone the prox01a host definition to prox02a, prox03a,.... up to prox10a: for host in {02..10} ; do ngcp-network --clone-from=prx01a --clone-to=prx${host}a done If the peer setting (as used in carrier environments) is present in the source host config (--clone-from=...) then we automatically set the peer for the destination, like: \| # ngcp-network --clone-from=prx01a --clone-to=prx01b \| Setting peer of host 'prx01b' to 'prx01a' \| Finished cloning host section 'prx01a' to 'prx01b'. \| Please do not forget to manually adjust '/etc/ngcp-config/network.yml'! and: \| # ngcp-network --clone-from=prx01a --clone-to=prx04a \| Setting peer of host 'prx04a' to 'prx04b' \| Finished cloning host section 'prx01a' to 'prx04a'. \| Please do not forget to manually adjust '/etc/ngcp-config/network.yml'! Change-Id: I6c30a2ce58dd8bc66247cfdd0028c18736173e99	10 years ago
Alexander Lutay	50b08a355a	MT#11097 Fix warning 'keys on reference is experimental' in ngcp-network Tnx to Rene for pointing! Change-Id: Iac23fd8337b4c58bf52d183906ddc8283a68b14e	11 years ago
Victor Seva	f6f94aef85	MT#11921 Adjust code to satisfy perlcritic/tap-test policies - add libreadonly-perl dependency Change-Id: Ic80ad46275da7edbfaaaade19b5557576a98dcc2	11 years ago
Victor Seva	7065656450	MT#9385 ngcp-network: add --dbnode option Adds 'dbnode' field value checking if the number is already in use Change-Id: I70a8473e6408f327ffd2f2f62a5da6d06745192c	12 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago

9 Commits (a4dd0365efe04d9c3598826152733c491eae90e5)