Hi Nirmal,
It seems this is the expected behavior. Quoting from the Wikipedia -
100 ContinueThis means that the server has received the request
headers, and that the client should proceed to send the request body
(in the case of a request for which a body needs to be sent; for
example, a POST req
On Wed, Sep 24, 2014 at 12:42 AM, Rajkumar Rajaratnam
wrote:
>
>
> On Tue, Sep 23, 2014 at 11:54 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Manula,
>>
>>
>>> CEP will receive the health stats once the agent will published them.
>>> Suppose the instance didn't activate due t
On Tue, Sep 23, 2014 at 11:54 PM, Akila Ravihansa Perera wrote:
> Hi Manula,
>
>
>> CEP will receive the health stats once the agent will published them.
>> Suppose the instance didn't activate due to some configuration problem. So
>> how to handle this kind of scenario. Are we use the same time
Hi Manula,
> CEP will receive the health stats once the agent will published them.
> Suppose the instance didn't activate due to some configuration problem. So
> how to handle this kind of scenario. Are we use the same time threshold
> mechanism to handle that ?
>
That's a good point!
I think w
Hi Sajith,
I used the docker image you provided and started kubernetes entities
successfully via Stratos in the host cluster. Following is the output of
one of the minions.
*core@minion-2** ~ $* docker ps
CONTAINER IDIMAGE COMMAND
CREATED
On Sun, Sep 21, 2014 at 1:41 PM, Nirmal Fernando
wrote:
> I posted them in a previous email in this thread.
>
> On Sun, Sep 21, 2014 at 1:37 PM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Nirmal,
>>
>> Can you post the curl request and request body data?
>>
>> Thanks.
>>
>> On
I posted then in a previous email in this thread.
On Sun, Sep 21, 2014 at 1:37 PM, Akila Ravihansa Perera
wrote:
> Hi Nirmal,
>
> Can you post the curl request and request body data?
>
> Thanks.
>
> On Sun, Sep 21, 2014 at 1:11 PM, Nirmal Fernando
> wrote:
> > Hi Akila,
> >
> > When I register
Hi Nirmal,
Can you post the curl request and request body data?
Thanks.
On Sun, Sep 21, 2014 at 1:11 PM, Nirmal Fernando wrote:
> Hi Akila,
>
> When I register a new Kubernetes host cluster, I see two response codes in
> the http response; Any idea?
>
> * About to connect() to 127.0.0.1 port 94
Hi Akila,
When I register a new Kubernetes host cluster, I see two response codes in
the http response; Any idea?
* About to connect() to 127.0.0.1 port 9443 (#0)
* Trying 127.0.0.1...
* Adding handle: conn: 0x7fd2b5021000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleT
Thanks Sajith... I'll continue testing.
On Sat, Sep 20, 2014 at 2:20 PM, Sajith Kariyawasam wrote:
> Hi,
>
> Docker image 54.254.64.141:5000/stratos-php is now updated with the above
> mentioned fixes
>
> Thanks,
> Sajith
>
> On Sat, Sep 20, 2014 at 10:47 AM, Sajith Kariyawasam
> wrote:
>
>> Se
Hi,
Docker image 54.254.64.141:5000/stratos-php is now updated with the above
mentioned fixes
Thanks,
Sajith
On Sat, Sep 20, 2014 at 10:47 AM, Sajith Kariyawasam
wrote:
> Seems I have tested with an old cartridge agent pack. Also it seems
> cartridge agent always expects MIN_COUNT, which ideal
Seems I have tested with an old cartridge agent pack. Also it seems
cartridge agent always expects MIN_COUNT, which ideally should have been
only when clustering is enabled.
I will do those fixes and update the image
On Fri, Sep 19, 2014 at 6:21 PM, Sajith Kariyawasam wrote:
> I have set up a do
I have set up a docker registry and pushed the image there, and that can be
accessed as 54.254.64.141:5000/stratos-php
Thanks,
Sajith
On Fri, Sep 19, 2014 at 12:44 PM, Sajith Kariyawasam
wrote:
> Found an issue in the docker php image, that MB/CEP ips and ports are not
> getting set in stratos.
Found an issue in the docker php image, that MB/CEP ips and ports are not
getting set in stratos.sh.
I have fixed that and pushed the updated image.
Please find the command below which you need to use in order to start an
instance.
docker run -d -P --name sajith --env SERVICE_NAME=php --env CLUST
This is the latest replicationController json after fixing the issue with
payload.
{
"kind": "ReplicationController",
"id": "test2.php.domain",
"apiVersion": "v1beta1",
"labels": {
"name": "test2.php.domain"
},
"desiredState": {
"replicas": 2,
"repli
Upon a subscription for a docker Cartridge, now autoscaler calls CC, and CC
deploys Kubernetes entities into the Kubernetes host cluster. Please see
the following log.
[2014-09-19 12:09:01,194] INFO
{org.apache.stratos.messaging.message.processor.topology.CompleteTopologyMessageProcessor}
- Topo
Please note that the environment variable section in the above
replicationController is not completed, found a bug! Will change the
updated version once it is fixed.
Following is a sample auto-generated Kubernetes proxy service;
{
"kind": "Service",
"id": "test2-php-domain",
"port": 4
Here's a auto-generated Kubernetes replication controller json as of
now, for clarity. This could change based on the other testing.
{
"kind": "ReplicationController",
"id": "test2.php.domain",
"apiVersion": "v1beta1",
"labels": {
"name": "test2.php.domain"
},
"desi
Here's the jsons and requests used.
Register Host ClusterHost Json
{
"groupId": "KubGrp1",
"description": "Kubernetes CoreOS cluster on EC2 ",
"kubernetesMaster": {
"hostId" : "KubHostMaster1",
"hostname" : "master.dev.kubernetes.example.org",
On Fri, Sep 19, 2014 at 9:56 AM, Nirmal Fernando
wrote:
> Hi all,
>
> I've carried out following testing on the docker integration branch, so
> far, and here's the status.
>
> * Set up a local Kubernetes cluster (master and 2 minions) and tested
> basic Kubernetes operations on it.
> * Tested Kub
Hi all,
I've carried out following testing on the docker integration branch, so
far, and here's the status.
* Set up a local Kubernetes cluster (master and 2 minions) and tested basic
Kubernetes operations on it.
* Tested Kubernetes host registration and here I faced an issue when hosts
getting p
Please take a moment to update the status of the tasks listed for 4.1.0 M1;
http://goo.gl/vpdZIa
Thanks.
On Mon, Sep 15, 2014 at 8:58 AM, Nirmal Fernando
wrote:
> Currently hitting an issue in the docker-integration branch :
> https://issues.apache.org/jira/browse/STRATOS-798
>
> On Sun, Sep 14
Currently hitting an issue in the docker-integration branch :
https://issues.apache.org/jira/browse/STRATOS-798
On Sun, Sep 14, 2014 at 11:12 PM, Nirmal Fernando
wrote:
> Please avoid committing changes that are not available for M1. I am gonna
> start an end-to-end testing.
>
> On Fri, Sep 12,
Please avoid committing changes that are not available for M1. I am gonna
start an end-to-end testing.
On Fri, Sep 12, 2014 at 10:23 AM, Nirmal Fernando
wrote:
> I create 4.1.0 M1 and M2 versions in the Jira. Please update the version
> of the Jiras you are planning to get to the first developer
I create 4.1.0 M1 and M2 versions in the Jira. Please update the version of
the Jiras you are planning to get to the first developer preview as 4.1.0
M1.
We need to come up with a code freeze date too. I'd suggest we code freeze
for M1 on 13th September 8pm PST. Thoughts?
On Wed, Sep 10, 2014 at
I'll create a 4.1.0 M1 version, so that we can tag Jiras that are/will be
ready.
On Wed, Sep 10, 2014 at 6:40 PM, Lakmal Warusawithana
wrote:
> If we are targeting this week for M1, what are the features can ship? JIRA
> list?
>
> On Wed, Sep 10, 2014 at 4:55 PM, Lakmal Warusawithana
> wrote:
>
If we are targeting this week for M1, what are the features can ship? JIRA
list?
On Wed, Sep 10, 2014 at 4:55 PM, Lakmal Warusawithana
wrote:
> Hi Dev,
>
> How about $subject? IMO, it will help all devs to check their dependancies.
>
> thanks
>
> --
> Lakmal Warusawithana
> Vice President, Apach
Hi Dev,
How about $subject? IMO, it will help all devs to check their dependancies.
thanks
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
28 matches
Mail list logo
