Fedora Infrastructure is running a private cloud infrastructure for various infrastructure and community projects. This infrastructure is currently running RHOSP 5 (Red Hat Open Stack Platform 5).
We have things setup in 2 cloudlets to allow us to serve existing cloud needs, while still having the ability to test new software and tech. From time to time we may migrate uses from one to the other as a newer version or kind of setup is determined to meet our production needs more closely.
Current primary setup
- fed-cloud09 is the main controller node
- fed-cloud03,04,05,06,07,08,10,11,12,13,14,15 and fed-cloud-ppc02 are compute nodes.
Setup / deployment
This hardware is setup on the 'edge' of the network and not connected to the rest of Fedora Infrastructure except via external networks. This allows us to us external ip's and make sure the cloud instance doesn't have access to anything in the regular Fedora Infrastructure. Storage will be on the local servers.
We have 17 physical servers total. Currently 14 of them are in production, and 3 are being used for testing purposes by the infrastructure team.
Storage is provided by 2 dell equalogics boxes (one with ~20TB space, the other with ~10TB)
The current setup has only 1 controller node so outages can and will occur when upgrades are being done, etc.
Nodes in this cloud use the 'fedorainfracloud.org' domain in most cases (with some few exceptions).
x86_64 and ppc64 and ppc64le instances are provided by the current cloud.
As many of the existing hardware boxes are reaching end of life/support, we have ordered some new hardware in Q2 of 2017. We plan to setup RHOSP10 (or later) on this new hardware and then recreate instances in this new cloud and retire the old one. This is planned for mid/late 2017. This new install should allow us to setup 2 head nodes with HA so we can do upgrades or the like without much in the way of outages. Additionally we hope to add armv7 and aarch64 support via openstack ironic.
Users or groups that need rare one off images can simply request one via a infrastructure ticket.
Users or groups that often need instances may be granted accounts to spin up and down their own images.
Instances may be rebooted at any time. Save your data off often.
Persistent storage may be available as seperate volumes. Data retention and Quotas may be imposed on this data.
Instances are assist in furthering the work related to the Fedora Project. Please don't use them for unrelated activities.
We reserve the right to shutdown, delete or revoke access to any instances at any time for any reason.
We will provide fedora, centos and rhel images.
If you need to add images, please name them the same as their filename. Ie, "Fedora 22 Beta TC 2" is fine, please don't use 'test image' as we have no idea what it might be.
- The copr buildsystem is housed entirely in the Fedora Infrastructure Private cloud.
- jenkins. Fedora infrastructure provides a jenkins instance to run tests on some open source projects.
- Many Infrastructure dev instances are housed in the Fedora Infrastructure private cloud.
- Fedora magazine and community blogs are hosted here.
- The twisted project runs some buildbot tests.
ssh access to the bare nodes will be for sysadmin-cloud and possibly fi-apprentice (with no sudo).
We are reserving the right to update and reboot the cloud when and as needed. We will schedule these outages as we do for any outage and will spin back up any persistent cloud instances we have in our ansible inventory after the outage is over. It's up to owners of any other instances to spin up new versions of them after the outage and make sure all updates are applied.
Contact / more info
Please contact the #fedora-admin channel or the fedora infrastructure list for any issues or questions around our private cloud.