Hi,

I am not sure what is the root cause for this. You can get more help from
the Kubernetes community. For the moment, you can check the logs in the
master node and other minion nodes to get some idea [1]. Looks like the
issue exists in only one node. In [1] there is troubleshoot guide you can
follow.

Please note that Stratos 4.1.5 is only tested in Kubernetes v1.0.6 and
below. There could be API changes in the latest Kubernetes releases.

[1] -
http://reddragonspace.blogspot.com/2015/07/setup-kubernetes-cluster-on-ec2.html

On Tue, Mar 22, 2016 at 12:04 PM, Aanand <anand...@gmail.com> wrote:

> Hi Pubudu,
>
> I am successful in creating a Stratos from the scratch on docker. but I
> installing kubernetes
>
> On a Ubuntu VM in OpenStack, I have followed the steps as per this link
> http://blog.guthnur.net/kubernetes-ubuntu-installation/
> to install Kubernetes.
>
> When running the following command only the master getting up but not
> minions is this related to VT-x in OpenStack
>
> And also, same kinda error when I am using Kubernetes setup with vagrant,
> see the attachment.
>
> Please give me some clue on this.
>
> root@stratos:~/kubernetes/cluster# KUBERNETES_PROVIDER=ubuntu
> ./kube-down.sh
> Bringing down cluster using provider: ubuntu
> Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
> FLANNEL_NET
> 172.16.0.0/16
> <http://t.sidekickopen50.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs2Bpw0YW2zWTD82BgKpCW1q7mhC56dJdpf8WWdCj02?t=http%3A%2F%2F172.16.0.0%2F16&si=5256626682986496&pi=d7324122-3ab1-4221-c554-bde745f6a562>
> Cleaning on node 127.0.0.1
> 9910
> etcd stop/waiting
> Connection to 127.0.0.1 closed.
> Done
> root@stratos:~/kubernetes/cluster# KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
> Starting cluster using provider: ubuntu
> ... calling verify-prereqs
> Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
> ... calling kube-up
> FLANNEL_NET
> 172.16.0.0/16
> <http://t.sidekickopen50.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs2Bpw0YW2zWTD82BgKpCW1q7mhC56dJdpf8WWdCj02?t=http%3A%2F%2F172.16.0.0%2F16&si=5256626682986496&pi=d7324122-3ab1-4221-c554-bde745f6a562>
> Deploying master and minion on machine 127.0.0.1
>
> config-default.sh                             100% 2902     2.8KB/s   00:00
> util.sh                                       100%   13KB  13.4KB/s   00:00
> kube-apiserver.conf                           100%  676     0.7KB/s   00:00
> etcd.conf                                     100%  576     0.6KB/s   00:00
> kube-controller-manager.conf                  100%  746     0.7KB/s   00:00
> flanneld.conf                                 100%  569     0.6KB/s   00:00
> kube-scheduler.conf                           100%  676     0.7KB/s   00:00
> kube-scheduler                                100% 2360     2.3KB/s   00:00
> kube-controller-manager                       100% 2672     2.6KB/s   00:00
> kube-apiserver                                100% 2358     2.3KB/s   00:00
> etcd                                          100% 2073     2.0KB/s   00:00
> flanneld                                      100% 2159     2.1KB/s   00:00
> reconfDocker.sh                               100% 1493     1.5KB/s   00:00
> etcd.conf                                     100%  576     0.6KB/s   00:00
> kube-proxy.conf                               100%  648     0.6KB/s   00:00
> flanneld.conf                                 100%  569     0.6KB/s   00:00
> kubelet.conf                                  100%  634     0.6KB/s   00:00
> kube-proxy                                    100% 2230     2.2KB/s   00:00
> etcd                                          100% 2073     2.0KB/s   00:00
> kubelet                                       100% 2162     2.1KB/s   00:00
> flanneld                                      100% 2159     2.1KB/s   00:00
> etcdctl                                       100% 6041KB   5.9MB/s   00:00
> kube-scheduler                                100%   17MB  17.0MB/s   00:01
> kube-controller-manager                       100%   26MB  26.2MB/s   00:00
> kube-apiserver                                100%   34MB  33.7MB/s   00:00
> etcd                                          100% 6494KB   6.3MB/s   00:00
> flanneld                                      100% 8695KB   8.5MB/s   00:00
> etcdctl                                       100% 6041KB   5.9MB/s   00:01
> kube-proxy                                    100%   17MB  16.8MB/s   00:00
> etcd                                          100% 6494KB   6.3MB/s   00:00
> kubelet                                       100%   33MB  33.2MB/s   00:00
> flanneld                                      100% 8695KB   8.5MB/s   00:01
> etcd start/running, process 23263
> Connection to 127.0.0.1 closed.
> Validating master
> Validating root@127.0.0.1
>
> Kubernetes cluster is running.  The master is running at:
>
>   http://127.0.0.1
> <http://t.sidekickopen50.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs2Bpw0YW2zWTD82BgKpCW1q7mhC56dJdpf8WWdCj02?t=http%3A%2F%2F127.0.0.1%2F&si=5256626682986496&pi=d7324122-3ab1-4221-c554-bde745f6a562>
>
> FLANNEL_NET
> 172.16.0.0/16
> <http://t.sidekickopen50.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XZs2Bpw0YW2zWTD82BgKpCW1q7mhC56dJdpf8WWdCj02?t=http%3A%2F%2F172.16.0.0%2F16&si=5256626682986496&pi=d7324122-3ab1-4221-c554-bde745f6a562>
> Using master 127.0.0.1
> Wrote config for ubuntu to /root/.kube/config
> ... calling validate-cluster
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
> Waiting for 2 ready nodes. 1 ready nodes, 1 registered. Retrying.
>
> Regards,
> Aanand
> Phone: 8098816226
> Skype: anand7007
>
> On Thu, Mar 17, 2016 at 10:54 AM, Pubudu Gunatilaka <pub...@apache.org>
> wrote:
>
>> Hi Aanand,
>>
>> What I am saying is you can hard code the mb endpoints in the Stratos and
>> create the docker image.
>>
>> Link in [1] is not upto date. That's why I asked you to create a docker
>> image from the scratch. That is the easiest way to do this.
>>
>> [1] -
>> https://cwiki.apache.org/confluence/display/STRATOS/Running+Stratos+inside+docker
>>
>> Thank you!
>>
>> On Wed, Mar 16, 2016 at 6:26 PM, Aanand <anand...@gmail.com> wrote:
>>
>>> Hi, How could use the "You can use a pre build docker image of stratos
>>> which has hard coded values for activemq endpoints" as your mentioned,
>>> where I could get this.
>>> Please help me get this done.
>>>
>>> Regards,
>>> Aanand
>>> Phone: 8098816226
>>> Skype: anand7007
>>>
>>> On Mon, Mar 7, 2016 at 12:40 PM, Aanand <anand...@gmail.com> wrote:
>>>
>>>> HI Pubudu, Thanks for your help, I will check.
>>>>
>>>> Regards,
>>>> Aanand
>>>> Phone: 8098816226
>>>> Skype: anand7007
>>>>
>>>> On Sat, Mar 5, 2016 at 11:55 AM, Pubudu Gunatilaka <pub...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Aanand,
>>>>>
>>>>> What are the issues you are getting? Basically to run Stratos on
>>>>> docker you need to consider following aspects.
>>>>>
>>>>> 1. JDK
>>>>> 2. Apache Activemq
>>>>> 3. CEP (Internally or Externally)
>>>>>
>>>>> As a basic installation I would suggest to do following.
>>>>>
>>>>> 1. Run activemq separately on a docker container or any other
>>>>> reachable host.
>>>>> 2. Create a docker image including JDK and Stratos.
>>>>>
>>>>> Please do the changes mentioned in [1]. You can use a pre build docker
>>>>> image of stratos which has hard coded values for activemq endpoints. If 
>>>>> you
>>>>> want you can go with a dynamically setting up approach using [2] or using
>>>>> environment variables approach.
>>>>>
>>>>> Guide [1] also points out how you can run CEP externally. If you are
>>>>> running CEP internally you don't need to do any changes in stratos side.
>>>>>
>>>>> Once you have the Stratos up and running follow [3] to add a
>>>>> Kubernetes cluster to Stratos.
>>>>>
>>>>> You can use WSO2 cartridges mentioned in [4]. Actually in these
>>>>> cartridges, configurations happen dynamically. In other words it happens 
>>>>> at
>>>>> the start of the docker container. Currently we are moving into pre-build
>>>>> docker images in [5]. This will be released soon.
>>>>>
>>>>> [1] -
>>>>> https://cwiki.apache.org/confluence/display/STRATOS/4.1.x+Deploying+Stratos+on+a+Preferred+IaaS
>>>>> [2] -
>>>>> https://github.com/wso2/private-paas-cartridges/tree/master/common/configurator/modules/distribution
>>>>> [3] -
>>>>> https://cwiki.apache.org/confluence/display/STRATOS/4.1.x+Adding+a+Kubernetes-CoreOS+Cluster+via+the+UI
>>>>> [4] - https://github.com/wso2/private-paas-cartridges
>>>>> [5] - https://github.com/wso2/kubernetes-artifacts
>>>>>
>>>>> Thank you!
>>>>>
>>>>> On Fri, Mar 4, 2016 at 4:23 PM, Aanand <anand...@gmail.com> wrote:
>>>>>
>>>>>> I am in the process of setup stratos with kubernetes. For I have
>>>>>> setup kubernetes as per in this link
>>>>>> http://containertutorials.com/get_started_kubernetes/index.html
>>>>>> stratos on other ubuntu machine as per this link
>>>>>> https://cwiki.apache.org/confluence/display/STRATOS/Running+Stratos+inside+docker
>>>>>> Now I am having problem linking kubernetes cluster with stratos. Is there
>>>>>> is any easy way to do this, my requirement is need to have stratos in
>>>>>> docker container and also all the cartridges of wso2 also in the docker.
>>>>>> Regards,
>>>>>> Aanand
>>>>>> Phone: 8098816226
>>>>>> Skype: anand7007
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to