Bug 1299663

Summary:	Automatic Change of network of VM after provision
Product:	Red Hat Satellite	Reporter:	Ashfaqur Rahaman <arahaman>
Component:	Provisioning Templates	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.5	CC:	bkearney, daniele, katello-bugs, ktordeur, mhulan
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-06 14:09:28 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:
Bug Blocks:	1353215

Description Ashfaqur Rahaman 2016-01-18 23:29:48 UTC

Description of problem:

Customer has a provisioning network, dedicated to the installation of the Host and VM. 

The VM must have only 1 NIC and can be attached only to the "Provisioning network" OR the "Production network".

After provisioning a VM via satellite (or even via an external tool that can be integrated in the provisioning process) , the product should automatically switch the network from the "Provisioning" to the "Production" vlan.

The desired feature is that Satellite should deal with both the OS and virtualization layer to place the VM in its final configuration.


Version-Release number of selected component (if applicable):
N/A

How reproducible:
N/A

Steps to Reproduce:

 1. We two Vlan - a) provisioning b) Production
 2. Before provisioning you will input of both VLANs information in Satellite.
 3. we will provision the vm in "Provisioning" Network 
 4. Once the vm got provisioned, the vm's Network will change automatically from "provision" --> "Production" 

Here change means - IP, GW, Subnet mask. 

only mac address will be the same.

Actual results:

Currently this feature is not available 
 


Expected results:
VM moved to "Provisioning" network to "Production" network.

Additional info:
N/A

Comment 5 Marek Hulan 2016-04-06 14:09:28 UTC

I think the scenario is too specific to support this as generic feature. Satellite should allow this by customizing provisioning templates. Also API could be used to update/destroy interfaces after the provisioning. If the change is triggered by some external process it should do the update of Satellite as well.

I'd also say that it should be possible to create more vlan interfaces during host creation, they are configured at the end the installation. Or similarly it could be done using puppet module afterwards. With upcoming version it should be possible to achieve this also using remote execution plugin.

Please reopen if you disagree.