On Wed, Jan 18, 2017 at 10:46 PM, Marvin Humphrey wrote:
>
>
> Since the consensus to retire seems clear, and since you have already
> started the steps to retire and no one has objected, I have taken the
> liberty of submitting an Attic resolution to the Board for today's meeting.
>
> Thanks Marv
On 2017-01-14 06:06 (-0800), Imesh Gunaratne wrote:
> Hi Marvin,
>
> On Thu, Jan 12, 2017 at 7:34 AM, Marvin Humphrey wrote:
>
> > Hi Stratos community,
> >
> > It seems there is consensus to retire the project. Can we please get the
> > following?
> >
> > - A resolution to move the project
Attic and Infra JIRAs are created:
https://issues.apache.org/jira/browse/ATTIC-162
https://issues.apache.org/jira/browse/INFRA-13335
Thanks
On Sat, Jan 14, 2017 at 7:36 PM, Imesh Gunaratne wrote:
> Hi Marvin,
>
> On Thu, Jan 12, 2017 at 7:34 AM, Marvin Humphrey
> wrote:
>
>> Hi Stratos commun
Hi Marvin,
On Thu, Jan 12, 2017 at 7:34 AM, Marvin Humphrey wrote:
> Hi Stratos community,
>
> It seems there is consensus to retire the project. Can we please get the
> following?
>
> - A resolution to move the project to the Attic, submitted in advance of
> next week's Board meeting.
> - A vol
Hi Stratos community,
It seems there is consensus to retire the project. Can we please get the
following?
- A resolution to move the project to the Attic, submitted in advance of next
week's Board meeting.
- A volunteer to carry through the steps of retirement.
For more info on both of those,
Hi Lakmal,
Agree with the decision based on the facts mentioned above.
Thank you!
On Wed, Dec 14, 2016 at 12:27 AM, Lahiru Sandaruwan
wrote:
> Agreed as there are no activities happened in resent past.
>
> Thanks.
>
> On Tue, Dec 13, 2016 at 1:37 PM, Imesh Gunaratne wrote:
>
>> Hi Lakmal,
>>
Agreed as there are no activities happened in resent past.
Thanks.
On Tue, Dec 13, 2016 at 1:37 PM, Imesh Gunaratne wrote:
> Hi Lakmal,
>
> Agree with your suggestion. Considering the current status of the project
> it would be meaningful to move it to attic unless otherwise if anyone has
> any
Hi Lakmal,
Agree with your suggestion. Considering the current status of the project
it would be meaningful to move it to attic unless otherwise if anyone has
any concerns.
Thanks
Imesh
On Tue, Dec 13, 2016 at 9:13 PM, Lakmal Warusawithana
wrote:
> Hi Devs/Users,
>
> If we look at the project,
Thanks for the detailed information Amit!
One other question, was there any reason for you to use Stratos +
Kubernetes instead of just Kubernetes?
The reason why I'm asking this is at this moment of time, there is no much
development work happening in our project and as a result, there is a
discus
Thanks Imesh,
Following the are the details that we have put in untill now.
We have used source 4.1.5 RC3
Flocker integration
--Added volume source type as flocker. so, user can configure the flocker
volume which can be attached to kubernetes pods.
Here, we had to modify the kubernetes model so
Hi Amit,
It's nice to hear from you!
Would you mind giving more context on your development work?
Thanks
On Thu, Oct 27, 2016 at 4:16 PM, Amit Wankhede
wrote:
> Hi ,
>
> I am working on stratos stuff and have few features implemented e.g.
> flocker integration,UI customization for update appli
gt;
>> [1] https://docs.google.com/document/d/1HnvCzmYqPVpqXSYV-
>> PwGo9d8cmjYKPCPx3TCMKJx8cQ/edit
>>
>> On Tue, Apr 19, 2016 at 2:13 AM, Imesh Gunaratne
>> wrote:
>>
>>> Hi All,
>>>
>>> It's really nice to see the enthusiasm on re
Thanks everyone for taking time to verify 4.1.6-RC1 and vote!
We have received twelve +1s and zero -1s. Therefore the vote has passed,
will proceed with the release.
Thanks
On Wed, Aug 10, 2016 at 9:32 AM, Akila Ravihansa Perera
wrote:
> +1
>
> Verified the source build from tag. Checked licens
+1
Verified the source build from tag. Checked licenses. Ran PHP, Tomcat
samples on Mock IaaS.
On Wed, Aug 10, 2016 at 7:57 AM, Gayan Gunarathne wrote:
> +1
>
> Verified the source build ,license headers and test the sample with mock
> IaaS
>
> Thanks,
> Gayan
>
>
> On Sat, Aug 6, 2016 at 7:51
+1
Verified the source build ,license headers and test the sample with mock
IaaS
Thanks,
Gayan
On Sat, Aug 6, 2016 at 7:51 AM, Imesh Gunaratne wrote:
> Hi All,
>
> This is the first release candidate of Apache Stratos 4.1.6 release.
> Please use the [Discuss] thread for anything but votes.
>
>
+1,
- Tested Mock IaaS single cartridge app
- Verified deploying a simple application via Jaggery console
- Maven build using rc-tag
On Tue, Aug 9, 2016 at 10:24 AM, Lahiru Sandaruwan wrote:
> +1
>
> Verified followings,
> - Built the source with integration test
> - Tested complex app 'php-t
+1
Verified followings,
- Built the source with integration test
- Tested complex app 'php-tomcat-group-postgres-mysql-group-esb' with mock
IaaS
Thanks.
On Tue, Aug 9, 2016 at 6:22 AM, Pubudu Gunatilaka wrote:
> +1
>
> Verified the following.
> - Built the source with integration test
> -
+1
Tested UI and related components in mock-iaas.
Thank You!
On Tue, Aug 9, 2016 at 4:52 PM, Pubudu Gunatilaka wrote:
> +1
>
> Verified the following.
> - Built the source with integration test
> - Verified the license headers with RAT plugin
> - Tested single cartridge app in mock IaaS
>
+1
Verified the following.
- Built the source with integration test
- Verified the license headers with RAT plugin
- Tested single cartridge app in mock IaaS
- Tested single cartridge app in Kubernetes
Thank you!
On Tue, Aug 9, 2016 at 9:38 AM, Anuruddha Liyanarachchi <
anurud...@apache.org
+1
Tested following:
- Built pack from 4.1.6-rc1 tag.
- Verified license headers using RAT tool.
- Built php docker image with PCA 4.1.6
- Deploy / Undeploy single cartridge php app in kubernetes 1.2.1 vagrant
setup.
- Teseted single cartridge deployment in mutilple kubernetes namespaces.
-
+1
Tested console UI & samples with mock IaaS
Regards,
*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, Inc.
lean.enterprise.middleware
0771100911
On Tue, Aug 9, 2016 at 1:22 AM, Isuru Perera wrote:
> +1
>
> I successfully built 4.1.6-rc1 tag (usi
+1
I successfully built 4.1.6-rc1 tag (using a new Maven local repository) and
I also verified the license headers using RAT tool.
Then I checked sha1 and md5 checksums of the binary zip files. I also
verified the GPG signature.
I did a smoke test and tested the console UI.
Thanks!
On Mon, Aug
Hi Darren,
Would you mind verifying 4.1.6-rc1 release and sending a vote? You can find
more information on the release in mail thread [1].
[1] [Vote] Release Apache Stratos 4.1.6-RC1
Thanks
On Wed, Aug 3, 2016 at 12:14 AM, Imesh Gunaratne wrote:
> Hi Darren,
>
> On Wed, Jul 27, 2016 at 7:13 A
+1 Here's my vote, I verified following:
- License headers with RAT tool
- SHA1, MD5 & ASC signatures and hash values of distributions
- PHP single cartridge application on Kubernetes v1.2.0
- Tomcat single cartridge application on Kubernetes v1.2.0
- Group scaling application on Mo
+1
Verified following:
1. Built source successfully with integration test
2. Verified license headers with RAT plugin
3. Un/Deployed and verified simple and complex applications using scripts
in mock iaas
4. Deployed and verified single-cartridge-app using php docker image in
kubernetes 1.2 iaas
+1.
Tested following;
1. Simple app with mock IaaS
2. Scaling app with group scaling against the mock IaaS
3. Simple, single-cartridge-app against Kurbernetes 1.2.0 (
with stratos/php:4.1.5 docker image)
thanks
On Sat, Aug 6, 2016 at 5:21 PM, Imesh Gunaratne wrote:
> Hi All,
>
> T
On Sat, Aug 6, 2016 at 4:52 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> On Sat, Aug 6, 2016 at 4:43 PM, Imesh Gunaratne wrote:
>>
>>
>> On Sat, Aug 6, 2016 at 3:39 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I've gone through the jiras and updated them a
Hi Devs,
On Sat, Aug 6, 2016 at 4:43 PM, Imesh Gunaratne wrote:
>
>
> On Sat, Aug 6, 2016 at 3:39 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi All,
>>
>> I've gone through the jiras and updated them as needed. Since I couldn't
>> resolve the jiras [1] and [2], please re
On Sat, Aug 6, 2016 at 3:39 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:
> Hi All,
>
> I've gone through the jiras and updated them as needed. Since I couldn't
> resolve the jiras [1] and [2], please resolve them.
>
Thanks Thanuja! Let me have a look.
Thanks
>
> [1]. https://is
Hi All,
I've gone through the jiras and updated them as needed. Since I couldn't
resolve the jiras [1] and [2], please resolve them.
[1]. https://issues.apache.org/jira/browse/STRATOS-1639
[2]. https://issues.apache.org/jira/browse/STRATOS-1658
Thanks.
On Sat, Aug 6, 2016 at 3:25 PM, Imesh Gun
Hi Devs,
Everything is ready to start 4.1.6-RC1 vote except for JIRA. Appreciate if
you can assist on that.
Binary files:
https://dist.apache.org/repos/dist/dev/stratos/releases/4.1.6-rc1/
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachestratos-1083/
The tag to b
On Fri, Aug 5, 2016 at 2:39 PM, Anuruddha Liyanarachchi <
anurud...@apache.org> wrote:
> Hi Devs,
>
> I tested the following.
>
> - Build stratos from 4.1.x branch.
> - Build php docker image with
> apache-stratos-python-cartridge-agent-4.1.6-SNAPSHOT
> included
> - Deploy / Undeploy single c
Hi Devs,
I tested the following.
- Build stratos from 4.1.x branch.
- Build php docker image
with apache-stratos-python-cartridge-agent-4.1.6-SNAPSHOT included
- Deploy / Undeploy single cartridge php app in kubernetes 1.2.1 vagrant
setup.
- Teseted app deployment in mutilple kubernetes name
Hi Devs,
I have started testing latest pack build from stratos 4.1.x branch on a
kubernetes setup.
I will share the results afterward.
Regards,
Anuruddha
On Thu, Aug 4, 2016 at 6:47 PM, Imesh Gunaratne wrote:
> The release prepare step completed successfully, now I'm executing the
> release pe
The release prepare step completed successfully, now I'm executing the
release perform.
Appreciate if others can assist on refining JIRA, verifying the features
and the vote mail.
Thanks
On Thu, Aug 4, 2016 at 5:18 PM, Imesh Gunaratne wrote:
> Hi All,
>
> On Tue, Jul 26, 2016 at 8:50 PM, Imesh
Hi All,
On Tue, Jul 26, 2016 at 8:50 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> I did a fresh build on a VM in Rackspace and the integration tests failed.
> Please see the attached log.
> Any thoughts why this is happening?
>
This issue may have raised because of limited resources in the VM. I
s
Hi Darren,
On Wed, Jul 27, 2016 at 7:13 AM, Darren Tang
wrote:
> Hi Imesh:
>
> we have already deployed an openstack liberty for stratos 4.1.5, it not
> works. openstack juno with stratos is fine.
> BTW, Do we have any more details(eg:doc, wiki?) for stratos working with
> openstack? Mayb
Hi Imesh:
we have already deployed an openstack liberty for stratos 4.1.5, it not
works. openstack juno with stratos is fine.
BTW, Do we have any more details(eg:doc, wiki?) for stratos working with
openstack? Maybe the official document is incomplete?
2016-07-27 1:30 GMT+08:00 Imesh Gunar
Hi Darren,
On Tuesday, July 26, 2016, Darren Tang wrote:
> Hi Imesh:
> Thanks for your reply.
> Is there any solution to support last version of openstack? Some advise?
>
>
At the moment we don't have any plans for that. Would you mind sharing your
requirements and how you plan to use stratos
Hi Imesh:
Thanks for your reply.
Is there any solution to support last version of openstack? Some advise?
thanks .
2016-07-26 23:18 GMT+08:00 Imesh Gunaratne :
> Hi Darren,
>
> On Tue, Jul 26, 2016 at 6:19 PM, Darren Tang
> wrote:
>
>> Hi:
>>The next version is 4.1.6 or 4.2.0? release da
Hi Darren,
On Tue, Jul 26, 2016 at 6:19 PM, Darren Tang
wrote:
> Hi:
>The next version is 4.1.6 or 4.2.0? release date?
>thanks your guys.
>
The next release version will be 4.1.6. It would contain bug fixes we have
done since 4.1.5.
We cannot guarantee a release date for this, most pr
On Sun, Jul 24, 2016 at 9:32 PM, Lakmal Warusawithana
wrote:
> Hi,
>
> Since this is a bug fixing release, we can do it from the 4.1.x branch. No
> need to cut it from master branch.
>
+1 Yes, I tried to resolve the merge conflicts but that is not
straightforward. Will release 4.1.x branch.
Tha
Hi,
Since this is a bug fixing release, we can do it from the 4.1.x branch. No
need to cut it from master branch.
On Sun, Jul 10, 2016 at 6:51 PM, Imesh Gunaratne wrote:
> On Sunday, July 10, 2016, Akila Ravihansa Perera
> wrote:
>
>> Hi Imesh,
>>
>> Shall we first cherry-pick only bug fixes
Hi,
I think the original issue is because GET method has been used instead of
POST. Regarding logout issue, I think it is not implemented at the moment.
Might have to track this.
@Imesh: any thoughts?
On Thursday, 21 July 2016, Imesh Gunaratne wrote:
> Hi Alonso,
>
> On Tue, Jul 19, 2016 at 7:3
Hi Alonso,
On Tue, Jul 19, 2016 at 7:30 PM, Iago Alonso Alonso wrote:
> I'm trying to send orders to Apache Stratos via API REST but I'm unnable
> to make it works.
>
Can you please explain what you are trying to achieve?
It would be better to share the request message, response message and th
Thanks and regards.
- Mensaje original -
De: "Isuru Haththotuwa"
Para: "dev"
Enviados: Martes, 19 de Julio 2016 18:15:35
Asunto: Re: Apache Stratos not works as expected
Hi Iago,
Can you please attach the complete server side error log, wso2carbon.log, which
is at /repo
Hi Iago,
Can you please attach the complete server side error log, wso2carbon.log,
which is at /repository/logs/ directory.
On Tue, Jul 19, 2016 at 7:30 PM, Iago Alonso Alonso wrote:
> I'm trying to send orders to Apache Stratos via API REST but I'm unnable
> to make it works.
>
> According to
On Sunday, July 10, 2016, Akila Ravihansa Perera
wrote:
> Hi Imesh,
>
> Shall we first cherry-pick only bug fixes made to master branch and port
> them to stratos-4.1.x? Then we can move everything from stratos-4.1.x to
> master. I'll commit recent fixes made to master branch to stratos-4.1.x as
Hi Imesh,
Shall we first cherry-pick only bug fixes made to master branch and port
them to stratos-4.1.x? Then we can move everything from stratos-4.1.x to
master. I'll commit recent fixes made to master branch to stratos-4.1.x as
well.
Thanks.
On Sun, Jul 10, 2016 at 10:58 AM, Imesh Gunaratne
Hi All,
I tried to rebase 4.1.x branch to master branch, but there are conflicts in
python cartridge agent. It looks like we have committed to both of these
branches in parallel.
Can someone assist me to resolve these conflicts? If not shall we discard
what we have in master branch and take 4.1.x
-
> *De: *"Imesh Gunaratne"
> *Para: *"dev"
> *Enviados: *Domingo, 3 de Julio 2016 20:06:34
> *Asunto: *Re: Empty blank page on some functions in Apache Stratos
>
>
> Hi Iago,
>
> This might be a problem with the identity management features installed
Hi, I created an issue on Jira a week ago. Here it's the link:
https://issues.apache.org/jira/browse/STRATOS-1661
Regards.
- Mensaje original -
De: "Imesh Gunaratne"
Para: "dev"
Enviados: Domingo, 3 de Julio 2016 20:06:34
Asunto: Re: Empty blank page on
Hi Iago,
This might be a problem with the identity management features installed.
Please report this in JIRA:
https://issues.apache.org/jira/browse/STRATOS
Thanks
On Fri, May 27, 2016 at 1:07 AM, Iago Alonso Alonso wrote:
> Hi, I'm new with Apache Stratos and I've downloaded the 4.1.5 version
Hi Devs,
I just created a new version in JIRA [1] for this release.
Shall we please move issues which are already reported to this version and
create new issues for missing ones?
[1] https://issues.apache.org/jira/browse/STRATOS/fixforversion/12337845/
Thanks
On Sun, Jul 3, 2016 at 7:12 PM, Ime
On Sunday, July 3, 2016, Lakmal Warusawithana wrote:
> +1 Imesh, let's do a release
Thanks Lakmal! Will prepare the release.
>
> On Sunday, July 3, 2016, Imesh Gunaratne > wrote:
>
>> Hi Devs,
>>
>> We did our last release on Dec 7th 2015 [1]. Since then we have done many
>> bug fixes. Shall
+1 Imesh, let's do a release
On Sunday, July 3, 2016, Imesh Gunaratne wrote:
> Hi Devs,
>
> We did our last release on Dec 7th 2015 [1]. Since then we have done many
> bug fixes. Shall we release them now?
>
> [1] https://github.com/apache/stratos/releases
> [2] https://github.com/apache/stratos
On Fri, Jun 17, 2016 at 4:15 PM, Akila Ravihansa Perera <
ravihansa3...@gmail.com> wrote:
> Hi,
>
> This issue is now fixed in master branch now. All integration tests are
> now enabled during build time. Stratos master commit build passed
> successfully [1]. Following are the changes made;
>
> -
Thanks Akila for looking into this .
On Friday, June 17, 2016, Akila Ravihansa Perera
wrote:
> Hi,
>
> This issue is now fixed in master branch now. All integration tests are
> now enabled during build time. Stratos master commit build passed
> successfully [1]. Following are the changes made;
>
Hi,
This issue is now fixed in master branch now. All integration tests are now
enabled during build time. Stratos master commit build passed successfully
[1]. Following are the changes made;
- Replaced Axis services wsdl files for AS, SM, CC components from
generated resources (via java2wsdl pl
Hi Akila,
On Thu, Jun 16, 2016 at 9:31 PM, Akila Ravihansa Perera <
raviha...@apache.org> wrote:
> Hi,
>
> It seems integration tests have not been running due to a change made in
> [1] since 2015 Dec 8. Only tests under "policies" group have been running
> since then. When I enabled all integrat
Seems a issue with some dependency archives being corrupted. Will check
locally.
On Thu, May 12, 2016 at 4:05 AM, wrote:
> See <
> https://analysis.apache.org/jenkins/job/stratos/org.apache.stratos$stratos-test-integration/436/
> >
>
> --
> [INFO]
> [INFO]
Hi Zhou Hua Kang
To circumvent these issues you can use the free www.getlantern.org, purchase a
VPN like Astrill or install your own VPN or SOCKS nearby China (typically
Singapore or HK). Good luck!
Best regards from Beijing,
Hans Martin Galliker
--
Sent from my Android phone with K-9 Mail. P
Hi,
Docker needs to be installed first, as a pre-requisite for K8S.
Follow the guidelines https://docs.docker.com/engine/installation/
Thanks,
Sajith
On Sun, May 1, 2016 at 1:22 PM, 周华康 <459673...@qq.com> wrote:
> Hi,
>I try to deploy the stratos on k8s at first,and not the VM(such as
> op
have public google doc to capture architecture. Created a
> doc [1]. Let start with basic components architecture.
>
> [1]
> https://docs.google.com/document/d/1HnvCzmYqPVpqXSYV-PwGo9d8cmjYKPCPx3TCMKJx8cQ/edit
>
> On Tue, Apr 19, 2016 at 2:13 AM, Imesh Gunaratne wrote:
>
>> Hi All,
l
>>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
>>> project aws-ec2: Execution default-test of goal
>>> org.apache.maven.plugins:maven-surefire-plugin:2.17:test failed: The forked
>>> VM terminated without properly saying goodbye. VM crash or System.ex
864623010.jar
>
> /project_workspace/stratos/myLocalRepo/stratos/dependencies/jclouds/aws-ec2/target/surefire/surefire3831696911642642093tmp
>
> /project_workspace/stratos/myLocalRepo/stratos/dependencies/jclouds/aws-ec2/target/surefire/surefire_0949880074517444186tmp
> [ERROR] ->
On Tue, Apr 19, 2016 at 2:13 AM, Imesh Gunaratne wrote:
> Hi All,
>
> It's really nice to see the enthusiasm on re-igniting Stratos and starting
> a new journey. The day Lakmal proposed this I challenged the idea for
> several hours and analyzed it's pros &
:
> Hi All,
>
> It's really nice to see the enthusiasm on re-igniting Stratos and starting
> a new journey. The day Lakmal proposed this I challenged the idea for
> several hours and analyzed it's pros & cons. This thread has already
> discussed those in detail.
>
/surefire/surefire_0949880074517444186tmp
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information
I fixed this issue sometime ago. Sajith, thanks for reporting! Sorry for
the late response.
Regards,
Mariangela
*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185
On Tue, Dec 8, 201
Hi All,
It's really nice to see the enthusiasm on re-igniting Stratos and starting
a new journey. The day Lakmal proposed this I challenged the idea for
several hours and analyzed it's pros & cons. This thread has already
discussed those in detail.
IMO Stratos Ignite Architec
uven.be/bitstream/123456789/470906/3/Walraven-JISA-15.pdf
>
> Thanks.
>
> On Sat, Apr 16, 2016 at 7:01 AM, Lakmal Warusawithana
> wrote:
>
>> Great explanation Lahiru. Supporting multiple PaaS is not necessary to
>> run multi PaaS in one deployment, but if you switch the
tch the PaaS, it will not
> change the user experience with Stratos. No need to re learn all
> complicated PaaS terminologies.
>
> On Fri, Apr 15, 2016 at 12:42 PM, Lahiru Sandaruwan
> wrote:
>
>> Hi Udara,
>>
>> IMO following are some advantages Stratos 5.0 ca
Great explanation Lahiru. Supporting multiple PaaS is not necessary to run
multi PaaS in one deployment, but if you switch the PaaS, it will not
change the user experience with Stratos. No need to re learn all
complicated PaaS terminologies.
On Fri, Apr 15, 2016 at 12:42 PM, Lahiru Sandaruwan
Great to hear that you like to contribute Stratos. Definitely we will help
you to contribute. Yes refacing will make it easy. We are most welcome code
contributors also contribution can done in many ways. Please see [1]
[1] http://stratos.apache.org/community/get-involved.html
On Thu, Apr 14, 201
Hi Udara,
IMO following are some advantages Stratos 5.0 can have.
- If we get the user experience right, users who has used Stratos for
one particular PaaS with Stratos, will not really lock his expertise when
they want to move to a different PaaS. Therefore it avoids the vendor
lock
Hi Lakmal,
To my understanding most Stratos users sticked to one IaaS though Stratos
supported multiple IaaS (cloud bursting). There are very few who used
multiple IaaS such as Ec2 and Openstack at the same time with Stratos.
With above knowledge and Stratos acts as a wrapper for PaaS, will user
Hi Alwis,
Thanks for your help.
See the attached JSON file to create kubernetes cluster and deploy.sh
script. Really I don't understand why the port 4501 coming in the picture
in creating the node.Kubernetes port range is 3-32767.
Regards,
Aanand
Phone: 8098816226
Skype: anand7007
On Wed, A
In a way, this is a wrapper to different PaaS frameworks. However, the new
architecture will also unify concept-wise the different approaches these
different PaaS frameworks have for Container cluster management.
@Lakmal, please correct me if I'm wrong.
Regards,
Chamila de Alwis
Committer and PM
Hi Devs,
I want to understand the theory beside the source code alone, so i
wish you can offer some theory reference attached in the email when you guys
push new code to the new repository of stratos ,so may be the newer like me can
follow your steps quickly.
PS:
With this architecture, will Stratos be a wrapper for different other PaaS
frameworks?
With Jclouds we get a unified interface for multiple IaaSes, with this
approach we thinking of proposing Stratos to provide a unified interface to
talk to different PaaS s?
On Wed, Apr 13, 2016 at 5:38 PM, Cham
The error at line 848 indicates that, for Kubernetes, you've specified a
port which is out of range of the default port range that is assigned to
Service NodePorts [1]. Stratos sets this range to 3-32767, and AFAIR,
Stratos automatically allocates a Node Port for each port mapping in the
Cartri
As Lakmal mentioned, IMO it is important to focus on a single user
experience on top of multiple PaaS frameworks. Various PaaSes have their
own implementations and compositions of common PaaS and Container cluster
related concepts. IMO Stratos Ignite Architecture should scope, at least
initially, t
this looks great!
i hope that you all keep this open to dev community for input as well as
share your progress. please take all your decisions through the
appropriate Apache 2.0 guidelines.
i can see a bright future with these changes. GO did bring many
improvements to PCF.
On Tue, Apr 12, 2
dev@ mailing list. mail header "[Proposal] Stratos 5.0 - Ignite Architecture
"
On Wed, Apr 13, 2016 at 10:23 AM, Tom Davidson wrote:
> Sorry if this is obvious. Where do I see "[Proposal] Stratos 5.0 - Ignite
> Architecture" ?
> Thanks, tom
>
--
Lakmal Warusawithana
Vice President, Apache S
Sorry if this is obvious. Where do I see "[Proposal] Stratos 5.0 - Ignite
Architecture" ?
Thanks, tom
Raj,
Please see "[Proposal] Stratos 5.0 - Ignite Architecture"
thanks
On Tue, Apr 12, 2016 at 8:42 PM, Raj Chudasama
wrote:
> thank you!
>
> are there any major changes coming?
>
>
>
> On Tue, Apr 12, 2016 at 1:07 AM, Lakmal Warusawithana
> wrote:
>
>> Hi Raj,
>>
>> Yes you are correct, there
Hi Jim,
Totally agreed. Thank you Jim for your feedback.
Couple of time community discussed about refacing Stratos but nothing
happen. But Raj mail trigged me and yesterday I met (offline) couple of
PMC/Committers and discussed how to going forward. We came up with a plan
and I will share it rig
Actually, any "refacing" should be discussed on this list,
and the info should be shared as it is being discussed and
debated.
Development on Apache projects are not done behind closed doors.
> On Apr 12, 2016, at 11:12 AM, Raj Chudasama wrote:
>
> thank you!
>
> are there any major changes c
thank you!
are there any major changes coming?
On Tue, Apr 12, 2016 at 1:07 AM, Lakmal Warusawithana
wrote:
> Hi Raj,
>
> Yes you are correct, there were very less dev/activities in last month or
> so. We are in the process of refacing Stratos align with new technology
> trends and demand. Wi
Hi Raj,
Yes you are correct, there were very less dev/activities in last month or
so. We are in the process of refacing Stratos align with new technology
trends and demand. Will share information very soon.
thanks
On Tue, Apr 12, 2016 at 4:13 AM, Raj Chudasama
wrote:
> i was looking at the git
On Mon, Apr 11, 2016 at 4:32 PM, Aanand wrote:
> Hi Imesh,
>
> But we will not get the dashboard like stratos know or is it there.
>
Kubernetes provides few dashboards:
http://kubernetes.io/docs/user-guide/ui/
https://github.com/kubernetes/kube-ui
https://github.com/cockpit-project/cockpit/wiki/
Hi Imesh,
But we will not get the dashboard like stratos know or is it there.
Regards,
Aanand
Phone: 8098816226
Skype: anand7007
On Mon, Apr 11, 2016 at 3:19 PM, Imesh Gunaratne wrote:
> Hi Anand,
>
> On Mon, Apr 11, 2016 at 2:42 PM, Aanand wrote:
>
>> Hi Imesh,
>>
>> Our requirement is: Need
Intresting! I will check.
>From mobile, excuse my typo
On Apr 11, 2016 3:19 PM, "Imesh Gunaratne" wrote:
> Hi Anand,
>
> On Mon, Apr 11, 2016 at 2:42 PM, Aanand wrote:
>
>> Hi Imesh,
>>
>> Our requirement is: Need to have the Stratos on Docker container and also
>> WSO2 cartridges also on the D
Hi Anand,
On Mon, Apr 11, 2016 at 2:42 PM, Aanand wrote:
> Hi Imesh,
>
> Our requirement is: Need to have the Stratos on Docker container and also
> WSO2 cartridges also on the Docker container for production.
>
If you have a better solution please let us know.
>
If your requirement is to use K
Hi Imesh,
Our requirement is: Need to have the Stratos on Docker container and also
WSO2 cartridges also on the Docker container for production.
If you have a better solution please let us know.
please see the issue on this:
Hi Pubudu,
I have installed Stratos from the scratch on docker as per
HI Isuru,
We have internal CEP now, I don't want to bother about the environment
variable right!
Following is the jndi properties file, it seems OK.
connectionfactoryName=TopicConnectionFactory
java.naming.provider.url=tcp://localhost:61616
java.naming.factory.initial=org.apache.activemq.jndi.Ac
Hi Anand,
I think you are having few basic problems:
1. The log file you have sent is too long, I think it has logs from the
very beginning. It would be better to delete it and recreate the problem
again. Then we would only get the logs related to the current problem you
are experienc
Anand,
CEP_HOME refers to the location in the file system where you have the CEP
installed. If you are not using an external CEP, the Stratos can act as a
CEP server as well. In this case, the jndi properties file is at
apache-stratos-4.1.5/repository/conf/jndi.properties location.
On Sat, Apr 9,
Hi Pubudu / Imesh,
This is the content in the file. In this MB URL is right
http://wso2.org/carbon/eventadaptormanager";>
tcp://localhost:61616
org.apache.activemq.jndi.ActiveMQInitialContextFactory
TopicConnectionFactory
topic
Where is jndi.properties file
root@a898ec74aa6c:/apache
1 - 100 of 8448 matches
Mail list logo
