With our impending Katello 2.0 release on the near horizon, I wanted
to share and get feedback from the community on what the Katello 2.1
release is going to focus on. The main areas are:
Errata Management
via email notifications
better views of applicable errata for content hosts
better views of available errata between environments
> Howdy,
>
> With our impending Katello 2.0 release on the near horizon, I wanted
> to share and get feedback from the community on what the Katello 2.1
> release is going to focus on. The main areas are:
>
> * Errata Management
> - via email notifications
> - better views of applicable errata for content hosts
> - better views of available errata between environments
>
> * Docker Content Support
> - sync'ing and managing Docker repositories
> - managing the lifecycle of a Docker repository
> - Docker repositories as a provisioning resource
>
> * Improved Usability
>
can you elaborate on this one? does it include supporting existing foreman
installs for example?
I think that until katello is not easier to consume by the community, it
would be hard to get valuable feedback?
thanks,
Ohad
···
On Wed, Oct 1, 2014 at 2:47 AM, Eric D Helms wrote:
I agree with Ohad
I already have a Foreman instance in my Production environment and I'm not
going to install / test Katello until I can add it to my existing instance
בתאריך יום רביעי, 1 באוקטובר 2014 10:02:51 UTC+3, מאת ohad:
···
>
>
>
> On Wed, Oct 1, 2014 at 2:47 AM, Eric D Helms > wrote:
>
>> Howdy,
>>
>> With our impending Katello 2.0 release on the near horizon, I wanted
>> to share and get feedback from the community on what the Katello 2.1
>> release is going to focus on. The main areas are:
>>
>> * Errata Management
>> - via email notifications
>> - better views of applicable errata for content hosts
>> - better views of available errata between environments
>>
>> * Docker Content Support
>> - sync'ing and managing Docker repositories
>> - managing the lifecycle of a Docker repository
>> - Docker repositories as a provisioning resource
>>
>> * Improved Usability
>>
>
> can you elaborate on this one? does it include supporting existing
> foreman installs for example?
>
> I think that until katello is not easier to consume by the community, it
> would be hard to get valuable feedback?
>
> thanks,
> Ohad
>
>>
>>
>> Thanks,
>> Eric
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
>
>>
>> Howdy,
>>
>> With our impending Katello 2.0 release on the near horizon, I wanted
>> to share and get feedback from the community on what the Katello 2.1
>> release is going to focus on. The main areas are:
>>
>> * Errata Management
>> - via email notifications
>> - better views of applicable errata for content hosts
>> - better views of available errata between environments
>>
>> * Docker Content Support
>> - sync'ing and managing Docker repositories
>> - managing the lifecycle of a Docker repository
>> - Docker repositories as a provisioning resource
>>
>> * Improved Usability
>
>
> can you elaborate on this one? does it include supporting existing foreman
> installs for example?
>
> I think that until katello is not easier to consume by the community, it
> would be hard to get valuable feedback?
Sure. This encompasses updates to our UI workflows, Foreman
integration workflows or additional views of content as we have time
to implement them over the next few releases. I was somewhat
purposefully vague about this particular line item as we are still
building out and grooming the stories in this area for the 2.1
release. As for the story around allowing Katello to be installed
alongside an existing Foreman
(Tracker #7605: As a Foreman user, I would like to be able to add Katello later to an existing Foreman installation - Katello - Foreman) we have decided, at a
minimum, to explore what changes would be necessary to accommodate
this request in order to better understand the scope and thus make an
informed decision around timeline with respect to it.
Eric
···
On Wed, Oct 1, 2014 at 3:02 AM, Ohad Levy wrote:
> On Wed, Oct 1, 2014 at 2:47 AM, Eric D Helms wrote:
> Hi Eric,
>
> Congratulation and thanks to everyone for the hard work on Katello 2.0 !!!
>
First, thanks!
> For Katello 2.1 it would be also great to see the following:
> - Errata Implementation for CentOS
Can you expand a little further on this? Is there CentOS errata that
you know of and want to manage or are you asking for the ability to
create your own errata?
> - Filter Option on Product Repo
Can you explain this one in a little more detail? What do you want to
filter by? Is this on the repositories list for a product?
> - Time Window Option for Package Action
I am assuming this is essentially requesting the ability to schedule actions?
Same here. As I have said before, this is really the deal breaker for us.
···
On Wed, Oct 1, 2014 at 3:17 AM, Royee Tager wrote:
I agree with Ohad
I already have a Foreman instance in my Production environment and I’m not
going to install / test Katello until I can add it to my existing instance
בתאריך יום רביעי, 1 באוקטובר 2014 10:02:51 UTC+3, מאת ohad:
With our impending Katello 2.0 release on the near horizon, I wanted
to share and get feedback from the community on what the Katello 2.1
release is going to focus on. The main areas are:
Errata Management
via email notifications
better views of applicable errata for content hosts
better views of available errata between environments
Docker Content Support
sync’ing and managing Docker repositories
managing the lifecycle of a Docker repository
Docker repositories as a provisioning resource
Improved Usability
can you elaborate on this one? does it include supporting existing
foreman installs for example?
I think that until katello is not easier to consume by the community, it
would be hard to get valuable feedback?
> I agree with Ohad
> I already have a Foreman instance in my Production environment and I'm not going to install / test Katello until I can add it to my existing instance
>
> בתאריך יום רביעי, 1 באוקטובר 2014 10:02:51 UTC+3, מאת ohad:
>
>
> Howdy,
>
> With our impending Katello 2.0 release on the near horizon, I wanted
> to share and get feedback from the community on what the Katello 2.1
> release is going to focus on. The main areas are:
>
> * Errata Management
> - via email notifications
> - better views of applicable errata for content hosts
> - better views of available errata between environments
>
+1 for Errata notifications via email
I am about to roll out a greenfield DC and was desperately hoping that a full implementation of Katello and Foreman would be released - RH keeps telling us that Satellite 6 will be available any day now the underlying technologies being Katello, Foreman and friends. So I am curious as to the status of this. I have played with the release candidates where the two appear to exist side by side but its not particularly intuitive for folks who are new to both services.
Is there any light you can shed on this Eric?
Regards
LukeK
···
On Oct 1, 2014, at 4:17 PM, Royee Tager wrote:
> On Wed, Oct 1, 2014 at 2:47 AM, Eric D Helms wrote:
Docker Content Support
sync’ing and managing Docker repositories
managing the lifecycle of a Docker repository
Docker repositories as a provisioning resource
Improved Usability
can you elaborate on this one? does it include supporting existing foreman installs for example?
I think that until katello is not easier to consume by the community, it would be hard to get valuable feedback?
> - Errata Implementation for CentOS
> Can you expand a little further on this? Is there CentOS errata that
> you know of and want to manage or are you asking for the ability to
> create your own errata?
>> Hi Eric,
>>
>> Congratulation and thanks to everyone for the hard work on Katello 2.0 !!!
>>
> First, thanks!
>
>> For Katello 2.1 it would be also great to see the following:
>> - Errata Implementation for CentOS
> Can you expand a little further on this? Is there CentOS errata that
> you know of and want to manage or are you asking for the ability to
> create your own errata?
Whereas katello syncs errata from an updateinfo.xml within the
repository. Ideally Centos would publish updateinfo.xml files but it
seems they do not due to complications around their repository
structuring and mirroring strategy
(http://lists.centos.org/pipermail/centos-devel/2014-January/009502.html).
For spacewalk a tool was created to parse their mailing list and import
this data into spacewalk through its API, since spacewalk supports
custom errata. (http://cefs.steve-meier.de/)
So at a minimum Katello could support creating errata on custom repos
(and it likely is not a ton of work to do). That would at least enable
someone not as familiar with Katello internals to develop the tool on
their own as was done for spacewalk. Going further we could add this
functionality to Katello itself.
···
On 10/01/2014 07:08 AM, Eric D Helms wrote:
> On Wed, Oct 1, 2014 at 4:03 AM, wrote:
Filter Option on Product Repo
Can you explain this one in a little more detail? What do you want to
filter by? Is this on the repositories list for a product?
Time Window Option for Package Action
I am assuming this is essentially requesting the ability to schedule actions?
Thank you for the all the efforts from this community in making a
release like this possible.
– bk
···
On 10/01/2014 07:50 AM, Luke Kearney wrote:
>
> On Oct 1, 2014, at 4:17 PM, Royee Tager > wrote:
>
>> I agree with Ohad
>> I already have a Foreman instance in my Production environment and I'm
>> not going to install / test Katello until I can add it to my existing
>> instance
>>
>> בתאריך יום רביעי, 1 באוקטובר 2014 10:02:51 UTC+3, מאת ohad:
>>
>>
>>
>> On Wed, Oct 1, 2014 at 2:47 AM, Eric D Helms > > wrote:
>>
>> Howdy,
>>
>> With our impending Katello 2.0 release on the near horizon, I
>> wanted
>> to share and get feedback from the community on what the
>> Katello 2.1
>> release is going to focus on. The main areas are:
>>
>> * Errata Management
>> - via email notifications
>> - better views of applicable errata for content hosts
>> - better views of available errata between environments
>>
>
> +1 for Errata notifications via email
>
> I am about to roll out a greenfield DC and was desperately hoping that a
> full implementation of Katello and Foreman would be released - RH keeps
> telling us that Satellite 6 will be available any day now the underlying
> technologies being Katello, Foreman and friends. So I am curious as to
> the status of this. I have played with the release candidates where the
> two appear to exist side by side but its not particularly intuitive for
> folks who are new to both services.
>
> Is there any light you can shed on this Eric?
>
> Regards
>
> LukeK
In order for us to support this, the underlying Pulp project which
handles content would need to support this first. I'd suggest filing a
feature request or discussing with them to start.
Eric
···
On Wed, Oct 1, 2014 at 9:42 AM, wrote:
Time Window Option for Package Action
I am assuming this is essentially requesting the ability to schedule
actions?
