[ad_1]
In half 1 of this weblog sequence, we overviewed the completely different instruments that might be used as you go up the stack from infrastructure to utility. On this weblog, we will likely be provisioning our Infrastructure as Code (IaC) utilizing Terraform, Ansible, Jenkins and GitHub. First, we are going to arrange our growth atmosphere with all of the instruments wanted for this deployment. Then we are going to evaluate our Terraform configuration information and Ansible playbooks intimately.
As all the time, your growth atmosphere might differ from what’s getting used on this sequence, however all of the Dev instruments we will likely be utilizing can be found on Microsoft, Mac, and Linux working methods. In our case, we will likely be utilizing Ubuntu 20.04 to run all our DevOps instruments.
We’ll deploy the most recent variations of Terraform, Ansible, AWS CLI, Docker, Jenkins and kubectl on our DevBox. Then we create a GitHub repository for supply code administration and model management of our infrastructure. We will likely be utilizing the Cloud Native Safety SPOT-ON Collection repository on this sequence. The very first thing we’re going to do is create a function department known as infra. We’re going to use function branches to merge our code into the important department, which is our manufacturing department. When modifications are made to the important department, the construct will likely be triggered by Jenkins. For every SPOT-On episode that we create, there will likely be a function department related to it. For instance, within the subsequent episode we are going to deploy our functions, so we are going to create one other function department named apps and merge into important.
Video demo for “Organising the Dev Atmosphere”
Within the subsequent part we may have an in depth take a look at the set up. I’ve additionally created a demo video for these of you preferring to look at as a substitute of learn. For individuals who choose my detailed written directions, you’ll discover them under. Additionally, don’t fear, this isn’t the final episode within the sequence! Subsequent up, we are going to use GitOps and CI/CD to construct and deploy the cloud infrastructure. For now, right here’s my demo video for this Half 2:
Cisco Safe Cloud Native Safety – Half 2.1 – Organising the Dev Atmosphere
Detailed Directions
In case you are studying this, it means you have an interest to study the main points of this arrange. Let’s leap proper in! First, allow us to take a look at Jenkins. We’ll create a multibranch pipeline named Spot On. We’ll use the Cloud Native Safety SPOT ON Collection as our Department Supply and can uncover all branches.
The Construct Configuration will likely be outlined by the Jenkinsfile. The Jenkinsfile is the directions of the pipeline itself. We’ll dive deeper into the Jenkinsfile within the subsequent part.
After we save the pipeline job, Jenkins will scan the GitHub repository and discover the branches we created. When a construct is run it’ll pull down the code from this repository.
Now that we’ve our pipeline built-in with our supply code repository, allow us to take a look at the infrastructure as code. Wanting on the construction of our infra department we see a Jenkinsfile, which is our Pipeline as Code. We additionally see Terraform information important.tf, output.tf, and variables.tf. These Terraform configuration information are set on the root of the venture, known as the Root Module. There may be additionally a modules/infra listing which additionally has a bunch of Terraform information. This module listing comprises the code that can provision the infrastructure.
Like we mentioned beforehand, the Jenkinsfile is our Pipeline as Code and supplies all of the directions for constructing our pipeline. Wanting on the Jenkinsfile first we outline the pipeline brokers. On this case we’re simply utilizing the Jenkins grasp, however we might have an outlined agent for every stage if we want. Subsequent, we set the atmosphere variables. Right here we set the atmosphere identify and ID, the AWS entry and secret keys, in addition to the area, availability zones, SSH key and FTD credentials.
As you possibly can see a few of these variables are outlined right here on the Jenkinsfile, however a number of the variables are referencing the syntax credentials(). Jenkins’ declarative Pipeline makes use of this helper methodology which helps secret textual content, username, and password, in addition to secret file credentials. We set these variables in Jenkins on the Handle Jenkins > Handle Credentials web page. This fashion we are able to go these secret variables to Terraform securely.
The subsequent part of the Jenkinsfile is the place our levels are outlined. For proper now, we solely have one stage which is Construct Atmosphere. Inside every stage we’ve a number of steps. Step one is simply echoing Constructing Atmosphere on the construct output. The second step will likely be a terraform get –replace, which is used to replace any new Terraform suppliers added to the venture. The third step will initialize all of the suppliers configured within the venture. The fourth step will apply the Terraform configuration passing all of the variables wanted to provision the atmosphere.
Allow us to take a look at the Terraform configuration information. The primary file to dive into is important.tf. This file is about on the root of the venture, which means it’s within the root module. On this file we outline one other module named Infrastructure which is sourced from ./modules/infra. You may consider a module as a operate in different programming languages. On this case we create a module to deploy our infrastructure and go the mandatory atmosphere variables to this module. Why would we do that? For instance, let’s say we’ve a number of environments, similar to Dev, Check, QA, and Prod. We would like the deploy every atmosphere with the identical actual assets, however the atmosphere variables similar to IP addresses, subnets, areas, and zones needs to be completely different. We additionally set our Terraform Suppliers right here in important.tf.
There may be additionally a variables.tf file positioned within the root module. These are the identical variables we’re passing from Jenkins as proven above, we’re simply declaring them in Terraform.
Then we’ve the modules/infra listing which is the place the infrastructure module config information are positioned. On this listing we see one other important.tf and variables.tf information. This will likely appear redundant however consider this like how we set international variables and native variables in different programming languages. On this case we’re defining variables within the root module and passing them to the infra module, which might be the identical as declaring variables globally and passing them variables as arguments to the operate.
There are additionally configuration information for the vpc.tf, ftdv.tf, and eks.tf. Every one in every of these information provisions their respective configurations. We might put all these configurations into one file however breaking it up makes it simpler to learn and extra modular. There may be additionally a file named ftdv_ansible_deploy.tf. We use this Terraform configuration file to run our Ansible playbooks in a Docker container. These Ansible playbooks are used to configure the Safe Firewall coverage we’ve deployed on one in every of our EC2 cases.
Keep tuned
Within the subsequent episode of this sequence, we are going to use GitOps and CI/CD to construct and deploy the cloud infrastructure. Hope to see you again once more!
Please let me know you probably have any questions, both within the “feedback” part under, or by way of the GitHub points.
We’d love to listen to what you suppose. Ask a query or depart a remark under.
And keep related with Cisco DevNet on social!
LinkedIn | Twitter @CiscoDevNet | Fb | Developer Video Channel
Share:
[ad_2]
