4 Commits (1054cb4d74dfd43912a4fe7fc64c7e19f0253069)

Author	SHA1	Message	Date
Guillem Jover	ae4e1f6d3c	TT#39401 Use List::Util in perl core instead of List::MoreUtils ... Change-Id: I20dcc7082b3f56945ec5bf065c92b6b78ffe4fad	8 years ago
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
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
Michael Prokop	3436c08361	Initial checkin	13 years ago