Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 01 11:37
    vovinski commented #637
  • Dec 01 11:37
    vovinski commented #637
  • Nov 30 23:00
    dawnerd opened #648
  • Nov 17 20:22
    daliborfilus commented #554
  • Nov 17 20:21
    daliborfilus commented #554
  • Nov 04 13:36
    neeweesomu commented #647
  • Nov 04 13:36
    neeweesomu commented #647
  • Nov 04 13:35
    neeweesomu commented #647
  • Nov 03 13:06
    neeweesomu reopened #647
  • Nov 03 12:50
    neeweesomu edited #647
  • Nov 03 12:46
    neeweesomu closed #647
  • Nov 03 12:46
    neeweesomu commented #647
  • Nov 03 12:26
    neeweesomu edited #647
  • Nov 03 12:26
    neeweesomu edited #647
  • Nov 03 12:24
    neeweesomu edited #647
  • Nov 03 12:23
    neeweesomu edited #647
  • Nov 03 12:23
    neeweesomu edited #647
  • Nov 03 12:22
    neeweesomu opened #647
  • Oct 29 15:10
    eramosr22 commented #607
  • Oct 29 15:08
    eramosr22 commented #607
Chase Pierce
@syntaqx
To know which version is "ready for production" - That happens on build - The image is tagged, Circle can deploy it. Then, for DR , we use GitHub's API to determine what the latest tag is
lumir-mrkva
@lumir-mrkva
@syntaqx have you considered to also tag images for environments (eg. dev, test, production )? then swarmpit would simply keep tagged image on its environment up to date
Chase Pierce
@syntaqx
The problem is we have multiple images in production/staging sometimes though
That's why that doesn't work
A simple example of when this is the case is if we're doing a partial rollout (ie, 10% of users) to see how well a new feature works. - We use multiple version hashes to do this
lumir-mrkva
@lumir-mrkva
so in that case you have basically 2 environments deployed in production?
Chase Pierce
@syntaqx
Indeed
Plus, if you use the same tag for prod, you can't do rollbacks?
lumir-mrkva
@lumir-mrkva
not really
Chase Pierce
@syntaqx
So yeah, that's not ideal, haha
lumir-mrkva
@lumir-mrkva
you would have to tag earlier image as "production"
if you want to trigger deploy on circle ci or any other change in your swarm, you can use swarmpit api
Chase Pierce
@syntaqx
Example? I haven't seen this. Is there docs?
lumir-mrkva
@lumir-mrkva
we don't have really a documentation yet for that, but you can get api token in account settings
just inspect for XHR that frontend does with your change, and you can export it to curl
and change it to your liking
Chase Pierce
@syntaqx
:wave: How goes it friends?
Pavol Noha
@nohaapav
all good man :)
Chase Pierce
@syntaqx
Are you guys using datadog agent by chance to collect logs in your swarms?
I'm trying to figure out what I need to configure for my services to show up correctly
Chase Pierce
@syntaqx
@nohaapav Any update on the terraform provider/api docs? :)
Pavol Noha
@nohaapav
not really ... busy with other work :) We're not using datadog in current setup ..
Chase Pierce
@syntaqx
FeelsBad. Hoping you guys will release stuff soon :(
Any way I can help? :)
Pavol Noha
@nohaapav
Nothing on my mind apart of 1.7 release .. But again clojure knowledge is a must .. :)
Chase Pierce
@syntaqx
I'm slowly learning it ;)
Chase Pierce
@syntaqx
@nohaapav How goes development of the various things? Terraform provider, api docs, general happiness I can start using? :)
Pavol Noha
@nohaapav
Finalizing release .. not really time for terraform .. api doc will be probably done in 1.8 (we're going to integrate swagger but first we need to introduce reitit instead of bidi routing)
Chase Pierce
@syntaqx
I suppose that's fair, hah
Ghost
@ghost~530e888d5e986b0712efbd49
I need some help with understanding how the auto redeploy works.
I cant seem to find any documentation for swarmpit
Pavol Noha
@nohaapav
If new image is pushed in registry, swarmpit update the service with force flag accordingly -> new image is used instead of old one ..
Ghost
@ghost~530e888d5e986b0712efbd49
how is it detecting which version to update to?
i have app:dev-1.0.0
does that mean if I push app:dev-1.0.1 it will use that next?
Chase Pierce
@syntaqx
@bludot It watches for when a tag gets overwritten, ie, image:latest. When something overwrites that, it redeploys it - Swarmpit doesn't leverage versions, so you also lose rollbacks by using this
Ghost
@ghost~530e888d5e986b0712efbd49
ah ok ok. so always use latest
Chase Pierce
@syntaqx
Just whatever tag you deploy is the one it's going to watch
Pavol Noha
@nohaapav
exactly
Ghost
@ghost~530e888d5e986b0712efbd49
thank you
Chase Pierce
@syntaqx
How goes things in delivery world? Are we getting any closer to having some of that new hotness terraform and such?
Pavol Noha
@nohaapav
Hi Chase, not really .. we're working on time series monitoring and alerts, dashboards & autoscalling ..
Chase Pierce
@syntaqx
:cry:
rwestbrookjr
@rwestbrookjr
Is anyone online?
godavarthiashok
@godavarthiashok
Hi Everyone
Regarding swarmpit, how does load balancing works in Swarmpit ,
Should we mention each port for each replica in docker compose yml or mentioning a single port will also help , please suggest.
Pavol Noha
@nohaapav
@godavarthiashok Hi, sorry .. we had vacation recently and our sync agent with gitter went down ..
You should always have just one replica of swarmpit ..
Swarmpit is management tool so short outage is ok .. Swarm is going to redeploy new instance almost immediately because of default restart policy ..