Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Imesh Gunaratne]

Hi Abhishek,

How can we build your latest code in [1]?
[1] https://github.com/abhishek0198/test-framework.git

Thanks

On Wed, Jul 20, 2016 at 11:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Imesh,
>
> Thanks a lot for the instructions, I will try the setup on OSX itself once
> I am done with the smoke tests.
>
> - Abhishek
>
>
> On Wednesday, July 20, 2016, Imesh Gunaratne  wrote:
>
>> Hi Abhishek,
>>
>> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I have been working on setting up Kubernetes cluster using vagrant and
>>> docker using [1]. I ran into multiple issues (coreos download taking hours,
>>> nfsd not being setup etc), however, those got resolved.
>>>
>>
>> ​Can you please execute following to ssh into the master node and check
>> the system log?
>>
>> vagrant ssh master
>> journalctl -f​
>>
>>
>>>
>>> Now, when I launch the setup using run.sh, I get this error [2]. I tried
>>> wiping out everything (vagrant destroy -f) and restart the whole process
>>> again, I get the same issue.
>>>
>>> One thing to note is, my host os is Mac and I use VirtualBox for
>>> development, so essentially I have virtualbox setup inside virtualbox. I
>>> don't think it should matter, but would like to get other people's opinion
>>> on this.
>>>
>>
>> ​This works on OSX.​
>>
>>
>>>
>>> While this issue gets resolved, I am planning to complete another
>>> milestone to add smoke tests for ESB and MB. I feel like, I should complete
>>> the test workflow for default platform before moving to Kubernetes, since
>>> the latter involves a lot of new technologies, more moving parts and other
>>> unknowns. I do plan to address Kubernetes testing, but would like to do
>>> that once default platform test workflow is complete. Thoughts?
>>>
>>
>> ​+1
>>
>> If [1] does not work for you, please try following:
>> http://kubernetes.io/docs/getting-started-guides/vagrant/
>>
>> Thanks​
>>
>>
>>>
>>> Thanks,
>>> Abhishek
>>>
>>> [1]. https://github.com/imesh/kubernetes-vagrant-setup
>>> [2].
>>> master: Waiting for machine to boot. This may take a few minutes...
>>> master: SSH address: 127.0.0.1:
>>> master: SSH username: core
>>> master: SSH auth method: private key
>>>
>>> Timed out while waiting for the machine to boot. This means that
>>> Vagrant was unable to communicate with the guest machine within
>>> the configured ("config.vm.boot_timeout" value) time period.
>>>
>>>
>>>
>>
>>
>> --
>> *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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Abhishek Tiwari]

Hi Imesh,

Thanks a lot for the instructions, I will try the setup on OSX itself once
I am done with the smoke tests.

- Abhishek

On Wednesday, July 20, 2016, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com
> > wrote:
>
>> Hi Mentors,
>>
>> I have been working on setting up Kubernetes cluster using vagrant and
>> docker using [1]. I ran into multiple issues (coreos download taking hours,
>> nfsd not being setup etc), however, those got resolved.
>>
>
> ​Can you please execute following to ssh into the master node and check
> the system log?
>
> vagrant ssh master
> journalctl -f​
>
>
>>
>> Now, when I launch the setup using run.sh, I get this error [2]. I tried
>> wiping out everything (vagrant destroy -f) and restart the whole process
>> again, I get the same issue.
>>
>> One thing to note is, my host os is Mac and I use VirtualBox for
>> development, so essentially I have virtualbox setup inside virtualbox. I
>> don't think it should matter, but would like to get other people's opinion
>> on this.
>>
>
> ​This works on OSX.​
>
>
>>
>> While this issue gets resolved, I am planning to complete another
>> milestone to add smoke tests for ESB and MB. I feel like, I should complete
>> the test workflow for default platform before moving to Kubernetes, since
>> the latter involves a lot of new technologies, more moving parts and other
>> unknowns. I do plan to address Kubernetes testing, but would like to do
>> that once default platform test workflow is complete. Thoughts?
>>
>
> ​+1
>
> If [1] does not work for you, please try following:
> http://kubernetes.io/docs/getting-started-guides/vagrant/
>
> Thanks​
>
>
>>
>> Thanks,
>> Abhishek
>>
>> [1]. https://github.com/imesh/kubernetes-vagrant-setup
>> [2].
>> master: Waiting for machine to boot. This may take a few minutes...
>> master: SSH address: 127.0.0.1:
>> master: SSH username: core
>> master: SSH auth method: private key
>>
>> Timed out while waiting for the machine to boot. This means that
>> Vagrant was unable to communicate with the guest machine within
>> the configured ("config.vm.boot_timeout" value) time period.
>>
>>
>>
>
>
> --
> *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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Imesh Gunaratne]

Hi Abhishek,

On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Mentors,
>
> I have been working on setting up Kubernetes cluster using vagrant and
> docker using [1]. I ran into multiple issues (coreos download taking hours,
> nfsd not being setup etc), however, those got resolved.
>

​Can you please execute following to ssh into the master node and check the
system log?

vagrant ssh master
journalctl -f​


>
> Now, when I launch the setup using run.sh, I get this error [2]. I tried
> wiping out everything (vagrant destroy -f) and restart the whole process
> again, I get the same issue.
>
> One thing to note is, my host os is Mac and I use VirtualBox for
> development, so essentially I have virtualbox setup inside virtualbox. I
> don't think it should matter, but would like to get other people's opinion
> on this.
>

​This works on OSX.​


>
> While this issue gets resolved, I am planning to complete another
> milestone to add smoke tests for ESB and MB. I feel like, I should complete
> the test workflow for default platform before moving to Kubernetes, since
> the latter involves a lot of new technologies, more moving parts and other
> unknowns. I do plan to address Kubernetes testing, but would like to do
> that once default platform test workflow is complete. Thoughts?
>

​+1

If [1] does not work for you, please try following:
http://kubernetes.io/docs/getting-started-guides/vagrant/

Thanks​


>
> Thanks,
> Abhishek
>
> [1]. https://github.com/imesh/kubernetes-vagrant-setup
> [2].
> master: Waiting for machine to boot. This may take a few minutes...
> master: SSH address: 127.0.0.1:
> master: SSH username: core
> master: SSH auth method: private key
>
> Timed out while waiting for the machine to boot. This means that
> Vagrant was unable to communicate with the guest machine within
> the configured ("config.vm.boot_timeout" value) time period.
>
>
>


-- 
*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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Abhishek Tiwari]

Hi Mentors,

I have been working on setting up Kubernetes cluster using vagrant and
docker using [1]. I ran into multiple issues (coreos download taking hours,
nfsd not being setup etc), however, those got resolved.

Now, when I launch the setup using run.sh, I get this error [2]. I tried
wiping out everything (vagrant destroy -f) and restart the whole process
again, I get the same issue.

One thing to note is, my host os is Mac and I use VirtualBox for
development, so essentially I have virtualbox setup inside virtualbox. I
don't think it should matter, but would like to get other people's opinion
on this.

While this issue gets resolved, I am planning to complete another milestone
to add smoke tests for ESB and MB. I feel like, I should complete the test
workflow for default platform before moving to Kubernetes, since the latter
involves a lot of new technologies, more moving parts and other unknowns. I
do plan to address Kubernetes testing, but would like to do that once
default platform test workflow is complete. Thoughts?

Thanks,
Abhishek

[1]. https://github.com/imesh/kubernetes-vagrant-setup
[2].
master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:
master: SSH username: core
master: SSH auth method: private key

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev