Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vmware.alb inclusion in the ansible package? #57

Open
dericcrago opened this issue Dec 6, 2021 · 10 comments
Open

vmware.alb inclusion in the ansible package? #57

dericcrago opened this issue Dec 6, 2021 · 10 comments
Assignees

Comments

@dericcrago
Copy link

Hi, we received a PR (ansible-collections/community.network#288) to remove the avi modules from the community.network collection. However, the vmware.alb collection is not currently included in the ansible package, so it would appear we have 2 options (see ansible-collections/community.network#288 (comment)). Would you like to add the vmware.alb collection to the ansible package or remove the avi modules from the community.network collection without the inclusion of vmware.alb? Please see https://github.com/ansible-collections/ansible-inclusion for more information about inclusion.

@sabandi
Copy link
Contributor

sabandi commented Dec 14, 2021

Hi @dericcrago

We would like to remove the avi modules from community.network and keep the vmware.alb collection out of the Ansible core. Please let me know if that works.

@dericcrago
Copy link
Author

Hi @sabandi, thank you for your reply. I just want to make sure I understand since sometimes the terminology can be confusing. When I mentioned the ansible package, I meant ansible (https://pypi.org/project/ansible/), not ansible-core (https://pypi.org/project/ansible-core/).

Scenario Outcome
Current situation The ansible package includes the community.network collection and that collection includes the avi modules
PR proposal The avi modules will be removed from the community.network collection and thus the ansible package will no longer include any avi modules unless they are explicitly installed via ansible-galaxy
Another alternative Request the inclusion of the vmware.alb collection into the ansible package and time the removal of the avi modules from the community.network collection to happen at the same time so that the transition is relatively seamless for the end user

So with that in mind, do you still want to remove the avi modules from the community.network collection without the inclusion of the vmware.alb collection into the ansible package (not ansible-core, but ansible)?

@sabandi
Copy link
Contributor

sabandi commented Dec 22, 2021

Thanks @dericcrago for the detailed response. Our current approach would be to remove the avi modules from community.network collection in ansible.

Having said that, I want to explore the option of adding our vmware.alb to community.network in future. Would moving to community.network tie our release cadence with anisble release ?

@dericcrago
Copy link
Author

@sabandi, that's interesting, I hadn't considered adding vmware.alb to community.network. I'm not sure if that will realistically be an option though. The original intent of community.network was to keep network plugins / modules that didn't already have a collection in the ansible package. Since there is already a vmware.alb collection, it would likely make more sense to just apply for the vmware.alb collection to be included in the ansible package.

As far as releases go, as long as you followed semver, you could do whatever you wanted and the ansible package would just pick up the appropriate version at build time. Please see the collection requirements for more details.

@gundalow
Copy link

gundalow commented Jan 6, 2022

Why were the sanity tests disabled in 8f8df7b? What's the plan to get them running again? Do you need help with this?

@sabandi
Copy link
Contributor

sabandi commented Jan 13, 2022

@sabandi, that's interesting, I hadn't considered adding vmware.alb to community.network. I'm not sure if that will realistically be an option though. The original intent of community.network was to keep network plugins / modules that didn't already have a collection in the ansible package. Since there is already a vmware.alb collection, it would likely make more sense to just apply for the vmware.alb collection to be included in the ansible package.

As far as releases go, as long as you followed semver, you could do whatever you wanted and the ansible package would just pick up the appropriate version at build time. Please see the collection requirements for more details.

Thanks @dericcrago for the detailed response. Now that we have finalised on keeping the vmware.alb outside the Ansible repo. Is there anything blocking us from removing avi modules from the community.network

@gundalow
Copy link

Thanks @dericcrago for the detailed response. Now that we have finalised on keeping the vmware.alb outside the Ansible repo. Is there anything blocking us from removing avi modules from the community.network

The next steps would be:

  1. Raise an Inclusion Request to get vmware.alb added to the ansible package
  2. One the above is merged git rm the plugins from community.network and update meta/runtime.yml to point to vmware.alb (prevents broken backwards compatability)

@grastogi23
Copy link
Contributor

adding @chaitanyaavi to the thread.

@chaitanyaavi chaitanyaavi self-assigned this Jun 23, 2022
@chandanapatnala
Copy link
Collaborator

Hi,
The community.network collections is showing an error while accessing that the repo has been disabled- https://github.com/ansible-collections/community.network . Is this temporary and is a timeline specified as when it'll be accessible again?

@gundalow
Copy link

Thanks for reporting this. We are investigating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants