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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+24-2Lines changed: 24 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,27 @@
2
2
All notable changes to this project will be documented in this file.
3
3
This project adheres to [Semantic Versioning](http://semver.org/).
4
4
5
+
## [1.1.0] - 2016-02-12
6
+
### Added
7
+
- Extended cisco_interface (@robert-w-gries)
8
+
- encapsulation dot1q
9
+
- mtu
10
+
- switchport trunk allowed vlan
11
+
- switchport trunk native vlan
12
+
- vrf member
13
+
- Travis-CI integration, currently running Rubocop and Foodcritic validation (@glennmatthews)
14
+
- Documentation workflow map to guide users, developers, and maintainers to the proper docs (@mikewiebe)
15
+
- Doc updates for examples, templates, and install instructions (@chrisvanheuveln)
16
+
- Test Kitchen integration (@adamleff, @edolnx)
17
+
- Serverspec tests (@adamleff)
18
+
- Added support for Chef 12.6.0 (@adamleff)
19
+
- Updated documentation with platform support for providers and required software versions (@robert-w-gries)
20
+
21
+
### Fixed
22
+
- Code changes to satisfy Rubocop. (@glennmatthews)
23
+
- Updated cisco ohai plugin to use correct load path for vendor gems (Alex Hunsberger)
24
+
- Cleaned up demo recipes for N5k, N6k, and N7k platforms (@robert-w-gries)
25
+
5
26
## [1.0.1] - 2015-09-21
6
27
### Fixed
7
28
- Fixed broken documentation links.
@@ -24,6 +45,7 @@ This project adheres to [Semantic Versioning](http://semver.org/).
24
45
- Initial release of cisco-cookbook for chef, supporting Cisco NX-OS software release 7.0(3)I2(1) on Cisco Nexus switch platforms: N95xx, N93xx, N30xx and N31xx.
25
46
- Please note: 0.9.0 is an EFT pre-release for a limited audience with access to NX-OS 7.0(3)I2(1). Additional code changes may occur in 0.9.x prior to the final 1.0.0 release.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,14 @@ Cisco Network Elements support a rich set of features to make network robust, ef
4
4
## Getting Started
5
5
6
6
* Create a [GitHub account](https://github.com/signup/free)
7
-
* Create a [cisco.com](http://cisco.com) account if you need access to a Network Simulator to test your code.
7
+
* 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 <get-n9kv@cisco.com>. 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)
8
+
8
9
9
10
## Making Changes
10
11
11
12
* Fork the repository
12
13
* Pull a branch under the "**develop**" branch for your changes.
13
-
* Follow all guidelines documented in [README-develop-resources-providers.md](docs/README-develop-resources-providers.md)
14
+
* Follow all guidelines documented in [README-develop-resources-providers.md](docs/README-develop-resources-providers.md)
14
15
* Make changes in your branch.
15
16
* Testing
16
17
* Run all the tests to ensure there was no collateral damage to existing code.
@@ -24,6 +25,12 @@ Cisco Network Elements support a rich set of features to make network robust, ef
24
25
* Submit a pull request to the repository
25
26
* A core team consisting of Cisco and Chef Inc employees will review your pull request and provide feedback.
26
27
* After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.
28
+
* All code commits must be associated with your github account and email address. Before committing any code use the following commands to update your workspace with your credentials:
0 commit comments