Open Stack

We have a “Tacker” project aiming to manage service VMs.
https://wiki.openstack.org/wiki/ServiceVM
Personally I think all the advance network services like firewall/LB/VPN can be provided by service VMs and eventually managed by Tacker.

From: A, Keshava [mailto:keshava.a at hp.com]
Sent: Thursday, April 16, 2015 2:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] openwrt VM as service

Hi,
SO we are going in a direction , where Open stack Infrastructure features  also moving into Service-VM ?
                Moving into Service-VM is mixing with NFV world, where these   Tennant/NFV Services are supposed to be outside open stack infrastructure.
                Let me know if my understanding is correct here.

keshava


From: Dean Troyer [mailto:dtroyer at gmail.com]
Sent: Wednesday, April 15, 2015 10:25 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] openwrt VM as service

On Wed, Apr 15, 2015 at 2:37 AM, Guo, Ruijing <ruijing.guo at intel.com<mailto:ruijing.guo at intel.com>> wrote:
I’d like to propose openwrt VM as service.

What’s openWRT VM as service:

a)            Tenant can download openWRT VM from http://downloads.openwrt.org/
b)            Tenant can create WAN interface from external public network
c)            Tenant can create private network and create instance from private network
d)            Tenent can configure openWRT for several services including DHCP, route, QoS, ACL and VPNs.


So first off, I'll be the first on in line to promote using OpenWRT for the basis of appliances for this sort of thing.  I use it to overcome the 'joy' of VirtualBox's local networking and love what it can do in 64M RAM.

However, what you are describing are services, yes, but I think to focus on the OpenWRT part of it is missing the point.  For example, Neutron has a VPNaaS already, but I agree it can also be built using OpenWRT and OpenVPN.  I don't think it is a stand-alone service though, using a combination of Heat/{ansible|chef|puppet|salt}/any other deployment/orchestration can get you there.  I have a shell script somewhere for doing exactly that on AWS from way back.

What I've always wanted was an image builder that would customize the packages pre-installed.  This would be especially useful for disposable ramdisk-only or JFFS images that really can't install additional packages.  Such a front-end to the SDK/imagebuilder sounds like about half of what you are talking about above.

Also, FWIW, a while back I packaged up a micro cloud-init replacement[0] in shell that turns out to be really useful.  It's based on something I couldn't find again to give proper attribution so if anyone knows who originated this I'd be grateful.

dt

[0] https://github.com/dtroyer/openwrt-packages/tree/master/rc.cloud
--

Dean Troyer
dtroyer at gmail.com<mailto:dtroyer at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150416/c3784159/attachment.html>