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

> 2. do you know that there is a global env already? just run: > > NOTIFICATIONS_POLLING=100 foreman start I hereby withdraw my proposal, this works for me. Quite hidden one :) -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups

[foreman-dev] Review of all our logrotate configuration

Hey, I spent some time reviewing logrotate scripts because we had some reports on logrotation when SELinux was preventing it. TL;DR - resolved the issue, filed temporary fix for our policy and RHEL BZ. Comments below: /var/log/foreman/*.log Works ok, copy and truncate.

[foreman-dev] Pull request github template proposal

I created the following proposal: https://github.com/theforeman/foreman/pull/5099/files I tried to keep it short and simple. Please comment. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from

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

The PR is finally up for review. https://github.com/theforeman/foreman/pull/5096 I recorded short demo how to set it up with Prometheus via statsd: https://youtu.be/i5iCOLEByZk On Mon, Nov 20, 2017 at 3:46 PM, Lukas Zapletal <l...@redhat.com> wrote: > Hey, > > on the last demo

Re: [foreman-dev] DHCP filename option no longer honored

u? > > Timo > > Am 14.12.17 um 14:21 schrieb Lukas Zapletal: >> >> Hey, >> >> I noticed that DHCP filename option is no longer honored in >> develop/1.17 branch anymore. This is regression from 1.15/1.16 series, >> filed a blocker bug for 1.17: >>

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

blog.openshift.com/tag/prometheus/ >> >> >> >> On Fri, Nov 24, 2017 at 12:54 PM, Lukas Zapletal <l...@redhat.com> wrote: >>> >>> > 1. what happened to the PCP approach we talked about in the past? >>> >>> Thats going in pa

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

in git, therefore update needs to be executed often. I guess it does not apply to npm. Confusing. On Thu, Dec 14, 2017 at 4:24 PM, Ewoud Kohl van Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: > On Thu, Dec 14, 2017 at 04:18:45PM +0100, Lukas Zapletal wrote: >> >> for some r

[foreman-dev] DHCP filename option no longer honored

Hey, I noticed that DHCP filename option is no longer honored in develop/1.17 branch anymore. This is regression from 1.15/1.16 series, filed a blocker bug for 1.17: http://projects.theforeman.org/issues/21975 This breaks UEFI provisioning. I git-bisected commit

Re: [foreman-dev] CDN for the theforeman.org

gt;> can't really compare that. >>> And cdn-fastly.deb.debian.org (which is the "real" Fastly host apt >>> hits) does not have SSL enabled at all. >>> >>> On Mon, Nov 20, 2017 at 11:58 AM, Greg Sutcliffe >>> <g...@emeraldreverie.org> wrote:

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

+1 +1 beer time! LZ On Wed, Dec 6, 2017 at 1:40 PM, 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

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

The idea behind turbolinks is good in general - it works great when you have a standard Rails application with its view stack (ERB). When I saw this talked, I liked it very much: https://www.youtube.com/watch?v=SWEts0rlezA Unfortunately, we are not good fit. This works for a clean app which ERB

Re: [foreman-dev] RFC: File audit for template rendering

I think, this can and should be done with a database. I agree, that the > audit model might not be the best place for this. But a database definitely > is. > > Just my 2 cents. > > - Timo > > Am 05.12.17 um 18:01 schrieb Lukas Zapletal: > >> Hello, >> >

[foreman-dev] RFC: File audit for template rendering

Hello, Foreman does have a nice audit trail for many operations, what's missing is ability to find how a template (e.g. kickstart) was rendered. Storing whole template text in audit table is probably not the best thing to do, production.log is also not a good fit, so here is a proposal. I want

[foreman-dev] Speed up Foreman development booting by 50%

I just filed this PR which speeds booting up quite a lot, from 10s to 6s on my system: https://github.com/theforeman/foreman/pull/5045 Feel free to test, I haven't tested with Katello but it should give even bigger boost with it. -- Later, Lukas @lzap Zapletal -- You received this message

Re: [foreman-dev] Firefox 57 and noVNC

: /etc/foreman/proxy_ca.pem :ssl_priv_key: /etc/foreman/client_key.pem On Tue, Dec 5, 2017 at 12:06 PM, Ewoud Kohl van Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: > On Tue, Dec 05, 2017 at 09:43:20AM +0100, Lukas Zapletal wrote: >> >> I was trying noVNC the other day on FF

Re: [foreman-dev] Koji Space on /

My 2C: 1) We need to setup foreman-infra mailing list, we had one set by Dominic but I am not sure we still have access to this. Greg, can you set up something for us and add our infra team? Whatever this is, but personally I'd prefer emails :) I had an email about this on Saturday but I haven't

[foreman-dev] Firefox 57 and noVNC

Hello, 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 worked out of box - when server CA was imported, it worked

Re: [foreman-dev] Request to Releasers: Please pull in translations and merge strings

Thanks for reminder, I am so bad in this. To github.com:theforeman/foreman_discovery.git d44e91f..40f44dc develop -> develop LZ On Sat, Dec 2, 2017 at 5:54 PM, Bryan Kearney wrote: > This is a request for folks who release plugins, either foreman or hammer. > > As

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

Just to be sure it does not get lost: > All inputs, including those not technically in a form (row select > checkboxes, for example) > All buttons All buttons (which are links) already has data-id which is always present and when not, it is auto-generated from HREF attribute. This was added by

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

This code was actually created by me to server the very same purpose - QAs asked for this. They wanted to have all buttons (links) to have an ID and now they have it. https://github.com/theforeman/foreman/commit/bfee97b6a6980b6ad4f5bd65f4b60680f08967f5 This is the request:

[foreman-dev] Re: Proposal: Foreman 1.XX = 2.0 (a new one)

Ok, gmail did not refresh me the thread, I was reading old posts. > D) I want to stick with 1.X, talk about feature-driven release > management or simply decide later It looks like majority want to continue the discussion, please carry on there. There are some voices that vertical nav with

[foreman-dev] Re: Proposal: Foreman 1.XX = 2.0 (a new one)

I think there is misunderstanding and the thread deviated to 2.0 feature discussion. This is not core of my proposal, I explicitly do not want to do feature talk. There will always be something that we would like to have in version X.Y. What I propose is: A) Let's do 2.0 instead 1.17 regardless

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

> 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 this "opportunity" to drop some deprecated things like V1 API,

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

wrote: > On 29/11/17 10:45, Lukas Zapletal wrote: >> Oh no, *everyone* is talking features. :-) This has really nothing to >> do with features, because that can easily fall into "neverending" >> category of what's big enough change or not. > > Well,

Re: [foreman-dev] [RFC] Deprecate and move Github RFC repo content

case of knowing the purpose of your > communication channels and picking *one* way to handle it that suits the > purpose. Having >1 just fragments everything (I learned that the hard > way with the RFC repo, sadly). At the very least, I'd ask that we finish > sorting out Discourse bef

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

Oh no, *everyone* is talking features. :-) This has really nothing to do with features, because that can easily fall into "neverending" category of what's big enough change or not. We've heard that 1.17 is possible, yeah I do agree but only if that's confirmed by the release engineer, not sure if

[foreman-dev] Proposal: Foreman 1.18 = 2.0

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 approaching crazy 20. "One point eighteen" sounds crazy, I always mess up

[foreman-dev] Missing github issues features (no migration)

Sup! When we introduced RedMine, Github issues were very limited. Calm down, this is just a review of what's missing from Github issues, I am not planning to propose or do anything :-) Let me do quick review of missing features as of today (fall 2017) and possible mapping to issues: REDMINE -

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

> Projects in GitHub are also per-team, Those Projects look great, but it's a good fit only when you use Issues as well. Having RedMine + GH Projects is not much added value I think. Ivan: Those votes I proposed would only choose if to put a plugin to prod instance or not of course. You would

Re: Re: [foreman-dev] [RFC] Deprecate and move Github RFC repo content

Yeah, I also think this would make sense. It's basically a wiki with discussion - ideal. Greg, can you turn it on in RFC repo so we can test this? If this fails, we can move to wiki and deprecate that repo. -- LZ Lukas @lzap Zapletal -- You received this message because you are subscribed

Re: [foreman-dev] Kanban tools and redmine

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 tickets as you want, e.g. Buy milk. It will work. This is a dogma I do not take as an argument. What's relevant is if you need to create

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

> 1. what happened to the PCP approach we talked about in the past? Thats going in parallel, PCP is just a monitoring framework you can integrate with instrumentation data just like any other. > 2. how would you integrate this to sosreport/foreman-debug? I'm thinking of > storing the statsd data

Re: [foreman-dev] Discourse - next steps / actions

Although I prefer to only migrate users list, if we decide to migrate both I would actually like to see foreman-announce to be migrated as well. We previously had issues sending plugin announcements into this low-volume list, it's a chance to change this and split it into announce-core and

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

Thanks please announce the branching day a day ago and ask to stop merging breaking changes, so we can test our plugins with the "candidate" for branching. That would be super nice! LZ On Thu, Nov 23, 2017 at 2:03 PM, Ondrej Prazak wrote: > Hi, > this is just a quick summary

Re: [foreman-dev] Getting Foreman and Smart-Proxy to run in FIPS environment.

n Mon, Nov 20, 2017 at 8:05 PM, Dmitri Dolguikh <witlessb...@gmail.com> wrote: > > > On Mon, Nov 20, 2017 at 2:05 AM, Lukas Zapletal <l...@redhat.com> wrote: >> >> Perhaps - can you bit elaborate the GDB >> thing? Is this some kind of hook that use used fo

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

Kearney <bryan.kear...@gmail.com> wrote: > How would folks disable it opt out of sending this data? > > On Nov 20, 2017 9:46 AM, "Lukas Zapletal" <l...@redhat.com> wrote: >> >> Hey, >> >> on the last demo I presented my proposal for telem

[foreman-dev] Foreman instrumentation for telemetry proposal

Hey, on the last demo I presented my proposal for telemetry (it is actually a separate video). I am looking for non-intrusive approach with broad integration possibilities: https://www.youtube.com/watch?v=gCLSI9-4QpE This was also showed on our demo last week (the same content):

Re: [foreman-dev] CDN for the theforeman.org

Great, thanks. Before moving on, I'd check if yum/deb accepts these kind of certificates. I *think* so, but I've heard from security guys they don't like these certs at all :-) LZ On Fri, Nov 17, 2017 at 4:14 PM, Greg Sutcliffe wrote: > Hi all, > > I've signed the

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

e to >>> explicitly only support EL 7.4 and up. We don't have the resources to >>> support older versions especially since CentOS doesn't support that either. >>> If users want verified working versions on EL < 7.4 then they should either >>> help us properly

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

t;>> On Wed, Nov 15, 2017 at 2:08 PM, Patrick Creech <pcre...@redhat.com> >>> wrote: >>> >>>> On Wed, 2017-11-15 at 14:00 -0500, Patrick Creech wrote: >>>> > On Wed, 2017-11-15 at 19:56 +0100, Lukas Zapletal wrote: >>>> > &

Re: [foreman-dev] Request to add Fedora 27 to Koji

We have 200GB spare space, one more Fedora could fit. Can we delete Fedoras 24 and 25? This is definitely the last time before we'd need to expand space again. I initiated mrepo dry run which turned into real run and koji is now out of service due to missing metadata, we are working on this. Will

[foreman-dev] Koji repo sync metadata problem

Hey, when I initiated mrepo -n (dry run) this morning to see how mrepo works on our koji in order to test if we are able to add Fedora 27 for Pulp, I learned that this "dry run" is actually a real run and mrepo initiated full resync of our content without metadata regeneration. This rendered our

[foreman-dev] [RFC] Deprecate and move Github RFC repo content

Hey, this is another proposal to deprecate Github RFC repo and move the content to our wiki. Reasons: A) There is zero merged proposals for the past year (Jan-Nov 2017): https://github.com/theforeman/rfcs/commits/master B) Activity is very low (comments in 3 PRs last winter, 3 PRs last summer,

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

I will just reply to phased rollout. > Also, this may be wishful, but the fact that > people choose to post on StackOverflow rather than our mailing list > again shows a desire for more modern forms of interaction. Why are we creating a duplicate of StackOverflow then? There is a community

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

; > Out of the box, you'll automatically get reporting of your controller, view, > and db runtimes for each request. > > That sounds a lot like what you're interested in. > > [1]: https://github.com/influxdata/influxdb-rails > > > On Tue, Nov 07, 2017 at 10:49:56AM +0100

Re: [foreman-dev] Foreman instrumenting analysis

> In reading about push vs. pull, my biggest issue with it is that the > application has to have knowledge of where it's pushing. Whereas the pull > model allows an application to say I have metrics here and anything that > knows how to scrape and interpret those metrics can grab them at their >

Re: [foreman-dev] speeding up tests

Nicely written. > Ruby 2.2 -- postgresql: 48 minutes > Ruby 2.2 -- mysql: 30 minutes > Ruby 2.2 -- sqlite3: 26 minutes > Ruby 2.3 -- postgresql: 56 minutes > Ruby 2.4 -- postgresql: 57 minutes Fun fact, the newer Ruby version the slower time. > Setup: 12 minutes This is one major pain we have

Re: [foreman-dev] speeding up tests

> We can define these tests as a seperate set that gets only a weekly run, > but deletion is IMHO the completetly wrong way. https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf A cleanup *is* reasonable, not completely wrong way. I bet that week after we move this into 2nd tier it

[foreman-dev] Re: Foreman instrumenting analysis

Any other ideas for telemetry protocols? If there are none, I will rebase my telemetry patch back to the original version based on statsd. LZ On Tue, Oct 31, 2017 at 8:33 PM, Lukas Zapletal <l...@redhat.com> wrote: > Hello, > > I am seeking for app instrumenting protocol fo

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

> No, I don't think we can. We've been over this in the preceeding emails. > We can give an archive a shiny GUI, but fundamentally they have a > different feature set, and a different target user group. Your position > on Discourse is clear, and recorded here for all to see. If enough > people

Re: [foreman-dev] speeding up tests

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 value is almost zero. This is not out of my head, I've heard that on a talk somewhere. Instead of deleting, we can move it to archive - run them on a

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

Greg, I absolutely understand the motivation, every two years amount of programmers doubles. That is a crazy amount of newcomers. But these new people are not idiots and some technical level is required even for soft roles in our community. And we can make lists approachable very much like forums.

[foreman-dev] Rails log is now printed for failed tests

Hey, just to want to increase visiblity of this patch: https://github.com/theforeman/foreman/pull/4739 In short, when you have a test failure, there should be a relevant Rails log printed on standard output. You can opt-out this via ENV variable if you don't like this, but I find this very

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

> So if I understand, you're OK with a web interface for creating / > managing a conversation that you don't want in your inbox in Hyperkitty, > but not happy with exactly the same workflow in Discourse? I find that > hard to resolve, can you clarify? All I want is standard mailman-like list

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

I was planning not to reply, but I can't sorry. >>> I don't like Discourse at all. <<< I was hoping to get rid of Google Groups in favour of - wait for it - GNU Mailman! Yeah, you might think this would be step backwards, but let me explain. GNU Mailman is the core of open source. It's the

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

t. I still have concerns about the non-standard special per-thread address way of replies which I get. How do I start a new thread via email? Can I do that, can't I? LZ On Fri, Nov 3, 2017 at 10:58 AM, Greg Sutcliffe <g...@emeraldreverie.org> wrote: > On 02/11/17 18:35, Lukas Zaple

Re: [foreman-dev] Foreman instrumenting analysis

> I lean towards the push model here. The main reason is > the simpler way to publish the instrumentation data from whatever > process we want to track. Also, my understanding is, that we don't care > only if the service is up or down (readiness and liveness) but also > about trends during the

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

Tried to reply with just few words and I am getting: We’re sorry, but your email message to [“theforeman.discourse+680bec16c469f36694d1ecef341e8...@gmail.com”] (titled Re: [TheForeman] [Testing Area] October newsletter) didn’t work. Reason: Body is too short (minimum is 20 characters) If you can

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

Big +1 to all of that. I think COPR provides some own GPG keys and IIRC you can't override those. It is possible to download packages from COPR and sign them again with a custom key of course. That's perhaps your plan I guess. Custom signatures is on COPR development TODO I think. LZ On Wed,

Re: [foreman-dev] Foreman instrumenting analysis

> Does Prometheus only not work in a multi-process Rails web server? Does it > work for a single process multi-threaded web server? This is an interesting > roadblock given you'd expect this to affect lots of webserver across > multiple languages out there. Any Rails app that has multiple

Re: [foreman-dev] Foreman instrumenting analysis

Statsd can be configured for remote transport, meaning that the collecting agent (or aggregating process if you like) can run on remote server (or container). It is recommended to run it either on localhost or at least LAN, it is not a good idea to route the UDP packets through complex

[foreman-dev] Foreman instrumenting analysis

Hello, I am seeking for app instrumenting protocol for Foreman Rails application that will fulfill the following requirements: The protocol must work with multi-process server like Passneger. The protocol can be easily integrated into Foreman Tasks and Smart Proxy. The protocol or agent must

Re: [foreman-dev] Koji builder crash - days after

for this kind of mails? Anyone else want to get these emails? If we decide to puppetize, let's make sure this is under puppet control. LZ On Mon, Oct 30, 2017 at 11:33 AM, Greg Sutcliffe <g...@emeraldreverie.org> wrote: > Hey > > On Mon, 2017-10-30 at 10:22 +0100, Lukas Zapletal wrote: &

Re: [foreman-dev] Koji Outage

ch 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 Th

[foreman-dev] Koji builder crash - days after

Lukas Zapletal, Eric Helms and Mike McCune. If you need to be there, contact them. h2. Volumes and mounts The instance has two EBS volumes attached: * /dev/sda1 - root * /dev/sdx - data volume (/mnt/koji available as /dev/xvdx1) The instance must be running in a security group with ports 22, 80, 443

Re: [foreman-dev] Jenkins can now send email

Ok waiting for: https://github.com/theforeman/foreman_discovery/commit/473f28621aeba96bea53117611312a78b9159341 On Thu, Oct 26, 2017 at 5:08 PM, Greg Sutcliffe <g...@emeraldreverie.org> wrote: > On Thu, 2017-10-26 at 15:53 +0200, Lukas Zapletal wrote: >> Ok added me into the l

Re: [foreman-dev] Heads up - hound rubocop version updated

Thanks Tomer! LZ On Thu, Oct 26, 2017 at 4:13 PM, John Mitsch wrote: > This was fixed on katello by https://github.com/Katello/katello/pull/7036 > > If you have an open PR on katello, you may want to re-kick off Jenkins > > -John > > John Mitsch > Red Hat Engineering >

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

+1 nice work thanks. LZ On Thu, Oct 26, 2017 at 11:39 AM, Sean O'Keeffe wrote: > Hi, > > I'd like to request write access to the installer team. > > I've been involved with 38 PRs across what I'd consider to be the 'main' > repos, apparently I created 15 of them and I guess

Re: [foreman-dev] Jenkins can now send email

Ok added me into the list in the post-build action. LZ On Thu, Oct 26, 2017 at 2:58 PM, Greg Sutcliffe <g...@emeraldreverie.org> wrote: > On Thu, 2017-10-26 at 14:50 +0200, Lukas Zapletal wrote: >> Greg, thanks for doing this. Now, honestly I do not understand a >>

Re: [foreman-dev] Koji Outage

) and then find the /mnt/tmp backups, restore the directory structure, restart (rather whole system than just koji) and it should show up. Last thing would be to associate the elastic IP. On Thu, Oct 26, 2017 at 2:56 PM, Lukas Zapletal <l...@redhat.com> wrote: > Likely a hardware failure

Re: [foreman-dev] Koji Outage

Likely a hardware failure according to notification, our instance is not responding. We are trying restart first. *** EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance associated with this event in the us-east-1 region. Due to this degradation, your

Re: [foreman-dev] Jenkins can now send email

Greg, thanks for doing this. Now, honestly I do not understand a single paragraph here. Can you show me an example JJB patch how to enable this for a plugin? Ideally discovery, with my spam eating lzap+...@redhat.com :-) LZ On Thu, Oct 26, 2017 at 2:21 PM, Greg Sutcliffe

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

+1 On Wed, Oct 25, 2017 at 3:25 PM, Eric D Helms wrote: > +1 from me as well. I'll look to add you to the team come Monday if no > objections are raised. > > On Tue, Oct 24, 2017 at 5:53 AM, Ohad Levy wrote: >> >> >> >> On Mon, Oct 23, 2017 at 7:16 PM,

[foreman-dev] OSS Europe 2017 Prague slide deck and demo video

Hey, I visited Prague on Monday and Tuesday to give talk about Foreman. I gave the standard talk, updated the standard slide deck a bit and gave it a small refresh. I pre-recorded DEMO showing PXE booting Debian 9 system with Puppet installing ntpd daemon in Foreman 1.15. The talk was not

[foreman-dev] Safemode doesn't allow to access 'block_pass' on &:present?

Hello, I am just preparing demo for OSS Europe and I noticed that the bug in safemode hasn't been fixed in 1.15.6 yet. That's a blocker bug we should consider fixing in 1.15 series. Was there a bump of safemode gem or templates? The issue is with: Katello Kickstart Default template:

[foreman-dev] Place to put slide decks

Hey, I have a couple of slide decks about Foreman, mostly recycled material. At OSS Europe in Prague I am giving "the standard" talk about Foreman on Monday, will edit the latest version of the slides but I was wondering - do we have a place to put those OpenOffice.org files in? If not, shall we

Re: [foreman-dev] Turned off autoupdate at transifex

I would like to know what was the reason to do that. It used to work fine for discovery so far. I just pushed updated POT into git, I am about to branch off 10.0 tomorrow. You told me you are going to re-enable this again? Thanks LZ On Thu, Oct 5, 2017 at 4:18 PM, Lukas Zapletal &l

Re: [foreman-dev] Vendorizing or Building RPMs

I agree with Tomer here, ditto. On the other hand, the way how rubygems are being packaged makes package patches (RPM patch file sets) really hard (in short - it's a hack). Since I also touch packaging work here and there, I know how much work is to maintain full stack like Ruby on Rails. So I

Re: [foreman-dev] Current State of Nightlies

EPEL is not great place to be for Rails or Node components. You should not bump versions in EPEL7 (major relase should go into EPEL8). On Tue, Oct 17, 2017 at 12:01 AM, Eric D Helms wrote: > > > On Oct 16, 2017 5:17 PM, "Sean O'Keeffe" wrote: > > Why

Re: [foreman-dev] Redmine running slowly

Thanks guys for doing this. If things go terribly wrong, we still have an account on EC2 where we run our koji. On Tue, Oct 10, 2017 at 9:21 PM, Greg Sutcliffe wrote: > On Tue, 2017-10-10 at 10:50 -0400, Andrew Kofink wrote: >> Me as well. It's quite difficult to work

[foreman-dev] Foreman develop brakeman report

Hello, I performed security audit report via brakeman gem and reviewed all warnings found. None of these look like exploitable security issue to me, so I am sending it here for further analysis. The first two warnings really smell tho therefore I created a refactor ticket - we should get rid of

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

tter place to show this information >> (and allow the user to filter to see only what are currently syncing). >> >> If we were going to just yank the sync status page, i think we would need >> to do some user interviews and confirm that the products page and dashboard >> widgets fu

[foreman-dev] Katello UX nitpick - Sync Status

Hey, I constantly keep mis-clicking on Sync Plans instead Sync Status in Katello. Any UX advice how to change that? I suggest either rename one to be more visible so you can easily target that with mouse or break these two guys into different main menu entries. LZ -- Later, Lukas @lzap

[foreman-dev] Recording: how to setup provisioning for development

Hello, although I know that forklift provides basic provisioning setup, this is only for nested environment which does not work for me (e.g. discovery livecd is booting up about an hour on my system in nested). We had a one hour head-to-head meeting with Rahul and I created recording of that

Re: [foreman-dev] Redmine running slowly

Ohad mentioned this on our coffee meeting, but why we insist on OpenShift? It's just a regular Rails app, we could easily drop it to one of our web hosts and maybe the performance will be even better than it was. In other words, no OpenShift V3, our infra for now and forever. Not sure how much

Re: Re: [foreman-dev] unscheduled 1.15.5

: >>>> >>>> Similarly I think the installer is meant to be updated to work with 7.4 >>>> - >>>> https://github.com/theforeman/foreman-installer/commit/f07567ee06742155a079f076823c6a3bfbc38120 >>>> >>>> On 10/03, Lukas Zapletal wr

Re: [foreman-dev] unscheduled 1.15.5

Ondra, what fixes are you talking about? Is this the container selinux installation issue? If there is a chance of sneaking in https://github.com/theforeman/foreman/pull/4555 if this is merged in the deadline, that would be great. Pretty important provisioning DHCP issue there. LZ On Tue,

Re: [foreman-dev] Form inputs and accessibility

I think there was a patch that added randomized IDs to all elements which were missing it. I think it did not get it through review. LZ On Sat, Sep 30, 2017 at 6:33 PM, Ohad Levy wrote: > > > On Fri, Sep 29, 2017 at 7:16 PM, Walden Raines wrote: >> >>

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

Assuming that folks are working on CI redesign, can you guys include that on your TODO please? LZ On Wed, Sep 27, 2017 at 1:46 PM, Ewoud Kohl van Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: > On Wed, Sep 27, 2017 at 01:34:08PM +0200, Lukas Zapletal wrote: >> >> what y

[foreman-dev] Requesting discovery test for core PRs

Hello, what you think about adding discovery to core PRs test suite, just one Ruby version on sqlite3? Recently we had all red situation when we bumped to Rails 5. After Ivan fixed that, we have the same due to fact import refactoring. These changes are good, it's just bad timing when we are

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

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 into Puppet and they tend to modify lots of configs manually

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

+1 thanks for all the help there. On Thu, Sep 21, 2017 at 6:47 PM, John Mitsch wrote: > +1 from me, you've been a great help at reviewing the katello scripts! > > -John > > John Mitsch > Red Hat Engineering > (860)-967-7285 > irc: jomitsch > > On Thu, Sep 21, 2017 at 12:00

[foreman-dev] Help needed: Discovery develop broken (Rails 5)

Hello, we are getting errors in discovery develop due to Rails 5 update: ActiveRecord::SubclassNotFound: Invalid single-table inheritance type: Host::Discovered is not a subclass of Host::Managed

Re: [foreman-dev] Re: Bundler is unable to solve deps for fresh checkout

o have suffered from this today (Monday 1.15.4 tarballs were built > just fine) > > Did you find any other way to fix this? Switching to 2.4 could be an option, > probably > putting a Gemfile.lock on every tagged release isn't a bad idea either. > > On Thursday, September 14, 2017

Re: [foreman-dev] Foreman iot platform plugin

Hello, smart-proxy is usually deployed on remote sites, datacenters or subnets to do all "dirty work" of managing local DHCP servers, turning servers on/off via BMC and stuff like that. Also clients connects to smart-proxies to do their rhsm registration, yum updates or uploading openscap reports.

Re: [foreman-dev] Bundler is unable to solve deps for fresh checkout

wrote: > Tried with rhel7 VM, same gem and ruby version as yours (2.0.0p648), > dependencies resolved just fine. > Failed later on installation of some gem (as it requires ruby 2.1+), > but the memory kept under 300MB > for all the time. > > -- Ivan > > On Fri, Sep 15, 2

Re: [foreman-dev] Bundler is unable to solve deps for fresh checkout

uld be causing this? >> >> -- Ivan >> >> On Thu, Sep 14, 2017 at 3:13 PM, Lukas Zapletal <l...@redhat.com> wrote: >>> Hey, >>> >>> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and >>> 2.4.1), bundle install is

[foreman-dev] Bundler is unable to solve deps for fresh checkout

Hey, when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and 2.4.1), bundle install is not able to resolve dependencies and loops forever. I am using latest stable bundler, tried also pre1 version. Can someone confirm and provide a workaround? I think copying Gemfile.lock from

Re: [foreman-dev] Re: Release of Foreman Discovery 9.1.2

Hey, foreman-discovery-image is the correct locale. We can remove the fdi.pot from the codebase, perhaps a mis addition. LLZ On Fri, Sep 8, 2017 at 8:26 PM, Bryan Kearney <bryan.kear...@gmail.com> wrote: > On 09/08/2017 08:01 AM, Lukas Zapletal wrote: >> >> Hello, >&

  1   2   3   >