(Initial page) |
No edit summary |
||
| Line 6: | Line 6: | ||
== Owner == | == Owner == | ||
* Name: [[User:Stefw| Stef Walter]] | * Name: [[User:Stefw| Stef Walter]] | ||
* Email: stefw@redhat.com | * Email: stefw@redhat.com | ||
| Line 17: | Line 15: | ||
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
* Tracker bug: <will be assigned by the Wrangler> | * Tracker bug: <will be assigned by the Wrangler> | ||
* Depends heavily on: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service | |||
== Detailed Description == | == Detailed Description == | ||
The Cockpit Web Service is a privileged container used on operating systems that do not allow packages to be installed, such as Fedora Atomic. Such a Fedora based privileged container has been available at the Docker Hub. This change proposes that Fedora infrastructure is used to build the container instead. | The Cockpit Web Service is a privileged container used on operating systems that do not allow packages to be installed, such as Fedora Atomic. Such a Fedora based privileged container has been available at the Docker Hub. This change proposes that Fedora infrastructure is used to build the container instead. | ||
This depends heavily on: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service | |||
It is important that such build infrastructure allows automated builds (as the Docker Hub does), to prevent unnecessary work in a volunteer based community. These automated builds could be driven off of koji build notifications or bodhi updates. | It is important that such build infrastructure allows automated builds (as the Docker Hub does), to prevent unnecessary work in a volunteer based community. These automated builds could be driven off of koji build notifications or bodhi updates. | ||
| Line 29: | Line 30: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Stef Walter | ||
* Other developers: | * Other developers: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service | ||
* Release engineering: Dennis Gilmore | * Release engineering: Dennis Gilmore | ||
| Line 43: | Line 44: | ||
== How To Test == | == How To Test == | ||
# atomic run | # atomic run whatever-the-image-repo.is.fedoraproject.org/cockpit/ws | ||
== User Experience == | == User Experience == | ||
Very small user experience change: The URL used to install Cockpit Web Service container. | |||
== Dependencies == | == Dependencies == | ||
This change depends on | This change depends on https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service being able to provide *automated* Docker image builds. | ||
== Contingency Plan == | == Contingency Plan == | ||
Latest revision as of 07:27, 8 September 2015
Automated Build of Cockpit Web Service Container
Summary
The Cockpit Web Service is a privileged container used on operating systems that do not allow packages to be installed, such as Fedora Atomic. Such a Fedora based privileged container has been available at the Docker Hub. This change proposes that Fedora infrastructure is used to build the container instead.
Owner
- Name: Stef Walter
- Email: stefw@redhat.com
- Product: Fedora Atomic
- Responsible WG: Cloud
Current status
- Targeted release: 24
- Last updated: 2015-09-08
- Tracker bug: <will be assigned by the Wrangler>
- Depends heavily on: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
Detailed Description
The Cockpit Web Service is a privileged container used on operating systems that do not allow packages to be installed, such as Fedora Atomic. Such a Fedora based privileged container has been available at the Docker Hub. This change proposes that Fedora infrastructure is used to build the container instead.
This depends heavily on: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
It is important that such build infrastructure allows automated builds (as the Docker Hub does), to prevent unnecessary work in a volunteer based community. These automated builds could be driven off of koji build notifications or bodhi updates.
Benefit to Fedora
Fedora gets to host its own content. There does not seem to be any other benefit.
Scope
- Proposal owners: Stef Walter
- Release engineering: Dennis Gilmore
- Policies and guidelines: <Not sure, perhaps a policy that parts of Fedora are built by Fedora?>
Upgrade/compatibility impact
The container built at the Docker Hub can be replaced by the one built by Fedora.
How To Test
- atomic run whatever-the-image-repo.is.fedoraproject.org/cockpit/ws
User Experience
Very small user experience change: The URL used to install Cockpit Web Service container.
Dependencies
This change depends on https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service being able to provide *automated* Docker image builds.
Contingency Plan
Continue to use the container at the Docker hub.
Documentation
The eventual Fedora image repository URL needs to be documented.
Release Notes
The eventual Fedora image repository URL should be in the release notes.