Bug 1409911

Summary:	[RFE] Add novajoin metadata REST service
Product:	Red Hat OpenStack	Reporter:	Rob Crittenden <rcritten>
Component:	python-novajoin	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED ERRATA	QA Contact:	Prasanth Anbalagan <panbalag>
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	berrange, dasmith, eglynn, fwissing, jschluet, kbasil, kchamart, markmc, mburns, nkinder, nlevinki, oblaut, panbalag, rcritten, rduartes, sbauza, sclewis, sferdjao, sgordon, slinaber, srevivo, vromanso
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-novajoin-1.0.13-0.20170403154656.054c186.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1493557 (view as bug list)		Environment:
Last Closed:	2017-12-13 20:57:54 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:
Bug Depends On:	1401666
Bug Blocks:	1442136, 1469329

Description Rob Crittenden 2017-01-03 21:12:25 UTC

Description of problem:

Clone from https://blueprints.launchpad.net/tripleo/+spec/novajoin

A nova metadata REST service and notification listener to detect when an instance is created and if requested, register it with IPA (freeipa.org) via cloud-init. This will provide the credentials needed for easy certmonger integration using the IPA CA to provision certificates. See also https://blueprints.launchpad.net/tripleo/+spec/tls-via-certmonger

Comment 2 Nathan Kinder 2017-01-09 15:57:06 UTC

*** Bug 1304017 has been marked as a duplicate of this bug. ***

Comment 17 Prasanth Anbalagan 2017-10-02 14:16:31 UTC

Verified using,

https://github.com/openstack/novajoin-tempest-plugin/blob/master/novajoin_tempest_plugin/tests

Comment 20 errata-xmlrpc 2017-12-13 20:57:54 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:3462