On Sun, Jan 6, 2013 at 9:26 AM, Damitha Kumarage <[email protected]> wrote:

> Hi Lahiru,
> We need a policy as to which tenant are eligible to which number of
> maximum number of cartridges and which type of resources. This policy will
> be configured at S2 deployment time in a policy file.
>
> We also need to have WSO2 S2 specific resource types which would be mapped
> to actual underlying IaaS resource types.
> For example
> s2-small - (A custom or available type in EC2 and Openstack with 1G memory
> 1cpu)
> s2-large - (A custom or availbel type in EC2 and Openstack with 2G memory
> and 2cpu)
> s2-xlarge- (A custom or available type in EC2 and Openstack with 4G memory
> and 4cpu) etc
>
>
> So for example an enterprise tenant can create upto 5 php cartridges in a
> cluster with s2-small or s2-large or s2-xlarge resource type.
>
Hi Damitha,

Noted. I'll elaborate the scenario in architecture@ with the design.

Thanks.

>
> Damitha
>
>
> On Sat, Jan 5, 2013 at 11:15 PM, Lahiru Sandaruwan <[email protected]>wrote:
>
>> Hi Amila,
>>
>> It seems we have to get this done before beta release, 31th Jan.
>> Because the tenants should be given some limitations like maximum number
>> of instances he can have in the cluster and the type(M1.large etc.) of the
>> instances that the system creates for him according to the type.
>> Any possibility of prioritizing this?
>>
>> Thanks in advance. :)
>>
>>
>> On Sun, Sep 16, 2012 at 10:21 PM, Amila Maha Arachchi <[email protected]>wrote:
>>
>>> Hi Sajith/Nirmal,
>>>
>>> We store the usage plan (which you refer as type) in the billing
>>> database. Earlier this was only relevant to Stratos deployment. Because
>>> these information are in two places (user store and billing DBs) this is
>>> not directly available with tenant information which is provided by the
>>> tenant manager. But now we have a requirement. So we'll have to make these
>>> information available with tenant information.
>>>
>>> I hope you are working on the trunk?
>>>
>>> Regards,
>>> AmilaM.
>>>
>>>
>>> On Sun, Sep 16, 2012 at 2:58 PM, Sajith Kariyawasam <[email protected]>wrote:
>>>
>>>> Hi Amila,
>>>>
>>>> Don't we maintain tenant types in Stratos database ? I couldn't find a
>>>> mapping in userstore schema. Are those available in some other schema?
>>>>
>>>> On Sun, Sep 16, 2012 at 9:56 AM, Amila Maha Arachchi 
>>>> <[email protected]>wrote:
>>>>
>>>>> Hi Lahiru,
>>>>>
>>>>> At the moment this is only available with the billing bundles. This
>>>>> requirement was raised during another scenario also (related to database
>>>>> usage measurement implementation work). We have an interface
>>>>> (TenantBillingService IIRC) in stratos.common bundle. I think we'll have 
>>>>> to
>>>>> make these details available via that bundle (given that we ship it with
>>>>> all products now.). I will work on it.
>>>>>
>>>>> Regards,
>>>>> AmilaM.
>>>>>
>>>>> On Sun, Sep 16, 2012 at 9:00 AM, Lahiru Sandaruwan 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> Hi devs,
>>>>>>
>>>>>> We have four types of tenants in Stratos.
>>>>>> Demo, SMB, Professional, and Enterprise.
>>>>>>
>>>>>> Can we do $subject?
>>>>>> I was not able to find it using 'MultitenantUtils' etc.
>>>>>>
>>>>>> I need it in ADS (Artifact Deployment Server) back end, to check the
>>>>>> type of the tenant when tenants create new cartridges.
>>>>>> ADS will be there in the Stratos default server stack as Stratos
>>>>>> manager, and Is.
>>>>>>
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Software Engineer,
>>>>>> Cloud Team,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: [email protected] cell: (+94) 773 325 954
>>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>>> twitter: http://twitter.com/lahirus
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> [email protected]
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Amila Maharachchi*
>>>>> Technical Lead
>>>>> Member, Management Committee - Cloud & Platform TG
>>>>> WSO2, Inc.; http://wso2.com
>>>>>
>>>>> Blog: http://maharachchi.blogspot.com
>>>>> Mobile: +94719371446
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> *
>>>> *
>>>> *Sajith Kariyawasam*
>>>> *Senior Software Engineer; WSO2, Inc.; http://wso2.com*
>>>>
>>>>
>>>
>>>
>>> --
>>> *Amila Maharachchi*
>>> Technical Lead
>>> Member, Management Committee - Cloud & Platform TG
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Blog: http://maharachchi.blogspot.com
>>> Mobile: +94719371446
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Cloud Team,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: [email protected] cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>> <http://wso2con.com/>
>>
>
>
>
> --
> __________________________________________________________________
> Damitha Kumarage
> Senior Technical Lead; WSO2 Inc.
> Oxygenating the Web Service Platform
> http://www.wso2.com/
> blog:
> http://damithakumarage.wordpress.com/
> __________________________________________________________________




-- 
--
Lahiru Sandaruwan
Software Engineer,
Cloud Team,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

email: [email protected] cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
<http://wso2con.com/>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to