Skip to main content

Posts

Showing posts with the label automation

Creating a pipeline in GoCD

If you haven’t installed GoCD yet, you can follow the  GoCD Installation Guide  to install the GoCD Server and at least one GoCD Agent. This is a good point to stop and learn about the first concept in GoCD. Concept 1: Server and agents In the GoCD ecosystem, the server is the one that controls everything. It provides the user interface to users of the system and provides work for the agents to do. The agents are the ones that do any work (run commands, do deployments, etc) that is configured by the users or administrators of the system. The server does not do any user-specified “work” on its own. It will not run any commands or do deployments. That is the reason you need a GoCD Server and at least one GoCD Agent installed before you proceed. Once you have them installed and running, you should see a screen similar to this, if you navigate to the home page in a web browser (defaults to:  http://localhost:8153 ): GoCD’s new pipeline page If you have installed t...

Creating a pipeline in GoCD

If you haven't installed GoCD yet, you can follow the  GoCD Installation Guide  to install the GoCD Server and at least one GoCD Agent. This is a good point to stop and learn about the first concept in GoCD. Concept 1: Server and agents In the GoCD ecosystem, the server is the one that controls everything. It provides the user interface to users of the system and provides work for the agents to do. The agents are the ones that do any work (run commands, do deployments, etc) that is configured by the users or administrators of the system. The server does not do any user-specified "work" on its own. It will not run any commands or do deployments. That is the reason you need a GoCD Server and at least one GoCD Agent installed before you proceed. Once you have them installed and running, you should see a screen similar to this, if you navigate to the home page in a web browser (defaults to:  http://localhost:8153 ): GoCD's new pipeline page If you have installed the GoCD ...

Cronjob

This documents gives details about the cronjob run options: This field follows the syntax of cron (with minor differences). Specifically, each line consists of 5 fields separated by TAB or whitespace: MINUTE HOUR DOM MONTH DOW MINUTE Minutes within the hour (0–59) HOUR The hour of the day (0–23) DOM The day of the month (1–31) MONTH The month (1–12) DOW The day of the week (0–7) where 0 and 7 are Sunday. To specify multiple values for one field, the following operators are available. In the order of precedence, *  specifies all valid values M-N  specifies a range of values M-N/X  or  */X  steps by intervals of X through the specified range or whole valid range A,B,...,Z  enumerates multiple values To allow periodically scheduled tasks to produce even load on the system, the symbol  H  (for “hash”) should be used wherever possible. For example, using  0 0 * * *  for a dozen daily jobs will cause a large spike at midn...

Docker tutum

Tutum is a platform to provide docker container as a service - cloud. Its equivalent docker universal control plane- on premise. n tutum you BYON and then tutum takes care of plumbing. Available in API,GUI,CLI. If there is any change in git repo code then tutum will automatically redeploy. in the node builder all the builds will occur if do not name a node as builder then all the build will occur on a node that has least amount of containers. All the repository build will happen inside tutum builder. Tutum has its own yaml file tutum.yml similar to docker-compose.yml. You can add a load balancer haproxy which is out-of-box which will automatically scale the application as per the requests. You can add the tags (tags are branches of git where you want to build) only the branches specified in the tag will be built for deployment. Tutum yaml is used when we create a stack in tutum. autoredploy: true

Terraform

Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. Configuration files describe to Terraform the components needed to run a single application or your entire datacenter. Terraform generates an execution plan describing what it will do to reach the desired state, and then executes it to build the described infrastructure. As the configuration changes, Terraform is able to determine what changed and create incremental execution plans which can be applied. The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS entries, SaaS features, etc. The key features of Terraform are: Infrastructure as Code : Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and...