Bug 1038295

Summary:	[RFE]Add Windows client support to Beaker
Product:	[Retired] Beaker	Reporter:	Dmitri Pal <dpal>
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, qwan, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1040246 (view as bug list)		Environment:
Last Closed:	2020-11-16 20:28:45 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:	1040245
Bug Blocks:	1040246

Description Dmitri Pal 2013-12-04 20:31:31 UTC

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-06 07:58:30 UTC

Beaker's native provisioning capability is kickstart based and hence closely coupled to the Anaconda installer.

However, we're planning to update the existing (but flawed [1]) dynamic provisioning capability to use OpenStack as the back end: http://beaker-project.org/dev/tech-roadmap.html#openstack-based-provisioning

The initial iteration of the integration will likely just bootstrap Anaconda and use the existing kickstart based provisioning (hopefully we can reuse some of the bootstrapping concepts from https://github.com/redhat-openstack/image-building-poc)

The next iteration will then aim to leverage cloud_init to permit image based installs (likely with only a subset of Beaker's full functionality, and likely still limited to POSIX systems).

After we can provision arbitrary POSIX systems in OpenStack, then we'd move to support provisioning non-POSIX systems.

Finally, we'd look at the network isolation features of OpenStack, that should let us provision systems for DHCP/DNS/NTP/AD testing without upsetting the rest of the lab network.

[1] http://beaker-project.org/docs/admin-guide/ovirt.html

Comment 4 Nick Coghlan 2013-12-11 03:01:22 UTC

I created a couple of blocker bugs for this, related to the OpenStack integration described above - one to allow kickstart based provisioning in OpenStack, and a second to allow image based provisioning of Linux distros.

This RFE would then extend the image based provisioning support to Windows clients.

Active Directory support is potentially more challenging, since AD servers tend to be quite possessive in regards to their role on the network, so I have cloned that aspect as a separate bug (1040246).

Comment 5 Nick Coghlan 2013-12-17 08:12:50 UTC

It occurs to me that license management could get interesting with this feature...

Comment 6 Dmitri Pal 2013-12-19 01:21:18 UTC

(In reply to Nick Coghlan from comment #5)
> It occurs to me that license management could get interesting with this
> feature...

MSDN licenses are per person so as long as the user running (launching) the test in beaker has the MSDN license assigned to him we are covered.

Comment 7 Nick Coghlan 2013-12-19 02:14:48 UTC

I guess it's also something that is really outside Beaker's scope - we'll be retrieving the images from Glance, so from Beaker's point of view, it will just be a named image, we won't necessarily know what OS it is running.