Remove DellEMC collections from community.general collectons

[rajeevarakkal]

SUMMARY

Need to get removed the dellemc collections community general repository as dellemc all modules are now available in Galaxy dellemc.openmanage collection.

ISSUE TYPE

• Feature Pull Request

ADDITIONAL INFORMATION

Already a PR created to update the botmeta & runtime files 
https://github.com/ansible/ansible/pull/71875

[felixfontein]

Adding negative review to prevent premature merge. dellemc.openmanage is not included in Ansible (yet), and we haven't decided how to proceed with such removals yet.

[ansibullbot]

cc @Sajna-Shetty @jagadeeshnv
click here for bot help

[rajeevarakkal]

Adding negative review to prevent premature merge. dellemc.openmanage is not included in Ansible (yet), and we haven't decided how to proceed with such removals yet.

Hi @felixfontein , are you referring to this PR ansible/ansible#71875 completion?

[felixfontein]

@rajeevarakkal no, I'm referring to the 'move content between collections where the target collection is not part of Ansible' policy which hasn't been decided yet.

Also, I don't think that PR in ansible/ansible will get merged, since ansible_builtin_runtime.yml is essentially frozen.

[felixfontein]

See ansible/community#539 (comment), "to discuss: what happens when the target collection is (not yet) contained in Ansible?".

[rajeevarakkal]

@felixfontein , i didn't get exactly target collection not contained in ansible, yes this dellemc.openmanage collections are not ansible certified, is that what you mean?

[felixfontein]

No, I mean Ansible itself (https://pypi.org/project/ansible/) - it was formerly called ACD (Ansible Community Distribution), maybe that name is more familiar to you. The collections included in Ansible 2.10 are listed here: https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in

[rajeevarakkal]

@felixfontein , Thanks, will go through this once.

[gundalow]

meta/runtime.yml needs updating for every plugin removed. An entry needs adding to point to the new collection.
.github/BOTMETA.yml also needs updating to remove the entries about these files and directories.

[rajeevarakkal]

@gundalow , The three contributed modules from dellemc -ie remote_managment/dellemc are now we are able to publish as part of dellemc.openmanage collections in the ansible galaxy space.

There been a request/communicaton earlier that community.general is temporary space and teams need to host their collections in to Galaxy space or other repository.

Since we have our collections available at dellemc.openmanage, what should we do, what next?

[thedoubl3j]

@rajeevarakkal you still need to update the files @gundalow referenced before this can get merged

[felixfontein]

There seems to be no modules called dellemc_idrac and ome in the new collection, but you remove these here. Have they been renamed? And are the other modules compatible to their verisons in the DellEMC collection?

[felixfontein]

For an example of how this PR should look like, see both f896c29 (main removal) and dbae7da (fixes changelog fragment, removes changelog fragments).

Please note that this can only be merged once the new collection is included in Ansible 2.10.

[felixfontein]

@rajeevarakkal could you please update/adjust this PR in a similar manner to e53f153 ? The removal would happen in community.general 3.0.0. Once this PR is in a good shape and ansible-community/ansible-build-data#58 has been merged, we can merge it and add an announcement to the next community.general 2.x.y release announcing this removal. (And of course update ansible/ansible#73046.)

[felixfontein]

@rajeevarakkal the PR now has conflicts, could you please rebase it?

[rajeevarakkal]

@rajeevarakkal the PR now has conflicts, could you please rebase it?

on it. Resolving the same

[ansibullbot]

@rajeevarakkal this PR contains the following merge commits:

• a2e87d3
• 41eb1cc

Please rebase your branch to remove these commits.

click here for bot help

[ansibullbot]

@rajeevarakkal This PR was evaluated as a potentially problematic PR for the following reasons:

• More than 50 changed files.

Such PR can only be merged by human. Contact a Core team member to review this PR on IRC: #ansible-devel on irc.freenode.net

click here for bot help

[felixfontein]

@rajeevarakkal could you please do a proper rebase to remove the merge commits, and remove all changes from this PR that do not belong in it (like the changes to .azure-pipelines/ and test/utils/)? Thanks.

[rajeevarakkal]

uld you please do a proper rebase to remove the merge commits,

@felixfontein Looks like rebase is running into chained conflicts. I will go ahead nd create a fresh PR and provide the link here. Is that fine?

[felixfontein]

@rajeevarakkal that's fine as well!

[rajeevarakkal]

@rajeevarakkal that's fine as well!

@felixfontein here is the new PR #1699

[rajeevarakkal]

New PR created due to multiple conflict here - #1699