Re: [foreman-dev] Re: Foreman Community Demo Items - Thu 09 Jun

> 2 days to go, still no presenters - I see 153 closed bugs and 23 closed > features in the last 3 weeks, surely someone has something to say? :) I can hardly say what I was eating for lunch yesterday. Can't you just drop the search query link to the list every month please? :-) -- Later,

Re: [foreman-dev] how to determine power on/off of discovered host from API?

Hey, > PUT api/v2/discovered_hosts/:id/refresh_facts yeah this or GET /features works as well. > Any other "ping status" API call? Nope, all other ports except 8443 and 8448 (http) are firewalled. Proper shutdown should delete discovered host (file RFE for this please), good idea. But hard

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

> > > 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 /etc/httpd/conf.d/ 05-foreman.conf 05-foreman.d 05-foreman-ssl.conf

[foreman-dev] UEFI RFC - final comments

Hello, UEFI RFC is now ready for last round of comments. Please speak up, if you have objections on the design: https://github.com/GregSutcliffe/rfcs/blob/21d269bafd70315876c4589f1c0564187a77c069/text/-PXE-Booting-UEFI.md I would like to start working on Foreman Core changes next week.

Re: [foreman-dev] Deprecate EL6?

> > That said, I believe security updates are the most important to them so > > you could consider supporting the last release on EL6 a bit longer. I > > don't know how much of a time/effort difference that makes compared to > > supporting it longer on the newest release. > > Yeah, I can

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

> For example, several dev teams are experimenting with redmine "versions" > for their sprints[1]. I don't think that a single version can include One more thing. This will pollute Target versions, I don't like this. Can't we simply use Issue trackers for that? Redmine is quite good in creating

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

> 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, own planning (Release versions, Target versions) and Categories. I don't see enough benefits of merging when I consider all the above. I don't know, I

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

> The problem with this approach is that it's hard to create a team > backlog (you create a giant tracker?), plus tracker issues don't allow > you to prioritize what do you do in each sprint. Backlog = whole RedMine (all Feature items that are not associated with any "sprint" tracker). > With

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

> You do realize that every other plugin except Katello is under the foreman > project in redmine, correct? I haven't realized that, sorry for the noise :-) -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To

Re: [foreman-dev] inspec or serverspec tests

> has somebody integration tests for infrastructure of theforeman > for example based on inspec or server spec ? Please do not cross-post. This belongs to the -users list I guess. I am not aware of these at all. -- Later, Lukas #lzap Zapletal -- You received this message because you are

[foreman-dev] Counter cache removed in develop (performance)

Hello, I just merged Tomer's patch which removes counter_cache fields. http://projects.theforeman.org/issues/12193 https://github.com/theforeman/foreman/pull/3596 http://guides.rubyonrails.org/association_basics.html#detailed-association-reference This was preliminary optimization, we have

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

> Sorry I don't get it, especially the price. What's the difference between core > and plugins in terms of permissions upgrades? If you rename plugin permission > you need to provide the same migration as if you renamed it in core. Once we merge everything into core roles, there is no easy way

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

> If you're concerned about the permissions table, this does not help. > Permission are created there by plugin. If the permission is removed later, it > should be removed from all roles anyway, user could already assign it to both > core and plugin role. Down below. > I suppose you wrote a

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

gt; writes: >>> >>> > On Tue, Jan 24, 2017 at 12:10:34AM +0100, Ivan Necas wrote: >>> >> Ohad Levy <ohadl...@gmail.com> writes: >>> >> >>> >> > On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal <l...@redhat.com> >>

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

Corrections. > Why you don't like explicit lock actions? I misinterpreted your statements above, looks like we both like explicit locking. > add_permission_to_provisioning_manager (also adds to "manager" role) > add_permission_to_provisioning_reader (also adds to "reader" role) >

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

> Ok, we discussed the migration path. We should be (with small changes*) able > to detect whether users modified existing Manager role. In case they did, we > would rename them to "Customized Manager" and create new Manager role with > default permissions but locked. Locked means no changes to

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

Hey, our design of template proxying is not good, I constantly need to solve problems setting it up. In order to have this working, both Templates and TFTP features needs to be turned on. This is confusing, then several Proxy settings need to be correctly set and since the names are also

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

+1 definitely much better experience, we can carry on then and provide a diff between cloned and original, so user can merge the changes more easily. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop

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

> Let's continue the discussion here since it might read more people. I think > that as a user I don't care that my installation consists of core and several > plugins and I want to have Viewer role that gathers all view permission for > the whole app. > > This does not in conflict with also

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

On Mon, Jan 16, 2017 at 6:55 PM, oprazak wrote: > So if a plugin is installed, user has to go and find what role/permission is > missing or ask someone who can grant permissions. I do not think the proposed approach is the best, here is my lengthy explanation:

Re: [foreman-dev] HoundCI - annoying?

I feel actually quite the opposite, we used to have Hound via some external service and this feels much better integrated. Since github introduced reviews, Hound integration could take advantage of it in the future? They will implode once a review is confirmed, that could help. On the other hand,

Re: [foreman-dev] Revert removal of @host.params for host_param

I am also for keeping the change but giving more attention to the upgrades and providing some tooling to convert existing templates. LZ On Wed, Jan 11, 2017 at 5:05 PM, Daniel Lobato Garcia wrote: > Hi foreman devs, > > Just noticed today

Re: [foreman-dev] .ISO deploys with Discovery

Thanks Greg, that's what I want to work on this week :-) More on this topic, we already have integration of Foreman Bootdisk with VMWare. You create new VM, that gets Bootdisk attached as an ISO file automatically and boots into Anaconda directly without PXE or DHCP. This might be interesting for

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

van Necas wrote: >> > Lukas Zapletal <l...@redhat.com> writes: >> > >> I'm not sure I follow what you mean by administrative tasks. Note that >> > >> reports >> > >> import and puppet envs import are core actiones that now run as a >> > >

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

> > 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/ Those first hits :-) I have considered that of course, it does

[foreman-dev] Hammer CSV module does not load

Hey, this is Katello 3.3, on every hammer call I am getting: Warning: An error occured while loading module hammer_cli_csv Is there a bug? -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from

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

> It would be nice to see the differences. It's almost the same speedup as with symlink (the difference is loading the database three times perhaps): real13m32.018s user11m13.229s sys 0m12.004s What is your file system? That might do the difference. -- Later, Lukas #lzap

Re: [foreman-dev] Changes to PR tests on Foreman repo

> script. It has a few advantages, such as running the jobs separately to > reduce the number of slave slots used, and aborting running jobs when a > PR is updated. I hope it will improve the general throughput of PR Thanks! -- Later, Lukas #lzap Zapletal -- You received this message because

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

> > Sounds pretty good to me. Just to check we're on the same page, the > > patch below is meant so that the discovery image accepts blocks, so that > > the discovery image can accept *another* image and boot from it? > > I was under the impression you could use image to dump to disk and boot it

Re: [foreman-dev] cannot provision w/ foreman

> Hostgroup creation is blocked by -> > http://projects.theforeman.org/issues/16532 Yeah, sorry about that, I've changed the attributes of the architecture_selected and os_selected to match the media_selected implementation to allow pxe_loader hook. This patch in Foreman core makes forms usable

Re: [foreman-dev] npm 3.x now needed for source installs

> 2. install locally using 'npm install npm' inside the foreman directory, > after which you will need to run './node_module/.bin/npm install' to use > the local version (this is what we do on jenkins) Thanks. Could you please update our https://theforeman.org/contribute.html guide with

[foreman-dev] Diploma projects - need ideas

Hello, few students of mine are considering doing Diploma Thesis for Red Hat. Can you figure out some good Foreman topics? Unfortunately, it looks like today UNIX and datacenter administration is uncool, as I have learned the other day, so ideally they are looking for: - JavaScript and UI/UX -

[foreman-dev] Need reviewers: https://github.com/theforeman/hammer-cli-foreman-admin

Hello, this small repo is lacking reviewers, take your chance! https://github.com/theforeman/hammer-cli-foreman-admin/pull/3 Thanks -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this

Re: [foreman-dev] Call for help: Installer changes for UEFI

> I think, we should not depend on downloads from the (evil/firewalled) > internet. I agree, but it does not appear to be present in Debian repos. > What do you think of packaging this? Not so keen about it. But it's an option for sure. > We should at least make the mirror url configurable.

Re: [foreman-dev] Call for help: Installer changes for UEFI

> > I think, we should not depend on downloads from the (evil/firewalled) > > internet. > > I agree, but it does not appear to be present in Debian repos. I actually found a way how to build EFI grub from modules, updated the description: http://projects.theforeman.org/issues/12635 Looks like

[foreman-dev] Re: RFC for foreman_api_v3

> 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 > accepts, I am happy to move this repo to theforeman/foreman_api_v3 Joseph, can you

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

in-memory, I will surely switch to it. > > > On Wednesday, August 24, 2016 at 12:10:05 PM UTC+3, Lukas Zapletal wrote: > > > > > It would be nice to see the differences. > > > > It's almost the same speedup as with symlink (the difference is loading >

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

> I would suggest even considering moving the entire /var/lib dir to tmpfs > instead of on disk so the other DBs will get a boost - assuming the > /var/lib dir is created anyways only for the worker's lifetime and > destroyed afterwards. That's perhaps too much. But fine tuning PostgreSQL and

[foreman-dev] CentOS/Ubuntu based Grub2 binaries for PXE

Hello, I will be creating a noarch RPM package containing Grub2 EFI binaries for various architectures (INTEL 64, AARM64, IBM POWER BE/LE) for RHEL in order to enable users to install them easily on Smart Proxy running on RHEL systems. This is aimed for Satellite 6 customers. At the moment, our

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

Hello, we have Smart Proxy in the Foreman Core, WebUI/API/CLI and also in our Core documentation, but in the installer and package name it's foreman-proxy. This creates confusion. I suggest to "communicate" it from now on with new official name: Foreman Smart Proxy This will help us to "teach"

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

On Fri, Nov 25, 2016 at 3:40 PM, Marek Hulán wrote: > Please share your ideas for other structuring or which of schema mentioned > above you find better. The level of nesting does not matter from technical > point of view but I think 2 or 3 directories is the limit. > I like

Re: [foreman-dev] Foreman bootloaders effort

On Wed, Nov 16, 2016 at 2:02 PM, Daniel Lobato Garcia wrote: > Thanks, this is very helpful and should probably be delivered with > Foreman itself. As far as I know you'd need to overwrite the bootloaders > if you change to Debian-family OSs (rendering provisioning with RH >

[foreman-dev] Weird behavior of ISC DHCP - solved

I spent some time on Foreman instance that was not working properly. There were literarly no leases or DHCP records, we verified this via curl that proxy was not returning anything, but New Host creation was always failing with 409 conflict. It turned out there were two dhcpd processes running

[foreman-dev] Foreman bootloaders effort

Hello, I created a script that is able to extract relevant bootloaders from Fedora, CentOS and RHEL OSes. Here is how it looks like: https://lzap.fedorapeople.org/temp/foreman-bootloaders/ The goal is to provide RPM and DEB packages for all our supported platforms so users can easily decide

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 <lz...@redhat.com >>> > <mailto:lz...@redhat.com>> wrote: >>> >> >>> >> > This appears more inconsistent than the cur

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

> Sounds positive so far - which repos should we try it on? I'm thinking > core, proxy, katello and the website for now? We can put it everywhere if > that goes well. I love this bot, I already know that in advance. I'd scratch the website tho, the three would be a good start. -- Later, Lukas

Re: [foreman-dev] steps to update locale before releasing gem?

http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Pl ugin#Translating I suggest to take a look on https://github.com/theforeman/foreman_discovery/blob/develop/release-ge m LZ Tom McKay píše v Po 10. 10. 2016 v 11:06 -0400: > Is there a doc somewhere on what steps to take for

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

> This appears more inconsistent than the current situation, as there will > now be three terms, differing between the UI names ("Foreman Smart > Proxy"), API/module names ("smart proxy"), and package names ("foreman > proxy"). That's indeed a very true statement, I'll add that the new term aims

Re: [foreman-dev] encryption/decryption functionality

AFAIK we are not using any self-develop cryptography, just regular Ruby and Rails algorighms like md5, sha, X509, UNIX crypt, ActiveSupport::MessageEncryptor and stuff like that. If you are going to do security audit, please share your results. Keep in mind that if you found a security bug, use

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

I like it, few false alerts here and there but it is worth it. LZ On Wed, Dec 7, 2016 at 4:50 AM, Tom McKay wrote: > +1 from me as, at a minimum, gives me an idea of who I could ping on IRC > to look at a PR. > > On Tue, Dec 6, 2016 at 1:11 PM, Marek Hulán

Re: [foreman-dev] Foreman bootloaders effort

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. On Wed, Nov 23, 2016 at 2:13 PM, Lukas Zapletal <l...@redhat.com> wrote: >

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

> > I'm not sure I follow what you mean by administrative tasks. Note that > reports > import and puppet envs import are core actiones that now run as a foreman > task > (both synchronous and asynchronous variants). By making the UI part > optional > users would not be able to monitor their

Re: [foreman-dev] Upgrading from 1.11 on CentOS 6 to 1.13 on CentOS 7

Hello, I noticed today we execute the import twice, for some reason. Reported a bug: http://projects.theforeman.org/issues/17974 You better use pg_restore directly on the dump. You may also need to provide --data-only if you migrated the database. On Fri, Jan 6, 2017 at 10:31 PM, Matthew Ceroni

Re: [foreman-dev] Retire the RFC repo?

I find email (properly tagged) more comfortable than github or wiki, but I can live with current status if folks prefer. So you can bucket me in "keep as is". LZ On Tue, Mar 21, 2017 at 4:39 PM, Greg Sutcliffe wrote: > I've been meaning to reply to this for about a

Re: [foreman-dev] Moving from infinite scrolling to pagination for katello tables

I am glad this is happening, it was so confusing to have such a different way of basic navigation. And I hope more to come! Kudos! LZ On Thu, Mar 23, 2017 at 8:15 PM, Walden Raines wrote: > Hey y'all, > > TL;DR: goodbye infinite scroll, hello pagination for katello tables. >

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

On Tue, Mar 14, 2017 at 2:28 PM, Daniel Lobato wrote: > foreman-selinux - Lukas - lzap Sure no problem, ping me when it's the time. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To

[foreman-dev] Heads up: Use ApplicationRecord base for your models

Heads up! Ivan merged my patch that changes behavior of how orchestration is logged. Previously it was logging everything into sql logger which is usually turned off by default as it is flooding logs. Since orchestration logs are very important I made a change which made possible to redirect

[foreman-dev] Re: Heads up: Use ApplicationRecord base for your models

> Heads up! > > PG::UndefinedTable: ERROR: relation "application_records" does not exist This error appears to show up when Rails devel environment is reloaded on change. We are tracking this down, but be careful until we find this. -- Later, Lukas @lzap Zapletal -- You received this

Re: [foreman-dev] Issues with support of IPv6/DHCPv6 in Smart-Proxy

On Mon, Mar 6, 2017 at 4:53 PM, Dmitri Dolguikh wrote: > - It is difficult to determine host’s client id (dhcp unique identifier, AKA > DUID) What you mean by that? If sysadmins let DUID to change, they are breaking IPv6 specs and servers will mis-behave. What exactly are

[foreman-dev] Re: Koji planned outage - tomorrow

I am restarting koji right now, expect it to come back in 5 minutes. Updated packages: glibc, glibc-common I disabled EPEL because there is new Koji version 1.13 pending update (we are on 1.11). No alerts in logs. On Mon, Jul 31, 2017 at 3:34 PM, Lukas Zapletal <l...@redhat.com> wrote: &

Re: [foreman-dev] How to disable puppet management of DHCP/DNS/TFTP

Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: > On Fri, Aug 11, 2017 at 08:25:56AM +0200, Lukas Zapletal wrote: >> >> Thanks, created http://projects.theforeman.org/issues/20555 >> >> If anyone can take a look, this has been pain for a very long time. > > > htt

Re: [foreman-dev] Icon Feedback

Hey, nice, but content and infrastructure is a bit weird to me. The folded paper icon is overused in many software and its meaning is blurry to me. Infrastructure is more like support software/hardware, smaller servers, forklift or network icon would be better fit. Something like:

Re: [foreman-dev] How to disable puppet management of DHCP/DNS/TFTP

Wijngaarden <ew...@kohlvanwijngaarden.nl> wrote: > On Tue, Aug 01, 2017 at 01:08:14PM +0200, Lukas Zapletal wrote: >> >> I wrote a short blogpost about how to add new DHCP subnet to Foreman: >> >> https://theforeman.org/2017/07/adding-new-subnet-for-provisioning.html &

[foreman-dev] Jenkins will show Rails logs for all failed tests

Hey, I had an idea today which turned into: https://github.com/theforeman/foreman/pull/4739 When there is a test failure, it is usually impossible to find the correct log in logs/test.log file for paritular failed tests. This patch automatically adds Rails logs (including ActiveRecord) to

[foreman-dev] Syncing F26 external repo on Koji

Hey, on pulp team request, I am adding external repository fedora26 (x86_64) into koji. Initiated the sync, tomorrow I will add that into koji external repositories. For the record, I installed mrepo from sources as it was not available in EPEL7 anymore. Foreman core team haven't decided yet if

Re: [foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

Excellent one, thanks. On Fri, Jun 30, 2017 at 12:35 AM, Eric D Helms wrote: > Thanks for setting this up Greg. > > I wanted to send out a few notes ahead of time so that folks can do any > background reading, using the work I'll be presenting or think about > questions

Re: [foreman-dev] Dropping Fedora 24 packages

Since Katello does not have builds for Fedora and it's extra work and I believe not many users use such an old Fedora systems for productions (there's CentOS of course), I am all for dropping it completely. We are loosing the flexibility of being "on track" with what's next for CentOS on the other

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

-external-repos | grep fedora-26 fedora-26 file:///mnt/koji/external-repos/www/fedora26-$arch/RPMS.os/ fedora-26-updates file:///mnt/koji/external-repos/www/fedora26-$arch/RPMS.updates/ So I guess my job is done then. Have fun. On Tue, Jul 18, 2017 at 9:59 AM, Lukas Zapletal <l...@redhat.com>

[foreman-dev] Re: Looking for facts from big servers

anitize some of the data. > > > On Monday, July 3, 2017 at 9:52:22 AM UTC-4, Lukas Zapletal wrote: >> >> Hey, >> >> we are redesigning UX of the discovery pages and I was wondering if >> you can send me output of facter from some big fat servers. Looking >>

[foreman-dev] Looking for facts from big servers

Hey, we are redesigning UX of the discovery pages and I was wondering if you can send me output of facter from some big fat servers. Looking for extremes, servers with: - lots of CPUs or cores - lots of memory - lots of disks or volumes - or other periciphals The command output we are

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

+1 Thanks. On Mon, Jun 26, 2017 at 3:41 PM, Greg Sutcliffe wrote: > On Mon, 2017-06-26 at 10:25 +0300, Tomer Brisker wrote: >> +1 to adding Eric, although that won't solve the issue of Ohad and >> Dominic being busy and having no owner available on this side of the >>

[foreman-dev] How to disable puppet management of DHCP/DNS/TFTP

Hello, I wrote a short blogpost about how to add new DHCP subnet to Foreman: https://theforeman.org/2017/07/adding-new-subnet-for-provisioning.html At the end of the post, I am giving an advice to turn off DHCP puppet management so new declarations won't get overwritten as our puppet modules

Re: [foreman-dev] Performance analysis deep-dive, what would you like to hear about?

Thanks for doing this. Ideas: - Rails ActiveRecord SQL debugging (eager loading and N+1 problems - how to spot them) - how we configure passenger by default and what are the limitations - how passenger handles memory-leaked processes (it doesn't - see my script) - how to enable slow SQL logging

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

; wrote: > On 05/10/2017 05:05 AM, Lukas Zapletal wrote: >> >> Check out the new version I just pushed into the gist! I hope you will >> like it. > > What is the process to go from gist to in 1.16? > > -- bk > > > -- > You received this message because

[foreman-dev] Migration to Copr POC

Hello, I would like to test Fedora Copr capabilities in serving us as the main build system instead our Koji instance. With assistance from Mirek Suchy, lead Copr developer, I would like to do proof-of-concept of integrating Copr into our workflow as a secondary build system together with Koji.

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

y > migration that removes STI's - it should be enough to remove all DB traces > for a plugin. > > > > On Wed, May 3, 2017 at 2:11 PM, Lukas Zapletal <l...@redhat.com> wrote: >> >> I agree with Tomas, it's more cleaner to remove all the data right >> away. Therefore

Re: [foreman-dev] Re: Koji outage on Sunday

for nightly builds. On Fri, Jun 9, 2017 at 2:46 PM, Lukas Zapletal <l...@redhat.com> wrote: > Hmmm if I'd have to create new koji I'd rather start from scratch > reimporting our repos back in. > > Current problems we had: > > - small vm with not enough cores/RAM to run builds &g

Re: [foreman-dev] Re: Koji outage on Sunday

>> http://34.226.218.207/koji/ >> >> (cleankoji) >> >> I am planning to reverse-engineer from the composes since I have all the >> builds loaded already. But, if there is an easy rebuild that would be great. >> >> -- bk >> >> On 06/09/2017

Re: [foreman-dev] Re: Koji outage on Sunday

:43 PM, Lukas Zapletal <l...@redhat.com> wrote: > Basically you go to foreman-packaging rpm/develop and then: > > git annex get (few won't download so delete them for now and skip them) > > for each package directory (you can do in loop) > tito release koji-foreman > tito r

Re: [foreman-dev] Re: Koji outage on Sunday

will build. Repeat several times, N^2 in the worst case :) LZ On Fri, Jun 9, 2017 at 11:50 PM, Lukas Zapletal <l...@redhat.com> wrote: > Bryan I think I found out, turn off kojira service and then you should > not get regens on each successful build! > > LZ > > On Fri, Jun 9,

[foreman-dev] Re: Koji outage on Sunday

, I need to figure out how to solve this by either increasing capacity or restarting it on different hypervisor. LZ On Sun, Jun 4, 2017 at 1:34 PM, Lukas Zapletal <l...@redhat.com> wrote: > Hey, > > I had to brought Koji services offline, I expect them to come back in > an h

[foreman-dev] Re: Koji outage on Sunday

was always huge pain of our deployment and I think we can simply launch koji on new but bigger instance with enough memory and CPUs so we can handle all the load with single instance without NFS dance. LZ On Fri, Jun 9, 2017 at 10:17 AM, Lukas Zapletal <l...@redhat.com> wrote: > He

Re: [foreman-dev] New Feature Available: Issue Links in PRs

God bless you! LZ On Mon, Jun 19, 2017 at 7:19 PM, Andrew Kofink wrote: > Due to a recent change [1] in prprocessor, issue links will now be added as > a comment [2] to PRs on projects that are enabled. To enable this feature > for a project, submit a PR to prprocessor which

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

I was typing quickly, maybe it was confusing, but nobody said we aim to *replace* fog at all. We were discussing decoupling from Fog API inside Foreman so we could enable writing non-Fog providers, which led to more opened topics like facets, smart-proxy communication or dynflow. This would be

Re: [foreman-dev] Migration to Copr POC

Hello Justin! > 1. Currently we rebuild candlepin srpms in our koji, sign them, and publish > the srpm and rpm > > Should we continue doing this? (in which case we likely need to setup a copr > build root for it). So you want to create Copr repositories in @theforeman Copr group for that,

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

rking to bring about >> more time for myself and others to do so. We need to actively invest in >> this area, make it a priority, and a first class citizen of our community >> to make an impact. >> >> We have wiki pages on creating and releasing plugins. But maybe we need

[foreman-dev] Re: Koji outage on Sunday

Hello, during migration I noticed we are running out of space on the data volume, I am going to remove Fedora 22 and 23 external repositories tomorrow. If you still need them, speak up! LZ On Sun, Jun 4, 2017 at 6:11 PM, Lukas Zapletal <l...@redhat.com> wrote: > I was wondering, if so

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

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 of the bugs we found in Discovery 9.0 would have been found just by executing unit tests with all the plugins enabled. If this is a

Re: [foreman-dev] Koji outage on Sunday

p? > > -- bk > > > On 06/08/2017 06:02 AM, Lukas Zapletal wrote: >> >> Bryan, I terminated builder2 it was running in incorrect security >> group. You can delete it. The one we need to use is called >> "launch-wizard-1" - this is where both koji and bui

Re: [foreman-dev] Koji outage on Sunday

commands. I had some troubles with NFS when we moved external-repos to different volume. Also added some permission changes. http://projects.theforeman.org/projects/foreman/wiki/KojiBuilderSetup Please give it a try now, it should be hopefully fine. On Thu, Jun 8, 2017 at 11:17 AM, Lukas Zapletal <

[foreman-dev] Koji outage on Sunday

Hey, I had to brought Koji services offline, I expect them to come back in an hour, we are trying to move the data to different EC2 instance. This is just a test and if the new instance will work fine, we will do the switchover during the week. Sorry for inconvenience, please resubmit your jobs

[foreman-dev] Re: Koji outage on Sunday

for the record. On Sun, Jun 4, 2017 at 1:34 PM, Lukas Zapletal <l...@redhat.com> wrote: > Hey, > > I had to brought Koji services offline, I expect them to come back in > an hour, we are trying to move the data to different EC2 instance. > This is just a test and if the new instance will

[foreman-dev] Discovery 9.1 this week

Hey, finally we merged all blocker bugs, the commit that will become 9.1 is: https://github.com/theforeman/foreman_discovery/commit/b92744b2d0897c206994ee1a0078b4a65ce29c7c If you want to give fixed discovery a try, please go ahead and report issues here. It is 1.15 compatible. -- Later,

[foreman-dev] Review of koji packages/tags cleanup

Hello, I created a small script https://gist.github.com/lzap/cc6c100feb0a558f961eaa07e01bfa59 which compares our whitelists agains koji. The first phase is packages added to tags. It was used to generate this wiki page where I want to track review process. The same script can be modified to

Re: [foreman-dev] Re: Koji outage on Sunday

non-foreman packages, just upload SRPMs once and then do several rounds of resubmits which are very quick. On Sat, Jun 10, 2017 at 9:12 AM, Lukas Zapletal <l...@redhat.com> wrote: > So I am mass rebuilding 1.13 now, I was able to figure out a GNU > parallel command that will upload all S

Re: [foreman-dev] Re: Koji outage on Sunday

for hours. Just skip that for now. This is a rough mass rebuild just to test how much feasible is this path, I will compare meshed repository with what we have. On Fri, Jun 9, 2017 at 11:54 PM, Lukas Zapletal <l...@redhat.com> wrote: > Also one thought - if your SSD VM is fast enough in

Re: [foreman-dev] Re: Koji outage on Sunday

<bryan.kear...@gmail.com> wrote: > On 06/09/2017 08:27 AM, Lukas Zapletal wrote: >> >> I have some bad news to share. I started on moving from our 2nd koji >> to 3rd koji created as m1.xxlarge instance so we would avoid NFS and >> could run on a single VM. I prepared ever

[foreman-dev] Re: Koji outage on Sunday

) ? On Fri, Jun 9, 2017 at 11:42 AM, Lukas Zapletal <l...@redhat.com> wrote: > After I increased capacity it started to pick tasks, but all were > stuck, I tracked it down to NFS hard connection which was stuck, I > rebooted the builder and it does not come up. > > If I won't fix this in

Re: [foreman-dev] Re: Koji outage on Sunday

zap, is there an easy way to snapshot where the machine is at right >> now? >> >> -- bk >> >> >> [1] >> https://docs.google.com/document/d/1909hoztG37oWHyzdSWA4U4M9E8ocrk4qy6a57j3P1FE/edit >> >> On 06/10/2017 11:25 AM, Lukas Zapletal wrote: >&

[foreman-dev] Re: Review of koji packages/tags cleanup

you see something incorrect on this list? https://gist.github.com/lzap/6a0fcc774bd14a15a30daf702827c5db If not, I will go ahead and execute the rest on Monday. Updated version of my script is at https://gist.github.com/lzap/cc6c100feb0a558f961eaa07e01bfa59 On Thu, Jun 15, 2017 at 4:16 PM, Lukas

  1   2   3   >