This proposal outlines the plan to migrate the docs.ansible.com subdomain to Read The Docs. This plan entails steps to create a new subdomain to replace docs.ansible.com on the current web server then migrating the CNAME record to Read The Docs. Additionally this plan outlines specific actions to preserve SEO authority and avoid 404 errors and broken redirects.
Motivation
There are two main driving factors behind the proposed migration of the docs.ansible.com subdomain:
Winding down Red Hat managed infrastructure including the web server and Jenkins jobs to reduce maintenance overhead, AWS spend, and security risk.
Creating a unified space for community documentation in the Ansible ecosystem. The docs.ansible.com subdomain signals the "official" location of trusted content for Ansible users, developers, maintainers, and contributors. At present this applies only to the package docs, core docs, and Ansible automation controller docs, which results in a fragmented experience for community documentation.
Reducing managed infrastructure
At present the content available from docs.ansible.com is served by Apache httpd running on RHEL hosts in an AWS EC2 instance behind Cloudflare. The Ansible engineering organization at Red Hat are responsible for the associated maintenance and infrastructure cost.
Don Naro changed 4 months agoView mode Like Bookmark
This public HackMD is to allow everybody to make notes during Contributor Summit on Wednesday 5th Feb which takes places as part of Configuration Managemenent Camp in Ghent.
Useful links:
Short URL to this page: red.ht/ansible-contributors-summit
Contributor Summit agenda in the forum
Ansible Developer Tools workshop (afternoon session): https://red.ht/ansible-devtools-lab
Live stream: https://www.youtube.com/watch?v=_QzODvwRlog
Warm up discussion
Don Naro changed 4 months agoView mode Like Bookmark
Room : Ansible 1 (B.1.017)
Gundalow: Ansible - State of the Community
Time: 14:00–14:50
Notes
Felix Fontein: Using SOPS to manage secrets in Ansible
Time: 14:50–15:40
Notes
Don Naro changed 5 months agoView mode Like Bookmark
Please update the speakers for the following talks:
Streamlining the Ansible creator experience with the new and improved Ansible Development tools
https://cfp.cfgmgmtcamp.org/ghent2025/talk/EDFRP8/
Speaker: Ganesh B Nalawade
Remove from speaker list: Don Naro
Beyond copy-paste: Using Ansible Development Tools for Robust Automation Content
https://cfp.cfgmgmtcamp.org/ghent2025/talk/GK8THR/
Don Naro changed 7 months agoView mode Like Bookmark
Details for organizing Ansible tracks at Cfgmgmtcamp 2025.
Track one: Monday, Feb 3
Proposed schedule for the first Ansible track on Monday.
Talk one: 50 mins
John "gundalow" Barker
Ansible - State of the Community
https://cfp.cfgmgmtcamp.org/orga/event/ghent2025/submissions/RY9YZU/
Status: Confirmed
Don Naro changed 7 months agoView mode Like Bookmark
This document outlines a proposal to create redirects in the ansible project on Read The Docs. The ansible project is the top-level namespace for Ansible project documentation that includes the Ansible package docs, ansible-core docs, as well as docs for projects across the Ansible ecosystem.
The purpose of creating redirects in the ansible project on Read The Docs is to facilitate the migration of the docs.ansible.com subdomain from Red Hat managed infrastructure to Read the Docs hosting. By doing this we can prevent 404 errors that would cause SEO degradation.
Redirects on Read The Docs
Read The Docs hosting provides a built-in redirect system that has a limit of 100 user-defined redirects on Read The Docs per project. For more details, refer to the User Defined Redirects section of the Read The Docs documentation.
To be equivalent to root pages on docs.ansible.com subdomain, the details in this plan concern redirects in the top-level Ansible project only.
There are approximately 30 redirects in this proposal to create in the ansible project on Read The Docs. At the moment, there are seven redirects that already exist in the project. This is well within the limit of 100 redirects and ensures we have enough capacity for additional redirects.
Don Naro changed 8 months agoView mode Like Bookmark
This document outlines a proposal to reduce the number of server-side redirects on Red Hat managed infrastructure behind docs.ansible.com. These server-side redirects exist to prevent 404 errors when documentation pages are moved or when url structures changed when the split to collections happened.
The purpose of reducing the number of redirects for docs.ansible.com is two-fold:
Firstly, consolidating redirects facilitates the migration of the docs.ansible.com subdomain to Read the Docs. There is a limit of 100 redirects for each project on Read the Docs. At present there are thousands of server-side redirects, greatly exceeding the limit.
Secondly, consolidating redirects drastically lowers the maintenance overhead that comes with thousands of server-side redirects. To prevent 404s, these server-side redirects need to be kept up to date as modules and plugins are moved between collections and collections get deprecated from the Ansible package.
Overview of server-side redirects
Server-side redirect rules are defined in .htaccess configuration files in the ansible/docsite repository. These files exist in two places:
Don Naro changed 8 months agoView mode Like Bookmark
Ansible releases have been deleted from PyPI to save space
While releasing Ansible 11.0.0rc1, the maintainers encountered a problem on PyPI. Namely, the number of packages for the "ansible" project exceeded the size limit of 10 GB.
A request was made to increase the limit but that could take some time to happen. To allow new releases to continue, community maintainers have deleted the following releases that were previously yanked for various reasons, such as incorrect package metadata or another breaking change:
10.0.0
9.6.0
9.5.0
9.0.0
Don Naro changed 8 months agoView mode Like Bookmark
This document lists possible documentation changes/recommendations that came out as part of the learning path to create a new collection that can be uploaded to galaxy.
Helpful links
collection_template
PRs created
https://github.com/ansible/ansible-documentation/pull/2034
General notes
Based on the learning path and video Andrei gave us:
Sandra McCann changed 9 months agoView mode Like Bookmark
Dates: Feb 3 - 5
CFP: https://cfp.cfgmgmtcamp.org/ghent2025/cfp
Kickoff mtg, Sept 18
13 talk proposals
https://cfp.cfgmgmtcamp.org/orga/event/ghent2025/login/?next=/orga/event/ghent2025/&
CFP is open // have dates // now it's time to push for submissions
who is going to sponsor?
Don Naro changed 10 months agoView mode Like Bookmark
(note: Some links go to internal Red Had Jenkins jobs and are not accessable to the general community at this point).
Problem
We want to be able to generate and publish the CLI guide to AWX documentation instead of controller docsite.
The current Jenkins job and supporting playbooks are controller-branded.
Also, the tool (awxcli) generates a complete sphinx-based html docsite (stand alone).
Options
Sandra McCann changed 10 months agoView mode Like Bookmark
Creating a new repository
In most cases, you should use the ansible-community/project-template when creating a new repository. Using the project-template populates the new repository with recommended content such as license, DCO, and code of conduct.
If required, you can move over content and contributor history from a source repository into your new repository. An alternative might be to use the GitHub importer at https://github.com/new/import to create a new repo that preserves contributor history and all content from the original source repo.
The GitHub importer allows you to basically mirror a repository without forking it. You can then add and remove content as needed. However if there is a need to change the license or other essential files, it's better to use the project-template. This way you have the correct license from the initial commit.
Preserving contributor history
When moving content from one repository to another, it is important to preserve contributor history. This section outlines some general techniques for moving git revision history.
Don Naro changed a year agoView mode Like Bookmark
When removing older communications sections, use the following guidelines:
Use the appropriate forum group if there is a group (except for core - use https://forum.ansible.com/tags/c/help/6/all/ansible-core instead).
For any tools in the dev-tools package, use the dev-tools group.
If there is no forum group, but you think there should be - open an issue in that project repo to suggest they ask for a forum group.
Otherwise, use the appropriate tag. If a tag does not exist, create one.
List of repos
As part of https://github.com/ansible-community/community-team/issues/554, this lists all the repos where this change needs to happen based on this search string:
Sandra McCann changed a year agoView mode Like Bookmark
Filed as https://issues.redhat.com/browse/AAP-25643
Goals
Make it as easy as possible to test collections using GHA
Reduce GHA runners usage (cost & speed)
Allow users to customize the test jobs running, like disabling some jobs types
Use a single workflows for running all tests: lint, sanity, unit, integration, publish
Ease update to new versions (via dependabot)
Versioning of this actions should depend on ansible-dev-tools release, so users would not be surprised by internal changes made inside our tools, or receive too many updates due to the number of components we have
Allow use of bleading edge releases (opt-in)
Sorin Sbarnea changed a year agoView mode Like 1 Bookmark
As we now have the forum for publishing the Bullhorn, we want to deprecate and end use of Mailchimp.
In order to do this, we need to migrate those subscribers to the Forum newsletter category.
The process to do this migration is:
Ensure all our docs & blogs point to The Forum (and not Bullhorn)
Create a hidden group in the forum for bullhorn subscribers.created - https://forum.ansible.com/g/Bullhorn
Create an invite code that will invite readers to join the forum specifically to the newsletter, watching first post so they get emails for each bullhorn issue.
Verify this setup works.
Sandra McCann changed a year agoView mode Like Bookmark
This week in Ansible Community
Issue #140, 2024-05-31 (Past Issues)
Welcome to The Bullhorn, our newsletter for the Ansible Community. If you have any questions or content you’d like to share, you're welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!
KEY DATES ⏱️
2024-06-04: DaWGs meeting, 15:00 UTC
2024-06-05: Community WG meeting, 18:00 UTC
2024-06-06: Bullhorn #137 content deadline, 18:00 UTC
Anwesha Das changed a year agoView mode Like Bookmark
Published 2024-03-29 13:00 UTC (no further changes accepted) https://forum.ansible.com/t/the-bullhorn-134/4631
This week in Ansible Community
Issue #134, 2024-03-29 (Past Issues)
Welcome to The Bullhorn, our newsletter for the Ansible Community. If you have any questions or content you’d like to share, you're welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!
KEY DATES ⏱️
cybette shared
2024-04-02: DaWGs meeting, 15:00 UTC
Carol Chen changed a year agoView mode Like Bookmark