[foreman-users] *** This mailing list is now archived ***
As per previous discussion, this mailing list is now archived. Community discussion and support is available on https://community.theforeman.org. If you still wish to use email, then once you have claimed your account, you can email "us...@community.theforeman.org" to start new topics on the forum. Do check your notification preferences too. For a short time, new posts here wil be seen by moderators and help provided to get you onto the forum. This will switch off in a few weeks, after which emails will bounce. Thanks for your support and understanding during the migration. 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 users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] 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 ;) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[foreman-users] 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 haven't already, you can claim your account using the Forgot Password link in combination with the email you post to the mailing list with. Also, for now, forum nicknames are freely editable - these normally lock after a few days, but I've disabled that for now so that people can change the auto-generated nicknames on the precreated accounts. I will of course give a warning before re-enabling this. Tags have been created, feel free to use them when creating new topics. Groups have also been created, both for you to mention in your posts if you need the attention of those people, and also to join if that part of the codebase / plugin is of interest to you. I've had no comments so far on the documentation, so I assume it's doing it's job. Feedback is still very welcome on that of course. I'll be spending this week preparing the PR to the website to remove mention of the mailing lists ready for Sunday night. Almost there. See you on the other side :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
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 capability * Tags are now created, please do use them where appropriate * "Solved" plugin is available if you want to mark solutions in Support * Introductory notes and issue template updated I'm still looking for feedback on how well the signposting works for a new user. Let me know if you have thoughts. In the coming week I'll be adding the Groups that you can join (if you wish to be notified when certain parts of the ecosystem are being talked about), and updating our Infra docs on the Discourse hosting. I'll also be preparting a PR to the website for removing mention of the lists (this will not be merged until the 31st). So far all is looking pretty good. I'll update again in a week (yes, I know that's Christmas Eve, I have no life :P) Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[foreman-users] ACTION - Foreman will move from Google Groups to Discourse on 1st Jan 2018
Hi all, TLDR - the mailing lists will be switched to read-only at the end of 31st Dec, and from 1st Jan, we will be moving to Discourse [0]. Message me on the forum at [1] if you have questions. # What's happening? As you'll all be aware from previous mails [2], YouTube content [3] and the newsletter [4], we've been debating for about a month on moving to a forum for our community interaction. That debate has run it's course, and the conclusion is clear - a move to Discourse is popular. Accordingly, I am now setting in motion the plan for the migration [5]. Today, I'm notifying all 3 lists that they will be switched to read-only on 31st Dec (3 weeks away). # What do I need to do? Firstly, claim your Discourse account (if you haven't yet) - if you've ever *posted* to the mailing list, then you already have an account, and can use the "Forgot Password" option on your email address to get logged in (or use GitHub login, if the email is the same there). (If you're a lurker and have never posted, then you'll have to create the account yourself, sorry. Don't be shy though, now's a good time :P). Once logged in there's an FAQ banner at the top to help you get started (with links to more in-depth topics), and Discobot (the forum bot) will message you with some tips too. You can dismiss the banner with the "X" once you're done with it. Any questions, you can send a message to me [1] on the forum and I'll respond as soon as I can (using the forum helps me collect them into an FAQ). If you prefer, you can also post in the "Site Feedback" category. # What happens next? During the next few weeks I'll be tweaking Discourse to suit our needs (groups, tags, settings, etc) and writing docs to help orient new users. I'm *very* interested in hearing from the first few users who jump on about how easy to find the docs are, and how helpful. I'll also be updating the Google Groups web interface with a deprecation notice, and preparing PRs to the website to point new users at Discourse. If you spot anything where we can improve sign-posting for people, get in touch [1]. The lists will remain functional for now, but I would encourage people starting *new* threads to consider using the forum. The entire list archive will be merged to the forum, so nothing will be lost, but it means you get a head start on getting used to Discourse, we can help you get oriented, and you can test our docs (and thanks for that!). Do hang tight, I'm sure *something* unexpected will come up - but we're shooting for the quietest time of year, and once we're up and running, I think this will be good for all of us. More updates will follow in due course :) Regards, Greg "Gwmngilfen" Sutcliffe Foreman Community Lead 0: https://community.theforeman.org 1: https://community.theforeman.org/u/gwmngilfen/ 2: https://groups.google.com/d/topic/foreman-users/XXSETIlScX4 3: https://www.youtube.com/watch?v=IdV6US_d4-U 4: https://theforeman.org/2017/11/foreman-community-newsletter-november-2017.html 5: https://community.theforeman.org/t/migration-plan/7550 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [foreman-users] Unable to install Foreman on my puppet master server.
On 05/12/17 12:37, Diego Lucas Jiménez wrote: > That's the version Foreman deploys with their repo. > foreman-installer (1.5.1-1) > Both in Ubuntu and CentOS. Just follow the how-to in their webpage and > that's the one you'll get. We can't be held responsible for how-to's that we didn't write. All documents on the internet tend to age fast. 1.5 is over 3 years (and 11 major releases) out of date. > Where can I download the latest version? We always recommend using *our* documentation and quickstart guides for new installs. You should start at https://theforeman.org and click the Quickstart link at the top. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Discourse - story so far, and some dates
Hi all, Over the two weeks, we've opened up a debate into whether a move from the mailing list to a forum (Discourse) would makes sense for the community. You can read the previous thread here: https://groups.google.com/d/topic/foreman-users/XXSETIlScX4/discussion There's also an AMA recording if video is your thing: https://www.youtube.com/watch?v=IdV6US_d4-U # So what's the result? The TL;DR is that this looks very likely to happen at this point. The debate has been strong, but we've seen a clear preference for a forum win out over a mailing list. In addition, we started a discussion about whether to move *only* foreman-users, or to include the development list, foreman-dev, as well. If having a view of the development discussions has value to you (or doesn't!), then there is a poll open on Discourse right now: https://community.theforeman.org/t/poll-which-lists-should-migrate-to-discourse/7598 There is still time to contribute to either the poll or more generally to the debate, though - I plan to take a final decision at the end of next week (Thu 7th). Please do let your views be known :) # What happens next? Unless there is a huge change in mood in the next 7 days (seems unlikely), then Discourse is going to happen. I'll write more about how the migration will happen next week, but for now here's a few dates: Thu Dec 7th - conclude polls and state decisions regarding list(s) Mon Dec 11th - T-3 weeks -> initiate migration plan Sun Dec 31st - at midnight (or close to it) migrate the list(s) One month to go, New Year, new tools. Should be fun :) Thanks! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Feedback wanted - migrate mailing lists to a forum?
On 24/11/17 09:00, Lukas Zapletal wrote: > If folks would not mind, I'd like to change that to something > reasonable. Here is what I propose: I will file a patch to Discourse > and we can apply it onto our instance immediately as I expect longer > discussion (perhaps an option or they might not like it at all). I'm OK with that, customization is fine. I think the obvious starting place is tha macros used in the email templates. I'll take a look at where they're defined next week, maybe we can tweak it, or maybe there's even one defined that's better for us... Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [foreman-users] Feedback wanted - migrate mailing lists to a forum?
On 22/11/17 11:42, Marek Hulán wrote:> > Yes please, editing feature feels odd to me. When you read the thread > later, it can be very confusing. Especially if we don't get email > notifications about the edit. Done. > Just to minimize the risk this could happen, I think it would be > reasonable to run discourse and users mailing list in parallel at > least for month. So Ohad already made a good point about roll-forward - given we would want to minimize disruption to users, any future migration would be to something where we could re-use the "users|d...@community.theforeman.org" addresses. We'll never be returning to the Google Groups mailing list anyway. On the above basis, I'm not sure what risk we're minimizing by running the two in parallel. The risk of Discourse not being right for us is still present, and the need to migrate to something new is still present. > We could change all links on our web sites to mention only > discourse, we could include the scheduled shutdown information to > every reply on mailing list but just to be cautious We generate a lot of work for ourselves this way. In addition, I can't finalize the import process until all the posts are migrated, so that's more work maintaining the importer, and also we can't merge duplicate users. The importer also blocks outgoing mail for about 6 minutes when it runs, so there's (small) chance that email notifies could fail if a post is created while the importer is running. This is all avoided if we can be done with the importing at migration-time. So instead, I would suggest that we use [1] (second part about blocking), but instead we moderate (not block) all new posts, and make the very last visible post to the list be the final migration notice (as well as updating the group description of course). We can migrate moderated posts to Discourse behind the scenes, and tell the user where it went. These posts will never appear in the mailing list, so the importer isn't needed. Even then, that's additional work (probably done by me, if we're being honest :P), so I'd only do that for a week or two at the most, just while people orient, and then block the Google group entirely. > we should not drop the existing list until we're sure discourse works > for us. I don't know if it *ever* makes sense to delete the Group completely, as that removes the web archive too, but we can decide that much later on. Hope that makes sense, Greg [1] https://support.google.com/groups/answer/2646833?hl=en_topic=2458761 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Feedback wanted - migrate mailing lists to a forum?
On 23/11/17 14:16, Lukas Zapletal wrote: > Thanks for answers, as long as you will keep pushing changes upstream > and try to solve some of my concerns, that'd be fine. Thanks for being understanding, nothing is going to be perfect for everyone. Of course we'll do our best to get changes where we think they're needed, that's one of the great values of FOSS :) > The most annoying is the big blue button for me, I'd prefer some > small light-gray link instead (if any). As I say, I only see that in HTML-view, are you definitely in plaintext mode? > I understand that's only my personal preference, you could possibly > push this upstream as user-configurable option. I see you started a thread, I'm watching it for replies. If anything comes up that we can use, I'll act on it, sure. > Not being able to reply to myself is not huge deal as you can merge > threads which are mis-posted that's fine. It also doesn't seem very common, looking through the archive, so manually fixing it seems like the way forward, for sure. > Bringing possibility to edit posts down to 5 minutes seems like a > reasonable solution, still allows you to quickly fix mis-formatting > but makes sure people are not doing crazy edits afterwards. Done. > Re nabble - I tried to integrate a test archive, created an account > but it did not work - mails did not show up (although they were sent, > I was receiving copies). Ah that was you, I did wonder :). Sad that it failed - but I'm totally ok with an archive of some kind, we can work out the details as part of the migration plan, for sure. Thanks for suggesting it. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Feedback wanted - migrate mailing lists to a forum?
Heya!
Answers in-line, but I wanted to put a quick summary here for folks in a
hurry. Most, if not all, of these questions are *technical* in nature -
they are things we can alter, either by existing settings, or by
altering the Discourse code. I see this as similar to our Redmine
instance - we've taken a FOSS tool and customized it to our needs, both
via code changes and plugins.
More generally, though, your post reads as a direct comparison to a
mailing list, and as I said in my opening post, I don't think a mailing
list is right for us anymore.
I'm not trying to mislead on this point. The mailing list mode that
Discourse offers *is* different, yes, so a direct comparision is likely
to find flaws. The real question is whether the *other* things it does
are worth the cost. I know (from our chat on the dev list) that you
don't agree with my conclusions about our needs as a community, so we're
going to end up differing on whether it's worthwhile.
If we migrate, then some "getting used to" is going to be needed, for
sure. A balance of tweaks vs change-acceptance will no doubt be found,
some of which I expect to be altered *after* we migrate. We don't have
to set *everything* in stone on day 1 (and that flexibility is one of
the things I like). Some things may be possible to do per-user, which is
even better (again, flexibility to interact with the community as each
user wants to).
OK, specific answers:
On 21/11/17 15:09, Lukas Zapletal wrote:
> 1) Edits are not propagated to e-mail only users, I edited a post
> andnever got an e-mail about this.
> 5) Email response is slow, I know there is some polling, but this is
> simply limiting and web users are inadvantage as they see the
> content earlier.
There is no polling now, that was temporary. Inbound email is instantly
visible in the UI.
Outbound email is delayed 5 min so that people have a chance to spot
typos, missed links etc in their posts (in the UI ofc) before the emails
are sent. I really don't think 5 minutes is a big deal, a quick scan of
our lists suggests average response time is Order(hours) - to claim it's
a disadvantage seems a bit of a jump. It seems an acceptable tradeoff to
get allow posts to be correct when sent in the first place, cutting down
on "oops, forgot the link" style followups.
As for editing, there is a limit on the length of time you can edit your
posts, currently that seems to default to 60 days (seems too high to me,
for sure). I guess we could set it to the same 5 mins as above, so that
no editing can be done after mails are sent, if this is a significant
concern for people.
> 2) It seems you can't reply to yourself via email, this often
> happens if you need to correct yourself.
This needs some context for those following along, and it's actually a
security thing.
This only happens when you reply to yourself by hitting "Reply" to the
mail in your Sent folder. In this case you'll be sending a second mail
to "someth...@community.theforeman.org" instead of
"reply+{token}@community.theforeman.org", which by default will create a
new thread.
I say "by default" because there *is* a setting to allow this, but the
consequence is that it then allows sender-spoofing to occur. Discourse
sends a different reply token to every user, so your reply-to address is
different to mine even for the same post, and Discourse requires the
"From" header to match the token. Unless you have my token, you can't
spoof-post things pretending to be me. We can disable this, but that
means sender spoofing is then possible. Details at [1].
So, we could enable this setting, but there are also other workarounds -
enabling "Send me my own posts" in mailing list mode will mean you have
something to reply to with a token (albeit after 5 minutes), and
moderators can also merge split threads back together in the UI. As
such, I'm inclined to leave it as it is, but we can flip that setting if
it becomes a problem.
> 3) All emails contain huge button to visit the thread
I see you're already asking about this upstream :)
Templates are editable, yes. That said, they seem fine in my client [2],
pretty much the same 3 lines Google Groups adds. Would love to see what
other plaintext readers get.
> 4) Does not support text/plain emails,
Again [2], plaintext in Thunderbird seems OK here.
The plaintext version is the raw markdown from the post, which has
some quirks, admittedly - I've opened [3] to discuss options there - but
largely I've been getting nice emails from it. Could be MUA specific (I
am reminded of the quote that there are no good mail readers, only some
that suck less than others :P).
> Now, on a different topic, with possible migration we will likely
> loose 3rd party archives.
I have no idea if it was deliberate action by someone (wasn't me), but I
saw that Nabble has already created an account on our instance [4]. Not
sure where that ends up yet, though, will investigate. As you say, it's
entirely solvable. I've added it to the Draft
Re: [foreman-users] Feedback wanted - migrate mailing lists to a forum?
On 16/11/17 17:16, Greg Sutcliffe wrote: > Next week I will hold an Ask Me Anything on our YouTube channel, and > you're welcome to come ask your questions. As promised, I've now scheduled this on our YouTube channel. You can join live on the day at: https://www.youtube.com/watch?v=IdV6US_d4-U This will be a good opportunity to put concerns forward, ask for details on possible migration paths, or just help get yourself oriented in Discourse so you can decide if you like it. If you can't make it live, do leave questions in advance for me - I've already got plenty of material, but I'll be happy to have more :) Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Build Token expired - what is it for and how to configure it ?
On 16/11/17 14:06, Neil Hanlon wrote: > Hey! Great question. > > The "Build Token" is (to my understanding) essentially there to keep > your servers from boot-looping when you PXE/network boot them. Actually that's not quite true. Sending a GET to /unattended/built is what breaks the boot loop, but it'll work without a token (if you set token_duration to 0 they aren't added to the URL). Tokens exist to identify hosts. In the past, we identified a host by the incoming request IP on the GET - but this doesn't work if you're on a NATed connection from another subnet. In that scenario you only see the incoming IP of the gateway machine. Tokens were added as a way to combat that, and eventually became the default because it's more reliable. On 17/11/17 07:57, andpk wrote: > Hey Neil, thanks for your answer and explanation of the build token. > > i try just pasting the phone_home variable in my user_data template, > but it seems that it has no affect on the build token. After the last > puppet apply it still said: > > It contains just VMware customization settings and in the end the > phone_home. Did i misunderstood something? It's worth knowing that VMWare customization-spec isn't a 1:1 mapping to userdata - it's extremely restrictive, and many people have had problems getting the phone-home bit to work. Searching the archive will find you some hits on the topic, but I don't know exactly home to make it work, sadly. Maybe someone else does. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Feedback wanted - migrate mailing lists to a forum?
Hi all TL;DR lets migrate to Discourse (forum software, self-hosted). I hope you'll read the rest of this mail though :) This is a big proposal. If you prefer audio/video to huge posts, I've also put some of my thoughts in the latest community demo: https://youtu.be/QHzNIFjMpTM?t=2103 (12min watch) # Not confirmed, only a proposal so far Lets get the important bit out of the way first - this is a *proposal*, it's is not guaranteed. No final decision has been taken. I'm posting this to get feedback from the community about whether it's a good idea, and I really (really really) want to hear what you've got to say. # What am I proposing? I want to migrate our mailing lists to a self-hosted Discourse instance. We have that Discourse instance set up, you can go play with it right now (see below for details). I want everyone to try it out, and tell me your thoughts. # Why do we need this? Let me start with a graph: https://imgur.com/a/jjPJI This is the volume of mailing list posts (users, dev, and the totals) over the last 6 years, grouped by month. As you can see, that traffic has been declining for the last 2 years, and that's a trend I also see in the IRC data too. This worries me. For some time now, I've been wondering if a mailing list is the right fit for our needs as a community. Times change, and I believe there's a significant group of people that would be willing to be part of our project, but do not want to join a list. In modern times, people expect a UI, and are more comfortable there. This is a thought I have heard repeated from other community members too, so I'm not alone. Specifically though, why a forum? I'm proposing we use Discourse, so let me link to https://blog.discourse.org/category/use-cases/ and pull a few examples out (in no specific order) * Easier for new users to get started withClean and simple interface * Better search and search engine indexing * Post creation tries to be helpful, suggesting similar topics * Markdown support * Category-level subscriptions * Browser & phone push notifications for new posts * Community digest by email & “unread” on the web (for those who can’t keep an eye on the web site all the time) * Converting a post to a wiki post, so everyone can edit it * Group-level notifications Broadly, a forum gives us both many new features out of the box, plus flexibility for the future. This post is long enough, but I went into much greater detail in my post to foreman-dev a few weeks ago, please do read it if it interests you (and maybe come to the AMA next week): https://groups.google.com/d/msg/foreman-dev/xSS1mNKpRQg/uFSmDNK6CAAJ # I like mailing lists though Discourse does offer a "mailing list mode". I'm not going to try and sell this to you as a 1:1 replacement for a mailing list, but the main features in terms of creating new topics in by mail, receiving new topics by mail, and getting/replying to new posts by mail should all work. Threading is there too, so the basic functionality should work fine - but I'd love to test this more. Setting up mailing list mode is covered in my intro notes to Discourse notifications here: https://community.theforeman.org/t/configuring-mail-notifications/7513 Is it a perfect replacement? No. Is it a worthwhile tradeoff? You tell me :) # How do I help test this? Glad you asked. Start at: https://community.theforeman.org Everyone who has ever mailed foreman-users or foreman-dev already has an account (importing the lists creates those users) but all outbound email is disabled by default so we don't spam people. To recover your account, simple log in with your mailing list email address, and then hit Recover Password. If you're a mailing list lurker (never posted) then you won't have an account yet - never fear, signups are available, or you can log in with your GitHub account. Once logged in, you'll be shown my FAQ to help orient yourself, and you can visit the docs for configuring mail (see above) # What's next? Nothing immediately. Next week I will hold an Ask Me Anything on our YouTube channel, and you're welcome to come ask your questions. Obviously questions are welcome here too, and you can email me privately (or private message @gwmngilfen on Discourse :P) if you like. After some time - exactly how much depends on how quickly we get feedback - we'll be able to take a look at the feedback so far and come to a decision. I absolutely do *not* want to rush this - I want to listen for a while first. It's a big change, and we need to get it right. I very much hope you'll join me on the expedition to the future. Change isn't easy, but I genuinely believe we need this. Let me know your thoughts! -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this
Re: [foreman-users] Foreman n00b having startup issues
On 14/11/17 09:27, Marek Hulán wrote: > also based on your Foreman version, the SCL might not be tfm, in that case I see "/opt/theforeman/tfm" in the stacktrace, so I'm guessing that will be the correct SCL. As marek says, you need to ensure the gem is available in the packaged Ruby, rather than the system Ruby :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Automatic OS installation in openstack instances using Foreman
On 11/11/17 04:31, hf2548 wrote: > Thanks for your answer > I can install OS in physical machines using Foreman automatically, I want > to know how to do this with virtual machines created y openstack. Small caveat, Openstack frequently moves faster than we do, so this *may* be broken. In general though, you can add your OpenStack instance under Compute Resources > New in the UI, and use your tenant credentials to set up the CR. Once you have a CR, it'll appear under Deploy On on the New Host form. You can select your openstack instance there and then configure the new host as normal. If yout hit any errors, please do share the logs and what you were doing so we can investigate. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] hammer wildcard
You could even use hammer with one of the output formatters, and loop over it. Something like "hammer --csv host list --hostgroup GCE" would get you the starting list of hosts to loop, then a call to this API (don't think hammer has last-report): '/api/v2/hosts//reports/last' | json_pp | grep "reported_at" would give you the last report date. You could compare those to $now and then call "hammer host delete --name " if it's too old. *OR* consider using the expire_hosts plugin, which if you're just concerned about cleanin up old hosts, might be exactly what you want. See https://github.com/theforeman/foreman_expire_hosts Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Automatic OS installation in openstack instances using Foreman
On 08/11/17 10:55, hf2548 wrote: > Hi > I'm new to Foreman. I read that we can manage openstack in foreman using > staypuft (I don't test it, yet). Staypuft has been dead for a very long time, as far as I know. Certainly no commits have been made upstream in over 2 years. There are guides out there for deploying openstack from Puppet in general, I'm sure those Puppet modules can be used from Foreman once you've set Foreman up. > But I want to know that can we automatically install OS in openstack > instances using Foreman or not? If yes, how? Do you mean the physical undercloud, or the virtual machines? Both can be managed from Foreman, but the answer is different depending on your goal. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] 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 because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Forman API: How to get "Reported at"
To follow up on that, the Reported At field is a property of the host in Foreman, it's not a fact. It's the time Foreman last received a report from Puppet (or Chef, Ansible, etc) about this host. You can get the last report for a given host using something like: $ curl -k -u user:pass 'https://topaz/api/v2/hosts//reports/last' \ |json_pp | grep "reported_at" Hope that helps. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: Foreman scalability -> 100k+ nodes anyone?
On 03/11/17 09:49, Greg Sutcliffe wrote: > On 01/11/17 22:25, ilya m. wrote: >> Dear foreman users, >> >> I've recently joined foreman users group. > > Welcome indeed! One extra fact that may be useful is that the majority > of Katello devs are on US-east-coast time, so if you hop into chat[1] > then you'll probably be able to get real-time help. Or keep asking here, > ofc :) Sigh, I need more caffeine, helps if you add the link: [1] https://theforeman.org/support.html#IRC -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: Foreman scalability -> 100k+ nodes anyone?
On 01/11/17 22:25, ilya m. wrote: > Dear foreman users, > > I've recently joined foreman users group. Welcome indeed! One extra fact that may be useful is that the majority of Katello devs are on US-east-coast time, so if you hop into chat[1] then you'll probably be able to get real-time help. Or keep asking here, ofc :) On 03/11/17 02:32, Andrew Schofield wrote: > Be careful with what you as expecting the capsules / smart-proxy to > offload all the load from the master isn't as you might think. There are > a lot of things which simply use the smart proxies as, well, a proxy > hence just feed the request directly to the master (subscriptions, > puppet fact / report / catalog processing etc). All the preceeding is good advice, but related to this, it's worth knowing that you can also cluster the Foreman core. A DB cluster and bunch of app boxes, with something like memcache to store Rails state, is possible, or just separate app boxes for different purposes - I know one large deployment which had a dedicated box for reports/facts/ENC and another for the users to interact with. Let us know how you get on Ilya! If it goes well, maybe we can do an interview or blog post on it ;) Greg Community Lead -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] How to write Puppet Classes used by Smart class parameters from Foreman
Hi anpk
On 01/11/17 11:08, anpk wrote:
> Good evening,
>
> iam relative new to Foreman and also to Puppet.
Welcome to the community!
> In the past i always write very simple puppet manifests and just apply
> them. Now i want to use the "Smart class parameters" from Foreman for
> example, setting the version of a software who will be installed. I play
> a little bit with smart class parameters by some puppet forge modules,
> look a bit at the code, but i still dont know how to write puppet
> classes who can be used as Foreman Smart class parameters.
>
> Are there some simple examples? Or what i must use from the puppet
> features wich are interpreted as Smart class parameters?
> i didn't see the forest for the trees :-) ...
We have some docs for this:
https://projects.theforeman.org/projects/foreman/wiki/Parameterized_class_support
It'll work for any Puppet class with parameters, so for example:
class test ($foo="bar") {
file { '/tmp/test.txt':
ensure => present,
content => $foo
}
This is a class that has one parameter, foo, and writes that parameter
to a file. If you put this in your modulepath, and Import classes into
Foreman, you'll be able to see the "test" class in the UI.
Once you can, edit the class, go to the "foo" parameter, and try setting
a default value, and assign the class to a host. It should pass the
value to Puppet (you can check on the hosts YAML page). After that, you
can try overriding the default at the Host level.
Here's a very old video walking through the process, it hasn't really
change much:
https://www.youtube.com/watch?v=Ksr0tilbmcc=youtu.be
Hope it helps,
Greg
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 26 Oct 3pm [BST]
In case you missed it, this was recorded last week. In the demo we took a look at the deb support for Katello, contributed by the good people of Atix AG, as well as a bunch of plugin and UI updates. I also spoke a bit about future community & infrastructure plans. Enjoy! Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/VpdRVZvx0jo?t=0 * 3rd party JS for plugins (oprazak) - https://youtu.be/VpdRVZvx0jo?t=388 * Vert nav updtes (afeferku) - https://youtu.be/VpdRVZvx0jo?t=656 * Notifications close (sharvit) - https://youtu.be/VpdRVZvx0jo?t=930 * Dynflow queue & workers (aruzicka) - https://youtu.be/VpdRVZvx0jo?t=1062 * Deb support in Katello (mdellweg) - https://youtu.be/VpdRVZvx0jo?t=1205 As always you can ask questions here in the comments, or on the mailing list, or in our IRC channel - presenter IRC names are in the notes above! Website: http://theforeman.org IRC: Freenode/#theforeman Matrix: #theforeman:matrix.org Twitter: @ForemanProject Mailing List: https://groups.google.com/forum/#!forum/foreman-users -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Matrix.org <-> IRC bridge for the Foreman community
Hi all, Over the past 2 weeks 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 least enough to try it out within our community. The rooms are "plumbed-in" to the IRC rooms, so it doesn't matter if you're on Matrix or IRC, you'll see the same content (and not via a single 'bot' account). Indeed, I've been on a Matrix client for the last 2 weeks and only a few people have noticed, I think :P. A few other good points to Matrix: * Open source (of course :P) * Federated (but our channels are on the main matrix.org server anyway) * Persistent by default (for all you people without IRC bouncers) * End-to-end encryption available for private chats * Plenty of clients (Riot.im is nice, WeeChat plugin for CLI, etc)[2] The only downside I can see is that only registered IRC users can private-message a Matrix user - unregistered users get a polite message about need to register first. This doesn't apply to channels, only PMs. I don't feel this is too bad, registering to IRC is trivial, and most support should happen in the channels anyway. I'll stress that there is *no need* to change anything if you're happy with IRC, those channels are not going away. But if you've been itching for something a little more shiny, or just an easy way to have a persistent connection to chat, Matrix may be of use. If you do hop on Matrix, I'm @gwmngilfen:matrix.org, and the Foreman channels [3,4] are in the public Room Directory. [1] https://matrix.org/ [2] https://matrix.org/docs/projects/try-matrix-now.html [3] https://riot.im/app/#/room/#theforeman:matrix.org [4] https://riot.im/app/#/room/#theforeman-dev:matrix.org Enjoy! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part
Re: [foreman-users] Re: "No templates were configured" for image builds?
On Tue, 2017-09-12 at 08:11 +0200, Ivan Necas wrote: > In order to be able to assign the template to the OS, you need first > go to the template's associations tab, and add the OS there. > Then it should make it possible to set that in the OS. > > I'm not sure why the default user_data template is not cloud-init, > but I deffer the question to someone else. Ivan, for your education :P - user-data comes in two flavours, that's all there is to it :D The first is cloud-init style specfications which are acted on by a variety of providers on the image. The second is a shell script executed as root by the cloud-init process as it boots. You can find out more here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html#user- data-shell-scripts Mike - so, I'm glad your EC2 instances are working, since that's what I'd hope. However, as Ivan noted, the VMware customization spec is *very* limited, and many people on here have had issues getting it to work. THis is sadly a limitation VMware chooses to place on itself, and there's not much we can do about it (except get VMware customers to pressure them to change it :P). Here's a link from a while ago from someone who says they got it working: https://groups.google.com/d/msg/foreman-users/d6Yc9uiK9oo/RZ9I MPo9AwAJ. In general, search the list for "vmware customization" should get you a few otehr hits too. Hope it helps! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] AWS EC2 with Foreman
On Wed, 2017-10-25 at 15:39 -0700, steved0ca wrote: > I was seeing this on 1.15.4 and upgraded to 1.15.6 with the same > results. > > For some reason image based deployments that have userdata enabled > also require a finish template associated. That's a bug if it's reproducible, as Foreman cannot use both for a VM creation anyway - they're mutually exclusive. If the user-data flag is set on the Image then it can only use that template. > This leads to 1 of 2 outcomes: > > 1. as Ivan stated, the host creation UI throws this error and a > cannot proceed > 2. as a workaround, a finish template is associated, but if VM is > being deployed with a non-root user (ie 'centos' for Centos > instances) the provisioning cannot be completed via SSH as the wrong > user is trying to login to run the finish script. This happens even > if the image is configured with user 'centos': There's two things here. That it is attempting to use the finish template suggests the user-data flag is not set on the Image, or not working. The choice of user & password for an SSH-based image, though, is configurable in the Image (in the edit page). Note when I say Image, I'm talking about the object in the Foreman UI that is linked to the AMI, not the AMI itself. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman - Solaris 11 install
On Mon, 2017-10-23 at 16:14 -0700, Trisha Hoang wrote: > Hello Foreman users, > > From my understanding, there is no support for Solaris 11 install on > Foreman. Not sure if the reason is that Solaris 11 has its own > automated installer or if there are technical challenges. Lukas is doing a great job of helping you out, so I'll just answer this point... Much of our OS support comes from the community, so it's up to people like yourselves to contribute it. The core development team only has so much time, after all. The reason we have no support for Solaris 11 is as simple as no-one has written it yet :) If you'd like to contribute your patches as a pull request once you're happy with them, please do! Thanks Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] How to display IPMI consoles in the Foreman?
On Thu, 2017-10-26 at 17:37 +0200, Konstantin Lepikhov wrote: > > You need to replace novnc js code in foreman by js code from kelleyk > version + modify foreman host controller. Then you can connect > to servers's bmc ikvm via foreman's websockify. > > Another thing - extend host inventory adding properties related > connection/bmc_type. This sounds like an excellent thing to send a patch for, if you're interested - or at least log a feature request with some tips on wiring it up. Then it can be available for everyone :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] DevConf.cz Feb 2018 - Call for presentations
Hi all, If you're planning your travel for early next year then DevConf.cz is one to add to your list. Foreman will be there in some form (hopefully with a booth & swag :P), and we'd love to meet you. If you are planning to go to DevConf, ou could also consider adding a Foreman talk to the CFP - just head to https://devconf.cz/cfp to do so. See you there! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman upgarde 1.8 to 1.9 - roll back and
On Mon, 2017-10-09 at 09:59 -0700, Kishor Ramanan wrote: > > I have the following questions > 1. How do I roll back an upgrade process? You can't, schema changes are made to the DB as part of the upgrade. Take backups, as per our docs [1] > 2. Should I upgrade the db also? Do you mean the version of PostgreSQL / MySQL or the schema of the Foreman database? For versions, that's up to you, but I'd always encourage keeping up-to-date. The Foreman DB will be updated as part of the Foreman version upgrade. > 3. Which command do I use to check the foreman version Your package manager will report it (rpm -qa |grep foreman) or you can check the About page in the UI. > 4. Any common issues associated with upgrade of foreman 1.8 to 1.19 should be fine, but note these versions are well over 3 years old now - 1.15 is the current version. You may want to make plans to upgrade further. Greg [1] https://theforeman.org/manuals/1.15/index.html#5.5.1Backup -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman 1.15 with Puppet5
On Mon, 2017-10-09 at 07:32 -0700, treydock wrote: > Is anyone running Foreman 1.15 with Puppet5 or does anyone from > Foreman have any comments on the compatibility? As far as I can tell > the support for Puppet5 was mostly centered around the puppet modules > used by Foreman Installer which I figured I could just update in my > r10k Puppetfile. Having looked at http://projects.theforeman.org/iss > ues/15096 it also looks like the proxy got some changes to support > querying classes. I don't import classes into Foreman so I'm hoping > the path to support Puppet 5 with Foreman 1.15 is just updating to > latest puppet modules. As far as I know, ugrading to Puppet 5 on an existing server is entirely fine. Our *official* support comes with 1.16, but so long as you don't want to run the installer, anecdotal evidence is that all is fine. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: Install on Fedora 26 failed
On Sun, 2017-10-15 at 23:27 -0700, c.j...@graphique-alliance.com wrote: > Hi, > > I'm used to Fedora distros. BTW i could also install on Debian 8, but > Debian 9 is here and IMO if you're supporting a distro, you should > also support upcoming release. Debian 9 support is available in Foreman 1.16, for which Release Candidate 1 is already available. We expect RC2 shortly, and we'd love reports > If Centos is going to be the only supported distros for foreman > installer, docs should be updated to say so. It isn't, and both Debian & Ubuntu remain supported, but be aware that it takes time. 1.16 is the first Foreman release since Stretch came out, so it couldn't have been done any earlier anyway. 1.16 sadly was delayed due to technical issues in the nightly builds, but it shouldn't be much longer. For Fedora, we generally have conflicts between how they package Ruby and how we do things (that is, we use an SCL to contain the Ruby stack, which Fedora does not). That means we can only release for Fedora on the magical periods where the Ruby/Rails stacks align - otherwise there are conflicts. Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] 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 the usual developer updates, new plugins, and community news talks, I'm very keen to hear from *users* - that's you! Submit your success stories (or horror stories!), things you learned in the trenches, or interesting ways you've put Foreman to use, and we'll make sure that the users get a voice in this years Foreman track. See you there! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Lots of "Mysql2::Error: Deadlock found when trying to get lock" under increased load
I've not seen that, no - I've CC'd someone who might know ;) Greg On Thu, 2017-10-05 at 18:35 -0700, 'Konstantin Orekhov' via Foreman users wrote: > > Let us know next week if this helped. I highly suggest upgrade to > > 1.15, it is a very solid release. > > > Are there any performance improvements for Smart-Proxy in 1.15, BTW? > > Lately, in one of my busiest locations, we've started seeing a > strange issue when SmP stops responding on 8443 for API calls. The > process itself is running, logs messages are logged, just no response > from it: > > [root@spc01 ~]# systemctl start foreman-proxy > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs https://localhos > t:8443/bmc; date > Thu Oct 5 17:53:36 MST 2017 > curl: (7) Failed connect to localhost:8443; Connection refused > Thu Oct 5 17:53:36 MST 2017 > > It does take ~30 seconds to start up in our env because of large DHCP > dataset, during which the connection would be refused. > > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs https://localhos > t:8443/bmc; date > Thu Oct 5 17:53:49 MST 2017 > curl: (28) NSS: client certificate not found (nickname not specified) > Thu Oct 5 17:54:19 MST 2017 > > Then it starts working for a very short period of time (above) and > then stops (below). > > [root@spc01 ~]# date; curl --connect-timeout 30 -kSs https://localhos > t:8443/bmc; date > Thu Oct 5 17:54:24 MST 2017 > curl: (28) Operation timed out after 30001 milliseconds with 0 out of > 0 bytes received > Thu Oct 5 17:54:54 MST 2017 > > So far there's nothing in proxy.log that helps me identify the issue. > I can't replicate it at will no matter what I do - had a bunch > clients hitting different APIs for a couple of days, nothing. > Then today the above happens and the only thing that helped me is to > move SmP from one node to another (I really wish DHCP SmP would allow > for active/active horizontal scaling instead of just being limited to > a single node). > Strace is useless as it only give this on tracing "ruby foreman- > proxy" process: > > [root@spc03 ~]# strace -p 12526 > strace: Process 12526 attached > futex(0x184e634, FUTEX_WAIT_PRIVATE, 1, NULL^Cstrace: Process 12526 > detached > > > I tried https://github.com/tmm1/rbtrace, but it is so heavy that it > actually pretty much kills SmP by itself. > > Do you have any suggestions on ways to troubleshoot this? I have > DEBUG enabled with these values: > > :log_buffer: 4000 > :log_buffer_errors: 2000 > > Also, is a way to move SmP from WebBrick to Apache/Passenger if that > makes sense at all? If so, any docs? Any other ways to increase the > performance as it does feel like a performance issue to me. > > Thanks! > -- > You received this message because you are subscribed to the Google > Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to foreman-users+unsubscr...@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Puppet Conf next week, who's going from Foreman
Hi all, So Puppet Conf is just around the corner (10th), and as usual I'd like to see if there's interest in a drinks meetup at some point during the conf. Who's going that would be interested in an ad-hoc Foreman meetup? Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: yum.theforeman.org having issues?
Thanks for the heads up. There was a bunch of network errors on that node over the weekend. We've hopefully fixed it, so let us know if it comes back. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman feedback, where to do it?
On Mon, 2017-10-02 at 08:51 -0700, Mike Wilson wrote:
> The reason I was thinking it would solve a problem is ... currently
> we use "HostGroups" as a location based setting. Pop has a specific
> hostgroup so that when the user goes to build a host his settings are
> set for "defaults" for that locale (such as puppet master, puppet CA,
> subnets/etc). Because of that we have a need of assigning puppet
> classes to a host group with specific parameters. So, applying a
> Config Group "dns-servers" would make sure all the classes for dns-
> servers puppet are applied to the server. In this case we'd need to
> be able to apply certain parameters to the "group" for those settings
> (such as specific firewall settings, dns settings/etc).
This is fine, and plenty of people do this. Using Smart Class
Parameters that match on Hostgroup should give you the flexibility you
need - is there some other reason you'd like to move away from using
Hostgroups for this?
> Now, if we switch to using host groups as a Host-Service we can get
> around this (and we're moving that way now) but because of that we
> really won't use Config Groups at all. They really don't buy us a lot
> unless we can set specific parameters for them.
Agreed, you won't gain much, but as above, I'm not sure that you need
them anyway?
> In short, we need Config Groups to have parameter options so we can
> have settings for those specific Config Groups. The plan originally
> was to have Config Groups be setup so that each group was a service.
> So, things like Apache, NTP, Mail/etc and each of those requires
> specific options for those groups while those not in those groups
> would need other options (normal machine wouldn't need to special
> mail server configs of say our primary mail spool).
So the elephant in the room is Config Group conflicts. We allow the
same classes to exist in multiple groups, so consdier a Host with these
two groups assigned:
group1:
classes:
dns:
country: usa
group2:
classes:
dns:
country: uk
In Puppet this would throw an error (you're basically doing two 'class
{ 'dns': ... }' calls with different params), but in Foreman we have no
way to handle it. Params can be constructed from facts, so we can't
parse them ahead of time to check for conflicts and warn the user. We
have no way to set some kind of 'priority' on Config Groups to
determine who "wins" a conflict, and even that's only good if you don't
want merge-tree behaviour, etc.
It's such a messy problem, so we decided it would be safer to do what
Puppet does - you can "include ::dns" as many times as you like in
Puppet, so long as you don't specify params :)
> Maybe there is a better way to do this and I'm just not seeing it.
> We're still REALLY new at provisioning with Foreman.
It does sound like Hostgroups could fill your needs, unless I'm missing
something. Another option is to edit the Foreman settings file and
enable Locations - but this adds a lot of complexity to the UI as
nearly everything (Proxies, Domains, Subnets, Hosts, etc) get scoped to
one-or-more Locations then. Still, it may be useful to you, as it's
another thing params can match on.
HTH
Greg
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Passenger/Foreman doesn't start anymore
This worries me: App 4417 stderr: --> passenger_native_support was compiled for Ruby API version 2.0.0, but you're currently running a Ruby interpreter with API version 2.2.0. App 4417 stderr: Refusing to load existing passenger_native_support. Are you *certain* you only updated Puppet? Was it just a "yum update" that could have touched other things? This log implies that either the Ruby version changed (unlikely since we SCL it) or the Passenger version changed. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] AWS EC2 with Foreman
On Thu, 2017-09-28 at 07:08 -0700, Ivan Adji-Krstev wrote: > Hi Greg, > and when i press resolve i got this message > Also when i try to press submit i get the same error. > > There is no finish template anywhere as options on the way. I have > try to lock the template but again same results. What version of Foreman are you on? There was a bug with the Resolve Templates button in recent Foreman versions (1.14 & 1.15, I think), but that was fixed in 1.15.4. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Lots of "Mysql2::Error: Deadlock found when trying to get lock" under increased load
On Tue, 2017-10-03 at 16:12 -0700, 'Konstantin Orekhov' via Foreman users wrote: > > As Lukas says, a full refactor may well happen, and we'd love input > > on that as we go forward. > > Any of you, guys, going to PuppetConf this year? If so, can we meet > and have a discussion on this maybe? I certainly won't be, sadly. I'll ask around and see if anyone is heading down. > > I think I agree - the hosts should keep retrying until they get a > > response from Foreman, but then actions can be taken. I'd probably > > be in favour of keeping the retry (so that, say, if the offending > > MAC is removed in Foreman, the host can register on the next > > retry), but perhaps split the process into two calls. The first is > > a light "am I registered?" call that returns true/false, and only > > if false would the heavier registration call be made. Does that > > work? > > Yes, this would definitely work. This is also is one of the states of > a system in the state machine we talked about above. Agreed, a proper place to hook it would be ideal, I'm just throwing ideas out that might help in the short term. Sounds like Lukas has you covered on the DB locking issues anyway though :P Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 05 Oct 3pm [BST]
Hi all, We're going to add an Ask Me Anything section to today's demo, as we're a bit light on content to show (lots of presenters on vacation today, sadly). So, if you have any burning questions, or would like me to go into some detail on a particular part of Foreman, then let me know - either here, or in IRC (ping 'gwmngilfen' in #theforeman) See you all in a few hours! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Cannot configure network interface error while provisioning hosts
We're going to need a lot more information to help you out with this. For the hosts that work, what are they? Physical or virtual? If virtual, what platform are you provisioning on? Some require mac addresses to be provided, some don't. For those that fail, the same question, but also provide the log of the failure from /var/log/foreman/production.log on the Foreman host. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] foreman installer and existing apache server
On Fri, 2017-09-29 at 11:25 -0700, Sean A wrote: > Sorry to dig up an old topic, but I just got nailed on this...as I > had forgotten about it. > > Has there been any update to being able to use foreman-installer with > preserving unrelated apache config files in /etc/httpd/conf.d? I am > trying to use an IP vhost to serve repositories and some other static > pages related to Foreman. I have the vhost in a separate config > file, but re-running foreman-installer blows it away. > > I know I could stuff those files down in /var/lib/foreman/public (or > whatever it is), but directory indexes are disabled, and I can't seem > to enable them and make that stick either. No, our installer assumes Foreman gets the sole use of the box. If you're running Puppet for the rest of your config management, then one option is to add the foreman-installer modules to the rest of your Puppet manifest, and configure them to match the installer. This means all the vhosts will be in Puppet and the code that deletes unmanaged files won't touch them. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 05 Oct 3pm [BST]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 05 Oct for a special edition of the community demo, for the usual roundup of all the new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=Oty8LWnilr8 [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] AWS EC2 with Foreman
On Wed, 2017-09-27 at 15:01 -0700, Ivan Adji-Krstev wrote: > Hi all, > Is there a good tutorial on how to provisioning EC2/VM on AWS using > Foreman. No need to restrict to AWS, provisioning is largely the same in Foreman regardless of the platform - that consistency is part of the attraction of Foreman for many people. > I have try the Foreman Documentation and some Google results, but all > i get some error for unfinished template " Failed to save: No finish > templates were found for this host, make sure you define at least one > in your CentOS_7 settings" The OS setup is indeed fiddly. Start by going to the finish template you want to use (Hosts > Provisioning templates), and on the Associations tab, make sure the CentOS 7 OS has been added. Save that, then go to the Operating Systems page, edit CentOS 7, and on the Templates tab, select the finish template as the default for this OS. Save the OS. When you provision a new host, you can click the Resolve Templates button to check it's picked up the right template before you hit Save. HTH, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: puppet agent upgrade on deployed hosts
Indeed, this looks like a side effect of moving from Puppet 3 to Puppet 4 - the config file for Puppet itself changes location (/etc/puppet/puppet.conf vs /etc/puppetlabs/puppet/puppet.conf). So unless additional care is taken to copy that file (either manually or by using something like Matt's suggestion) and any related files like $ssldir etc. then you'll get a blank config file, and thus what you're seeing with new certs etc. Migrating Puppet 3 to Puppet 4 was, in my experience, a giant pain, but at least you only have to do it once. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman feedback, where to do it?
On Tue, 2017-09-26 at 11:03 -0700, Mike Wilson wrote: > Where is the best place to leave feedback of RFI? We've ran into an > issue where I'd really like to have class parameters on "Config > Groups" and was wondering where I could make a feedback/suggestion. If you just want to discuss ideas, then here is absolutely fine. If you're certain of what you want already, then you can raise an issue on our bug tracker [1]. Parameters in config groups could be very tricky to implement though, so do share your thoughts on this :) Cheers Greg 1: http://projects.theforeman.org/projects/foreman/issues/new -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: Foreman 1.16.0-RC1 available for testing
On Mon, 2017-09-25 at 11:14 -0700, Eric Sorenson wrote: > Hey Daniel - awesome to see the puppet5 support coming in so quickly > after release! The links to the release notes below aren't live yet, > but I'm wondering how smoothly the update went and whether there are > any outstanding bugs/issues we should look at upstream before this > goes from RC into GA. I saw a couple of items about new > trapperkeeper services that were resolved, anything else? So I wasn't directly involved myself, but what I heard was: * Most of our code worked fine, some minor patches needed * Where we use upstream modules in the installer, getting new releases published with Puppet 5 in the metadata took a lot of time * Of those modules, the Puppetlabs-maintained modules that we use were among the slowest of these to update / release new versions * Support for Debian 9 (stretch) was made harder by the lack of Puppet Server packages - that's still not released I think? The impression we're getting around modules particularly is that the Puppetlabs module team are struggling to keep up. Getting PRs merged in for Puppet 5 support / removing Puppet 4 deprecations was probably the most time consuming thing. I know the people closer to the ground will jump in if I got anything wrong ;) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: Foreman 1.16.0-RC1 available for testing
On Mon, 2017-09-25 at 11:14 -0700, Eric Sorenson wrote: > The links to the release notes below aren't live yet, Fixed - thanks for the heads up :) -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Templates
On Tue, 2017-09-26 at 13:51 +0300, Ido Kaplan wrote: > Hi Greg, > > I mean about contents of the templates in Foreman, for example - > "Kickstart default.rb"? Those should not be altered by that button, no. The only time the default templates would be updated would be during a version upgrade of Foreman. Changes to templates are audited, so you should be able to see the history of changes, so that's worth looking at to see what might have made the changes. Also, if you can reproduce it reliably, we can try and see if we see the same behaviour Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Lots of "Mysql2::Error: Deadlock found when trying to get lock" under increased load
A few extra thoughts on this, since a lot of it is still based on my design from nearly 5 years ago ;) On Wed, 2017-09-20 at 17:27 -0700, 'Konstantin Orekhov' via Foreman users wrote: > > Hmm, one generic question on this - according to above logic, if my > managed host had crashed, say because it lost its HW RAID controller, > for example, so it can't boot off the disk anymore thus resulting in > PXE boot (given that BIOS boot order is set that way), correct? > Now, by default, Foreman default pxeconfig file makes a system to > boot off its disk, which in this particular situation will result in > endless loop until some external (to Foreman) monitoring detects a > system failure, then a human gets on a console and real > troubleshooting starts only then. This is absolutely true. We had, at one time, considered adding a state machine (or similar) to Foreman, so that such things (as well as boot loops in Kickstart, and so forth) could be detected, but it was never completed. > Now, with that in mind, I was thinking of moving actual OS > provisioning tasks to Foreman as well. However, if crashed system > would never be allowed to re-register (get discovered) because it is > already managed by Foreman, the above flow is just not going to work > anymore and I'd have re-think all flows. Are there specific reasons > why this in place? I understand that this is how it is implemented > now, but is there a bigger idea behind that? If so, what is it? There were two goals - to prevent duplicates (if unprovisioned hosts are rebooted, for example), and to allow recycling (delete a host from Foreman, reboot it, and it'll be back in the discovered hosts list to be re-used). Neither of these is insurmountable some other way, but this was the easiest. > Also, if you take my example of flows stitching for a complete system > lifecycle management, what would you suggest we could do differently > to allow Foreman to be a system that we use for both discovery and OS > provisioning? As Lukas says, a full refactor may well happen, and we'd love input on that as we go forward. For a workaround today, I'd probably lean towards a secondary plugin that sits on top of Discovery and interacts with the registration process - given your example, you could add a check if the regitraion matches a host that's already provisioned, and take further action if so. That might also be a good way to proof-of- concept some ideas, before merging the code back into Discovery. > Another thing (not as generic as above, but actually very applicable > to my current issue) - if a client system is not allowed to register > and given 422 error, for example, it keeps trying to register > resulting in huge amount of work. This is also a gap, IMHO - > discovery plug-in needs to do this differently somehow so rejected > systems do not take away Foreman resources (see below for actual > numbers of such attempts in one of my cluster). I think I agree - the hosts should keep retrying until they get a response from Foreman, but then actions can be taken. I'd probably be in favour of keeping the retry (so that, say, if the offending MAC is removed in Foreman, the host can register on the next retry), but perhaps split the process into two calls. The first is a light "am I registered?" call that returns true/false, and only if false would the heavier registration call be made. Does that work? Thanks! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Templates
On Mon, 2017-09-25 at 23:35 -0700, Ido Kaplan wrote: > Hi, > > It looks like that sometimes provisioning templates are restored to > default. Can you clarify what you mean here? Are the contents of the templates *in Foreman* changing, or on the TFTP proxy? > I think that it's happens when I click "Build PXE Default". > Is it by design? When that button is clicked, all the TFTP proxies should have the $tftpdir/pxelinux.cfg/default file rewritten to match the selected default template. Nothing should change in Foreman, or in any other tftp file. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: ignored_environments.yml
On Tue, 2017-09-05 at 20:55 +0200, Roger Mårtensson wrote: > > No problem. My file is: > --- top of file --- > #:ignored: > # - test > > :filters: >- !ruby/regexp '/^(?!role::.*)$/' > --- bottom of file --- > > The "---" is of course not part of the file. This should be a > copy-and-paste directly from the documentation. Yeah, that looks fine. YAML is annoyingly special about whitespace, but that indentation looks ok too. > Not long ago (sorry for not replying earlier) I noticed that I coult > get it to work by adding a .* to the end of the rule just before the > $. So to be clear, (?!role::.*) doesn't work, but (?!role::).* does work? I see the same behaviour on Rubular.com, although I haven't tested it locally yet. Would you be prepared to send a small patch to the docs? > The documentation also states that "It will not delete any > environments or classes already in Foreman." which is false. After > adding the rule (with the ending .*) it asked if I wanted to delete > any of the ignored classes. True, I guess this doc predates when we added the import page offering to remove unfound items - although the removal is unchecked by default, I think. Again, a patch to the docs (or just an issue logged in our issue tracker) would be awesome. Thanks! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Migrating Foreman database from MariaDB (MySQL) to PostgreSQL
A bit of a stab in the dark here ... :) If I recall correctly, the prod2dev task isn't great at creating *every* table in the source db, but rather only the ones it thinks it needs. However it then tries to copy *every* table, which can lead to errors when it tries to copy into the target db. Try comparing the two dbs after it's failed, and then see which tables are missing (i'm betting they'll be plugin related...). If that looks realistic, you could create those tables yourself and run the migrate again... Tedious, I know. If that works, do log a bug about it in the issue tracker ;) -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Getting "400 Bad Request" when trying to remove host entry in Foreman webGUI
Best thing to do is probably to go to the appropriate DHCP proxy and up it's logging to "debug" level, and then tail it's logs while performing one of the failing actions - hopefully that will shed light on what's happening. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: can i receive enc for other hosts.
On Tuesday, 22 August 2017 15:48:39 UTC+1, Dmitry Vasilets wrote: > > hello > there are tasks - receive list of databases and configure connection to > all of them from web app. > I can use function foreman > https://github.com/theforeman/puppet-foreman/blob/master/lib/puppet/parser/functions/foreman.rb, > > but require configure tls or basic auth. > Can i receive same information by node.rb or more easy ? > thanks > So long as the user connecting to the API has the required rights, then yes, you can retrieve information via node.rb. However anything in the ENC is available in Foreman itself, so it *might* be easier to specify that information in the ENC of the target host, via a smart class parameter - depends exactly on what you're trying to achieve, of course. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: ignored_environments.yml
Heya! That issue is what lead to that entry being placed in the manual, so they're effectively the same thing. Can you share the exact contents of your ignored_environments.yml, just so we can see? Maybe there's a typo or something on another line that is causing issues -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Foreman with saltstack
Hey, sorry for the slow reply! You can disable the Puppetmaster service after the Foreman installer has done it's job, if you want - it shouldn't cause any issues. You can also remove Puppet entirely, but that will break your ability to re-run the installer after major upgrades (not 100% required but often good practice). Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 24 Aug 3pm [BST]
Hi all, This was recorded last week, we covered some minor changes on the code, and then spent a significant portion on discussing proposals for a new template auditing feature from Shim. Your thoughts on this are very much wanted! Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/aOqA8-wpPKQ?t=0 * Minor fixes (tbrisker) - https://youtu.be/aOqA8-wpPKQ?t=118 * UX improvements (mhulan) - https://youtu.be/aOqA8-wpPKQ?t=379 * REX: Timeouts (aruzicka) - https://youtu.be/aOqA8-wpPKQ?t=706 * New fog-ovirt (orabin) - https://youtu.be/aOqA8-wpPKQ?t=898 * RFC template audit (shimshtein) - https://youtu.be/aOqA8-wpPKQ?t=1029 URLs mentioned: New fog-ovirt gem: https://github.com/fog/fog-ovirt Shim's template auditing RFC: https://github.com/theforeman/foreman_templates/pull/61 Cheers Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: foreman-proxy and dhcpd next-server
Hi Bill, On Tue, 2017-08-15 at 09:48 -0700, Bill Sirinek wrote: > Is there any update to this issue? I'm working on upgrading to 1.15.3 > and this problem still exists. I have about 20 DHCP servers with > smart proxies and many of them are multi-homed because we do a lot of > building on non-routable admin networks. > > I see Bug #1221 http://projects.theforeman.org/issues/1221 that was > "Ready For Testing" but got moved back to "New" (!) I'm not sure you meant 1221, that bug appears to have been closed 5 years ago... > There is also http://projects.theforeman.org/issues/9169 that appears > related I think this is the bug you meant. To be clear, Ready For Testing means a patch has been written and can be reviewed. If the patch is not merged, or the approach needs to be changed, then the PR will be closed and the state reverted to New (or Assigned if someone is still owrking on it). In this case, as far as I can see, the person who proposed the change abandoned the patch before it got merged (see https://github.com/thefor eman/foreman/pull/3360#issuecomment-200659805), so it's correct that it was set back to New. I still think such a feature (a checkbox on the Subnet to not set next-server) is a welcome one, if anyone else wants to pick it up. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 03 Aug 3pm [BST]
Sorry for the delay in updating this (vacation!), but here's the show notes for the demo just over a week ago. In this demo we covered Remote Execution (REX) updates, new developer tooling in Hammer, the new scheduing support for ActiveJob, and a new community-made plugin for ActiveDirectiry. Enjoy! Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/rZY6dE0HVyM?t=0 * Granular Permissions (mhulan) - https://youtu.be/rZY6dE0HVyM?t=156 * REX: Async SSH (aruzicka) - https://youtu.be/rZY6dE0HVyM?t=470 * REX: Abort/poll tasks (inecas) - https://youtu.be/rZY6dE0HVyM?t=630 * Hammer: New debug (tstrachota) - https://youtu.be/rZY6dE0HVyM?t=839 * ActiveJob backend (dlobatog) - https://youtu.be/rZY6dE0HVyM?t=1261 * AD Realm integration (mcassel) - https://youtu.be/rZY6dE0HVyM?t=2300 You can find the presenter IRC nicknames in the links above - feel free to ask questions here or in IRC. Cheers Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Re: LCE or CV/CCV package differentials
On Wed, 2017-08-02 at 13:02 +1000, Lachlan Musicman wrote: > On the "I wish" pile. Maybe also add it to our "I wish" pile too? :) http://projects.theforeman.org/projects/katello/issues/new Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 03 Aug 3pm [BST]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 03 Aug for a special edition of the community demo, for the usual roundup of all the new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=rZY6dE0HVyM [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 13 Jul 3pm [BST] - 8th Birthday Edition
Slightly late, but in case you missed it, here's the show notes from our birthday demo - it's pretty packed! * Intro (gwmngilfen) - https://youtu.be/sL8KylTcqsg?t=0 * Search performance (tbrisker) - https://youtu.be/sL8KylTcqsg?t=241 * Fast Host list API (tbrisker) - https://youtu.be/sL8KylTcqsg?t=403 * Ansible roles for deploying Foreman (tstrachota) - https://youtu.be/sL8KylTcqsg?t=528 * Netgroup / usergroup mapping (tstrachota) - https://youtu.be/sL8KylTcqsg?t=799 * Backup/restore content proxies (jomitsch) - https://youtu.be/sL8KylTcqsg?t=1149 * Foreman Docker 3.2.1 (bastillian) - https://youtu.be/sL8KylTcqsg?t=1510 * Webpack for plugins (dlobatog) - https://youtu.be/sL8KylTcqsg?t=1693 * Rails 5 summary (dlobatog) - https://youtu.be/sL8KylTcqsg?t=1999 * foreman-bootloaders-redhat (lzap) - https://youtu.be/sL8KylTcqsg?t=2203 * Discovery helper script (lzap) - https://youtu.be/sL8KylTcqsg?t=2668 * Host Info providers (shimshtein) - https://youtu.be/sL8KylTcqsg?t=2898 Thanks to all the presenters, as always, and to the community as a whole - 8 years and going strong :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 13 Jul 3pm [BST] - 8th Birthday Edition
Hi all It's time for the next Foreman Community Demo! This time, the demo just *happens* to be bang on our 8th birthday! So, join us at 3pm on Thu 13 Jul for a special edition of the community demo, with special sauce on top of the usual roundup of all the new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=sL8KylTcqsg [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman host data not updating...
The obvious candidate is that facts aren't being uploaded, but you say that's not the case (maybe double-check with something that changes frequently like uptime?) The next step would be to get some logs from the Foreman production.log during a puppet agent run - ideally with logging set to debug and the various loggers turned on (see Logging under https://theforeman.org/man uals/1.15/#3.5.2ConfigurationOptions). Put that in a pastebin and lets have a look at it :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Plugin or tool to link Foreman to GIT
On Mon, 2017-07-03 at 10:04 -0700, 1284ty...@gmail.com wrote: > Hi All > > I have been attemtping to use r10k as a tool to create dynamic > environments with git and my puppet master, however i was wondering > if there is a plugin or tool that would interface between a git repo > and Foreman directly? What exactly are you looking for? Are we talking about deploying classes to disk, or importing classes into Foreman after a deployment? For the former, Foreman doesn't care how the classes get to the puppetserver. I personally use a bare git repo (in /var/lib/puppet/puppet.git) and a post-commit hook that checks out the repo to /etc. r10k certainly works to, as does a variety of other methods. If you're talking about importing the classes into Foreman after a deployment, then there's a rake task you can execute on the Foreman host (foreman-rake puppet:import:puppet_classes). Be careful with this though - the UI offers a chance to review the changes (especially which classes have been deleted), but the rake task will import the changes with no confirmation. Be sure your commits don't have syntax errors in if you go down this road ;) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Foreman 1.15.1 user data template issue with EC2/AWS
On Thu, 2017-06-29 at 16:25 -0700, Mike Wilson wrote: > I am testing out AWS with foreman 1.15.1 and when I try and resolve > the template during a creation I get the following error in the logs, > the web interface simply says "Sorry no templates were configured." The OS has a user-data template, that's good - but did you mark the Image in Foreman as requiring user-data? By default I think they default to SSH-based provisioning, and there's a checkbox to make it use user-data. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Finding parameters for a host
On Wed, 2017-07-05 at 08:45 -0700, Brian McArdle wrote: > Is my understanding above all correct? Is there a shortcut that I'm > missing to finding out what values a host is using for a class? It's already in the ENC data that Foreman sends to Puppet (assuming the host is in the hostgroup in question). When the ENC YAML is compiled, Foreman will parse the parameters from least specific to most specific, overriding ones with the same name as it goes. So if your hostgroup has "class foo -> parameter bar = quux" you should see that on your host directly (check the YAML button on the host page). But if the host has "class foo -> parameter bar = qaaz" then you'll see that instead. The exact hierarchy is listed in the manual, see: https://theforeman.org/manuals/1.15/#4.2.3Parameters You don't actually say *where* you're trying to consume this data though. I assume you're wanting it in Puppet, which should work out of the box - anything in the ENC is passed to Puppet and should be used directly. If you want to access it in templates, you can use "<%= host_enc %>" (via http://projects.theforeman.org/projects/foreman/wiki/ TemplateWriting#Functions-and-macros), and from some other place, there is an API call to get the host's ENC data (GET /api/hosts/:id/enc) If want to access data for other hosts / hostgroups in Puppet manifests, there are ways - but for brevity I'll not go into to that yet. If that's what you're actually looking for, shout out :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)
Hi all, Running Foreman in a container is a question that comes up from time to time in the Foreman community. Eric Helms has been experimenting with running the whole Foreman stack (core, proxies, plugins) inside Kubernetes, and wants to show you how it looks. We'll be holding a deep dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in here: https://www.youtube.com/watch?v=mPjUvNAYp1c As always, we welcome your contributions to the video - do join us live on YouTube Live chat or in our IRC channel to put your questions to Eric! Cheers, Greg -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Deep Dive] Vertical Navigation Proposal, with Rox & Serena
Hi all, A while back there was a proposal for a vertical navigation for Foreman [1,2]. This has been rumbling on for a while, so I felt it might be time to shine a spotlight on it and get some fresh voices in the discussion. When it comes to UI changes though, I find screenshots hard to visualize, so perhaps a live demo is in order... :P Accordingly, there will be a deep dive on Tuesday where Rox and Serena will spend some time talking about what they feel is wrong with our current UI (and horizontal UIs in general), how moving to a vertical navigation helps, how it worked out for a couple of other communities, and how it *might* look for us. https://www.youtube.com/watch?v=hQwJ11GYfjY To be clear, these are still *proposals* at this stage, and we definitely want to hear from people about how they feel on this - what you feel is wrong with the current UI, and how we might fix it. This is one approach, but perhaps you have other suggestions :) Feel free to join us live and ask questions to Rox & Serena via the usual IRC or YouTube methods, or if you catch it later, we can continue the discussion here on the mailing list. Thanks! Greg 1 https://groups.google.com/d/topic/foreman-dev/2dERjSniGzc/discussion 2 https://github.com/theforeman/foreman/pull/4302 -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] last call for speakers - Portland Config Management Camp
Hi all, If you're interested in speaking about Foreman at the upcoming Portland Config Management Camp, there's still *just* time to submit. It closes in about 24 hours. I know from the organisers they're very keen to have some Foreman involvement, and CfgMgmtCamp is always a blast - so please do submit if you're in a position to do so! https://github.com/cfgmgmtcamp/2017-pdx-cfp/ Thanks! Greg -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] Deep Dive on performance analysis for Foreman instances, 3pm Thurs 15th
(Apologies for cross-posting) Hi all, This coming Thursday, Shimon Stein will be giving a deep dive into performance analysis on Foreman instances. We'll be looking at: 1. Installation of tooling in dev env 2. Simple request breakdown (view, sql) 3. Debugging API request 4. Time graph (flamegraph) 5. Memory consumption 6. Installation in prod env Do join us live to take part and ask your questions to Shimon in realtime - as ever, you can use IRC (#theforeman) or the YouTube Live chat on the event page. The event page is https://www.youtube.com/watch?v=bFQvj8CyvXI See you then! Greg -- IRC / Twitter: @gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 01 Jun 3pm [GMT]
Hi all, Sadly this demo will have to be cancelled due to a combination of circumstances - mainly lack of presenters, but also I can't be present today to host it. We'll see you in 3 weeks! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 01 Jun 3pm [GMT]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 01 Jun for a roundup of all the new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=_OrYpestGQc [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: Deep Dive - Monitoring with Foreman, 4pm CEST Thu 27th Apr
Sadly we had to push this back by a week - the new date is Thu May 4th, same time. See you then! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 20 Apr 3pm [GMT]
This is now going to be a Foreman AMA - see https://groups.google.com/d /topic/foreman-users/TSf6tph1l8U/discussion for details and to ask your questions! Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] Foreman Talks at PuppetConf [10-12 Oct] - CFP closes in a few days!
Hi all, Eric Sorenson from Puppet reminded me recently that some Foreman talks would be lovely to have at PuppetConf this year, and asked me to pass on the message below. Sadly, I then totally failed to do so (bad community guy, bad!) - but there's still time! If you do submit something, let me know! If you're speaking, I can hook you up with swag to take with you :P Cheers! Greg -- Forwarded message -- The PuppetConf 2017 call for proposals is now open, and we'd love to include your voice in the conversation. It's happening in San Francisco, California 10-12 October. The link to submit your talk proposal is here: https://puppet.com/puppetconf/cfp-registration We’re especially interested in: • Stories and examples of DevOps success. • Real-world adventures involving technologies like cloud and containers, innovative integrations with Puppet, or using Puppet to manage your applications, infrastructure, and datacenter. • Introductory topics for getting started with Puppet; writing, testing, and deploying modules; or your workflow and best practices recommendations. If you're interested in presenting but want a hand developing your idea into a great talk proposal, we'd love to help! Either email me directly or stop by the #speaking channel in the Puppet Community slack and we'll walk through it together. (You can sign up at https://slack.puppet.com if you're not already on it) Puppet celebrates diversity. Travel scholarships are available for speakers from underrepresented groups in tech who may not otherwise participate in PuppetConf. To apply, indicate your interest on the talk submission form. Be sure to get your submissions in by 23 April. Thanks, and hope to see you in October! Eric Sorenson - e...@puppet.com director of product, ecosystem and platform -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] Foreman @ Red Hat Summit - Boston, May 2-4th
Hi all, Red Hat Summit 2017 is just a few weeks away, and just like last year, we'll be there in the Community Central section! https://www.redhat.com/en/summit/2017 If you're planning to go (or already have your ticket!) and want to meet up, please do stop by the booth and say hi! We'll have a full offline provisioning demo, with a whole ton of plugins on top of Foreman itself (Katello, Discovery, Remote Executon, the list goes on) - so there's plenty to see. We'll also have a community dinner - details to follow on that, but I'd keep Tuesday night free if you can, it looks the best night to go for! If you'd like to help out on the Summit community booth, please get in touch with me *ASAP* - I have one volunteer already, and space for one more on the booth, and it'd be awesome to have some of you there to represent our amazing community. Enjoy! Greg -- IRC / Twitter: @gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 20 Apr 3pm [GMT]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 20 Apr for a roundup of the recent conferences, and the usual review of new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=0sl4HgMzgio [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 13 Apr 3pm [GMT]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 13 Apr for a roundup of the recent conferences, and the usual review of new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=0sl4HgMzgio [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] autoassign hosts to subnets
On Wednesday, 5 April 2017 13:19:11 BST funk sen wrote: > Hi, > > when I deploy a new vm with foreman over hammer, I add the subnet as > argument und the host gets assiciated correctly ofc > > > but when I add an existing system to foreman with puppet, the interface is > not associated to a subnet automatically, is there a way to do so? I set > parameters like mailrelay over subnets Not directly, no. Hosts created from Puppet facts/reports are what we call "unmanaged" hosts, which have all orchestration disabled. You might be able to do what you want via the foreman_hooks[1] plugin though, take a look. [1] https://github.com/theforeman/foreman_hooks Greg -- IRC / Twitter: gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part.
Re: [foreman-users] Completely uninstalling Foreman on Amazon Linux
On Friday, 24 March 2017 08:28:03 BST Johannes Kastl wrote: > D Last schrieb: > > However I cannot find documentation in the Manual for how to go about > > an uninstallation. > > > > Can someone please tell me how to completely remove it from an Amazon > > Linux system? > I would like to know, too, to somehow get to a clean slate while > experimenting... There's no automated way to do this, and given the hundreds of options in the installer, it's not really possible to doucment *all* the potential places where changes may happen. For a *default* installer run (Foreman, Proxy, Puppetserver, TFTP) then you'd want to stop the Proxy and Puppet(,server) processes, remove the Foreman vhost from Apache, and disable the inetd TFTP config. Plus you may ish to revert changes to Apache's config and more. If you're on EC2 though... just rebuild the hosts? :) HTH Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] "provisioning" IP for Puppet
On Tuesday, 28 March 2017 23:04:09 BST 'Jason B. Nance' via Foreman users wrote: > Hello, > > Has anyone happened to already have written some code to get the > "provisioning" IP (provision: true in the foreman_interfaces array) for a > host for use in a Puppet ERB template? I'm not aware of any puppet module for working with foreman_interfaces, although that would be cool :) You could use something more generic (like https://github.com/voxpupuli/ puppet-network) and pass in data via the smart parameters - then you'd put something like <%= @host.provision_interface.ip %> in your matcher HTH Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Manage DHCP through foreman-proxy module or foreman-dhcp ?
On Sunday, 2 April 2017 21:38:44 BST Matt wrote: > Hi Guys, > > I'm figuring out what the difference is between managing my DHCP pools with > the foreman-proxy module through the foreman-dhcp module or the > foreman-dhcp module itself. I have the foreman-dhcp module configured right > but I'm not able to find out how the foreman-proxy modules uses the > foreman-dhcp module when dhcp_managed => true > > Is there some format example available maybe ? The proxy just declares the main DHCP class and a single pool - see: https://github.com/theforeman/puppet-foreman_proxy/blob/master/manifests/ proxydhcp.pp#L27-L43 If you need anything more complex, you'll want to set managed => false and then use puppet-dhcp directly with your own pools. Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 16 Feb 3pm [GMT]
In case you missed it, the recording of this demo is available on YouTube - we covered sync and repo improvements, new notifications options for plugin maintainers, a new catalog diffing plugin, and updates to foreman-maintenance. Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/jg-pe6G05Mk?t=0 * Force sync and verify sync (jsherrill) - https://youtu.be/jg-pe6G05Mk?t=109 * Container registry product discovery (thomasmckay) - https://youtu.be/jg-pe6G05Mk?t=268 * Foreman-maintain updates (inecas) - https://youtu.be/jg-pe6G05Mk?t=611 * New notifications -Provisioning, discovery (ohadlevy) - https://youtu.be/jg-pe6G05Mk?t=1044 * Foreman-puppetdiff plugin (gwmngilfen) - https://youtu.be/jg-pe6G05Mk?t=1500 * Pulp sync performance update (jomitsch) - https://youtu.be/jg-pe6G05Mk?t=2146 * Metrics (gwmngilfen) - https://youtu.be/jg-pe6G05Mk?t=3490 URLs: Notifications PR: https://github.com/theforeman/foreman_discovery/pull/328 https://github.com/GregSutcliffe/smart_proxy_puppetdiff https://github.com/GregSutcliffe/foreman_puppetdiff You can find the presenter IRC nicknames in the links above. You can ask questions in the thread below, or on IRC. Thanks, Greg -- IRC / Twitter: gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout. signature.asc Description: This is a digitally signed message part.
[foreman-users] [Event] Next Foreman Community Demo - Thu 09 Mar 3pm [GMT]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 09 Mar for a roundup of the recent conferences, and the usual review of new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=jg-pe6G05Mk [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 16 Feb 3pm [GMT]
This was recorded last week, and if you missed it, the video is available on YouTube. In this community demo, we covered a wide range of topics from new tools & plugin releases, to UI changes and API updates, along with the usual roundup of news. Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/Zz0Bgt87wPE?t=0 * API for hidden params (orabin)- https://youtu.be/Zz0Bgt87wPE?t=118 * Tailoring OpenSCAP (oprazak) - https://youtu.be/Zz0Bgt87wPE?t=340 * Hammer for config groups (oprazak) - https://youtu.be/Zz0Bgt87wPE?t=640 * New Katello UI look (walden) - https://youtu.be/Zz0Bgt87wPE?t=747 * Forklift & Ansible (tstrachota) - https://youtu.be/Zz0Bgt87wPE?t=1218 * Foreman-Ansible 1.4.4 (dlobatog) - https://youtu.be/Zz0Bgt87wPE?t=1540 * Foreman maintenance (inecas) - https://youtu.be/Zz0Bgt87wPE?t=1798 * Parsing sosreports and logs (mbacovsk) - https://youtu.be/Zz0Bgt87wPE?t=2560 * Metrics (gwmngilfen) - https://youtu.be/Zz0Bgt87wPE?t=3490 You can find the presenter IRC nicknames in the links above. You can ask questions in the comments below, or come chat on IRC. Cheers, Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 16 Feb 3pm [GMT]
Hi all It's time for the next Foreman Community Demo! Join us at 3pm on Thu 16 Feb for a roundup of the recent conferences, and the usual review of new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the YouTube live chat, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=Zz0Bgt87wPE [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Your input needed! Foreman Community Survey (2017 edition) is ready!
Hi all I'm happy to announce the 2017 community survey is now ready for your input! Tell us how you use Foreman, what's good/bad, and help us shape what the next year of Foreman looks like! https://goo.gl/forms/xswoDALeJFoPMcy73 This year we've gone to a multi-page format - mainly for readability and sensible groupping. It shouldn't really take much longer to complete than last year. However, to say thanks for giving us your input, we're going to be giving away some *prizes* in a raffle at the end of the survey! We're looking at getting a couple of RaspberryPi3 (or similar SoC devices) to give away, plus t-shirts & stickers to runners up. A chance to have your own Foreman sandbox for messing about on - so get responding! https://goo.gl/forms/xswoDALeJFoPMcy73 I don't want to make this too burdensome, as we're an awesome & sensible community, but here's a minimum disclaimery stuff: * You'll have to give a contact email address at the end of the survey to be in the raffle, but it's entirely optional. You can remain anonymous if you prefer. All email addresses will be deleted after the raffle, in any case. * If shipping/customs is tricky, I might have to give you a gift card for an equivalent amount. We'll work it out. * Raffle will be done live on a future Communty Demo (prior notice be given) - email addressses will not be fully revealed (that would be a data breach!), but I'll show part of the address so it's clear that I'm not making it up :) Thanks again for your participation in Foreman - I look forward to writing the analysis blog post in a month or so :) Cheers Greg -- IRC / Twitter: gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [events] DevConf, FOSDEM, CfgMgmtCamp, Foreman Hackday & community dinners, oh my!
Hi all, Just thought I'd do a bump / round-up of what you can expect from the Foreman crew over the the next two weeks as we head into the chaos of conferences that is February. Do note the two community dinners ;) # DevConf 27-29th Jan We'll have a stand in the D105 area where you can come and chat with us, snag a t-shirt, and watch some demos. I'm also running a "Get started with Foreman" workshop on Fri at 1.30pm where we'll be building a Foreman sandbox in libvirt. Come along! We've also got a Community Dinner planned (thanks for handling it Tomas!) at 7pm, Sat 28th at The Immigrant (http://www.theimmigrant.cz/location). You can sign up here: https://plus.google.com/events/co5jeeofnu4issgrp5fguss6ovo (or drop me a mail if you don't like Google). Hope to see you there! # FOSDEM 4th-5th Feb As usual, we'll be sharing a table with the awesome oVirt guys in K-building - again, you can find us there for swag, chat, and demos. # CfgMgmtCamp 6th-7th Feb Once again, we have a full and exciting Foreman track at CfgMgmtCamp - you can read the whole lineup here - http://cfgmgmtcamp.eu/schedule/#foreman We'll also have a Foreman Community dinner on Tue 7th, provisionally 7.30pm at De Progres (http://www.duprogres.be/en - booking is awaiting confirmation :P). You can sign up here: https://plus.google.com/events/c0691utaaeikrb6dned8vt38e0g (or drop me a mail if you don't like Google). Hope to see you there! # Foreman Construction Day If you're an existing contributor to Foreman, or want to become one, this is the event for you. We'll have guided walkthoughs of parts of the codebase, working groups for specific topics, general tutorials, and so on. If that's your thing, you can grab a (free) ticket here: http://foreman-construction-day-2017.eventbrite.com/ It's going to be fun... see you all soon! Cheers Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 19 Jan 3pm [GMT]
On 2017-01-19 12:45, Greg Sutcliffe wrote: Just a quick reminder that this will be live in just over 2 hours (there's a countdown on the YouTube page) - see you there! Actually its https://www.youtube.com/watch?v=GiU2O8MCe8s Thanks to Klaas for pointing it out :) Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 19 Jan 3pm [GMT]
Just a quick reminder that this will be live in just over 2 hours (there's a countdown on the YouTube page) - see you there! https://www.youtube.com/watch?v=WwY_IawhRKc Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Next Foreman Community Demo - Thu 19 Jan 3pm [GMT]
Hi all It's time for the first Foreman Community Demo of 2016! Join us at 3pm on Thu 19 Jan for a look back over 2016, as well as the usual review of new & interesting developments from around our community. As ever, more information is available on the event page [1] and the show agenda is being compiled at the Foreman wiki [2]. If you have anything new, cool tips, etc, that you'd like to share with the community, please do let me know and I can arrange for you to be on the demo, or (if you can't make it) I can demo for you. As ever, we encourage live participation via the Hangouts Q app, or in IRC (#theforeman on Freenode). For those that can't attend, the video will be posted to YouTube afterwards. If you'd like to know when other Foreman events are happening, do check out our Events page on the Foreman website [3]. [1] https://www.youtube.com/watch?v=WwY_IawhRKct [2] http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information [3] http://theforeman.org/events Cheers! -- Greg IRC: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [Event] Case Study: Foreman at Scale with Chris Baldwin (Tue 17th Jan, 2pm GMT)
It's been a while, but we've got a new case study for you :) Next Tue I'll be joined by Chris Baldwin of Cisco (IRC: oogs) to talk about using Foreman on tens-of-thousands of nodes. Join us for a discussion about load-balancing, multiple datacentres, DB clustering, memcache and much more! As always, you can join in live via YouTube Live chat, or on our IRC channel (Freenode / #theforeman). The stream will be here: https://www.youtube.com/watch?v=WwY_IawhRKc See you then! Greg -- IRC / Twitter: gwmngilfen Diaspora: gwmngil...@joindiaspora.com -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 15 Dec 2pm [GMT]
In case you couldn't join us live, the recording is now available. The panel discussion at the end went really well - if watching it sparks any thoughts of your own, do share them with us! Also, let me know if you'd like to see more of this style of content. As promised in my "Upcoming events" section, the Foreman Construction Day event is now open for registration - you can see my recent post to the list about it here: https://groups.google.com/forum/#!topic/foreman-users/QYIHyJ1kSBc/discussion Sections in today's demo: * Intro (gwmngilfen) - https://youtu.be/CY1U_54Cbbs?t=0 * Upcoming events (gwmngilfen) - https://youtu.be/CY1U_54Cbbs?t=143 * Community metrics (gwmngilfen) -https://youtu.be/CY1U_54Cbbs?t=273 * Background lengthy UI tasks (ohadlevy) - https://youtu.be/CY1U_54Cbbs?t=593 * Ignoring facts on import (dlobatog) -https://youtu.be/CY1U_54Cbbs?t=860 * new Ansible options (tbrisker) - https://youtu.be/CY1U_54Cbbs?t=1120 * 2016 panel chat (everyone) - https://youtu.be/CY1U_54Cbbs?t=1297 Event Urls: * DevConf.cz - https://devconf.cz * FOSDEM - https://fosdem.org/2017 * CfgMgmtCamp Ghent - http://cfgmgmtcamp.eu/gent-2017 * CfgMgmt Foreman Hackday - https://foreman-construction-day-2017.eventbrite.com/ URLs mentioned: Foreman Metrics Dashboard - http://tinyurl.com/foreman-metrics You can find the presenter IRC nicknames in the links above, and as always you're welcome to ask questions on this thread or in IRC. Cheers Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] [event] Foreman Construction hackday - Ghent, 8th Feb 2017 (after CfgMgmt) - Registration open!
Hi all, As promised on yesterday's demo, the registration page for the Foreman Construction Day is now open! This went really well last year (20+ people, all of whom enjoyed it), so I'm excited to see if we can do even better. You can register here: http://foreman-construction-day-2017.eventbrite.com The feedback last year was to perhaps have a little more structure, and maybe some prior discussion of topics. So, this year, we're adding a half-day track of deep dives and workshops. The exact agenda is still to be decided, but the current proposal is: * 09.30 - Welcome & Introductions * 10.00 - Deep dive / workshop 1 * 10.30 - Deep dive / workshop 2 * 11.00 - coffee break * 11.30 - Deep dive / workshop 3 * 12.00 - Deep dive / workshop 4 * 12.40 - LUNCH * Afternoon - Coding time (with coffee break at 15.00) * 16.00 - Conclusions & Thanks As with last year, we'll have several rooms, so if you want to grab some people and go code all morning, that's still an option, and we'll have coding time all afternoon too. I expect by lunchtime we'll all have an idea of what we'd like to spend the afternoon on :) However, I'd like input from the community on what these sessions & hacking topics should be! So far, from speaking to a few people, I know we could do workshops on: * Getting started with contributing (dev environment, writing good bugs/PRs, getting help) * Running Foreman via docker-compose * Developing Foreman UI components with React * Getting started with Foreman plugins I'm sure there's many other potential topics, so I've created a really short (two questions!) form here: https://goo.gl/forms/phjwj2ViQKn1s9kZ2 Feel free to put multiple topics in one answer, or submit the form multiple times - I'll parse it all out later :) Any questions, let me know. Hope to see you there! Cheers Greg -- IRC / Twitter: gwmngilfen -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-users] Deleting smart class parameters when deleting a puppetclass
Tricky question. I agree they're not so useful without a record of what class they were tied to, and worse, if you upload a new class of the same name, it may no longer accept those parameters, so it's questionable if they can be restored smoothly anyway. My gut feeling is to drop them - but before we go there, let me ask a UI question. Given the current import page already shows quite a lot of information, is there a good way to also show what parameter overrides will be deleted? Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
[foreman-users] Re: [Event] Next Foreman Community Demo - Thu 24 Nov 3pm [GMT]
In case you missed this live, the recording is available - in this episode, we have templating updates, a new Azure plugin release, improvements to background tasks, power information, and permissions systems There's also the usual roundup of metrics, events, and other things that have been going on in the last month. Sections in this demo: * Intro (gwmngilfen) - https://youtu.be/M0-3x8AUfFQ?t=0 * Upcoming events (gwmngilfen) - https://youtu.be/M0-3x8AUfFQ?t=65 * Community metrics (gwmngilfen) - https://youtu.be/M0-3x8AUfFQ?t=141 * Azure plugin 1.2 (dlobatog) - https://youtu.be/M0-3x8AUfFQ?t=325 * Katello: apps needing restart (sean797) - https://youtu.be/M0-3x8AUfFQ?t=992 * foreman_templates: settings & filesystem import (oprazak) - https://youtu.be/M0-3x8AUfFQ?t=1365 * Power info on hosts/index page (oprazak) - https://youtu.be/M0-3x8AUfFQ?t=1560 * Memory watcher for Dynflow (shimshtein) - https://youtu.be/M0-3x8AUfFQ?t=1716 * Multiple executors in foreman-tasks (shimshtein) - https://youtu.be/M0-3x8AUfFQ?t=1870 * Compute Resource (downloadable) key pairs (shlomizadok) - https://youtu.be/M0-3x8AUfFQ?t=2107 * Parameters permissions unification (mhulan) - https://youtu.be/M0-3x8AUfFQ?t=2401 * Templates export via API (mhulan) - https://youtu.be/M0-3x8AUfFQ?t=2861 * Listing roles inherited from usergroups (dhlavacd) - https://youtu.be/M0-3x8AUfFQ?t=3217 Apologies to Sean and Marek for slightly misunderstanding their entry on the agenda ;) Upcoming Event Urls: * DevConf.cz - https://devconf.cz * FOSDEM - https://fosdem.org/2017 * CfgMgmtCamp Ghent - http://cfgmgmtcamp.eu/gent-2017 * CfgMgmt Foreman Hackday - TBA -> watch for the announcements! URLs mentioned: Foreman Metrics Dashboard - http://tinyurl.com/foreman-metrics (very early days for this, much more to come) You can find the presenter IRC nicknames in the links above. You can ask questions in this thread, or on IRC. Cheers Greg -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
