docker mesos integration

122 views
Skip to first unread message

Jakub Veverka

unread,
Feb 4, 2015, 5:22:06 PM2/4/15
to go...@googlegroups.com
HI, 

we are considering migration to go from jenkins In our team. I find only one component missing and I would like to ask you if this is somehow simply solvable in go wold... 

We are using jenkins mesos plugin (https://github.com/jenkinsci/mesos-plugin) as our slave cloud provider which will do the following when there is no slave available for given job:

- connect to the mesos cluster as its framework
- create docker container and register to jenkins 
- let us do the required task
- kill the docker container when not needed

Is there any way the go could be extended to enable such behavior or maybe better isn't it already implemented?

Jakub

srinivas upadhya

unread,
Feb 4, 2015, 11:43:12 PM2/4/15
to go...@googlegroups.com
If you are talking about could/elastic/on-demand/auto-scaling (whatever you want to call it) agents - reference 1 & 2. There are quiet a few Go users doing this.

Jakub Veverka

unread,
Feb 5, 2015, 4:00:02 AM2/5/15
to go...@googlegroups.com
Cool do you have any reference to point me to? Thats just last thing and I wanna be sure we will not miss this feature. 

Aravind SV

unread,
Feb 5, 2015, 7:45:46 AM2/5/15
to Jakub Veverka, go...@googlegroups.com
Though some people are doing this, Go doesn't make this extremely easy to do. There's definitely more work than just using a plugin. You'll need to setup auto registration (not hard) and do idle monitoring of your Go Agents yourself, using the APIs mentioned by Srinivas. This is not totally straightforward. For instance, you will need to define the "not needed", in your last point. Is it when the job finishes, or is it after some time? What if another job needs that same container soon?

I'd definitely consider the cost of doing that, before you go down that path. The plan is for some of this to become more native to Go soon, but I felt you need to know it needs effort, as it stands right now.

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jakub Veverka

unread,
Feb 5, 2015, 10:39:12 AM2/5/15
to go...@googlegroups.com, veverk...@gmail.com
Thanks for the tips, I've missed the references in Sirnivas email... 
Would you have quick link to more details (feature that I could track, maybe assign programmer to help with) about such feature comming? 

J

Md. Ali Ejaz

unread,
Feb 11, 2015, 1:47:16 AM2/11/15
to Jakub Veverka, go...@googlegroups.com
Hi,

Currently the discussions around the elastic agents are in the very initial phase. There are no stories framed yet. We would post a thread on go-cd-dev forum for taking the discussions forward once we have some core ideas on how we would like to go ahead with this.

The go.cd roadmap page has the current roadmap. You could join on the discussions on this roadmap here. Also the issues/bugs/features currently being worked on could be tracked on the Github issues.
--
- Ali
@mdaliejaz
Reply all
Reply to author
Forward
0 new messages