You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Major refactor and enhancement of `CommandReference` YAML files:
120
+
- Added support for `auto_default`, `default_only`, `kind`, and `multiple`
121
+
- Added filtering by product ID (`/N7K/`) and by client type (`cli_nexus`)
122
+
-`CommandReference` methods that do key-value style wildcard substitution now raise an `ArgumentError` if the result is empty (because not enough parameters were supplied).
123
+
4
124
## [v1.1.0]
5
125
6
126
### New feature support
@@ -15,10 +135,12 @@ Changelog
15
135
* RADIUS
16
136
* radius_global (@jonnytpuppet)
17
137
* radius_server (@jonnytpuppet)
138
+
* SNMP
139
+
* snmp_notification_receiver (@jonnytpuppet)
18
140
* SYSLOG
19
141
* syslog_server (@jonnytpuppet)
20
142
* syslog_setting (@jonnytpuppet)
21
-
* Miscellaneous
143
+
* Miscellaneous
22
144
* dns_domain (@hunner)
23
145
* domain_name (@bmjen)
24
146
* name_server (@hunner)
@@ -43,6 +165,8 @@ Changelog
43
165
* Added `config` and `(assert|refute)_show_match` helper methods for testing.
44
166
* Added `bin/check_metric_limits.rb` helper script in support of refactoring.
45
167
* Added best practices development guide.
168
+
* Added support for radius_global (@jonnytpuppet)
169
+
* Added support for radius_server_group (@jonnytpuppet)
Copy file name to clipboardexpand all lines: README.md
+19-12
Original file line number
Diff line number
Diff line change
@@ -35,10 +35,23 @@ Please see [Learning Resources](#resources) for additional references.
35
35
36
36
The CiscoNodeUtils gem provides utilities for management of Cisco network
37
37
nodes. It is designed to work with Puppet and Chef as well as other
38
-
open source management tools. This release supports Cisco NX-OS nodes
39
-
running NX-OS 7.0(3)I2(1) and later.
38
+
open source management tools.
40
39
41
-
Please note: A virtual Nexus N9000/N3000 may be helpful for development and testing. Users with a valid [cisco.com](http://cisco.com) user ID can obtain a copy of a virtual Nexus N9000/N3000 by sending their [cisco.com](http://cisco.com) user ID in an email to <[email protected]>. If you do not have a [cisco.com](http://cisco.com) user ID please register for one at [https://tools.cisco.com/IDREG/guestRegistration](https://tools.cisco.com/IDREG/guestRegistration)
40
+
This CiscoNodeUtils gem release supports the following:
41
+
42
+
Platform | OS | OS Version |
43
+
-----------------|-------|----------------------|
44
+
Cisco Nexus 30xx | NX-OS | 7.0(3)I2(1) and later
45
+
Cisco Nexus 31xx | NX-OS | 7.0(3)I2(1) and later
46
+
Cisco Nexus 93xx | NX-OS | 7.0(3)I2(1) and later
47
+
Cisco Nexus 95xx | NX-OS | 7.0(3)I2(1) and later
48
+
Cisco N9kv | NX-OS | 7.0(3)I2(1) and later
49
+
Cisco Nexus 56xx | NX-OS | 7.3(0)N1(1) and later
50
+
Cisco Nexus 60xx | NX-OS | 7.3(0)N1(1) and later
51
+
Cisco Nexus 7xxx | NX-OS | 7.3(0)D1(1) and later
52
+
53
+
54
+
Please note: For Cisco Nexus 3k and 9k platforms, a virtual Nexus N9000/N3000 may be helpful for development and testing. Users with a valid [cisco.com](http://cisco.com) user ID can obtain a copy of a virtual Nexus N9000/N3000 by sending their [cisco.com](http://cisco.com) user ID in an email to <[email protected]>. If you do not have a [cisco.com](http://cisco.com) user ID please register for one at [https://tools.cisco.com/IDREG/guestRegistration](https://tools.cisco.com/IDREG/guestRegistration)
42
55
43
56
## <aname="installation">Installation</a>
44
57
@@ -97,15 +110,9 @@ network node. It provides the base APIs `config_set`, `config_get`, and
97
110
98
111
### CommandReference
99
112
100
-
The `CommandReference` module provides for the abstraction of NX-OS CLI,
101
-
especially to handle its variance between hardware platforms.
102
-
A series of YAML files are used to describe the CLI corresponding to a given
103
-
`(feature, attribute)` tuple for any given platform. When a `Node` is
104
-
connected, the platform identification of the Node is used to construct a
105
-
`CmdRef` object that corresponds to this platform. The `Node` APIs
106
-
`config_set`, `config_get`, and `config_get_default` all rely on the `CmdRef`.
113
+
The `CommandReference` class abstracts away the differences between various supported `Node` types, be that API differences (CLI vs. YANG), platform differences (NX-OS vs. IOS XR), or hardware differences (Nexus 9xxx vs. Nexus 3xxx). A series of YAML files describe various `feature` groupings. Each file describes a set of `attributes` of the given feature and the specifics of how to inspect and manage these attributes for any supported `Node` types. When a `Node` is connected, the platform identification of the Node is used to construct a `CommandReference` instance containing a set of `CmdRef` objects specific to this `Node`. The `Node` APIs `config_set`, `config_get`, and `config_get_default` all rely on the `CmdRef`.
107
114
108
-
See also [README_YAML](lib/cisco_node_utils/README_YAML.md).
115
+
See also [README_YAML](lib/cisco_node_utils/cmd_ref/README_YAML.md).
109
116
110
117
### Feature Providers
111
118
@@ -161,7 +168,7 @@ See [CHANGELOG](CHANGELOG.md) for a list of changes.
161
168
## <aname="license_info">License Information</a>
162
169
163
170
164
-
Copyright (c) 2013-2015 Cisco and/or its affiliates.
171
+
Copyright (c) 2013-2016 Cisco and/or its affiliates.
165
172
166
173
Licensed under the Apache License, Version 2.0 (the "License");
167
174
you may not use this file except in compliance with the License.
0 commit comments