[foreman-users] Re: Performance Problems on Webinterface /puppetclasses
Passenger tuning only helped with puppet runs, but not search problem. -- 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: Performance Problems on Webinterface /puppetclasses
Probably need to start from Apache/Passenger tuning as I started to get these on puppet runs: Could not retrieve catalog from remote server: Error 503 on SERVER: This website is under heavy loadWe're sorry, too many people are accessing this website at the same time. We're working on this problem. Please try again later. -- 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: Performance Problems on Webinterface /puppetclasses
On the same note - after upgrading to 1.13.1 today, I immediately noticed the huge delays in search through the hosts in both WebUI and API (the latter is actually worse than WebUI). Here are few examples: # time curl -kSs -u admin:$PASS https://localhost/api/hosts | jq '.' | grep total "total": 1695, "subtotal": 1695, real 0m0.816s user 0m0.040s sys 0m0.076s But the search through my 1695 hosts on this instances takes 2.5 minutes (!): # time curl -kSs -u admin:$PASS https://localhost/api/hosts?search=test | jq '.' | grep total "total": 1695, "subtotal": 1, real 2m25.147s user 0m0.053s sys 0m0.063s For comparison, the same operations in 1.7.1 (from which I migrated one of the instances) give these results: $ time curl -kSs -u korekhov:$PASS https://localhost/api/v2/hosts | jq '.' | grep total "total": 2561, "subtotal": 2561, real 0m1.057s user 0m0.014s sys 0m0.007s $ time curl -kSs -u korekhov:$PASS https://localhost/api/v2/hosts?search=test | jq '.' | grep total "total": 2561, "subtotal": 1, real 0m1.101s user 0m0.012s sys 0m0.007s Would much appreciate the help figuring this out. -- 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: Windows Smart Proxy 1.12+ Requirement of gem rkerberos
I think I didn't RTFM when doing bundle and excluding a few things. Per the documentation: bundle install --without development test krb5 puppet_proxy_legacy bmc libvirt is what I should have been running. Not just bundle install. On Thursday, October 27, 2016 at 3:37:01 PM UTC-4, jonath...@bluemedora.com wrote: > > I have a working 1.9 smart proxy on a windows 2008 r2 box. > > I am trying to get 1.12+ in order to support msdns ptr record creation on > this same box. > > It is requiring the rkerberos ruby gem. In order to build this gem, it > needs the MIT kerberos library files available. > > Has anyone found an easy way to get the kerberos libraries on windows to > build this gem (aside to building kerberos from source)? > > When I try to install the gem, I get the following message since it cannot > build it: > extconf.rb:11:in `': kadm5clnt library not found (RuntimeError) > > > > > -- 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] Windows Smart Proxy 1.12+ Requirement of gem rkerberos
I have a working 1.9 smart proxy on a windows 2008 r2 box. I am trying to get 1.12+ in order to support msdns ptr record creation on this same box. It is requiring the rkerberos ruby gem. In order to build this gem, it needs the MIT kerberos library files available. Has anyone found an easy way to get the kerberos libraries on windows to build this gem (aside to building kerberos from source)? When I try to install the gem, I get the following message since it cannot build it: extconf.rb:11:in `': kadm5clnt library not found (RuntimeError) -- 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] aarch64 packages for Ubuntu/xenial available
Hello, after adding an AArch64 (aka. ARMv8 or ARM64) build slave to the Jenkins infrastructure, binary packages for Ubuntu/xenial are available (again), starting with the 1.13.1 release. Regards -- Michael Moll -- 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] Dropping armhf builds for Ubuntu/trusty
Hello, due to a long standing issue (http://projects.theforeman.org/issues/15827) we were not able to solve, armhf package building for Ubuntu/trusty was dropped today. If you're using Foreman on armhf, consider upgrading to Ubuntu/xenial or migration to Debian/jessie. Regards -- Michael Moll -- 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: Katello 3.2 RC3 released
I also want to mention that 3.2 RC3 includes el6 support John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Thu, Oct 27, 2016 at 1:21 PM, John Mitsch wrote: > We are happy to announce the third release candidate for Katello 3.2 (Malt > Liquor). > > One notable change in 3.2 is the support of Puppet 4. More info about > upgrading to Puppet 4 can be found here: > > http://www.katello.org/docs/nightly/upgrade/puppet.html > > Your help is appreciated to ensure our GA release is solid, by either > installing a new instance or upgrading a test server. > > A list of the changes in Katello 3.2 is in our release notes: > http://www.katello.org/docs/3.2/release_notes/release_notes.html > > > Installation or Upgrade > == > > For installation, please see the instructions at: > > Server: http://www.katello.org/docs/3.2/installation/index.html > Capsule: http://www.katello.org/docs/3.2/installation/capsule.html > > For those testing upgrades, please use the instructions below and file > any issues you encounter. Please note that there are separate upgrade > instructions for the Katello server and Capsules: > > Server: http://www.katello.org/docs/3.2/upgrade/index.html > Capsule: http://www.katello.org/docs/3.2/upgrade/capsule.html > > Bug reporting > === > If you come across a bug in your testing, please file it and note the > version of Katello that you're using in the report and set the release > to 3.2.0. > > http://projects.theforeman.org/projects/katello/issues/new > > John Mitsch > Red Hat Engineering > (860)-967-7285 > irc: jomitsch > -- 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] Katello 3.2 RC3 released
We are happy to announce the third release candidate for Katello 3.2 (Malt Liquor). One notable change in 3.2 is the support of Puppet 4. More info about upgrading to Puppet 4 can be found here: http://www.katello.org/docs/nightly/upgrade/puppet.html Your help is appreciated to ensure our GA release is solid, by either installing a new instance or upgrading a test server. A list of the changes in Katello 3.2 is in our release notes: http://www.katello.org/docs/3.2/release_notes/release_notes.html Installation or Upgrade == For installation, please see the instructions at: Server: http://www.katello.org/docs/3.2/installation/index.html Capsule: http://www.katello.org/docs/3.2/installation/capsule.html For those testing upgrades, please use the instructions below and file any issues you encounter. Please note that there are separate upgrade instructions for the Katello server and Capsules: Server: http://www.katello.org/docs/3.2/upgrade/index.html Capsule: http://www.katello.org/docs/3.2/upgrade/capsule.html Bug reporting === If you come across a bug in your testing, please file it and note the version of Katello that you're using in the report and set the release to 3.2.0. http://projects.theforeman.org/projects/katello/issues/new John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch -- 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] PXE Issues + Provisioning Templates Broken
Thanks guys. I'm on my way to the airport and will be traveling for the next 30 hours so I won't get a chance to work on this till Monday. I did look at the guide Lukas provided, but I was looking at topic A so looks like I was working with the wrong configuration. Still looks like I'll need the network admin assistance with some setup so I'll need to identify the best contact for that. Appreciate the assistance! Travis On Oct 27, 2016 10:02 PM, "Greg Sutcliffe" wrote: > On 27 October 2016 at 05:00, Travis Ross wrote: > >> Thanks for the quick response Greg - I'm traveling in India so my >> timezone is a bit off. >> >> Images - These were my initial thought of use with oVirt until I started >> thinking about post deployment. I want there to be as little work >> necessary on the VM's as they will be for SQC and Engineering Developers to >> quickly test features and dispose of the VM. As you mentioned Foreman >> *could* still work with the Template - but how would it connect. I >> could technically have a static IP that gets changed after build - but what >> happens when 2 users try and create a VM at the same time. That's likely >> not the best solution. >> > > In addition to Lukas' reply for iPXE, another option for > image/template-based booting is this - Foreman 1.13 supports using > user-data with oVirt images. In this scenario, Foreman doesn't need to SSH > to the box, so it works even if Foreman can't know the IP. In return > though, the VMs need to be able to reach Foreman (they'll make a call to > /unattended/built when they're done). Might be worth investigating :) > > Greg > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Foreman users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/foreman-users/Q0xaeKxKQZk/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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] PXE Issues + Provisioning Templates Broken
On 27 October 2016 at 05:00, Travis Ross wrote: > Thanks for the quick response Greg - I'm traveling in India so my timezone > is a bit off. > > Images - These were my initial thought of use with oVirt until I started > thinking about post deployment. I want there to be as little work > necessary on the VM's as they will be for SQC and Engineering Developers to > quickly test features and dispose of the VM. As you mentioned Foreman > *could* still work with the Template - but how would it connect. I could > technically have a static IP that gets changed after build - but what > happens when 2 users try and create a VM at the same time. That's likely > not the best solution. > In addition to Lukas' reply for iPXE, another option for image/template-based booting is this - Foreman 1.13 supports using user-data with oVirt images. In this scenario, Foreman doesn't need to SSH to the box, so it works even if Foreman can't know the IP. In return though, the VMs need to be able to reach Foreman (they'll make a call to /unattended/built when they're done). Might be worth investigating :) 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] PXE Issues + Provisioning Templates Broken
Hello, it looks like you are using oVirt which has iPXE firmware built in. You don't need to use PXE at all! Configure your infrastructure as described in http://projects.theforeman.org/projects/foreman/wiki/Fetch_boot_files_via_http_instead_of_TFTP#C-Chainbooting-virtual-machines The only change you need to do is on your DHCP server that does this: "if iPXE is booting, then hand over iPXE template, otherwise hand over PXELinux". The ISC DHCP bit is on the wiki page. Other DHCP servers work similar way I think. On Thu, Oct 27, 2016 at 6:00 AM, Travis Ross wrote: > Thanks for the quick response Greg - I'm traveling in India so my timezone > is a bit off. > > Images - These were my initial thought of use with oVirt until I started > thinking about post deployment. I want there to be as little work necessary > on the VM's as they will be for SQC and Engineering Developers to quickly > test features and dispose of the VM. As you mentioned Foreman could still > work with the Template - but how would it connect. I could technically have > a static IP that gets changed after build - but what happens when 2 users > try and create a VM at the same time. That's likely not the best solution. > > It sounds like I need to get with IT and work on some integration. I'm sure > they will help me out as I had our AD/Linux Team assist in getting oVirt > integrated with our Domain which required a bit more than a simple login. > Unfortunately that work may have been in vain as it looks like now my User > Frontend will be Foreman rather than oVirt for VM Creation. > > I'll have to contact my IT Network team and see what would be easiest with > the least amount of questions... my subnet is only for my lab and my servers > so likely just creating a rule on my DHCP server would be easiest to forward > to my Foreman TFTP server. Making changes to the Corporate PXE server might > be a bit more of a pain and stir up more questions than i'm interested in > dealing with. > > I wonder outside of PXE is it possible to have Foreman mount the ISO to the > system and have it boot off local media? I have the ISO's stored in an ISO > Repository in oVirt so they are available, I'm just not sure if this is > something that Foreman supports. I guess the VM needs to be on the network > for Foreman to contact it to go through kickstart so simply booting to the > media isn't sufficient. (probably answered my own question there just > thinking allowed). > > > > Regarding my Logs. I'll go through enabling debugging to see if I can spawn > an error. The "Submit" i'm referring to is when I make any changes to a > Provisioning Template, whether it be association or script editing. When > you "Submit" the changes, I am redirected to the error page and nothing > takes place. It seems like the actions I took corrupted something within > the application. It's not like I have much done on the system to if it's > too much trouble I can just start from scratch considering it'll probably > take me awhile to get the DHCP settings updated I can't do much provisioning > anyway. > > > Thanks, > -Travis > > On Wednesday, October 26, 2016 at 6:51:04 AM UTC-5, Greg Sutcliffe wrote: >> >> On 26 October 2016 at 11:08, Travis Ross wrote: >>> >>> Okay I'm new to Foreman and oVirt but have been trying to set something >>> up in my lab for our developers. >> >> >> Welcome :) >> >>> >>> During my initial testing of deploying a VM to oVirt everything seems to >>> work except when my VM PXE boots I'm grabbing an IP outside of my >>> infrastructure and it's trying to load windows so likely it's a domain PXE >>> server that seems to be taking precedence. >> >> >> So one option would be to use premade images that can be configured when >> they spin up (I think oVirt calls them "templates", just to overload that >> term further :P). That would be one way to bypass the need for a TFTP >> server. >> >> However, Foreman will expect to know the IP so it can SSH in and configure >> the image once booted. You may have some issues there - but rather than >> derail further now, we can discuss it if that's an interesting direction. >> >> > I have restarted foreman.service >> >> You need to restart Apache, by default. The foreman service is provided by >> the packages for convenience but we use Apache/Passenger in the installer. >>> >>> 1. How to point my PXE boot to my foreman server rather than the >>> corporate PXE server? >>> >>> Is this on the oVirt side or Foreman Side to isolate which PXE server to >>> point to? >> >> Assuming you dont want to use images, as per above, then there's three >> steps: >> >> 1) Where does the VM get DHCP from. If it's a private network, you can >> control it. If it's bridged, it's time to talk nicely to the DHCP guys :) >> 2) The DHCP server hands out bootp and next-server records that direct the >> VM to the TFTP server - these need to be right >> 3) Or, the existing PXE server needs a class file (something for your >> network segmen
Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available
Foreman 1.13.1 and associated plugins have now been released into this repository for EL6. Eric On Tue, Oct 18, 2016 at 2:27 AM, Ivan Necas wrote: > Eric D Helms writes: > > > All, > > > > Given that Foreman has officially dropped EL6 support for 1.13, we are > > providing a set of EL6 builds for existing Foreman users as well as > Katello > > users who may not have been aware of the impending support drop. The > builds > > are being hosted with Katello's repositories and are signed by the > Katello > > GPG key. This includes an EL6 plugins repository as well (although, like > > usual, they are not signed). > > > > We will be working to ensure that for each Foreman z-stream release, we > > will rebuild the EL6 repositories with the updates and provide them > within > > a few days of the official Foreman release. > > > > Known Issues: > > > > Base Foreman installation will fail with a TFTP error that will ideally > be > > fixed by having [1] included in Foreman 1.13.1. > > > > We do not plan to build and support Foreman 1.14 and beyond on EL6 which > > also means Katello will be moving off EL6 then as well. So please > consider > > planning a migration strategy to continue getting updates if you are on > > EL6. The Katello team will be working to build out a migration path and > > strategy to ensure there is a supported path to go from EL6 to El7. If > you > > have questions or concerns please reach out to us so we can help with > this > > effort. > > > > For Katello 3.2 RC users, expect an EL6 Katello build to follow in the > next > > few days. > > Thanks Eric, Daniel and anyone else involved! I think this was an > important step to do before the actual move from rhel6 > > -- Ivan > > > > > > > Thanks, > > Eric > > > > > > [1] https://github.com/theforeman/puppet-foreman_proxy/pull/293 > > > > > > -- > > Eric D. Helms > > Red Hat Engineering > > > > -- > > 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. > > -- > 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. > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- 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 Nov 3pm [GMT]
Hi all It's once again time for the Foreman Community Demo, on Thu 03 Nov. So, join us for a 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]. 3pm is still working well, but do watch out for daylight-saving time changes around the world. As always, the calendar (https://theforeman.org/events) will render in your local timezone, so you can avoid missing it. 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&A 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=J1ejZaDFR8o [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: [katello] Portal conflict while upgrading
I finally got this figured out. Somehow, my katello-answers.yaml file had been modified. When I got that fixed, the upgrade completed successfully. On Wed, Oct 26, 2016 at 1:53 PM, Peter Kirby wrote: > When I upgraded to Katello 3.1, from 3.0, the installer (it appears via > puppet) keeps changing the foreman proxy tls port from whatever it was set > to in settings.yml to 8443. > > That port conflicts with the default candlepin port which causes the > upgrade to have an error because the proxy can't start with the address > already in use. > > Am I missing something that needs to change so I don't run into this every > time I upgrade? I'm currently facing the same issue trying to upgrade from > 3.1 to 3.2. > > Thank you, > Peter > -- 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 Column View Bug
On 4 October 2016 at 13:22, Greg Sutcliffe wrote: > For those not following the PR, https://github.com/ > GregSutcliffe/foreman_column_view/pull/18 and > https://github.com/theforeman/foreman/pull/3884 together fix the issue. > I'll release column_view 0.3.0 shortly but the core commit is only > scheduled for 1.13.1 so the true fix won't take effect until then. > > Props to Tomer Brisker for working on the fixes! > Just a reminder that since 1.13.1 has been released, this should be working correctly now (looks ok on my prod instance, certainly). 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] Using Foreman as CMDB
Everyone might roll their eyes at me for this, but I'm evaluating using The Foreman not just as an ENC and "source of truth", but also towards an organizational CMDB. I'd like to be able to associate network gear with it as well (switches, firewalls, load balancers) - has anybody done this? I created some "unmanaged" resources, but it seems quite cludgy. Is there a plugin available? -- 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: Repository structure
Hi Custom repos are all repos which are not Red Hat official repos. So, these are repos which you had created yourself. I don't know if you can delete them. And why do you want to delete them? Edgars ceturtdiena, 2016. gada 27. oktobris 12:15:46 UTC+2, Denis Müller rakstīja: > > Hi, > > im trying to understand how katello/pulp manage directory structure. > > I created > > Organization: Microcorp > Lifecycle Environemt: Library > Content View:default > Product:centosos-7-x86_64 > repo: updates > > If i publish it over http im getting on fs: > > > /var/lib/pulp/published/yum/http/repos/Microcorp/Library/default/*custom* > /centos-7-x86_64/updates/ > > What is custom and how i delete it? > > Greets, > Denis > -- 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] Repository structure
Hi, im trying to understand how katello/pulp manage directory structure. I created Organization: Microcorp Lifecycle Environemt: Library Content View:default Product:centosos-7-x86_64 repo: updates If i publish it over http im getting on fs: /var/lib/pulp/published/yum/http/repos/Microcorp/Library/default/*custom* /centos-7-x86_64/updates/ What is custom and how i delete it? Greets, Denis -- 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: LDAP users not showing up, partially functional
Hi Jason I have the same issue. I cannot see LDAP users in web gui. The only way to get them show up is give them admin privilege with hammer, like this hammer user update --admin true --id 10 where 10 is user id. Only then they show up. Edgars trešdiena, 2016. gada 26. oktobris 20:38:06 UTC+2, Jason B. Nance rakstīja: > > Hello, > > I have configured my Katello 3.1 instance to use my FreeIPA instance for > LDAP. I selected "automatically create accounts in Foreman" and "Usergroup > sync". LDAP users don't show up under Administer -> Users. They are able > to login and manage CVs and such, but cannot set any of their user > preferences (such as default Org), and cannot execute remote commands. I > have granted these users administrative privileges via an LDAP group. > > Any ideas as to how to clear this up? > > Thanks, > > j > > -- 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] using global parameters in smart class parameter
On 27/10/16 06:48, francesc bassas wrote: > Hi, > I'm using Foreman 1.12 with puppet 3.8.7 > I've defined a global parameter which is a list of IP's and I would like > to use it as a value in a smart class parameter. Is this possible? > How can I reference to it? I mean if the parameter is "ips_list" I've > tried $::ips_list, but it does not work. > Excuse me if the answer is trivial. <%= @host.params['ips_list'] %> should work. http://projects.theforeman.org/projects/foreman/wiki/TemplateWriting#Host--or-Hostgroup-parameters, other macros on that page should also work in the context of a smart class parameter or global parameter. -- Dominic Cleal domi...@cleal.org -- 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.
