Re: [Discuss] Kubernetes workflow is now working!

Hi David, These Vagrant scripts are creating virtual machines inside a host machine. Seems like you are trying on Openstack instance which is also a virtualized environment. On Fri, Jan 9, 2015 at 6:29 AM, david hbase wrote: > Thanks for you guys. > > Further issue showing up: ( the instance ub

Re: [Discuss] Kubernetes workflow is now working!

Thanks for you guys. Further issue showing up: ( the instance ubuntu 12.04 is from my private openstack ) vagrant-kubernetes-setup# ./up.sh ---> Step 0: Flush everything ==> minion-2: VM not created. Moving on... ==> minion-1: VM not created. Moving on... ==> master: VM not created. Moving on...

Re: [Discuss] Kubernetes workflow is now working!

Error says "group id cannot be empty". But we do not have grouping in 4.1.0-m3 developer preview. It seems David is trying master branch with M3 guide. Please follow the document Imesh shared if you trying out master branch. Thanks. On Thu, Jan 8, 2015 at 2:59 PM, Imesh Gunaratne wrote: > Hi Da

Re: [Discuss] Kubernetes workflow is now working!

Hi David, If you prefer you could tryout the latest Kubernetes implementation in the master branch by refering the following document: https://gist.github.com/imesh/b8f81fac8de39183a504 If you need to get 4.1.0-M3 working, please send us the artifacts (json files) that you are using and the carbo

Re: [Discuss] Kubernetes workflow is now working!

Hi David, Are you using the code base with 4.1.0-m3 tag or master branch? Thanks. On Thu, Jan 8, 2015 at 2:23 PM, david hbase wrote: > Kubernetes workflow is not working! >

Re: [Discuss] Kubernetes workflow is now working!

Kubernetes workflow is not working! I have following all the steps in the M3, but can not "Registering Kubernetes-CoreOS Host Cluster in Stratos" Er

Re: [Discuss] Kubernetes workflow is now working!

Seems like we have a string formatting issue in agent: http://stackoverflow.com/questions/18053500/typeerror-not-all-arguments-converted-during-string-formatting-python On Fri, Dec 26, 2014 at 3:11 PM, Imesh Gunaratne wrote: > I fixed the above issue with INTERNAL parameter and now I'm seeing t

Re: [Discuss] Kubernetes workflow is now working!

I fixed the above issue with INTERNAL parameter and now I'm seeing the following error: [2014-12-26 09:37:27,321] INFO {cartridgeagentconfiguration.py:__init__} - Cartridge agent configuration initialized Traceback (most recent call last): File "/usr/lib/python2.7/logging/__init__.py", line 850,

Re: [Discuss] Kubernetes workflow is now working!

As I found there was an issue in agent code, it was using PROVIDER constant to fetch the INTERNAL parameter. I cannot see PROVIDER parameter being using in the agent. Thanks On Fri, Dec 26, 2014 at 2:32 PM, Gayan Gunarathne wrote: > Hi Imesh, > > Attachment is the sample launch_params that I ha

Re: [Discuss] Kubernetes workflow is now working!

Hi Imesh, Attachment is the sample launch_params that I have tested. Thanks, Gayan On Fri, Dec 26, 2014 at 2:22 PM, Gayan Gunarathne wrote: > Hi Imesh, > > Is that launch_params contains the PROVIDER parameter? I guess this comes > when the provider is not available in the payload. Seems lik

Re: [Discuss] Kubernetes workflow is now working!

Hi Imesh, Is that launch_params contains the PROVIDER parameter? I guess this comes when the provider is not available in the payload. Seems like we are showing wrong error message. Thanks, Gayan On Fri, Dec 26, 2014 at 2:05 PM, Imesh Gunaratne wrote: > Thanks Gayan, yes it was not there in la

Re: [Discuss] Kubernetes workflow is now working!

Thanks Gayan, yes it was not there in launch_params, I just fixed it and seeing the below error: [2014-12-26 08:31:17,311] INFO {cartridgeagentconfiguration.py:__init__} - INTERNAL payload parameter is not found [2014-12-26 08:31:17,311] INFO {cartridgeagentconfiguration.py:__init__} - Cartridge

Re: [Discuss] Kubernetes workflow is now working!

Hi Imesh, This is happen when CLUSTER_INSTANCE_ID not contain as the payload parameter of the cartridge agent.I think we can first check the agent payload and see CLUSTER_INSTANCE_ID is there in the agent payload. Thanks, Gayan On Fri, Dec 26, 2014 at 1:39 PM, Imesh Gunaratne wrote: > I fixed

Re: [Discuss] Kubernetes workflow is now working!

I fixed the above issue in cartridge agent and re-created the base image, now I'm seeing another error: root@e82ebdc6-8cd5-11e4-85d5-080027f35f1b:~# cat /tmp/agent.screen.log Traceback (most recent call last): File "agent.py", line 32, in from modules.extensions import defaultextensionhandl

[Discuss] Kubernetes workflow is now working!

Hi Devs, I fixed some of the issues in Kubernetes Iaas and tested the Kubernetes workflow with sample php docker image. Now replication controllers, services and containers get created without a problem. We can also access the php server in the container. However I noticed that agent does not sen