Re: [openstack-dev] [Nova]Passing flat_injected flag through instance metadata
On 05/30/2014 05:29 PM, ebaysf, yvempati wrote: Hello all, I am new to the openstack community and I am looking for feedback. We would like to implement a feature that allows user to pass flat_injected flag through instance metadata. We would like to enable this feature for images that support config drive. This feature helps us to decrease the dependency on dhcp server and to maintain a uniform configuration across all the hypervisors running in our cloud. In order to enable this feature should I create a blue print and later implement or can this feature be implemented by filing a bug. I'm not sure I understand what you're trying to do here. As I recall, when flat_injected is set the static network configuration is already included in the config drive data. I believe there have been some changes around file injection, but that shouldn't affect config drive as far as I know. If you just need that functionality and it's not working anymore then a bug might be appropriate, but if you need something else then a blueprint/spec will be needed. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova]Passing flat_injected flag through instance metadata
Hi, Thanks for getting back to me. The current flat_injected flag is set in the hypervisor nova.conf. The config drive data uses this flag to set the static network configuration. What I am trying to accomplish is to pass the flat_injected file through the instance metadata during the boot time and use it during the config drive network configuration rather setting the flag at the hypervisor level. Regards, Yashwanth Vempati On 6/2/14, 9:30 AM, Ben Nemec openst...@nemebean.com wrote: On 05/30/2014 05:29 PM, ebaysf, yvempati wrote: Hello all, I am new to the openstack community and I am looking for feedback. We would like to implement a feature that allows user to pass flat_injected flag through instance metadata. We would like to enable this feature for images that support config drive. This feature helps us to decrease the dependency on dhcp server and to maintain a uniform configuration across all the hypervisors running in our cloud. In order to enable this feature should I create a blue print and later implement or can this feature be implemented by filing a bug. I'm not sure I understand what you're trying to do here. As I recall, when flat_injected is set the static network configuration is already included in the config drive data. I believe there have been some changes around file injection, but that shouldn't affect config drive as far as I know. If you just need that functionality and it's not working anymore then a bug might be appropriate, but if you need something else then a blueprint/spec will be needed. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova]Passing flat_injected flag through instance metadata
We have discussed this a bunch in the past, and the right implementation here is to put the network configuration in a standard format (json?) in both the config drive and metadata. cloud-init can be modified to read from that format and write out a proper /etc/network/interfaces (or appropriate files for the guest distro) Vish On Jun 2, 2014, at 10:20 AM, ebaysf, yvempati yvemp...@ebaysf.com wrote: Hi, Thanks for getting back to me. The current flat_injected flag is set in the hypervisor nova.conf. The config drive data uses this flag to set the static network configuration. What I am trying to accomplish is to pass the flat_injected file through the instance metadata during the boot time and use it during the config drive network configuration rather setting the flag at the hypervisor level. Regards, Yashwanth Vempati On 6/2/14, 9:30 AM, Ben Nemec openst...@nemebean.com wrote: On 05/30/2014 05:29 PM, ebaysf, yvempati wrote: Hello all, I am new to the openstack community and I am looking for feedback. We would like to implement a feature that allows user to pass flat_injected flag through instance metadata. We would like to enable this feature for images that support config drive. This feature helps us to decrease the dependency on dhcp server and to maintain a uniform configuration across all the hypervisors running in our cloud. In order to enable this feature should I create a blue print and later implement or can this feature be implemented by filing a bug. I'm not sure I understand what you're trying to do here. As I recall, when flat_injected is set the static network configuration is already included in the config drive data. I believe there have been some changes around file injection, but that shouldn't affect config drive as far as I know. If you just need that functionality and it's not working anymore then a bug might be appropriate, but if you need something else then a blueprint/spec will be needed. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev signature.asc Description: Message signed with OpenPGP using GPGMail ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova]Passing flat_injected flag through instance metadata
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Then I think the answer to the original question is that this requires a new spec, unless one already exists? - -Ben On 06/02/2014 12:50 PM, Vishvananda Ishaya wrote: We have discussed this a bunch in the past, and the right implementation here is to put the network configuration in a standard format (json?) in both the config drive and metadata. cloud-init can be modified to read from that format and write out a proper /etc/network/interfaces (or appropriate files for the guest distro) Vish On Jun 2, 2014, at 10:20 AM, ebaysf, yvempati yvemp...@ebaysf.com wrote: Hi, Thanks for getting back to me. The current flat_injected flag is set in the hypervisor nova.conf. The config drive data uses this flag to set the static network configuration. What I am trying to accomplish is to pass the flat_injected file through the instance metadata during the boot time and use it during the config drive network configuration rather setting the flag at the hypervisor level. Regards, Yashwanth Vempati On 6/2/14, 9:30 AM, Ben Nemec openst...@nemebean.com wrote: On 05/30/2014 05:29 PM, ebaysf, yvempati wrote: Hello all, I am new to the openstack community and I am looking for feedback. We would like to implement a feature that allows user to pass flat_injected flag through instance metadata. We would like to enable this feature for images that support config drive. This feature helps us to decrease the dependency on dhcp server and to maintain a uniform configuration across all the hypervisors running in our cloud. In order to enable this feature should I create a blue print and later implement or can this feature be implemented by filing a bug. I'm not sure I understand what you're trying to do here. As I recall, when flat_injected is set the static network configuration is already included in the config drive data. I believe there have been some changes around file injection, but that shouldn't affect config drive as far as I know. If you just need that functionality and it's not working anymore then a bug might be appropriate, but if you need something else then a blueprint/spec will be needed. -Ben ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTjLpUAAoJEDehGd0Fy7uqPQAH/0y4j/0KUnB3veQjjopxKeRp Uf+lK3YrnGqvqLIh9VWv58exHshvWFh6RRWys7wCuPH6vf1/Lzt3X3M6NdLP/INh 2no8kj2V7Z9ex6Q6yS9Rt3YVX5Rt2xgyg2QPiZNnCLTJ2NfBRdgxVYW5WobcKOY3 n6ymaEqJxcGGnz2GcBGxiXekWqA9F3mEIND10KjrPL5j9B6zLW4ffknX6tgT/uUn JwZrKC3r++tdNpATnJ2tD9W5A5wzVHtnaglnfFGJRwRVj+aPiu8Jt8awNah+mf2Q dTdKiL7OY2q6Tv1wGpxGObq69fZDYcnYyXBK2/2+yHYz5TrfzsDY/cyb8YJ659I= =xLDw -END PGP SIGNATURE- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
