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

2017-11-16 Thread Eric D Helms
I started an mrepo run after adding CentOS in a screen session. The run appears to be running a lot longer than previous and it's not clear to me what exactly it's doing at present or whats safe to do. Lukas could you check on it in your morning and see if you spot anything odd about why it seems t

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

2017-11-16 Thread Dmitri Dolguikh
What is FIPS? >From Wikipedia [1]: The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB 140-2), is a U.S. government computer security standard used to approve cryptographic modules. The title is Security Requirements for Cryptographic Modules. What are Implications of F

Re: [foreman-dev] Re: [UX] Facets and Host UI - roadmap discussion.

2017-11-16 Thread Roxanne Hoover
Specifically talking to the new host wizard, it was designed to allow users to basically choose a certain type of workflow which would populate the wizard with the relevant data entry forms. This obviously only addresses the creation of things, not necessarily the editing or viewing of them. I don'

Re: [foreman-dev] 1.17 branching schedule

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

Re: [foreman-dev] 1.17 branching schedule

2017-11-16 Thread Eric D Helms
Howdy, I am not clear on what the shape of everything else is, but I think there are two larger updates that are in risk if we stick to our hard time based releases here: 1) Dynflow as a stand-alone service used by Foreman which is targeted for 1.16 GA but needs to also make 1.17 2) 1.17 with R

[foreman-dev] 1.17 branching schedule

2017-11-16 Thread Ondrej Prazak
Hi, I am sending this just to let you know that, according to the schedule, the 1.17 branching should happen in 2 weeks. O. -- 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

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

2017-11-16 Thread Greg Sutcliffe
On 16/11/17 11:51, Greg Sutcliffe wrote: > I've just finished rebasing our Redmine patches onto each of the stable > branches in the upstream repo (see [1]). Next up is testing the DB > migrates correctly, and then I can add the question plugin Marek > mentioned as part of the upgrade. Links help

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

2017-11-16 Thread Greg Sutcliffe
On 16/11/17 11:23, Ivan Necas wrote: > +0, or at least not relying on it as the only way the triage happens. > > +1 for resolving the needinfo feature in redmine: the triage mtg has bigger > potential with it I've just finished rebasing our Redmine patches onto each of the stable branches in the

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

2017-11-16 Thread Ivan Necas
On Thu, 16 Nov 2017 at 12:13, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > +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 > tri

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

2017-11-16 Thread Ewoud Kohl van Wijngaarden
+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 b

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

2017-11-16 Thread Ewoud Kohl van Wijngaarden
Those sound like good arguments, but if we don't test on older releases then we don't know for sure they work either. IMHO it's acceptable 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 user

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

2017-11-16 Thread Lukas Zapletal
Thanks Eric, I added this section about the process for the future: http://projects.theforeman.org/projects/foreman/wiki/KojiSetup#Adding-external-repository On Wed, Nov 15, 2017 at 9:57 PM, Eric D Helms wrote: > This now appears to be working again. One out standing question that affects > node

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

2017-11-16 Thread Tomer Brisker
Hello, After giving discourse a quick spin, I have to say I like it a lot. The UI is great for new comers, the ability to have tags that you can follow and teams is great for focusing on things that require your attention or interest you (or grab someone else's attention when needed). Honestly, I

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

2017-11-16 Thread Lukas Zapletal
We still have 180GB space left, it will be shrinking as we will continue building but let's just wait with Fedora removal until the next release. Eric fixed the building issues anyway. And I just did: [root@koji ~]# koji add-external-repo fedora27-external-repo file:///mnt/koji/external-repos/www