The openstack superproject records tested commit sets, not code you can run
Repository tracking all OpenStack repositories as submodules. Mirror of code maintained at opendev.org.
At a glance
- What is it?
- openstack/openstack is not a service and not a bundle of code: it is a submodule superproject whose commits name one tested combination of every OpenStack component. This is what that arrangement buys you, what the root tree contains, and where the actual code lives.
- Who is it for?
- Use this repository when you need a combination of component commits that has actually passed the Zuul timeline, or when you want to see the full component set in one place. It cannot install, deploy or run OpenStack, and its own commit history is not where component history lives, so follow the pointers to opendev.org for real work and treat a superproject commit as a tested set rather than as a version of OpenStack.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 19, 2026, and from our analysis. They are not legal advice.
Star history
- openstack/openstack6,081 ★ · +42
| Repository | 2026-09-23 | 2026-11-19 |
|---|---|---|
| openstack/openstack | 6k | 6.1k |
42 Stars in the last 57 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This repository is a submodule index, not OpenStack itself
OpenStack is a collection of interoperable components that can be deployed to provide computing, networking and storage resources, and those resources are reached by end users through programmable APIs. The repository openstack/openstack holds none of that code. It exists because the components live in separate repositories, and this one keeps a pointer to every one of them, with the description calling it a mirror of code maintained at opendev.org. The root carries four hand written entries, .gitmodules for the submodule definitions, .gitreview for the review hook that matches the Gerrit workflow described below, README.rst, and LICENSE for the Apache-2.0 terms. Everything else at the top level is a submodule directory, which is why the tree reads as a list of project names rather than as source code.
Zuul's single timeline is the reason the superproject exists at all
The README explains the arrangement under a heading asking why this repository exists, and the answer is testing, not convenience. Zuul, the continuous integration system, gates all of the contained projects on one effective timeline, so across all projects OpenStack already has a sequence of combinations that have been explicitly tested. The problem is the direction of travel: going from a single commit of one project to the commits that were tested alongside it is non-trivial. That mapping is what the superproject supplies. Instead of asking which components were paired with your nova commit at a given moment, you read the commit that names the pairing. The value is entirely in provenance, so a superproject commit is best read as a tested set rather than as a release of OpenStack.
Gerrit updates the superproject, and a commit here fans out to a tested set
The mechanism has two halves. Gerrit's submodule tracking feature updates the superproject every time a subproject is updated, so the specific sequence created by Zuul is captured in the superproject's commits. And the README says the opposite direction is not the point: this repo is intended to be used in a read-only manner, and any commit made here pulls in a collection of commits in the other repositories that have been explicitly tested with each other. In other words, you push to the component repository and the pairing arrives here as a record.
The root tree mixes services, charms, Ansible roles, specs and UI projects
Reading the top level alphabetically gives the clearest picture of the OpenStack project set, and the names fall into families. Charm directories carry the charm- prefix: charm-aodh, charm-ceph-osd, charm-ceph-radosgw, charm-ceph-rbd-mirror, charm-ceilometer-agent, charm-cinder, charm-cinder-ceph, charm-cinder-backup, charm-cinder-purestorage, charm-cinder-backup-swift-proxy, charm-cloudkitty, charm-designate and charm-designate-bind. Ansible roles carry ansible-role-, covering chrony, systemd_mount, systemd_networkd, systemd_service, uwsgi, qdrouterd, container-registry, thales-hsm, atos-hsm, lunasa-hsm, tripleo-modify-image, redhat-subscription, python_venv_build, collect-logs, and openstack-operations, alongside a separate ansible-hardening entry. Then there are specification and test plugin pairs such as barbican-specs, blazar-specs, barbican-tempest-plugin and blazar-tempest-plugin, interface projects such as adjutant-ui and barbican-ui, and standalone names including aodh, automaton, bashate, bifrost, blazar, castellan, ceilometer and ceilometermiddleware.
A commit to this tree changes nothing on its own
Because the repository is a set of pointers, the usual reason to touch it does not apply. If you want to change Nova or add a service, the work belongs in the component repository at opendev.org/openstack, and the review happens there through Gerrit. This tree changes as a consequence, when the review system records a new tested pairing. The corollary is a practical one: a superproject checkout is a snapshot of pointers, so cloning it tells you nothing about component maturity, review status or whether a component still receives work. Two components that sit next to each other alphabetically can be at very different stages. The README itself routes every such question elsewhere: opendev.org/openstack for the component repositories, openstack.org/software for what the components are, openstack.org/community for contribution and governance.openstack.org for how the project is governed.
No releases and no tags: the commit list is the release record
The repository has no GitHub releases, and that is consistent with what it contains. A release of OpenStack is a set of component releases, and those tags live in the component repositories rather than here. What this history does hold is the tested sequence, ordered, with the diff between two commits telling you which submodule pointers moved. That makes the history useful for two specific jobs: finding the combination that a deployment was built from, and seeing how far apart two components have drifted in their paired commits. It is not useful for changelog purposes, because a commit message in this tree describes a repointing rather than a code change. The default branch is master, and the last push landed on 2 November 2026, so the pointer list is current rather than frozen.
Nothing here installs, deploys or starts anything
The limits are worth stating plainly. There is no install script, no package definition, no service manifest and no configuration sample in the root; the four hand written files are the module definitions, the review hook, the readme and the license. The README points at the component repositories for code and at openstack.org/software for descriptions, which means the work of assembling a running cloud is done elsewhere, from the many components named here. The submodule set also gives no indication of which components are required for a given deployment, in what order they start, or which are alternatives to each other. Treat the directory list as an inventory of the OpenStack project set and as a provenance record, and take deployment design, component choice and configuration from the documentation that belongs to each project.
Editorial conclusion
Use this repository when you need a combination of component commits that has actually passed the Zuul timeline, or when you want to see the full component set in one place. It cannot install, deploy or run OpenStack, and its own commit history is not where component history lives, so follow the pointers to opendev.org for real work and treat a superproject commit as a tested set rather than as a version of OpenStack.
Frequently asked questions
What is the purpose of the openstack/openstack repository?
It represents OpenStack as a collection of git submodules, mirroring code maintained at opendev.org. Each commit here captures a set of component commits that Zuul tested together, and the repository is intended to be read only.
Is the OpenStack superproject still being updated?
The repository is not archived and its last push was 2 November 2026. Because Zuul gates all contained projects on one timeline, new tested combinations of component commits keep landing here as superproject commits.
What is OpenStack?
OpenStack is described as a collection of interoperable components that can be deployed to provide computing, networking and storage resources, which end users then reach through programmable APIs. The repository holding the project set contains only submodule pointers to those components.
How do I install OpenStack from this repository?
You cannot, because this repository contains no installer or packaged software. The individual component repositories are listed at opendev.org/openstack, and openstack.org/software describes what the components do, so deployment work starts there rather than in the superproject.
How do I use the OpenStack command line client?
Nothing about a command line client is described here, since this repository only tracks component repositories as submodules. The client belongs to one of the component repositories listed on opendev.org, and this tree can only tell you which components are part of the project set.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openstack-openstack)Star history chart for your README
[](https://hysenlabs.com/projects/openstack-openstack)Was this useful?