Open Stack

I think your driver should implement a wrapper around both VendorPassthru
interfaces and call each appropriately, depending on the request. This
keeps each VendorPassthru driver separate, and encapsulates the logic about
when to call each of them in the driver layer.

As an aside, this is a code path (multiplexed VendorPassthru interfaces)
that we haven't exercised yet, but has come up in other discussions
recently too, so if you run into something else that looks awkward, please
jump into IRC and we'll help hash it out.

Cheers,
Devananda


On Fri, Jan 31, 2014 at 1:34 AM, Rohan Kanade <openstack at rohankanade.com>wrote:

> > The deploy ramdisk should ping back the Ironic API and call the
> > vendor_passthru/pass_deploy_info with the iscsi informations etc... So,
> > make sure you've built your deploy ramdisk after this patch landed on
>
> Any strategies on how to verify if the ramdisk has been deployed on the
> server?
>
> Also, I am using different Power and VendorPassthru interfaces (unreleased
> SeaMicro), And i am using PXE only for Deploy interface. How can the
> pass_deploy_info be called by the ramdisk since it is not implemented by
> SeaMicro VendorPassthru?
>
> Regards,
> Rohan Kanade
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140131/4ec74d59/attachment.html>