Thanks for the doc Mari! I've updated few places and I think I've messed up
with the formatting at the info box against 'memoryConsumption':(. Please
correct it.
On Fri, Aug 15, 2014 at 5:15 PM, Mariangela Hills
wrote:
> I resolved JIRA [1] and updated the following pages in wiki 4.1.0 based
>
Please change 'expiryTimeout' property in repository/conf/autoscaler.xml
file accordingly.
90
On Sat, Aug 16, 2014 at 10:39 AM, Ignacio Ayuste <
ignacio.ayu...@bairesdev.com> wrote:
> Hi Akila thanks for the quick answer i think i not use cartb
Hi Akila thanks for the quick answer i think i not use cartbridge agent
because i use default service name in the puppet agent, is there is anyway
to extend that time, maybe changing some parameter.
Thanks
Ignacio
2014-08-16 1:29 GMT-03:00 Akila Ravihansa Perera :
> Hi Ignacio,
>
> It seems Str
Hi,
I hope this is the same issue you raised at the thread [1]
[1]Stratos Eliminate the instances EC2 automatically
Touched, not typed. Erroneous words are a feature, not a typo.
On Aug 15, 2014 8:18 PM, "Ignacio Ayuste"
wrote:
> Hi Udara thanks for the answer yesterday i created a centos ima
Hi Ignacio,
It seems Stratos is killing those instances because they have not activated
within the given timeout period (15mins in default).
Make sure cartridge agent is running in the instances and ports given in
cartridge definition (8280, 8243) are active. Agent will blockingly wait
until all
Hi,
It seems that your instances are not activated. Please have a look at the
log snippet I pasted below extracted from your logs.
Pending state of member: lbpuppet.stratos.domain5ea49353-
ce4e-4817-b8d5-399e52250f12 is expired. Adding as an obsoleted member.
Background:
When you deploy a MT s
I configure stratos with all the step and the step 6 multitenant services
create two instances but then when i logged Stratos kill the instances of
EC2, why stratos have this behaviour, i provide the scripts:
URL REST SERVICES
https://54.186.150.199/stratos/?_wadl
(Step 1) Partition:
{
"id": "z
Jeffrey Nguyen created STRATOS-747:
--
Summary: Networking support for vCloud
Key: STRATOS-747
URL: https://issues.apache.org/jira/browse/STRATOS-747
Project: Stratos
Issue Type: Improvement
Hi,
I have some few questions regarding this.
1.Why do we have a super tenant in the first place?
Shouldn't it be "default tenant"?
2. Do we have a tenant admin role in Stratos?
Thanks.
Hi,
Yes what Pradeep has pointed out is true, this has been done by design.
Super tenant cannot perform oper
Hi Udara thanks for the answer yesterday i created a centos image in Amazon
EC2 and configure puppet agent following this tutorial:
https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Creating+a+Cartridge+on+EC2#id-4.0.0CreatingaCartridgeonEC2-Step2-Configuringthecartridge
then for testing
Hi,
Yes what Pradeep has pointed out is true, this has been done by design.
Super tenant cannot perform operations in tenant space.
Thanks
On Fri, Aug 15, 2014 at 8:05 AM, Pradeep Fernando
wrote:
> Hi,
>
> Adding to that, i sense something wrong with above requirement. tenant is
> the isolati
Hi,
Adding to that, i sense something wrong with above requirement. tenant is
the isolation unit we use. So other tenants (even the super tenant) should
not play around with my tenant space. (after the initial tenant admin
creation, super tenant work is done IIUC)
Tenant admin can do the above op
Hi Sajith,
The code i provided you make use of the docker image id for spawning
instances. Can't we use that code bit to spawn instances using image id ?
thanks,
--Pradeep
On Thu, Aug 14, 2014 at 9:20 AM, Sajith Kariyawasam wrote:
>
> On Tue, Aug 12, 2014 at 10:00 AM, Lakmal Warusawithana
>
Hi Rukmal,
Sorry for the delayed response.
It is not tightly bound to carbon modules.
1. You can use basic auth to authenticate each and every API call Or,
2. Call authentication service and retrieve cookie. Use the cookie for
subsequent requests.
3. There is a handler for Oauth as well. But is
[
https://issues.apache.org/jira/browse/STRATOS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills updated STRATOS-735:
-
Issue Type: Sub-task (was: Bug)
Parent: STRATOS-645
> [Documentation] Auto-scal
I resolved JIRA [1] and updated the following pages in wiki 4.1.0 based on
JIRA [2].
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Deploying+an+Auto-scaling+Policy+Definition
https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Listing+Auto-scaling+Policies
https://cwiki.apache.o
[
https://issues.apache.org/jira/browse/STRATOS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-735.
--
Resolution: Fixed
I updated the following pages based on the update in the auto-scalin
[
https://issues.apache.org/jira/browse/STRATOS-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-746.
> [Wiki] 4.1.0 wiki pages point to 4.0.0 wiki release
> --
[
https://issues.apache.org/jira/browse/STRATOS-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-746.
--
Resolution: Fixed
Checked and fixed the links in all the sub-pages under the following
Hi Amila,
Sorry for the delayed response. In the current implementation, this is not
supported.
On Wed, Aug 13, 2014 at 5:34 PM, Amila Maha Arachchi
wrote:
> Hi Devs,
>
> AFAIU, at the moment when subscribe to a service (via the REST api), we
> need to provide the tenant user's credentials.
>
Mariangela Hills created STRATOS-746:
Summary: [Wiki] 4.1.0 wiki pages point to 4.0.0 wiki release
Key: STRATOS-746
URL: https://issues.apache.org/jira/browse/STRATOS-746
Project: Stratos
[
https://issues.apache.org/jira/browse/STRATOS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills reassigned STRATOS-735:
Assignee: Mariangela Hills
> [Documentation] Auto-scaling policy definition should
22 matches
Mail list logo
