Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 973589 - [RFE] Provide PXE Server Information via API
Summary: [RFE] Provide PXE Server Information via API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-12 09:21 UTC by james labocki
Modified: 2016-10-07 13:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-07 13:16:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description james labocki 2013-06-12 09:21:33 UTC 
This is a request to provide information about the PXE server via Satellite's API if it is being utilized. This information is required by CloudForms and could assist with automatic discovery and configuration of Satellite as a provisioning method within CloudForms. Information required includes:

Name: 

Access URL - http accessible address of PXE server.
URI - for SMB or NFS access.
PXE Directory - Directory of PXE server.
Windows Images Directory - Directory containing windows images.
Customization Directory - Directory where PXE records can be written.
Filename - menu file name for PXE server.
Comment 1 RHEL Program Management 2013-06-12 18:33:17 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Ohad Levy 2013-06-24 06:34:48 UTC 
I'm not sure if it makes a lot of sense to expose this information directly via the api.

In Sat6 arch, we support multiple pxe servers (e.g. across locations) and the content and settings (e.g. boot files / pxe config files) are auto generated and maintained.

exposing the information and allow to change it directly (e.g. not part of a bigger os / host life cycle) is not advised.

Can you elaborate more on how you would like to consume that information?

thanks.
Comment 4 james labocki 2013-06-24 18:59:04 UTC 
The thought is that provisioning may be initiated from a system that is not Satellite, but want to utilize the underlying PXE server within Satellite to perform the provisioning. 

Where SystemX is a system that wants to utilize the PXE server within Satellite to provision a workload and SystemY is the provision system it seems this could be done by:

Scenario A
 1. SystemX ----Discover----> Satellite6
 2. SystemX ----Write-------> Appropriate PXE Server
 3. SystemX --Provision VM--> Virtualization/IaaS/MaaS Provider
 4. SystemY --Register -----> Satellite6

Scenario B
 1. SystemX    ----Request-----> Satellite6
 2. Satellite6 ---Write--------> Appropriate PXE Server
 3. Satellite6 ---Acknowledge--> SystemX
 4. SystemX    --Provision VM--> Virutalization/IaaS/MaaS Provider
 5. SystemY    --Register -----> Satellite6

At my first analysis it seems like Scenario A might be beneficial in that SystemX doesn't need to wait for a response from Satellite 6 in order to utilize the PXE server provided.

How would you envision SystemX provisioning via Satellite6?
Comment 5 Mike McCune 2013-08-16 18:00:56 UTC 
getting rid of 6.0.0 version since that doesn't exist
Comment 6 Mike McCune 2013-08-26 15:23:03 UTC 
moving to
Comment 8 Bryan Kearney 2016-10-07 13:16:13 UTC 
Closing out an old bug. If this is still needed, please feel free to re-open with additional information.
Note You need to log in before you can comment on or make changes to this bug.