cisco.iosxr
overview
| cisco.iosxr | overview | |
|---|---|---|
| 3 | 12 | |
| 65 | 246 | |
| - | 1.2% | |
| 8.0 | 3.7 | |
| 11 days ago | 1 day ago | |
| Python | ||
| GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cisco.iosxr
-
The Bullhorn #108 (Ansible Newsletter)
cisco.iosxr has been released with new features (changelog).
-
The Bullhorn #100 (Ansible Newsletter)
We're happy to announce the following networking collection updates: * cisco.iosxr 5.0.2 has been released with a fix to iosxr_interfaces (changelog) * junipernetworks.junos 5.1.0 has been released with bugfixes and a new feature for junos_package (changelog) * openvswitch.openvswitch 2.1.1 has been released with documentation updates (changelog)
-
The Bullhorn #62 (Ansible Newsletter)
Two more networking collection announcements: * cisco.iosxr 3.1.0 has been released with new features (changelog) * junipernetworks.junos 3.0.1 has been released with bugfixes (changelog)
overview
-
The Bullhorn #84 (Ansible Newsletter)
As mentioned in last week's Bullhorn issue, cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. A week has passed since the community-topics issue was filed and other SC members confirmed the violation, so a vote has been started (vote ends on 2022-12-16).
-
The Bullhorn #83 (Ansible Newsletter)
cyberark.pas is subject to removal from version 9 of the Ansible community package due to unresolved Collection Requirements violations. Please see community-topics#168 for more information.
-
The Bullhorn #80 (Ansible Newsletter)
The community steering committee has started a vote on whether we should amend the Ansible community package removal process to consider collections with unresolved Collection Requirements violations unmaintained and thus subject to removal. Please see the PR that amends the policy and the community-topics ticket for more information.
-
The Bullhorn #79 (Ansible Newsletter)
The Ansible Community Steering Committee has approved a change to the Collection Requirements re. SCM and release requirements. Collections were always required to tag releases, but we have clarified what tagging actually means. We have also explicitly stated that "collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release." Please see the full change for more information.
-
The Bullhorn #69 (Ansible Newsletter)
We are happy to announce that the ibm.spectrum_virtualize collection has been included in the ansible community package. Thanks to everyone who helped review the collection and thanks to the maintainers for submitting the collection and making it satisfy the Collection requirements!
-
The Bullhorn #62 (Ansible Newsletter)
How? Copy the Review checklist into a discussion and go through it. See the complete example.
-
The Bullhorn #56 (Ansible Newsletter)
We've recently signed off on that process, which you can review here.
-
The Bullhorn #55 (Ansible Newsletter)
Your votes needed! Proposal: merge and adopt the procedures defined in Describe how collections can be removed from the Ansible package. Please vote in this issue (and not in the PR). The vote will close on 2022-04-27.
-
Future of Ansible package
Pros: - Motivation for developers to create new collections which can become a part of Ansible package ("so popular and important in IT world", etc). - Motivation to create content satisfying the collection requirements. - Motivation to maintain included collections to avoid kicking them out from the package "I can't show off with my collection any more..:(" - ...(suggest yours)
-
The Bullhorn #49 (Ansible Newsletter)
We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details
What are some alternatives?
z_ansible_collections_samples - Sample playbooks utilizing Red Hat Ansible Certified Content for IBM Z
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
antsichaut - Antsichaut aims to automate the filling of a changelog.yaml used by antsibull-changelog
docsite - Static HTML and assets for docs.ansible.com
cisco.nxos - Ansible Network Collection for Cisco NXOS
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
tox-ansible - The tox-ansible plugin dynamically creates a full matrix of python interpreter and ansible-core version environments for running integration, sanity, and unit for an ansible collection both locally and in a Github action. tox virtual environments are leveraged for collection building, collection installation, dependency installation, and testing.
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
openvswitch.openvswitch - Ansible Network Collection for Open vSwitch
ansible-borgbase - Ansible modules for managing borgbase SSH keys and repositories
junipernetworks.junos - Ansible Network Collection for Juniper JunOS
community.network - Ansible Community Network Collection