Open Stack

On Thu, Jan 9, 2014 at 6:14 AM, Steven Dake <sdake at redhat.com> wrote:

> that


Steve
Thanks for detailed email. Apologize for the delayed response but we have
been thinking about how does software config fit into configuring network
and service function devices. I agree with you that in general it is best
to get appliance vendors to put cloudinit into their images and thus get on
board with what every cloud is doing. I thought I would get some feedback
on the direction of Heat for configuring network devices and appliances.

I am thinking there are few things to consider for configuring Network and
Network Service devices/Virtual Appliances.

Neutron APIs along with the service APIs provide a way to configure network
devices by abstracting the APIs and have a plugin model for individual
devices. These APIs include Neutron core apis, Service API such as LBaaS,
FWaaS, VPNaaS. Though these are currently for physical devices, there is a
movement towards configuring Virtual Appliances too. These APIs will be
addressed via Heat Neutron resources.

While *aaS do address configuring the supported service, they do not
address the bootstrapping of the device. Generally for most devices
bootstrapping is done via rest API and/or SSH. And for unsupported
 services that do not have these APIs one needs to use custom way to
configure where Heat can really help.  Bootstrapping includes installing
licences, configuring admin password, upgrade software  and some with more
than that. For this our thought is it would be great to have  Heat software
config/deployment do bootstrapping, upgrade etc.

 While I agree long term is to have vendors to implement cloudinit
framework, we were wondering if there is an intermediate solution that will
allow configuration without requiring agent and cloudinit, If there is
enough critical mass behind such a requirement we can have further
discussions on the design and implementation options.

BTW puppet seems to use similar proxy way to network device configuration.
See link below
https://puppetlabs.com/blog/managing-f5-big-ip-network-devices-with-puppet

thanks
prasadv
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140113/a2acb724/attachment.html>