Bug 1331539

Summary:	[RFE] Please add instructions on how to mirror oval files from Red Hat.
Product:	Red Hat Satellite	Reporter:	Bryan Kearney <bkearney>
Component:	Documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Andrew Dahms <adahms>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	adahms, bkearney, dmacpher, mpreisle
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-11 04:28:19 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:

Description Bryan Kearney 2016-04-28 18:11:24 UTC

This is supoprted with Satellite 6.2 now:


1) Create a product called "Oval Files"
2) Create a repo of type "file" called Red Hat. Make the upstream url be https://www.redhat.com/security/data/oval/. Set the repo to be exposed via http
3) Sync the repo
4) $$PROFIT

At this point you have a local http repo of the oval files. Create a sync plan and it will update at your convenience. This repo can be promoted through environments in the same way as any other content.

Comment 1 Dan Macpherson 2016-04-29 01:15:33 UTC

This could be applied in two locations:

a) Content Management Guide
b) Host Configuration Guide (Chapter 5. Security Compliance Management)

It could also be something to document in both guides, not just in one guide.

@adahms, did you have a preference for what we should do? I'm happy to take this BZ on.

Comment 2 Andrew Dahms 2016-04-29 01:40:49 UTC

Hi Dan,

At a glance, this looks like it would be a good candidate for the Content Management Guide, but what do you think?

If needed, we can always link to it from the chapter on security compliance management, and when this content is also converted into AsciiDoc, we can explore having a single-sourced version of the content in both guides then if that would be appropriate.

Happy for you to take this on as well, and we can verify and publish the changes as soon as they're in.

Kind regards,

Andrew

Comment 3 Dan Macpherson 2016-04-29 03:03:01 UTC

Sure, I'll add to the CMG. It's content and can be synchronized, so it makes sense that the CMG is where it belongs.

Comment 7 Dan Macpherson 2016-05-06 03:24:42 UTC

The bugs were included as part of technical review of the full guide. In addition, the guide has been peer reviewed.

Setting the QA contact to adahms and flipping the status to ON_QA.

Comment 9 Dan Macpherson 2016-05-09 15:39:29 UTC

Sorry, this got caught in a bulk bug update. Switching back to ASSIGNED.

Comment 11 Andrew Dahms 2016-05-11 04:13:25 UTC

Looks good to me.

Moving to VERIFIED.

Comment 12 Andrew Dahms 2016-05-11 04:28:19 UTC

This content is now live on the Customer Portal.

Closing.