[
https://issues.apache.org/jira/browse/STRATOS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa reassigned STRATOS-761:
-
Assignee: Shiroshica Kulatilake
> Tenant isolation for policies and definitions
[
https://issues.apache.org/jira/browse/STRATOS-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Isuru Haththotuwa reassigned STRATOS-770:
-
Assignee: Shiroshica Kulatilake
> Adding in a "Description" field to all definit
Hi Sajith,
Thanks for the response. It solved the issue.
On Wed, Sep 3, 2014 at 12:42 AM, Sajith Kariyawasam wrote:
> Hi Madhawa,
>
>
>
> On Tue, Sep 2, 2014 at 6:26 PM, Madhawa Bandara wrote:
>
>> The issue seems to be when restarting the apache2.
>>
>> Here is the log:
>> Info: /Stage[main]
Mariangela Hills created STRATOS-771:
Summary: [Wiki] Auto commit option in UI not documented
Key: STRATOS-771
URL: https://issues.apache.org/jira/browse/STRATOS-771
Project: Stratos
Issu
Shiroshica Kulatilake created STRATOS-770:
-
Summary: Adding in a "Description" field to all definition types
Key: STRATOS-770
URL: https://issues.apache.org/jira/browse/STRATOS-770
Project: St
Hi Madhawa,
On Tue, Sep 2, 2014 at 6:26 PM, Madhawa Bandara wrote:
> The issue seems to be when restarting the apache2.
>
> Here is the log:
> Info: /Stage[main]/Php/File[/etc/apache2/apache2.conf]: Filebucketed
> /etc/apache2/apache2.conf to puppet with sum da32fcc6a783acaebf0d74c17c726b
> f7
[
https://issues.apache.org/jira/browse/STRATOS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chris snow updated STRATOS-734:
---
Description:
This task lists some general improvements:
- complete Dockerfile MAINTAINTER element
-
[
https://issues.apache.org/jira/browse/STRATOS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118171#comment-14118171
]
chris snow edited comment on STRATOS-737 at 9/2/14 1:11 PM:
A
[
https://issues.apache.org/jira/browse/STRATOS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chris snow resolved STRATOS-737.
Resolution: Fixed
Fix Version/s: (was: 4.2.0)
4.1.0
Although there is
Currently, auto-commit can be enabled at the time of subscription via CLI,
UI or REST API for single tenant framework cartridges and at the time of
cartridge deployment for multi-tenant framework cartridges.
However, auto-checkout can only be enabled by updating the init.pp file in
the puppet/modu
The issue seems to be when restarting the apache2.
Here is the log:
Info: /Stage[main]/Php/File[/etc/apache2/apache2.conf]: Filebucketed
/etc/apache2/apache2.conf to puppet with sum da32fcc6a783acaebf0d74c17c726b
f7
Notice: /Stage[main]/Php/File[/etc/apache2/apache2.conf]/content: content
changed
Mariangela Hills created STRATOS-769:
Summary: Enabling Auto Checkout per Git repository
Key: STRATOS-769
URL: https://issues.apache.org/jira/browse/STRATOS-769
Project: Stratos
Issue Typ
[
https://issues.apache.org/jira/browse/STRATOS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills closed STRATOS-740.
Based on JIRA [1] the Admin Guide will be removed and the CLI/REST API/ UI
actions will be gro
Gayan
Normally you would structure your topic hierarchy to be capture the
structure of events and the schema
e.g.
topic
/metrics/datacentre1/system1/cpu
message
{ json format for cpu data }
Paul
On 2 September 2014 11:40, Gayan Gunarathne wrote:
> Hi Paul,
>
> AFAIU with the existing message
Hi Paul,
AFAIU with the existing message design and with your points with the
Pub/Sub ,+1 for improve our Startos messaging model as far as we can as it
will improve the performance as well as standards.As far as I understood
the current messaging model , we can thinking about following two
sugges
Hi,
I thought of implementing $subject as a project to learn Python. I tried
below code to list deployment policies as a test and it works well. I have
not implemented this as a CLI yet.
Advantages,
- JAVA not required.
- Seems Python requires less coding than Java since there are built in
Gayan
I don't understand this. I think this is a mistake on how to use Pub/Sub.
The headers timestamp and expiry should probably be in the message (not
sure)
The destination is part of the pub/sub network
The event-class should be implicitly based on the topic. In other words in
a pub/sub network
We can use custom JSON serializer, deserializer from Stratos end to avoid
the message header.
On Tue, Sep 2, 2014 at 2:14 PM, Gayan Gunarathne wrote:
> Hi Paul,
>
> Please find the example of existing message header and body.AFAIK
> "event-class-name" is the header value used for distinguish th
Hi Paul,
Please find the example of existing message header and body.AFAIK
"event-class-name" is the header value used for distinguish the messages.
header: key expires , value 0
header: key timestamp , value 1409646637558
header: key destination , value /topic/topology
header: key persistent , v
Can you post an example of the headers and body?
Paul
On 2 September 2014 09:17, Gayan Gunarathne wrote:
> Hi Paul,
>
> Currently we have existing java based message publisher with the headers.
> Here we try to use those published messages with the python client. If we
> use JSON structured me
Hi Paul,
Currently we have existing java based message publisher with the headers.
Here we try to use those published messages with the python client. If we
use JSON structured message with headers enclosed we have to change all
other current implementations as well. AFAIK We will distinguished t
What headers do you need to pass?
The way of doing headers with MQTT is to use a structured message (e.g.
JSON) and put some headers into the JSON.
Paul
On 2 September 2014 07:58, Gayan Gunarathne wrote:
>
> We did some analysis regarding the MQTT protocol as well.Following are our
> findings
Hi Nirmal - I just performed a fresh build and it is starting ok.
Many thanks!
On Mon, Sep 1, 2014 at 4:04 PM, Nirmal Fernando wrote:
> Hi Chris,
>
> Further from where you took the Stratos pack? Is it from Jenkins? I faced a
> similar issue with a Jenkins generated pack recently.
>
>
> On Mon,
We did some analysis regarding the MQTT protocol as well.Following are our
findings regarding the MQTT.
MQTT is low bandwidth consumption messaging protocol which supports pub/sub
protocol with the following limitations.
- It has fixed header (2 bytes) . Specifications mentioning that it can
24 matches
Mail list logo
