+1
On Wed, Dec 24, 2014 at 9:26 PM, Imesh Gunaratne wrote:
> Hi Devs,
>
> I think we need to do $subject containing following information:
> - Reason for taking a copy
> - Modifications done
> - Pull requests given
> - Any other information needed
>
> Thanks
>
>
> --
> Imesh Gunaratne
>
> Techni
On Thu, Dec 25, 2014 at 4:29 AM, John Mathon wrote:
> Lakmal, this is amazing. It will not only allow us to test Stratos better
> and faster and encourage others to contribute but it is potentially an
> engine for us to test cartridges against future versions of Stratos as well
> as different ver
Discussed in the following mail thread.
Docker pulling the image from the repository in the Kubernetes setup
Thanks
On Thursday, December 25, 2014, Rajkumar Rajaratnam
wrote:
> Chamila also reported this sometimes back in stratos dev list. I don't
> remember whether he was able to solve this.
Chamila also reported this sometimes back in stratos dev list. I don't
remember whether he was able to solve this.
Thanks
On Thursday, December 25, 2014, Imesh Gunaratne wrote:
> Hi Devs,
>
> I'm seeing a problem with Kubernetes 0.5.2 where it always trying to pull
> docker images from the Dock
Hi Devs,
I'm seeing a problem with Kubernetes 0.5.2 where it always trying to pull
docker images from the Docker Hub even though the docker images are
available locally.
I can see this issue has been reported and fixed here:
https://github.com/GoogleCloudPlatform/kubernetes/issues/504
I'm curren
Yes there is no reference to 1.7.1-stratos in the codebase, I guess maven
is trying to fetch the latest available since the dependency is not there.
On Thu, Dec 25, 2014 at 12:35 AM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Just completed a clean repo build on STRATOS_HOME/pom.xml and all went
> fin
Lakmal, this is amazing. It will not only allow us to test Stratos better and
faster and encourage others to contribute but it is potentially an engine for
us to test cartridges against future versions of Stratos as well as different
versions of similar cartridges against one Stratos version. W
Hi,
Just completed a clean repo build on STRATOS_HOME/pom.xml and all went fine
without any issues.
But I noticed that the dependency to openstack-neutron:1.8.1-stratos is
missing from cc feature pom.xml.
However it will not cause a build failure. Reason is
STRATOS_HOME/dependencies are built fi
*createReplicationController(String replicationControllerId, String
replicationControllerName,*
*String dockerImage,
List containerPorts,*
*EnvironmentVariable[]
environmentVariables, int replicas)*
On Wed, Dec
Hi Devs,
In Kubernetes API client we have used following methods to create
replication controllers, services and pods:
*createReplicationController(ReplicationController replicationController)*
*createService(Service service)*
*createPod(Pod pod)*
Replication controller creation process involves
Thanks for the clarification Raj!
On Wed, Dec 24, 2014 at 11:15 PM, Rajkumar Rajaratnam
wrote:
> Yes we did.
>
> As mentioned in my previous reply, please refer this JIRA for more
> information. This contains why we did/didn't fork each modules.
>
> https://issues.apache.org/jira/browse/STRATOS-
Yes we did.
As mentioned in my previous reply, please refer this JIRA for more
information. This contains why we did/didn't fork each modules.
https://issues.apache.org/jira/browse/STRATOS-1002
Thanks.
On Wed, Dec 24, 2014 at 11:10 PM, Imesh Gunaratne wrote:
> Make sense, did we verify whethe
Make sense, did we verify whether changes done in openstack-nova 1.8.0 fork
are available in 1.8.1?
Thanks
On Wed, Dec 24, 2014 at 11:06 PM, Rajkumar Rajaratnam
wrote:
> Hi,
>
> Please refer this JIRA for more information on this jclouds upgrade from
> 1.8.0 to 1.8.1
>
> https://issues.apache.o
Hi,
Please refer this JIRA for more information on this jclouds upgrade from
1.8.0 to 1.8.1
https://issues.apache.org/jira/browse/STRATOS-1002
Thanks.
On Wed, Dec 24, 2014 at 11:03 PM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> This is openstack-nova 1.8.0 fork.
>
> We have switched to 1.8.1
Hi Imesh,
This is openstack-nova 1.8.0 fork.
We have switched to 1.8.1 from December 3rd.
Thanks.
On Wed, Dec 24, 2014 at 10:59 PM, Imesh Gunaratne wrote:
> Seems like we have removed it two days ago, did we verify whether it is
> used or not before removing?
>
>
> https://github.com/apache/s
Seems like we have removed it two days ago, did we verify whether it is
used or not before removing?
https://github.com/apache/stratos/commit/a9834e9ec1c7c9056fb36dbfcf18bc3fd73087bc#diff-ddb15574bef1e045333ad243338de9c9
On Wed, Dec 24, 2014 at 10:09 PM, Rajkumar Rajaratnam
wrote:
> Sorry for t
Both clases ClientCredentialsGrantHandler and SignedJWTAuthenticator have
the package name "org.wso2.carbon.identity...", which implies that they
belong to Carbon Identity Management.
We have not extended ClientCredentialsGrantHandler class, rather we have
duplicated the code and added more logic,
Hi Imesh,
Those are not identity components. Only JWT authenticator which is used by
AF is forked. Client credential handler is extended by me to return an JWT
token which earlier sent a text token. It is not a folk I guess.
I will add it to readme.
Touched, not typed. Erroneous words are a fe
Sorry for the typo :)
s/Do we the fork in our code base?/Do we have the fork in our code base?
Thanks.
On Wed, Dec 24, 2014 at 9:39 PM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> We didn't fork openstack-nova 1.8.1.
>
> Do we the fork in our code base? Where?
>
> Thanks.
>
> On Wed, Dec 24, 20
Hi Devs,
Shall we mention the reasons for forking following Carbon Identity
Management classes in a README file:
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Yes, the dependency to this module was missing in the cloud controller
feature. Try to do a clean repo build, you will see the error.
Thanks
On Wed, Dec 24, 2014 at 9:42 PM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> Can you explain a bit about this error and the fix you made?
>
> We didn't use
Hi Imesh,
Can you explain a bit about this error and the fix you made?
We didn't use openstack-neutron in any of the previous releases. It is
added recently and the version is 1.8.1-stratos.
Thanks.
On Wed, Dec 24, 2014 at 9:29 PM, Imesh Gunaratne wrote:
> I just found the problem and fixed i
Hi Imesh,
We didn't fork openstack-nova 1.8.1.
Do we the fork in our code base? Where?
Thanks.
On Wed, Dec 24, 2014 at 9:33 PM, Imesh Gunaratne wrote:
> Does anyone know why we have forked it?
>
> On Wed, Dec 24, 2014 at 9:25 PM, Udara Liyanage wrote:
>
>> If we are not packaging, we can rem
Does anyone know why we have forked it?
On Wed, Dec 24, 2014 at 9:25 PM, Udara Liyanage wrote:
> If we are not packaging, we can remove it
>
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
> On Dec 24, 2014 9:22 PM, "Imesh Gunaratne" wrote:
>
>> Hi Devs,
>>
>> I just notice
If we are not packaging, we can remove it
Touched, not typed. Erroneous words are a feature, not a typo.
On Dec 24, 2014 9:22 PM, "Imesh Gunaratne" wrote:
> Hi Devs,
>
> I just noticed that we have forked OpenStack Nova module but we are not
> packaging it. As I see in the cloud controller fea
I just found the problem and fixed it. We have not defined a dependency for
the above module in the cloud controller feature pom.xml file.
Please do a clean repo build when module dependencies/versions are changed,
otherwise such issues might not surface.
Thanks
On Wed, Dec 24, 2014 at 9:11 PM,
Hi Devs,
I think we need to do $subject containing following information:
- Reason for taking a copy
- Modifications done
- Pull requests given
- Any other information needed
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Hi Devs,
I just noticed that we have forked OpenStack Nova module but we are not
packaging it. As I see in the cloud controller feature we are packaging
jclouds version of it:
org.apache.jclouds.api:openstack-nova:${jclouds.version}
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer
I see the below error in Cloud Controller feature:
[ERROR] Failed to execute goal on project
org.apache.stratos.cloud.controller.feature: Could not resolve dependencies
for project
org.apache.stratos:org.apache.stratos.cloud.controller.feature:pom:4.1.0-SNAPSHOT:
Failure to find org.apache.stratos
Thanks for the information Raj, shall we add this to a README file under
this module?
IMO each forked module should have a README file mentioning the changes we
have done, any pull requests given, etc.
Thanks
On Wed, Dec 24, 2014 at 7:38 PM, Rajkumar Rajaratnam
wrote:
> s/Once we upgrade *jclou
s/Once we upgrade *jclouds to 1.8.1*, we can safely remove the clone/Once
we upgrade *to next jclouds version*, we can safely remove the clone
Thanks.
On Wed, Dec 24, 2014 at 7:34 PM, Rajkumar Rajaratnam
wrote:
> Hi Imesh,
>
> Jclouds neutron bundle's manifest is malformed, hence it is not load
Hi Imesh,
Jclouds neutron bundle's manifest is malformed, hence it is not loaded into
OSGi runtime. I conveyed this to Jclouds team and they fixed it. But it
will not be back ported to 1.8.1 soon. Hence I had to clone neutron api to
stratos code base. Once we upgrade jclouds to 1.8.1, we can safel
Thanks Nirmal, I will try this out.
On Wed, Dec 24, 2014 at 1:43 PM, Nirmal Fernando
wrote:
> Hi Imesh,
>
> I fixed the issue with minion yaml file and please try with latest master.
>
> And I was using a 2-VM setup, please find the vagrant file at
> https://github.com/nirmal070125/vagrant-kuber
Hi Raj,
What is the reason for forking openstack-neutron module? Do we have any
local changes?
Thanks
On Wed, Dec 24, 2014 at 12:14 PM, Imesh Gunaratne wrote:
> Great! Thanks Raj!
>
> On Wed, Dec 24, 2014 at 10:05 AM, Rajkumar Rajaratnam
> wrote:
>
>> Hi Imesh,
>>
>> We have been using this v
Rajkumar Rajaratnam created STRATOS-1054:
Summary: Stratos should not release(delete) predefined floating IPs
Key: STRATOS-1054
URL: https://issues.apache.org/jira/browse/STRATOS-1054
Project:
Hi Devs,
Created a JIRA to track this for FUTURE releases.
https://issues.apache.org/jira/browse/STRATOS-1054
Thanks.
On Fri, Nov 21, 2014 at 5:41 PM, Nirmal Fernando wrote:
> Great! Please check on other IaaSes too.
>
> On Fri, Nov 21, 2014 at 12:03 PM, Rajkumar Rajaratnam
> wrote:
>
>> Pro
[
https://issues.apache.org/jira/browse/STRATOS-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam reassigned STRATOS-1053:
Assignee: Rajkumar Rajaratnam
> Turning off auto-scaling
> --
Rajkumar Rajaratnam created STRATOS-1053:
Summary: Turning off auto-scaling
Key: STRATOS-1053
URL: https://issues.apache.org/jira/browse/STRATOS-1053
Project: Stratos
Issue Type: New
Hi Devs,
Created a JIRA to track this feature for FUTURE releases.
https://issues.apache.org/jira/browse/STRATOS-1053
Thanks.
On Wed, Nov 5, 2014 at 5:21 PM, Lahiru Sandaruwan wrote:
> +1 for the feature as it removes the overhead of running scale rule(now we
> can do it by setting min=max).
Hi Imesh,
I fixed the issue with minion yaml file and please try with latest master.
And I was using a 2-VM setup, please find the vagrant file at
https://github.com/nirmal070125/vagrant-kubernetes-setup/blob/master/2-vm-setup/Vagrantfile
On Wed, Dec 24, 2014 at 9:34 AM, Imesh Gunaratne wrote:
40 matches
Mail list logo