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

On Wed, Dec 20, 2017 at 9:09 AM, Ohad Levy wrote: > > > 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

Re: [foreman-dev] speeding up tests

On Tue, Nov 7, 2017 at 11:17 AM, Ivan Necas wrote: > On Tue, Nov 7, 2017 at 9:29 AM, Lukas Zapletal wrote: >> We should start tracking test breakages in time, if we have a test >> that did not break for a year, lets delete it. As simple as that. It's >> added

Re: [foreman-dev] Proposed drop of supporting ruby 2.0 in hammer

, Andrew Kofink <akof...@redhat.com> wrote: > +1 out with the old > > On Tue, Oct 10, 2017 at 8:00 AM, Michael Moll <kved...@kvedulv.de> wrote: >> >> On Tue, Oct 10, 2017 at 01:45:42PM +0200, Ewoud Kohl van Wijngaarden >> wrote: >> > On Tue, Oct 10,

[foreman-dev] Proposed drop of supporting ruby 2.0 in hammer

Hi all, we recently encountered a compatibility issue with older version of Clamp that we use on ruby 2.0 installations. Latest Clamp releases require ruby 2.1+. See [1] for some more details. The easiest solution seems to be dropping ruby 2.0 support, which was eol 2016-02-24 anyway. We use scl

Re: [foreman-dev] [Infra] Reducing Test Matrix

On Wed, Aug 23, 2017 at 5:37 PM, Ivan Necas wrote: > > On Wed, 23 Aug 2017 at 15:10, Eric D Helms wrote: >> >> There are a few different points to reply to, hopefully I did not miss >> one. For the base topic, based on feedback and target for post 1.16, I

Re: [foreman-dev] API usage - getting Hosts in Hostgroup

> Hi Thomas , > > Thanks for your response , any workaround for the rest api interface? > > Thanks , > Roy > > On Wednesday, August 16, 2017 at 11:10:25 AM UTC+3, Tomas Strachota wrote: >> >> Hello, >> this is a known bug: >> http://projects.theforeman.or

Re: [foreman-dev] kerberos auth for the API

Hello, yes, kerberos API authentication is tracked in the issue that you sent. Unfortunately there's really no solution yet. Important prerequisites have been released with the Foreman 1.15 (session support in the API) but the API still lacks entry point for external login (equivalent of

[foreman-dev] Entry level hammer issues

Couple of people has asked me about some easy to fix issues in hammer that would be good to start with if they wanted to learn hammer and deep into its waters slowly. I went through the backlog and picked a few tasks that I think should be simple to fix. The current list is at [1] and I'll try to

[foreman-dev] Shareable makefile and rake tasks for extracting translations in hammer

Past two hammer-cli and hammer-cli-foreman releases we experienced some issues with merging translations, fuzzy matching or generating .mo files, which caused us to update the rake tasks and Makefile we use for extracting strings and merging translations. Probably all translated hammer plugins

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

On Mon, Jun 5, 2017 at 4:14 PM, Lukas Zapletal wrote: > On Mon, Jun 5, 2017 at 2:48 PM, Tomer Brisker wrote: >> My suggestion is that we replace the katello test currently running on every >> PR with a test that installs the top 5 plugins together and runs

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

On Tue, May 23, 2017 at 10:07 AM, Ivan Necas wrote: > Timo Goebel writes: > >>> On 22. May 2017, at 12:27, Ohad Levy wrote: >>> >>> Since we get a lot of lift from fog, especially for popular providers (e.g. >>> ec2) IMHO its not a

[foreman-dev] hammer-cli and hammer-cli-foreman 0.10.2 released

New minor versions of hammer-cli and hammer-cli-foreman were released. They contain fixes around fetching server CA certs and retry mechanism when session expires. This should go to the next foreman 1.15 RC. PR into rpm packaging is open at:

Re: [foreman-dev] hammer-cli, -foreman version numbers on master

Done, versions in both repos bumped to 0.11-develop and strings extracted in the master. Thanks T. On Fri, May 5, 2017 at 3:25 PM, Dominic Cleal <domi...@cleal.org> wrote: > On 05/05/17 14:21, Tomas Strachota wrote: >> Is it enough just to bump the version to 0.11-develop or do

Re: [foreman-dev] hammer-cli, -foreman version numbers on master

Is it enough just to bump the version to 0.11-develop or do I need to do whole new release? T. On Fri, May 5, 2017 at 11:11 AM, Dominic Cleal wrote: > The version numbers on hammer-cli and hammer-cli-foreman's master > branches are currently behind the latest release (from

Re: [foreman-dev] [RFC] Proposal: make foreman STI to work even when an inherited class is not found in Ruby.

This issue is tightly coupled with plugin uninstallation and I think we should solve the two problems together. At the moment there's no standard plugin uninstallation procedure that would take care of cleaning up the system. This is something each plugin should provide. One thing (imho the less

Re: [foreman-dev] Organization titles in CLI

llow > updating that attribute (i.e. --parent/--parent-id)? We already have a > handler in the ID resolver when multiple records are returned when only one > is expected, though the error message does not tell the user how to further > filter the results. > > - Andrew > > On Mon, Ap

Re: [foreman-dev] Re: 1.15 branching in approximately 2 weeks

16, 2017 at 11:45 AM, Dmitri Dolguikh <witlessb...@gmail.com> > wrote: >> On Wed, Mar 15, 2017 at 8:10 AM, Tomas Strachota <tstra...@redhat.com> wrote: >>> On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato <elobat...@gmail.com> wrote: >>>> We're plannin

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

On Mon, Mar 6, 2017 at 10: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

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

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 content dynamically would probably bring the desired speedup. I like

Re: [foreman-dev] Host Creation

On Thu, Feb 9, 2017 at 5:27 PM, Tom McKay wrote: > I like the "add" buttons (eg. operating system) but there were some > resources that didn't have add buttons (eg. partition tables). Should all of > the associated resources have buttons? Not UX specifically, but it would

Re: [foreman-dev] Opinions from plugin maintainers wanted: permissions and roles

On Mon, Jan 16, 2017 at 6:55 PM, oprazak wrote: > Hi, > I recently started identifying problematic areas in Permissions and Roles, > especially with regard to plugins. Foreman provides 'Viewer' and 'Manager' > roles out of the box and users expect these roles to work for

Re: [foreman-dev] Draft community survey questions

On Wed, Dec 21, 2016 at 9: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

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

On Fri, Nov 25, 2016 at 3:40 PM, Marek Hulán wrote: > Hello foreman devs, > > As I demonstrated on last community demo [1] templates can be now easily > exported from Foreman. I also mentioned that I'm working [2] on > foreman_templates feature to easily export all templates to

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

On 10/17/2016 03:26 PM, Greg Sutcliffe wrote: On 17 October 2016 at 14:12, Lukas Zapletal > wrote: > This appears more inconsistent than the current situation, as there will > now be three terms, differing between the UI names ("Foreman Smart > Proxy"),

Re: [foreman-dev] hammer requires ruby >= 2.1.0

On 08/31/2016 01:13 PM, David Davis wrote: We probably need to pin the version to 1.1.0. It looks like 1.2.0 which came out this month requires ruby >= 2.1.0. Yes, the requirement is quite new, but we actually need 1.2.0 to get the performance improvements it received recently. As Tomer

Re: [foreman-dev] Re: RFC for foreman_api_v3

21/hosts What do you think? -- Dominic Cleal domi...@cleal.org <mailto:domi...@cleal.org> On Fri, Aug 26, 2016 at 11:36 PM, Tomas Strachota <tstrach...@redhat.com <mailto:tstrach...@redhat.com>> wrote: On 08/26/2016 07:58 AM, Joseph Magen wrote:

[foreman-dev] Re: RFC for foreman_api_v3

On 08/26/2016 07:58 AM, Joseph Magen wrote: Hi all, I created a RFC for a plugin called foreman_api_v3 and the initial repo at github.com/isratrade/foreman_api_v3 . If the

Re: [foreman-dev] RFC for foreman_api_v3

On 08/26/2016 10:39 AM, Daniel Lobato Garcia wrote: On 08/26, Joseph Magen wrote: Hi all, I created a RFC for a plugin called foreman_api_v3 and the initial repo at github.com/isratrade/foreman_api_v3. If the community

Re: [foreman-dev] Webpack merged into develop branch

On 08/10/2016 02:01 PM, Tomer Brisker wrote: Hello, I am happy to inform you that Webpack has finally been added to Foreman. This step which will help us modernize our front-end code, take advantage of the blooming javascript eco-system, and easily integrate technologies such as ES2015, React,

Re: [foreman-dev] Possible to move redmine Katello project under Foreman?

On 08/03/2016 06:30 PM, Tom McKay wrote: On Wed, Aug 3, 2016 at 10:26 AM, Lukas Zapletal > wrote: > Is there a case for keeping katello separate any longer, or can we combine? Because it's a plugin? And plugins have its own release cadence,

Re: [foreman-dev] Hammer CLI Options for ID Resolution

On 07/22/2016 09:01 PM, Andrew Kofink wrote: Hi Team (especially Martin and Tomas), I've been banging my head on the table for a few days now, so I thought I would just ask: I want to resolve a content view by its name; currently, content_views#index has no required parameters, so no automatic

Re: [foreman-dev] 1.12 branched

On 05/31/2016 05:02 PM, Dominic Cleal wrote: On 31/05/16 15:03, Dominic Cleal wrote: In preparation for the first 1.12 release candidate, I've branched the develop branch on these repos to 1.12-stable: foreman, smart-proxy, foreman-installer, foreman-selinux, community-templates,