[foreman-dev] Code owners attempt 2

Hello all, A while ago I proposed code owners for the packaging files. We tried this[1] but didn't work in our setup. It turns out that those mentioned as owners need permissions on the repository. In our case the packaging team (not individual members) has no permission. There are 3

Re: [foreman-dev] Releases for EOL Fedora, why ?

On Sun, Dec 17, 2017 at 02:11:25AM -0800, Matt wrote: Why are the latest Fedora versions so poorly supported and EOL ones are ? Lack of time to properly package and test it. Is the primairy reason. Another thing that was always difficult for the main foreman package was keeping rails

[foreman-dev] Forklift boxes are moving

Hello all, tl;dr: forklift boxes are now in boxes.d/*.yaml and you manage boxes.d/99-local.yaml instead of boxes.yaml. Migration should happen automatically but do rebase your open PRs. Longer explanation: https://github.com/theforeman/forklift/pull/393 was merged. This change unifies all

Re: [foreman-dev] Request for Koji access

On Wed, Dec 13, 2017 at 10:30:53AM +0100, Ondrej Prazak wrote: as we are getting closer to 1.17 branching, I would like to ask for access to Koji, because I will need to update build targets and configuration. +1 -- You received this message because you are subscribed to the Google Groups

Re: [foreman-dev] The package.json thing in git

On Thu, Dec 14, 2017 at 04:18:45PM +0100, Lukas Zapletal wrote: for some reason, npm upgrade is touching my package.json on every run. This file is in git, so it is annoying to have that edited every run. Can we do something with this? I think you're supposed to use npm install. npm upgrade is

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

On Thu, Dec 07, 2017 at 01:02:00PM +0100, Ondrej Prazak wrote: OAuth fix for Rails 5 [3] did not receive much attention from OAuth maintainers. We plan to package a forked version with included fix until new gem version compatible with Rails 5 is released. [3]

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

On Thu, Dec 07, 2017 at 09:52:21AM -0500, Eric D Helms wrote: Thanks for the weekly updates! I'll echo that. Greatly appreciated. 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

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 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] Nominating additional maintainers in foreman-core

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 Michael Moll - has 71 merged commits [3] and has taken part in the reviews of 130 merged commits[4]. He is also already a

Re: [foreman-dev] Firefox 57 and noVNC

On Tue, Dec 05, 2017 at 09:43:20AM +0100, Lukas Zapletal wrote: I was trying noVNC the other day on FF 57. Imported katello CA (it was a katello intance), but it didn't work until I flipped flag "network.websocket.allowInsecureFromHTTPS" on and then it worked. I remember that Firefox always

Re: [foreman-dev] Kanban tools and redmine

On Thu, Nov 30, 2017 at 10:27:40AM +0100, Marek Hulán wrote: Dne středa 29. listopadu 2017 9:05:28 CET, Lukas Zapletal napsal(a): Can you elaborate on why something does not make sense to track in RedMine? I am not following, RedMine is a generic ticketing system and you can create as many

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

On Thu, Nov 30, 2017 at 09:57:24AM +0100, Marek Hulán wrote: Dne středa 29. listopadu 2017 14:36:18 CET, Ewoud Kohl van Wijngaarden napsal(a): On Wed, Nov 29, 2017 at 02:18:35PM +0100, Lukas Zapletal wrote: >> Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in >&

Re: [foreman-dev] Unique IDs and UI testing automation

On Wed, Nov 29, 2017 at 01:08:13PM -0500, Walden Raines wrote: In order to assist in UI automation, I would like to propose that we add unique IDs to the following elements: - Tables and table rows (s) - All inputs, including those not technically in a form (row select checkboxes, for

Re: [foreman-dev] 1.16.0 release builds started

plugins plan for release work. On Wed, Nov 29, 2017 at 8:16 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: A quick heads up: 1.16.0 final was tagged and we started the builds. Especially the ARM builds a take a while. -- You received this message because you are subs

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

On Wed, Nov 29, 2017 at 02:18:35PM +0100, Lukas Zapletal wrote: Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in the near future, but *please* lets use it to deprecate / drop stuff we no longer want to maintain. Otherwise there's no real point to it. I agree we can take

[foreman-dev] 1.16.0 release builds started

A quick heads up: 1.16.0 final was tagged and we started the builds. Especially the ARM builds a take a while. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

Anything that's on the mailing list with [plugin author action required] is likely breaking the API. Recently we had the mass change from FactoryGirl to FactoryBot (which is causing a lot of pain while cherry picking to older releases as well). That had to be coordinated to sync it up with

Re: [foreman-dev] Proposal: Foreman 1.18 = 2.0

On Wed, Nov 29, 2017 at 10:39:42AM +0100, Lukas Zapletal wrote: What have Linus Torvalds and me in common? We both don't remember numbers higher than ten. I propose to follow Linux kernel versioning and do 2.0 instead of 1.18 for no other reason that it's just too high number and it's

Re: [foreman-dev] Community-developed Ansible modules for Foreman API objects

I had a look at this at some point but what I really dislike about Hammer as an API is that the JSON output is also capitalized and inconsistent. Ended up with large mappings and quickly gave up. Maybe I missed something and it can be done easily. On Wed, Nov 29, 2017 at 09:35:46AM +,

Re: Re: [foreman-dev] Kanban tools and redmine

On Wed, Nov 29, 2017 at 09:45:49AM +0100, Daniel Lobato Garcia wrote: On 11/28, Ewoud Kohl van Wijngaarden wrote: On Tue, Nov 28, 2017 at 04:29:01PM -0500, Walden Raines wrote: > I really like the idea of a trello/kanboard like tool but I hate having to > update tasks in multiple

Re: [foreman-dev] Kanban tools and redmine

On Tue, Nov 28, 2017 at 04:29:01PM -0500, Walden Raines wrote: I really like the idea of a trello/kanboard like tool but I hate having to update tasks in multiple places. Another idea I had was to switch (back) to using GH issues and use GH projects [2] as well. Just going to jump on the GH

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

On Thu, Nov 23, 2017 at 02:03:11PM +0100, Ondrej Prazak wrote: this is just a quick summary of where we stand with 1.17, please feel free to correct me if I got something wrong. #21546 is also blocking proxy registration on Debs. That's already on Rails 5 but EL7 is getting closer to

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

On Mon, Nov 20, 2017 at 05:36:29PM +, Ivan Necas wrote: po 20. 11. 2017 v 13:36 odesílatel Daniel Lobato Garcia <elobat...@gmail.com> napsal: On 11/20, Ohad Levy wrote: > On Sun, Nov 19, 2017 at 10:35 PM, Ewoud Kohl van Wijngaarden < > ew...@kohlvanwijngaarden.nl> wrote:

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

On Tue, Nov 21, 2017 at 11:10:41AM +0200, Ohad Levy wrote: 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

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

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 anyone shed some light on ETA for 1.16 GA? I should have given an update earlier. So far we've been wanting to include the foreman tasks as a service

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

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 earlier. So far we've been wanting to include the foreman tasks as a service from core rather than from foreman-tasks. As always we want that change to

Re: [foreman-dev] Regular Foreman-core issue triage?

+1 the open issues need to be reviewed. I don't know if this is the best solution but can't hurt to get more eyes on them. What I don't see is something to go over old issues that have been triaged at some point. I did that a while back for the installer and could close a few issues that had

Re: [foreman-dev] Koji repo sync metadata problem

sion, chances are that SELinux won't load on older releases. So basically we must be ready to do minimum requirements change here. Thanks for solving the problem. LZ On Wed, Nov 15, 2017 at 10:05 PM, Ewoud Kohl van Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: I think we should sync & update

Re: [foreman-dev] Koji repo sync metadata problem

have, this path DOES have repodata: /mnt/koji/external-repos/www/epel7-x86_64/RPMS.epel/repodata > > LZ > > > > On Wed, Nov 15, 2017 at 6:15 PM, Ewoud Kohl van Wijngaarden > > <ew...@kohlvanwijngaarden.nl> wrote: > > > I still get errors when building: > >

Re: [foreman-dev] Koji repo sync metadata problem

I still get errors when building: http://koji.katello.org/koji/taskinfo?taskID=52363 http://koji.katello.org/kojifiles/work/tasks/2363/52363/root.log DEBUG util.py:439: Error downloading packages: DEBUG util.py:439:1:nodejs-6.10.3-1.el7.x86_64: failed to retrieve

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

On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote: To make this a more "official" policy, I've created a "Foreman" account on Rubygems, and the user can be added to any gem we keep on our namespace. This should minimize any issues when transferring

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

On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote: A few months ago we added a policy that required 2 gem authors per plugin. We did, however struggle to actually get two authors on some plugins. To make this a more "official" policy, I've created a "Foreman" account on Rubygems,

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

On Thu, Nov 09, 2017 at 02:37:10PM +, Greg Sutcliffe wrote: On 09/11/17 14:25, Ewoud Kohl van Wijngaarden wrote: If a separate repository, would it not be as simple as adding a git clone? Possibly, I don't have that much insight into the entire deployment flow. Hence my preference

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

On Thu, Nov 09, 2017 at 09:04:55AM -0500, Eric D Helms wrote: On Thu, Nov 9, 2017 at 9:00 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: On Wed, Nov 08, 2017 at 07:35:04AM -0500, Eric D Helms wrote: All, I brought this idea up in a separate thread, bu

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

On Wed, Nov 08, 2017 at 07:35:04AM -0500, 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-infra repository. I believe this makes them

[foreman-dev] Status of the nightlies

Hello all, tl;dr: nightlies are fixed, we're staying on top of them. report issues As you might have picked up, the nightlies were a bit unstable and unreliable lately. The biggest problem was that core and packaging drifted apart. For now this has been synced up. Now the challenge is to

Re: [foreman-dev] Re: Moving katello-packaging to foreman-packaging

On Wed, Nov 08, 2017 at 11:49:55AM -0500, Eric D Helms wrote: The work for this transition has completed. All packages have been moved at this point, and katello-packaging fully deprecated. The packaging PR testing on foreman-packaging has been updated to account for these new packages as well

Re: [foreman-dev] Abandoned plugins under theforeman github org

+1 on just marking it in README and in the github description. On Wed, Nov 08, 2017 at 12:07:43PM +0100, Ivan Necas wrote: +1 of marking as unmaintained, but keeping around -- Ivan On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote: ... i would not remove it from the

Re: [foreman-dev] Building a Rails 5.1 SCL

+1 for 2.4. I believe currently it's beta in SCLo but I assume that it'll be GA by the time we finish it and the RH-SCL version is already GA. On Tue, Nov 07, 2017 at 11:59:43AM -0500, Eric D Helms wrote: One thing I didn't include as part of this discussion was a discussion of the version of

Re: [foreman-dev] Re: Foreman instrumenting analysis

Have you had a look at influxdb? While I have limited experience with it, it's push based which can have benefits. There's infludb-rails[1] which states: Out of the box, you'll automatically get reporting of your controller, view, and db runtimes for each request. That sounds a lot like

Re: [foreman-dev] speeding up tests

On Tue, Nov 07, 2017 at 08:34:45AM -0500, Eric D Helms wrote: So many items to unpack here that I am going to attempt to break my response into categorizations. If I miss a key point, please point it out so I can follow up addressing it. There's a lot of good thoughts in your mail. I'm just

Re: [foreman-dev] Re: Moving katello-packaging to foreman-packaging

+1 On Mon, Nov 06, 2017 at 08:20:26AM -0500, Eric D Helms wrote: An important part I missed with the migration and initial proposal is around maintainers. I am proposing that all katello-packagers be given commit access to foreman-packaging as part of this move. All developers in this group

Re: [foreman-dev] Propsing a move from Google Groups to Discourse

My views do align with Martin here: email does feel like a second class citizen. Sending email does work properly (likely because they could just use the github parser gem) but what it sends out is ... barely enough. On the other hand (and this has been pointed out by other people), it might

Re: [foreman-dev] Moving katello puppet modules to the foreman github namespace

on theforeman organization. On Thu, Nov 2, 2017 at 12:38 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: Hello all, Previously this has been discussed in various threads but now we're ready to make it a reality. All modules should be ready to use a single modulesync repo

[foreman-dev] Moving katello puppet modules to the foreman github namespace

Hello all, Previously this has been discussed in various threads but now we're ready to make it a reality. All modules should be ready to use a single modulesync repository and a pull request has been opened. https://github.com/theforeman/foreman-installer-modulesync/pull/78 lists all tasks

Re: [foreman-dev] Building a Rails 5.1 SCL

On Thu, Nov 02, 2017 at 11:24:26AM +0100, Daniel Lobato Garcia wrote: Just one question, my understanding is that you prefer to do this (SCL) because we are uncertain of the time/effort required for vendoring the gems/npm packages. Given that long-term we would have to keep up building SCLs

Re: [foreman-dev] Merge permission for theforemen/foreman-ansible-modules

+1 while I haven't looked at his ansible work that closely I have seen that he's already behaving like an excellent maintainer: good reviews, active and generally a good and friendly person to have around. On Mon, Oct 30, 2017 at 11:46:34AM -0400, Andrew Kofink wrote: +1 from me! We have

Re: [foreman-dev] Koji Outage

Turns out it was started in a new security group which didn't allow rsync. lzap fixed that now. On Sat, Oct 28, 2017 at 08:09:39PM +0200, Ewoud Kohl van Wijngaarden wrote: It looks like the rsync service isn't started causing our promotion pipeline to fail. Could you have a look? On Thu, Oct

Re: [foreman-dev] Vendorizing or Building RPMs

On Mon, Oct 23, 2017 at 09:52:39AM +0100, Greg Sutcliffe wrote: On Mon, 2017-10-16 at 14:36 +0100, Greg Sutcliffe wrote: That said, I've not really been involved with the RPMs, so I'm unsure if this causes a bigger headache for Yum users than Apt users. I'm also unsure of the work required to

Re: [foreman-dev] Merge rights to Katello installer

On Thu, Oct 26, 2017 at 10:39:28AM +0100, Sean O'Keeffe wrote: I'd like to request write access to the installer team. +1 Sean has shown insight in the modules and the overall picture. His PRs are consistently of a high quality. I've been involved with 38 PRs across what I'd consider to be

[foreman-dev] Issue with foreman tests

Hello all, On Friday a PR was merged[1] that was intended to verify seeding worked. It turns out that you can't run rake db:migrate db:seed in one command which resulted in failing tests. An issue has been created[2] and a workaround implemented[3]. Please rerun tests that failed on NOT

Re: [foreman-dev] 1.16 RC2 preparation

13:55 GMT+02:00 Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl>: On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote: While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation. From the installer side I can handle it, but will need help from

Re: [foreman-dev] 1.16 RC2 preparation

On Thu, Oct 12, 2017 at 05:42:19PM +0200, Ewoud Kohl van Wijngaarden wrote: While Daniel is on PTO I'd like to take over the 1.16 RC2 preparation. From the installer side I can handle it, but will need help from a core maintainer and a proxy maintainer to tag releases. We did prepare

Re: [foreman-dev] Centralizing tool_belt in theforeman Github

On Fri, Oct 20, 2017 at 04:59:33PM -0400, Eric D Helms wrote: For quite a few releases now, we've been using a little tool named tool_belt as a CLI to perform release tasks such as finding cherry picks, or building koji configurations. The larger idea of the repository is you define a release

Re: [foreman-dev] Current State of Nightlies

And https://github.com/theforeman/foreman-packaging/pull/1869 should fix the other issue. On Wed, Oct 18, 2017 at 02:24:19PM +0200, Ewoud Kohl van Wijngaarden wrote: Agreed. https://github.com/theforeman/foreman-packaging/pull/1866 On Tue, Oct 17, 2017 at 09:16:52AM +0200, Lukas Zapletal

Re: [foreman-dev] Current State of Nightlies

the right open source path, I'd weigh: 1) how long will nighties be broken waiting on a new package? 2) 2.0 to 4.1 is a large jump and as a base dependency other EPEL packages may not work. On Mon, Oct 16, 2017 at 9:31 PM, Ewoud Kohl van Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote:

Re: [foreman-dev] Sharing and idea: VMWare VIX instead of DHCP for vCenter VM's provisioning

On Mon, Oct 16, 2017 at 11:39:56AM -0700, Evgeny Vasilchenko wrote: I'd like to share an idea for provisioning of VMware guest VM's with Foreman. The idea required programming new type of Foreman proxy - unfortunately, I neither have time or enough skills for that. *The goal:* - Allow

Re: [foreman-dev] Current State of Nightlies

On Mon, Oct 16, 2017 at 04:18:53PM -0400, Eric D Helms wrote: Nightly RPM and tests have been broken for around 2 weeks now. This morning a bit of a regression was merged to foreman core to fix the breaking RPM aspect and I can report that nightly RPMs are now building. However, this leads to a

Re: [foreman-dev] Found In Version Katello Redmine custom field

https://projects.theforeman.org/projects/foreman/issues/new has this, but I'm not sure we can rename the Release field since it's part of the Redmine Backlogs plugin though my memory is fuzzy here. I think someone with admin rights on Redmine can say more about the practicalities but the idea

[foreman-dev] Redmine available over HTTPS

Hello all, Long overdue, but we now have https://projects.theforeman.org available. For now we have no redirects or change defaults. Please start testing it while we look for places that need to update to new URLs. If you have any scripts, please change them too. If you have any issues,

Re: [foreman-dev] Availablity of yum.theforeman.org

On Fri, Oct 13, 2017 at 05:35:45AM -0700, Dirk Götz wrote: http://yum.theforeman.org/ is showing the Debian apache default package and a colleague and I having both problems with timeouts and package availablitiy during installation in two different environments. Is there some work going on or

Re: [foreman-dev] Redmine running slowly

On Thu, Oct 12, 2017 at 11:50:55AM +0100, Greg Sutcliffe wrote: And we're back. Please test extensively and report issues ;) In particular, we're now on Ruby 2.0 (up from 1.9 on Openshift) so I suspect the plugins might have issues. Any issues, please report them here and we'll take a look. I

[foreman-dev] Jenkins over HTTPS

Hello all, We now have https://ci.theforeman.org/ but there's no redirect yet. I'd like to ask you to start testing - especially if you log in. The next step is to replace all URLs we have to HTTPS and set up a redirect. -- You received this message because you are subscribed to the Google

Re: [foreman-dev] Redmine running slowly

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: http://51.15.192.166 is now live for your testing pleasure, with a copy Any chance to update/enable https in the process? That is the

Re: [foreman-dev] Redmine running slowly

We deployed a new version but that took longer than expected. Now we use bare git clones rather than doing full checkouts. This should save a lot of IO which is generally a limiting factor. Hopefully this helps enough until we can migrate to the new platform.

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

On Tue, Oct 10, 2017 at 01:21:36PM +0200, Tomas Strachota wrote: 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

Re: [foreman-dev] Katello UX nitpick - Sync Status

Given 3.4 has been released I think that renaming a menu item is not in order. Patch releases should fix bugs, not introduce enhancements. On Mon, Oct 09, 2017 at 05:13:58PM +0200, Lukas Zapletal wrote: While I have no issues with redesigning things for better UX, I was hoping for some

Re: Re: [foreman-dev] unscheduled 1.15.5

It looks like #19986 was fixed in puppetserver 2.8.0 and GH-249 was merged so from the installers side I think we're good to go. On Wed, Oct 04, 2017 at 05:34:51PM +0200, Ewoud Kohl van Wijngaarden wrote: These are now released and the PR[1] is open to bump the versions. Note that I want

Re: [foreman-dev] request for write-access to katello-packaging

Was this ever implemented? On Fri, Sep 22, 2017 at 08:40:20PM -0400, Eric D Helms wrote: +1 from me as well On Fri, Sep 22, 2017 at 3:57 AM, Lukas Zapletal wrote: +1 thanks for all the help there. On Thu, Sep 21, 2017 at 6:47 PM, John Mitsch wrote: >

Re: Re: [foreman-dev] unscheduled 1.15.5

at 12:38:55PM +0200, Ewoud Kohl van Wijngaarden wrote: That's only part of it. These are still open: Fix issues on EL7.4: * https://github.com/theforeman/puppet-foreman_proxy/pull/376 * https://github.com/theforeman/puppet-foreman_proxy/pull/377 Fix OpenSCAP on Puppet 4 systems: * https

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

On Wed, Oct 04, 2017 at 10:18:12AM +0100, Greg Sutcliffe wrote: On Mon, 2017-09-25 at 14:01 +0200, Ewoud Kohl van Wijngaarden 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. That's over

Re: Re: [foreman-dev] unscheduled 1.15.5

That's only part of it. These are still open: Fix issues on EL7.4: * https://github.com/theforeman/puppet-foreman_proxy/pull/376 * https://github.com/theforeman/puppet-foreman_proxy/pull/377 Fix OpenSCAP on Puppet 4 systems: * https://github.com/theforeman/puppet-puppet/pull/554 Once those are

Re: [foreman-dev] Release process & permissions

proach would help avoid overly broad permissions too. -d On Thu, Sep 28, 2017 at 3:23 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: To release a gem to rubygems I'd recommend looking at how voxpupuli implemented this using Travis[1]. The same can be done for puppe

Re: [foreman-dev] Release process & permissions

maintainers who are capable of doing most of the leg-work. The role of the release nanny then becomes coordinating the effort, making public announcements and such. Such an approach would help avoid overly broad permissions too. -d On Thu, Sep 28, 2017 at 3:23 AM, Ewoud Kohl van Wijngaarden <

Re: [foreman-dev] Release process & permissions

To release a gem to rubygems I'd recommend looking at how voxpupuli implemented this using Travis[1]. The same can be done for puppet[2]. That means you can push a tag to git and the release is there. There are also tools that help you bump. For puppet there is puppet-blacksmith[3]. How to do

Re: [foreman-dev] Release process & permissions

While I agree we should automate a lot, I agree with Eric. Doing a Foreman release should involve a human to keep the end-to-end quality. Just giving permissions is wrong. For example in Foreman 1.15.5 the installer was tagged and released before I could push in my changes. That communication

Re: [foreman-dev] Requesting discovery test for core PRs

On Wed, Sep 27, 2017 at 01:34:08PM +0200, Lukas Zapletal wrote: what you think about adding discovery to core PRs test suite, just one Ruby version on sqlite3? +1 Recently we had all red situation when we bumped to Rails 5. After Ivan fixed that, we have the same due to fact import

[foreman-dev] Access to foreman-infra

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. Regards, Ewoud Kohl van Wijngaarden -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To u

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

On Fri, Sep 22, 2017 at 04:19:43PM -0400, Eric D Helms wrote: Howdy, There have been recent conversations that have popped up on PRs, for example [1], and IRC conversations around whether or not our RPM packages should be performing database actions and restarting services. This thread is

Re: [foreman-dev] Removing old Jenkins jobs

It appears I don't have permission to delete these jobs. On Thu, Sep 21, 2017 at 08:39:15AM -0400, Eric D Helms wrote: +1 On Thu, Sep 21, 2017 at 8:22 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: Hello all, We have many old jobs in Jenkins that are no longer re

[foreman-dev] Removing old Jenkins jobs

Hello all, We have many old jobs in Jenkins that are no longer relevant. To make a start I'm proposing to the delete 'installer lint and *' jobs. You can see them at http://ci.theforeman.org/view/Installer/ As you can see they haven't been used for 3 years and it all happens on Travis these

Re: [foreman-dev] Building an Infra/Deployment/Platform Roadmap

On Mon, Sep 18, 2017 at 11:21:04AM -0400, Eric D Helms wrote: Howdy All, We've recently had some discussions about infra changes, past discussions about deployment projects and additions (e.g. containers) and platform changes (e.g. Rails 5.X support). For me, these all live in a similar area of

Re: [foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

On Wed, Sep 13, 2017 at 12:05:49PM -0700, ssht...@redhat.com wrote: First attempt to create a design. It's an open discussion, everyone who wants to chime in, please do. The engine: will be deployed as a separate gem. My name suggestion the-detective

Re: [foreman-dev] From Foreman to Iot Platforme

, Ewoud Kohl van Wijngaarden a écrit : On Wed, Sep 13, 2017 at 02:25:01AM -0700, Fairouz el ouazi wrote: > I m trying to develop a plugin in Foreman so i can manage all the >devices that are connected to my IoT platform . I can communicate with my >IoT platform via REST API . In fi

Re: [foreman-dev] From Foreman to Iot Platforme

On Wed, Sep 13, 2017 at 02:25:01AM -0700, Fairouz el ouazi wrote: I m trying to develop a plugin in Foreman so i can manage all the devices that are connected to my IoT platform . I can communicate with my IoT platform via REST API . In first place with GET request i can get all the

Re: [foreman-dev] Problems with Katello Bastion UI when changing Foreman base URL

On Tue, Sep 12, 2017 at 8:18 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: Hello Gerrit, You're right that a lot assumes a static location. Katello has much more assumptions in this area than vanilla Foreman and while there is an effort to at least be able to split se

Re: [foreman-dev] Problems with Katello Bastion UI when changing Foreman base URL

be very grateful if you share them with me. Many thanks and regards, --Gerrit On Tuesday, September 12, 2017 at 12:29:05 PM UTC+2, Ewoud Kohl van Wijngaarden wrote: On Tue, Sep 12, 2017 at 02:56:06AM -0700, gerrit.sc...@avid.com wrote: >I am having a setup where I use Foreman as a compl

Re: [foreman-dev] Permissions cleanup

On Mon, Sep 11, 2017 at 12:41:02PM +0100, Greg Sutcliffe wrote: 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 never really

Re: [foreman-dev] Problems with Katello Bastion UI when changing Foreman base URL

On Tue, Sep 12, 2017 at 02:56:06AM -0700, gerrit.schwerth...@avid.com wrote: I am having a setup where I use Foreman as a complete backend service. Another service works on the document root of the HTTPD server. In order to have all pages of Foreman still reachable, I tried altering the base URL

Re: [foreman-dev] What is the process to get new resources added to transifex?

+1 to adding Bryan. We don't have a process in place and Bryan obviously cares. On Mon, Sep 11, 2017 at 10:36:27AM +0200, Marek Hulán wrote: I think we don't have to follow the full-blown nomination process here, any concerns regarding giving Bryan admin access? Please let me know here or

Re: [foreman-dev] [infra] Packaging reorganization

On Mon, Sep 04, 2017 at 02:13:27PM -0400, Justin Sherrill wrote: On 09/02/2017 03:00 PM, Eric D Helms wrote: On Sep 2, 2017 10:22 AM, "Timo Goebel" > wrote: I am wondering if we should name the katello-client repository either

Re: [foreman-dev] [Infra] Proposal to Move Jenkins Job Configurations

On Sat, Sep 02, 2017 at 08:02:32AM -0400, Eric D Helms wrote: On Sep 2, 2017 6:27 AM, "Ewoud Kohl van Wijngaarden" < ew...@kohlvanwijngaarden.nl> wrote: On Fri, Sep 01, 2017 at 07:27:23PM -0400, Eric D Helms wrote: Howdy, Some quick background, for those that don't know a

Re: [foreman-dev] [Infra] Proposal to Move Jenkins Job Configurations

On Fri, Sep 01, 2017 at 07:27:23PM -0400, Eric D Helms wrote: Howdy, Some quick background, for those that don't know a majority of our Jenkins job configuration are stored in git. I find our Jenkins job configuration to be important for developers to be able to understand and contribute

Re: [foreman-dev] [infra] Packaging reorganization

On Fri, Sep 01, 2017 at 07:48:19PM -0400, Eric D Helms wrote: As a lead-in to being working towards migrating Katello's packages to the foreman-packaging repository, I'd like to propose a slight re-organization of the repository. As well, to seek any other ideas or problems any might see with

Re: [foreman-dev] [Infra] Jenkins Job Naming Conventions

Joining in on the party: +1 for #2 On Fri, Sep 01, 2017 at 09:29:17AM -0400, John Mitsch wrote: Another vote for #2 as you can scan quickly and group by project. John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Fri, Sep 1, 2017 at 8:56 AM, Justin Sherrill

Re: [foreman-dev] Katello pulp_export_destination checks happen inside the application

On Mon, Aug 21, 2017 at 08:06:01AM +0200, Timo Goebel wrote: Am 20.08.17 um 22:39 schrieb Ewoud Kohl van Wijngaarden: I think if Pulp took a parameter to publish to a non-default location, we would not need to do the extra copy step that ties Katello and Pulp closely together. Currently

Re: [foreman-dev] Katello pulp_export_destination checks happen inside the application

On Sun, Aug 20, 2017 at 04:11:13PM -0400, Christopher Duryee wrote: On Sun, Aug 20, 2017 at 4:02 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: Hello all, While working on splitting the Katello installation from its services I ran into the pulp_export_destination s

[foreman-dev] Katello pulp_export_destination checks happen inside the application

Hello all, While working on splitting the Katello installation from its services I ran into the pulp_export_destination setting. That made me look at the Repository Export[1] which assumes the pulp server and application server share the same filesystem. That means I'm stuck in attempting

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

On Sun, Aug 20, 2017 at 09:56:40AM -0700, Dmitri Dolguikh wrote: On Sun, Aug 20, 2017 at 6:49 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: On Fri, Aug 18, 2017 at 12:48:06PM +0100, Greg Sutcliffe wrote: Ewoud Kohl van Wijngaarden: - smart_proxy_dns_powerdns L

  1   2   >