|
On 23/04/2014 11:09 PM, Brian Gupta
wrote:
My initial take is that this seems a reasonable approach, if we packaged it for sid, and make a backport. However, I would be curious to know if (and how) Ubuntu handles this, as coordinating efforts here might be useful? I fired up an Ubuntu image, and I don't see it handling the additional network sub-interface I created. The key mitigating difference I think, is: a) this is really needed for some VPC cloud use cases b) no users who don't need this functionality will be impacted (please confirm) I don't believe there is any impact on users who dont need this functionality at all. We can review the code as well (its just pure shell). From my quick look tonight the only dependency appears to be on iproute2 (/sbin/ip). An alternative approach (if it technically works) would be to still package it in backports, but to use cloud-init itself to install the package and bring up the interfaces. However, the timing of it might not work at all, and even if it does it might be overly complicated? I think we're thinking the same thing - possible catch-22 there on needing the interface up to apply the package at boot time (instead of image creation time). Would this pair of scripts be useful outside of EC2 - is it worth packaging if it is only ever used here as part of bootstrap-vz (and then leave this to be included in a packaging effort of bootstrap-vz)? James --
Mobile: +61 422 166 708, Email: james_AT_rcpt.to |