For a tenant though, I may not want to have to write user-data to bind every thing I launch through horizon's nova workflow, heat, sahara, etc. Just having one place to put the hook and its always called has some major advantages.
Thanks, Kevin ________________________________________ From: Mathieu Gagné [mga...@calavera.ca] Sent: Tuesday, May 03, 2016 3:25 PM To: Fox, Kevin M Cc: Michael Still; openstack-operators@lists.openstack.org; Sean Dague Subject: Re: [Openstack-operators] Anyone else use vendordata_driver in nova.conf? On Tue, May 3, 2016 at 5:51 PM, Fox, Kevin M <kevin....@pnnl.gov> wrote: > > I think I see at least one use case for minimum 2 hooks... > > Cloud provider wants to inject some stuff. > > Cloud tenant wants their own hook called to inject stuff to point to the > Config Management server in their own tenant. > > Maybe that's not vendor_data but tenant_data or something... > I think this could very well be addressed by cloud-init or any other sane initialization service. We just have to make sure instance identification and any other reasonable information are made available to those tools so they can be passed to their own Config Management server. I see vendor_data as a non-intrusive way to pass additional data to the instance without requiring the vendor/provider to inject an agent or custom code within the customer's image. -- Mathieu _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
