http://ask.projectatomic.io/en/question/3572/how-do-i-set-up-a-static-networking-configuration/
On Thu, Feb 16, 2017 at 12:05 PM, Shahar Havivi <shav...@redhat.com> wrote: > Hi Marc, > As I see it oVirt pass all your input to cloud-init package. > I think the input is wrong as far as cloud-init parser goes, > looking at the file: > backend/manager/modules/vdsbroker/src/main/java/org/ > ovirt/engine/core/vdsbroker/vdsbroker/CloudInitHandler.java > you need to set at-least one interface and the search domains should be > under. > > you are using the CustomScript so you need to set the yaml as the package > expected. > something like: > iface eth0 inet > address x.x.x.x > netmast x.x.x.x > gateway x.x.x.x > dns-nameservers x.x.x.x > > this is how oVirt set the interface (not via CustomScript but via setting > each interface and dns servers to search) > > On Thu, Feb 16, 2017 at 8:39 AM, Vinzenz Feenstra <vfeen...@redhat.com> > wrote: > >> >> > On Feb 15, 2017, at 11:51 PM, Marc Young <3vilpeng...@gmail.com> wrote: >> > >> > Are there limitations to cloud-init and oVirt? I wouldn't think so, >> > but i"m having a weird issue. >> >> >> What’s the guest OS? >> >> > >> > If i use the cloud-init yaml from the ovirt4 ruby sdk examples (ignore >> > formatting, gmail is messing with it): >> > >> > write_files: >> > - content: | >> > Hello, world! >> > path: /tmp/greeting.txt >> > permissions: '0644' >> > >> > it works, that file exists, and it shows in the /var/lib/cloud where >> i'd expect >> > >> > $ sudo cat /var/lib/cloud/instance/user-data.txt >> > #cloud-config >> > output: >> > all: '>> /var/log/cloud-init-output.log' >> > disable_root: 0 >> > runcmd: >> > - 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo >> > ''datasource_list: >> > ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg' >> > ssh_pwauth: true >> > chpasswd: >> > expire: false >> > user: root >> > write_files: >> > - content: | >> > Hello, world! >> > path: /tmp/greeting.txt >> > permissions: '0644' >> > >> > >> > If i use this: >> > >> > manage-resolv-conf: true >> > resolv_conf: >> > nameservers: ['192.168.2.113'] >> > searchdomains: >> > - blindrage.local >> > - bar.example.com >> > >> > resolv_conf does not get modified. It looks as expected in >> /var/lib/cloud: >> > >> > $ sudo cat /var/lib/cloud/instance/user-data.txt >> > #cloud-config >> > output: >> > all: '>> /var/log/cloud-init-output.log' >> > disable_root: 0 >> > runcmd: >> > - 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo >> > ''datasource_list: >> > ["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg' >> > ssh_pwauth: true >> > chpasswd: >> > expire: false >> > user: root >> > manage-resolv-conf: true >> > resolv_conf: >> > nameservers: ['192.168.2.113'] >> > searchdomains: >> > - foo.local >> > - bar.example.com >> > >> > I also don't see anything in /var/log/cloud-init.log or >> > /var/log/cloud-init-output.log on either run even though the >> > write_files yaml worked. >> > _______________________________________________ >> > Devel mailing list >> > Devel@ovirt.org >> > http://lists.ovirt.org/mailman/listinfo/devel >> >> _______________________________________________ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > >
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel