# Requesting Celestica SONiC community repository **URL:** \ **Category:** Collection Development\ **Tags:** coll-repo-request, awx\ **Created:** [October 18, 2024, 5:13pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403 "2024-10-18T17:13:52Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 18, 2024, 5:13pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/1 "2024-10-18T17:13:52Z")
I am looking for support in creating new repository under ansible-collections org to manage Celestica SONiC network operating system. I would like to have the repo as [https://github.com/ansible-collections/celestica.sonic](https://github.com/ansible-collections/celestica.sonic) Please guide me on the procedure to create new repo under ansible-collections org named as celestica.sonic ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 19, 2024, 10:51am UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/2 "2024-10-19T10:51:39Z")
I’m afraid I can’t help you there. But I think maybe you should change the title and make it more to the point. Like “Requesting Celestica SONiC community repository” or similar. This would make clear what this thread is about. ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 19, 2024, 5:05pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/3 "2024-10-19T17:05:55Z")
@mariolenz - Thanks for your reply, As suggested, renamed the title. In general, if you share the procedure to add or request new repo under ansible-collections, that will be useful. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [October 19, 2024, 5:21pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/4 "2024-10-19T17:21:12Z")
The procedure is described here: [Communicating with the Ansible community — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/community/communication.html#requesting-a-community-collection-repository) Quoting from there: > Working groups are often built around Ansible community collections. You can use a repository under your organization or request one under [ansible-collections](https://github.com/ansible-collections) on the forum by creating a topic in the [Project Discussions category and the coll-repo-request tag](http://forum.ansible.com/new-topic?category=project&tags=coll-repo-request). ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 20, 2024, 12:56pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/5 "2024-10-20T12:56:38Z")
@felixfontein - The current topic has been created by clicking [Project Discussions category and the coll-repo-request tag](http://forum.ansible.com/new-topic?category=project&tags=coll-repo-request) Hope that this shall be sufficient. ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 21, 2024, 4:04pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/6 "2024-10-21T16:04:52Z")
Hello All, Appreciate your support on this request. Thank you. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 22, 2024, 1:12pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/7 "2024-10-22T13:12:27Z")
@dharmaraj-gurusamy Welcome to the Forum! 1. Do you work for Celestica? 2. Is this related to [GitHub - ansible-collections/dellemc.enterprise\_sonic: Ansible Network Collection for Enterprise SONiC Distribution by Dell Technologies](https://github.com/ansible-collections/dellemc.enterprise_sonic) 3. Do you already have some modules for Celestica SONiC on GitHub so we can see what functionality there is? 4. We’ve found that having a few maintainers for a community collection works better, is there anybody else helping with this? Kind regards ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 22, 2024, 1:56pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/8 "2024-10-22T13:56:52Z")
Hi @gundalow - Thank you for the response. Here are the details. 1. I am working for Celestica Corporation, part of software development team 2. dellemc.enterprise\_sonic is intended to manage Dell/Broadcom SONiC network operating system (enterprise version of SONiC developed by Dell & Broadcom). The new collection is intended to manage Celestica SONiC network operating system (enterprise version of SONiC developed by Celestica) which will be used in switch / router devices. 3. Celestica SONiC will support collection core modules (command, config, etc) and 40+ idempotent network resource modules to automate switching and routing functionalities (e.g. IP config, Access Control List, LLDP, BGP, sFlow, VLAN, VxLAN, McLAG, etc). 4. Github usernames who will maintain this repository (dharmaraj-gurusamy and reshmanbablo) I would like to highlight the below too. 1. Collection has been developed based on Network Resoure modules 2. Collection is ready to be published into galaxy 3. New Namespace (celestica) in galaxy has been created already under my name. 4. More releases are planned on the new collection to support new features Here are the repo details we wish to create under ansible-collections Name: celestica.sonic Description: Ansible Network Collection for Celestica SONiC NOS. Type: Public License: GNU General Public License v3.0 Maintainers: dharmaraj-gurusamy and reshmanbablo Please let me know if more details are required. I will be glad to share. ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 23, 2024, 1:12pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/9 "2024-10-23T13:12:08Z")
Hi @gundalow - Please guide us on creating new repo. We can share more details, if required. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 23, 2024, 3:21pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/10 "2024-10-23T15:21:05Z")
@dharmaraj-gurusamy Thanks for the all the details, that really helps. # Summary I think this should be a Red Hat Ansible Automation Certification]([Partner technology validation and certifications | Red Hat Partner Connect](https://connect.redhat.com/en/partner-with-us/red-hat-ansible-automation-certification)), in your own GitHub Org. Ansible’s Partner Engineering Team can help you with this. # Details The rest of this reply has more detail on what _Certified Content_ is, though I know it’s often easier to just jump on a call and we can answer your questions directly, so please email `ansiblepartners@redhat.com` and we can get a video call setup. The Dell Collection is an example of [Red Hat Ansible Certified Content Collections](https://connect.redhat.com/en/partner-with-us/red-hat-ansible-automation-certification) by Dell. I think we should replicate that arrangement at Celestica which would be beneficial for your current and future customers. In practice, this would mean you’d create a GitHub repo for the collection in your Celestica’s GitHub Org and have this published into Galaxy & [Ansible automation hub](https://www.redhat.com/en/technologies/management/ansible/automation-hub) as something like `celestica.sonic`. # Red Hat Ansible Certified Content Collections Integrate your product with Ansible Automation Platform Red Hat Ansible Certified Content contains fully-supported roles and modules that are enterprise- and production-ready for use in our customers’ environments. By building and publishing Red Hat Certified Content, you can help Ansible Automation Platform customers introduce automation into your product, resulting in a better customer experience for them and fewer Ansible-related support issues for you. Red Hat Ansible Certified Content is supported by both Red Hat and our partners. Red Hat Ansible Certified Content Collections are published in both Ansible automation hub as well as Galaxy. # Documentation - [Red Hat Ansible Automation Certification](https://connect.redhat.com/en/partner-with-us/red-hat-ansible-automation-certification) overview document - [Ansible Certified Content FAQ](https://access.redhat.com/articles/4916901) - [Webinar that explains the on-boarding process](https://www.brighttalk.com/webcast/18106/579930) (1 hour) ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 23, 2024, 3:54pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/11 "2024-10-23T15:54:45Z")
Thanks much @gundalow for the details. I will check and come back for further support. ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 24, 2024, 2:37pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/12 "2024-10-24T14:37:37Z")
Hi @gundalow - Here is our response based on internal discussions. 1. We understand the benefits of Red Hat Ansible Certified Collection. Due to our internal process guidelines, we will not be able to initiate the certification process right now. 2. We would like to proceed with publishing the collection in galaxy (the namespace is owned already) and host the source code in ansible-collections Org (similar to other NOS vendors like arista.eos, cisco.nxus, dellemc.enterprise\_sonic, etc). To summarize, our current requirement is to have a collection repo under ansible-collections Org which is required for publishing into Galaxy and Red Hat Automation Hub. Would you please create “celestica.sonic” repo under ansible-collections Org and add me as maintainer? We will initiate the Red Hat Ansible Certification once the internal process is approved. Please let me know if you would like to view the collection content & TAR file. I will be happy to host in my github account and share with the community team for reference. Thank you. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [October 24, 2024, 3:20pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/13 "2024-10-24T15:20:12Z")
@dharmaraj-gurusamy You can create the repo in your own GitHub Org (the repos you mentioned as under [Ansible Collections · GitHub](http://github.com/ansible-collections) for legacy reasons). Copying the files from [GitHub - ansible-collections/collection\_template: A GitHub Template repo to use as the basis for future repos](https://github.com/ansible-collections/collection_template/) will give you working CI Once you’ve got the repo created and populated with initial files we will happily take a look to advice about future action. As you suggested, we can look at Certified Collection status in the future. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [October 24, 2024, 4:08pm UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/14 "2024-10-24T16:08:56Z")
> [@dharmaraj-gurusamy](#): > > To summarize, our current requirement is to have a collection repo under ansible-collections Org which is required for publishing into Galaxy and Red Hat Automation Hub. I don’t know about Red Hat Automation Hub, but a collection doesn’t have to live in ansible-collections to be published on galaxy. See [dellemc.openmanage](https://galaxy.ansible.com/ui/repo/published/dellemc/openmanage) for an example. As far as I understand, your collection will be owned and maintained by your company (Celestica) so it’s not really a _community_ collection. Or is it? Anyway, having the repo in your own GitHub org wouldn’t make it impossible for the community to contribute 😏 BTW if the collection repo is in your own GitHub org you would have **full** control over it. I guess this might even be an advantage for you as a company in contrast to having the collection in ansible-collections which isn’t owned by you. ---
**Author:** ![dharmaraj-gurusamy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dharmaraj-gurusamy/32/5203_2.png) [@dharmaraj-gurusamy](https://forum.ansible.com/u/dharmaraj-gurusamy)\ **Post date:** [October 25, 2024, 9:15am UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/15 "2024-10-25T09:15:10Z")
@gundalow and @mariolenz - Thanks for your inputs. I agree with your views on publishing into own Org and ansible-collections Org makes no difference. We prefer to host under [Ansible Collections · GitHub](http://github.com/ansible-collections) with the assumption that hosting the collection has two options supported as per the guideline stated in [Communicating with the Ansible community — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/community/communication.html#requesting-a-community-collection-repository) ![image](https://us1.discourse-cdn.com/ansible/original/2X/0/049feae8db57d6b820bd5f8328bf3deb73befc6e.png) That’s the trigger for this topic. I am in the assumption till now that community allows hosting the collection, but looks like that’s not the case. May I know the reasons behind? Is this a recent change in ansible community? ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [November 5, 2024, 9:37am UTC](https://forum.ansible.com/t/requesting-celestica-sonic-community-repository/10403/16 "2024-11-05T09:37:41Z")
@dharmaraj-gurusamy You’ll have the same functionality if the collection repo is in your own GitHub Org or ansible-community. Though having the collection in your own GitHub Org allows you to better manager who has `write` privileges to the repo You aren’t requesting a community collection, you will be setting up a company owned collection. The reason you see some company collections (such as Dell, Google, etc) under ansible-collections is because before collections we had ansible-core + 4,000+ modules in a single GitHub repository. Copy [GitHub - ansible-collections/collection\_template: A GitHub Template repo to use as the basis for future repos](https://github.com/ansible-collections/collection_template) and use that as the basis for your collection in your own repo. We will happily guide you though any issues and answer any questions you may have.