<HTML>
<HEAD>
<TITLE>Re: [Openstack] RHEL / CentOS - interfaces.template</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Does anyone have any experience with <a href="https://fedorahosted.org/netcf/">https://fedorahosted.org/netcf/</a> (RH??)<BR>
<BR>
Just from a little search that project seems to be oriented to do this (os agonistic net cfg)<BR>
<BR>
It just seems to be missing a python api (at the moment).<BR>
<BR>
On 2/14/12 10:48 AM, "Scott Moser" <<a href="smoser@ubuntu.com">smoser@ubuntu.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>On Tue, 14 Feb 2012, Leandro Reox wrote:<BR>
<BR>
> Hi guys,<BR>
><BR>
> Anyone already implemented networking injection to RHEL systems acting as a<BR>
> guest ? If no any plans to make it to Essex final ?<BR>
<BR>
<BR>
Before we go down the road of trying to write system network configuration<BR>
scripts for each potential guest OS, I'd suggest that its would be better<BR>
to either:<BR>
a.) just accept that 'interfaces' is the openstack format and guests<BR>
should need to read that.<BR>
b.) create a OS agnostic interface configuration format.<BR>
<BR>
While you may be looking at my email address and assuming that I think 'a'<BR>
is the right answer only to make it harder for anyone else.<BR>
<BR>
However, the reason I dislike the current solution (or going down a path<BR>
of implementing population mechanisms for other operating systems) is<BR>
1.) you cannot possibly support all possible operating systems<BR>
2.) injecting files assumes host OS knowledge (or guestfs knowledge) of<BR>
the guest filesystem<BR>
3.) specific files indicates that the host can somehow determine which<BR>
format the guest is expecting (or also unacceptable, only allowing<BR>
this configuration for one OS per cloud).<BR>
4.) injecting files via overwriting them is lossy and possibly<BR>
destructive to a guest (imagine other vpn routes inserted there or<BR>
something else more advanced).<BR>
<BR>
I would *much* rather there be a "openstack networking configuration file<BR>
format" that was put into config_drive if dhcp was not sufficient.<BR>
<BR>
Then, the guests are just made to read that information that is in a<BR>
standard, easily documetable format and respond accordingly.<BR>
<BR>
_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>