OpenDev is a space for collaborative Open Source software development.
OpenDev’s mission is to provide project hosting, continuous integration tooling, and virtual collaboration spaces for Open Source software projects. OpenDev is itself self hosted on this set of tools including Code Review (Gerrit), Continuous Integration (Zuul), Etherpad, Wiki (mediawiki), Code Browsing (gitea) and so on. This means that OpenDev itself is run like an open source project, you can join us and help run the system. Additionally all of the services we run are open source software themselves. The configuration for this site lives here!
We are still early in the process of building this out.
Most of the services we run were inherited and rebranded from the existing community run OpenStack Infrastructure. This means that while we do already have many services running, there may still be some services branded as "OpenStack" while we complete the rebranding.
As mentioned previously the OpenDev services themselves are open source software managed on top of OpenDev itself. This means that in addition to using OpenDev to host your software development activities you can help us run OpenDev with all of the same tools.
If you use the system and find it useful, we’d love to have your help running it as well.
It is more than that. We want to make this toolset available to others that would find it helpful. OpenStack is one of the OpenDev tenants, but other tenants like Zuul or $gizmo would be just as important.
Yes! However, as noted above it is still early days yet and the early experience might be a bit bumpy. Certain things may still say “OpenStack” on them as we figure out the transition. And while any moves should come with appropriate redirects, we may have some inadvertent misses.
Currently all of our test resources are Linux based. Adding additional platforms would likely require someone to help us get that running, but Zuul will support systems with ansible connection plugins. Talk to us!
No. We’ll continue to communicate changes as they happen. We’ll also do our best to make this as smooth a transition as possible. If we run into situations that force us to break something we’ll be sure to let you know at that point.
We’ve got a fair bit of experience with the existing toolset and adding new tools for which we’ve already got an answer is currently out of scope. We think the existing tools (like Gerrit) work well, and should only get better as we update them. The system is able to scale because we do not need multiple implementations of different software that solve similar problems.
For scaling and redundancy purposes we are actually running a number of independent Giteas behind a load balancer. We can keep git repos in sync from Gerrit reasonably well, but the issue tracker and wiki functionality would need another level of state syncing. Once Gitea can be run as a proper cluster this may change, but until then the functionality is limited.