Revision as of 14:46, 10 April 2016

Background

Fedora Infrastructure is running a private cloud infrastructure for various infrastructure and community projects. This infrastructure is currently running on the Icehouse release, but is in the progress of being upgraded.

Two Cloudlets

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 setup

fed-cloud09 is the main controller node
fed-cloud03,04,05,06,07,08,10,11,12,13,14,15 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 15 physical servers total. Currently 13 of them are in production, and 2 are being used for testing purposes by the infrastructure team.

Policies

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.

Images

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.

Major users

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.

The twisted project runs some buildbot tests.

hardware access

ssh access to the bare nodes will be for sysadmin-cloud and possibly fi-apprentice (with no sudo).

maint windows

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.

@@ Line 1: / Line 1: @@
 = Background =
-Fedora Infrastructure is looking to setup a private eucalyptus cloud instance in 2012. This cloud instance will be used in a number of ways to benefit Fedora. We evaluated a number of cloud technologies and decided (at least for now) on eucalyptus as the best fit for our needs.
+Fedora Infrastructure is running a private cloud infrastructure for various infrastructure and community projects. This infrastructure is currently running on the Icehouse release, but is in the progress of being upgraded.
-= Why Eucalyptus =
+= Two Cloudlets =
-* Open Source
+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.
-* Active Community
+= Current setup =
-* Deployable now
+* fed-cloud09 is the main controller node
+* fed-cloud03,04,05,06,07,08,10,11,12,13,14,15 are compute nodes.
-* Instances can be VLAN private so they cannot interfere with each other.
+= Setup / deployment =
-= Use cases =
+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.
-* Fedora QA may use instances with it's AutoQA setup. Instances would be created, tests run and destroyed. It's unknown how many instances we would need here.
+We have 15 physical servers total. Currently 13 of them are in production, and 2 are being used for testing purposes by the infrastructure team.
-* Infrastructure Development hosts may be moved to this cloud. These instances could possibly be 'on demand' when development needs to take place. Currently we have about 8 development instances.
+= Policies =
-* Infrastructure Staging hosted may be moved to this cloud. Some of these may be 'always on' and some may be on demand. Currently we have about 13 of these instances.
-* Chainbuilding / Kopers may use this cloud to build chains of packages that are not yet in Fedora and thus cannot be build via scratch builds in the existing buildsystem. These may also be used for spinning test live or install images by QA. This may be open to Fedora contributors or restricted to a subset such as packagers.
-* Test instances may be used for testing new tech or applications as a proof of concept before persuing a RFR. We currently have several publictest instances.
+Users or groups that need rare one off images can simply request one via a infrastructure ticket.
-* We may want to move some of our one-off instances that are outside phx2 into the cloud for easier management. Things like keyservers, unbound instances, listservers or hosted resources.
+Users or groups that often need instances may be granted accounts to spin up and down their own images.
-* Mass rebuilds of Fedora packages. This could be done for testing a new global rpm/package change, or to discover FTBFS (Fails to build from source) packages. This would use as many builders as we could easily spin up to reduce time for building all 10,000+ Fedora packages. Could use the chainbuilding setup as above as a scaffolding. Additionally, extra builder instances could be potentially used by the official build system during mass rebuilds to reduce rebuild time.
+Instances may be rebooted at any time. Save your data off often.
-For initial deployment, we would need to be able to run ~30 or so instances at a time with ability to grow rapidly above that for qa and building needs.
+Persistent storage may be available as seperate volumes. Data retention and Quotas may be imposed on this data.
-= Dependencies =
+Instances are assist in furthering the work related to the Fedora Project. Please don't use them for unrelated activities.
-* Need a way to easily provision new instances with limited admin intervention. Looking at ansible for this task.
+We reserve the right to shutdown, delete or revoke access to any instances at any time for any reason.
-* Would like to be able to create images via kickstart and normal install/deployment methods if needed.
+= Images =
-* Hardware needs to be ordered and installed.
+We will provide fedora, centos and rhel images.
-* Public IP addresses need to be made available.
+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.
-* Would be nice to get full EPEL packages to deploy with.
+= Major users =
-= Setup / deployment =
+* The copr buildsystem is housed entirely in the Fedora Infrastructure Private cloud.
-This hardware will be on the 'edge' of the network and not connected to the rest of Fedora Infrastructure except via external networks. This will allow 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 for caching with additional netapp space for images and data.
+* jenkins. Fedora infrastructure provides a jenkins instance to run tests on some open source projects.
-= Implementation overview / timelines =
+* Many Infrastructure dev instances are housed in the Fedora Infrastructure private cloud.
-<strike>2012-04 - Hardware is being determined and finalized. </strike>
+* The twisted project runs some buildbot tests.
-<strike>2012-07 - Initial hardware setup and install</strike>
+= hardware access =
--08 - Initial use cases setup and tested
+ssh access to the bare nodes will be for sysadmin-cloud and possibly fi-apprentice (with no sudo).
--09 - Announce availability and collect more use cases.
+= maint windows =
--10 - Evaluate load and expansion needs.
+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.
-= Policies =
+= Contact / more info =
-This section is currently under discussion. We need to setup clear policies on usage and access to the private cloud. In general we plan to open things to a small group of trusted contributors, take their feedback and usage and expand access out to larger groups as capacity and desire allows.
+Please contact the #fedora-admin channel or the fedora infrastructure list for any issues or questions around our private cloud.

Search

Infrastructure private cloud: Difference between revisions