[katello-devel] Future feature RFC: Package Upload

[Bryan Kearney]

On 03/19/2012 03:25 PM, Brad Buckingham wrote:
> In the future, the plan is to provide Katello users with the ability to
> upload a package. This email is to present a couple of options for
> accomplishing this in the UI and gather some initial feedback.
>
> Assumptions:
> - Prior to package upload, the target repository must exist.
> - When a package is uploaded, it will be uploaded only to the Library.
>
> The following are a couple of options for accomplishing this in the UI:
>
> 1. Incorporate it as part of Content Management -> Custom Content Providers
>
> For example,
> a. select [provider] -> Products & Repos -> [repository]
> b. from the Repository Details subpanel, allow the user the ability to
> browse
> to a package file and click 'Upload'
>
> 2. Incorporate it as part of Content Management -> Promotions
>
> For example,
> a. in the content tree, navigate to Repos
> b. select the repo. (Note: currently, users can see repos listed, but
> not select them).
> c. from the Repository Details pane (new), allow the user the ability to
> browse
> to a package file and click 'Upload'. (Notes: We could also use this
> pane to display
> a few details on the repository, such as name, url and other useful info.).
>
> I lean towards option 2 for a couple of reasons:
> - Before a user adds a package, they are likely to browse to see what
> packages exist. Currently, this would be done from the Promotions page;
> therefore, they would already be on the page.
> - In the future, users will have the ability to download packages.
> Assuming this will be based on earlier implementations, this would be
> from the Promotions page; therefore, having both upload/download on
> Promotions keeps it 'somewhat' consistent.
>
> There may be other options as well.
>
> Any thoughts/opinions/preferences?

 From the Content Browser. I would like to see what packages exist w/o 
having to go to a promotions exercise.

In reality, I htink the main use case will be CLI or API. For example, I 
script an upload from the end of every jenkins build.

-- bk