[Dev] Error when running the Cassandra Docker
Hi, I'm currently working on creating a cassandra cartridge for apache stratos using docker. I was able to successfully build the cassandra cartridge in the virtual machine and the member is getting activated successfully. When i try to run the cassandra inside the instance, I am getting the following error. root@instance-0001:/opt/cassandra/bin# ./cassandra xss = -ea -javaagent:./../lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1240M -Xmx1240M -Xmn310M -XX:+HeapDumpOnOutOfMemoryError ./cassandra: 151: exec: root@instance-0001:/opt/cassandra/bin# java: not found Below is the cassandra file from the line 146 to 154 if [ x$foreground != x ]; then cassandra_parms=$cassandra_parms -Dcassandra-foreground=yes exec $NUMACTL $JAVA $JVM_OPTS $cassandra_parms -cp $CLASSPATH $props $class # Startup CassandraDaemon, background it, and write the pid. else exec $NUMACTL $JAVA $JVM_OPTS $cassandra_parms -cp $CLASSPATH $props $class - [ ! -z $pidpath ] printf %d $! $pidpath true fi I would like to know what causes this issue. Thank you, -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error when running the Cassandra Docker
Hi Manula, I did try increasing it to JVM_OPTS to Xss280 and Xss380, still I'm getting that issue. On Fri, Oct 3, 2014 at 2:32 PM, Sajith Kariyawasam saj...@wso2.com wrote: On Fri, Oct 3, 2014 at 2:26 PM, Manula Chathurika Thantriwatte manu...@wso2.com wrote: Hi Vishanth, Can you increase the JVM_OPTS values and try again. Thanks ! On Fri, Oct 3, 2014 at 1:29 PM, Vishanth Balasubramaniam vishan...@wso2.com wrote: Hi, I'm currently working on creating a cassandra cartridge for apache stratos using docker. I was able to successfully build the cassandra cartridge in the virtual machine and the member is getting activated successfully. When i try to run the cassandra inside the instance, I am getting the following error. root@instance-0001:/opt/cassandra/bin# ./cassandra xss = -ea -javaagent:./../lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1240M -Xmx1240M -Xmn310M -XX:+HeapDumpOnOutOfMemoryError ./cassandra: 151: exec: root@instance-0001:/opt/cassandra/bin# java: not found Seems java bin directory is also not properly set to $PATH what does echo $JAVA_HOME and echo $PATH gives you? Below is the cassandra file from the line 146 to 154 if [ x$foreground != x ]; then cassandra_parms=$cassandra_parms -Dcassandra-foreground=yes exec $NUMACTL $JAVA $JVM_OPTS $cassandra_parms -cp $CLASSPATH $props $class # Startup CassandraDaemon, background it, and write the pid. else exec $NUMACTL $JAVA $JVM_OPTS $cassandra_parms -cp $CLASSPATH $props $class - [ ! -z $pidpath ] printf %d $! $pidpath true fi I would like to know what causes this issue. Thank you, -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sajith Kariyawasam* *Committer and PMC member, Apache Stratos,WSO2 Inc., http://wso2.com http://wso2.comAMIE (SL)Mobile: +94772269575* -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture][APIM] Swagger validation
Hi Madusanka, I too think the right approach is to validate at the backend. I came across this json schema validator project [1] sometime back, check if this is useful for you in some way. [1] - https://github.com/fge/json-schema-validator Regards, Vishanth On Fri, Mar 20, 2015 at 12:36 PM, Madusanka Premaratne madusan...@wso2.com wrote: Hi all, As you all know APIM uses YAML and Swagger. We have already done YAML validation part and will be there as real time yaml syntax validator in the upcoming release. In the validation of swagger we can either validate swagger at the front-end using javascript or validate at the backend using json schema validator. According to the offline discussions I had with Colin and Jo, it is more suitable to validate it at the backend, because there are two ways(write/import) to feed a swagger doc. Does anyone worked with a json schema validator which can be used to fulfil our need? Feedbacks and suggestions for this improvement would be appreciated. Thanks, -- *Madusanka Premaratne* | Associate Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 835 70 73| Work: +94 112 145 345 Email: madusan...@wso2.com | Web: www.wso2.com [image: Facebook] https://www.facebook.com/maduzanka [image: Twitter] https://twitter.com/rmmpremaratne [image: Google Plus] https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub [image: Linkedin] http://lk.linkedin.com/in/madusanka/ [image: Instagram] http://instagram.com/madusankapremaratne [image: Skype] http://@rmmpremaratne ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ClassNotFoundException when running SAML SSO Test in IS 5.1.0 on TAF 4.3.1
) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) INFO [org.wso2.carbon.automation.engine.testlisteners.TestManagerListener] - On test failure... Yet, I could see velocity-1.5.jar in the WEB-INF/lib folder of the travelocity application deployed in the embedded tomcat. I have tried importing the org.apache.velocity package to the sso.agent bundle also. Highly appreciate if someone can point the cause for this. Also, please note that this test worked properly on carbon 4.2.0 and TAF 4.2.8. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/is/5.1.0/modules/integration/tests/src/test/java/org/wso2/carbon/identity/tests/saml/SAMLSSOTestCase.java Thanks, Malithi. -- *Malithi Edirisinghe* Senior Software Engineer WSO2 Inc. Mobile : +94 (0) 718176807 malit...@wso2.com -- *Malithi Edirisinghe* Senior Software Engineer WSO2 Inc. Mobile : +94 (0) 718176807 malit...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build failure while building the carbon mediation in develop branch
-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/InboundEndpointInfoDTO.java:[54,11] error: cannot find symbol [ERROR] [ERROR] class InboundEndpointInfoDTO [ERROR] /home/kathees/Documents/ESBTask/Task2/NewKafkaRepo/carbon-mediation/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/InboundEndpointInfoDTO.java:[58,36] error: cannot find symbol [ERROR] [ERROR] class InboundEndpointInfoDTO [ERROR] /home/kathees/Documents/ESBTask/Task2/NewKafkaRepo/carbon-mediation/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/InboundEndpointsDataStore.java:[24,53] error: package org.apache.synapse.transport.passthru.core.ssl does not exist [ERROR] [ERROR] /home/kathees/Documents/ESBTask/Task2/NewKafkaRepo/carbon-mediation/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/InboundEndpointsDataStore.java:[119,96] error: cannot find symbol [ERROR] [ERROR] class InboundEndpointsDataStore [ERROR] /home/kathees/Documents/ESBTask/Task2/NewKafkaRepo/carbon-mediation/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/PersistenceUtils.java:[146,20] error: cannot find symbol [ERROR] [ERROR] class PersistenceUtils [ERROR] /home/kathees/Documents/ESBTask/Task2/NewKafkaRepo/carbon-mediation/components/inbound-endpoints/org.wso2.carbon.inbound.endpoint.persistence/src/main/java/org/wso2/carbon/inbound/endpoint/persistence/PersistenceUtils.java:[147,35] error: cannot find symbol [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 about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.inbound.endpoint.persistence Thanks, Kathees -- Kathees Software Engineer, email: kath...@wso2.com mobile: +94772596173 -- -- Chanaka Fernando Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 773337238 Blog : http://soatutorials.blogspot.com LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 Twitter:https://twitter.com/chanakaudaya Wordpress:http://chanakaudaya.wordpress.com -- Kathees Software Engineer, email: kath...@wso2.com mobile: +94772596173 -- -- Chanaka Fernando Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 773337238 Blog : http://soatutorials.blogspot.com LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 Twitter:https://twitter.com/chanakaudaya Wordpress:http://chanakaudaya.wordpress.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Chamila de Alwis
/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Gayan Gunarathne Technical Lead WSO2 Inc. (http://wso2.com) email : gay...@wso2.com | mobile : +94 766819985 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Carbon] org.apache.jasper.JasperException when trying to access the Carbon Server URL
) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:64) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:49) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:516) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1086) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:659) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1558) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1515) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) All the Jars are getting scan by the CarbonTomcatJarScanner. Can someone tell me what is the reason for this? Thanks Best Regards /Thusitha -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] JSON parsing platform standard library
Hi Inosh, IMO i think it is either Jackson or Gson. Jackson is considered to be a faster library than Gson and also I remember Gson was having some case insensitive problem, I am not sure if it still does. Regards, Vishanth. On Mon, Mar 23, 2015 at 10:57 PM, Prabath Abeysekera praba...@wso2.com wrote: Hi Guys, Came across [4] while I was searching for any good performance benchmark done over the JSON parser libraries around. As it appears, the results were published like 3 years back and I'm pretty sure that most of these libraries have come a long way since then. However, based on the results the blog carries, I'm tempted to use either Jackson or Staxon purely because of the performance numbers, since there's going to be loads of serialization/de-serilaization of JSON messages taking place in the critical path as part of most of the MDM functionalities. One interesting point to note is that, even though, the numbers published against Staxon doesn't look too attractive, things can perhaps be different if we properly use it in its streaming-mode. Therefore, I'd prefer we do some tests around and select one out of the libraries mentioned above. @Inosh, would you be able check on this and see what suits us the most? [4] http://blog.novoj.net/2012/02/05/json-java-parsers-generators-microbenchmark/ Cheers, Prabath On Mon, Mar 23, 2015 at 9:41 PM, Ishan Jayawardena is...@wso2.com wrote: Hi Inosh, ESB uses StAXON [1] in builders/formatters and Jayway JsonPath [2] for JSONPath evaluation. The ScriptMediator depends on google-gson[3] [1] https://github.com/beckchr/staxon [2] https://github.com/jayway/JsonPath [3] https://code.google.com/p/google-gson/ Thanks, Ishan. On Mon, Mar 23, 2015 at 7:25 PM, Inosh Perera ino...@wso2.com wrote: Hi all, What is platform standard library used for JSON parsing? I have seen some variation such as Gson, Jackson, jsonpath. Regards, Inosh -- Inosh Perera Software Engineer, WSO2 Inc. Tel: 0785293686 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ishan Jayawardena Senior Software Engineer ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cross database pagination
Hi Dulitha, Found this Pagination with ROWNUM example (source [1]), sharing it if you could find it helpful: select * from ( select /*+ FIRST_ROWS(n) */ a.*, ROWNUM rnum from ( your_query_goes_here, with order by ) a where ROWNUM = :MAX_ROW_TO_FETCH ) where rnum = :MIN_ROW_TO_FETCH; :FIRST_ROWS(N) tells the optimizer, Hey, I'm interested in getting the first rows, and I'll get N of them as fast as possible. :MAX_ROW_TO_FETCH is set to the last row of the result set to fetch—if you wanted rows 50 to 60 of the result set, you would set this to 60. :MIN_ROW_TO_FETCH is set to the first row of the result set to fetch, so to get rows 50 to 60, you would set this to 50. [1] - http://www.oracle.com/technetwork/issue-archive/2006/06-sep/o56asktom-086197.html Thank you, Vishanth On Mon, Mar 23, 2015 at 2:10 PM, Udara Rathnayake uda...@wso2.com wrote: Hi All, We faced an issue while following the above method. Even if we store the DB specific select query within a configurable file, number of properties and property order may vary from one to another. If we are using prepared statements we need to reflect above differences within our logic. We can solve this by using stored procedures but calling a stored procedure is still difference from one to another. Following is the proposed solution: We are going to delegate these DB specific logic to a driver. We can provide a default driver for H2/MySQL/Postgres and another driver for Oracle initially. If someone is going to use a different DB type they can develop their own. How to use : During product creation we copy the default driver (Since we are using H2 by default) to the CARBON_HOME/repository/components/lib directory. If we are going with Oracle we can replace the default one with Oracle. (Remove default one from lib and dropins directories) Appreciate any feedback on this. Regards, UdaraR On Wed, Mar 4, 2015 at 12:57 PM, Udara Rathnayake uda...@wso2.com wrote: Hi All, We had the same discussion yesterday and had a small chat with Prabath too. Since there is no viable solution ATM we decided to store these select statements in a script and pick according to the data-source configuration. Eg:- /dbscripts/social/oracle/select_script, /dbscripts/social/sql/select_script Since we can use the same select statement with limit,offset for h2,MySQL,PostgreSQL may be we can have a common one. Thoughts? Regards, UdaraR On Mon, Mar 2, 2015 at 8:31 AM, Dulitha Wijewantha duli...@wso2.com wrote: Hi guys, I am working on creating a device listing API that supports pagination. In the SQL world, LIMIT and OFFSET seems to be the standard way of doing pagination in MySQL and PostgreSQL. Below is an example, SELECT Device.id, Device.name FROM Device LIMIT 10 OFFSET 10 But Oracle seems to be using rownum. What's the recommended approach in doing this? Cheers~ -- Dulitha Wijewantha (Chan) Software Engineer - Mobile Development WSO2 Inc Lean.Enterprise.Middleware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : 1 4087864651 | 94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : 1 4087864651 | 94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Himasha Guruge
Congratulations Himasha!! On Wed, May 27, 2015 at 2:35 PM, Tharik Kanaka tha...@wso2.com wrote: Congratulations Himasha On Wed, May 27, 2015 at 2:22 PM, Vijitha Ekanayake vijit...@wso2.com wrote: Congratulations Himasha ...!!! On Wed, May 27, 2015 at 2:07 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Congratulations !!! On Wed, May 27, 2015 at 1:55 PM, Dilan Udara Ariyaratne dil...@wso2.com wrote: Congratz, Himasha !!! *Dilan U. Ariyaratne* Software Engineer WSO2 Inc. http://wso2.com/ Mobile: +94775149066 lean . enterprise . middleware On Wed, May 27, 2015 at 12:25 PM, Rajith Vitharana raji...@wso2.com wrote: Congrats . :) On Wed, May 27, 2015 at 12:15 PM, Thusitha Thilina Dayaratne thusit...@wso2.com wrote: Congratulations ...!! On Wed, May 27, 2015 at 12:14 PM, Milan Perera mi...@wso2.com wrote: Congratz Himasha..!!! On Wed, May 27, 2015 at 12:11 PM, Dinithi De Silva dinit...@wso2.com wrote: Congratz Himasha :) On Wed, May 27, 2015 at 11:46 AM, Damith Wickramasinghe dami...@wso2.com wrote: Congrats ... :) :) On Wed, May 27, 2015 at 11:43 AM, Shiva Balachandran sh...@wso2.com wrote: Congrats and Good Luck Himasha! :) On Wed, May 27, 2015 at 11:41 AM, Maheeka Jayasuriya mahe...@wso2.com wrote: Congratulations Himasha !!! Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Wed, May 27, 2015 at 11:40 AM, Madhuranga Bandara madhura...@wso2.com wrote: Congratulations !!! *Madhuranga Sampath Bandara* Software Engineer ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 Blog - https://shivabalachandran.wordpress.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Software Engineer WSO2 Inc.; http://wso2.com http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg lean.enterprise.middleware mobile: *+94728671315 %2B94728671315* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dinithi De Silva* Associate Software Engineer, WSO2 Inc. m:+94716667655 | e:dinit...@wso2.com | w: www.wso2.com | a: #20, Palm Grove, Colombo 03 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Milan Harindu Perera Software Engineer *WSO2, Inc* (+94) 77 309 7088 lean . enterprise . middleware http://lk.linkedin.com/in/milanharinduperera ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thusitha Dayaratne Software Engineer WSO2 Inc. - lean . enterprise . middleware | wso2.com Mobile +94712756809 Blog alokayasoya.blogspot.com Abouthttp://about.me/thusithathilina ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Rajith Vitharana Software Engineer, WSO2 Inc. : wso2.com Mobile : +94715883223 Blog : http://lankavitharana.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vijitha Ekanayake Software Engineer*, *WSO2, Inc.; http://wso2.com/ Mobile : +94 777 24 73 39 | +94 718 74 44 08 lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Tharik Kanaka* | Associate Software Engineer WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka Email: tha...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Private PaaS product pack name
+1 for wso2ppaas-4.1.0 and wso2server.sh On Wed, May 27, 2015 at 2:09 PM, Anuruddha Liyanarachchi anurudd...@wso2.com wrote: Hi, +1 for renaming to wso2server.sh and wso2ppass-4.1.0 On Wed, May 27, 2015 at 2:04 PM, Imesh Gunaratne im...@wso2.com wrote: On Wed, May 27, 2015 at 11:49 AM, Udara Liyanage ud...@wso2.com wrote: Hi, We need to rename stratos.sh to wso2server.sh then? +1 On Wed, May 27, 2015 at 11:49 AM, Udara Liyanage ud...@wso2.com wrote: Hi, We need to rename stratos.sh to wso2server.sh then? On Wed, May 27, 2015 at 10:56 AM, Imesh Gunaratne im...@wso2.com wrote: +1 for naming the product as wso2ppaas-4.1.0. On Wed, May 27, 2015 at 10:53 AM, Lahiru Sandaruwan lahi...@wso2.com wrote: IMO we should rename it to ppaas*. Thanks. On Wed, May 27, 2015 at 10:50 AM, Udara Liyanage ud...@wso2.com wrote: Hi, Since we clone Stratos in PP 400, the name of the product was Stratos. However since we are not cloning Stratos code base, but just create a new product with existing features except for UI, are we going to rename the product or keep the same name as in 400? -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 a thili...@wso2.comnurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Dinithi De Silva
Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chamin Dias *Software Engineer* Mobile : +94 (0) 716 097455 %2B94%20%280%29%20773%20451194 cham...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Supun Sethunga* Software Engineer WSO2, Inc. http://wso2.com/ lean | enterprise | middleware Mobile : +94 716546324 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards S.Sriashalya, WSO2 *Inc*. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Thanks and Regards,* Anuruddha Lanka Liyanarachchi Software Engineer - WSO2 Mobile : +94 (0) 712762611 Tel : +94 112 145 345 anurudd...@wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Vishanth Balasubramaniam* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: *+94771737718* about me: *http://about.me/vishanth http://about.me/vishanth* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] EMM - Cannot Add Device - Illegal access attempt
)
at org.jaggeryjs.rhino.emm.modules.c6.call(/emm/modules/device.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.emm.api.c4._c_anonymous_14(/emm/api/deviceRouter.js:159)
at org.jaggeryjs.rhino.emm.api.c4.call(/emm/api/deviceRouter.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.emm.modules.c5._c_anonymous_13(/emm/modules/goose.js:174)
at org.jaggeryjs.rhino.emm.modules.c5.call(/emm/modules/goose.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.emm.modules.c3._c_callAPI_12(/emm/modules/absolute.js:171)
at org.jaggeryjs.rhino.emm.modules.c3.call(/emm/modules/absolute.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
at
org.jaggeryjs.rhino.emm.modules.c3._c_anonymous_15(/emm/modules/absolute.js:228)
at org.jaggeryjs.rhino.emm.modules.c3.call(/emm/modules/absolute.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at org.jaggeryjs.rhino.emm.c0._c_script_0(/emm//index.jag:189)
at org.jaggeryjs.rhino.emm.c0.call(/emm//index.jag)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.jaggeryjs.rhino.emm.c0.call(/emm//index.jag)
at org.jaggeryjs.rhino.emm.c0.exec(/emm//index.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:567)
... 75 more
Caused by: java.lang.SecurityException: Illegal access attempt to cache ]
owned by tenant
{[carbon.super],[-1234]}
by tenant
{[carbon.super],[1]}
at org.wso2.carbon.caching.impl.Util.checkAccess(Util.java:45)
at
org.wso2.carbon.caching.impl.CarbonCacheManager.getCache(CarbonCacheManager.java:111)
at
org.wso2.carbon.user.core.common.UserRolesCache.getUserRolesCache(UserRolesCache.java:67)
at
org.wso2.carbon.user.core.common.UserRolesCache.addToCache(UserRolesCache.java:93)
at
org.wso2.carbon.user.core.common.AbstractUserStoreManager.addToUserRolesCache(AbstractUserStoreManager.java:2838)
at
org.wso2.carbon.user.core.common.AbstractUserStoreManager.getRoleListOfUser(AbstractUserStoreManager.java:2020)
at sun.reflect.GeneratedMethodAccessor142.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 105 more
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Vishanth Balasubramaniam*
Committer PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94771737718*
about me: *http://about.me/vishanth http://about.me/vishanth*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] API-M VM/Docker Cartridge
Hi Pubudu, The path to the dockerfile in [1] is incorrect. It should be corrected to https://github.com/wso2/product-private-paas/blob/master/cartridges/docker/wso2am-1.9.0 [1] - https://hub.docker.com/r/wso2/am/ Regards, Vishanth On Wed, Sep 2, 2015 at 6:55 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Imesh, > > Will update API-Manager to 1.9.1 for the Private-Paas 4.1.0-GA. Now the > API-Manager 1.9.0 docker image is available in docker hub[1]. > > [1] - https://hub.docker.com/r/wso2/am/ > > Thank you! > > On Mon, Aug 31, 2015 at 1:06 PM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Devs, >> >> API-M has released 1.9.1 [1]. We might need to use this for Private PaaS >> 4.1.0-GA >> [1] http://wso2.com/api-management/try-it/ >> >> Thanks >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.gunaratne.org >> Lean . Enterprise . Middleware >> >> > > > -- > > *Pubudu Gunatilaka* > Software Engineer > WSO2, Inc.: http://wso2.com > lean.enterprise.middleware > mobile: +94 77 4078049 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94771737718* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] API-M VM/Docker Cartridge
Hi, I corrected the URL. Regards, Vishanth On Thu, Sep 3, 2015 at 11:42 AM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi Pubudu, > > The path to the dockerfile in [1] is incorrect. It should be corrected to > > https://github.com/wso2/product-private-paas/blob/master/cartridges/docker/wso2am-1.9.0 > > [1] - https://hub.docker.com/r/wso2/am/ > > Regards, > Vishanth > > On Wed, Sep 2, 2015 at 6:55 PM, Pubudu Gunatilaka <pubu...@wso2.com> > wrote: > >> Hi Imesh, >> >> Will update API-Manager to 1.9.1 for the Private-Paas 4.1.0-GA. Now the >> API-Manager 1.9.0 docker image is available in docker hub[1]. >> >> [1] - https://hub.docker.com/r/wso2/am/ >> >> Thank you! >> >> On Mon, Aug 31, 2015 at 1:06 PM, Imesh Gunaratne <im...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> API-M has released 1.9.1 [1]. We might need to use this for Private PaaS >>> 4.1.0-GA >>> [1] http://wso2.com/api-management/try-it/ >>> >>> Thanks >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.gunaratne.org >>> Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> >> *Pubudu Gunatilaka* >> Software Engineer >> WSO2, Inc.: http://wso2.com >> lean.enterprise.middleware >> mobile: +94 77 4078049 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Vishanth Balasubramaniam* > Committer & PMC Member, Apache Stratos, > Software Engineer, WSO2 Inc.; http://wso2.com > > mobile: *+94771737718* > about me: *http://about.me/vishanth <http://about.me/vishanth>* > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94771737718* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fix for https://wso2.org/jira/browse/IDENTITY-4646
Hi, Please review and merge the following PRs. - https://github.com/wso2/carbon-identity-framework/pull/321 - https://github.com/wso2/carbon-identity-framework/pull/322 This is the fix for https://wso2.org/jira/browse/IDENTITY-4646 To improve performance on user self registration in UserInformationRecoveryService of identity management. Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fixing IDENTITY-4722
Hi, Please review and merge the PR [1] which has the fix for [2]. [1] - https://github.com/wso2-extensions/identity-outbound-auth-passive-sts/pull/10 [2] - https://wso2.org/jira/browse/IDENTITY-4722 Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fixing IDENTITY-4722
Thanks Godwin. Fixed now. On Thu, Jun 23, 2016 at 7:50 PM, Godwin Shrimal <god...@wso2.com> wrote: > Added a comment to PR. > > On Thu, Jun 23, 2016 at 6:58 AM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Hi, >> >> Please review and merge the PR [1] which has the fix for [2]. >> >> [1] - >> https://github.com/wso2-extensions/identity-outbound-auth-passive-sts/pull/10 >> >> [2] - https://wso2.org/jira/browse/IDENTITY-4722 >> >> Regards, >> Vishanth >> >> -- >> *Vishanth Balasubramaniam* >> Committer & PMC Member, Apache Stratos, >> Software Engineer, WSO2 Inc.; http://wso2.com >> >> mobile: *+94 77 17 377 18* >> about me: *http://about.me/vishanth <http://about.me/vishanth>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Godwin Amila Shrimal* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94772264165* > linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>* > twitter: https://twitter.com/godwinamila > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] PPaaS Artifact Migration Tool- Naming Convention for Application ID
On Wed, Jan 13, 2016 at 6:24 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Malmee, > > I would suggest to use application id as alias with application suffix. > > For an example if the alias is myphp we can use application id as > myphp-application. This naming convention will be easy to identify > applications rather than using only the alias. > > +1 > Thank you! > > On Wed, Jan 13, 2016 at 12:17 PM, Malmee Weerasinghe <mal...@wso2.com> > wrote: > >> Hi All, >> >> In the tool that is being developed to convert artifact JSON files of >> PPaaS 4.0.0 to PPaaS 4.1.x, the conversion has to be done as such one >> application has to be created for one subscription. In this conversion what >> should be the naming convention of the application ID? One approach is to >> use 'alias' in subscription data as an ID for a particular application. >> >> Thanks >> -- >> Malmee Weerasinghe >> WSO2 Intern >> mobile : (+94)* 71 7601905* | email : <dehan.vith...@aiesec.net> >> mal...@wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774079049 <%2B94772207163> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSoC Dockerfiles] Status update
Great work Abhishek.
On Tue, Jun 28, 2016 at 1:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Dear Mentors,
>
> I have implemented the following components after our last discussion:
>
> 1. Ability to configure product testing, to specify multiple products to
> test, versions, provisioning methods and various deployment platform. The
> config is implemented using JSON and looks something like this:
>
> "products": {
> "esb": {
> "enabled":"true",
> "name": "wso2esb",
> "version": "4.9.0",
> "provisioning_method": "puppet"
> }
> }
>
>
> This is pretty rudimentary at this point and will get sophisticated as we
> add more features.
>
> 2. Enhanced existing test framework to also account puppet provisioning.
>
> 3. Redirect test results from all the products to a final report-like log
> file, which contains success/failure along with test run times.
>
> The changes can be reviewed in the git repo [1], would love to get your
> feedback/comments. I would schedule a hangout call for tomorrow (6/29) at
> 10am for demo.
>
> Thanks,
> Abhishek
>
> [1]. https://github.com/abhishek0198/test-framework
>
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fix for https://wso2.org/jira/browse/IDENTITY-4646
Thanks Isura On Fri, Jun 17, 2016 at 11:10 AM, Isura Karunaratne <is...@wso2.com> wrote: > merged. > > On Thu, Jun 16, 2016 at 6:28 PM, Darshana Gunawardana <darsh...@wso2.com> > wrote: > >> Isura, can you please follow up on this. Thanks. >> >> >> On Thursday, 16 June 2016, Vishanth Balasubramaniam <vishan...@wso2.com> >> wrote: >> >>> Hi, >>> >>> Please review and merge the following PRs. >>> >>>- https://github.com/wso2/carbon-identity-framework/pull/321 >>>- https://github.com/wso2/carbon-identity-framework/pull/322 >>> >>> This is the fix for https://wso2.org/jira/browse/IDENTITY-4646 >>> >>> To improve performance on user self registration in >>> UserInformationRecoveryService of identity management. >>> >>> Regards, >>> Vishanth >>> >>> -- >>> *Vishanth Balasubramaniam* >>> Committer & PMC Member, Apache Stratos, >>> Software Engineer, WSO2 Inc.; http://wso2.com >>> >>> mobile: *+94 77 17 377 18* >>> about me: *http://about.me/vishanth <http://about.me/vishanth>* >>> >> >> >> -- >> Regards, >> >> >> *Darshana Gunawardana*Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> >> *E-mail: darsh...@wso2.com <darsh...@wso2.com>* >> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware >> >> > > > -- > Isura Dilhara Karunaratne > Senior Software Engineer > > Mob +94 772 254 810 > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue when starting the server - SSLException: Connection has been shutdown
Hi Dilini,
Try commenting out the rest of the properties in H2DatabaseConfiguration in
carbon.xml.
>
> 8082
>
>
> **
>
Regards,
Vishanth
On Tue, Feb 2, 2016 at 5:37 PM, Dilini Gunatilake <dili...@wso2.com> wrote:
> Hi Carbon Team,
>
> I wanted to browse the H2 repository and followed the blog in [1] and
> configured the carbon.xml file accordingly. But, when I started the pack, I
> observed the following error. What could be the reason for this?
>
> This issue was observed in WSO2 ESB 4.10.0-Milestone 2 and DS 2.0.0 Beta 2
> packs. (carbon 4.4.3)
>
> ubuntu@ds-long-n1:~/releases/wso2ds-2.0.0-SNAPSHOT/bin$ sh wso2server.sh
> JAVA_HOME environment variable is set to /home/ubuntu/software/jdk1.8.0_51
> CARBON_HOME environment variable is set to
> /home/ubuntu/releases/wso2ds-2.0.0-SNAPSHOT
> Using Java memory options: -Xms256m -Xmx1024m
>
> [2016-02-02 11:26:27,394] INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} - Starting H2 Web
> server...
> [2016-02-02 11:26:28,006] INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} - Starting H2 TCP
> server...
> [2016-02-02 11:26:28,030] INFO
> {org.wso2.carbon.h2.osgi.console.ConsoleService} - Starting H2 PG server...
> org.h2.server.TcpServerThread@273ec7dc Connect
> Connect
> Disconnect
> Close
> javax.net.ssl.SSLException: Connection has been shutdown:
> javax.net.ssl.SSLHandshakeException: Remote host closed connection during
> handshake
> at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
> at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
> at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at java.io.DataOutputStream.flush(DataOutputStream.java:123)
> at org.h2.value.Transfer.flush(Transfer.java:85)
> at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
> connection during handshake
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:928)
> at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
> at java.io.DataInputStream.readInt(DataInputStream.java:387)
> at org.h2.value.Transfer.readInt(Transfer.java:145)
> at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
> ... 1 more
> Caused by: java.io.EOFException: SSL peer shut down incorrectly
> at sun.security.ssl.InputRecord.read(InputRecord.java:505)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
> ... 9 more
> org.h2.server.TcpServerThread@273ec7dc Disconnect
> org.h2.server.TcpServerThread@273ec7dc Close
> [2016-02-02 11:26:29,170] INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} - Starting WSO2
> Carbon...
> [2016-02-02 11:26:29,177] INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} - Operating System :
> Linux 3.13.0-36-generic, amd64
> [2016-02-02 11:26:29,177] INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Home:
> /home/ubuntu/software/jdk1.8.0_51/jre
> [2016-02-02 11:26:29,178] INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Version :
> 1.8.0_51
> [2016-02-02 11:26:29,181] INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java VM :
> Java HotSpot(TM) 64-Bit Server VM 25.51-b03,Oracle Corporation
>
>
> [1]
> http://www.vitharana.org/2012/04/how-to-browse-h2-database-of-wso2.html
>
>
> Thank you.
>
> Regards,
>
> --
>
> *Dilini GunatilakeSoftware Engineer - QA Team*
> Mobile : +94 (0) 771 162518
> dili...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in worker/manager separated cluster in Kubernetes
Hi Pubudu,
Even with the proxy port set in the manager and worker profiles, it is
still having the same problem. Sharing the axis2.xml and
catalina-server.xml [1] [2] of the manager node.
[1] -
https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJVVJiZ0pMaUcwVEE/view?usp=sharing
[2] -
https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJTFFPOEpNTFB5Y00/view?usp=sharing
Regards,
Vishanth
On Tue, Feb 2, 2016 at 10:25 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:
> Hi Vishanth,
>
> Looks like you haven't configured the proxy port in catalina-server.xml.
>
> In k8 we create a service for each port mapping according to [1]. This
> port will be accessible via the nodeport in k8. So you need to set this
> node port value in the catalina-sever.xml using hiera data. If this is not
> set correctly you cannot access the management console.
>
> [1] -
> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13
>
> Thank you!
>
> On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I have been working on WSO2 AS worker/manager separated cluster in
>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>> CoreOs [1].
>> I built the docker images for manager and worker with the following
>> Kubernetes membership scheme configurations in the profile.
>>
>> wso2::clustering :
>>> enabled : true
>>> local_member_host : local.as.wso2.com
>>> local_member_port : 4000
>>> membership_scheme : kubernetes
>>> k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>> subDomain : mgt
>>
>>
>> wso2::clustering :
>>> enabled : true
>>> local_member_host : worker.as.wso2.com
>>> local_member_port : 4000
>>> membership_scheme : kubernetes
>>> k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>> subDomain : worker
>>
>>
>> I SCP-ed the saved zip file of built images and loaded them in the
>> Kubernetes minion. Then I deployed the worker/manager service and
>> controller. I SSH-ed into the container where the manager node is running,
>> and there are no error logs as you can see below.
>>
>> TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>> Using kubernetes based membership management scheme
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> - Initializing kubernetes membership scheme...
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> - Kubernetes clustering configuration: [master]
>>> http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:54,499] INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>>> : https://10.244.78.4:9443/carbon/
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>
>>
>> But it doesn't become the cluster coordinator node and there is no any
>> other log after this. Also I am not able to access the carbon management
>> console from my local machine.
>>
>> But whereas, when I deploy only the default profile (not cluster), then
>> it runs fine and I am able to access the carbon management console from my
>> local machine with the provided nodeport.
>>
>> Have I misconfigured anything in worker/manager cluster setup?
>>
>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>
>> Regards,
>> Vishanth
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774079049 <%2B94772207163>
>
>
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in worker/manager separated cluster in Kubernetes
Hi,
I will test it with the latest changes and see if it fixes the issue.
Regards,
Vishanth
On Wed, Feb 3, 2016 at 2:05 AM, Isuru Haththotuwa <isu...@wso2.com> wrote:
> Hi,
>
> Debugged the code to find the problem. In the K8s membership scheme, we
> were earlier creating a HTTPS connection always, which was attempting to
> create a HTTPS connection even to a non secure endpoint. That was the
> issue. I changed that to create a secure/non-secure connection depending on
> the URL, and that resolved the issue. Committed the fix now.
>
> On Wed, Feb 3, 2016 at 1:20 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi Pubudu,
>>
>> Even with the proxy port set in the manager and worker profiles, it is
>> still having the same problem. Sharing the axis2.xml and
>> catalina-server.xml [1] [2] of the manager node.
>>
>> [1] -
>> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJVVJiZ0pMaUcwVEE/view?usp=sharing
>> [2] -
>> https://drive.google.com/a/wso2.com/file/d/0B1Vp6McRCyeJTFFPOEpNTFB5Y00/view?usp=sharing
>>
>> Regards,
>> Vishanth
>>
>> On Tue, Feb 2, 2016 at 10:25 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>>> Hi Vishanth,
>>>
>>> Looks like you haven't configured the proxy port in catalina-server.xml.
>>>
>>> In k8 we create a service for each port mapping according to [1]. This
>>> port will be accessible via the nodeport in k8. So you need to set this
>>> node port value in the catalina-sever.xml using hiera data. If this is not
>>> set correctly you cannot access the management console.
>>>
>>> [1] -
>>> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2as/kubernetes/wso2as-manager-service.yaml#L13
>>>
>>> Thank you!
>>>
>>> On Tue, Feb 2, 2016 at 9:49 PM, Vishanth Balasubramaniam <
>>> vishan...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have been working on WSO2 AS worker/manager separated cluster in
>>>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>>>> CoreOs [1].
>>>> I built the docker images for manager and worker with the following
>>>> Kubernetes membership scheme configurations in the profile.
>>>>
>>>> wso2::clustering :
>>>>> enabled : true
>>>>> local_member_host : local.as.wso2.com
>>>>> local_member_port : 4000
>>>>> membership_scheme : kubernetes
>>>>> k8 :
>>>>> k8_master : http://172.17.8.101:8080
>>>>> k8_namespace : default
>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>> subDomain : mgt
>>>>
>>>>
>>>> wso2::clustering :
>>>>> enabled : true
>>>>> local_member_host : worker.as.wso2.com
>>>>> local_member_port : 4000
>>>>> membership_scheme : kubernetes
>>>>> k8 :
>>>>> k8_master : http://172.17.8.101:8080
>>>>> k8_namespace : default
>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>> subDomain : worker
>>>>
>>>>
>>>> I SCP-ed the saved zip file of built images and loaded them in the
>>>> Kubernetes minion. Then I deployed the worker/manager service and
>>>> controller. I SSH-ed into the container where the manager node is running,
>>>> and there are no error logs as you can see below.
>>>>
>>>> TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>> Using kubernetes based membership management scheme
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>>>> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>> - Initializing kubernetes membership scheme...
>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>>>> - Kubernetes clustering configuration: [master]
>>>>> http://172.17.8.101:8080 [namespace] default [services]
>>>>> wso2as-manager
>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
Re: [Dev] Issue in worker/manager separated cluster in Kubernetes
Hi Isuru,
With those changes in the Kubernetes Membership Scheme, now the
worker/manager separation is working fine. I have tested this with WSO2 AS.
In the log now I am able to see the manager is being elected as a
coordinator node.
TID: [-1234] [] [2016-02-03 08:16:09,373] INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Local member: [cf010018-3cf6-4a44-8f6a-5b72043017e2] - Host:10.244.86.4,
> Remote Host:null, Port: 4000, HTTP:9763, HTTPS:9443, Domain:
> wso2.carbon.domain, Sub-domain:mgt, Active:true
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-03 08:16:09,457] INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Elected this member [cf010018-3cf6-4a44-8f6a-5b72043017e2] as the
> Coordinator node
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-03 08:16:09,564] INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Cluster initialization completed
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
Regards,
Vishanth
On Wed, Feb 3, 2016 at 7:50 AM, Isuru Haththotuwa <isu...@wso2.com> wrote:
>
>
> On Tue, Feb 2, 2016 at 10:47 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>
>>
>>
>> On Wed, Feb 3, 2016 at 1:13 AM, Isuru Haththotuwa <isu...@wso2.com>
>> wrote:
>>
>>>
>>> AFAIK this is the correct way. If we start the manager first, there is
>>> no worker pod at that moment. So the manager can start on its own. When the
>>> worker pod is being created, it can add both manager and worker services'
>>> IPs and connect to the manager node.
>>>
>>
>> No Isuru, this is the list of services [1] given to each Carbon server
>> instance to query Pods. So ideally it should have both worker service and
>> manager service.
>>
> Thanks Imesh. I was of the idea that we should add individual pod IPs.
>
>>
>> [1]
>> https://github.com/wso2/kubernetes-artifacts/blob/master/common/kubernetes-membership-scheme/src/main/java/org/wso2/carbon/membership/scheme/kubernetes/KubernetesMembershipScheme.java#L141
>>
>>>
>>>> Thanks
>>>>
>>>> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
>>>> vishan...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have been working on WSO2 AS worker/manager separated cluster in
>>>>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>>>>> CoreOs [1].
>>>>> I built the docker images for manager and worker with the following
>>>>> Kubernetes membership scheme configurations in the profile.
>>>>>
>>>>> wso2::clustering :
>>>>>> enabled : true
>>>>>> local_member_host : local.as.wso2.com
>>>>>> local_member_port : 4000
>>>>>> membership_scheme : kubernetes
>>>>>> k8 :
>>>>>> k8_master : http://172.17.8.101:8080
>>>>>> k8_namespace : default
>>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>>> subDomain : mgt
>>>>>
>>>>>
>>>>> wso2::clustering :
>>>>>> enabled : true
>>>>>> local_member_host : worker.as.wso2.com
>>>>>> local_member_port : 4000
>>>>>> membership_scheme : kubernetes
>>>>>> k8 :
>>>>>> k8_master : http://172.17.8.101:8080
>>>>>> k8_namespace : default
>>>>>> k8_services : wso2as-manager,wso2as-worker
>>>>>> subDomain : worker
>>>>>
>>>>>
>>>>> I SCP-ed the saved zip file of built images and loaded them in the
>>>>> Kubernetes minion. Then I deployed the worker/manager service and
>>>>> controller. I SSH-ed into the container where the manager node is running,
>>>>> and there are no error logs as you can see below.
>>>>>
>>>>> TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
>>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>> Using kubernetes based membership management scheme
>>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>>>>> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
>>>>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipSchem
Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.0.0 RC2
[x] Stable - go ahead and release Verified the following products with clustering - WSO2 ES - WSO2 BRS Verified the ReadMe and License. Regards, Vishanth On Wed, Feb 3, 2016 at 9:59 AM, Thanuja Uruththirakodeeswaran < thanu...@wso2.com> wrote: > +1 for the release > > Verified following products with clustering: > > 1. DSS 3.5.0 > 2. ESB 4.9.0 > 3. AS 5.3.0 > > Also tested DAS 3.0.0 default profile. > > Thanks. > > On Wed, Feb 3, 2016 at 9:32 AM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> +1 release >> >> Verified the Puppet manifests for BRS, MB, and GREG (default profile) >> >> Additional changes to templates and hieradata have to be added to cater >> for the majority of the possible use cases, however this release can be >> done without those changes. More sophisticated and configurable templates >> can be added later to each product. >> >> >> Regards, >> Chamila de Alwis >> Committer and PMC Member - Apache Stratos >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> >> On Mon, Feb 1, 2016 at 12:47 PM, Isuru Haththotuwa <isu...@wso2.com> >> wrote: >> >>> Hi, >>> >>> AFAIU we can't just use this templates anyway as they are, but might >>> need to modify to fit to the usecase. These modules do not cover all the >>> parameters that each of the products have, just have the most basic set. >>> More importantly this set of puppet modules have standardized the >>> separation of data from puppet code by using hiera to use as a common set >>> of puppet modules for all WSO2 use cases. We can improve them as we >>> move along. >>> >>> On Mon, Feb 1, 2016 at 11:46 AM, Ramith Jayasinghe <ram...@wso2.com> >>> wrote: >>> >>>> had a chat with IsuruH and agreed to add the ability to configure this >>>> on next release. >>>> >>>> On Mon, Feb 1, 2016 at 11:25 AM, Ramith Jayasinghe <ram...@wso2.com> >>>> wrote: >>>> > HI, >>>> > in : >>>> https://github.com/wso2/puppet-modules/blob/v1.0.0-rc2/modules/wso2mb/templates/3.0.0/repository/conf/datasources/master-datasources.xml.erb >>>> > I see that, >>>> > false is not added to MB >>>> > data-source (only MB data-source requires that). that would lead to >>>> > problems. shall we fix that. >>>> > regards >>>> > Ramith >>>> > >>>> > On Mon, Feb 1, 2016 at 11:14 AM, Isuru Haththotuwa <isu...@wso2.com> >>>> wrote: >>>> >> Hi devs, >>>> >> >>>> >> This is the second release candidate of WSO2 Puppet Modules 1.0.0. >>>> Please >>>> >> download, test and vote. >>>> >> >>>> >> [ ] Broken - do not release (explain why) >>>> >> [ ] Stable - go ahead and release >>>> >> >>>> >> The tag to be voted upon: >>>> >> https://github.com/wso2/puppet-modules/tree/v1.0.0-rc2 >>>> >> >>>> >> Source and binary distribution files: >>>> >> https://github.com/wso2/puppet-modules/releases/tag/v1.0.0-rc2 >>>> >> >>>> >> The vote will be open for 72 hours or as needed. >>>> >> >>>> >> -- >>>> >> Thanks, >>>> >> The WSO2 Private PaaS Team >>>> >> >>>> >> >>>> >> >>>> >> ___ >>>> >> Dev mailing list >>>> >> Dev@wso2.org >>>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >> >>>> > >>>> > >>>> > >>>> > -- >>>> > Ramith Jayasinghe >>>> > Technical Lead >>>> > WSO2 Inc., http://wso2.com >>>> > lean.enterprise.middleware >>>> > >>>> > E: ram...@wso2.com >>>> > P: +94 777542851 >>>> >>>> >>>> >>>> -- >>>> Ramith Jayasinghe >>>> Technical Lead >>>> WSO2 Inc., http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> E: ram...@wso2.com >>>> P: +94 777542851 >>>> >>> >>> >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanuja Uruththirakodeeswaran > Software Engineer > WSO2 Inc.;http://wso2.com > lean.enterprise.middleware > > mobile: +94 774363167 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue in worker/manager separated cluster in Kubernetes
Hi,
I have been working on WSO2 AS worker/manager separated cluster in
Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
CoreOs [1].
I built the docker images for manager and worker with the following
Kubernetes membership scheme configurations in the profile.
wso2::clustering :
> enabled : true
> local_member_host : local.as.wso2.com
> local_member_port : 4000
> membership_scheme : kubernetes
> k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
> subDomain : mgt
wso2::clustering :
> enabled : true
> local_member_host : worker.as.wso2.com
> local_member_port : 4000
> membership_scheme : kubernetes
> k8 :
> k8_master : http://172.17.8.101:8080
> k8_namespace : default
> k8_services : wso2as-manager,wso2as-worker
> subDomain : worker
I SCP-ed the saved zip file of built images and loaded them in the
Kubernetes minion. Then I deployed the worker/manager service and
controller. I SSH-ed into the container where the manager node is running,
and there are no error logs as you can see below.
TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
> Using kubernetes based membership management scheme
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> - Initializing kubernetes membership scheme...
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> - Kubernetes clustering configuration: [master] http://172.17.8.101:8080
> [namespace] default [services] wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
> TID: [-1234] [] [2016-02-02 12:43:54,499] INFO
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
> : https://10.244.78.4:9443/carbon/
> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
But it doesn't become the cluster coordinator node and there is no any
other log after this. Also I am not able to access the carbon management
console from my local machine.
But whereas, when I deploy only the default profile (not cluster), then it
runs fine and I am able to access the carbon management console from my
local machine with the provided nodeport.
Have I misconfigured anything in worker/manager cluster setup?
[1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
Regards,
Vishanth
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in worker/manager separated cluster in Kubernetes
On Tue, Feb 2, 2016 at 10:28 PM, Imesh Gunaratne <im...@wso2.com> wrote:
> I noted one other thing in the log:
>
> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme} -
> Kubernetes clustering configuration: [master] http://172.17.8.101:8080
> [namespace] default [services] wso2as-manager
> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>
> K8S services only has manager service. See the highlighted text. We need
> to add both manager and worker here to let them connect to the same carbon
> cluster.
>
I tried with both [services] wso2as-manager,wso2as-worker as well as
[services] wso2as-manager
>
> Thanks
>
> On Wed, Feb 3, 2016 at 12:19 AM, Vishanth Balasubramaniam <
> vishan...@wso2.com> wrote:
>
>> Hi,
>>
>> I have been working on WSO2 AS worker/manager separated cluster in
>> Kubernetes. I have setup the Kubernetes cluster using the Vagrant and
>> CoreOs [1].
>> I built the docker images for manager and worker with the following
>> Kubernetes membership scheme configurations in the profile.
>>
>> wso2::clustering :
>>> enabled : true
>>> local_member_host : local.as.wso2.com
>>> local_member_port : 4000
>>> membership_scheme : kubernetes
>>> k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>> subDomain : mgt
>>
>>
>> wso2::clustering :
>>> enabled : true
>>> local_member_host : worker.as.wso2.com
>>> local_member_port : 4000
>>> membership_scheme : kubernetes
>>> k8 :
>>> k8_master : http://172.17.8.101:8080
>>> k8_namespace : default
>>> k8_services : wso2as-manager,wso2as-worker
>>> subDomain : worker
>>
>>
>> I SCP-ed the saved zip file of built images and loaded them in the
>> Kubernetes minion. Then I deployed the worker/manager service and
>> controller. I SSH-ed into the container where the manager node is running,
>> and there are no error logs as you can see below.
>>
>> TID: [-1234] [] [2016-02-02 12:43:53,892] INFO
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>> Using kubernetes based membership management scheme
>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
>>> TID: [-1234] [] [2016-02-02 12:43:53,905] INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> - Initializing kubernetes membership scheme...
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:53,909] INFO
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> - Kubernetes clustering configuration: [master]
>>> http://172.17.8.101:8080 [namespace] default [services] wso2as-manager
>>> {org.wso2.carbon.membership.scheme.kubernetes.KubernetesMembershipScheme}
>>> TID: [-1234] [] [2016-02-02 12:43:54,499] INFO
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL
>>> : https://10.244.78.4:9443/carbon/
>>> {org.wso2.carbon.ui.internal.CarbonUIServiceComponent}
>>
>>
>> But it doesn't become the cluster coordinator node and there is no any
>> other log after this. Also I am not able to access the carbon management
>> console from my local machine.
>>
>> But whereas, when I deploy only the default profile (not cluster), then
>> it runs fine and I am able to access the carbon management console from my
>> local machine with the provided nodeport.
>>
>> Have I misconfigured anything in worker/manager cluster setup?
>>
>> [1] - https://github.com/pires/kubernetes-vagrant-coreos-cluster
>>
>> Regards,
>> Vishanth
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>
>
>
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> Lean . Enterprise . Middleware
>
>
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Kubernetes Volume for sharing artifacts in manager and worker nodes
Hi, I am currently researching on using Kubernetes PaaS feature volume to share APIs among gateway manager and worker nodes. In Kubernetes Artifacts, we are separating the worker and the manager nodes in 2 different pods, for which each uses separate replication controller. Due to nodes being in separate pods, we cannot use the simple Kubernetes volume mount [1] (like emptyDirs, gitRepo etc...), rather there are other approaches to share spaces between pods like NFS or GlusterFS as persistent volume [2]. Doing a POC now to check how the NFS persistent volume can be used to share the APIs among gateway manager and worker nodes. Will keep this thread updated on the findings. [1] - http://kubernetes.io/v1.1/docs/user-guide/volumes.html [2] - http://kubernetes.io/v1.1/docs/user-guide/persistent-volumes.html Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Packaging the Kubernetes Artifacts
Hi, This is to discuss the packaging structure of Kubernetes Artifacts. The project structure is attached [1]. The plan is to package the Docker related distributions and Kubernetes related distributions separately per product. Docker related distribution of a product would look like this. -Docker-1.0.0.zip |--- /docker |--- Common |--- docker/base-image |--- scripts/docker |--- ReadMe.md Should we package the docker base-image within every docker distribution of a product or should it be packaged separately. Thoughts? Kubernetes related distribution of a product would look like this. -Kubernetes-1.0.0.zip |--- /kubernetes |--- Common |--- scripts/kubernetes |--- ReadMe.md [1] - Attachment: Kubernetes-Artifacts-Project-Structure.png Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Packaging the Kubernetes Artifacts
Thanks Imesh. On Tue, Mar 1, 2016 at 7:27 AM, Imesh Gunaratne <im...@wso2.com> wrote: > > On Tue, Mar 1, 2016 at 7:16 AM, Imesh Gunaratne <im...@wso2.com> wrote: > >> >> WSO2 has repeated in the artifact names, see above >> Might be better to rename wso2am-docker-1.0.0.zip >> to wso2am-dockerfile-1.0.0.zip >> >> I have now fixed above: > > > https://github.com/wso2/kubernetes-artifacts/commit/764c50282ab3f538f7bfa39e56eb25287a55d221 > > https://github.com/wso2/kubernetes-artifacts/commit/a3114e6b79c67bf23257ad2c61cf33375a4116ff > > Thanks > > >> Thanks >> >> On Mon, Feb 29, 2016 at 1:15 PM, Chamila De Alwis <chami...@wso2.com> >> wrote: >> >>> Hi Vishanth, >>> >>> The plan is to have the base image in Docker Public registry so that >>> anyone can pull it whenever they want. However, IMO we should also ship the >>> common image artifacts, in case the users need to modify the Base image. >>> >>> We can additionally link the common Dockerfile with the Docker registry >>> [1]. >>> >>> [1] - https://docs.docker.com/docker-hub/github/ >>> >>> >>> Regards, >>> Chamila de Alwis >>> Committer and PMC Member - Apache Stratos >>> Software Engineer | WSO2 | +94772207163 >>> Blog: code.chamiladealwis.com >>> >>> >>> >>> On Mon, Feb 29, 2016 at 12:41 PM, Vishanth Balasubramaniam < >>> vishan...@wso2.com> wrote: >>> >>>> Hi, >>>> >>>> This is to discuss the packaging structure of Kubernetes Artifacts. The >>>> project structure is attached [1]. The plan is to package the Docker >>>> related distributions and Kubernetes related distributions separately per >>>> product. >>>> >>>> Docker related distribution of a product would look like this. >>>> -Docker-1.0.0.zip >>>> |--- /docker >>>> |--- Common >>>> |--- docker/base-image >>>> |--- scripts/docker >>>> |--- ReadMe.md >>>> >>>> Should we package the docker base-image within every docker >>>> distribution of a product or should it be packaged separately. Thoughts? >>>> >>>> Kubernetes related distribution of a product would look like this. >>>> -Kubernetes-1.0.0.zip >>>> |--- /kubernetes >>>> |--- Common >>>> |--- scripts/kubernetes >>>> |--- ReadMe.md >>>> >>>> [1] - Attachment: Kubernetes-Artifacts-Project-Structure.png >>>> >>>> Regards, >>>> Vishanth >>>> >>>> -- >>>> *Vishanth Balasubramaniam* >>>> Committer & PMC Member, Apache Stratos, >>>> Software Engineer, WSO2 Inc.; http://wso2.com >>>> >>>> mobile: *+94 77 17 377 18* >>>> about me: *http://about.me/vishanth <http://about.me/vishanth>* >>>> >>> >>> >> >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.io >> Lean . Enterprise . Middleware >> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Packaging the Kubernetes Artifacts
Thanks Isuru. Noted, will do it that way. On Tue, Mar 1, 2016 at 1:45 PM, Isuru Haththotuwa <isu...@wso2.com> wrote: > Hi Vishanth, > > Few comments: > >- Move the property kubernetes.artifacts.version to root pom >- No need to define profiles, common plugins (assembly) and >repositories in each pom, they can be declared in the root pom and >inherited. > > > On Tue, Mar 1, 2016 at 9:29 AM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Thanks Imesh. >> >> On Tue, Mar 1, 2016 at 7:27 AM, Imesh Gunaratne <im...@wso2.com> wrote: >> >>> >>> On Tue, Mar 1, 2016 at 7:16 AM, Imesh Gunaratne <im...@wso2.com> wrote: >>> >>>> >>>> WSO2 has repeated in the artifact names, see above >>>> Might be better to rename wso2am-docker-1.0.0.zip >>>> to wso2am-dockerfile-1.0.0.zip >>>> >>>> I have now fixed above: >>> >>> >>> https://github.com/wso2/kubernetes-artifacts/commit/764c50282ab3f538f7bfa39e56eb25287a55d221 >>> >>> https://github.com/wso2/kubernetes-artifacts/commit/a3114e6b79c67bf23257ad2c61cf33375a4116ff >>> >>> Thanks >>> >>> >>>> Thanks >>>> >>>> On Mon, Feb 29, 2016 at 1:15 PM, Chamila De Alwis <chami...@wso2.com> >>>> wrote: >>>> >>>>> Hi Vishanth, >>>>> >>>>> The plan is to have the base image in Docker Public registry so that >>>>> anyone can pull it whenever they want. However, IMO we should also ship >>>>> the >>>>> common image artifacts, in case the users need to modify the Base image. >>>>> >>>>> We can additionally link the common Dockerfile with the Docker >>>>> registry [1]. >>>>> >>>>> [1] - https://docs.docker.com/docker-hub/github/ >>>>> >>>>> >>>>> Regards, >>>>> Chamila de Alwis >>>>> Committer and PMC Member - Apache Stratos >>>>> Software Engineer | WSO2 | +94772207163 >>>>> Blog: code.chamiladealwis.com >>>>> >>>>> >>>>> >>>>> On Mon, Feb 29, 2016 at 12:41 PM, Vishanth Balasubramaniam < >>>>> vishan...@wso2.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> This is to discuss the packaging structure of Kubernetes Artifacts. >>>>>> The project structure is attached [1]. The plan is to package the Docker >>>>>> related distributions and Kubernetes related distributions separately per >>>>>> product. >>>>>> >>>>>> Docker related distribution of a product would look like this. >>>>>> -Docker-1.0.0.zip >>>>>> |--- /docker >>>>>> |--- Common >>>>>> |--- docker/base-image >>>>>> |--- scripts/docker >>>>>> |--- ReadMe.md >>>>>> >>>>>> Should we package the docker base-image within every docker >>>>>> distribution of a product or should it be packaged separately. Thoughts? >>>>>> >>>>>> Kubernetes related distribution of a product would look like this. >>>>>> -Kubernetes-1.0.0.zip >>>>>> |--- /kubernetes >>>>>> |--- Common >>>>>> |--- scripts/kubernetes >>>>>> |--- ReadMe.md >>>>>> >>>>>> [1] - Attachment: Kubernetes-Artifacts-Project-Structure.png >>>>>> >>>>>> Regards, >>>>>> Vishanth >>>>>> >>>>>> -- >>>>>> *Vishanth Balasubramaniam* >>>>>> Committer & PMC Member, Apache Stratos, >>>>>> Software Engineer, WSO2 Inc.; http://wso2.com >>>>>> >>>>>> mobile: *+94 77 17 377 18* >>>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>* >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Imesh Gunaratne* >>>> Senior Technical Lead >>>> WSO2 Inc: http://wso2.com >>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>> W: http://imesh.io >>>> Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.io >>> Lean . Enterprise . Middleware >>> >>> >> >> >> -- >> *Vishanth Balasubramaniam* >> Committer & PMC Member, Apache Stratos, >> Software Engineer, WSO2 Inc.; http://wso2.com >> >> mobile: *+94 77 17 377 18* >> about me: *http://about.me/vishanth <http://about.me/vishanth>* >> > > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Moved WSO2 Dockerfiles to a separate git repository
Hi, Dockerfiles for the WSO2 Products is now moved out from the Kubernetes-Artifacts repo [1]. You can find the dockerfiles now at [2]. [1] - https://github.com/wso2/kubernetes-artifacts [1] - https://github.com/wso2/dockerfiles Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Dockerfiles build logs
Hi, Currently when building the wso2 docker images [1], we are not prompting the complete image building logs [2], we are only prompting if there is any error while building. Is there any specific reason for not prompting the complete log trace when building these images? Isn't it better to show the complete build logs or at least an option for user to see the complete logs? Thoughts? [1] - https://github.com/wso2/dockerfiles [2] - https://github.com/wso2/dockerfiles/blob/master/common/scripts/docker-build.sh#L196-L208 Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Restructuring Kubernetes-Artifacts and Docker-Artifacts
Hi, Now that we are planning to move the docker artifacts to a separate git repository from wso2/kubernetes-artifacts. I would like to propose the following directory structure for the Kubernetes-Artifacts [1] and Docker-Artifacts repositories. wso2/kubernetes-artifacts |--- common |--- |--- kubernetes-membership-scheme/ |--- |--- scripts/ |--- / |--- |--- README.md |--- |--- deploy.sh |--- |--- undeploy.sh |--- |--- rolling-update.sh |--- |--- deployments/ |--- |--- |--- default/ |--- |--- |--- |--- -default-controller.yaml |--- |--- |--- |--- -default-service.yaml |--- |--- |--- distributed/ |--- |--- |--- |--- -manager-controller.yaml |--- |--- |--- |--- -manager-service.yaml |--- |--- |--- |--- -worker-controller.yaml |--- |--- |--- |--- -worker-service.yaml wso2/docker-artifacts |--- common |--- |--- base-image/ |--- |--- scripts/ |--- / |--- |--- README.md |--- |--- Docker file |--- |--- build.sh |--- |--- run.sh |--- |--- save.sh |--- |--- scp.sh WDYT? Provide your thoughts. [1] - https://github.com/wso2/kubernetes-artifacts Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.1.0 RC2
Hi, [X] Stable - Go ahead and release - Tested the default profiles of all and clustering scenarios of some. - wso2as - wso2am - wso2brs - wso2bps - wso2greg - wso2mb - Verified Heiradata from some profiles - Verified the Readme and License Regards, Vishanth On Wed, Mar 9, 2016 at 12:07 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi, > > Please note that the voting period is 72 hours. > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Wed, Mar 9, 2016 at 10:33 AM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> Hi, >> >> This is RC2 for WSO2 Puppet Modules 1.1.0. Please download, verify, and >> vote. >> >> [ ] Broken - Do not release (explain why) >> [ ] Stable - Go ahead and release >> >> *This release is based on the following tag:* >> https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc2 >> >> *Release verification guide can be found at:* >> https://github.com/wso2/puppet-modules/wiki/Verifying-Puppet-Modules >> >> *Source and distribution packages can be downloaded at:* >> https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc2 >> >> Regards, >> Chamila de Alwis >> Committer and PMC Member - Apache Stratos >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera
come bad experience for the end user in end of the day. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>>>>> Why can't we do this by using defined types in Hiera and lookup >>>>>>>>>>>> parameters for a given instance? Based on the identify keys we >>>>>>>>>>>> set for each vm, docker, K8S etc we can select the appropriate data >>>>>>>>>>>> set from Hiera file. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Will you be able to provide a sample? >>>>>>>>>>> >>>>>>>>>> >>>>>>> >>>>>>> I think we can make this with with Defined Types[1][2] without >>>>>>> creating duplicate set of YAML files for each platform. We can do the >>>>>>> same >>>>>>> as the example given in the document. >>>>>>> >>>>>> I do not think we need to duplicate the yaml files here. Sorry that >>>>>> the sample in the first reply sent by me implied so. What we can do is >>>>>> refactor out the hiera data so that data which is changing according to >>>>>> the >>>>>> platform (ex.: clustering section) can be moved to a different yaml >>>>>> file(s). For an example, clustering for kubernetes scenario can be >>>>>> included >>>>>> in *puppet-modules/hieradata/dev/wso2/kubernetes/clustering.yaml*. >>>>>> Here, 'kubernetes' is the value of the facter which is used to identify >>>>>> the >>>>>> environment. Similarly, other such data can be refactored out. >>>>>> >>>>> >>> If we follow this approach, then we can't specify product and profile >>> specific data (ex: kubernetes service name varies per product and >>> proxy_ports varies per poduct/profile) in the common platform hiera file: >>> *puppet-modules/hieradata/dev/wso2/kubernetes/clustering.yaml.* >>> >>> >>>>>>> [1] >>>>>>> https://docs.puppet.com/puppet/latest/reference/lang_defined_types.html >>>>>>> [2]http://puppetlunch.com/puppet/hiera.html >>>>>>> >>>>>>> >>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Gayan >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Apr 9, 2016 at 8:28 AM, Imesh Gunaratne <im...@wso2.com >>>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa < >>>>>>>>>>>>> isu...@wso2.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> hieradata >>>>>>>>>>>>>> |--- dev >>>>>>>>>>>>>>|--- wso2 >>>>>>>>>>>>>>| >>>>>>>>>>>>>> |--- >>>>>>>>>>>>>>|-- >>>>>>>>>>>>>> *vm* >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- default.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- manager.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- worker.yaml >>>>>>>>>>>>>>|--* >>>>>>>>>>>>>> docker* >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- default.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- manager.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- worker.yaml >>>>>>>>>>>>>>|-- >>>>>>>>>>>>>> *kubernetes* >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- default.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- manager.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> |-- worker.yaml >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> +1 for the suggestion Isuru, will proceed with this. We can >>>>>>>>>>>>> add other platforms such as OpenShift, Mesos, Cloud Foundry on >>>>>>>>>>>>> the same >>>>>>>>>>>>> level. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>>>> W: http://imesh.io >>>>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Thanks and Regards, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Isuru H. >>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>> W: http://imesh.io >>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ___ >>>>>>>>>>>>> Dev mailing list >>>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> Gayan Gunarathne >>>>>>>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>>>>>>> Committer & PMC Member, Apache Stratos >>>>>>>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>>>>>>> <%2B94%20766819985> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ___ >>>>>>>>>>>> Dev mailing list >>>>>>>>>>>> Dev@wso2.org >>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>> Senior Technical Lead >>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>> W: http://imesh.io >>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Imesh Gunaratne* >>>>>>>>> Senior Technical Lead >>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>> W: http://imesh.io >>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>> >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Lakmal Warusawithana >>>>>>>> Director - Cloud Architecture; WSO2 Inc. >>>>>>>> Mobile : +94714289692 >>>>>>>> Blog : http://lakmalsview.blogspot.com/ >>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Gayan Gunarathne >>>>>>> Technical Lead, WSO2 Inc. (http://wso2.com) >>>>>>> Committer & PMC Member, Apache Stratos >>>>>>> email : gay...@wso2.com | mobile : +94 775030545 >>>>>>> <%2B94%20766819985> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks and Regards, >>>>>> >>>>>> Isuru H. >>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Pubudu Gunatilaka* >>>>> Committer and PMC Member - Apache Stratos >>>>> Software Engineer >>>>> WSO2, Inc.: http://wso2.com >>>>> mobile : +94774078049 <%2B94772207163> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Thanuja Uruththirakodeeswaran >>> Software Engineer >>> WSO2 Inc.;http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 774363167 >>> >> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera
On Fri, Apr 8, 2016 at 7:48 PM, Isuru Haththotuwa <isu...@wso2.com> wrote: > > > On Fri, Apr 8, 2016 at 5:12 PM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Devs, >> >> IMO we need to handle $subject without affecting other deployments. At >> the moment we have updated default.yaml with K8S specific configurations >> and manager and worker yaml files also have clustering configurations >> enabled for K8S. >> > +1. As per the offline discussion, one possible method of doing this is to > have a separation under the product level of hieradata to indicate whether > the configuration is relevant to vm, docker, kubernetes, mesos, etc based > scenarios. So the hieradata structure should change as below: > > hieradata > |--- dev >|--- wso2 >| > |--- >|-- *vm* > |-- > default.yaml > |-- > manager.yaml > |-- worker.yaml >|--* docker* > |-- > default.yaml > |-- > manager.yaml > |-- worker.yaml >|-- *kubernetes* > > |-- > default.yaml > |-- > manager.yaml > |-- worker.yaml > > wdyt? > +1 It is better to provide configurations separately for different deployments and the structure looks good > > > Thanks >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.io >> Lean . Enterprise . Middleware >> >> > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Native Cloud Support for Running WSO2 Middleware on Apache Mesos
following: >>>>>>> >>>>>>> https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal29:[Cloud]NativeCloudSupportforRunningWSO2MiddlewareonMicrosoftAzure >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On Sat, Mar 5, 2016 at 3:25 PM, Osura Rathnayake <osura...@gmail.com >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi sir, >>>>>>>> >>>>>>>> I followed the steps in [1]. >>>>>>>> >>>>>>>> [1] http://mesos.apache.org/gettingstarted/ >>>>>>>> >>>>>>>> thanks and regards >>>>>>>> >>>>>>>> On Sat, Mar 5, 2016 at 3:17 PM, Imesh Gunaratne <im...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Can you please explain how you installed Mesos on a Ubuntu >>>>>>>>> machine? >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> >>>>>>>>> On Saturday, March 5, 2016, Osura Rathnayake <osura...@gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Sir, >>>>>>>>>> >>>>>>>>>> We were able to install mesos, docker and WSO2 carbon on a Ubuntu >>>>>>>>>> machine. Furthermore we installed wso2 ESB and AS through docker. >>>>>>>>>> Currently >>>>>>>>>> we are working on understanding how K8S works in this scenario. >>>>>>>>>> After that >>>>>>>>>> what would be the next step? >>>>>>>>>> >>>>>>>>>> thanks and regards, >>>>>>>>>> Osura Rathnayake, Sahan Wickramaarachchi, Vishwa Jayaratne, Allan >>>>>>>>>> Barthelot >>>>>>>>>> >>>>>>>>>> On Mon, Feb 29, 2016 at 12:38 PM, Imesh Gunaratne <im...@wso2.com >>>>>>>>>> > wrote: >>>>>>>>>> >>>>>>>>>>> Hi Osura, >>>>>>>>>>> >>>>>>>>>>> It's nice to hear your interest on this project. The starting >>>>>>>>>>> point would be to install Mesos and see how it works. Then try to >>>>>>>>>>> deploy a >>>>>>>>>>> WSO2 product on Mesos using Docker. Then understand how Carbon >>>>>>>>>>> clustering >>>>>>>>>>> works including K8S membership scheme [1] we have implemented for >>>>>>>>>>> the same >>>>>>>>>>> purpose on K8S. Later on move to other native PaaS features needed. >>>>>>>>>>> >>>>>>>>>>> [1] >>>>>>>>>>> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> >>>>>>>>>>> On Mon, Feb 29, 2016 at 12:29 PM, Osura Rathnayake < >>>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Dear Sir, >>>>>>>>>>>> >>>>>>>>>>>> We are a group of 4th year students following the Computer >>>>>>>>>>>> Systems and Networking degree program at SLIIT. We are interested >>>>>>>>>>>> in >>>>>>>>>>>> undertaking above mentioned project as our 4th year research >>>>>>>>>>>> project. >>>>>>>>>>>> >>>>>>>>>>>> As 4th year CSN students we have a fairly good understanding in >>>>>>>>>>>> PaaS concepts and Java language. We have a basic understanding of >>>>>>>>>>>> basic >>>>>>>>>>>> features of WSO2 Carbon. >>>>>>>>>>>> >>>>>>>>>>>> We were asked to contact you by Senior Lecturer Mr. Lakmal >>>>>>>>>>>> Rupasinghe. >>>>>>>>>>>> Please get back to us soon. >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Osura Rathnayake, Sahan Wickramaarachchi, Vishwa Jayaratne, >>>>>>>>>>>> Allan Barthelot >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>> Senior Technical Lead >>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>> W: http://imesh.io >>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Imesh Gunaratne* >>>>>>>>> Senior Technical Lead >>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>> W: http://imesh.io >>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Imesh Gunaratne* >>>>>>> Senior Technical Lead >>>>>>> WSO2 Inc: http://wso2.com >>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>> W: http://imesh.io >>>>>>> Lean . Enterprise . Middleware >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Imesh Gunaratne* >>>>> Senior Technical Lead >>>>> WSO2 Inc: http://wso2.com >>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>> W: http://imesh.io >>>>> Lean . Enterprise . Middleware >>>>> >>>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.io >>> Lean . Enterprise . Middleware >>> >>> >> > > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Setting up a local Kubernetes v1.2.0 cluster in around 2 minutes
Hi, This is great. It just took under 3 minutes to setup a Kubernetes cluster with 1 node from the 2nd time onwards. Regards, Vishanth On Fri, Mar 25, 2016 at 11:03 AM, Imesh Gunaratne <im...@wso2.com> wrote: > Hi Devs, > > I just updated the Kubernetes Vagrant Setup [1] to do $subject. This was > originally written by Pires [2], I have improved it to take the Kubernetes > binary and the required Docker images from the disk to reduce the startup > time and the internet usage. > > Docker image files are not added to the git repository due to their large > size. Those would get downloaded in the first run. Give it a try and let me > know your thoughts. > > [1] https://github.com/imesh/kubernetes-vagrant-setup/tree/v1.2.0 > [2] https://github.com/pires/kubernetes-vagrant-coreos-cluster > > Thanks > > -- > *Imesh Gunaratne* > Senior Technical Lead > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: http://imesh.io > Lean . Enterprise . Middleware > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Puppet Modules 1.1.0 RC1
[X] Stable - Go ahead and release - Tested the default profiles of the following products. - wso2brs - wso2bps - wso2greg - wso2mb - Verified Heiradata from some profiles - Verified the Readme and License Regards, Vishanth On Fri, Mar 4, 2016 at 11:08 AM, Chamila De Alwis <chami...@wso2.com> wrote: > Hi, > > This is the first release candidate of WSO2 Puppet Modules 1.1.0. Please > download, verify, and vote. > > [ ] Broken - Do not release (explain why) > [ ] Stable - Go ahead and release > > *This release is based on the following tag:* > https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc1 > <https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc1> > <https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc1> > > *Release verification guide can be found at:* > https://github.com/wso2/puppet-modules/wiki/Verifying-Puppet-Modules > > *This release contains the following new features:* > >1. Puppet configurations to enable SecureVault >2. Puppet templates and Hieradata for WSO2 API Manager 1.10.0 >3. Additional Hieradata for WSO2 API Manager 1.9.1 Key Manager, Store, >Publisher, and Gateway profiles >4. Puppet templates and Hieradata for WSO2 Message Broker 3.1.0 >5. Puppet templates and Hieradata for WSO2 Data Analytics Server 3.0.1 > > Furthermore, it contains minor fixes to streamline Hieradata. > > *Source and distribution packages can be downloaded at:* > https://github.com/wso2/puppet-modules/releases/tag/1.1.0-rc1 > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > _______ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.0.0 RC3
*[x] Stable *- Go ahead and release Verified the following - Distribution and it's structure. - License headers - READMEs - Smoke test on all the products - Tested the versioning and organization name option tags when building - Tested the products using default provisioning method - Tested wso2esb using puppet provisioning method Regards, Vishanth On Mon, Apr 4, 2016 at 9:36 AM, Chamila De Alwis <chami...@wso2.com> wrote: > *[x] Stable *- Go ahead and release > > Verified the following > >- Repository structure >- Distribution >- Helper Scripts (build, run, stop) for WSO2 MB and WSO2 AM, and smoke >tests for basic product functionality >- License headers >- README content > > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Fri, Apr 1, 2016 at 3:54 PM, Isuru Haththotuwa <isu...@wso2.com> wrote: > >> This is the third release candidate (RC3) of WSO2 Dockerfiles 1.0.0 >> release. >> >> *Tag to be voted upon:* >> https://github.com/wso2/dockerfiles/tree/v1.0.0-rc3 >> >> *Source and distribution packages:* >> https://github.com/wso2/dockerfiles/releases/tag/v1.0.0-rc3 >> >> Please download, test, and vote. The README file under each product >> directory contains instructions on how to try it out locally. >> >> [ ] Broken - Do not release (explain why) >> [ ] Stable - Go ahead and release >> >> This vote will be open for 72 hours or as needed. >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Kubernetes] Using MySQL as the Default DB for WSO2 K8s Artifacts
+1 To brief out the changes that is required. Changes on Puppet-Modules - modify the hieradata (datasources to use mysql driver and correct url) - enabling -dSetup in wso2server.sh.erb Changes on Kubernetes-Artifacts - adding replication controller and service for product related mysql database - modifying the deploy and undeploy scripts for adding these product related mysql database controller and service I have now completed these changes in Puppet-modules and Kubernetes-Artifacts for WSO2AS and WSO2BPS products. Will continue working these changes on other products. Regards, Vishanth On Tue, Apr 26, 2016 at 1:20 PM, Isuru Haththotuwa <isu...@wso2.com> wrote: > Hi Devs, > > We can do $subject in the Kubernetes Artifacts. Its possible to define the > DB url with the relevant Kubernetes service name, hence there is no need to > know the exact IP of the database pod. > > Currently in mysql docker image [1], its only possible to create one DB > per container. Therefore to support the usual deployment clustered wso2 > products, we would need at least 3 pods: > >1. gov_db - shared across all products as necessary >2. user_db - shared across all products as necessary >3. product_db - used for config db (shared with all members of the >same cluster) and any other product specific db tables > > This will allow the users to deploy the wso2 products using defined real > distributed deployment patterns in a kubernetes environment with minimal > effort, without doing any configuration changes. > > Note that the purpose of this effort is to make it easier to try out WSO2 > products in a K8s environment, and to try out K8s features like > autoscaling, etc. without the hassle of configuring databases, etc. WDYT? > > [1]. https://hub.docker.com/_/mysql/ > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][Vote] Release WSO2 Puppet Modules 2.0.0
gt;>>> >>>> Removed use of Kubernetes Master details in Clustering templates >>>> - >>>> >>>> Streamlined use of hiera, hiera_array, and hiera_hash lookup >>>> - >>>> >>>>WSO2 API Manager Gateway Manager-Worker separate profiles in >>>>Hieradata >>>>- >>>> >>>>WSO2 PPaaS Puppet module and Hiera data removed >>>>- >>>> >>>>Deprecated older product versions >>>>- >>>> >>>> WSO2 AM 1.9.1 >>>> - >>>> >>>> WSO2 BRS 2.1.0 >>>> - >>>> >>>> WSO2 GREG 4.6.0 >>>> - >>>> >>>> WSO2 IS 5.0.0 >>>> - >>>> >>>> WSO2 MB 3.0.0 >>>> - >>>> >>>>Improve Puppet Vagrant setup to use PUPPET_HOME environment >>>>variable >>>>- >>>> >>>>Included sample config.yaml files in the Puppet Vagrant setup to >>>>quickly test standalone and distributed deployments >>>>- >>>> >>>>Fixed Java System Prefs location issue >>>>- >>>> >>>>Included YAML Style Guide for Hiera data files >>>> >>>> >>>> >>>> This release is based on the following tag: >>>> >>>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1 >>>> >>>> Release verification guide can be found at: >>>> >>>> >>>> https://docs.wso2.com/display/PM200/Setting+up+the+Development+Environment >>>> >>>> Source and distribution packages can be downloaded at: >>>> >>>> https://github.com/wso2/puppet-modules/releases/tag/v2.0.0-rc1 >>>> >>>> >>>> Regards, >>>> Chamila de Alwis >>>> Committer and PMC Member - Apache Stratos >>>> Software Engineer | WSO2 | +94772207163 >>>> Blog: code.chamiladealwis.com >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.io TW: @imesh >>> Lean . Enterprise . Middleware >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanuja Uruththirakodeeswaran >> Software Engineer >> WSO2 Inc.;http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 774363167 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] GSoC Dockerfiles weekly status meeting minutes
Hi, That's great Abhishek. You can build the docker images using puppet provisioning for Kubernetes platform and try to deploy in Kubernetes, you can follow the steps provided in the docs [1]. It is very easy to follow. [1] - https://docs.wso2.com/display/KA100/Deploying+a+WSO2+Product+in+Kubernetes Regards, Vishanth On Thu, May 19, 2016 at 9:49 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi All, > > Following are the meeting notes from our weekly status update meeting: > > *Tasks completed:* > 1. Completed code walk-through of Dockerfiles project. > 2. Understanding and build of clustered configuration for WSO2 ESB. This > was a huge step in understanding various profiles for clustered environment. > 3. Debugging and testing of docker-build and docker-run scripts. > 4. Added ability to fail fast when docker daemon is not running in the > host. Pull request [1]. > > *Current tasks:* > 1. Deploy docker products using puppet provisioning modules [2]. > 2. Use puppet provisioning to configure manager and worker profiles for > ESB. > 3. Investigate suitable programming languages and technologies for the > proposed test framework. > > Thanks, > Abhishek > > [1]. https://github.com/wso2/dockerfiles/pull/44 > [2]. https://github.com/wso2/puppet-modules > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Kubernetes Artifacts 1.0.0
*[X ] Stable* - go ahead and release I have verified the following. - READMEs - License - Packaging Tested the default and distributed deployment for the following products - WSO2 AS - WSO2 BPS - WSO2 BRS - WSO2 ESB - WSO2 GREG - WSO2 IS Regards, Vishanth On Fri, May 13, 2016 at 3:39 PM, Thanuja Uruththirakodeeswaran < thanu...@wso2.com> wrote: > [x] - Go ahead and release > > Verified the following: > > 1. License headers > 2. Tested distributed deployment in Kubernetes 1.2.0 with docker images > built using puppet provisioning: > >- WSO2 AS 5.3.0 >- WSO2 DSS 3.5.0 >- WSO2 ES 2.0.0 >- WSO2 BPS 3.5.0 >- WSO2 ESB 4.9.0 > > Thanks. > > On Fri, May 13, 2016 at 3:23 PM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> *[X] Stable* - go ahead and release >> >> Verified the following. >> >> >>1. README content >>2. License headers >>3. Packaging >>4. Tested distributed deployment using Puppet provisioned Docker >>images of the following products >> 1. WSO2 MB >> 2. WSO2 IS >> 3. WSO2 GREG >> 4. WSO2 BRS >> 5. WSO2 ESB >> 6. WSO2 DAS >> 7. WSO2 DSS >> 8. WSO2 AS >> >> >> >> >> Regards, >> Chamila de Alwis >> Committer and PMC Member - Apache Stratos >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> >> On Thu, May 12, 2016 at 6:17 PM, Imesh Gunaratne <im...@wso2.com> wrote: >> >>> +1 for the release, I verified following and did not see any problems: >>> >>>- README.md files >>>- K8S membership scheme and clustering >>>- Built product profile docker images using Puppet provisioning >>>- Distributed deployments of following on K8S 1.2: >>> - Application Server 5.3.0 >>> - API Manager 1.10.0 >>> - Enterprise Service Bus 4.9.0 >>> - Business Process Server 3.5.0 >>> - Business Rules Server 2.2.0 >>> - Data Services Server 3.5.0 >>> - Enterprise Store 2.0.0 >>> - Governance Registry 5.1.0 >>> - Data Analytics Server 3.0.1 >>> - Complex Event Processor 4.0.0 >>> >>> Thanks >>> >>> >>> On Wed, May 11, 2016 at 10:57 AM, Isuru Haththotuwa <isu...@wso2.com> >>> wrote: >>> >>>> This is the first release candidate (RC1) of WSO2 Kubernetes Artifacts >>>> 1.0.0. >>>> >>>> Please download, test and vote. Please refer the README files under >>>> each product for details on testing the artifacts. >>>> >>>> Source & binary distribution files: >>>> https://github.com/wso2/kubernetes-artifacts/releases/tag/v1.0.0 >>>> >>>> Maven staging repo: >>>> >>>> https://maven.wso2.org/nexus/content/repositories/orgwso2carbonkubernetesartifacts-1001/ >>>> >>>> The tag to be voted upon: >>>> https://github.com/wso2/kubernetes-artifacts/tree/v1.0.0 >>>> >>>> >>>> [ ] Broken - do not release (explain why) >>>> >>>> [ ] Stable - go ahead and release >>>> >>>> -- >>>> Thanks and Regards, >>>> >>>> Isuru H. >>>> +94 716 358 048* <http://wso2.com/>* >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.io TW: @imesh >>> Lean . Enterprise . Middleware >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanuja Uruththirakodeeswaran > Software Engineer > WSO2 Inc.;http://wso2.com > lean.enterprise.middleware > > mobile: +94 774363167 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.1.0 RC1
Hi, Thank you for taking your time to test and verify WSO2 Dockerfiles 1.1.0 RC1. The vote is been closed now. The vote passes with 8 'stable' votes and no votes for 'broken'. It will now be prepared for the release of WSO2 Dockerfiles 1.1.0. Regards, Vishanth On Fri, May 6, 2016 at 2:58 PM, Akila Ravihansa Perera <raviha...@wso2.com> wrote: > [x] Stable - Go ahead and release. > > Verified the following with Docker images built via WSO2 Dockerfiles; > - WSO2 IS 5.1.0 on Kubernetes > - WSO2 APIM 1.10.0 on Kubernetes > > > On Mon, May 2, 2016 at 5:42 PM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Hi Devs, >> >> >> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.1.0 >> release. >> >> Tag to be voted upon: >> >> https://github.com/wso2/dockerfiles/tree/v1.1.0-rc1 >> >> Source and distribution packages: >> >> https://github.com/wso2/dockerfiles/releases/tag/v1.1.0-rc1 >> >> Please download, test, and vote. The README file under the distribution >> contains guide and instructions on how to try it out locally. >> >> [ ] Broken - Do not release (explain why) >> >> [ ] Stable - Go ahead and release >> >> This vote will be open for 72 hours or as needed. >> >> Regards, >> Vishanth >> -- >> *Vishanth Balasubramaniam* >> Committer & PMC Member, Apache Stratos, >> Software Engineer, WSO2 Inc.; http://wso2.com >> >> mobile: *+94 77 17 377 18* >> about me: *http://about.me/vishanth <http://about.me/vishanth>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Dockerfiles 1.1.0 Released!
WSO2 PaaS team is pleased to announce the release of *WSO2 * *Dockerfiles 1.1.0.* WSO2 Dockerfiles 1.1.0 is the successor of 1.0.0. The main changes for this release: - An option flag in build script to skip confirmation for image overwriting - An option flag in build script to provide platform as an argument to build - An option flag in build script to tag name param in the build script - Fixing ‘IP command not found’ issue in puppet provisioning - Fixing ‘IP command not found’ issue by adding iproute2 to apt-get install - Added a root build script to build all docker images with default provisioning - Added a script to clean all the docker images built with default provisioning - Export CARBON_HOME before calling the profile init script - Option to prompt container logs in docker run script - Pick port between 8000 - 8010 for the http server - Corrected container_id variable name Release artifacts: https://github.com/wso2/dockerfiles/releases/tag/v1.1.0 Documentation: https://docs.wso2.com/display/DF110/WSO2+Dockerfiles+Documentation Known Issues: https://github.com/wso2/dockerfiles/issues Thank you, Vishanth on behalf of WSO2 PaaS Team. -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Dockerfiles 1.1.0 Released!
Thanks Akila for pointing that. I have corrected the tag now. Regards, Vishanth On Mon, May 9, 2016 at 9:56 AM, Akila Ravihansa Perera <raviha...@wso2.com> wrote: > Hi Vishanth, > > It seems Dockerfiles 1.1.0 has been released with the wrong tag. It should > have been the last commit for Dockerfiles 1.1.0-rc1 which points to [1], > but the released tag v1.1.0 points to [2]. > > [1] > https://github.com/wso2/dockerfiles/commit/fb17893b468133f4f87464e823493ebec9250f4d > [2] > https://github.com/wso2/dockerfiles/commit/638c84edd8566c797c67736dade553f9e3820709 > > Thanks. > > > > > On Fri, May 6, 2016 at 5:11 PM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> WSO2 PaaS team is pleased to announce the release of *WSO2 * >> *Dockerfiles 1.1.0.* >> >> WSO2 Dockerfiles 1.1.0 is the successor of 1.0.0. The main changes for >> this release: >> >> >>- >> >>An option flag in build script to skip confirmation for image >>overwriting >>- >> >>An option flag in build script to provide platform as an argument to >>build >>- >> >>An option flag in build script to tag name param in the build script >>- >> >>Fixing ‘IP command not found’ issue in puppet provisioning >>- >> >>Fixing ‘IP command not found’ issue by adding iproute2 to apt-get >>install >>- >> >>Added a root build script to build all docker images with default >>provisioning >>- >> >>Added a script to clean all the docker images built with default >>provisioning >>- >> >>Export CARBON_HOME before calling the profile init script >>- >> >>Option to prompt container logs in docker run script >>- >> >>Pick port between 8000 - 8010 for the http server >>- Corrected container_id variable name >> >> >> Release artifacts: >> >> https://github.com/wso2/dockerfiles/releases/tag/v1.1.0 >> >> >> Documentation: >> >> https://docs.wso2.com/display/DF110/WSO2+Dockerfiles+Documentation >> >> >> Known Issues: >> >> https://github.com/wso2/dockerfiles/issues >> >> >> >> Thank you, >> Vishanth on behalf of WSO2 PaaS Team. >> >> -- >> *Vishanth Balasubramaniam* >> Committer & PMC Member, Apache Stratos, >> Software Engineer, WSO2 Inc.; http://wso2.com >> >> mobile: *+94 77 17 377 18* >> about me: *http://about.me/vishanth <http://about.me/vishanth>* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Failed to add rxt to registry issue in GREG
Hi,
I'm trying to setup 2 GREG nodes clustered in Kubernetes using Kubernetes
Membership Scheme. The GREG nodes are started using Dsetup.
When both GREG nodes are started in different Pods during same time, the
following error occurs in one of the nodes but the product starts fine.
TID: [-1234] [] [2016-05-09 11:50:03,903] ERROR
{JAGGERY.app-scripts.init-scripts.app:js} -
org.mozilla.javascript.WrappedException: Wrapped
*org.wso2.carbon.registry.core.exceptions.RegistryException*: *Failed to
add rxt to registry* (/publisher/modules/publisher.js#48)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:42)
at
org.jaggeryjs.rhino.publisher.modules.c1._c_anonymous_2(/publisher/modules/publisher.js:48)
at
org.jaggeryjs.rhino.publisher.modules.c1.call(/publisher/modules/publisher.js)
at org.mozilla.javascript.ScriptRuntime.applyOrCall(ScriptRuntime.java:2430)
.
.
.
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
*Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException:
Failed to add rxt to registry*
at
org.wso2.carbon.governance.registry.extensions.utils.CommonUtil.addRxtConfigs(CommonUtil.java:265)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
... 144 more
*Caused by:
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/governance/repository/components/org.wso2.carbon.governance/types*
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:172)
at
org.wso2.carbon.registry.core.session.UserRegistry.getInternal(UserRegistry.java:613)
at
org.wso2.carbon.registry.core.session.UserRegistry.access$400(UserRegistry.java:60)
at
org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:596)
at
org.wso2.carbon.registry.core.session.UserRegistry$5.run(UserRegistry.java:593)
at java.security.AccessController.doPrivileged(Native Method)
at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:593)
at
org.wso2.carbon.governance.registry.extensions.utils.CommonUtil.addRxtConfigs(CommonUtil.java:224)
... 149 more
{JAGGERY.app-scripts.init-scripts.app:js}
What causes this issue?
Also this doesn't happen when one node is started first and then later if
it is scaled up.
Regards,
Vishanth
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Running WSO2ESB in Clutered mode
Hi Abhishek, On Mon, May 9, 2016 at 7:14 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi All, > > I have been trying to run ESB in clustered setup (one master and one > worker node). Here are the steps I followed: > 1) Have two copies of wso2esb-4.9.0 (esb-master and esb-worker). > 2) Started esb-master/bin/wso2server.sh > 3) Verified server start from logs and web management console. > 4) Started esb-workder/bin/wso2server.sh -DworkerNode (this gave port > already used exceptions for monitoring ports already in use) > I guess it could be because the port offset is not set in one of your esb nodes. Follow the steps in the link provided by Chamila, that would help. > > The above does not work, and unfortunately, I did not find cluster/profile > specific documentation in ESB documentation ( > https://docs.wso2.com/display/ESB490/Getting+Started), and there weren't > any samples (https://docs.wso2.com/display/ESB490/Samples) either. So my > questions are: > 1) How do run master worker setup in localhost. Any Docs? > 2) Are there any predefined profiles for this use-case? > > Thanks > Abhishek > Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSoC Dockerfiles] Meeting minutes
Hi, Good work so far Abhishek. We'll focus on getting the Kubernetes setup done soon and test it on that. Regards, Vishanth On Thu, Jul 28, 2016 at 2:49 PM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi All, > > We had a meeting on the progress and next steps of Dockerfiles test > framework. Here are the meeting minutes: > > 1. We are currently able to test default and puppet provisioning of WSO2 > products. I did a test of next Dockerfiles stable release 1.2.0 and did not > find any issue. > > 2. I am currently working on adding the ability to run smoke tests from > the framework. The idea is to have the capability of having product > specific smoke tests, then teams with more product knowledge can add smoke > tests. I will add smoke tests for ESB at this point. > > 3. I am going to try to have kubernetes setup on Mac using vagrant and > will try to deploy ESB docker build on it. If all goes well, we will have a > demo next week to a much larger audience and collect some feedback. > > 4. I will also add instructions to install golang locally on ubuntu on the > git repo, so that other developers can use the test framework for future > releases. > > Thanks > Abhishek > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework
Hi, Shall we have the demo on Friday Afternoon (IST)? Regards, Vishanth On Tue, Aug 9, 2016 at 4:28 PM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Mentors, > > Dockerfiles test framework is now able to run smoke tests, with smoke > tests for ESB added at this point. Developers can extend the framework to > add product specific smoke tests. > > Smoke test for ESB are implemented as follows: > 1. Once a new docker image is deployed and the container is up, the script > does a login to WSO2 carbon server and maintains cookies so that it can use > logged in state in subsequent requests. > > 2. Creates a new pass-through proxy service. [1] > > 3. Validates the newly created proxy service is accessible (validates Http > response code for the proxy testing url [2]) > > 4. Removes the newly created proxy service. [3] > > I would like to demo the current state of the project, please provide your > preferred date and time. > > Thanks > Abhishek > > [1]. Http post using /carbon/proxyservices/template_pass-through.jsp > [2]. Http get using /carbon/services/?tryit > [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang
Hi Abhishek, I see that you have given absolute path for "TestConfigPath" in "common/test-context.go". Why don't we give relative path from the project directory for this? Regards, Vishanth On Mon, Jul 11, 2016 at 5:22 PM, Imesh Gunaratne <im...@wso2.com> wrote: > Hi Abhishek, > > On Mon, Jul 11, 2016 at 1:53 PM, Abhishek Tiwari < > abhishek.tiwari0...@gmail.com> wrote: > >> Hi Mentors, >> >> I have been working on migrating the WSO2 Dockerfiles test framework from >> bash and python to use Golang. I must say, its been quite a ride but >> finally the migration has been successful. I am happy to offload many >> important features (logging, JSON parsing etc) to existing Golang packages. >> > >> I have also implemented interval based polling with linear backoff for >> exposed ports and carbon server status. The changes are committed to the >> repo [1], would love to get your feedback/comments. >> > > Very nice to hear this! > > We will go through the code. May be you can arrange a session to review > this. > > >> >> Since I am totally new to this language and completely blank on its >> coding standards, I am following the coding standards used in the open >> source Kubernetes [2]. >> > > +1 for following K8S coding standards. A bunch of Google developers are > involved in that > > project and AFAIK coding standards are at their best. > >> >> I absolutely love Golang and those who are interested, I would highly >> recommend gobyexample [3], I was able to get up to speed within hours. >> > > Yeah [3] is really useful. We also did couple of sessions on Golang at > WSO2 [4] > > [4] http://www.slideshare.net/imesh/an-introduction-to-go-55991343 > > Thanks > > > >> >> Thanks, >> Abhishek >> >> [1]. https://github.com/abhishek0198/test-framework/ >> [2]. https://github.com/kubernetes/kubernetes >> [3]. https://gobyexample.com/ >> > > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Update on Kubernetes setup
Alright Abhishek. On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Imesh, > > Most important issue was the IP address of docker container is not > accessibly directly, so I added a config in the test-config.json to specify > docker-machine ip address. If it is not present, I try to get the IP > address of the docker container. > > Vishanth, > I am still working on completing smoke tests so that I can make the > end-to-end workflow. Once that is done, I will schedule the demo. > > Thanks > Abhishek > > On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Abhishek, >> >> Please always send mails to WSO2 Dev except when you have sensitive >> information (such as credentials, etc) to share with us. >> >> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari < >> abhishek.tiwari0...@gmail.com> wrote: >> >>> Hi Mentors, >>> >>> I am able to run Kubernetes cluster on my Mac now and currently working >>> on deploying ESB on it. I ran into few issues with test framework not >>> working on Mac. >>> >> >> >> I >> t would be better to be more specific on the errors. >> >>> >>> Mac uses docker-machine (OSX specific util) to create virtual hosts >>> where it runs docker daemon, so its a bit different than Unix where daemon >>> runs directly on host. The IP address of deployed container is not directly >>> accessible, you need either create forwarding or go through >>> docker-machine's IP address. There were bunch of other small changes that I >>> had to do to make the test framework work across both Mac and Unix. Now >>> that its done, I am working on deployment. >>> >> >> What were the changes you did? >> >> Thanks >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [GSoC] Meeting minutes from Dockerfiles test framework demo
Great work Abhishek. We need to prioritize the work and discuss the final deliverables. We can probably do that in our next meeting. It would be great if you could do an effort estimation in your milestone plan sheet, where you can identify how many days it would take to finish off these tasks. Regards, Vishanth On Wed, Jun 29, 2016 at 11:55 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi All, > > Thanks so much for attending the demo and providing great feedback. > Following are the meeting minutes: > > 1. Demo of testing WSO2ESB 4.9.0 with default profile, discussed output > log and few implementation details. > > 2. Feedback: > a) Test framework should add the ability to check docker logs as well. > b) Checking for exposed ports should happen periodically with a timeout, > instead of a static sleep. > c) Look into feasibility of classifying errors (in build or run) in terms > of specific module (e.g. build failed due to an issue with hieradata). > d) Check status code returned from build and run scripts. > e) Look into integrating the test results into Jenkins, to allow nightly > runs. > f) Support of Kubernetes platform as well as product profiles (worker, > manager nodes) > > Please add if I missed something. > > Thanks > Abhishek > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue when configuring EmailOTP with Email API
Hi,
I followed the steps mentioned in the docs [1]. I am not sure what exactly
I need to set for the following configurations
- SendgridFormData
- SendgridURLParams
I am getting the following error when I tried to do the 2 step
authentication via Email OTP.
[2017-01-30 11:30:35,087] ERROR
{org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator} -
Unable to send the code
org.wso2.carbon.identity.application.authentication.framework.exception.AuthenticationFailedException:
Unable to send the code
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.initiateAuthenticationRequest(EmailOTPAuthenticator.java:186)
at
org.wso2.carbon.identity.application.authentication.framework.AbstractApplicationAuthenticator.process(AbstractApplicationAuthenticator.java:64)
at
org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler.doAuthentication(DefaultStepHandler.java:466)
.
.
.
Caused by:
org.wso2.carbon.identity.application.authentication.framework.exception.AuthenticationFailedException:
Unable to send the code
at
org.wso2.carbon.identity.authenticator.emailotp.EmailOTPAuthenticator.initiateAuthenticationRequest(EmailOTPAuthenticator.java:186)
... 62 more
[1] -
https://docs.wso2.com/display/ISCONNECTORS/Configuring+EmailOTP+With+Email+APIs
Regards,
Vishanth
--
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com
mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth <http://about.me/vishanth>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [puppet] Setting up puppet home from script
Hi, That probably be the reason. And yes it should be fixed. Regards, Vishanth On Wed, Sep 21, 2016 at 11:06 AM, Anuruddha Liyanarachchi < anurudd...@wso2.com> wrote: > Hi Vishanth, > > "Declare -A" option is not working in mac os because bash version of mac > os is not supporting declaring associate arrays [1]. Associative array > support is available from shell version 4 and upwards, and mac os shell > version is 3.2.57. > > I am currently looking into an alternative method without using > associative arrays. > > [1] http://stackoverflow.com/questions/6047648/bash-4- > associative-arrays-error-declare-a-invalid-option > > On Tue, Sep 20, 2016 at 5:23 PM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Hi Akila, >> >> With those changes, whatever product I specify it is setting up wso2das. >> >> For example, when I give *./setup.sh -p esb*, it is setting up wso2das >> module. >> >> Probably the declaration is not properly functioning. >> >> Regards, >> Vishanth >> >> On Mon, Sep 19, 2016 at 1:59 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi, >>> >>> I've improved the Puppet-Home setup script by introducing two map; >>> product_code_to_name_map and product_name_to_module_repo_map. With this >>> approach we can handle cases where product name and product code is >>> different. For eg: API Manager code is "apim" while product name is >>> "wso2am". >>> >>> Also I've added platform support for Hiera data as well. You can use >>> "setup.sh -p -l " to setup Puppet Home with >>> Hiera data for a specific platform. If none given it will default to >>> 'default' platform. >>> >>> The relevant platform repo for the given product should contain a >>> hieradata directory which will be symlink'd to PUPPET_HOME/hieradata. For >>> eg: wso2esb kubernetes platform - https://github.com/wso2/kubernetes-esb >>> should >>> contain a "hieradata" directory at the repo root level; >>> https://github.com/wso2/kubernetes-esb/tree/master/hieradata >>> >>> Thanks. >>> >>> On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi < >>> anurudd...@wso2.com> wrote: >>> >>>> Hi Pubudu, >>>> >>>> +1 for the platform support. >>>> I will add the platform support once we finalized the platform >>>> hieradata structure. >>>> >>>> On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne <im...@wso2.com> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka <pubu...@wso2.com> >>>>> wrote: >>>>> >>>>>> >>>>>> I think we need to include the platform as well. If we consider the >>>>>> big picture, ideally any user should be able to use this script and >>>>>> create >>>>>> a puppet home for building docker images for Kubernetes, Mesos, or any >>>>>> other platforms. As we have separate repos for platform hieradata, we >>>>>> need >>>>>> to copy those hieradata to the puppet home repo. >>>>>> >>>>> >>>>> +1 >>>>> >>>>> >>>>>> >>>>>> Thank you! >>>>>> >>>>>> >>>>>> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne <im...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi < >>>>>>> anurudd...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Imesh, >>>>>>>> >>>>>>>> I have now added the ability to configure multiple products using >>>>>>>> comma separated product list. >>>>>>>> Also included '-p all' option which configures all the products. >>>>>>>> >>>>>>>> Ex: ./setup.sh -p as >>>>>>>> Ex: ./setup.sh -p as,esb,bps >>>>>>>> Ex: ./setup.sh -p all >>>>>>>> >>>>>>> >>>>>>> Great! >>>>>>> Nice to hear that! >>>>>>> >>>>>>>> >>>
Re: [Dev] [puppet] Setting up puppet home from script
└── modules >>>>>>>> >>>>>>>> 3. Create a symlink to manifest/site.pp file. >>>>>>>> >>>>>>>> 4. Clone wso2base puppet module into /modules >>>>>>>> directory. >>>>>>>> >>>>>>>> 5. Create a symlink to wso2base common.yaml hiera-file. >>>>>>>> >>>>>>>>> /modules/wso2base/hieradata/wso2/common.yaml -> >>>>>>>>> /hieradata/dev/wso2/ >>>>>>>> >>>>>>>> >>>>>>>> 6. Clone wso2 puppet module into /modules >>>>>>>> directory. >>>>>>>> >>>>>>>> 7. Create a symlink to wso2 hiera-files. >>>>>>>> >>>>>>>>> /wso2/hieradata/dev/wso2/wso2 -> >>>>>>>>> ../hieradata/dev/wso2/ >>>>>>>> >>>>>>>> >>>>>>>> Once the setup.sh completes, users can copy product pack and jdk >>>>>>>> distribution for relevant folders and run vagrant setup against >>>>>>>> above-created puppet home. >>>>>>>> >>>>>>>> We are planning to automate the copying of product pack, jdk >>>>>>>> distribution and starting vagrant setup as well. >>>>>>>> >>>>>>>> Setup.sh can be found at [1]. Please share your suggestions towards >>>>>>>> this approach. >>>>>>>> >>>>>>>> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh >>>>>>>> >>>>>>>> -- >>>>>>>> *Thanks and Regards,* >>>>>>>> Anuruddha Lanka Liyanarachchi >>>>>>>> Software Engineer - WSO2 >>>>>>>> Mobile : +94 (0) 712762611 >>>>>>>> Tel : +94 112 145 345 >>>>>>>> a <thili...@wso2.com>nurudd...@wso2.com >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Imesh Gunaratne* >>>>>>> Software Architect >>>>>>> WSO2 Inc: http://wso2.com >>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>> W: https://medium.com/@imesh TW: @imesh >>>>>>> lean. enterprise. middleware >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Thanks and Regards,* >>>>>> Anuruddha Lanka Liyanarachchi >>>>>> Software Engineer - WSO2 >>>>>> Mobile : +94 (0) 712762611 >>>>>> Tel : +94 112 145 345 >>>>>> a <thili...@wso2.com>nurudd...@wso2.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Imesh Gunaratne* >>>>> Software Architect >>>>> WSO2 Inc: http://wso2.com >>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>> W: https://medium.com/@imesh TW: @imesh >>>>> lean. enterprise. middleware >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Pubudu Gunatilaka* >>>> Committer and PMC Member - Apache Stratos >>>> Software Engineer >>>> WSO2, Inc.: http://wso2.com >>>> mobile : +94774078049 <%2B94772207163> >>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Software Architect >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: https://medium.com/@imesh TW: @imesh >>> lean. enterprise. middleware >>> >>> >> >> >> -- >> *Thanks and Regards,* >> Anuruddha Lanka Liyanarachchi >> Software Engineer - WSO2 >> Mobile : +94 (0) 712762611 >> Tel : +94 112 145 345 >> a <thili...@wso2.com>nurudd...@wso2.com >> > > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [puppet-common] Setup puppet environment for specific product version
Hi, Now you can provide the product version to checkout from the git repository when setting up the puppet environment from setup.sh in puppet-commons [1]. Ex: ./setup.sh -p esb -v 4.9.0 -v is an optional argument, where if it is not specified it will checkout the latest puppet module of the product. [1] - https://github.com/wso2/puppet-common Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Samples config files for each product in puppet common
Hi Imesh, Thank you. I will add the vagrant samples for IoT. Regards, Vishanth On Wed, Nov 23, 2016 at 12:05 PM, Imesh Gunaratne <im...@wso2.com> wrote: > Hi Vishanth, > > On Tue, Nov 22, 2016 at 8:44 PM, Vishanth Balasubramaniam < > vishan...@wso2.com> wrote: > >> Hi Imesh, >> >> Have we removed the $subject? >> > > Yes, apologies for not notifying this. We moved vagrant samples to > puppet- repositories as those get changed with product > requirements: > > https://github.com/wso2/puppet-apim/tree/master/vagrant-samples > https://github.com/wso2/puppet-esb/tree/master/vagrant-samples > https://github.com/wso2/puppet-is/tree/master/vagrant-samples > https://github.com/wso2/puppet-cep/tree/master/vagrant-samples > https://github.com/wso2/puppet-das/tree/master/vagrant-samples > > Thanks > >> >> Regards, >> Vishanth >> >> -- >> *Vishanth Balasubramaniam* >> Committer & PMC Member, Apache Stratos, >> Software Engineer, WSO2 Inc.; http://wso2.com >> >> mobile: *+94 77 17 377 18* >> about me: *http://about.me/vishanth <http://about.me/vishanth>* >> > > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [PUPPET][CEP/DAS] Releasing puppet modules for restructured CEP-4.0.0 and DAS-3.0.1 puppet module distribution.
Hi Imesh, I have now added the custom logic in setup.sh in puppet-common for initializing IoT. I believe the setup script needs some improvements where I noticed that it still takes platform as an argument which is not being used. Regards, Vishanth On Tue, Nov 22, 2016 at 3:23 PM, Imesh Gunaratne <im...@wso2.com> wrote: > Adding others who are working on product puppet modules. > > I updated puppet-common and puppet-base repositories: [1], [2] as needed. > Vishanth is now working on adding custom logic to setup.sh in puppet-common > for initializing IoT product profiles. Once he is done we should be able to > release [1] and [2]. > > [1] https://github.com/wso2/puppet-common/commits/master > [2] https://github.com/wso2/puppet-base/commits/master > > Thanks > > On Mon, Nov 21, 2016 at 5:33 PM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Sajith, >> >> Thanks for your contributions on preparing DAS and CEP puppet modules. I >> will update puppet-common and puppet-base and let you know once they are >> ready to be released. >> >> We would need to publish product puppet modules (including wso2base) to >> Puppet Forge [5]. >> >> [5] https://docs.puppet.com/puppet/latest/reference/modules_ >> publishing.html >> >> Thanks >> >> On Mon, Nov 21, 2016 at 3:26 PM, Sajith Perera <saji...@wso2.com> wrote: >> >>> Hi All, >>> >>> We are planning to do a release on Puppet modules related to Complex >>> Event Processor 4.0.0 and Data Analytics Server 3.0.1. >>> Current puppet module for DAS 3.0.1 and CEP 4.0.0 supports following >>> deployment patterns. >>> >>> Pattern-1: Standalone server with default profile. >>> Pattern-2: Clustered environment (minimum HA) >>> >>> Also we are required to release puppet-common[2] 1.0.0 prior to these >>> releases. >>> I have tested the deployment scenarios via Puppet using VM and Docker >>> build as explained in [4]. >>> >>> [1] https://github.com/wso2/puppet-cep >>> [2] https://github.com/wso2/puppet-das >>> <https://github.com/wso2/puppet-base> >>> [3] https://github.com/wso2/puppet-common >>> [4] https://github.com/wso2/puppet-base/wiki/Setting-up-the-Deve >>> lopment-Environment >>> >>> Thanks, >>> SajithD >>> >>> -- >>> <http://wso2.com/signature> >>> Sajith Dimal >>> Software Engineer >>> Email : saji...@wso2.com >>> Mobile : +94783101496 >>> WSO2 Inc. | http://wso2.com >>> lean.enterprise.middleware >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Software Architect >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: https://medium.com/@imesh TW: @imesh >> lean. enterprise. middleware >> >> > > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > lean. enterprise. middleware > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Samples config files for each product in puppet common
Hi Imesh, Have we removed the $subject? Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Identity Server on the cloud with custom data stores (not the classic connectors)
Hi Hanen, Providing you the puppet module [1] and dockerfile [2] for WSO2IS here, if it can help you speed up your deployment process. [1] - https://github.com/wso2/puppet-is [2] - https://github.com/wso2/docker-is [3] - https://docs.wso2.com/display/PM200/Deploying+WSO2+Products+on+Kubernetes+Using+WSO2+Puppet+Modules Regards, Vishanth On Mon, Nov 14, 2016 at 2:11 PM, Hanen Ben Rhouma <hanen...@gmail.com> wrote: > Hello, > > Can WSO2 Identity Server be installed on the cloud and communicate with > custom data stores installed on premises (like through REST endpoints, LDAP > or JDBC stores) ? If so, how much time does the whole > installation/configuration/deployment process take ? > > > Regards, > > > *Hanen Ben Rhouma* > *Java Tech Lead* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while validating the signature in SAML Grant Type
Hi, In WSO2 IoT, we have created a service provider for our webapp and we use SAML grant type to create OAUTH Token. This works fine for the super tenant mode, but it fails for the tenant flow with the following error ERROR - SAML2BearerGrantHandler Error while validating the signature. org.opensaml.xml.validation.ValidationException: Signature did not validate against the credential's key at org.opensaml.xml.signature.SignatureValidator.validate(SignatureValidator.java:79) at org.wso2.carbon.identity.oauth2.token.handlers.grant.saml.SAML2BearerGrantHandler.validateGrant(SAML2BearerGrantHandler.java:511) at org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:212) at org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:223) at org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:287) at org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:151) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) When debugging we identified that the SSO signature is signed with super tenant key-store but it gets verified in the grant type with tenant's key-store. Have you all encountered this issue before? How can this be achieved? Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Not able to view the IoT Device Statistics Dashboard as a tenant
Hi Sinthuja, While testing the multi tenancy flow in the IoT Server I identified that when I am logged into the 'devicemgt' as a tenant, I am not able to go to the device statistics page/dashboard. Looked a little deeper and found out that the tenant space is created under jaggeryapps/portal/store but the gadgets folder within is empty for the tenant. I would like to know whether it is an issue or have I missed any configuration? Regards, Vishanth -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Not able to view the IoT Device Statistics Dashboard as a tenant
Hi, Thanks a lot for the replies. When trying to access the device statistics dashboard as a tenant through the device mgt UI, it directs to the " https://localhost:9443/portal/t/wso2.com/dashboards/device-statistics-dashboard/;. Which works fine for the super tenant but for tenants the url should be " https://localhost:9443/portal/t/wso2.com/dashboards/device-statistics-dashboard/?shared=true; and by default the device statistics dashboard should be shared with all tenants. I guess we need to do those changes for now. I have created a JIRA for this [1]. [1] - https://wso2.org/jira/browse/IOTS-343 Regards, Vishanth On Wed, Dec 21, 2016 at 2:13 PM, Sinthuja Ragendran <sinth...@wso2.com> wrote: > Hi Megala, > > On Wed, Dec 21, 2016 at 1:55 PM, Megala Uthayakumar <meg...@wso2.com> > wrote: > >> Hi Vishanth, >> >> Please find my comments inline. >> >> On Wed, Dec 21, 2016 at 1:08 PM, Vishanth Balasubramaniam < >> vishan...@wso2.com> wrote: >> >>> Hi Sinthuja, >>> >>> While testing the multi tenancy flow in the IoT Server I identified that >>> when I am logged into the 'devicemgt' as a tenant, I am not able to go to >>> the device statistics page/dashboard. >>> >> >> Device Statistics Dashboard will only work in the super-tenant mode. >> Reason behind this is dashboards will saved in the relevant tenant registry >> space and the dashboards that are packed within the car file will saved in >> the super-tenant space. We had another option of sharing dashboards between >> tenants but we cannot use that feature for this particular purpose as with >> that feature dashboard will be visible to all the tenant users regardless >> of his/her role. >> > > AFAIR this feature was implemented in such a way that we get the list of > roles of the logged in user and validate them, and in the case of shared > dashboard this validation will be occurred by the role again but then in > the tenant level, there should be such role created and the user should > have that role. It doesn't mean it is open to all users, such as > internal/everyone. > > We can handle this during the tenant creation time where we need to create > that role what ever we configure to view the device stats dashboard in the > tenant space, and assign the tenant admin user for that role. When we do > that, the tenant admin will be able to see the dashboard, and according to > his/her perference he/she can assign the roles to other users for whom he > would like to grant this right. But then later on if super tenant changes > the setting of the dashboard, all tenants view will be affected, I believe > this is not something which will happen regularly in the run time rather in > the setup time, so we can simply document the effect therefore it can be > gracefully handled. > > Thanks, > Sinthuja. > > >> But this dashboard requires some level of permissions, and should not be >> visible to all the users. So only option we left with it is to ask the >> tenant admin to upload the car files manually and created a documentation >> jira for this [1]. But while further testing we found that there is a >> problem in the implementation of oauth token generation part in portal >> level. In portal level, we generate the client credentials and save them in >> the registry. When we are in the tenant mode, to access that client >> credentials, we should start the tenant flow and get it. But in the portal >> side implementations, the tenant flow is not properly handled, due to that >> it will not work for other tenants even if the user uploads the car file. >> Since the token generation part is now completely changed in the portal >> side, I think that error should have been resolved by now and we should be >> able to view the dashboard in tenant mode as well by manually uploading the >> car file. >> >>> >>> Looked a little deeper and found out that the tenant space is created >>> under jaggeryapps/portal/store but the gadgets folder within is empty for >>> the tenant. >>> >> >> By default, sample gadgets will be only available in super-tenant space. >> So it is the expected behavior to not to have any gadgets in that >> particular location. >> >>> >>> I would like to know whether it is an issue or have I missed any >>> configuration? >>> >>> >> [1] https://wso2.org/jira/browse/DOCUMENTATION-4063 >> >> Thanks. >> >> Regards, >> Megala >> -- >> Megala Uthayakumar >> >> Software Engineer >> Mobile : 0779967122 <077%20996%207122> >> > > > > -- > *Sinthuja Rajendran* > Technical Lead > WSO2, Inc.:http://wso2.com > > Blog: http://sinthu-rajan.blogspot.com/ > Mobile: +94774273955 <+94%2077%20427%203955> > > > -- *Vishanth Balasubramaniam* Committer & PMC Member, Apache Stratos, Software Engineer, WSO2 Inc.; http://wso2.com mobile: *+94 77 17 377 18* about me: *http://about.me/vishanth <http://about.me/vishanth>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
