Answers: <p>here are my 2 cents,</p>
  
  <ol>
  <li><p>You can use GITLAB to have merge requests for all your security requests like adding users to the groups for every new user or existing users. the Mr can be approved by only your IAM admin. You can use GITLAB CI pipelines to go and perform the operation once the MR is approved. From the users side, the user has to  provide their keys and submit as an MR so that the IAM team can validate and approve it. </p></li>
  <li><p>You can deploy your applications easily using Ansible and Gitlab CI. All you need is just source code of your application and some knowledge of YAML. I am sure, your folks already are equipped with that. Ansible can be used for infra provisioning as well so you can just run the show with them. With regards to os updates, I would say ansible can easily do it. Have the SDLC workflow in place for developing playbooks and once the playbook is modularized, it can used in production. </p></li>
  </ol>
  
  <p>Let me know if I answered your query and if you have any other questions.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-05-07T21:09:02.730Z
Answers: Thanks for the input @Sreekar.  I appreciate the detail.  Based on you comments, I'd like to ask you what is your team doing in this regard?
Answers: ddarling
Answers: CC BY-SA 4.0
Answers: 2020-05-20T06:46:10.937Z
Answers: Well, I have illustrated what we are doing here only :) However we don't have any separate roles like IAM admin, etc. Also, we have used terraform for infra provisioning as we felt its win over ansible with regards to the TF state file. It was concluded to use terraform after many calculations. I haven't suggested you because you specifically asked for ansible. If you have a choice, I suggest to go with terraform for infra provisioning.
Answers: Sreekar
Answers: CC BY-SA 4.0
Answers: 2020-04-21T09:41:05.347Z
Answers: 2020-04-21T09:41:05.347Z
Answers: Sreekar
Answers: <p>You have a lot of ways to automatize you infrastructure. For your pipelines you can use a tool for this like Jenkins, Travis CI, GitLab, Concourse CI, Drone IO and through turn better CI/CD for your developer.</p>
  
  <p>From the perspective of automating the infra, you can use Terraform to raise it, manage to maintain the default using Ansible and to handle jobs you can use Rundeck.</p>
  
  <p>But the more important it's you plan how to you link these tools.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-01-16T15:21:25.147Z
Answers: Thank you for your input. The desire is to utilize GitLab and Ansible as much as possible. It's nice to know that there are real options for told as well.
Answers: ddarling
Answers: CC BY-SA 4.0
Answers: 2020-01-16T18:26:35.957Z
Answers: @ddarling GitLab have a tools for CI/CD, sincerely I never used, but see a lot of professionals talking good about them.
Answers: Vader
Answers: CC BY-SA 4.0
Answers: 2020-01-13T23:40:17.330Z
Answers: 2020-01-13T23:40:17.330Z
Answers: Vader
Body: <p>I am looking to validate the use of devops for a team of seven people, each having a specific function. </p>
  
  <p>1 Java Developer<br>
  1 System Administrator<br>
  1 Team Lead/Project Manager<br>
  1 Identity Management Admin<br>
  2 Access Management Admin<br>
  1 PKI Registration Agent  </p>
  
  <p>We have different workflows for each function. However, from my perspective, it's all the same. New ideas or requirements bring about new or changes to code, which initiates the workflow.  To me, application updates, OS patching, and innovation are all the same. Could CI/CD pipelines be created to standardize infrastructure security and configuration as well as enable a faster and more feature tuned application release cycle?  Any input would be most appreciated. </p>
  
  <p>-Darryl</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-01-15T09:50:56.267Z
Comments: Hi and welcome to DevOps.SE. DevOps is merely a flowery (but to-the-point) term for automating infrastructure tasks surrounding development and operation of (software) services. I think you're right to see those commonalities, but I'd argue that doesn't equate to a "one size fits all" model but rather that the same or similar tools can be used to facilitate the workflows you identified. I for one would not automate all aspects of application updates the same as OS patches (think human approval in the process). But a question: are those roles or 1:1 matches of roles:people?
Comments: 0xC0000022L
Comments: CC BY-SA 4.0
Comments: 2020-01-16T15:12:26.307Z
Comments: Thanks for the engagement. Yes the number next to the role of the number of individuals in that role. I appreciate your comment concerning approvals. That is an important thing to remember.
Comments: ddarling
Tags: <automation><infrastructure-as-code><workflow>
Title: Infrastructure Automation with GitLab
UserDisplayName: ddarling
ThreadText: # Infrastructure Automation with GitLab
  
  (Asked by: username_0 on 2020-01-10)
  
  I am looking to validate the use of devops for a team of seven people, each having a specific function.
  
  1 Java Developer  
  1 System Administrator  
  1 Team Lead/Project Manager  
  1 Identity Management Admin  
  2 Access Management Admin  
  1 PKI Registration Agent
  
  We have different workflows for each function. However, from my perspective, it's all the same. New ideas or requirements bring about new or changes to code, which initiates the workflow. To me, application updates, OS patching, and innovation are all the same. Could CI/CD pipelines be created to standardize infrastructure security and configuration as well as enable a faster and more feature tuned application release cycle? Any input would be most appreciated.
  
  -Darryl
  
  **Tags:** automation, infrastructure-as-code, workflow
  
  > **Comments:**
  > **username_1**: Hi and welcome to DevOps.SE. DevOps is merely a flowery (but to-the-point) term for automating infrastructure tasks surrounding development and operation of (software) services. I think you're right to see those commonalities, but I'd argue that doesn't equate to a "one size fits all" model but rather that the same or similar tools can be used to facilitate the workflows you identified. I for one would not automate all aspects of application updates the same as OS patches (think human approval in the process). But a question: are those roles or 1:1 matches of roles:people?  
  > **username_0**: Thanks for the engagement. Yes the number next to the role of the number of individuals in that role. I appreciate your comment concerning approvals. That is an important thing to remember.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2020-04-21. Score: 2
  
  here are my 2 cents,
  
  1. You can use GITLAB to have merge requests for all your security requests like adding users to the groups for every new user or existing users. the Mr can be approved by only your IAM admin. You can use GITLAB CI pipelines to go and perform the operation once the MR is approved. From the users side, the user has to provide their keys and submit as an MR so that the IAM team can validate and approve it.
  2. You can deploy your applications easily using Ansible and Gitlab CI. All you need is just source code of your application and some knowledge of YAML. I am sure, your folks already are equipped with that. Ansible can be used for infra provisioning as well so you can just run the show with them. With regards to os updates, I would say ansible can easily do it. Have the SDLC workflow in place for developing playbooks and once the playbook is modularized, it can used in production.
  
  Let me know if I answered your query and if you have any other questions.
  
  > **Comments:**
  > **username_0**: Thanks for the input @username_2.  I appreciate the detail.  Based on you comments, I'd like to ask you what is your team doing in this regard?  
  > **username_2**: Well, I have illustrated what we are doing here only :) However we don't have any separate roles like IAM admin, etc. Also, we have used terraform for infra provisioning as we felt its win over ansible with regards to the TF state file. It was concluded to use terraform after many calculations. I haven't suggested you because you specifically asked for ansible. If you have a choice, I suggest to go with terraform for infra provisioning.  
  
  ---
  
  ### Answer by username_3 on 2020-01-13. Score: 1
  
  You have a lot of ways to automatize you infrastructure. For your pipelines you can use a tool for this like Jenkins, Travis CI, GitLab, Concourse CI, Drone IO and through turn better CI/CD for your developer.
  
  From the perspective of automating the infra, you can use Terraform to raise it, manage to maintain the default using Ansible and to handle jobs you can use Rundeck.
  
  But the more important it's you plan how to you link these tools.
  
  > **Comments:**
  > **username_0**: Thank you for your input. The desire is to utilize GitLab and Ansible as much as possible. It's nice to know that there are real options for told as well.  
  > **username_3**: @username_0 GitLab have a tools for CI/CD, sincerely I never used, but see a lot of professionals talking good about them.  
  
  ---
  
  