[katello-devel] Content Views - initial pull request to master created

[Brad Buckingham]

Thanks to all that have commented on the pull request below, so far.  If 
possible, we'd really like to get this PR merged in to master by the end 
of this week. In order to support that goal, it would be greatly 
appreciated if we could get comments by ~noon EST tomorrow (Friday 
2/15).  All code that is in this PR to master, has been in previous PRs 
to the content_views branch; therefore, it has gone through an initial 
round of feedback.

Our concern with waiting is that we do have additional enhancements that 
we'd like to be adding to content views; however, while this PR is open, 
we really don't have anywhere to generate the PRs against to have those 
enhancements reviewed.

Thanks for your understanding and support!

Brad

On 02/13/2013 02:54 PM, Brad Buckingham wrote:
> Hey Folks,
>
> As most already know, developers have been feverishly working on a new 
> feature referred to as "Content Views".  Not really sure what that 
> means?  Refer to the following wiki page for some additional information:
>
>     https://fedorahosted.org/katello/wiki/ContentViews
>
> The development of the feature is still ongoing; however, the team 
> wanted to create a github pull request and get what is available so 
> far in to master.  The pull request can be found at the link below. 
> Please look it over and provide comments/feedback.
>
>     https://github.com/Katello/katello/pull/1592
>
> The following is a high-level summary of the functionality that is 
> available (in UI/CLI/API), so far:
>
> 1. ability to create content view definitions
> 2. ability to publish and refresh content views based on those 
> definitions
> 3. ability to promote content views through environments, as well as 
> delete views from environments
> 4. ability to associate content views with activation keys
> 5. ability for a client system to register to katello using a content 
> view or using an activation key that specifies a content view
> 6. ability for a client system to consume (e.g. yum install) content 
> from a content view
> 7. ...etc.
>
> There are a lot of additional feature enhancements planned for the 
> future.  A few of the things that are still to come include:
>
> A. full support for composite content view definitions (e.g. a 
> definition made up of published views)
> B. support for adding filters to a content view definition (e.g. 
> errata filters, package whitelist/blacklist filters...etc) and 
> applying them to views that are published/refreshed
> C. full support of content views within the content search
> D. ....etc
>
> thanks,
> Brad, David, Partha, Mike, Justin.....etc...
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel