ContentViewExportDesign » History » Revision 4
Revision 3 (Mike McCune, 10/27/2014 04:50 PM) → Revision 4/8 (Mike McCune, 10/28/2014 10:12 AM)
h1. Content View Export Design
h2. Initial Etherpad:
http://pad-katello.rhcloud.com/p/cv-export-requirements
h2. Stories
- As a user I want to be able to export a Content View from the Library to a filesystem location on the Katello server
- As a developer I want to design how we export Content Views from the Library
- As a user I want an API to initiate an export of a Content View from the Library that accepts disk location, export chunk size and Content View and version to be exported
- As a user I want a hammer CLI command to initiate an export of a Content View
- As a user I want to view the progress of a Content View export
- As a user I want to be able to initiate an export of a Content View from the WebUI
- As a administrator I want to be able to configure the export location for Content View exports
- As a user I want to be able to specify a date range for an export to allow for incremental exports of content
- As a user I want to be able to view the date and time I last exported a Content View.
- As a user I want the export API to support date ranges for incremental exports of content
- As a user I want the WebUI to support date ranges during export
- As a user I want a hammer command to support a date range for an export to allow for incremental exports of content
- As a developer I want to design how to import an exported content view into Katello
- As a user I want to be able to import a Content View from a local filesystem directory
- As a user I want to be able to use imported Content Views as Red Hat content
- As a user I want to be able to import Red Hat content from a local directory into the Library
- As a user I want to view what content is available on the locally mounted export
- As a user I want to be able to import from the selected set of repositories
- as a user I want to re-import an incremental export into Katello
- As a user I want imported content to be tied to the correct subscriptions
h2. Design
TBD