cisco.iosxr
community-topics
| cisco.iosxr | community-topics | |
|---|---|---|
| 3 | 60 | |
| 65 | 34 | |
| - | - | |
| 8.0 | 5.0 | |
| 11 days ago | 3 days ago | |
| Python | Shell | |
| 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)
community-topics
-
The Bullhorn #115 (Ansible Newsletter)
There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.
-
The Bullhorn #114 (Ansible Newsletter)
As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.
-
The Bullhorn #108 (Ansible Newsletter)
2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)
-
The Bullhorn #107 (Ansible Newsletter)
Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.
-
The Bullhorn #106 (Ansible Newsletter)
Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.
-
The Bullhorn #105 (Ansible Newsletter)
It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.
-
The Bullhorn #104 (Ansible Newsletter)
The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.
-
The Bullhorn #103 (Ansible Newsletter)
As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.
-
The Bullhorn #101 (Ansible Newsletter)
2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)
-
The Bullhorn #100 (Ansible Newsletter)
Work continues combining several pytest plugins for ansible.
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
cisco.ios - Ansible Network Collection for Cisco IOS
cisco.nxos - Ansible Network Collection for Cisco NXOS
ansible.netcommon - Ansible Network Collection for Common Code
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.
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.
openvswitch.openvswitch - Ansible Network Collection for Open vSwitch
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
junipernetworks.junos - Ansible Network Collection for Juniper JunOS
ansible-navigator - A text-based user interface (TUI) for Ansible.