canmove, Confirmed users
1,394
edits
ReleaseOperations/Projects/AutomaticProvisioning: Difference between revisions
Jump to navigation
Jump to search
ReleaseOperations/Projects/AutomaticProvisioning (view source)
Revision as of 19:16, 21 January 2014
, 21 January 2014no edit summary
(Created page with "== Description == AutomaticProvisioning is the umbrella project for supporting dynamic provisioning of systems within the releng infrastructure. This will include hosts with...") |
No edit summary |
||
| Line 12: | Line 12: | ||
* [[ReleaseOperations/Projects/AutomaticProvisioning/Meetings]] | * [[ReleaseOperations/Projects/AutomaticProvisioning/Meetings]] | ||
== Schedule == | |||
(tentative of course) | |||
=== 2014Q1 ==== | |||
* Be able to provision Linux instances on a single 4-node iX server chassis via an API call | |||
** No automatic support for creating images | |||
* Resolve requirements for object storage, select an implementation | |||
* Research direct connection to AWS, provide decisionmakers with enough data to make a yes/no decsision | |||
* Determine project metrics (financials, measurements) and begin gathering them | |||
=== 2014Q2 ==== | |||
* Automatic creation of images with puppet, MDT, Kickstart, etc. | |||
* Deploy object storage | |||
* Support production provisioning across all platforms | |||
== Tasks == | |||
=== Bare Metal Provisioning === | |||
==== Linux on Servers ==== | |||
==== Windows on Servers ==== | |||
==== OS X on Apple Hardware ==== | |||
=== Top-level API === | |||
=== Local Object Store === | |||
Figure out how to build an on-site object store similar to S3. | |||
Requirements here are still unclear. | |||
=== Amazon Direct Connect === | |||
Determine if a direct connection between Mozilla and AWS is viable, and if it would represent a cost savings or efficiency increment over the current arrangement. | |||
== Components == | == Components == | ||
TBD | |||