1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
|
%global _empty_manifest_terminate_build 0
Name: python-net-contextdiff
Version: 0.15.12
Release: 1
Summary: Compare network device configuration files using contextual structures
License: MIT License
URL: https://gitlab.developers.cam.ac.uk/uis/netsys/udn/net-contextdiff
Source0: https://mirrors.aliyun.com/pypi/web/packages/92/4e/de14b7bea859224c782f2ab293aaf2a4eb3a8f8beda50e7b7273a93764c0/net-contextdiff-0.15.12.tar.gz
BuildArch: noarch
Requires: python3-deepops
Requires: python3-netaddr
%description
This package contains two main elements used to compare text-based
configuration files (or other files in simple text in a similar format) where
they are structured using indented blocks of directives/commands, typically for
network devices:
* a parser to read in configuration files and stored them in a dictionary --
the parser utilises the hierarchical nature of the configuration to
understand that the same command name might mean different things in
different contexts
* a comparator that takes two configuration dictionaries (typically produced by
the parser, above) - a source and a target configuration - and writes out
a configuration file (or update command set) to transform the source
configuration into the destination - this uses a series of 'converters' to
handle the difference for each configuration element (e.g. changing the
description assigned to an interface)
Each of these are written as abstract base classes that can be inherited from
to crete concrete classes for each platform, but the base processing of the
parsing and comparing should be consistent, requiring only the specific
commands to be handled.
Currently, Cisco IOS is the only concrete platform and only a subset so far
(the comparator is still being tweaked to handle this all relatively
straightforwardly, before all the commands are implemented). There are
currently some odd commands and edge cases which are awkward to handle without
some improvements to the core process.
The scripts also support a system whereby 'excludes' can be specified, to
exclude those elements of the configuration dictionary which should not be
compared, if a known difference exists that cannot be resolved, either as an
interim divergence, or a permanent exception.
%package -n python3-net-contextdiff
Summary: Compare network device configuration files using contextual structures
Provides: python-net-contextdiff
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-net-contextdiff
This package contains two main elements used to compare text-based
configuration files (or other files in simple text in a similar format) where
they are structured using indented blocks of directives/commands, typically for
network devices:
* a parser to read in configuration files and stored them in a dictionary --
the parser utilises the hierarchical nature of the configuration to
understand that the same command name might mean different things in
different contexts
* a comparator that takes two configuration dictionaries (typically produced by
the parser, above) - a source and a target configuration - and writes out
a configuration file (or update command set) to transform the source
configuration into the destination - this uses a series of 'converters' to
handle the difference for each configuration element (e.g. changing the
description assigned to an interface)
Each of these are written as abstract base classes that can be inherited from
to crete concrete classes for each platform, but the base processing of the
parsing and comparing should be consistent, requiring only the specific
commands to be handled.
Currently, Cisco IOS is the only concrete platform and only a subset so far
(the comparator is still being tweaked to handle this all relatively
straightforwardly, before all the commands are implemented). There are
currently some odd commands and edge cases which are awkward to handle without
some improvements to the core process.
The scripts also support a system whereby 'excludes' can be specified, to
exclude those elements of the configuration dictionary which should not be
compared, if a known difference exists that cannot be resolved, either as an
interim divergence, or a permanent exception.
%package help
Summary: Development documents and examples for net-contextdiff
Provides: python3-net-contextdiff-doc
%description help
This package contains two main elements used to compare text-based
configuration files (or other files in simple text in a similar format) where
they are structured using indented blocks of directives/commands, typically for
network devices:
* a parser to read in configuration files and stored them in a dictionary --
the parser utilises the hierarchical nature of the configuration to
understand that the same command name might mean different things in
different contexts
* a comparator that takes two configuration dictionaries (typically produced by
the parser, above) - a source and a target configuration - and writes out
a configuration file (or update command set) to transform the source
configuration into the destination - this uses a series of 'converters' to
handle the difference for each configuration element (e.g. changing the
description assigned to an interface)
Each of these are written as abstract base classes that can be inherited from
to crete concrete classes for each platform, but the base processing of the
parsing and comparing should be consistent, requiring only the specific
commands to be handled.
Currently, Cisco IOS is the only concrete platform and only a subset so far
(the comparator is still being tweaked to handle this all relatively
straightforwardly, before all the commands are implemented). There are
currently some odd commands and edge cases which are awkward to handle without
some improvements to the core process.
The scripts also support a system whereby 'excludes' can be specified, to
exclude those elements of the configuration dictionary which should not be
compared, if a known difference exists that cannot be resolved, either as an
interim divergence, or a permanent exception.
%prep
%autosetup -n net-contextdiff-0.15.12
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-net-contextdiff -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.15.12-1
- Package Spec generated
|
