[PetiteCloud] requirements for 0.3

[Aryeh Friedman]

We also should at some near future point workout a common meta-script for
all the main generated scripts (/tmp/X[install|run] and ones called one
command at a time by the java)...

The reason for not using java for the command line is it is very hard to
script (very long confusing command lines mostly) and the need to
eventually get down to .1 or .01 CU instances


On Thu, Feb 13, 2014 at 6:58 PM, Aryeh Friedman <aryeh.friedman at gmail.com>wrote:

>
>
>
> On Thu, Feb 13, 2014 at 6:28 PM, Michael Thoreson <m.thoreson at c4labs.ca>wrote:
>
>> On 13/02/2014 5:12 PM, Aryeh Friedman wrote:
>>
>>> We practice open requirements (i.e. except for a few very specific goals
>>> we have in mind for each version we let the community define what it will
>>> have in it). So the immediate goals for us are:
>>>
>>> 0.2.7. VBox and VMWare, Windows as a host (if it is scriptable if it
>>> needs coding it will have to wait)
>>>
>> Powershell scripting should be able to do what we want. I personally
>> don't know Powershell, but from what I read it is very capable.
>
>
> Can the installer also be scripted?
>
>
>>
>>
>>  0.2.8. iSCSI connections and storage abstraction API
>>>
>> This should be able to be scripted to use existing host NFS\SMB\ISCSI
>> tools and we can always add Gluster or other cluster filesystems.
>
>
> Thanks for confirming my list of what remote file systems to support
> natively and which ones to externalize.   Should we also include fuse? (I
> think anything that advanced would be externalized already)
>
>
>>
>>
>>> 0.3.0. Most of the core is moved to C (even though we vastly prefer Java
>>> the need for tomcat might be an issue), simple ACL's (users and single
>>> admin)
>>>
>> i am confused why move from Java to C anyway if the idea of PetiteCloud
>> is to be more of a web app. I would have thought Java with some php and
>> perl would work well.
>>
>
> The primary reason is we want to also have a 100% script-able command line
> as well as when start talking about sub-cloud unit [CU] (internally we
> speak in terms of how many CU an application would require... for example
> most programming can be done on a 1 CU instance [pc-dev is 1.5 CU roughly])
> having a webapp might be prohabtive and most cloud foundation hosts would
> be running in "dark room" mode... a CU is what $300-400 buys retail interms
> of RAM confined to running on a single core (with your typical machine in
> this catagory coming with 1T+ of disk disk is essentially limitless for
> most non-big data apps)... Dee will be posting sometime soon on the
> requirements for the command line
>
>
>>  0.3.1. Enterprise identity solution integration, plugin archticiture
>>> worked out, layer 1 control/monitoring via API of PC
>>> 0.3.2. Roles and security groups, basic plugin's supported
>>>
>>> 0.3.3. Auditing support, all plugins supported
>>>
>>> --
>>> 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
>



-- 
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/4ed31501/attachment-0003.htm>