Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 17 2019 21:49

    tomzo on master

    release 0.13.0 (compare)

  • Jan 17 2019 21:49

    tomzo on 0.13.0

    release 0.13.0 (compare)

  • Jan 07 2019 05:20
  • Nov 23 2018 20:27
    tomzo commented #18
  • Nov 20 2018 18:13
    chrislovsund commented #18
  • Nov 20 2018 18:13
    chrislovsund commented #18
  • Nov 20 2018 18:13
    chrislovsund commented #18
  • Nov 20 2018 12:37
    tomzo opened #18
  • Aug 30 2018 07:34
    tomzo commented #17
  • Aug 30 2018 07:34

    tomzo on master

    Fix issue which caused the cach… Merge pull request #17 from chr… (compare)

  • Aug 30 2018 07:34
    tomzo closed #17
  • Aug 29 2018 11:04
    gocd-cla-bot commented #17
  • Aug 29 2018 11:01
    gocd-cla-bot commented #17
  • Aug 29 2018 11:01
    chrislovsund opened #17
  • Jul 12 2018 08:32
    tomzo closed #15
  • Jul 12 2018 08:32
    tomzo commented #15
  • Jul 12 2018 08:28

    tomzo on master

    release 0.12.0 (compare)

  • Jul 12 2018 08:28

    tomzo on 0.12.0

    release 0.12.0 (compare)

  • Jul 12 2018 08:18
    tomzo commented #16
  • Jul 12 2018 08:17

    tomzo on master

    Fix for #15 that will log ERROR… Merge pull request #16 from chr… (compare)

poppy
@poppy62313111_twitter
@arvindsv Ok, we are now getting Could not find file `config/agent-launcher-logback.xml'. Attempting to load from classpath.
could this be a version missmatch?
Aravind SV
@arvindsv
@poppy62313111_twitter Is the next line: Using classpath resourcejar:file:/path/to.../data/deps-446f4ccd1d026917-agent-launcher.jar/agent-launcher-18.7.0-25826-classes.jar!/config/agent-launcher-logback.xml’.` ?
If so, you’re ok. It’s just a warning that it couldn’t find it in the first place it looked.
If it stopped logging after that, it’s probably logging into the logs/ directory.
poppy
@poppy62313111_twitter
k
let me ask my team member
Aravind SV
@arvindsv
You might want to ask in the gocd/gocd channel instead of here. Others might be able to help there.
poppy
@poppy62313111_twitter
cool.. can i ask you one more dumb question
this field
GO_EA_AUTO_REGISTER_ELASTIC_AGENT_ID=
we are stating like this GO_EA_AUTO_REGISTER_ELASTIC_AGENT_ID=elastic-agent1
Aravind SV
@arvindsv
The docker (or docker-swarm) plugins automatically start the elastic agent (using the specified docker image). You shouldn’t need to start it yourself.
poppy
@poppy62313111_twitter
ok.. we are just using the docker not the swarm plugin... cool
Aravind SV
@arvindsv
Basically you configure the plugin and tell it where your docker host is. Then, you can configure an elastic agent profile, to tell it which image to use.
poppy
@poppy62313111_twitter
ok
Aravind SV
@arvindsv
When needed, it’ll start a docker container with those values.
When not needed (when job is finished), it’ll stop the container.
I think this can benefit from a video or a better walkthrough. I’ll see if I can add it or ask someone to.
poppy
@poppy62313111_twitter
dude that will be rad
and just to double check in our yaml file that will create a pipeline, we are referencing the agent like this by, its profileid name
    elastic_profile_id:
      - yomta_test_EA
    environment_variables:
Aravind SV
@arvindsv
That should be right. In that elastic profile, you’ll configure it to use an image which works with elastic agents. Like the official one on dockerhub. Start with that and get a "hello world” going first. Make sure you understand how it works - when the pipeline starts and the job in it starts, it should automatically bring up a docker container with the configured docker image and then run the job. Once done, the container should go away.
mpadilla1
@mpadilla1
The container comes up ok and the agent registers with our go instance, but never gets assigned to the job, just sits idle at that point.
Ketan Padegaonkar
@ketan
@tomzo @barrowkwan — I’ve listed the openstack plugin on the gocd plugins page (https://gocd.org/plugins) should be published in a few minutes from now
poppy
@poppy62313111_twitter
Hey guys, how do you configure the go-elastic agent to run docker in docker?
poppy
@poppy62313111_twitter
we need to pass this
docker run -it -v /var/run/docker.sock:/var/run/docker.sock docker:dind sh
do we add this under the Docker Command: (Enter one parameter per line) section of the configuration page?
Mahesh Panchaksharaiah
@maheshp
@tomzo @barrowkwan I have sent a PR gocd-contrib/openstack-elastic-agent#19 to change the Request Processors API version. This is required after changes to GoCD core gocd/gocd#5654. Can you guys please take a look.
NikoHeikki
@NikoHeikki
Hello! I deployed Gocd Kubernetes version to Openshift okd using helm, it automatically added cluster profile configuration but It doesn't seem to connect to my cluster. What service account token it wants and how much permissions it needs? Does the token matter if it has enough permissions?
chinmaya korlepara
@chinmayakcv_twitter
Hello, I have a noob question. I installed gocd agents in aws ec2 instance using docker. I understood by using elastic agent I can automate creation & deletion of agents but how can I autoscale ec2 instances & their configuration?
Ketan Padegaonkar
@ketan
@chinmayakcv_twitter: you'd need the (commercial) ECS plugin: https://extensions-docs.gocd.org/ecs/current/
chinmaya korlepara
@chinmayakcv_twitter
@ketan Thanks :)
Christian Lövsund
@chrislovsund
I would like to check when the elastic agent is low on diskspace and retire the agent instance based on that. Looking at the https://plugin-api.gocd.org/19.5.0/elastic-agents I can not see a way to get free diskspace as presented in the GoCD server’s agent page. Does anyone know how to get that data in the plugin?
Tomasz Sętkowski
@tomzo
@chrislovsund that information could be obtained via HTTP API. But as far as I know there is no way to call the API from plugins at the moment.
But for the case you mention, perhaps a free_space field could be added to all the data which gocd server presents to the plugin (along the current status of agent and its job).
I mean, it could be added in AgentMetadata
Christian Lövsund
@chrislovsund
Yes, that would be very useful.
Christian Lövsund
@chrislovsund
@tomzo Any idea how I increase the likelihood of that change being implemented? Pull request?
Aravind SV
@arvindsv
@chrislovsund Can openstack itself be interrogated to find that value? If not, yeah, will need to get it somehow. One option could be to talk to the server through the API: https://api.gocd.org/current/#get-one-agent — but it’ll still need authentication.
Tomasz Sętkowski
@tomzo
It cannot, its a value known to OS kernel only.
Aravind SV
@arvindsv
I see. Ok.
Tomasz Sętkowski
@tomzo
I really think its viable to add it in the agent metadata along the status values
I guess this information could be leveraged by any elastic plugin
It makes sense to disable and delete agents once they are full.
And calling the API from within the plugin is just hacky
Christian Lövsund
@chrislovsund
I agree with @tomzo.
Aravind SV
@arvindsv

And calling the API from within the plugin is just hacky

Yes, I agree.

Ketan Padegaonkar
@ketan
I think it should be reasonable to expose (some of) the data available in the agents api to plugins. @chrislovsund: a PR would be most welcome, but if you could open an issue on gocd, we can take the conversation there.