[foreman-dev] *** This mailing list is now archived ***

. I'm sure we'll like our new home, but it may take us a short while to settle in :) Happy New Year (and new tools)! Greg -- Greg Sutcliffe Foreman Community Lead -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from

[foreman-dev] Discourse migration begininng now

As per the migration schedule, the final migration happens tonight. I'm beginning work on this now, so expect some weirdness in the near future ;) I'm setting all users to "moerated posting" so that we can catch any users that havent seen the change yet and gently redirect them to the forum - if

[foreman-dev] Final reminder - Foreman will move from Google Groups to Discourse on 1st Jan 2018

Hi all, As per the migration plan, all is going smoothly and we are in the final week before tranisiton on New Year's Eve. We're already seeing some good traffic to the forum and people are getting answers so it seems it'll perform it's primary function just fine :) A reminder that if you

[foreman-dev] Re: [foreman-users] ACTION - Foreman will move from Google Groups to Discourse on 1st Jan 2018

We're now 2 weeks away from migration date, so here's a quick update. * Lists, website, blog, and Twitter updated with the migration details * 100+ user visits in the last week * Support, Dev, and Feedback categories actually getting some real use * Outbound email and system load well within

Re: [foreman-dev] Introducing #theforeman-dev-ui, an experiment

On 14/12/17 16:04, Walden Raines wrote: > The UX team is playing with the idea of forking UI discussions out > into a separate channel. We will do a month long experiment and see > how it goes. > > *Background:* The irc channel #theforeman-dev is very busy and > there are often times multiple

Re: [foreman-dev] Re: Discourse - upcoming dates

Yeah, I wasn't suggesting changing the default, it's just a nice option to have. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop

[foreman-dev] Notifications / monitoring for infra

Lukas asked me to raise this after Koji ran out of space, so ... :) Currently there are two forms of notification from our infra. Firstly there is the private infra Google Group, but no-one seems to know who maintains is (Dominic?). Secondly, there is a list of email addresses written by Puppet

[foreman-dev] 2018 community survey

It's time (again, :P) to start drafting the community survey for while we're in Belgium next year :) I'm short on time today, so here's a link to last year's survey. Much of the generic questions will remain the same, they seem to work. What other burning issues would people like data on? What

[foreman-dev] Re: Discourse - upcoming dates

It's been a week since I opened up the poll, time for an update... TLDR: Poll closes next week, then it's "New year, new tools" ;) # Myself As most of you know, today is my last day full-time, as I go off on leave tomorrow for a few months. However, this is my most ambitious community project

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

On 29/11/17 12:17, Ewoud Kohl van Wijngaarden wrote: > So I'd disagree we use SemVer. I didn't mean we use it *properly*, just that anytime I see X.Y.Z as a versioning structure, my mind immediately thinks SemVer. That we *do* use it in other places only adds to the confusion. What I am

[foreman-dev] Redmine upgrades - WIP

Hi all, As you all know, our Redmine instance is very very old, so I just wanted to give a quick note about where I got to with upgrading it, and some notes if anyone wants to take over, since I likely won't have time to push this forward while I'm away. The TLDR is that plugins are a pain...

Re: [foreman-dev] Kanban tools and redmine

On 28/11/17 21:29, Walden Raines wrote: > Hey, > > With several teams moving to kanban style tools for the visualization of > tasks I'm wondering if anyone has tried redmine's PluginKanban [1]. Haven't tried it, yet :). Performance would be good to find out about (Redmine Backlogs was *awful*

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

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, *technically* we use SemVer (I know, I know...). For that,

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

On 29/11/17 08:47, Daniel Lobato Garcia wrote: > If it helps, I think > https://github.com/blog/2471-introducing-team-discussions looks also > like a good tool for these kind of discussions, without any need for > a moderator. The discussions are restricted to people in the GitHub > team. TLDR:

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

Given 1.17 will have: * vertical nav * rails 5.X I think this is a good candidate, if we're ever going to do it. It's also a good chance to put the woes of 1.16 behind us :) 1.17 hasn't been branched, but it's soon. If we're going to do this, we'll need to decide what should be deprecated.

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

On 29/11/17 09:33, Lukas Zapletal wrote: > Or maybe I miss the main reason why we are not using Github issues at > all? As you said, the last time we evaluated it, it simply wasn't suitable. The situation is more comparable now, however (in addition to BZ link and private issues) I think we

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

On 24/11/17 20:34, Greg Sutcliffe wrote: >> I assume there would be an easy way of subscribing to those tags >> via RSS or email. > > Indeed there is, you can add ".rss" to any category, topic, or tag.. Ugh, writing-emails-when-tired-- Forgot to add, email notifies

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

On 24/11/17 08:56, Lukas Zapletal wrote: > 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

[foreman-dev] Discourse - next steps / actions

Hi all, I'll try to keep this brief, at least by my standards :) Firstly, I think it's clear that the discussion is leaning towards implementing Discourse for at least one, and possibly both, of the mailing lists. Many people have contributed - I'd like to thank them all for keeping this from

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

On 20/11/17 10:08, Lukas Zapletal wrote: > 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 :-) Thanks for the heads up, good to know. I believe Fastly is used by the

[foreman-dev] CDN for the theforeman.org

Hi all, I've signed the contact with our newest sponsor, Fastly, and we now have a CDN available for us to use on our web host. This comes with a single wildcard certificate, so we should be able to use it for all the vhosts on there (yum.tf, deb.tf, etc) Being entirely honest, I've never set up

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

> I will update the direct-category and reply-to addresses (the > foreman.discourse+(token)@gmail.com one) to be correct later today, > but be aware it will break reply-to addresses in existing mails - > sorry, unavoidable but entirely worthwhile. Quick update on the email record stuff. These

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

On 15/11/17 13:58, Lukas Zapletal wrote: > I AM STRONGLY AGAINST *MIGRATING* OUR MAILING LISTS TO ANY KIND OF > FORUM. I have included your opinion in both summaries. As a long standing member of the community, your vote does carry some weight - but shouting doesn't get you an extra one, and

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

+1 to moving them to the Redmine wiki. The RFC repo was a good experiment but handled badly (at least some of the blame for that is on me). At this point I don't think it's possible to rescue it. On 15/11/17 10:52, Sean O'Keeffe wrote: > Without wanting to hijack this thread... I think this is

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

On 15/11/17 07:42, Tomer Brisker wrote: > One concern though is the amount of time it would take We could time-limit it to one hour, and start with "New" issues each time, sorted by oldest first. That way anything we don't get to one week would be present the next week. That's still better than

[foreman-dev] New sponsor slave & Reclaiming a rackspace slave

Hi all, NETWAYS have sponsored us a new 4Gb / 4cpu slave which is now up and running and processing jobs in Jenkins. Thanks guys! I'd like to use this to turn off one of the 4/4 rackspace slaves - that's means net-no-change to CI, but would avoid the small amount of over-spend we currently see

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

On 10/11/17 15:20, Ewoud Kohl van Wijngaarden wrote: > On Fri, Nov 10, 2017 at 02:02:10PM +0000, Greg Sutcliffe wrote: >> To make this a more "official" policy, I've created a "Foreman" account >> on Rubygems, and the user <theforeman.rubyg...@gmail.com>

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

On 10/11/17 14:02, Greg Sutcliffe wrote: > To make this a more "official" policy, I've created a "Foreman" account > on Rubygems, and the user <theforeman.rubyg...@gmail.com> can be added > to any gem we keep on our namespace. This should minimize any issues >

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

On 10/11/17 14:23, Ewoud Kohl van Wijngaarden wrote: > > I like this. What are the opinions on deploying gems through Travis like > voxpupuli does? > > https://docs.travis-ci.com/user/deployment/rubygems/ > > tl;dr: on tags it can deploy the gem to rubygems. It standardizes the > deploy process

[foreman-dev] CfgMgmtCamp 2018 tickets are available

Hi all, Quick heads up, if you're looking at coming to CfgMgmtCamp in February, then the first slice of tickets are now available (and you do need one - they're free but venue space is limited). I've got mine ;) http://cfgmgmtcamp.eu/index.html#registration Greg -- You received this message

[foreman-dev] Discourse - summary of week 1

Hi all, If you've been avoiding the Discourse mega-thread because you're super busy, I hope this summary will be useful. I'll keep it short(ish) and still represent eveyone accurately (I hope). TLDR: cautiously positive overall, some great debate, next steps at the end of this mail Some stats

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

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 of making small changes since our backlog is > big enough

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

On 08/11/17 16:47, Eric D Helms wrote: [tons of useful stuff] Thanks Eric! I think that format will work for us too, might take a little practice. We'll need volunteers to be the runner, ofc ;) On 09/11/17 07:03, Marek Hulan wrote: > I'd join regularly, after few years for which I receive all >

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

Another update on this, almost there :) Threading now apears entirely functional. Ewoud and I ran a private test using Mailgun last night (so as not to spam everyone in case it was still broken). As you can see, in this Gist, it appears to be working in Mutt:

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

So on IRC the idea of a regular issue triage for core issues in redmine came up, and I think it's a pretty good idea. I think we'd want to do this on a public stream (but recorded, I think), and then anyone interested can join. We'd need a minimum number of people involved to make it work, I

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

On 08/11/17 11:12, Ewoud Kohl van Wijngaarden wrote: > +1 on just marking it in README and in the github description. +1 from me too. I can make those changes as an Org owner if need be. Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To

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

On 08/11/17 12:35, 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 > hard to

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

Apparently my arguments aren't coming out coherently - I think we've misunderstood each other on a couple of points... > I'm afraid the amount of time waiting doesn't have any influence on > the feeling if something is big bang or not. Sure, that's not what I was trying to say, I was just

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

Just a quick update on threading, since that's causing the most pain... On 05/11/17 18:51, Martin Bačovský wrote: > - for some reason the threads are not kept together in my Gmail and the > messages from one thread are split into multiple threads even if they seem > to have same subject. I'm not

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

Thanks for returning to excellent debating form :) On 07/11/17 08:50, Lukas Zapletal wrote: > HyperKitty is not just a nice archive, you can easily just use mailing > list as a forum. There are other options like Gmane and others, but I > find HyperKitty as the nicest and smoothest experience.

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

I'll add that I'm planning to attempt the Redmine upgrades once the day-to-day tweaking of the Discourse platform calms down a little. Hoping to get started this week. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this

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

And this is what happens when you edit drafts as new messages. You don't need fancy software to break threading, just a silly mistake will do :) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups

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

On 03/11/17 18:29, Lukas Zapletal wrote: > Greg, I absolutely understand the motivation, Good. However, we're not the only two people on this list, and over-communication is key to reducing misunderstanding in remote relationships. You know me pretty well, but others do not, so I lay my position

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

Update on threading... On 06/11/17 11:43, Greg Sutcliffe wrote: > Thanks for the testing help, Martin. > > * for some reason the threads are not kept together in my Gmail and the > messages from one thread are split into multiple threads even if they > seem to have same subject. I

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

On 06/11/17 13:20, 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. +1 from me, all good candidates :) -- You received

[foreman-dev] PrPRocessor not working correctly

Hi all, PrProcessor appears to have some issues - at the moment it's not applying labels correctly etc. See [1] for an example, labels applied manually, no mention of commit message, etc. Eric has made some changes which we think will help, but if you see other weirdness, please report it here

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

Thanks for the testing help, Martin. * for some reason the threads are not kept together in my Gmail and the messages from one thread are split into multiple threads even if they seem to have same subject. I'm not sure why, it may be because I tuned the account settings. I'll keep testing this

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

Some updates from the weekend testing: * Inbound email should work properly now (community-t...@theforeman.org to start a topic) * A few people have brought up threading - I'll take this upstream once we've isolated the issue (see reply to Martin). It's actually using a fork of the GitHub email

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

One more thought occurred to me while I was out on the nursery pickup, so I'll drop here before I bow out for the weekend. Lukas, I think part of our disagreement is our different goals. As I highlighted in the last mail, users behave differently to devs. These days I consider myself more user

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

Putting what I think is the more important part first ... On 03/11/17 13:30, Lukas Zapletal wrote: > What we are running is a mailing list here. We are running a mailing list *today*, and you're right, I want to change that. This may well be where we simply have to stop and let others join in

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

Thanks Lukas - I wanted a healthy debate, and now I've got one :) This is indeed constructive - you've forced me to go back and examine my starting post more than a few times while writing this. That's a very good thing - we need to be sure of our goal here. There's a lot of good points here,

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

Quick update... A few people have been posting to the users/dev categories on Discourse, so let me quickly clarify - there is no sync Discourse -> List. Anything you post there will not make back to the lists. To help prevent that, for now I've locked those 3 categories. Admins can still post,

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

On 02/11/17 17:46, Matthias Dellweg wrote: > Hi Greg, > so you tested the happy flow. But as a scientist i must ask you, did you check > the opposite, too? Does someone not being the author nor a member of the > mentioned > group not receive the notification? > cheers As it happens, I can answer

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

On 03/11/17 10:32, Lukas Zapletal wrote: > Greg, I have not interest in moving to any kind of web UI. I want to > send another millions of emails, including those "+1". I think we all > agree that any kind of migration must not disrupt way we work today - > a plain mailing-list we all know and use

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

On 02/11/17 18:35, Lukas Zapletal wrote: > 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: >

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

I appreciate I tend to write a thousand words when pictures might do. Here's one shot from the metrics (which may or may not be accurate as it depends on the MBOX importer being correct, but you get the idea), one from the foreman-users list index, and one from the markdown version of this post

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

On Wed, 2017-11-01 at 14:15 -0400, Andrew Kofink wrote: > I admit, I skimmed the prior emails (they were tl). I just wanted to > ask if discourse is searchable/is indexed from the wider internet. > I've often found relevant mailing list discussions by searching from > Google, and I really value

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

That's indeed one of my aims. One common piece of Discourse wisdom is not to have too many categories, so I don't for see one per plugin - but the system also has tags which would work well in the Support category (I.e. foreman-users) A category for Infra might well make sense separate from dev

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

The site will be made public if/when we go live with it. I assume Google will index it then, I don't think it does any robots.txt stuff - certainly I'm using google to look up configuration questions on meta.discourse.org :) -- Sent from my Android device with K-9 Mail. Please excuse my

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

One more point, we're currently on a free tier of our SMTP provider, which is limited to 6k emails / month & 200 mails / day. I'm seeing if I can negotiate a free higher tier for a FOSS project, but for now, go easy on the mail testing :D Greg -- You received this message because you are

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

OK, some questions I expect to come up: * Will the mailing list import be kept up to date? Yes, I plan to update it every day or two. Happily it's incremental (no 7 hour import) but sadly it's not something that's easy to automate. It's also why I've not renamed the categories yet, or fixed

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

Hi all, As ever from me, this is long. Sorry about that, it's a habit. Here's the TL;DR: * What: move Google Groups -> Discourse * Why: https://blog.discourse.org/category/use-cases/ * Can I try? - Scroll to the end for login details So, as some of you know, I'm a big fan of the Discourse[1]

Re: [foreman-dev] 1.17 schedule

On Tue, 2017-10-31 at 13:11 +0100, Marek Hulán wrote: > I think the date is reasonable. Given we have 2-3 RCs per 2 weeks, we > could expect 1.17 release early next year right? Which I think is > good since we'll have time to fix potential blockers after we're back > from Christmas time off. 1.16

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

Hey On Mon, 2017-10-30 at 10:22 +0100, Lukas Zapletal wrote: > After several hours of outage, we were able to bring it up by > mounting the volume in a temporary VM, editing /etc/fstab and > starting new instance. Thanks for the effort, especially on a Friday! > Started new wiki page where we

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

On Thu, 2017-10-26 at 15:53 +0200, Lukas Zapletal wrote: > Ok added me into the list in the post-build action. Cool, trigger a build and see if you get an email :P Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this

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

On Thu, 2017-10-26 at 14:50 +0200, Lukas Zapletal wrote: > 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 :-) I

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

On Thu, 2017-10-26 at 12:58 +0100, Greg Sutcliffe wrote: > I have enabled it, but I can't just see where to add this to my user. > Perhaps someone with better eyes can spot it. If it works it will > remove the need to update JJB so frequently (only for the permenent, > important n

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

Apparently Jenkins could send email before, but I was unaware of it, so sorry if I confused anyone there. In any case, the sending is a little clearer now as a result of my changes (hat tip to Eric for the info). Apparently users should also be able to create their own email notifications. From

[foreman-dev] Matrix.org / IRC bridge

Hi all, Over the past week or so I've been trialling Matrix.org[1] as an alternative to my IRC client. This was partly due to my own curiosity, and partly because a few people keep suggesting Slack (my objections to Slack are, I think, well known :P). Overall I'm pretty impressed with Matrix, at

[foreman-dev] Jenkins can now send email

Hi all, In response to a good idea from Lzap about failed plugin builds being able to email authors, I've enabled SMTP on Jenkins. This is configured via the Email-Ext plugin [1]. The global config (SMTP auth is done) but for defaults, no triggers are currently enabled, so that no-one suddenly

Re: [foreman-dev] Vendorizing or Building RPMs

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 create an SCL, but if it's non- > t

Re: [foreman-dev] Katello Packaging Migration to Foreman Packaging Plan Proposal

On Sun, 2017-10-22 at 21:27 -0400, Eric D Helms wrote: > > Note that this plan says nothing about changing our actual yum > repository structure. That would come later. This is just about > beginning with moving all package management to be centralized in > foreman-packaging git repository. So

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

On Fri, 2017-10-20 at 16:59 -0400, Eric D Helms wrote: > > If there are no objections, I will perform this next Wednesday or > Thursday. +1 -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups

[foreman-dev] [Event] Foreman Community Demo Items - Thu 26 Oct 3pm [BST]

Hi all Demo time! As always, have a think for items which have been completed since the last demo on 2017-10-05. There is a query that will show you items completed (i.e. marked as closed) since the last demo [2]. Please add demo items following the instructions on the agenda page [3]. I will

[foreman-dev] Rackspace ending OSS discount program

Hi all, As of yesterday I received a mail from Rackspace stating that they are ending the OSS discount program at the end of Dec. I have spoken to our Rackspace Account Manager, and there's no offer of some other kind of discount - we'll need to migrate the workload, or pay for the usage. Given

Re: [foreman-dev] foreman_tasks V1 endpoint works but V2 returns 404

On Mon, 2017-10-16 at 22:15 -0700, rajesh.eras...@gmail.com wrote: > # curl --user sledge:hammer -H "Content-Type:application/json" -k htt > ps://ind2q00katello01.qa.local/foreman_tasks/api/V2/tasks/3574500b- > 0394-4a94-9f86-8ff1890ceadb I think this is a character-case issue - it's *v2* not

Re: [foreman-dev] Vendorizing or Building RPMs

On Sat, 2017-10-14 at 14:24 -0400, Eric D Helms wrote: > Note: This is specific to RPMs because as far as I know the Debian > process is different and uses gems directly. Please correct me and > contribute any information with respect to Debian that I miss. I > believe the Nodejs part of the email

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

On Fri, 2017-10-13 at 15:01 +0200, Ewoud Kohl van Wijngaarden wrote: > > I don't see why we would have timeout but I can't investigate that > because I don't have access to any monitoring. There's isn't any really (we should add that to the Infra TODO list). `dmesg` doesn't show any of the

Re: [foreman-dev] Redmine running slowly

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 checked quickly and didn't see any errors, but I was in a hurry :P

Re: [foreman-dev] Redmine running slowly

We're ready to switch. I'll take Redmine offline in about 30mins (11.15 UK time) and we should be back up on the new host at 12 noon. Please save your work ;) Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group

Re: [foreman-dev] Redmine running slowly

On Wed, 2017-10-11 at 21:52 +0300, Ohad Levy wrote: > > > redmine01.theforeman.org A 51.15.192.166 > > redmine01.theforeman.org 2001:bc8:4400:2300::5:e03 > > both should be resolved. Thanks Ohad. SMTP is now unblocked and confirmed working, so we're ready to switch over. As soon as I can

Re: [foreman-dev] Redmine running slowly

Update on migration: http://51.15.192.166 is now live for your testing pleasure, with a copy of the DB from a few days ago. Email is currently disabled, so you can't spam anyone. There's still a few small tasks to sort out that will keep me busy, but if you want to see if you can break it, go

Re: [foreman-dev] Redmine running slowly

Things are no better today, and I'm out of patience with Openshift. I've spun up an instance on Scaleway that should be able to cope and am in the process of creating a copy of Redmine there. Once it's ready I'll stop Openshift, re-import the db and cut over the DNS. Continue to use Redmine as

[foreman-dev] FOSDEM / CfgMgmtCamp 2018 - Call for Presentations!

Hi all, It's that time of year again - the call for presentations for our yearly conference season is now open! FOSDEM - https://penta.fosdem.org/submission/FOSDEM18 CfgmgmtCamp - http://cfgmgmtcamp.eu/#cfp This year is the 5th CfgMgmtCamp, and we want to make it the best yet. So in addition to

Re: [foreman-dev] Redmine running slowly

On Tue, 2017-10-10 at 10:50 -0400, Andrew Kofink wrote: > Me as well. It's quite difficult to work this way. Yeah, I know :( Openshift aren't saying much other than that this is mainly due to the number of people that decided to upgrade to Silver Tier to avoid the sunset of v2. That's putting a

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

Hi all, We're seeing more and more interest in Ansible within the Foreman community, and one facet of that is the ability to deploy Foreman itself using Ansible. That obviously requires a set of resources that use the Foreman API to create/update objects in Foreman. That effort has already been

[foreman-dev] Redmine running slowly

Since the start of this week Redmine has been consistently slow. Console shows very high load (not dropping below 10, often above 20). We haven't chnaged anyhting, so my suspicions are on the v2 sunset that happened at the end of last week. I've opened a support case to see what's going on, but

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

On Thu, 2017-09-28 at 16:51 +0200, Evgeni Golov wrote: > On Wed, Sep 27, 2017 at 7:26 PM, Timo Goebel > wrote: > > ... have you considered using some kind of a CDN for downloads, > > e.g. cloudflare, if traffic is a concern? > > fastly.com is usually happy to sponsor

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

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 a week, no concerns - welcome to the infra team Ewoud :) Greg

Re: [foreman-dev] SmartOS (Solaris 11), Joyent cloud

On Wed, 2017-09-27 at 12:24 -0700, Dmitriy Morozovsky wrote: > Hello dear team. > I see you support Solaris 8,10 what about Solaris 11 or SmartOS > Our big infrastructure based on Joyent Cloud and we looking for > support of Foreman on Solaris 11 As with much of the OS support in Foreman, the

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

On Wed, 2017-09-27 at 19:26 +0200, Timo Goebel wrote: > ... have you considered using some kind of a CDN for downloads, e.g. > cloudflare, if traffic is a concern? > > > I'll see what I can do. The Rackspace billing does provide an > > extensive CSV of all charges (several MB, which for CSV is >

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

On Wed, 2017-09-27 at 17:32 +0200, Michael Moll wrote: > > > This would be PR-blocking, I assume? I'm fine with that, just > > checking. > > While I'm +1 about this in general, the two specific cases for > Discovery > the last weeks were Rails 4.2 -> 5.0 and separation of puppet facts > from

Re: [foreman-dev] Release process & permissions

On 27. Sep 2017, at 16:46, Daniel Lobato Garcia > > wrote: > > > > 2 is to extend http://ci.theforeman.org/view/Release%20pipeline/ > > and make it a real pipeline from 0 to release completed. At this > > moment, releases that are not the first RC1 are mostly automated by >

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

On Wed, 2017-09-27 at 13:46 +0200, Ewoud Kohl van Wijngaarden wrote: > 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 This would be PR-blocking, I assume? I'm fine with

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

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. +1, I'm actually surprised you don't already have it ;) -- You received

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

So, +1 to this idea, we've been lacking in direction for a bit, and a "community roadmap" has been on my agenda for a while. Whilst that's not 1:1 the same as what you're saying, it's related, and planning is a good idea. On Mon, 2017-09-18 at 11:21 -0400, Eric D Helms wrote: > > [1]

Re: [foreman-dev] Bootdisk members (was Plugin gems with a single author)

On Mon, 2017-09-11 at 13:02 +0100, Greg Sutcliffe wrote: > > With no response here, or on various pull requests [1,2] in some > months, would anyone object if I add Lukas and Timo to the bootdisk > plugin on GitHub? They could then review each others work as we > normally do. On

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

On Sun, 2017-08-20 at 16:33 +0200, Timo Goebel wrote: > I'd also be interested in helping with foreman_bootdisk. Although > it's sad to see, it looks like Dominic isn't maintaining this at all > anymore. On Mon, 2017-08-21 at 09:19 +0200, Lukas Zapletal wrote: > I also have some knowledge of

[foreman-dev] Permissions cleanup

Hi all, 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 done a permissions cleanup before, so I thought it might

[foreman-dev] [Event] Foreman Community Demo Items - Thu 14 Sep 3pm [BST]

Hi all Demo time! As always, have a think for items which have been completed since the last demo on 2017-08-24. There is a query that will show you items completed (i.e. marked as closed) since the last demo [2]. Please add demo items following the instructions on the agenda page [3]. If you

  1   2   >