Help us make the RDO community site a great place for users and cloud operators in the Red Hat ecosystem by sharing your OpenStack questions and solutions on ask.openstack, and by adding the most useful solutions and user stories to the RDO website.
Our community strives to operate according to the terms of the OpenStack Code of Conduct.
- Get involved
- Stay informed
- Ask and answer
- Docs and website
Come chat in real-time with RDO users on IRC on the Freenode server:
- #rdo: Discussion around RDO in general (Transcripts)
- #rdo-puppet: Discussion around deploying RDO with Packstack and it's puppet modules
- #openstack: Discussion around OpenStack with the broader OpenStack community
- #centos-devel: Discussion around the CentOS Cloud Special Interest Group (SIG)
We have weekly IRC meetings you can participate in:
- RDO meetings @ every Wednesday at 15:00 UTC on #rdo
- CentOS Cloud SIG meetings @ every Thursday at 15:00 UTC on #centos-devel
Join us for various Events around the world. Organize your own meetup. If you run a meetup group, or if you're speaking at a meetup here's some of the ways we can help out.
Follow us on Twitter at @rdocommunity, on Google+, or on Facebook, as you prefer.
Tweets by RDOcommunity
Join our newsletter mailing list for monthly updates on RDO and the larger OpenStack world.
Watch RDO videos. These include recorded talks, meetups, and other community events.
Ask and answer
- Check our Frequently Asked Questions (FAQ) page for answers to common questions
- Try our troubleshooting page for solutions to common problems
- Join the ask.openstack community to ask and answer questions:
The site ask.openstack is the upstream Q&A for all manner of OpenStack issues.
- Search ask.openstack to find previous discussions on the topic.
- If you ask a new question, consider adding the tag “rdo” to it. You can use this link to add a new question with this tag.
- Find all questions on ask.openstack related to RDO.
If you're a frequent poster on ask.openstack and wish to identify yourself as part of the RDO community, consider adding the RDO logo to your avatar, like Lars: https://ask.openstack.org/en/users/1745/larsks/ .
- Help improve our knowledge base by turning the best answers to questions on the mailing lists or on ask.openstack.org into a page in our troubleshooting section. In case of ask.openstack.org, a link might be sufficient.
- Blog about how you're using RDO. If you blog frequently about RDO and OpenStack, consider requesting that your blog be added to the upstream Planet OpenStack.
- Fork the website on Github and help us improve our documentation.
An important way that you can contribute to RDO is by reporting any problems you encounter.
To file bugs against RDO, use the RDO bugzilla.
To report problems with this website, use the tracker on GitHub.
If you're not sure where the problem likes ask.openstack.org is the best place to start.
RDO is a large community interested in packaging and deploying OpenStack on RHEL and its derivatives.
We can always use your feedback and contributions to make RDO better.
Get started by looking at the RDO packaging documentation, taking a glance at our packages and help with patch reviews.
Packages provided by RDO to install and configure OpenStack are available through several projects which could all use your help:
Docs and website
Help improve the documentation and website! The main pages for contributed content are documentation, troubleshooting and user stories.
- Take a look at the open issues list: https://github.com/redhat-openstack/website/issues
- Update this or another page by submitting pull requests to the https://github.com/redhat-openstack/website repo, or by clicking the
Edit on Githubbanner at the top right.
- Fork the whole website: https://github.com/redhat-openstack/website
Here are a few guidelines for contributing new content to the website:
- Please search first to check if there is a similar page which you can update.
- Use normal English case for page names. Running an instance is correct, Get Involved is not.
- Please keep the website content connected! When you add a new page, add a link to it from the appropriate page(s).