Page tree
Skip to end of metadata
Go to start of metadata

Project Name:

  • Open Open Infra Hardware Project (Open^2 Infra HW Project)

Project description:

  • The idea is to compile a community sourced database of Ceph HW reference architectures for various use cases and make them searchable based on use case, workload etc. Today the barrier to entry for new Ceph installations is very high and this limits the adoption of Ceph as a storage platform. The hope is that by creating a community sourced database of reference designs, an organization interested in getting started with Ceph can just look up their workload and get a reference HW design based on up to date hardware. Ideally, automated installation, deployment and monitoring scripts would be included with each reference design.


  • Describe the are that project is addressing (for instance cloud infrastructure)
    • The project addresses on prem Ceph installations.
  • Describe the planned areas of focus and development (for instance keystone federation for distributed clouds)
    • None. It's more about collecting and curating various reference architectures from people who are running Ceph today.
  • Specify any upstream sources or projects the team will be working with (for instance OpenStack/keystone)
    • None. Well, I guess maybe the Ceph projects, although strictly, very little interaction is needed.
  • Specify and local testing and integration needs (outline intent here, infra needs are listed later)
    • None.
  • Describe how the project is extensible in the future or how others might participate.
    • Everyone can participate. It can be extended to reference architectures covering OpenStack and Kubernetes as well, but we have to start somewhere and storage is a very nice and isolated use case, so I hope that by starting there, we'll have something to show for it.

Infrastructure needs:

  • A traditional lamp stack on 1 VM. (Or maybe 2 in case of replication for DR purposes and backup).

This section should cover the source repository needs (GitHub or Gerrit workflows), if you have specific hardware or cloud needs (keystone federation requires multiple running OpenStack instances) and if you require integration with any external systems (for instance "I want to use openlab resources for deployment and testing").  This section should give a good indication to the TC and the infra team on how to get your environment in place.  You may be starting a new project in an existing area and would simply state you would use the existing infra set-up for that project, or require some extra "xyz".


  • Identify similar projects is underway or being proposed in Nordix or upstream projects
  • Identify any specific development be staged with respect to the upstream project and releases.

Project members and contributors:

  • Names of the committers/maintainers
    • None at the moment. Due to time constraints, I cannot do this alone.
  • Names of any other members/contributors
  • No labels