Bug 1040246

Summary:	[RFE]Add Active Directory server support to Beaker
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	azelinka, cbouchar, dpal, qwan, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1038295	Environment:
Last Closed:	2020-11-13 19:29:38 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:
Bug Depends On:	1038295
Bug Blocks:

Description Nick Coghlan 2013-12-11 02:58:04 UTC

Supporting Active Directory servers in Beaker poses additional challenges due to potential interference with the rest of the lab network.

Thus, support Active Directory within Beaker may first require support for OpenStack based network isolation for multihost recipes.


+++ This bug was initially created as a clone of Bug #1038295 +++

Right now there is no way to run AD or Windows 7/8 in beaker.

IPA, SSSD, realmd, RHS, etc. support integration with Active Directory and actively developing new features for this integration. But there is no way to deploy an AD/Windows system on demand to test against. This so far has to be done manually. This RFE requests a repeatable setup for AD in Beaker for integration testing.

The IPA team at least needs access to 2008R2 and 2012 Windows OS and Windows 7 client machines in Beaker. Other teams might need other requirements.

Comment 2 Nick Coghlan 2013-12-17 08:08:53 UTC

It turns out even OpenStack currently has issues with provisioning DHCP servers in a way that avoids confusing other systems on the network.

However, implementing bug 1038295 means making Windows images potentially available through the OpenStack image library.

Armed with that, it may be possible to use libvirt on a bare metal system provisioned in Beaker to set up Active Directory on a local private libvirt network, and do testing there.

We do something similar with dnsmasq in the virtual Fedora quick start for Beaker, so I've created bug 1043789 to track that possibility.

Comment 3 Nick Coghlan 2013-12-17 08:13:22 UTC

Sorry, the end of that last comment wasn't clear. By "that possibility", I was referring to the idea of bypassing Beaker's normal guest provisioning tasks in order to do local testing on an isolated subnet. We know the virtual Fedora instructions work, so that's a simpler test case that trying to add Windows into the mix at the same time.

So once the dnsmasq based Beaker self-test works, and Windows images are available, then it may be possible to do something similar for Active Directory.

Comment 4 Dan Callaghan 2016-03-23 07:10:57 UTC

Now that OpenStack Neutron is well supported and a standard part of OpenStack deployments, including ours, it probably makes more sense to do Active Directory testing inside a Neutron private network rather than trying to implement any libvirt based stuff ourselves.