Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CGCP] Onboard UCI components to DevOps system #32

Open
13 tasks
karntrehan opened this issue Apr 10, 2023 · 3 comments
Open
13 tasks

[CGCP] Onboard UCI components to DevOps system #32

karntrehan opened this issue Apr 10, 2023 · 3 comments

Comments

@karntrehan
Copy link
Contributor

karntrehan commented Apr 10, 2023

Onboard UCI to https://github.com/Samagra-Development/Samagra-DevOps-Guide

  • outbound
  • inbound
  • transformer
  • orchestrator
  • broadcast-transformer
  • dao
  • adapter
  • message-rosa
  • utils
  • uci-apis
  • transport-socket
  • uci-web-channel
  • uci-admin

Project

UCI

Organization Name:

Samagra

Domain

Communications

Tech Skills Needed:

Docker, Jenkins

Mentor(s)

@tushar5526

Complexity

Medium

Category

Feature

Sub Category

CI/CD, Docker, Jenkins, Deployment

@tushar5526
Copy link
Collaborator

tushar5526 commented Jun 20, 2023

Current shortcomings

  • Few services need custom configs to be mounted from a certain dir of server. This problem is supposed to be covered in c4gt. Possible solutions are to build temporary images before deployment and mount the config there or to copy configs on all slave nodes.
  • Depends on .env refactoring and clean up  #33 to clean up .env and separate environment variables

Benefits

  • Common deployment strategy for both dev and staging. We can also add a QA environment later when needed easily.
  • Continuous deployment on staging through GitHub events and prod release can be controlled through Jenkins using tags.
  • No need for devs to do anything on the server directly. There only point of contact is Jenkins

Time estimates

  • It will require around 1 - 2 days to close .env refactoring and clean up  #33 with support of UCI devs
  • Approx 2-3.5 days to onboard all services and test them. This includes configuring Github hooks as well for dev.
  • Data migration for dev servers should take 0.5 - 1 day and then test them.
  • Data does not needs to be migrated for prod as it is already setup for Docker swarm deployments.
  • 0.5 days for testing and KT with devs on the pipeline.

NOTE: Time estimates based on I focus primarily on docker-deploy.

@chinmoy12c chinmoy12c changed the title Onboard UCI components to DevOps system [CGCP] Onboard UCI components to DevOps system Jun 20, 2023
@aryasoni98
Copy link

I would like to work on it

@c4gt-community-support
Copy link

Hi!
Mandatory Details - The following details essential to submit tickets to C4GT Community Program are missing. Please add them!

  • Product Name - (Missing/Misspelled)

Without these details, the ticket cannot be listed on the C4GT Community Listing.

Important Details - These following details are helpful for contributors to effectively identify and contribute to tickets.

Please update the ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants