[foreman-users] Re: Image Provisioning using VMware template

[Francois Herbert]

Sorry, didn't realise you wanted to deploy a linux template. I only deploy 
windows using a template, linux I deploy using pxe/kickstart.

On Friday, November 11, 2016 at 6:04:35 PM UTC+13, Unix SA wrote:
>
> Hello, i came across that, but that's windows, do i need same thing 
> applied to Linux ? 
>
> Thanks,
> DJ
>
> On Friday, 11 November 2016 02:04:29 UTC+5:30, Francois Herbert wrote:
>>
>> Have a look at a post I wrote a while ago, still works for me now: 
>> http://www.herbert.org.nz/?p=245
>>
>> Cheers
>> Francois
>>
>> On Thursday, November 10, 2016 at 9:40:54 PM UTC+13, opr...@redhat.com 
>> wrote:
>>>
>>> Hi,
>>> from my limited experience with VMware, I can tell that 
>>> "globalIPSettings" is a required key in a customization config. Adding 
>>> something like:
>>>
>>> globalIPSettings:
>>>   dnsSuffixList: [<%= @host.domain %>]
>>>
>>> into your template might do the trick. There is also a thread [1] 
>>> discussing image provisioning on VMware which might be useful.
>>>
>>> Hope this helps,
>>> O.
>>>
>>> [1] https://groups.google.com/forum/#!topic/foreman-users/uRfEnTFcgdk
>>>
>>

-- 
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: Image Provisioning using VMware template

[Unix SA]

Hello, i came across that, but that's windows, do i need same thing applied 
to Linux ? 

Thanks,
DJ

On Friday, 11 November 2016 02:04:29 UTC+5:30, Francois Herbert wrote:
>
> Have a look at a post I wrote a while ago, still works for me now: 
> http://www.herbert.org.nz/?p=245
>
> Cheers
> Francois
>
> On Thursday, November 10, 2016 at 9:40:54 PM UTC+13, opr...@redhat.com 
> wrote:
>>
>> Hi,
>> from my limited experience with VMware, I can tell that 
>> "globalIPSettings" is a required key in a customization config. Adding 
>> something like:
>>
>> globalIPSettings:
>>   dnsSuffixList: [<%= @host.domain %>]
>>
>> into your template might do the trick. There is also a thread [1] 
>> discussing image provisioning on VMware which might be useful.
>>
>> Hope this helps,
>> O.
>>
>> [1] https://groups.google.com/forum/#!topic/foreman-users/uRfEnTFcgdk
>>
>

-- 
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] 1.13.1 - Host deletion DHCP/DNS error

[Jack Watroba]

I have a foreman 1.13.1 server and a smart-proxy 1.13.1 server which 
connects to our MS 2008R2 DNS and DHCP server. For the most part everything 
is working fine except for when deleting a host from foreman, the first 
attempt fails with this error on the UI: "Failed to destroy the record"

In the logs on the foreman server, I see this:

2016-11-10 23:51:31 0e78cd72 [app] [I] Delete DHCP reservation for 
example.example.com- xx:xx:xx:xx:xx:xx
2016-11-10 23:51:34 0e78cd72 [app] [W] Failed to parse response:
 | Changed the current scope context to x.x.x.x scope.
 |
 | Command completed successfully.
 |  -> 757: unexpected token at 'Changed the current scope context to 
x.x.x.x scope.
 |
 | Command completed successfully.
 | '
2016-11-10 23:51:34 0e78cd72 [app] [I] Add DNS PTR record for 
x.x.x.x/example.example.com
2016-11-10 23:51:34 0e78cd72 [app] [I] Add DNS A record for 
example.example.com/x.x.x.x
2016-11-10 23:51:35 0e78cd72 [app] [W] Action failed
 | ActiveRecord::RecordNotDestroyed: Failed to destroy the record


On the proxy server I see that it deletes the DHCP reservation, and then 
what's really weird is that then it says that it creates the DNS entry...

D, [2016-11-10T15:51:34.560903 #828] DEBUG -- : Removed DHCP reservation 
for example.example.com => x.x.x.x - xx:xx:xx:xx:xx:xx
..
D, [2016-11-10T15:51:34.841707 #828] DEBUG -- : Added PTR entry 
x.x.x.x.in-addr.arpa => example.example.com
..
D, [2016-11-10T15:51:35.091310 #828] DEBUG -- : Added DNS entry 
example.example.com => x.x.x.x


If I then go back and attempt to delete the host in Foreman again, it 
deletes it without any errors.  

Has anyone else seen this behavior? The strangest part of this to me is 
that it adds DNS records on a host delete and then fails trying to delete 
them, or so it seems.

I also have a foreman 1.11 server and smart proxy that are setup the exact 
same way with the exact same config and it works fine and never runs into 
this problem. 

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.

Re: [foreman-users] Naming products and repos?

['Jason B. Nance' via Foreman users]

Here are a couple screen shots that show the layout of one of my Katello 
instances: 

Products: 

https://tresgeek.net/cloud/index.php/s/RgYDpYl09ePjqWm 

Content Views: 

https://tresgeek.net/cloud/index.php/s/MByLW0Ho99rIFOS 

(this instance doesn't have OEL, but it's pretty much the same as CentOS with 
some minor differences) 

I, too, struggled with how to organize my products. I landed on this for a 
couple reasons: 

1) I knew I was going to need/use CVs 
2) Grouping by vendor/upstream felt "right" 

Why CVs, you ask? For me it is to maintain consistency and give a path for 
rollbacks. Product repos are raw and versionless. You get what you get when you 
get it. CVs are basically snapshots or moments in time (handled via symlinks 
and database info). 

I classify systems as either non-prod or prod, so my process looks like this: 

Product repos are updated nightly. 
CV version is created and prompted to "non-prod" the day before non-prod 
patching. 
Non-prod systems patched. 
A few weeks later, that same CV version is prompted to "production" the day 
before production patching. 
Production systems patched. 

That gives me a few weeks of bake-in time for updates before they go to 
production. It also means that a server installed on Friday as has the same 
versions of the same packages that were installed on a server of the same 
environment on Monday. 
If an issue is discovered after patching, I can roll everything back to the 
previous known good CV version. 

I also make use of Composite Content Views, which are just a collection of 
specific versions of CVs. CCVs allow a couple things to happen: 

1) Share the same version of a CV across multiple different distros (for 
example, EPEL 7 is used by both CentOS 7 and OEL 7) 
2) Allows a "sub" CV version to get wonky without breaking the whole process 

Some elaboration on #2... My Katello box isn't always the happiest of things. 
Sometimes CV version creation/promotion fails. If it's the day before patching 
and my Software Collections CV version create/promote is failing and I don't 
have time to fix it, I don't want to have to delay patching (especially for 
such a "minor" repo in my environment). So with a CCV I can just use the last 
known good CV version of SCL in my CCV. 

There's a bit more to this as how CVs, lifecycle envs, host groups, and 
activate keys all relate, but I'll stop the fire hose here for now. :) 

TL;DR: CVs are about maintaining consistency and content flow through your 
environment (IMO). 

Clear as mud? 

j 



From: "Alan Evans"  
To: "Foreman users"  
Cc: ja...@tresgeek.net 
Sent: Thursday, November 10, 2016 12:41:04 PM 
Subject: Re: [foreman-users] Naming products and repos? 

Jason, 

I have considered going to a single "CentOS" product. I still haven't wrapped 
my head around content views. It seems like a needless layer of abstraction but 
maybe I just don't get it yet. 

Thanks for your thoughts, this is exactly the discussion I was hoping to have. 

-Alan 

On Wednesday, November 9, 2016 at 6:45:37 PM UTC-7, Jason B. Nance wrote: 


HI Alan, 

Regarding products, I organize by the upstream/vendor not by versions. For 
example, I have CentOS, OEL, and EPEL products. My content views are where I 
split up stuff into versions and such. 

Your examples look good to me. 

j 



From: "Alan Evans" < [ javascript-blocked: | alanw...@gmail.com ] > 
To: "Foreman users" < [ javascript-blocked: | forema...@googlegroups.com ] > 
Sent: Wednesday, November 9, 2016 5:19:54 PM 
Subject: [foreman-users] Naming products and repos? 

Is there any guide or are there any recommendations for naming/labeling 
products and repos? 

Is CentOS, CentOS 6, CentOS 6 x86_64 a product? 
What are people doing for CentOS/EPEL? 

If left to it's own devices katello just replaces spaces with underscores for 
product/repo labels. 

What about other "products?" 
Is Katello a product? Katello 3.2? 
Puppet? Puppet PC1? 
Puppet Enterprise? Puppet Enterprise 2016.4? or is the product "Puppet" with 
repos for the versions? 

I am leaning toward: 

Product: CentOS 6 (centos-6) 
Repo: CentOS 6 x86_64 OS - centos-6-x86_64-os = [ 
http://mirror.centos.org/centos/6/os/x86_64/ | 
http://mirror.centos.org/centos/6/os/x86_64/ ] 
Repo: CentOS 6 x86_64 Updates - centos-6-x86_64-updates = [ 
http://mirror.centos.org/centos/6/updates/x86_64/ | 
http://mirror.centos.org/centos/6/updates/x86_64/ ] 
- or more generally - 
Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = lower( [ 
http://mirror.centos.org/centos/$major/$repo/$arch/ | 
http://mirror.centos.org/centos/$major/$repo/$arch/ ] ) 

Product CentOS 7 (centos-7) 
Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = lower( [ 
http://mirror.centos.org/centos/$major/$repo/$arch/ | 
http://mirror.centos.org/centos/$major/$repo/$arch/ ] ) 

Product EPEL 6 (epel-6) 
Repo: EPEL $major $arch - lower(epel-$major-$arch) = [ 

[foreman-users] Custom variables in templates

[Alexander Rilik]

Hello,

I would like to run Foreman in a distributed, multi-site setup. Each site 
has a dedicated dhcp+tftp smart proxy, including a Windows WDS host.
I am in need to provide a "boot from WDS" menu item in the PXE menu. That 
is easy, but each proxy should provide a PXE menu customized to point at 
the site-specific WDS.

Two options I thought of:

   - DNS based solution, with same url but changing IP by site
   - A variable (@wds_server_ip) in the PXE file, associated to a host 
   group, different per site

Now, this second option is tempting but I can't figure out how to make it 
happen: I have been kindly pointed at the Functions/Macros section of the 
wiki. Sadly, host/hostgroup specific parameters don't apply to global PXE 
templates (see here 
http://projects.theforeman.org/projects/foreman/wiki/templatewriting#PXE-Menus).

I would love to find a solution to this, since also the Discovery PXE 
snippet has an hardcoded smart-proxy value, and I need that to be dynamic 
per site.

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.

[foreman-users] Re: Image Provisioning using VMware template

[Francois Herbert]

Have a look at a post I wrote a while ago, still works for me now: 
http://www.herbert.org.nz/?p=245

Cheers
Francois

On Thursday, November 10, 2016 at 9:40:54 PM UTC+13, opr...@redhat.com 
wrote:
>
> Hi,
> from my limited experience with VMware, I can tell that "globalIPSettings" 
> is a required key in a customization config. Adding something like:
>
> globalIPSettings:
>   dnsSuffixList: [<%= @host.domain %>]
>
> into your template might do the trick. There is also a thread [1] 
> discussing image provisioning on VMware which might be useful.
>
> Hope this helps,
> O.
>
> [1] https://groups.google.com/forum/#!topic/foreman-users/uRfEnTFcgdk
>

-- 
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] discovery failed after added new hostgroup

[Greg Sutcliffe]

Sounds like the OS you've associated with that hostgroup isn't fully
configured for provisioning - check it has an architecture, at least one
partition layout, at least one installation media, and a set of templates.

-- 
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] Naming products and repos?

[Alan Evans]

Greg,

Thank you for your thoughts.  This is the kind of discussion I was hoping 
for.

I considered using (and may still) a single "CentOS" repo and use 
activation keys to get boxes assigned to the right repos.  As I mentioned 
to Jason I am still not clear on content-views but that is another topic.

On Wednesday, November 9, 2016 at 9:50:42 PM UTC-7, Greg Swift wrote:
>
> Here's a run down of how i've tried approaching this, then I'll explain 
> why i've heard complaints from some users
>
>
> Product: CentOS
> Repos:
>   - el6-64-os
>   - el6-64-updates
>   - el6-64-extras
>   - el7-64-os
>   - el7-64-updates
>   - el7-64-extras
>

Seeing it actually done this way I am liking it a lot better.
 

> Product: EPEL
> Repos:
>   - el6-64
>   - el7-64
>
> Product: Internal
> Repos:
>   - el6-noarch-product1
>   - el6-noarch-product2
>   - el7-noarch-product1
>   - el7-noarch-product2
>
> So on a rhel 6 box via yum the repos end up being named like this:
>
> ORG-CentOS-el6-64-os
> ORG-CentOS-el6-64-updates
> ORG-EPEL-el6-64
> ORG-Internal-el6-noarch-product1
>
> What ends up being the problem is the katello UI.  In several places you 
> are only given a list of repositories to select from, so based on the above 
> you get a list like this:
>
> Repos:
>   - el6-64-os
>   - el6-64-updates
>   - el6-64-extras
>   - el7-64-os
>   - el7-64-updates
>   - el7-64-extras
>   - el6-64
>   - el7-64
>   - el6-noarch-product1
>   - el6-noarch-product2
>   - el7-noarch-product1
>   - el7-noarch-product2
>
> So I have users that want to try different routes but that means some 
> interesting results, like these names in yum:
>
> ORG-CentOS-centos-6-64-os
> ORG-CentOS-centos-6-64-updates
> ORG-EPEL-epel-6-64
> ORG-Internal-el6-noarch-product1
>
> which is just duplication. Or 
>

Yeah I am not happy with having duplication all over like this either.  The 
OCD part of me ticks when I do it or think of doing it.  But yeah you are 
right, if you have only  the repo name to look at you are missing some 
context.
 

>
> ORG-Linux-centos-6-64-os
> ORG-Linux-centos-6-64-updates
> ORG-Linux-epel-6-64
> ORG-Internal-el6-noarch-product1
>
> Which loads even more things into a single product, which i'm not a fan of 
> but maybe it doesn't matter.
>

Yeah I would agree here.  This would be overloading the "Linux" product and 
I think make things more confusing and complicated in the long run.
 

>
> Another concern that was raised was managing the repo selection in 
> activation keys.  By grouping EL6&7 in the same Product and relying on 
> enabling/disabling in the activation keys it can be slightly annoying 
> managing a bunch of keys. Where as if we move to a Product like CentOS6, 
> then there is no enabling/disabling of repos to deal with.  but we wrote a 
> simple bas function around that... but its definitely not ideal.
>
> So Far i'm leaning towards not changing from the first schema I mentioned, 
> but the UI is definitely annoying with it.
>
>
You could file a feature request to include the product name or label when 
displaying repos.  Maybe: "$repo_name ($product_name)" or "$product_name - 
$repo_name", the second of which has the interesting side effect of 
grouping things by product if sorted by name.  And where labels are 
concerned display them like they are used in pulp.  Pulp doesn't even have 
a conept of product, it just manages repos so pulp repo names just become 
"$product_label" + "_" + "$repo_label".
 

> -greg
>
> On Wed, Nov 9, 2016 at 7:45 PM 'Jason B. Nance' via Foreman users <
> forema...@googlegroups.com > wrote:
>
>> HI Alan,
>>
>> Regarding products, I organize by the upstream/vendor not by versions.  
>> For example, I have CentOS, OEL, and EPEL products.  My content views are 
>> where I split up stuff into versions and such.
>>
>> Your examples look good to me.
>>
>> j
>>
>>
>> --
>> *From: *"Alan Evans" 
>> *To: *"Foreman users" 
>> *Sent: *Wednesday, November 9, 2016 5:19:54 PM
>> *Subject: *[foreman-users] Naming products and repos?
>>
>> Is there any guide or are there any recommendations for naming/labeling 
>> products and repos?
>>
>> Is CentOS, CentOS 6, CentOS 6 x86_64 a product?
>> What are people doing for CentOS/EPEL?
>>
>> If left to it's own devices katello just replaces spaces with underscores 
>> for product/repo labels.
>>
>> What about other "products?"
>>   Is Katello a product?  Katello 3.2?
>>   Puppet?  Puppet PC1?
>>   Puppet Enterprise? Puppet Enterprise 2016.4?  or is the product 
>> "Puppet" with repos for the versions?
>>
>> I am leaning toward:
>>
>> Product: CentOS 6 (centos-6)
>>   Repo: CentOS 6 x86_64 OS - centos-6-x86_64-os = 
>> http://mirror.centos.org/centos/6/os/x86_64/
>>   Repo: CentOS 6 x86_64 Updates - centos-6-x86_64-updates = 
>> http://mirror.centos.org/centos/6/updates/x86_64/
>>   - or more generally -
>>   Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = 
>> 

Re: [foreman-users] Naming products and repos?

[Alan Evans]

Jason,

I have considered going to a single "CentOS" product.  I still haven't 
wrapped my head around content views.  It seems like a needless layer of 
abstraction but maybe I just don't get it yet.

Thanks for your thoughts, this is exactly the discussion I was hoping to 
have.

-Alan

On Wednesday, November 9, 2016 at 6:45:37 PM UTC-7, Jason B. Nance wrote:
>
> HI Alan,
>
> Regarding products, I organize by the upstream/vendor not by versions. 
>  For example, I have CentOS, OEL, and EPEL products.  My content views are 
> where I split up stuff into versions and such.
>
> Your examples look good to me.
>
> j
>
>
> --
> *From: *"Alan Evans" 
> *To: *"Foreman users" 
> *Sent: *Wednesday, November 9, 2016 5:19:54 PM
> *Subject: *[foreman-users] Naming products and repos?
>
> Is there any guide or are there any recommendations for naming/labeling 
> products and repos?
>
> Is CentOS, CentOS 6, CentOS 6 x86_64 a product?
> What are people doing for CentOS/EPEL?
>
> If left to it's own devices katello just replaces spaces with underscores 
> for product/repo labels.
>
> What about other "products?"
>   Is Katello a product?  Katello 3.2?
>   Puppet?  Puppet PC1?
>   Puppet Enterprise? Puppet Enterprise 2016.4?  or is the product "Puppet" 
> with repos for the versions?
>
> I am leaning toward:
>
> Product: CentOS 6 (centos-6)
>   Repo: CentOS 6 x86_64 OS - centos-6-x86_64-os = 
> http://mirror.centos.org/centos/6/os/x86_64/
>   Repo: CentOS 6 x86_64 Updates - centos-6-x86_64-updates = 
> http://mirror.centos.org/centos/6/updates/x86_64/
>   - or more generally -
>   Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = 
> lower(http://mirror.centos.org/centos/$major/$repo/$arch/)
>
> Product CentOS 7 (centos-7)
>   Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = 
> lower(http://mirror.centos.org/centos/$major/$repo/$arch/)
>
> Product EPEL 6 (epel-6)
>   Repo: EPEL $major $arch - lower(epel-$major-$arch) = 
> http://dl.fedoraproject.org/pub/epel/$major/$arch/
>
> Puppet Enterprise (puppet-enterprise)
>   Repo: Puppet Enterprise 3.7.2 EL7 x86_64 - 
> puppet-enterprise-3.7.2-el-7-x86_64 = 
> https://puppet-master:8140/packages/3.7.2/el-7-x86_64
>   Repo: Puppet Enterprise 2016.4 EL7 x86_64 - 
> puppet-enterprise-2016.4-el-7-x86_64 = 
> https://puppet-master:8140/packages/2016.4/el-7-x86_64
>
> Thoughts?
> -Alan
>
> -- 
> 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-user...@googlegroups.com .
> To post to this group, send email to forema...@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] [katello] modifying repository attributes in content views

['Jason B. Nance' via Foreman users]

On Thu, Nov 10, 2016 at 12:24 PM, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 



Hi Tom, 

I don't believe that download policy is an attribute of a content view, only of 
a product repository, as packages aren't really owned by CVs, they are just 
referenced by CVs. So this change would really be at the product/repo level and 
affect consumers of that repo. You should be able to change the download policy 
of a repository at any time regardless of whether it is referenced via a CV or 
not and then initiate a sync (such as if you are moving from on demand to 
immediate). 

Sorry if I'm not following you, 

j 




> Each version of a content view has a reference to its own version of a 
> product repo. So for CV-1.0, there is a repo, and for CV-2.0 there is a repo. 
> My goal would be to allow the attributes of these separate repos to be 
> managed separately. How that management is presented to user user (eg. is it 
> tied to the content view, the lifecycle environment, or that version of a 
> repo) would be worth discussing. I'm interested, though, if anyone else has 
> seen the need for something like this. 

In your example of download policies how would this work, though? Each CV 
doesn't have its own copy of a package, right? I thought that CVs were 
basically just symlinks and database entries and that pulp was unaware of them. 

I don't mean to derail and I'm sorry if I'm focusing too much on one specific 
example. You noted download policy and http/https publishing. Is that where you 
would draw the line or would you also include mirror on sync, metadata, etc? 

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] [katello] modifying repository attributes in content views

[Tom McKay]

On Thu, Nov 10, 2016 at 12:24 PM, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> Hi Tom,
>
> I don't believe that download policy is an attribute of a content view,
> only of a product repository, as packages aren't really owned by CVs, they
> are just referenced by CVs.  So this change would really be at the
> product/repo level and affect consumers of that repo.  You should be able
> to change the download policy of a repository at any time regardless of
> whether it is referenced via a CV or not and then initiate a sync (such as
> if you are moving from on demand to immediate).
>
> Sorry if I'm not following you,
>
> j
>
>
Each version of a content view has a reference to its own version of a
product repo. So for CV-1.0, there is a repo, and for CV-2.0 there is a
repo. My goal would be to allow the attributes of these separate repos to
be managed separately. How that management is presented to user user (eg.
is it tied to the content view, the lifecycle environment, or that version
of a repo) would be worth discussing. I'm interested, though, if anyone
else has seen the need for something like this.


>
> --
> *From: *"Tom McKay" 
> *To: *foreman-users@googlegroups.com
> *Sent: *Thursday, November 10, 2016 10:20:53 AM
> *Subject: *[foreman-users] [katello] modifying repository attributes in
> content views
>
> There are times when I wish I could edit the attributes of a repository in
> a specific content view and am wondering how hard this would be.
>
> For example, I sync RHEL-7.2 with a download policy of on demand. From
> there I craft a content view with specific filters and publish and promote
> it to my production lifecycle environment. At that point, I'd like to use
> inter-server sync (ISS) to export for use in another organization. However,
> ISS does not work with on demand. For my use case, I'd like to switch the
> download policy of the specific repo in the product content view to
> immediate, then sync it to pull down all the packages.
>
> Another use case would be creating unprotected custom product repos
> ("Publish via HTTP") but then when they make it to my production
> environment, switching them to protected HTTPS.
>
> Is manipulating aspects of repositories in content views something others
> would find useful? Is this a difficult thing to implement?
>
> --
> 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.
>

-- 
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] [katello] modifying repository attributes in content views

['Jason B. Nance' via Foreman users]

Hi Tom, 

I don't believe that download policy is an attribute of a content view, only of 
a product repository, as packages aren't really owned by CVs, they are just 
referenced by CVs. So this change would really be at the product/repo level and 
affect consumers of that repo. You should be able to change the download policy 
of a repository at any time regardless of whether it is referenced via a CV or 
not and then initiate a sync (such as if you are moving from on demand to 
immediate). 

Sorry if I'm not following you, 

j 



From: "Tom McKay"  
To: foreman-users@googlegroups.com 
Sent: Thursday, November 10, 2016 10:20:53 AM 
Subject: [foreman-users] [katello] modifying repository attributes in content 
views 

There are times when I wish I could edit the attributes of a repository in a 
specific content view and am wondering how hard this would be. 

For example, I sync RHEL-7.2 with a download policy of on demand. From there I 
craft a content view with specific filters and publish and promote it to my 
production lifecycle environment. At that point, I'd like to use inter-server 
sync (ISS) to export for use in another organization. However, ISS does not 
work with on demand. For my use case, I'd like to switch the download policy of 
the specific repo in the product content view to immediate, then sync it to 
pull down all the packages. 

Another use case would be creating unprotected custom product repos ("Publish 
via HTTP") but then when they make it to my production environment, switching 
them to protected HTTPS. 

Is manipulating aspects of repositories in content views something others would 
find useful? Is this a difficult thing to implement? 


-- 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
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.

[foreman-users] Unable to fetch my node definition, but the agent run will continue

[Akash Kaveti]

Hi,

i am facing this issue, when ever I run puppet in agent.

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
{"message":"Server Error: Could not find node 'host.mydomain.com'; cannot 
compile","issue_kind":"RUNTIME_ERROR","stacktrace":["/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:336:in
 
`node_from_request'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:50:in
 
`find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
 
`find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
 
`do_find'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
 
`call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in 
`override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in 
`override'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
 
`call'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in
 
`process'","org/jruby/RubyArray.java:1613:in 
`each'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
 
`process'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
 
`profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
 
`profile'","/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
 
`process'","file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
 
`handleRequest'","Puppet$$Server$$Master_1033412677.gen:13:in 
`handleRequest'","request_handler_core.clj:273:in 
`invoke'","jruby_request.clj:46:in `invoke'","jruby_request.clj:31:in 
`invoke'","request_handler_service.clj:34:in 
`handle_request'","request_handler.clj:3:in 
`invoke'","request_handler.clj:3:in `invoke'","core.clj:2493:in 
`invoke'","master_core.clj:428:in `invoke'","ring.clj:21:in 
`invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
`invoke'","ring_middleware.clj:284:in `invoke'","core.clj:168:in 
`invoke'","core.clj:211:in `invoke'","core.clj:45:in 
`invoke'","core.clj:343:in `invoke'","core.clj:51:in 
`invoke'","ringutils.clj:86:in `invoke'","legacy_routes_core.clj:114:in 
`invoke'","legacy_routes_core.clj:94:in 
`invoke'","legacy_routes_core.clj:184:in 
`invoke'","legacy_routes_core.clj:151:in `invoke'","ring.clj:21:in 
`invoke'","ring.clj:12:in `invoke'","comidi.clj:249:in 
`invoke'","jetty9_core.clj:424:in 
`invoke'","normalized_uri_helpers.clj:80:in `invoke'"]}
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

my production log, while running puppet agent is,

2016-11-10T07:15:34 [app] [I] Started POST "/api/hosts/facts" for 
192.168.119.44 at 2016-11-10 07:15:34 +0100
2016-11-10T07:15:34 [app] [I] Processing by Api::V2::HostsController#facts 
as JSON
2016-11-10T07:15:34 [app] [I]   Parameters: {"facts"=>"[FILTERED]", 
"name"=>"host.mydomain.com", "certname"=>"host.mydomain.com", "apiv"=>"v2", 
:host=>{"name"=>"host.mydomain.com", "certname"=>"host.mydomain.com"}}
2016-11-10T07:15:34 [app] [I] Import facts for 'host.mydomain.com' 
completed. Added: 0, Updated: 5, Deleted 0 facts
2016-11-10T07:15:34 [app] [I] Completed 201 Created in 96ms (Views: 1.6ms | 
ActiveRecord: 45.4ms)
2016-11-10T07:15:34 [app] [I] Started GET 
"/node/host.mydomain.com?format=yml" for 192.168.119.44 at 2016-11-10 
07:15:34 +0100
2016-11-10T07:15:34 [app] [I] Processing by HostsController#externalNodes 
as YML
2016-11-10T07:15:34 [app] [I]   Parameters: {"name"=>"host.mydomain.com"}
2016-11-10T07:15:34 [app] [I]   Rendered text template (0.0ms)
2016-11-10T07:15:34 [app] [I] Completed 200 OK in 68ms (Views: 0.2ms | 
ActiveRecord: 4.5ms)

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.

[foreman-users] [katello] modifying repository attributes in content views

[Tom McKay]

There are times when I wish I could edit the attributes of a repository in
a specific content view and am wondering how hard this would be.

For example, I sync RHEL-7.2 with a download policy of on demand. From
there I craft a content view with specific filters and publish and promote
it to my production lifecycle environment. At that point, I'd like to use
inter-server sync (ISS) to export for use in another organization. However,
ISS does not work with on demand. For my use case, I'd like to switch the
download policy of the specific repo in the product content view to
immediate, then sync it to pull down all the packages.

Another use case would be creating unprotected custom product repos
("Publish via HTTP") but then when they make it to my production
environment, switching them to protected HTTPS.

Is manipulating aspects of repositories in content views something others
would find useful? Is this a difficult thing to implement?

-- 
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] LDAP auth without SASL

[Justin Davis]

I've got a newly configured Foreman 1.13 instance running on CentOS7. I'm 
able to run ldapsearch from the VM without issues so long as I use the -x 
flag to disable SASL. I am unable to auth through with Foreman using the 
same settings, which leads me to the conclusion that it's using SASL by 
default.

Is there an option to disable SASL in a config file (as it isn't in the web 
GUI), or a reasonable workaround?

Anonymized config is included.

-- 
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] Officially Unofficial Foreman 1.13 on EL6 Now Available

[Greg Sutcliffe]

On 10 November 2016 at 09:57, Roman Plevka  wrote:
>
> Hello there.
> Are the el6 packages built already? I can't find them anywhere in
https://yum.theforeman.org/releases/1.13/

> On Thursday, 27 October 2016 18:01:41 UTC+2, Eric Helms wrote:

> 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).

As Eric says, they're a separate build stream which can be found in the
Katello repos. See
https://fedorapeople.org/groups/katello/releases/yum/foreman/ and
http://www.katello.org/docs/3.2/installation/index.html (Required
Repositories).

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] reboot loop with second nic on vm

[Jorick Astrego]

On 11/09/2016 02:36 PM, Lukas Zapletal wrote:
> I have no idea, it's weird. I just encountered similar behaviour on 
> oVirt.
>
> Can you tell what causes the traditional localboot entry not to work? 
> Is this really adding a NIC? Can you verify what kind of NIC firmware 
> have you configured for both NICs? Are these the same drivers? 
> Different? Can you try with all of the drivers possible?
>
Yes, when I remove the NIC or just unplug it in ovirt, it works. When I 
add one or plug it back in, it works.

The driver used for all NIC's is VIRTIO as they are virtual. It works 
after the timeout with the modifications I did to the pxeboot, oressing 
enter to continue without waiting for the timeout puts it in the loop

With the normal default pxe boot, it still fails no matter which NIC 
driver I use "e1000" or "rtl839".

Very weird, for now I just change the boot order after provisioning

Regards,




> I could not reproduce this on my instance. What version of oVirt do 
> you have?
>
> LZ
>
> On Wed, Nov 9, 2016 at 10:50 AM, Jorick Astrego  > wrote:
>
> Yes local_legacy mode works. Could it be caused by us having the
> discovery plugin installed and enabled on our main foreman and not
> on the capsule?
>
> We want to use discovery for the bare metal but not the VM's in
> ovirt
>
> Regards,
>
> Jorick Astrego
>
> On 11/08/2016 03:44 PM, Lukas Zapletal wrote:
>> So again, you have a provisioned host that is not in "build"
>> mode, you power it off, add new NIC, power on and it does not
>> localboot?
>>
>> In that case, can you try local_legacy mode?
>>
>> 
>> https://github.com/theforeman/community-templates/blob/9769dc89ec5d93193b059aeec3f3f9c80bc160d3/snippets/pxelinux_chainload.erb
>> 
>> 
>>
>> Just edit the PXELinux configuration manually for that host on
>> the TFTP server and reboot if it helps. Just curious if this has
>> anything to do with it. All right, all right, I am shooting in
>> the dark :-)
>>
>> LZ
>>
>> On Mon, Nov 7, 2016 at 2:54 PM, Jorick Astrego
>> > wrote:
>>
>> Hi,
>>
>> Today I'm having something weird again.
>>
>> When I add a second nic either through oVirt or foreman
>> itself and
>> reboot the vm, it gets to the local boot screen and after the
>> counter
>> hits 0 it keeps rebooting.
>>
>> When I unplug or remove the NIC, bootup works fine again.
>>
>>
>>
>>
>>
>>
>> Met vriendelijke groet, With kind regards,
>>
>> Jorick Astrego
>> *
>> Netbulae Virtualization Experts *
>> 
>> 
>> Tel: 053 20 30 270   i...@netbulae.eu
>> Staalsteden 4-3AKvK 08198180
>> Fax: 053 20 30 271   www.netbulae.eu 
>> 7547 TA Enschede BTW NL821234584B01
>>
>>
>> 
>> 
>>
>> -- 
>> 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
>> .
>>
>>
>>
>>
>> -- 
>> Later,
>>   Lukas @lzap Zapletal
>> -- 
>> 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
>> .
>
>
>
>
>
> Met vriendelijke groet, With kind regards,
>
> Jorick Astrego
> *
> Netbulae Virtualization Experts *
> 

Re: [foreman-users] can katello be installed on an existing foreman installation?

[davide]

Hello

sorry for bumping this old thread but the issue still exists since 
http://projects.theforeman.org/issues/7605 is still not implemented.
So my question is: what's the "best practice" for a new Katello 
installation to be integrated as best as possible with an *existing* 
Foreman installation where I've already poured hours of configurations & 
tinkering?

Because right now I've installed (following the Katello manual) a fresh 
katello install on a brand new virtual machine and now I have a full 
foreman install with no data and knowing nothing about my already in place 
Foreman installation.

Thanks!

On Thursday, February 12, 2015 at 10:03:38 AM UTC+1, Cédric Dupont wrote:
>
> Hi,
>
> Thanks for the issue link.
> Here we have the same question. Using foreman since 2 years and happy. We 
> have get a look before at candlepin/pulp/katello but never make the step to 
> use them.
> Now that Katello is a plugin, we will be very happy to deploy them.
> So I understand it's needing time.
>
> To wait, can you give some advice/best practice if people want to start 
> using the candlepin and pulp product for exemple, so that later, we can 
> integrate all these beautiful products together when installing Katello ?
> For exemple : 
> can we start by installing candlepin/pulp and later these ones will just 
> need the installation of a capsule ?
> is there some good advice about what to avoid in configuration of Foreman 
> for later integration of katello plugin ? (thinking hostgroup, puppet 
> environnements ...)
>
> Thanks,
>
> Cédric
>
> 2015-02-08 21:28 GMT+01:00 Eric D Helms 
> :
>
>> Howdy,
>>
>> You cannot currently add Katello to an existing Foreman. Katello requires 
>> a stand-alone installation that provides itself and Foreman. This has been 
>> a popular request and as such is being tracked here - 
>> http://projects.theforeman.org/issues/7605
>>
>> Thanks,
>> Eric
>>
>> On Sun, Feb 8, 2015 at 3:14 PM, Cristian Falcas > > wrote:
>>
>>> Hello,
>>>
>>> Can Katelllo 2.1 be installed inside an existing foreman installation?
>>> I can't find anything to say that this is true.
>>>
>>> Best regards,
>>> Cristian Falcas
>>>
>>> --
>>> 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-user...@googlegroups.com .
>>> To post to this group, send email to forema...@googlegroups.com 
>>> .
>>> Visit this group at http://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-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com 
>> .
>> Visit this group at http://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.

[foreman-users] nothing to boot, failed to load file or directory in discovery.

[Christian Froestl]

Hi,

I have problems running discovery with katello with PXE boot.
If add a new host, the installation of the os works, but I don't know how 
to use the discovery mode installation.

I already configured the katello server as described in this 
manual: 
https://theforeman.org/plugins/foreman_discovery/7.0/index.html#2.Installation
Katello is working as dns, dhcp, tfptp, realm and discovery proxy. All 
other proxy services beside discovery are working great.

But all I get is the error message, that there is nothing to boot.

Katello Version: 1.12.4
Discovery Proxy enabled for network and active in smart proxy overview.

PXE Linux global template:
<%#
kind: PXELinux
name: PXELinux global default
%>

<%# This template has special name (do not change it) and it is used for 
booting unknown hosts. %>

DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT discovery

LABEL discovery
MENU LABEL Foreman Discovery
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso 
rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 
rd.lvm=0 rd.bootif=0 rd.neednet=0 rd.debug=1 nomodeset 
proxy.url=https://katello.example.com:9090 proxy.type=proxy
IPAPPEND 2


Does anyone of you have an idea whats going wrong? Do you need any more 
informations or configs?

-- 
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] Officially Unofficial Foreman 1.13 on EL6 Now Available

[Roman Plevka]

Hello there.
Are the el6 packages built already? I can't find them anywhere in 

https://yum.theforeman.org/releases/1.13/

Thanks

On Thursday, 27 October 2016 18:01:41 UTC+2, Eric Helms wrote:
>
> 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-user...@googlegroups.com .
>> > To post to this group, send email to forema...@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-user...@googlegroups.com .
>> To post to this group, send email to forema...@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.

Re: [foreman-users] creating autosign entries?

[Lukas Zapletal]

Hello, AFAIK Satellite Server don't have such an API, but Smart Proxy
does (you need to have https client certificate tho).

You can also call "puppet ca" on Capsules themselves if that's
feasible as a workaround.

LZ

On Thu, Nov 10, 2016 at 4:23 AM, Jason McMahan
 wrote:
> Good day,
> Has anyone been able to create autosign entries using the foreman api?
> My co-worker and I have been perusing the api docs but we are not 100%
> positive how to do this?
>
> Our thinking is to for now create an api call to foreman, create the
> autosign entry, install the puppet agent on the server then allow
> communication and classifications.
>
> This is a temp fix until we are able to complete the roll out of
> provisioning through foreman.
>
> Thank you
>
> --
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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: Image Provisioning using VMware template

[Unix SA]

Can someone help me with this please?

Thanks,
DJ

-- 
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.