This is somewhat off topic, but related. I've always thought ApacheCloudStack should come with a PXE server on the controller to boot the hypervisors over the network. Automatic construction of the hypervisors so there are no local disks would be really nice. I imagine DHCP attributes could be a part of provisioning functionality. It would be really nice if you just racked up servers and the local disks showed up as a storage option, but there was no OS disk on the hypervisor to get jacked up. Later those local disks could be federated later.
Dustin On Wed, Feb 8, 2017 at 9:04 AM, Syed Ahmed <sah...@cloudops.com> wrote: > Hi Sigert, > > Instead of creating a new table `nic_extra_dhcp_option` is it possible to > use the table `nic_options` The *_details tables are usually used as a > key-value store to store details about the various secondary params. You > can have a look at host_details table for example. There is already > boilerplate code (like NicDetailsDao & NicDetailsVO etc) in Cloudstack for > doing this. You could just use that instead. > > On Wed, Feb 8, 2017 at 5:37 AM, Sigert GOEMINNE < > sigert.goemi...@nuagenetworks.net> wrote: > > > All, > > > > We would like to add support for extra DHCP options to Nuage in > CloudStack. > > > > We want to add an extra optional parameter for extra DHCP options to the > > deployVm, updateVM and addNic API, and pass this to the plugin, using a > new > > method on the DHCP Service provider interface. > > > > Please take a look at the FS [1], and jira ticket [2]. > > > > [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/C > > loudStack+extra+DHCP+option+support > > [2] https://issues.apache.org/jira/browse/CLOUDSTACK-9776 > > > > Kind regards, > > > > *Sigert Goeminne* > > Software Development Engineer > > > > *nuage* <http://nuagenetworks.net>networks.net > > Copernicuslaan 50 > > 2018 Antwerp > > Belgium > > >
