Bug 1195777
| Summary: | [doc] Update Discovery chapter in User Guide - Changed in 6.1 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | Docs User Guide | Assignee: | David O'Brien <daobrien> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | adstrong, bkearney, daobrien, dlackey, hhudgeon, lcarlon, lzap, mmccune, sfolkwil |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-13 14:41:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Lukas Zapletal
2015-02-24 14:32:34 UTC
Using the KCS and not the googledoc as source. Re extensions: Typically you put extensions as ZIP files onto remote server, but in case of network drivers, you can "burn" them into the image. This is not yet properly documented, I will put it the README. Filed an issue for this, keep the link https://github.com/theforeman/foreman-discovery-image to if you can. http://projects.theforeman.org/issues/11852 The correct form is: facts.ipaddress_eth1 ~ "192.168.*" Note the star char! This chapter is currently undergoing various patches and clean-up prior to async release. swadeley and Clayton are also working on something in a branch (don't know what, exactly, need to check). > Line 525 and comment #20 and 21: The question about the directory is there
> are files which presumably should have content -- Ruby files, Shell scripts
> -- which are not explained. Is there a template that customers should copy?
> If not, then where do they get 01_zip.sh or test.rb or the .so files? A
> little more description about that directory and the files in it (like,
> where they come from or what they should contain) would be helpful.
Lukas,
can you comment on this request please? We'd like to get this in for async release if possible.
thanks
Hello, there is a template but I believe it is not worth including as I think it should be clear that these are scripts or libraries or Ruby libraries that needs to be there. Content is up to the reader. Anyway we have this: https://github.com/theforeman/foreman-discovery-image/tree/master/example_zip Re: "required params": All parameters which are flagged as required on the New Host provisioning form. (E.g. have the * icon): Name, Puppet Environment, Subnet/Domain, Operation System (whole tab). (In reply to Lukas Zapletal from comment #29) > Hello, > > there is a template but I believe it is not worth including as I think it > should be clear that these are scripts or libraries or Ruby libraries that > needs to be there. Content is up to the reader. Anyway we have this: > > https://github.com/theforeman/foreman-discovery-image/tree/master/example_zip > > Re: "required params": All parameters which are flagged as required on the > New Host provisioning form. (E.g. have the * icon): Name, Puppet > Environment, Subnet/Domain, Operation System (whole tab). Thanks Lukas I'll leave the section as-is for now; we might have time to review how to use the upstream link and content in next sprint/async. We don't *usually* refer customers to these places, but exceptions happen where necessary. I rephrased the part about mandatory args just to indicate that those with * are required, instead of trying to list them. Anything else that needs addressing in this section (missing tags and whatever) will have to go into async2+. It's publishable at this stage. |