GalaxyNG is the next generation of the codebase behind https://galaxy.ansible.com. We hope to meld this code in a way that makes it suitable for both the customers of the Ansible Automation Platform and the community around https://galaxy.ansible.com.
Galaxy launched in 2013 by the company later known as "Ansible". The release announcement gives an interesting perspective of the original intent for the site that helps provide context for where we need the future of the galaxy_ng project to go.
What’s Galaxy? Ansible Galaxy is an automation content site designed from the ground up with an emphasis on being very dynamic — offering up a lot of new ways to find content.
Galaxy is structured around roles. You download the roles you like, then you write very simple play books that assemble all the roles together with roles you also write yourself. ...
At the initial phase, we’ve made sign up as painless as we could — you can login with a local account, but you can also login with OAuth from Twitter, GitHub, or Google+. (We just use this for login, so we won’t tweet for you or anything). You can also link social accounts later if you sign up first with a local account, but we expect social auth is the way to go for many of you.
Once you log in, from the “Explore” page, you can see not only the top roles in each category, but also the top reviewers, top authors, new roles, and new authors. You can browse the users arbitrarily and see what they have contributed and reviewed.
When we started Galaxy, a lot of our design influences were from consumer sites — things like iTunes, Flickr (Explore), and most significantly … beeradvocate.com! For this reason you’ll see linked reviews and ratings, ratings with structure, and highlighted reviews from AnsibleWorks employees. It’s designed to help you find what’s good very very clearly, and explore other things you might be interested in.
GalaxyNG is a total rewrite of some features from galaxy but catered to serving collections to Red Hat customers as a SaaS on https://cloud.redhat.com (now https://console.redhat.com) and as an on-premise deployment known as "Private Automation HUB". The new codebase did not include support for standalone roles and solely focused instead on collections.
The biggest change with GalaxyNG is that it is no longer a standalone django application with an AngularJS+Bootstrap frontend. As part of the rewrite, the project became a "pulp plugin", meaning it heavily relies on the family of projects in the https://github.com/pulp organization. Galaxy's v2 api makes use of "repositories" from pulp, but it was added on top of the previous codebase rather then conforming to the pure definition of pulp plugin.
We would like to consolidate the features of https://github.com/ansible/galaxy and https://github.com/ansible/galaxy_ng into the galaxy_ng codebase and bring community usage, contribution and improvements there. In doing so, we want to sunset the galaxy codebase and cooperatively plan to rehost https://galaxy.ansible.com with an instance of the galaxy_ng codebase.
We do not yet have a timeline for the migration or the cut over.
Communication and Feedback.¶
The galaxy dev team, contributors and community can mostly be found on libera.chat's #ansible-galaxy irc channel.
For bug reports and feature requests, see "Filing Issues".
- Go to https://issues.redhat.com/browse/AAH (can browse without login)
- Register for red hat account
- Click blue “Create” button at top of screen to get a dialog box for AAH project
- Set “Issue Type” to Bug or Task
- Set “Summary” (give it a title) & “Description”, and mention community
- Click “Create” at bottom of dialog box
See the Community Development documentation.