[PetiteCloud] to nat/dhcp or not?

[Aryeh Friedman]

An other solution is do it via templating scripts... the main issue I had
with how to implement it correctly is each variant I saw seemed to be
highly specific to it's host settings and no easy way to change some of
them automatically (such as setting the dhcp listen initerface).... the
reason for the templated scripts it allows people to swap them out as
needed for their own improved ones or complete rewrites (it is also a place
where someone might want to make a commercial add-on that's better then the
default one)... our general thinking here is the stuff that needs to be
rigid to keep everything stable is rigid and the stuff that can be flexible
should be flexible... at every "flex" point we also want to add the ability
to do plugins (for really low level stuff that is usually a fill in the
blank script generated by something)


On Thu, Feb 13, 2014 at 10:22 AM, Michael Thoreson <m.thoreson at c4labs.ca>wrote:

> I suppose may offering NAT\DHCP directly within PetiteCloud is required.
> But having support for a virtual switch and router would be beneficial.
> Something similar to VMWare vSwitch. Make NAT'ing and DHCP an add on
> through virtual routers. There are may free and open BSD\Linux routing
> projects out there and most admins comfortable with CLI can whip up a small
> router to suite their specific purpose.
>
> Michael Thoreson,
>
>
>
> On 13/02/2014 4:29 AM, Aryeh Friedman wrote:
>
>> When we where designing PetiteCloud originally we made a few assumptions
>> about our technical goals that we have reworked (not removed in the
>> majority of cases) and may or may not still be valid.  One assumption was
>> that we would be the primary/only cloud platform running (recursively) on
>> any given physical host.   This is clearly not the case any more.   One
>> such assumption we made was since our market was different then other cloud
>> platforms (see attached draft white paper notes) we would need to provide
>> more of the smoke and mirrors of cloud computing then we need to only be a
>> cloud foundation layer and not any other goal higher.   Addtionaly as the
>> list knows we firmly believe in off loading everything that is not
>> PetiteCloud's problem on to someone else.  The someone else in this case
>> often is the market place for apps and such.
>>
>> One such reworked assumption was the assumption we would be providing all
>> the networking for smaller clouds (likely no more then a spare machine. NAS
>> and cable modem).   This puts us firmly in layer 1 which is not where we
>> think PetiteCloud itself should be for "basic" networking (3rd party addons
>> and such will help here).   Since we only provide the raw "plumbing" for
>> networking is there any reason to offer NAT and/or DHCP on the host end?
>>
>> --
>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
>>
>>
>> _______________________________________________
>> petitecloud-general mailing list
>> petitecloud-general at lists.petitecloud.nyclocal.net
>> http://lists.petitecloud.nyclocal.net/listinfo.cgi/petitecloud-general-
>> petitecloud.nyclocal.net
>>
>
> _______________________________________________
> petitecloud-general mailing list
> petitecloud-general at lists.petitecloud.nyclocal.net
> http://lists.petitecloud.nyclocal.net/listinfo.cgi/petitecloud-general-
> petitecloud.nyclocal.net
>



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.petitecloud.nyclocal.net/pipermail/petitecloud-general-petitecloud.nyclocal.net/attachments/20140213/8d2cbb3e/attachment-0003.htm>