Feature #3150

Context.sh is not updated when NIC with updated IP is attached

Added by Christian Hüning over 5 years ago. Updated over 3 years ago.

Status:ClosedStart date:08/13/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Context
Target version:Release 5.0
Resolution:fixed Pull request:

Description

We detached and re-attached a NIC to a VM and changed the IP for that NIC. Sunstone correctly shows the new IP address, but the one-context contextualization mechnism still tries to configure the old IP address.


Related issues

Related to Feature #3147: Change CDROM media Pending 08/11/2014
Related to Request #3402: Allow to modify NICs in running VMs Pending 12/05/2014
Related to Backlog #3470: Delete-Recreate fails if context-scripts are changed Closed 12/19/2014

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Tracker changed from Bug to Backlog
  • Category set to Context

Context is not updated after the VM boots, so this is not exactly a bug. You can access (from the VM) to VM information using onegate service. We want to adapt this dynamic configuration to the contextualization process, probably leveraging cloudinit an a gate supported provider.

Moving this to backlog.

#2 Updated by novid Agha Hasani about 5 years ago

Ruben S. Montero wrote:

Context is not updated after the VM boots, so this is not exactly a bug. You can access (from the VM) to VM information using onegate service. We want to adapt this dynamic configuration to the contextualization process, probably leveraging cloudinit an a gate supported provider.

Moving this to backlog.

there is not any way for generating new context.sh after attach or deattach nic? and then reattach cdrom to vm? you just overwrite to disk1.iso

#3 Updated by Ruben S. Montero about 5 years ago

I'm afraid that currently there is no alternative, we are looking into this.

#4 Updated by Ruben S. Montero about 5 years ago

#5 Updated by Ruben S. Montero about 5 years ago

Added change media as a related issue, as this could be address as changing the context cd-rom as suggested. Other alternatives includes the use of one-gate.

#6 Updated by EOLE Team about 5 years ago

Ruben S. Montero wrote:

Added change media as a related issue, as this could be address as changing the context cd-rom as suggested. Other alternatives includes the use of one-gate.

What to do if the CDROM is mounted in the guest?

#7 Updated by Ruben S. Montero about 5 years ago

Yes, the other alternative involves one-gate, similar to the EC2 user-data broker... The problem here is basically require VM-to-onegate connectivity either by requiring both to be reachable (i.e. add a public IP to the VM or a virtual router...) or capture the a link local IP in 169.254.0.1/16 and forward it to the onegate server. This however may impose strong network requirements on the hypervisors, and I'm not sure we want to go that way

#8 Updated by Carlos Martín almost 5 years ago

  • Related to Request #3402: Allow to modify NICs in running VMs added

#9 Updated by Ruben S. Montero over 4 years ago

  • Related to Backlog #3470: Delete-Recreate fails if context-scripts are changed added

#10 Updated by Ruben S. Montero almost 4 years ago

  • Tracker changed from Backlog to Feature
  • Status changed from Pending to New
  • Target version set to Release 5.0

#11 Updated by Ruben S. Montero over 3 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

This is now implemented in master, a specific reconfigure action is invoked in the drivers and the context regenerated.

#12 Updated by Dominic Luechinger over 3 years ago

Is this update only triggered if the NIC informations are updated?
I'm looking for a solution to generate a new context.sh if a 'User Inputs' attribute is changed.

#13 Updated by Ruben S. Montero over 3 years ago

Every time the VM is deployed it is updated (i.e. in power-on power-off cycles...)

Also available in: Atom PDF