As part of the migration to scoped_search for katello Eric and I are
currently in the process of migrating Packages and Puppet Modules. These
are the last two main content types to be removed, so it makes sense to
remove content search as part removing these two pieces. With that we
have a couple options:
As part of migrating packages and puppet modules, modify Content
Search to remove each one. This would leave content search completely
useless and able to be removed.
Go ahead and remove content search and then migrate packages and
puppet modules (which are already in progress)
I'd prefer option 2, as it would simplify the migration process for
those two content types. I have gone ahead and opened a PR here:
Thoughts?
Note that existing UI (and UI added as part of the package and
puppet_module migration) should fill all the use caes content search is
providing today with the exception of comparison. We have added to
current Core sprint go come up with a design for implementing comparison
of the different types across content view versions.
>
> As part of the migration to scoped_search for katello Eric and I are
> currently in the process of migrating Packages and Puppet Modules. These
> are the last two main content types to be removed, so it makes sense to
> remove content search as part removing these two pieces. With that we
> have a couple options:
>
> 1. As part of migrating packages and puppet modules, modify Content
> Search to remove each one. This would leave content search completely
> useless and able to be removed.
> 2. Go ahead and remove content search and then migrate packages and
> puppet modules (which are already in progress)
It seems like both options will have the same result at the end, so
+1 for 2., as it seems it makes the life easier. The only problem would be,
if there was missing content search, and the packages/modules not converted
to scoped search, at the time of Katello release.
– Ivan
···
----- Original Message -----
I’d prefer option 2, as it would simplify the migration process for
those two content types. I have gone ahead and opened a PR here: https://github.com/Katello/katello/pull/5299
Thoughts?
Note that existing UI (and UI added as part of the package and
puppet_module migration) should fill all the use caes content search is
providing today with the exception of comparison. We have added to
current Core sprint go come up with a design for implementing comparison
of the different types across content view versions.
>
>> As part of the migration to scoped_search for katello Eric and I are
>> currently in the process of migrating Packages and Puppet Modules. These
>> are the last two main content types to be removed, so it makes sense to
>> remove content search as part removing these two pieces. With that we
>> have a couple options:
>>
>> 1. As part of migrating packages and puppet modules, modify Content
>> Search to remove each one. This would leave content search completely
>> useless and able to be removed.
>> 2. Go ahead and remove content search and then migrate packages and
>> puppet modules (which are already in progress)
> It seems like both options will have the same result at the end, so
> +1 for 2., as it seems it makes the life easier. The only problem would be,
> if there was missing content search, and the packages/modules not converted
> to scoped search, at the time of Katello release.
Yeah, we don't have to merge the content search removal PR until the
other two get opened and that would minimize the window. If for some
reason they didn't both make 2.3, we could backport the needed code, as
it should be a very short time window.
-justin
···
On 06/15/2015 04:31 AM, Ivan Necas wrote:
> ----- Original Message -----
– Ivan
I’d prefer option 2, as it would simplify the migration process for
those two content types. I have gone ahead and opened a PR here: https://github.com/Katello/katello/pull/5299
Thoughts?
Note that existing UI (and UI added as part of the package and
puppet_module migration) should fill all the use caes content search is
providing today with the exception of comparison. We have added to
current Core sprint go come up with a design for implementing comparison
of the different types across content view versions.
On Monday 15 of June 2015 04:31:17 Ivan Necas wrote:
----- Original Message -----
As part of the migration to scoped_search for katello Eric and I are
currently in the process of migrating Packages and Puppet Modules. These
are the last two main content types to be removed, so it makes sense to
remove content search as part removing these two pieces. With that we
have a couple options:
As part of migrating packages and puppet modules, modify Content
Search to remove each one. This would leave content search completely
useless and able to be removed.
Go ahead and remove content search and then migrate packages and
puppet modules (which are already in progress)
It seems like both options will have the same result at the end, so
+1 for 2., as it seems it makes the life easier. The only problem would be,
if there was missing content search, and the packages/modules not converted
to scoped search, at the time of Katello release.
– Ivan
I’d prefer option 2, as it would simplify the migration process for
those two content types. I have gone ahead and opened a PR here: https://github.com/Katello/katello/pull/5299
Thoughts?
Note that existing UI (and UI added as part of the package and
puppet_module migration) should fill all the use caes content search is
providing today with the exception of comparison. We have added to
current Core sprint go come up with a design for implementing comparison
of the different types across content view versions.
