Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Running Concourse CI on enterprise private cloud

ozzozz
June 28, 2016

Running Concourse CI on enterprise private cloud

There are many merits to use Concourse CI. Above all, it is important for enterprises that Concourse CI is easily runnable on their own private clouds, because they often make much of confidentiality. This talk will show you a way to run Concourse CI on private clouds, which is integrated with private Docker registry, GitHub clones, and chat apps, based on OpenStack, Docker and BOSH.

ozzozz

June 28, 2016
Tweet

More Decks by ozzozz

Other Decks in Programming

Transcript

  1. •  .PSFUIBOZFBSTXJUI+FOLJOTGPSEFWFMPQJOH BOEJOWFTUJHBUJOHBSPVOE$MPVE'PVOESZ CVUʜ •  %FQFOEJOHPOQFSTPOBMLOPXMFEHF l+FOLJOTPKJTBOzQSPCMFN  •  )BSEUPFOTVSF$*KPCEFpOJUJPOT

    UISPVHIDPEFSFWJFXT •  .BTUFSOPEFJTIBSEUPTDBMFPVU CFDBVTF BMMKPCEFpOJUJPOTBOEMPHTBSFTBWFEBTpMFT PONBTUFSOPEF`TpMFTZTUFN •  7FSZIBSEUPEFpOFKPCQJQFMJOFT 8IZ$PODPVSTF$*   
  2. •  )PXFWFS PUIFSTPMVUJPOTXFSFOPU BWBJMBCMFZFUUPEFQMPZ$*FOWTPO QSJWBUFDMPVET •  $*BTBTFSWJDF TVDIBT5SBWJT$*  BSFQVCMJDTFSWJDFTBOECBTFEPO

    NFUFSSBUFDIBSHJOH •  )BSEUPBDDFQUCFDBVTFPG DPOpEFOUJBMJUZBOECVEHFU NBOBHFNFOU 8IZ$PODPVSTF$*   
  3. •  QSJWBUF%PDLFSSFHJTUSZ •  UPJNQSPWFUIF$*TQFFE •  IBSEUPDPNNVOJDBUFXJUI%PDLFS)VCXIFO JNBHFTJ[FJTMBSHF •  NPSFF⒎FDUTXIFOQSPYZFYJTUT • 

    (JU#VDLFU •  BHPPE(JU)VCDMPOF PQFOTPVSDF •  3PDLFU$IBU •  BHPPE4MBDLDMPOF PQFOTPVSDF •  TVQQPSUTJODPNJOHXFCIPPL •  +*3" •  3VOOBCMFPOQSJWBUFDMPVETJG*CVZUIFTFSWFS MJDFOTF 8IZEP*VTFUIFN 
  4. •  1SJWBUF%PDLFSSFHJTUSZ  •  (JU#VDLFU •  3PDLFU$IBU •  TFFʜIUUQTSPDLFUDIBUEPDTJOTUBMMBUJPO EPDLFSDPOUBJOFSTEPDLFSDPNQPTF

    •  +*3" •  TFFʜIUUQTHJUIVCDPNDQUBDUJPOIBOL EPDLFSBUMBTTJBOKJSB )PXUPSVO%PDLFSDPOUBJOFST $ docker run -d -p 8080:8080 -p 29418:29418 \ -v /srv/gitbucket:/gitbucket f99aq8ove/gitbucket $ docker run -d -p 5000:5000 \ -v /srv/docker-registry:/var/lib/registry registry:2
  5. JOTJEF$PODPVSTF$*EFQMPZFECZ#04) qZ $-*  BUD UTB QPTUHSFTRM HSPVOEDSFX HBSEFOSVOD CBHHBHFDMBJN

    $PODPVSTF "1* $PODPVSTF(6* NBTUFS7. XPSLFS7. QSJWBUF SFHJTUSZ BOSH
  6. •  %FQMPZCZ#04) EFTDSJCFPOEFQMPZNFOUNBOJGFTU •  3VOXPSLFSCZTUBOEBMPOFCJOBSZ BEEBDPNNBOEMJOFPQUJPO )PXUPVTFQSJWBUF%PDLFSSFHJTUSZGSPN $PODPVSTF$* properties: garden:

    insecure_docker_registry_list: - 192.168.1.200:5000 $ sudo concourse worker --work-dir … \ --garden-insecure-docker-registry \ 192.168.1.200:5000
  7. •  %FQMPZCZ#04) EFTDSJCFPOEFQMPZNFOUNBOJGFTU •  3VOXPSLFSCZTUBOEBMPOFCJOBSZ BEEDPNNBOEMJOFPQUJPOT )PXUPSVO$PODPVSTF$*CFIJOEUIF QSPYZTFSWFS properties: http_proxy_url:

    http://192.168.1.2:8080 https_proxy_url: http://192.168.1.2:8080 no_proxy: [localhost, 192.168.1.200] $ sudo concourse worker --work-dir … \ --http-proxy http://192.168.1.2:8080 \ --https-proxy http://192.168.1.2:8080 \ --no-proxy localhost,192.168.1.200