Ansible Certified Content FAQ

Updated -

The following is a Frequently Asked Questions for the Ansible Automation Platform Certification Program. If you have any questions regarding the items below, please email ansiblepartners@redhat.com.

Why certify Ansible collections?

The following reasons:

  1. The Ansible Certification Program enables a shared statement of support for Certified Ansible Collections between Red Hat and the ecosystem partner. An end customer may open a support ticket (request for information, a problem, etc.) with Red Hat and expect the ticket will be addressed by Red Hat and the ecosystem partner.

  2. Red Hat offers go-to-market benefits for Certified Partners to grow market awareness, demand generation and collaborative selling.

  3. Ansible Certified Collections are distributed via Ansible Automation Hub (subscription required), a centralized repository for jointly supported Ansible Content. As a certified partner, publishing Collections to Ansible Automation Hub provides end customers the power to manage how trusted automation content is used in their production environment with a well known support life cycle.

For more information about getting started with certifying a solution, please refer to https://www.ansible.com/partners for details.

How do I get a Collection certified?

Please refer to http://www.ansible.com/partners for the Ansible certification policy guide to understand how to certify your collection.

What’s the difference between Ansible Galaxy and Ansible Automation Hub?

Collections published to Ansible Galaxy are the latest content published by the Ansible community and have no joint support claims associated. Ansible Galaxy is the recommended frontend “directory” for the Ansible community accessing all content.

Collections published to Automation Hub are targeted for joint customers of Red Hat and selected partners. Customers need an Ansible subscription to access and download certified collections present on Automation Hub. A Certified Collection means that Red Hat and partners have a strategic relationship in place and are ready to support joint customers, and may have had additional testing and validation done against them.

How do I request a namespace on Galaxy?

Please send an email to ansiblepartners@redhat.com after you request a namespace via an Ansible Galaxy GitHub Issue. You will have to provide us with the GitHub username which you have used to sign up on Ansible Galaxy, and must log in at least once in order the system to validate. Once users are added as admins of the namespace, then additional admins can be added via self-serve process.

Are there any restrictions for Galaxy namespace naming?

Collection namespaces must follow python module name convention. This means Collections should have short, all lowercase names. Underscores may be used in the Collection name if it improves readability.

Are there any naming recommendations for Collection naming?

A general suggestion is to create a collection with company_name.product format. This way multiple products may have different collections under the company namespace.

How do I get a namespace on Ansible Automation Hub?

By default namespaces used on Ansible Galaxy will also be utilized on Ansible Automation Hub by the Ansible Partner Team. For any queries and clarifications please contact ansiblepartners@redhat.com.

How do I run sanity tests on my collection?

Ansible Sanity tests are made up of scripts and tools used to perform static code analysis. The primary purpose of these tests is to enforce Ansible coding standards and requirements. Ansible Collections must be in a very specific path, such as the following:
{...}/ansible_collections/{namespace}/{collection}/

You must ensure your collection is in that specific path—with an empty directory named ansible_collections, then a directory for the namespace, and finally a directory for the collection itself.

Does Galaxy house the source code for my Collection?

No, Galaxy does not house the source for the Collections. The actual Collection source must be housed outside of Ansible Galaxy, for example GitHub. Ansible Galaxy contains the Collection build tarball to publish the collection. You can include the link to the source for community users in the galaxy.yml file contained in the Collection. This provides information to users of where they should go if they want to contribute to the Collection or even file issues against it.

Does Red Hat officially support Collections downloaded and installed from Ansible Galaxy?

No, collections downloaded from Galaxy do not have any support claims associated and are 100% community supported. Users and contributors of any such collection must contact the collection developers directly.

How does the joint support agreement on certified collections work?

If a customer raises an issue with the Red Hat support team on a certified collection, Red Hat support will triage the issue and check if the problem exists within Ansible or Ansible usage and they will also check if the issue is with a certified collection. If there is a problem with the certified collection, support teams will transfer the issue to the vendor owner of the certified collection through an agreed upon tool such as TSANet.

How to migrate existing modules/plugins to collections?

Please follow the guide found here to start developing a collection. To test if the collection is working properly you can follow the usage guide found here as it explains how collections will be consumed.=

Can we create and certify a collection containing only Ansible Roles?

Collections containing only roles may be created and certified. Current testing requirements are focused on collections containing modules, and additional resources are currently in progress for testing collections only containing roles. Please contact us for more information.