Bug 1029510
| Summary: | [RFE] Ship Broker and Node as Virtual Appliances | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | james labocki <jlabocki> |
| Component: | RFE | Assignee: | jofernan |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0.0 | CC: | bleanhar, lmeyer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-27 18:49:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
james labocki
2013-11-12 14:05:27 UTC
Given OSE 2.1 and oo-install, the implementation here could be a lot more straightforward than before. Basically, ship two VM appliances which include: 1. Installed RPMs for OpenShift broker or node 2. "installer" user with known set of keys 3. oo-install running at firstboot to wire together as many VMs as are deployed. oo-install would need a few new special features to run in this mode. a. Automatically start with hosts in "installed" state b. Assume the "installer" user c. Deploy a new user for access post-install and nuke the "installer" user There may well be infrastructure-specific features (e.g. HEAT templates) that could construct the oo-install config file based on the deployment and just automate everything. We need to think seriously about how to enable subscriptions as part of this process, though. |