This repository is not used anymore.
If you are here to discuss Ansible community collections or request a repository for a community collection under the ansible-collections
GitHub organization, see the communication guide.
Collections overview, how to request a namespace
License: GNU General Public License v3.0
This repository is not used anymore.
If you are here to discuss Ansible community collections or request a repository for a community collection under the ansible-collections
GitHub organization, see the communication guide.
ansible-galaxy collection build
has support for an ignore list to prevent files ending up in the built tarball.
Although ideally Collection builds should be happening in a sandbox (CI) their is still the chance that they may include incorrect files.
Also people do build and publish collections locally, where their checkouts maybe dirty.
.gitignore
.gitignore
See ansible-collections/community.general#230 for example.
Need to review pre-ansible-base/
and see which other modules need updating in different collections.
Also see if dev_guide need updating
Following on from Part 1
migrate.py
rewrote in pluginsmigrated_to_collection_repo
https://github.com/ansible/ansible/labels/migrated_to_collection_repo to moved items.Questions
Python imports
from ansible_collections.community.grafana.plugins.module_utils.base import grafana_argument_spec
There are various files in contrib + integration tests that need moving to their correct home
grep 'needs/file/contrib/inventory' test/integration/targets/*/aliases
test/integration/targets/inventory_aws_conformance/aliases:needs/file/contrib/inventory/ec2.py
test/integration/targets/inventory_foreman_script/aliases:needs/file/contrib/inventory/foreman.py
test/integration/targets/vmware_inventory/aliases:needs/file/contrib/inventory/vmware_inventory.py
test/integration/targets/vmware_inventory/aliases:needs/file/contrib/inventory/vmware_inventory.ini
Some collections have a tests/sanity/requirements.txt
file copied from the ansible/ansible repo.
This file is not used by ansible-test
and should be removed to avoid confusion. I've seen it in two collections, but others which copied these may also have it:
How can we review this?
Once we've answered the above, we can look at tooling that exists.
Description TBD
rabbitmq
This infra should include both people who are maintaining what's in ansible-2.10+ and people who want to maintain collections in 2.10+
This shall be Ansible collection for Dell EMC Networking OS10
Currently, code is available at https://github.com/ansible-collection-migration/dell.os10
dellemc_networking.os10
Need to document this:
ansible/ansible
before the mass migration can continue to be used by the short form thanks to routing.ymlcollection:
formEXAMPLES
for new modules MUST have FQCN. This means Playbook authors can copy-paste examples without having to set collections:
routing.yml
. The entries was frozen in time when pre-ansible-base
was tagged. Hence 3.Every Collection Repo is it's own (mini) Community.
Some of these Collection Repos are managed by individuals or Partners that maybe new to helping building and maintaining Open Source Communities, we should give them some guidance as well as a clear way to speak to us.
It's hopefully easier to track what improvements to the documentation are needed if we break it down by who, then secondly what.
Once we have an understanding of what needs doing we can link to specific PRs from here.
We may move content from https://github.com/ansible-collections/overview/blob/master/README.rst into the main doc site (though we must keep the sections in README.rst
as we have given those links out)
Yep, this has been a useful tool and people rely upon it.
How to test proposed changes to a collection you depend on.
Speak to Paul
Did you know that the @ansible devel branch is about to get a lot smaller
(wordsmith to be much scarier)THE place to detail what happens after migrate.py gets run.
If you know of things that I've missed, please ping me, or add comments and I'll update this list.
s
-migration
ssh->https0.1.0
0.1.0
.github/workflows/ansible-test.yml
- Update checkout locationtests/utils/shippable
from FIXME.github/workflows/ansible-test.yml
form FIXMEOne of the primary design goals of Ansible 2.10 is that Ansible 2.9 Playbook should work without modification, to ensure that's the case we need to define some test cases
jpmens
jpmens
(Official)? Zabbix module namespace by community for the:
https://github.com/ansible/ansible/tree/devel/lib/ansible/modules/monitoring/zabbix
Near future plans would be to deploy custom CI so we can test modules against every zabbix LTS release.
https://www.zabbix.com/life_cycle_and_release_policy
community.zabbix
PRs are still being raised against ansible/ansible. Some/lots of these PRs are against content that's a
Can we put something in the PULL_TEMPLATE to put people into a holding pattern?
This is particularly useful between now and devel
being emptied out (23rd March) https://github.com/ansible-collections/overview/blob/master/README.rst#timeline
https://github.com/ansible/ansible/blob/devel/.github/PULL_REQUEST_TEMPLATE.md
This shall be the Ansible collection repository for Dell EMC Networking SONiC
dellemc_networking.sonic
ANSIBLE_METADATA has two fields of use:
That leaves status of preview vs stable. Do collection owners still see relevance in that information per module? If so, let's create a DOCUMENTATION field to cover that.
Collections which are tested on Shippable against RHEL 7.6 should update to RHEL 7.8.
This requires an update to shippable.yml
to replace T=rhel/7.6
with T=rhel/7.8
. Here's one such line in community.general
:
Some tests may need to be updated. For example, the name of the RHEL extras repository changed in RHEL 7.7, which is known to affect at least one test. See:
shippable.yml
as detailed above. In the PR please reference this issue, so we can track where the fix has been applied.Once most of the repos are up an running we need to review Shippable configuration
ansible-test change detection
-ve
For each repo under gh/ansible-collections that uses Shippable
alises
filessanity
durations and rebalance.To rebalance https://github.com/ansible/ansible/blob/devel/hacking/shippable/rebalance.py
Collections which are tested on Shippable against RHEL 8.1 should update to RHEL 8.2.
This requires an update to shippable.yml to replace T=rhel/8.1 with T=rhel/8.2. Here's one such line in ansible/ansible:
ansible/ansible@1c5c89b#diff-033d042b39454e8e066ab38fd89610a5L33-R33
Some tests may need to be updated.
Define the ansible-collections version of Core & external contributors. These people will have powers on all of the Community Repos under gh/ansible-collection.
Community Team (GDK's people)
Community Leadership (external)
Core Team?
Update Bot to honor these teams for Collections (rather than gh/ansible teams)
Reduce Bot user account so it no longer needs gh/ansible/ powers
Update settings.yml to give these people powers?
Detail the remaining steps to get us to Ansible 2.10.
This is just a proposal, the order and contents of the milestones may change.
As a reminder ansible-base
(gh/ansible/ansible) has it's own roadmap
[1d]
ie [3d] Migrated Modules Messaging #48
AIM: Get the Collections into a state so people can test and give us feedback
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket2
community.
collectionsAIM: Allow people to contribute
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket3
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket4
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket5
AIM: A basic build of ansible-2.10
on PyPi to allow people to check that the new process works. Allows us to confirm that Ansible 2.9 playbooks work without modification
FIXME: Should this be split into multiple milestones
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket6
community.general
or community.network
into dedicated collectionsacd.in
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket7
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket8
...
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket9
https://github.com/orgs/ansible-collections/projects/1?card_filter_query=label%3Abucket10
Now that ansible/ansible#68646 has been merged we need to view and possibly correct how they are defined.
_
for deprecation, they useWhen raising PRs to fix this, please mention #58 in the PR, so we can track where this has been fixed
On the GitHub landing page for this collection, it would be nice if the repo metadata links at the top of the page (which are currently empty—no description or website) had a link to https://galaxy.ansible.com/community/general
I like to be able to bounce between Galaxy and the source repo, and right now I can only go from Galaxy to the source repo and not vice-versa.
readme.md
N/A
Hi admin,
My repo is https://github.com/ansible-collections/ibm.spectrum_virtualize
In the setting button, I didn't find any setting can be used to set the default branch, would you please help to guide me to do it? Thank you very much.
Collections which are tested on Shippable against Fedora 30 should now test against Fedora 32 (so they are testing on 31 and 32), and at their discretion, drop support for Fedora 30 which is going end-of-life soon.
This requires an update to shippable.yml to add T=linux/fedora/32
. Here's one such line in ansible/ansible:
ansible/ansible@de59b17#diff-033d042b39454e8e066ab38fd89610a5R40
Some tests may need to be updated.
This shall be Ansible collection for Dell EMC Networking OS9
Currently, code is in https://github.com/ansible-collection-migration/dell.os9
dellemc_networking.os9
We need some nicer to allow movement of issues from gh/ansible/ansible to gh/ansible-collections/REPO.
Built in GitHub functionality only allows Issues to be moved within the same GH Org.
PR mover is solved by #5
I've contacted GitHub to see if they have any ideas
migrated_to_collection_repo
https://github.com/ansible/ansible/labels/migrated_to_collection_repo to moved items.This shall be Ansible collection for Dell EMC Networking OS6
Currently, code is in https://github.com/ansible-collection-migration/dell.os6
dellemc_networking.os6
At the time of the move to Collections there will be some differences and limitations in contributor workflow, we should keep an uptodate "Known issues and Limitations" list.
For example:
Description TBD
First stab: acozine/ansible@8b5388b
We need to add Galaxy Tags to the community.
Collections
Some thought and care will be needed for community.general
and community.network
scaleway
@scaleway/devtools
If assigning team does not work, you can use the individual GitHub profile:
@remyleone
@jerome-quere
@kindermoumoute
@QuentinBrosse
@loicbourgois
NO LONGER IN USE
Please subscribe to ansible-collections/news-for-maintainers
In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of this issue.
Watch
button in the upper right corner on the repository's home page.Issues
.I want to use "IBM Spectrum Virtualize" as my repo name, but in my galaxy.yaml, the collection name is "spectrum_virtualize"
wangpww
It is not entirely clear where modules have moved to, while a google search may clear up some things it is still hard to see which collection a module has moved to.
I am proposing some documentation to list out where the modules have gone. I think a single page with the relevant information will go a long way.
Module | Galaxy Name | Collection | Repo |
---|---|---|---|
ios_*. | cisco.ios | https://galaxy.ansible.com/cisco/ios | https://github.com/ansible-collections/cisco.ios/ |
digital_ocean_* | community.general | https://galaxy.ansible.com/community/general | https://github.com/ansible-collections/community.general |
Less of a bug, and more of a feature, but there was not ability to create a feature.
For the repos we look after community.(aws,general,vmware,windows)
Define and implement what is out minimum level of CI.
Whatever isn't done, can be delayed moved this into Part 2
We need to confirm, though the thought is that we should update documentation to use FQCN.
Module & plugin docs
Examples repos
Training materials
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.