Katello 2.3 Roadmap

All,

With the branching of 2.2, we have identified some targets for 2.3. These
fall into 2 categories; stories we have broken out and those that need
exploration and grooming. The current set of stories that has been assigned
to the release can be seen at [1]. The below list may shift over the next
few weeks, and we welcome input from the community as to what they would
like to see.

Groomed Features:

  • Move to scoped search and drop elasticsearch
  • Content Host/Host Integration
  • Katello on an existing Foreman

Ungroomed:

  • Package applicability
  • Moving installer to 1.9.3/SCL (due to segfaults with newer puppet
    modules on 1.8.7)
  • Moving upgrade from kafo hooks to puppet based solution

[1]
http://projects.theforeman.org/rb/issues/backlog/product/katello?release_id=31

Please make sure reach out to scap since they have a similar issue.
– bk

··· On 02/24/2015 09:02 PM, Eric D Helms wrote: > All, > > With the branching of 2.2, we have identified some targets for 2.3. > These fall into 2 categories; stories we have broken out and those that > need exploration and grooming. The current set of stories that has been > assigned to the release can be seen at [1]. The below list may shift > over the next few weeks, and we welcome input from the community as to > what they would like to see. > > Groomed Features: > * Move to scoped search and drop elasticsearch > * Content Host/Host Integration

> * Move to scoped search and drop elasticsearch

Out of curiosity, how packages will be searched in Foretello after that
change? Will pulp provide searching capabilities?

··· -- Later, Lukas #lzap Zapletal

Hello,

could you point me to some issue or something related to

> Ungroomed:
> * Moving upgrade from kafo hooks to puppet based solution

Thanks

··· -- Marek

> > * Move to scoped search and drop elasticsearch
>
> Out of curiosity, how packages will be searched in Foretello after that
> change? Will pulp provide searching capabilities?
>

Similar to how they are today, just trading out Elasticsearch for the
existing Postgres database w/ scoped search. This is part of an effort to
standardization search across and remove. Justin already performed this
switch with Errata moving it into Postgres and fully searchable. The same
would be done for the other content types.

Eric

··· On Wed, Feb 25, 2015 at 3:38 AM, Lukas Zapletal wrote:


Later,
Lukas #lzap Zapletal


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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

>
>
>
>> All,
>>
>> With the branching of 2.2, we have identified some targets for 2.3.
>> These fall into 2 categories; stories we have broken out and those that
>> need exploration and grooming. The current set of stories that has been
>> assigned to the release can be seen at [1]. The below list may shift
>> over the next few weeks, and we welcome input from the community as to
>> what they would like to see.
>>
>> Groomed Features:
>> * Move to scoped search and drop elasticsearch
>> * Content Host/Host Integration
>>
>
> Please make sure reach out to scap since they have a similar issue.

Who is the best contact(s) to reach out to?

··· On Wed, Feb 25, 2015 at 6:27 AM, Bryan Kearney wrote: > On 02/24/2015 09:02 PM, Eric D Helms wrote:

– bk


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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

The background for this comes from this PR
https://github.com/Katello/katello-installer/pull/147#issuecomment-71537575
. I'll ping Stephen to explain a little further this issue.

Eric

··· On Feb 26, 2015 4:49 AM, "Marek Hulan" wrote:

Hello,

could you point me to some issue or something related to

Ungroomed:

  • Moving upgrade from kafo hooks to puppet based solution

Thanks


Marek


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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

> Hello,
>
> could you point me to some issue or something related to
>
> > Ungroomed:
> > * Moving upgrade from kafo hooks to puppet based solution
>
> Thanks

I plan to break the stories out here
http://projects.theforeman.org/issues/9515 when I get a minute.

Basically, we're doing the migrations of pulp, candlepin, etc in kafo
hooks (triggered by the --upgrade flag).

https://github.com/Katello/katello-installer/pull/147

But the problem is, we noticed an issue where we're running the pulp
migration before we update some mongo settings that we needed. It would
just be cleaner to do it all in Puppet, I think. We still need to work
out the details.

··· On Thu, Feb 26, 2015 at 11:49:37AM +0200, Marek Hulan wrote:


Marek


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-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Best Regards,

Stephen Benjamin
Red Hat Engineering

Try Shlomi and Simon.

– bk

··· On 02/25/2015 08:54 AM, Eric D Helms wrote: > > > On Wed, Feb 25, 2015 at 6:27 AM, Bryan Kearney > wrote: > > > > On 02/24/2015 09:02 PM, Eric D Helms wrote: > > All, > > With the branching of 2.2, we have identified some targets for 2.3. > These fall into 2 categories; stories we have broken out and > those that > need exploration and grooming. The current set of stories that > has been > assigned to the release can be seen at [1]. The below list may shift > over the next few weeks, and we welcome input from the community > as to > what they would like to see. > > Groomed Features: > * Move to scoped search and drop elasticsearch > * Content Host/Host Integration > > > Please make sure reach out to scap since they have a similar issue. > > > Who is the best contact(s) to reach out to?