Re: [foreman-dev] 1.17 branching - update 4

On Thu, Dec 14, 2017 at 6:08 PM, Ondrej Prazak wrote: > Hi, > quick summary about 1.17 branching status. The develop branch moved to > Rails 5 and turbolinks were added to tfm-ror51. Right now, the develop is > basically ready to move to Rails 5.1 by getting in [1]. When that is done, > there are

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

On Dec 22, 2017 8:12 PM, "Michael Moll" wrote: Hi, > Then I'd open a PR with the switch from Rails 5.0 to 5.1 and > https://github.com/theforeman/foreman/pull/5026 After that one got merged, only https://github.com/theforeman/foreman/pull/4836 was the missing final change. > After that one got

Re: [foreman-dev] Introducing #theforeman-dev-ui, an experiment

On Sat, Dec 16, 2017 at 2:38 AM, Greg Sutcliffe wrote: > On 14/12/17 16:04, Walden Raines wrote: > > The UX team is playing with the idea of forking UI discussions out > > into a separate channel. We will do a month long experiment and see > > how it goes. > > > > *Background:* The irc channel

Re: [foreman-dev] Proposal: Let's make notifications optional

On Wed, Dec 20, 2017 at 10:07 AM, Lukas Zapletal wrote: > Hello, > > while I agree that notifications is useful feature to our users, its > one second polling mechanism is killing me during development, it > makes watching logs or debugging sessions a nightmare. > > I propose an Administer - Sett

Re: [foreman-dev] Foreman instrumentation for telemetry proposal

On Thu, Dec 14, 2017 at 5:28 PM, Lukas Zapletal wrote: > Exactly, I based my proposal on Prometheus and Statsd. You can choose. > > I am going to work on my PR next week hopefully, but you can test it today: > > https://gist.github.com/lzap/2dfdd4dea29786a837cb1b7feb7862fd Don't you have a dock

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

e :) > We can consider using SSE for sending notifications too, but I'm uncertain how it would play with passenger. a more reliable approach would probably be to start using redis + websockets additional service proxied by apache (and webpack in development) Ohad > > On Wed, Dec

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

Dec 2017 at 17:50, Ohad Levy wrote: > On Wed, Dec 6, 2017 at 6:48 PM, Andrew Kofink wrote: > >> As part of this I would love to see *all* auto reloads default to off >>> >> > +1 - PR are welcomes ;) > > >> Oh yeah, especially notifications. Why can'

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

On Wed, Dec 6, 2017 at 6:48 PM, Andrew Kofink wrote: > As part of this I would love to see *all* auto reloads default to off >> > +1 - PR are welcomes ;) > Oh yeah, especially notifications. Why can't they just update when the > page updates? > > On Wed, Dec 6, 2017 at 11:27 AM, Walden Raines

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

On Wed, Dec 6, 2017 at 5:10 PM, 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 p

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

On Dec 6, 2017 7:41 AM, "Tomer Brisker" wrote: Hello, ​As many of you may have noticed, foreman-core open PR​ count has been in the area of 100-110 for most of the last few months. There are only a few people with merge access that actively review PRs, so that the time it takes for changes to be

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

On Mon, Dec 4, 2017 at 9:57 PM, Eric D Helms wrote: > > > On Thu, Nov 30, 2017 at 5:52 PM, Michael Moll wrote: > >> Hi, >> >> On Thu, Nov 30, 2017 at 02:20:09PM -0500, Eric D Helms wrote: >> > * Rails 5 SCL initial builds minus turbolinks exist [1] >> > * Turobolinks 2.4.5 is being released th

Re: [foreman-dev] Kanban tools and redmine

On Wed, Nov 29, 2017 at 1:26 PM, Greg Sutcliffe wrote: > On 28/11/17 21:29, Walden Raines wrote: > > Hey, > > > > With several teams moving to kanban style tools for the visualization of > > tasks I'm wondering if anyone has tried redmine's PluginKanban [1]. > > Haven't tried it, yet :). Performa

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Tue, Nov 21, 2017 at 11:02 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Sun, Nov 19, 2017 at 09:35:04PM +0100, Ewoud Kohl van Wijngaarden wrote: > >> On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote: >> >>> >>> Can

Re: Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Mon, Nov 20, 2017 at 2:36 PM, Daniel Lobato Garcia wrote: > On 11/20, Ohad Levy wrote: > > On Sun, Nov 19, 2017 at 10:35 PM, Ewoud Kohl van Wijngaarden < > > ew...@kohlvanwijngaarden.nl> wrote: > > > > > On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy w

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Sun, Nov 19, 2017 at 10:35 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote: > >> >> Can anyone shed some light on ETA for 1.16 GA? >> >> > I should have given an update ea

Re: [foreman-dev] Discourse summary week 2 (ish)

+1 On Fri, Nov 17, 2017 at 10:54 PM, Dmitri Dolguikh wrote: > Another +1 from me -- quite like the UI, email integration seems to be (or > will be?) good enough. As long as the amount of maintenance isn't too big, > I think the move is a good idea. > -d > > On Wed, Nov 15, 2017 at 7:05 AM, John

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Sep 25, 2017 6:56 PM, "Daniel Lobato Garcia" wrote: On 09/24, Ohad Levy wrote: > On Wed, Sep 20, 2017 at 10:04 AM, Daniel Lobato Garcia < elobat...@gmail.com> > wrote: > > > More updates on what's going on: > > > > On 09/14, Daniel Lobato Garc

Re: [foreman-dev] 1.17 branching schedule

On Thu, Nov 16, 2017 at 3:18 PM, Eric D Helms wrote: > Howdy, > > I am not clear on what the shape of everything else is, but I think there > are two larger updates that are in risk if we stick to our hard time based > releases here: > > 1) Dynflow as a stand-alone service used by Foreman which

Re: [foreman-dev] Proposal: Move Foreman Jenkins Jobs to foreman-ci repository

On Wed, Nov 8, 2017 at 3:42 PM, Greg Sutcliffe wrote: > On 08/11/17 12:35, Eric D Helms wrote: > > All, > > > > I brought this idea up in a separate thread, but want to formalize it > into > > it's own direct proposal. As of today, the Jenkins Job (JJB) > configurations > > live buried inside the

[foreman-dev] speeding up tests

Hi, The challenge: As a developer, I feel under utilized waiting for tests, the current test suite for foreman core takes over an hour, multiply it by number of really simple code fixes based on comment and it takes up a good chunk of a day. I would like to suggest a short and long term solution

Re: [foreman-dev] 1.17 schedule

On Tue, Oct 31, 2017 at 1:48 PM, Ondrej Prazak wrote: > Hi, > based on the Redmine release dates [1], 1.17 is supposed to be branched on > December 1st. Do we want to stick to this plan or do we want to take into > account that 1.16 was delayed? > > Let me know what you think, > Given the fact t

Re: [foreman-dev] Merge permissions to foreman-packaging

On Mon, Oct 23, 2017 at 7:16 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > Hello all, > > To get more involved in packaging I'd like to request merge access to > foreman-packaging. I've already been monitoring PRs and submitted various > patches[1][2]. > +1 > > Regards,

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

On Oct 20, 2017 11:39 AM, "Tomas Strachota" wrote: I'm also fine with removing them. I don't think it adds much value when we're moving towards UI based on React. I would be happy if someone compare UI responsiveness before we make the changes T. On Fri, Oct 20, 2017 at 8:17 AM, Ivan Necas

Re: [foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes

On Oct 12, 2017 3:56 AM, "Lisa Kachold" wrote: I have setup TheForeman 1.17.1-0 in a Development install on AWS. ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler errors using other versions) WEBrick 1.3.1 ALL Ports open from Server to my IP I changed Rails to listen on

Re: [foreman-dev] Redmine running slowly

On Wed, Oct 11, 2017 at 7:39 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Wed, Oct 11, 2017 at 07:36:39PM +0300, Ohad Levy wrote: > >> On Oct 11, 2017 5:40 PM, "Greg Sutcliffe" >> wrote: >> >> Update on migration: &

Re: [foreman-dev] Redmine running slowly

On Oct 11, 2017 5:40 PM, "Greg Sutcliffe" wrote: Update on migration: http://51.15.192.166 is now live for your testing pleasure, with a copy Any chance to update/enable https in the process? Thanks! of the DB from a few days ago. Email is currently disabled, so you can't spam anyone. There'

Re: [foreman-dev] Form inputs and accessibility

On Fri, Sep 29, 2017 at 7:16 PM, Walden Raines wrote: > Hey everyone, > > I would like to propose that we establish a requirement that all new form > inputs include both a unique ID attribute and a like so: > > Name: > > > For form fields where the is no label we should use bootstrap's .sr-only

Re: [foreman-dev] Access to foreman-infra

On Mon, Sep 25, 2017 at 3:01 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > Hello all, > > To get more involved in foreman infra I'd like to request push access to > foreman-infra. At first I'd like to help more with the CI. > > +1 from my side. > Regards, > Ewoud Kohl van

Re: [foreman-dev] Re: Database and Service Actions in RPM Post Scripts

On Mon, Sep 25, 2017 at 9:30 AM, Lukas Zapletal wrote: > I am all for pulling all complex changes out of post scriplets. > > On the other hand, I like that not calling an installer was always an > option, at least for minor releases. We have lots of users (mainly in > downstream) who did not buy

Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Wed, Sep 20, 2017 at 10:04 AM, Daniel Lobato Garcia wrote: > More updates on what's going on: > > On 09/14, Daniel Lobato Garcia wrote: > > Hi all, > > > > Just a heads up on the status of all of the upcoming releases: > > > > - 1.15.4 > > - After doing all the cherry-picks, 1.15.stable

Re: [foreman-dev] Permissions cleanup

On Mon, Sep 11, 2017 at 2:41 PM, Greg Sutcliffe wrote: > Hi all, > > In the context of the plugins-bus-factor discussion, etc, it occurred > to me that we still have a lot of people with access who aren't really > active any more - this can make it hard to see where action is needed. > > We've ne

Re: [foreman-dev] Re: Foreman core nightly is currently broken

On Tue, Sep 5, 2017 at 12:36 PM, Sebastian Gräßl wrote: > There is now another approach to fix this by using a plain Object instead > of a Map[1]. > This won't require any additional dependencies to be added. > > [1] https://github.com/theforeman/foreman/pull/4811 > Thanks Sebastian for the fix,

[foreman-dev] Foreman core nightly is currently broken

Hi, Following up on the recent thread about merging PR's, just to let you know that develop branch is currently broken due to [1] and PR to fix it as already available at [2] and hopefully it will be back to usual business within the next few hours. Please don't merge any JS related commits until

Re: [foreman-dev] Plugin gems with a single author

Kohl van Wijngaarden: > - smart_proxy_dns_powerdns > > Greg Sutcliffe: > - foreman_column_view > - foreman_default_hostgroup > > Marek Hulan: > - foreman_chef > - smart_proxy_chef > > Lukas Zapletal: > - smart_proxy_discovery_image > > Ohad Levy: > - for

Re: [foreman-dev] Syncing F26 external repo on Koji

On Tue, Jul 18, 2017 at 1:35 PM, Bryan Kearney wrote: > Why stop building against fedora? > see https://groups.google.com/d/msg/foreman-dev/uAk6LSfXsi4/B_xT2WRtCQAJ > > On Jul 17, 2017 4:27 PM, "Lukas Zapletal" wrote: > >> Hey, >> >> on pulp team request, I am adding external repository fedor

[foreman-dev] Proposal/Request - Foreman Ansible plugin - Dynamic inventory parameters definition

It seems I reject this mail by mistake, forwarding to the list to restart the conversation. -- Forwarded message -- From: juraj.fun...@gmail.com To: foreman-dev Cc: Bcc: Date: Fri, 14 Jul 2017 05:44:44 -0700 (PDT) Subject: Proposal/Request - Foreman Ansible plugin - Dynamic inven

[foreman-dev] Dropping Fedora 24 packages

Hi, Since Fedora 24 is out of maintenance, should we drop it? It also makes me wonder keep fedora packaging as a whole? Greg - can you have a look into how many people use it? thanks, Ohad -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To uns

Re: [foreman-dev] Nomination for an additional GitHub org owner

On Thu, Jul 6, 2017 at 1:41 PM, Tomer Brisker wrote: > Hello, > It has been a week, a bunch of +1s and no -1 here or in private. > Ohad - please add Greg to the repo owners. > Added - thanks Greg! > > On Thu, Jun 29, 2017 at 11:42 AM, Tomer Brisker > wrote: > >> Well, how about our fearless co

[foreman-dev] Rails 5.0 support merged

Hello, Since today, Foreman core develop branch has rails 5.0 support, thanks to the work Dominic Cleal initiated. Foreman now supports two version of rails, 4.2 (by default) and 5.0 (only on ruby 2.3 and newer). Since we don't plan on shipping rails 5.0 prior to 1.17 (where we plan to drop ruby

[foreman-dev] Using webpack/react in plugins

Hello, recently, a pr [1] was merged that now allow to use webpack [2] power in plugins as well - it means that now you can: - use ES6 in your javascript code, scss/css import etc etc - use react, or any other js library that is used by foreman core it self in your plugin (including react componen

Re: [foreman-dev] Re: Nomination for an additional GitHub org owner

On Fri, Jun 30, 2017 at 12:30 PM, Greg Sutcliffe wrote: > On Fri, 2017-06-23 at 13:44 +0100, Greg Sutcliffe wrote: > > ... my suggestion would be Eric Helms... > > A week has passed, I see many +1s and no -1s (and nothing sent to me in > private). Ohad, could you do the honours when you have a mo

Re: [foreman-dev] [Infra] Service accounts and secret storage

On Tue, Jun 27, 2017 at 5:54 PM, Greg Sutcliffe wrote: > On Tue, 2017-06-27 at 17:43 +0300, Ohad Levy wrote: > > > > Are you suggesting to host mail infra ourself > > Nope. > > > pay to google > > Nope. > > > or some other alternative? Changing DNS

Re: [foreman-dev] [Infra] Service accounts and secret storage

istribution list through google groups or >> the like to forward mails to for the shared email. >> > > That could work just as well though we should have some archive somewhere. > > On Tue, Jun 27, 2017 at 10:43 AM Ohad Levy wrote: >> >> On Tue, Jun 27, 2017 at 5:3

Re: [foreman-dev] [Infra] Service accounts and secret storage

On Tue, Jun 27, 2017 at 5:33 PM, Greg Sutcliffe wrote: > On Tue, 2017-06-27 at 13:03 +0200, Ewoud Kohl van Wijngaarden wrote: > > > > What are the options to use a @theforeman.org email address? Looks > > like google now requires money for that where it used to be free. > > The advantage would be

Re: [foreman-dev] Koji is back online

On Tue, Jun 13, 2017 at 5:21 PM, Eric D Helms wrote: > Lukas and Bryan big thanks for the time and effort getting this back > online. As well, the openness and status reports have been greatly > appreciated. > +1 Thanks Lukas and Bryan! > > > Eric > > On Jun 13, 2017 9:44 AM, "Lukas Zapletal"

Re: [foreman-dev] Dropping Ruby 2.0 support in 1.16?

On Thu, Jun 1, 2017 at 2:43 PM, Michael Moll wrote: > Hi, > > On Thu, Jun 01, 2017 at 01:53:40PM +0300, Tomer Brisker wrote: > > Considering no objections were raised, as a first step I have opened a PR > > to disable Ruby 2.0 tests for core & plugins: > > https://github.com/theforeman/foreman-in

Re: [foreman-dev] Unit test jenkins job with all plugins enabled

On Thu, Jun 1, 2017 at 2:10 PM, Marek Hulán wrote: > On čtvrtek 1. června 2017 12:17:25 CEST Lukas Zapletal wrote: > > Hello, > > > > I would like to open discussion about having a unit test job of > > foreman with all major plugins enabled (katello, discovery, bootdisk, > > rex, openscap). Some

Re: [foreman-dev] Dropping Ruby 2.0 support in 1.16?

On Thu, Jun 1, 2017 at 1:53 PM, Tomer Brisker wrote: > Considering no objections were raised, as a first step I have opened a PR > to disable Ruby 2.0 tests for core & plugins: > https://github.com/theforeman/foreman-infra/pull/296 > > I believe that 1.16 should require 2.1 at least, and I hope t

Re: [foreman-dev] Moments of Coffee Meeting: Fog and Compute Resrouces NG

On Mon, May 22, 2017 at 12:30 PM, Lukas Zapletal wrote: > Hey, > > I brought an interesting topic about RHEV support in Foreman, Ori > pointed out that RHEV v3 API is going to be deprecated soon (rumors > are 4.2 which is very soon) and since we are still using v3 via > rbovirt, it's the time to

[foreman-dev] Re: [foreman-users] Foreman TLV meetup

On Fri, May 19, 2017 at 2:30 PM, Ori Rabin wrote: > Hello all, > > In celebration of Foreman 1.15 release we will be holding a meetup in the > Red Hat offices in Israel. > > The meetup will be on June 7th between 17:30 and 21:00 IST. > The office is located at 34 Yerushalaim Rd, Raanana, Israel.

Re: [foreman-dev] Script to recycle passenger processes

On Wed, May 10, 2017 at 10:28 AM, Lukas Zapletal wrote: > Hello, > > I wrote a script that gracefully terminates Passenger processes > consuming more than 2.5 GB of private RSS memory. Typical consumption > of Foreman with Katello and other basic plugins is around 1.5 GB and > since only Passenge

Re: [foreman-dev] vmware html5 console support

On Sat, May 6, 2017 at 1:09 AM, Michael Eklund wrote: > I am interested in support for the html5 console for vmware in place of > the vnc console. I have a proof of concept of sorts by overwriting the > vm_console call in compute_resources_vms_helper.rb. The jist of it is a > url that looks lik

[foreman-dev] Re: Notification content

On Wed, Jan 25, 2017 at 9:42 AM, Ohad Levy wrote: > Hi, > > As you probably heard (and saw in the last demo) we have a new > notification system, now its time to start using and improving it. > > here are some of the content I think make sense to discuss, comments etc > ar

Re: [foreman-dev] Ansible based foreman-installer

On Mon, Mar 13, 2017 at 9:22 PM, Michael Hofer < michael.ho...@adfinis-sygroup.ch> wrote: > Hi all > > Some time ago there was a discussion about having an (alternative) Ansible > based > foreman-installer. Is someone still interested in such an implementation? I > don't want to advertise our play

Re: [foreman-dev] Using sync task for running Ansible plays hangs Foreman

On Mon, Mar 13, 2017 at 12:09 PM, wrote: > Hello, > > I have an issue with triggering synchronous tasks in foreman-tasks. I have > written a plugin that is triggering an Ansible Play as a foreman-tasks' > sync_task (the foreman_ansible plugin itself uses only asynchronous > tasks, but I want the

Re: [foreman-dev] No provisioning templates in dev foreman

On Thu, Mar 9, 2017 at 10:46 PM, Tyler Gregory wrote: > Hello all, > > I'm developing a plugin so that foreman can use Azure Resource Manager, > and I'm at the point where I would like to start deploying some VMs. I've > set up a development environment as described here >

Re: [foreman-dev] Speed up rake apipie:cache:index

On Mar 6, 2017 11:11 AM, "Martin Bačovský" wrote: The current state is that the apipie cache consists of root index page and page per API resource and method and JSON desription of whole API (multiplied by number of languages). Currently we build all the resource specific pages during the packag

Re: [foreman-dev] Speed up rake apipie:cache:index

On Mon, Mar 6, 2017 at 10:34 AM, Tomas Strachota wrote: > It's used for generating both html doc pages and json (consumed by > apipie bindings). We can't get rid of iterating over languages, but > generating docs only in json format and having html page that loads it > async and generates the con

Re: [foreman-dev] Dev/Design weekly meeting notes: Subscription.Next

On Wed, Feb 22, 2017 at 5:44 PM, Roxanne Hoover wrote: > Link to Google Docs: https://docs.google.com/document/d/1IsylCDVXl7_ > CiMEO5dCofhqcOReX4l9-Tv-jXcWG1y4/edit > > > Subscription.Next > > Presented by Thomas McKay > > Subscriptions through Content > > > Product> Detailed page > > > Products

Re: [foreman-dev] Re: Seeding templates overrides custom changes - should we lock templates we ship?

On Mon, Feb 20, 2017 at 4:58 PM, Ivan Necas wrote: > Timo Goebel writes: > > > +1 to locking. This is the only workflow that makes sense imho. > > Please note, that we need [1] merged first. > > +1 - let's set the right expectations > I think its +1 across, the main question i have is is a mino

Re: [foreman-dev] Re: showing the hidden "Select Action" button on all hosts page

On Thu, Feb 2, 2017 at 11:51 AM, Marek Hulán wrote: > Hello, > > I also think the button should be displayed even without selecting any > item. > > I've created http://projects.theforeman.org/issues/18364 Ohad > -- > Marek > > On středa 1. února 2017 12:48:10 CET Roxanne Hoover wrote: > > Tom,

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

On Fri, Jan 27, 2017 at 12:23 AM, Greg Sutcliffe wrote: > I'll comment on the rest of this when I have time to think it over, > however I > do want to correct one point: > > On Thursday, 26 January 2017 10:27:47 CET Lukas Zapletal wrote: > > > This is only relevant to provision, iPXE and script t

[foreman-dev] Notification content

Hi, As you probably heard (and saw in the last demo) we have a new notification system, now its time to start using and improving it. here are some of the content I think make sense to discuss, comments etc are welcomed: first, I would like to group notification based of topic, for example, prov

Re: [foreman-dev] disable logging of GET /notification_recipients

On Wed, Jan 25, 2017 at 12:52 AM, Tom McKay wrote: > My email history search failed but I think there is a way to disable > logging of certain api routes; anyone know how? > > I'd like to suggest that we disable the logging of > > 2017-01-24T22:51:22 9e5f9d73 [app] [I] Started GET > "/notificatio

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

On Tue, Jan 24, 2017 at 9:51 AM, Ivan Necas wrote: > Ewoud Kohl van Wijngaarden writes: > > > On Tue, Jan 24, 2017 at 12:10:34AM +0100, Ivan Necas wrote: > >> Ohad Levy writes: > >> > >> > On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal > wr

Re: [foreman-dev] Moving foreman-tasks to the core: the plan

On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal wrote: > Why we haven't considered ActiveJob API in the first place? This looks > like ideal solution, easy development and documented API. > > Can't ActiveJob help us with memory issues we have with external task > executor in Katello? I mean what

Re: [foreman-dev] Foreman bootloaders effort

On Tue, Jan 3, 2017 at 9:47 AM, Lukas Zapletal wrote: > All right, I hereby ask creating new repository foreman-bootloaders under > theforeman organization. Since 1.14 is almost done, I would like to have > first nightly builds available so users can start testing this. > I've created https://g

Re: [foreman-dev] Draft community survey questions

On Wed, Dec 21, 2016 at 10:04 PM, Greg Sutcliffe wrote: > Hi all, > > Last year I rushed the community survey, and forgot to get feedback on the > questions it contained - I'm not making that mistake again :) > > Below is the draft question set - fair warning, its a big email :P. My aim > is to e

Re: [foreman-dev] Vertical Navigation

10:55:51 AM UTC-5, Walden Raines >>>> wrote: >>>>> >>>>> > is there an assumption we should move to full width with this >>>>> change? >>>>> >>>>> I personally was making that assumption based on the scre

Re: [foreman-dev] Vertical Navigation

ing that assumption based on the screen in the >>> patternfly vertical navigation documentation [1] and I support using a >>> container that is very close to full width (i.e. you'll still want some >>> padding so you can easily tell that things aren't appearing o

Re: [foreman-dev] Katello 3.3 Branching in 1 week

On Thu, Dec 15, 2016 at 3:10 PM, Eric D Helms wrote: > > > On Wed, Dec 14, 2016 at 4:17 AM, Ohad Levy wrote: > >> >> >> On Tue, Dec 13, 2016 at 12:29 AM, Justin Sherrill >> wrote: >> >>> Will branch towards the end of the day December 19th &g

Re: [foreman-dev] Katello 3.3 Branching in 1 week

On Tue, Dec 13, 2016 at 12:29 AM, Justin Sherrill wrote: > Will branch towards the end of the day December 19th > Just out of curiosity, why don't you branch as the same time as foreman does? if you do that, it would be much easier to align the release dates? Ohad > > -Justin > > -- > You rece

Re: [foreman-dev] Nominating Katello.org devs for theforeman/theforeman.org commit access

On Tue, Dec 13, 2016 at 9:19 PM, Daniel Lobato wrote: > One week has passed! > I've added the new members - welcome :) > > On Thu, Dec 8, 2016 at 5:35 PM, Greg Sutcliffe > wrote: > > +1 > > > > -- > > You received this message because you are subscribed to the Google Groups > > "foreman-dev"

Re: [foreman-dev] Nominating Katello.org devs for theforeman/theforeman.org commit access

On Wed, Dec 7, 2016 at 12:26 AM, Daniel Lobato Garcia wrote: > Hi devs, > > I'd like to nominate ehelms, jlsherrill, beav and johnpmitch for commit > access on theforeman.org. > > They have been maintaining katello.org this year, and from what I see > these are the top contributors in that repos

Re: [foreman-dev] Re: New community-templates structure

On Wed, Nov 30, 2016 at 10:13 AM, wrote: > > For navigation (reading) IMHO kind/subkind works well (although I have to > admit I am not a sysadmin - I didn't have to do it as my day job) > What about modification use case? > Is there any use case where a user wants to modify multiple templates fr

Re: [foreman-dev] Vertical Navigation

On Tue, Nov 22, 2016 at 3:57 PM, Walden Raines wrote: > +1 I'm a fan of switching to a vertical navigation but I do have one > question. > > Is there a pattern for being able to collapse the vertical navigation? At > times you don't need the navigation at all and it takes up roughly 1/6th of > t

Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test failures)

On Thu, Nov 3, 2016 at 3:50 PM, Greg Sutcliffe wrote: > More generally, does it make sense for someone to do an audit of the most > common > places that plugins hook in, and make sure we have tests for them? > I don't think its a lack of tests, but rather someone updates a method and its tests f

Re: [foreman-dev] Foreman Ansible Tasks Pending

On Mon, Oct 31, 2016 at 9:41 PM, Daniel Kuffner wrote: > Hi All, > > I want to try our Foreman with ansible. I have installed the plugin and > the ansible call back. Ansible and Foreman is on the same host machine. > When I press "|> Ansible Role" on my selected host then I can see that a > task

Re: [foreman-dev] Use mention-bot to increase reviews?

On Mon, Oct 17, 2016 at 4:02 PM, Greg Sutcliffe wrote: > On 13 October 2016 at 13:28, Eric D Helms wrote: > >> This has been turned on for the Katello repo, if devs find it needs >> tweaking there is a configuration file that can be added ( >> https://github.com/facebook/mention-bot#configuratio

Re: [foreman-dev] Move rsync to rsync.theforeman.org

On Thu, Oct 27, 2016 at 10:49 AM, Dominic Cleal wrote: > Ohad, could you create another CNAME at rsync.theforeman.org to point > back to web02.theforeman.org? > done > > I'd like to begin moving rsync traffic from {apt,downloads,yum} to use a > separate rsync name so it's separate from HTTP(S) t

Re: [foreman-dev] Issues needed in 1.13.1

On Wed, Oct 26, 2016 at 10:36 AM, Dominic Cleal wrote: > On 25/10/16 17:33, Eric D Helms wrote: > > Can we please have the following two issues included into Foreman 1.13.1 > > via puppet-foreman_proxy release update? > > > > https://github.com/theforeman/puppet-foreman_proxy/commit/ > 9b75833407

Re: [foreman-dev] Freeze edits on a host?

On Tue, Sep 20, 2016 at 9:43 AM, oprazak wrote: > I believe there is already a related feature request in our Redmine: > > http://projects.theforeman.org/issues/10799 > > and potentially related - http://projects.theforeman.org/issues/499 Ohad > On Wednesday, September 14, 2016 at 4:13:43 PM UT

[foreman-dev] Using certificates for SSH access

Hi, I was looking at [1] which talks about how to leverage a CA for managing SSH access, and I thought it could be interesting for REX and potentially for foreman to manage. In the post, they describe how they create different principles (groups - think hostgroups) for access, generating certific

Re: [foreman-dev] CfP entry for CfgMgmt camp in Berlin

On Tue, Sep 6, 2016 at 11:35 AM, Daniel Lobato Garcia wrote: > On 09/05, Lukas Zapletal wrote: > > I just submitted for the record: > > > > Abstract: > > > > First, it starts with a DVD with an OS installer, then is a recipe to > > automate it. And then PXE booting from network which sometimes le

Re: [foreman-dev] Intermittent Slave Timeouts

On Tue, Aug 30, 2016 at 7:48 PM, Eric D Helms wrote: > Do we have any idea what is causing the intermittent errors pulling > rubygems on the Rackspace slaves? The errors take the form of: > > *15:12:36* ERROR: While executing gem ... > (Gem::RemoteFetcher::FetchError)*15:12:36* Errno::ETIME

[foreman-dev] Adding GitHub label for all UI/Visual enhancements

Hi, Now that we have a dedicated UX professional (Hi Roxanne :-) ) I would like to suggest that we add a new label for every work that has a UI element to it, the aim is to expose UI changes to wider group (e.g beside the reviewer) that other people can provide feedback, ideally across all foreman

Re: [foreman-dev] Using tmpfs significantly reduces testing time

On Sun, Aug 21, 2016 at 9:35 AM, wrote: > > I heard that there is an option to use sqlite in-memory. > I gave to admit I didn't try it, but I think it worth mentioning. > first google hit: http://www.calicowebdev.com/2011/01/25/rails-3-sqlite-3-in-memory-databases/ Ohad > > > On Friday, August

Re: [foreman-dev] Deprecate EL6?

On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms wrote: > This thread has seen a revival with many points being made on both sides. > However, things have gone cold for nearly a week now and there are > processes and decisions that hinge on the outcome with respect to users and > developers alike. Ar

Re: [foreman-dev] List moderation "always allow posts" errors

On Thu, Aug 4, 2016 at 3:33 PM, Dominic Cleal wrote: > Are any other list moderators (of either -dev or -users) getting the > following errors when allowing the current plus future posts from a user? > > "One message has been posted. Failed to always allow posts from > u...@example.com due to err

Re: [foreman-dev] Re: Re: Status of RPM packaging for npm modules in Foreman

ed in a simple tar >> ball or a single package containing everything. >> Lets finish this, please, one way or another, so we can concentrate on >> building a better Foreman for our community. >> >> Tomer >> >> >> On Fri, Jul 22, 2016 at 10:26 PM, Ohad L

Re: [foreman-dev] Deprecate EL6?

On Tue, Jul 26, 2016 at 4:36 PM, Dominic Cleal wrote: > On 26/07/16 14:17, Ohad Levy wrote: > > +1 I believe 1.14 is a more suitable candidates. mostly after having a > > proper backup/restore procedure to migrate foreman, proxy and plugins. > > The manual already ha

Re: [foreman-dev] Deprecate EL6?

On Tue, Jul 26, 2016 at 4:13 PM, Eric D Helms wrote: > > > On Tue, Jul 26, 2016 at 4:46 AM, Dominic Cleal wrote: > >> On 10/05/16 10:26, Dominic Cleal wrote: >> > I'd like to propose a deprecation of EL6 for Foreman 1.12, so we have >> > the option of leaving it out of the 1.13 release. >> >> I'

Re: [foreman-dev] Re: Re: Status of RPM packaging for npm modules in Foreman

On Jul 22, 2016 9:01 PM, "Daniel Lobato Garcia" wrote: > > On 07/22, Daniel Lobato Garcia wrote: > > On 07/21, Daniel Lobato Garcia wrote: > > > > > 3. Put node_modules in a new package (foreman-npm-assets?) that > > > foreman-assets %install section puts in the right place? > > > > > > - Upside

Re: [foreman-dev] Status of RPM packaging for npm modules in Foreman

On Thu, Jul 21, 2016 at 12:46 PM, Daniel Lobato Garcia wrote: > Hi devs, > > Just wanted to give you an update on packaging for npm & webpack > incidentally. We have two PRs in core that are dabbling in a more modern > way of doing frontend development in Foreman. > https://github.com/theforeman/

Re: [foreman-dev] Jenkins Email Notifications

On Thu, Jul 21, 2016 at 9:55 AM, Dominic Cleal wrote: > Ohad, can you add a record for ci.theforeman.org to > 2001:4802:7802:102:1da0:e668:ff20:49f8 please? I'll update the reverse. > done. Ohad -- You received this message because you are subscribed to the Google Groups "foreman-dev" g

Re: [foreman-dev] httpd fails to start after being updated

On Tue, Jun 14, 2016 at 2:18 PM, Lukas Zapletal wrote: > > > > an rm -rf on the conf.d/ssl.conf file > > I have a clean Foreman installation on CentOS7 and this file does not > appear to be present: > > [root@fseven ~]# rpm -q httpd > httpd-2.4.6-40.el7.centos.1.x86_64 > > [root@fseven ~]# ls /et

Re: [foreman-dev] Re: Foreman Community Demo Items - Thu 19 May

On May 18, 2016 14:56, "Greg Sutcliffe" wrote: > > Reminder, this is tomorrow and we only have one presenter thus far. > > My redmine metrics say that we've closed 164 bugs and 28 features since the last demo - surely someone has something to say about some of them? :) Puppet 4 support? :) > > Gr

Re: [foreman-dev] Deprecate EL6?

On Mon, May 16, 2016 at 2:14 PM, Dominic Cleal wrote: > On 16/05/16 12:07, Ohad Levy wrote: > > IMHO if you see a yum user agent grabbing a metadata file thats a > > consistent and reliable way to know that there is a configured system > > using it, it might be a stale rep

Re: [foreman-dev] Deprecate EL6?

On Mon, May 16, 2016 at 12:40 PM, Greg Sutcliffe wrote: > On 13 May 2016 at 10:56, Ohad Levy wrote: > > > > What about repository metadata queries? (That should be anyone with yum > repository configured doing a yum update/search etc). > > Can't say from the apache