Re: [foreman-dev] Be sure to import your product content data for Katello 3.6

On Thursday, December 7, 2017 at 6:04:45 AM UTC-5, Ewoud Kohl van Wijngaarden wrote: > > On Wed, Dec 06, 2017 at 07:07:05AM -0800, Jonathon Turel wrote: > >A change > >< > https://github.com/Katello/katello/commit/946b2990c9a054babc9ad563e1b14c4161207b3e> > > > >landed in Katello yesterday

Re: [foreman-dev] Custom hiera in Katello 3.4 deployment

On Thu, Dec 07, 2017 at 04:16:14PM +0100, Lukas Zapletal wrote: I have Katello 3.4 and I created this file: /etc/foreman-installer/custom-hiera.yaml --- dns::zones: home.lan: soa: winter.home.lan soaip: 192.168.99.1 contact: hostmaster.home.lan. After re-running the installer (in

Re: [foreman-dev] Be sure to import your product content data for Katello 3.6

On Thursday, December 7, 2017 at 5:31:44 AM UTC-5, Eric Helms wrote: > > This sounds great! How long on average are you seeing the import take? > In my environment I have two orgs each with a manifest, totaling 270 products. It's been taking about a minute to run the rake task (including the

[foreman-dev] Custom hiera in Katello 3.4 deployment

Hey, I have Katello 3.4 and I created this file: /etc/foreman-installer/custom-hiera.yaml --- dns::zones: home.lan: soa: winter.home.lan soaip: 192.168.99.1 contact: hostmaster.home.lan. After re-running the installer (in dry mode) nothing really happens. This is already

Re: Re: [foreman-dev] RFC Auto Refresh on ForemanTasks#Tasks Page

> > notification updates (they're cached) are only a hassle because they're > logged Agreed. In development, the extra logs make debugging more difficult; performance is not the motivation. On Thu, Dec 7, 2017 at 10:08 AM, Daniel Lobato Garcia wrote: > On 12/06, Ohad Levy

Re: [foreman-dev] 1.17 branching - status update 3

I would rather go with option 1 to avoid a large amount of cherry-picks. Thanks for pointing out the fog update. On Thu, Dec 7, 2017 at 3:52 PM, Eric D Helms wrote: > Thanks for the weekly updates! > > Do you forsee 1.17 working as: > > 1) Wait till the core codebase is

Re: Re: [foreman-dev] RFC Auto Refresh on ForemanTasks#Tasks Page

On 12/06, Ohad Levy wrote: > On Wed, Dec 6, 2017 at 9:10 PM, Walden Raines wrote: > > > > Oh yeah, especially notifications. Why can't they just update when the > > page updates? > > > > I think it would be good to move the notifications to a websocket approach > > instead of

Re: Re: [foreman-dev] Nominating additional maintainers in foreman-core

On 12/06, Ewoud Kohl van Wijngaarden wrote: > On Wed, Dec 06, 2017 at 02:40:36PM +0200, Tomer Brisker wrote: > > Shimon Shtein - has 75 merged commits [1] and has taken part in the reviews > > of 64 merged commits[2]. > > +1 +1 > > > Michael Moll - has 71 merged commits [3] and has taken part in

Re: [foreman-dev] Is it time to remove turbolinks?

On 12/06, Walden Raines wrote: > I am seeing more and more issues [1][2] around turbolinks and I'm wondering > if it's time to remove it from foreman. I have seen it recommended that > one shouldn't use the back button in foreman; I thought that request was > reserved for poorly written php sites

Re: [foreman-dev] 1.17 branching - status update 3

Thanks for the weekly updates! Do you forsee 1.17 working as: 1) Wait till the core codebase is updated to Rails 5.1 then branch and notify plugins 2) Branch soon at some stable point and backport the Rails 5.1 code changes I believe also on the list of items is the update to fog 1.42 that

[foreman-dev] Milestones added on GH for upcoming core releases

Hello, I've added milestones on GH for 1.16.1 and 1.17.0 releases to make it easy to see which issues are blocking a certain release. Maintainers - please update PRs if they need to be included in a certain release. ​Perhaps we can also look​ into automating this to align release field on redmine

[foreman-dev] 1.17 branching - status update 3

Hi, this is a quick summary of current 1.17 branching status. As before, feel free to correct/complete the information below. The new version of turbolinks-classic (2.5.4) was released about 12 hours ago, and we work on adding it to tfm-ror51 [1]. Dynflowd deployment on Debian is almost ready to

Re: [foreman-dev] The road to Rails 5.1

Hi, On Thu, Nov 30, 2017 at 11:52:24PM +0100, Michael Moll wrote: > > Would someone with more knowledge on the code side of the Rails 5 mind > > sending along an update of the path we see for getting to 5.1? > > We're currently blocked by two external dependencies: > -

Re: [foreman-dev] Is it time to remove turbolinks?

+1 to the comments above, moving forward with React will allow us to drop turbolinks at some point without a noticeable decrease in UI performance - at least that is my hope. On Wed, Dec 6, 2017 at 5:46 PM, Ohad Levy wrote: > > > On Wed, Dec 6, 2017 at 5:10 PM, Walden Raines

Re: [foreman-dev] Be sure to import your product content data for Katello 3.6

On Wed, Dec 06, 2017 at 07:07:05AM -0800, Jonathon Turel wrote: A change landed in Katello yesterday which introduced a new pattern of importing product content information from Candlepin into the Katello DB.

Re: [foreman-dev] Be sure to import your product content data for Katello 3.6

This sounds great! How long on average are you seeing the import take? On Dec 6, 2017 10:07 AM, "Jonathon Turel" wrote: > Hi all, > > A change > > landed in Katello yesterday which introduced

Re: [foreman-dev] Nominating additional maintainers in foreman-core

Yes, please. We can use all the help we can get and both Shimon and Michael are doing great work. Thanks Tomer for bringing this up. > On 7. Dec 2017, at 09:23, Ondrej Prazak wrote: > > +1 to both > >> On Wed, Dec 6, 2017 at 5:19 PM, Ivan Necas wrote: