Are AWS/Azure cloud based jobs like system support jobs?
Almost all the cloud jobs description mentions an on-call rotation work. It is true even for roles like cloud developers, cloud architects and solution architect, not just DevOps, SysOps or SREs. **Is there any cloud job for someone who prefers only day-time work?** As a software developer in a core tech company, I get it that it depends a lot on the team and the project. However, the jobs description doesn't say it depends on the team and even for a company like Google and Amazon, the job descriptions of a cloud based role expects on-call rotation support work. Why do AWS/Azure cloud job responsibilities make them like system support jobs?
https://redd.it/erjvto
@r_devops
Almost all the cloud jobs description mentions an on-call rotation work. It is true even for roles like cloud developers, cloud architects and solution architect, not just DevOps, SysOps or SREs. **Is there any cloud job for someone who prefers only day-time work?** As a software developer in a core tech company, I get it that it depends a lot on the team and the project. However, the jobs description doesn't say it depends on the team and even for a company like Google and Amazon, the job descriptions of a cloud based role expects on-call rotation support work. Why do AWS/Azure cloud job responsibilities make them like system support jobs?
https://redd.it/erjvto
@r_devops
reddit
Are AWS/Azure cloud based jobs like system support jobs?
Almost all the cloud jobs description mentions an on-call rotation work. It is true even for roles like cloud developers, cloud architects and...
Survey results: API support options
Hi everyone,
Thank you to all of you who answered my short survey about where you like to go to get help when you have a question about using APIs. I have closed the survey and wanted to share the results with you. There were five questions and 46 respondents and the results are below.
Hope you find it interesting and thanks again. You are all rockstars! :)
# Question 1: Are you (or do you consider yourself) a developer? If not, what is your role.
Yes = 67.4%
No = 32.6 %
Other roles
* Product manager
* Developer for many years, now domain architect
* Cognitive scientist
* SRE
* Network Administrator
* SQA Test
* Sysadmin
* DevOps
* System Admin
* Infrastructure Engineer
* SysEng/SRE
* Growth
* Project Manager
* Implementation consultant
# Question 2: What level of expertise and experience do you have with APIs?
Beginner = 15.2%
Intermediate = 45.7%
Expert = 39.1%
Question 3: Thinking generally about all of the APIs you use, what are the ways you prefer to get help when you have an API-related question? Please select all that apply.
Twitter = 0.6%
Stack Overflow = 16.1%
Ask the community = 7.5%
FAQs/Knowledge Base = 14.9%
API documentation = 28%
Tutorials = 8.7%
Use cases/Partner showcases = 5%
Open a support ticket = 4.3%
GitHub = 11.8%
Other = 3.1% (Google (x2), read the server implementation, curl is your friend as is python & selenium,“ Look for an experienced SME in the vendor organization or LinkedIn. Had a number of projects on REST APIs and some Security APIs lately... ”)
# Question 4: In your opinion, what is the most important aspect of API support? To put it another way, what makes you smile and what makes you frown when thinking about getting help with APIs?
• Short, clear and to the point info that can be search in an efficient way
• Well organized documentation and overall the API is easy to use
• Examples with expected return data and common error codes.
• Great documentation with example calls/responses
• "Good documentation. I shouldn't have to be contacting the developers directly in 99 percent of cases. The API should be well documented with example requests and responses and well tested so when I follow the docs, it works the same way that the examples do.
• What annoys me is when I follow the docs but they are out of date or incomplete and then I have to scour the internet figuring out how to make the API work as intended."
• "Documentation must be complete, accurate, and up to date. This includes both endpoint-specific docs and tutorials/how-tos for implementing common workflows.
• The API design itself should be consistent such that as a developer becomes familiar with the naming conventions etc, it becomes possible to predict how another endpoint can be used. In the same vein, web APIs should follow available standards instead of inventing new ones."
• Documentation
• Docs. I don't want Twitter. I don't want to talk to someone. I don't want a "reach out." I don't want whitepapers full of marketing fluff. I want docs that don't suck.
• I like a sandbox that will help me build the API with a GUI or CLI interface.
• What make me smile/frown is reading through every product API documentation I tested with no standard tool specified.
• "Clear documentation of all aspects the API as well as code samples/tutorials documenting best practice ways of accessing/consuming them are the best. Ideally it should be autogenerated from code comments so I can be sure it is up to date with the latest version of code.
• If I have to interact with somebody to use the API then things have gone wrong. Documentation should not come from social media and should not rely on other users to help with tricky bits. If users are constantly asking the same questions in support forums for things that seem as though they should be simple, you have a problem (looking at you Telerik)"
• Good written documentation with examples
• If you have good documentation why do I need support?
• Thorough documentation, API explorer usual
Hi everyone,
Thank you to all of you who answered my short survey about where you like to go to get help when you have a question about using APIs. I have closed the survey and wanted to share the results with you. There were five questions and 46 respondents and the results are below.
Hope you find it interesting and thanks again. You are all rockstars! :)
# Question 1: Are you (or do you consider yourself) a developer? If not, what is your role.
Yes = 67.4%
No = 32.6 %
Other roles
* Product manager
* Developer for many years, now domain architect
* Cognitive scientist
* SRE
* Network Administrator
* SQA Test
* Sysadmin
* DevOps
* System Admin
* Infrastructure Engineer
* SysEng/SRE
* Growth
* Project Manager
* Implementation consultant
# Question 2: What level of expertise and experience do you have with APIs?
Beginner = 15.2%
Intermediate = 45.7%
Expert = 39.1%
Question 3: Thinking generally about all of the APIs you use, what are the ways you prefer to get help when you have an API-related question? Please select all that apply.
Twitter = 0.6%
Stack Overflow = 16.1%
Ask the community = 7.5%
FAQs/Knowledge Base = 14.9%
API documentation = 28%
Tutorials = 8.7%
Use cases/Partner showcases = 5%
Open a support ticket = 4.3%
GitHub = 11.8%
Other = 3.1% (Google (x2), read the server implementation, curl is your friend as is python & selenium,“ Look for an experienced SME in the vendor organization or LinkedIn. Had a number of projects on REST APIs and some Security APIs lately... ”)
# Question 4: In your opinion, what is the most important aspect of API support? To put it another way, what makes you smile and what makes you frown when thinking about getting help with APIs?
• Short, clear and to the point info that can be search in an efficient way
• Well organized documentation and overall the API is easy to use
• Examples with expected return data and common error codes.
• Great documentation with example calls/responses
• "Good documentation. I shouldn't have to be contacting the developers directly in 99 percent of cases. The API should be well documented with example requests and responses and well tested so when I follow the docs, it works the same way that the examples do.
• What annoys me is when I follow the docs but they are out of date or incomplete and then I have to scour the internet figuring out how to make the API work as intended."
• "Documentation must be complete, accurate, and up to date. This includes both endpoint-specific docs and tutorials/how-tos for implementing common workflows.
• The API design itself should be consistent such that as a developer becomes familiar with the naming conventions etc, it becomes possible to predict how another endpoint can be used. In the same vein, web APIs should follow available standards instead of inventing new ones."
• Documentation
• Docs. I don't want Twitter. I don't want to talk to someone. I don't want a "reach out." I don't want whitepapers full of marketing fluff. I want docs that don't suck.
• I like a sandbox that will help me build the API with a GUI or CLI interface.
• What make me smile/frown is reading through every product API documentation I tested with no standard tool specified.
• "Clear documentation of all aspects the API as well as code samples/tutorials documenting best practice ways of accessing/consuming them are the best. Ideally it should be autogenerated from code comments so I can be sure it is up to date with the latest version of code.
• If I have to interact with somebody to use the API then things have gone wrong. Documentation should not come from social media and should not rely on other users to help with tricky bits. If users are constantly asking the same questions in support forums for things that seem as though they should be simple, you have a problem (looking at you Telerik)"
• Good written documentation with examples
• If you have good documentation why do I need support?
• Thorough documentation, API explorer usual
ly gets the job done.
• Fast and accurate response
• Having the code (and various implementations) openly available to learn and understand from. If it is proprietary , the documentation and author reputation better be outstanding along with a direct support channel
• Example responses with mock data help give a feel for how the ergonomics of an API
• I don't want to have to ask support for what should be written documentation
• When a vendor explains their rationale for an API's behavior.
• Writing guides with zero skill assumption and constant callbacks to linked articles
• Proper documentation. Ideally the documentation is built in the API itself, i.e. you can query for API schema of given endpoint.
• Good documentation
• Well-written and easily searchable docs with lots of example are invaluable.
• A proper rest interface with proper authentication easily handled with python/powershell/whatever
• Having documentation at all helps. But ideally that documentation should guide good usage of an API, not just something that \*works\*. For frameworks this is includes things like establishing convention, and best practice. If there are two ways of achieving something, but one of them is preferred, safer, or otherwise more \*correct\* then this should be clearly indicated.
• "Good: ability to submit changes or request features, fast support/response to issues/bugs, well documented API docs, working examples, documented release notes, future plans, overall communication
Bad: the opposite of any of the above things"
• Honestly finding an API doc that has examples of requests and responses for the common use cases is the greatest thing. The best API is a well-documented one!
• Stability. Don't break existing clients.
• Having good documentation available is key.
• Quick responses that get to the root issue quickly
• Most important is to have an understanding of capabilities and limitations and extent of effort required to configure. What I find intriguing is in the beginning vendors and developer SMEs say - no worries there is an API and it can do what is needed - that brings a smile and then it takes forever to document and actually get things done when APIs are involved.
• When APIs change without informing us makes me frown.
• Valid examples
Having excellent online documentation makes the API usable; examples for usage are hugely important, as well.
# Question 5: Is there anything else you would like to tell us about this topic?
• The Unix world had it quite well with the 'man' command line command, there are some sites that emulate the spirit.
• Please try to be API first when it comes to features. CLI and GUI should be using the APIs to configure. There are so many times where I look for a feature that the GUI can do, but API cannot.
• An API is great but having readily available common language SDKs for the API is even better.
• Build well organized and thought out documentation and include examples for any non standard references
• Documentation with lots of examples are everything.
• Update your documentation with lots of different examples, mongo is a good example of terrible documentation, yes its all technically correct, but very little explanation on why and so few examples, if your trying anything that's not the 1 common query then the examples are useless.
• Video tutorials are the worst, and need to be accompanied by a text version (if they are used at all). I can search text, move back and forward through it precisely and easily, skim it, or take it slow.
• D O C U M E N T A T I O N
• Check out Moesif to understand user behavior on APIs
• Good topic for research. Please do share the results.
I love well-documented APIs!
https://redd.it/erja19
@r_devops
• Fast and accurate response
• Having the code (and various implementations) openly available to learn and understand from. If it is proprietary , the documentation and author reputation better be outstanding along with a direct support channel
• Example responses with mock data help give a feel for how the ergonomics of an API
• I don't want to have to ask support for what should be written documentation
• When a vendor explains their rationale for an API's behavior.
• Writing guides with zero skill assumption and constant callbacks to linked articles
• Proper documentation. Ideally the documentation is built in the API itself, i.e. you can query for API schema of given endpoint.
• Good documentation
• Well-written and easily searchable docs with lots of example are invaluable.
• A proper rest interface with proper authentication easily handled with python/powershell/whatever
• Having documentation at all helps. But ideally that documentation should guide good usage of an API, not just something that \*works\*. For frameworks this is includes things like establishing convention, and best practice. If there are two ways of achieving something, but one of them is preferred, safer, or otherwise more \*correct\* then this should be clearly indicated.
• "Good: ability to submit changes or request features, fast support/response to issues/bugs, well documented API docs, working examples, documented release notes, future plans, overall communication
Bad: the opposite of any of the above things"
• Honestly finding an API doc that has examples of requests and responses for the common use cases is the greatest thing. The best API is a well-documented one!
• Stability. Don't break existing clients.
• Having good documentation available is key.
• Quick responses that get to the root issue quickly
• Most important is to have an understanding of capabilities and limitations and extent of effort required to configure. What I find intriguing is in the beginning vendors and developer SMEs say - no worries there is an API and it can do what is needed - that brings a smile and then it takes forever to document and actually get things done when APIs are involved.
• When APIs change without informing us makes me frown.
• Valid examples
Having excellent online documentation makes the API usable; examples for usage are hugely important, as well.
# Question 5: Is there anything else you would like to tell us about this topic?
• The Unix world had it quite well with the 'man' command line command, there are some sites that emulate the spirit.
• Please try to be API first when it comes to features. CLI and GUI should be using the APIs to configure. There are so many times where I look for a feature that the GUI can do, but API cannot.
• An API is great but having readily available common language SDKs for the API is even better.
• Build well organized and thought out documentation and include examples for any non standard references
• Documentation with lots of examples are everything.
• Update your documentation with lots of different examples, mongo is a good example of terrible documentation, yes its all technically correct, but very little explanation on why and so few examples, if your trying anything that's not the 1 common query then the examples are useless.
• Video tutorials are the worst, and need to be accompanied by a text version (if they are used at all). I can search text, move back and forward through it precisely and easily, skim it, or take it slow.
• D O C U M E N T A T I O N
• Check out Moesif to understand user behavior on APIs
• Good topic for research. Please do share the results.
I love well-documented APIs!
https://redd.it/erja19
@r_devops
reddit
Survey results: API support options
Hi everyone, Thank you to all of you who answered my short survey about where you like to go to get help when you have a question about using...
Relevant certifications/courses to have in order to be considered for a DevOps position.
Please remove if not allowed.
​
My short working experience ranges from (backend and frontend) developer for a SAAS solution, System Administrator (both, physical and virtual ones, I even set up and migrated the whole thing to AWS), and now I'm working in a big company but as an Application Specialist, which is just a fancy way to call tech support.
​
But above all those, I've been a Linux nerd since I was young and the best way for me to built a career based on it, is in the DevOps world. I know there are still some roles for Linux Engineers but they are becoming so rare that I need to expand my hunt.
​
I have applied before to some DevOps related jobs and never got any. And the few chances I have had,
I have successfully take their practical tests with Ansible, Terraform, Docker.
​
So I was guessing having some certs on my bucket would be a better way to get a DevOps job. At least as a way to be considered more for job interviews.
​
Any suggestions on where to start?
​
I already have some GitHub projects I've made proving I can use those tools, but honestly, anyone smart enough can have those if documentation is properly read.
​
​
**tl;dr want to get DevOps job, what certs do I need to get closer to it without having a DevOps role before**
https://redd.it/erjtdl
@r_devops
Please remove if not allowed.
​
My short working experience ranges from (backend and frontend) developer for a SAAS solution, System Administrator (both, physical and virtual ones, I even set up and migrated the whole thing to AWS), and now I'm working in a big company but as an Application Specialist, which is just a fancy way to call tech support.
​
But above all those, I've been a Linux nerd since I was young and the best way for me to built a career based on it, is in the DevOps world. I know there are still some roles for Linux Engineers but they are becoming so rare that I need to expand my hunt.
​
I have applied before to some DevOps related jobs and never got any. And the few chances I have had,
I have successfully take their practical tests with Ansible, Terraform, Docker.
​
So I was guessing having some certs on my bucket would be a better way to get a DevOps job. At least as a way to be considered more for job interviews.
​
Any suggestions on where to start?
​
I already have some GitHub projects I've made proving I can use those tools, but honestly, anyone smart enough can have those if documentation is properly read.
​
​
**tl;dr want to get DevOps job, what certs do I need to get closer to it without having a DevOps role before**
https://redd.it/erjtdl
@r_devops
reddit
Relevant certifications/courses to have in order to be considered...
Please remove if not allowed. My short working experience ranges from (backend and frontend) developer for a SAAS solution, System...
[ELK] Logstash Parsing issues.
Hey Guys!
I have ELK stack configured, where multiple sources (Filebeat) push logs to Logstash and it pushes logs to Elastic search.
However, there are multiple instances where logs were not pushed in ES because of some error such as:
\-Error parsing JSON
\-Unexpected character (, etc
I came to know about this issue when I checked var logs of Logstash.
Question1: How can I check which was the source when Logstash failed to parse and what log it was?
Question 2: How can I configure alerts for Logstash, triggered when any line failed to parse?
https://redd.it/erax55
@r_devops
Hey Guys!
I have ELK stack configured, where multiple sources (Filebeat) push logs to Logstash and it pushes logs to Elastic search.
However, there are multiple instances where logs were not pushed in ES because of some error such as:
\-Error parsing JSON
\-Unexpected character (, etc
I came to know about this issue when I checked var logs of Logstash.
Question1: How can I check which was the source when Logstash failed to parse and what log it was?
Question 2: How can I configure alerts for Logstash, triggered when any line failed to parse?
https://redd.it/erax55
@r_devops
reddit
[ELK] Logstash Parsing issues.
Hey Guys! I have ELK stack configured, where multiple sources (Filebeat) push logs to Logstash and it pushes logs to Elastic search. However,...
Opentracing - Jaeger vs. Zipkin
I was wondering, have anyone used either jaeger or zipkin in production. What worked for you, what are the pros ans cons of the two?
https://redd.it/eraqve
@r_devops
I was wondering, have anyone used either jaeger or zipkin in production. What worked for you, what are the pros ans cons of the two?
https://redd.it/eraqve
@r_devops
reddit
Opentracing - Jaeger vs. Zipkin
I was wondering, have anyone used either jaeger or zipkin in production. What worked for you, what are the pros ans cons of the two?
GitOps (argo cd, flux or custom) and migrations and secrets
We have \~10 microservices mostly in Django, but we will add more. I'm trying to introduce GitOps (we have yamls and some helms) and some tools for releasing/promoting images to different environments and rollbacks... But I have a big problem with migrations:
1. I can handle "forward" migration in hooks/jobs/init containers in argo cd.
2. However, when I want to make rollback migrations let's say migrate database version 16 to 14, then it blows my mind how to do it. Argo cd doesn't support rollback hooks.
​
Another problem:
1. How to handle secrets in GitHub repository?
https://redd.it/eru0fg
@r_devops
We have \~10 microservices mostly in Django, but we will add more. I'm trying to introduce GitOps (we have yamls and some helms) and some tools for releasing/promoting images to different environments and rollbacks... But I have a big problem with migrations:
1. I can handle "forward" migration in hooks/jobs/init containers in argo cd.
2. However, when I want to make rollback migrations let's say migrate database version 16 to 14, then it blows my mind how to do it. Argo cd doesn't support rollback hooks.
​
Another problem:
1. How to handle secrets in GitHub repository?
https://redd.it/eru0fg
@r_devops
reddit
GitOps (argo cd, flux or custom) and migrations and secrets
We have \~10 microservices mostly in Django, but we will add more. I'm trying to introduce GitOps (we have yamls and some helms) and some tools...
Blog post: Building an Azure DevOps Pipeline [Soup to Nuts]
Hey guys, I just wrote a new blog post you may enjoy on the ATA blog.
Summary: Learn how to build a real Azure DevOps pipeline for an ARM template from beginning to end in this real-world, step by step tutorial.
https://adamtheautomator.com/azure-devops-pipeline-infrastructure/
If you'd like to write posts like this, get promoted and get paid, join us! https://adamtheautomator.com/friends
https://redd.it/ervvzy
@r_devops
Hey guys, I just wrote a new blog post you may enjoy on the ATA blog.
Summary: Learn how to build a real Azure DevOps pipeline for an ARM template from beginning to end in this real-world, step by step tutorial.
https://adamtheautomator.com/azure-devops-pipeline-infrastructure/
If you'd like to write posts like this, get promoted and get paid, join us! https://adamtheautomator.com/friends
https://redd.it/ervvzy
@r_devops
Adam the Automator
Building an Azure DevOps Pipeline [Soup to Nuts]
Learn how to build a real Azure DevOps pipeline for an ARM template from beginning to end in this real-world, steo by step tutorial.
«Consuming» existing on-prem infrastructure with IaC
Hi all,
I currently have a number of sites with on-prem infrastructure that due to various reasons (bandwidth, latency etc) cannot be migrated to cloud.
I also recently set up a new site, where I modified our existing cloud pipeline/IaC-framework (Terraform/Ansible etc) to deploy new site infra from scratch and it worked a charm.
I would like to extend the modified on-prem IaC-framework to existing sites as well. Unfortunately, for these I don’t have the luxury of a scratch deploy as all sites are nearly 24/7 operations.
Are there strategies or best practices for applying/transitioning in an CI/CD-pipeline for IaC into an existing infrastructure?
https://redd.it/eryfsp
@r_devops
Hi all,
I currently have a number of sites with on-prem infrastructure that due to various reasons (bandwidth, latency etc) cannot be migrated to cloud.
I also recently set up a new site, where I modified our existing cloud pipeline/IaC-framework (Terraform/Ansible etc) to deploy new site infra from scratch and it worked a charm.
I would like to extend the modified on-prem IaC-framework to existing sites as well. Unfortunately, for these I don’t have the luxury of a scratch deploy as all sites are nearly 24/7 operations.
Are there strategies or best practices for applying/transitioning in an CI/CD-pipeline for IaC into an existing infrastructure?
https://redd.it/eryfsp
@r_devops
reddit
«Consuming» existing on-prem infrastructure with IaC
Hi all, I currently have a number of sites with on-prem infrastructure that due to various reasons (bandwidth, latency etc) cannot be migrated to...
Single-tenant application delivered as a multi-tenant service?
I'm trying to wrap my head around how this might work: Rather than create a multi-tenant application, my thought is to create a single-tenant application that is then deployed repeatedly for new customers.
I'm curious if anyone else has adopted this approach, and if so, how? What are some potential downfalls that would make this a pretty bad idea?
https://redd.it/erwzro
@r_devops
I'm trying to wrap my head around how this might work: Rather than create a multi-tenant application, my thought is to create a single-tenant application that is then deployed repeatedly for new customers.
I'm curious if anyone else has adopted this approach, and if so, how? What are some potential downfalls that would make this a pretty bad idea?
https://redd.it/erwzro
@r_devops
reddit
Single-tenant application delivered as a multi-tenant service?
I'm trying to wrap my head around how this might work: Rather than create a multi-tenant application, my thought is to create a single-tenant...
Building a Delivery Platform
https://blog.brujordet.no/post/devops/building-a-delivery-platform/
This is a blog post I wrote that initially started out as a confluence page where I wanted to lay the foundation for building a Deliver Platform at my new job. We don’t really have anything yet, and I needed to describe the basics so others can chip in.
This is all based on my experiences so I’m keen to hear your thoughts on this. Especially the approach to a golden path and how you’ve dealt with PaaSifying deployment to k8s for developers who don’t care much for DevOps. Is this pretty much obvious stuff that I’m talking about or do you have contradicting advice?
https://redd.it/erz1j5
@r_devops
https://blog.brujordet.no/post/devops/building-a-delivery-platform/
This is a blog post I wrote that initially started out as a confluence page where I wanted to lay the foundation for building a Deliver Platform at my new job. We don’t really have anything yet, and I needed to describe the basics so others can chip in.
This is all based on my experiences so I’m keen to hear your thoughts on this. Especially the approach to a golden path and how you’ve dealt with PaaSifying deployment to k8s for developers who don’t care much for DevOps. Is this pretty much obvious stuff that I’m talking about or do you have contradicting advice?
https://redd.it/erz1j5
@r_devops
blog.brujordet.no
Building a Delivery Platform
A journey begins Almost 10 years ago I finished my Masters degree in Computer Science and started working as a consultant at KnowIt in Oslo. My team was in charge of developing the integration bus for the local municipality, and we had earned a lot of freedom…
Has anyone used or heard of KubeMQ?
We're in the process of migrating to Kubernetes and we were looking into alternatives for message queues. We found one that looked promising, KubeMQ, that claims to be a cloud native message queue that was specifically designed for running on Kubernetes. However, when we started looking into the adoption rate, we were a bit stumped... It seems like KubeMQ has zero presence online. Nobody has ever asked a question about it on stack overflow, nobody has written blog posts about using it (except 1 single person), nobody has compared it to kafka or rabbitmq (except KubeMQ themselves). It seems strange to me that something that seems so "legit" has never been tested or talked about by anybody, even here on reddit.
So, has anybody heard about this technology or used it?
https://redd.it/es0s78
@r_devops
We're in the process of migrating to Kubernetes and we were looking into alternatives for message queues. We found one that looked promising, KubeMQ, that claims to be a cloud native message queue that was specifically designed for running on Kubernetes. However, when we started looking into the adoption rate, we were a bit stumped... It seems like KubeMQ has zero presence online. Nobody has ever asked a question about it on stack overflow, nobody has written blog posts about using it (except 1 single person), nobody has compared it to kafka or rabbitmq (except KubeMQ themselves). It seems strange to me that something that seems so "legit" has never been tested or talked about by anybody, even here on reddit.
So, has anybody heard about this technology or used it?
https://redd.it/es0s78
@r_devops
reddit
Has anyone used or heard of KubeMQ?
We're in the process of migrating to Kubernetes and we were looking into alternatives for message queues. We found one that looked promising,...
Seeing the state of production in git and parameterising deployments that are very similar
Hi folks,
I was once mentored by a fellow who i am no longer in contact with and he recommended to me that all of the config for production remain in a single repository, as a sort of "source of truth" and I was wondering how that might be done and if it is still (if at all) a best practice?
My current thinking is that all config should live in the repository along with source code and the infrastructure required for that code to run in the cloud, so that all of the code required for a service exists as an atomic unit.
But, this causes problems when we e.g. want to deploy 10 services which are all essentially parametrised versions of each other, that is that the source code is the same but the configuration related to each of the 10 deployments is what functionally separates them. Do we separate this information into 10 repositories? For a concrete example we might have 10 data sources that we want to scrape from and all return the same format for data
I would be grateful for any discussion or resources on the matter.
https://redd.it/es1ipp
@r_devops
Hi folks,
I was once mentored by a fellow who i am no longer in contact with and he recommended to me that all of the config for production remain in a single repository, as a sort of "source of truth" and I was wondering how that might be done and if it is still (if at all) a best practice?
My current thinking is that all config should live in the repository along with source code and the infrastructure required for that code to run in the cloud, so that all of the code required for a service exists as an atomic unit.
But, this causes problems when we e.g. want to deploy 10 services which are all essentially parametrised versions of each other, that is that the source code is the same but the configuration related to each of the 10 deployments is what functionally separates them. Do we separate this information into 10 repositories? For a concrete example we might have 10 data sources that we want to scrape from and all return the same format for data
I would be grateful for any discussion or resources on the matter.
https://redd.it/es1ipp
@r_devops
reddit
Seeing the state of production in git and parameterising...
Hi folks, I was once mentored by a fellow who i am no longer in contact with and he recommended to me that all of the config for production...
Minimal tracking of OS health indicators with alarms
I have a one off project that requires the tracking of:
* memory usage
* load average
* disk utilization
for a linux VM. The minimum functionality is to send notifications (email, Slack message) when those metrics exceed a threshold.
Knee-jerk responses might be to use Nagios, prometheus, SNMP etc. I want something simple with minimum effort (max: 1 day effort). What is your expert recommendation ?
https://redd.it/es07t8
@r_devops
I have a one off project that requires the tracking of:
* memory usage
* load average
* disk utilization
for a linux VM. The minimum functionality is to send notifications (email, Slack message) when those metrics exceed a threshold.
Knee-jerk responses might be to use Nagios, prometheus, SNMP etc. I want something simple with minimum effort (max: 1 day effort). What is your expert recommendation ?
https://redd.it/es07t8
@r_devops
reddit
Minimal tracking of OS health indicators with alarms
I have a one off project that requires the tracking of: * memory usage * load average * disk utilization for a linux VM. The minimum...
Stopping Python-based backdoor Attacks with zerotrust networking
An overview of how to stop attacks like MechaFlounder with a zerotrust networking approach.
https://vimeo.com/383337193/65c5e52bcd
https://redd.it/es32i6
@r_devops
An overview of how to stop attacks like MechaFlounder with a zerotrust networking approach.
https://vimeo.com/383337193/65c5e52bcd
https://redd.it/es32i6
@r_devops
Vimeo
Stopping Python-based Backdoor Attacks
The MechaFlounder was a backdoor attack linked to Iranian threat actors who targeted Turkish entities. Similar Python-based backdoor attacks have managed to evade…
Automated testing for audio DSP software (VST)?
I have been using automated unit tests with TDD (test driven development) at work for physics software development and it made me wonder if audio DSP software could work with tests/TDD.
Some VST developers I know have posted videos about how debugging can be very time consuming for them, how they have noticed that certain parts of the audio processing are never actually executed (which I think is purely a code coverage issue), etc. which interests me in seeing if there is some way to do automated unit tests for TDD.
VSTs aren't standalone software, they run inside a VST host, such as a DAW (Digital Audio Workstation), almost all of which are graphical programs. So far the only way I have found to test them is to build to .dll file and use the VST in the DAW, which is purely manual testing. In addition some DAWs handle plugins differently.
I was thinking a sort of command line based VST host could suffice for setting parameters on the VST, hosting it, letting audio pass in and out, etc. [I did find Ecasound which apparently has command line support](https://lwn.net/Articles/509958/) but it is Linux only. But that is better than nothing.
I was also thinking I could use a recorder to write the output of the plugin to an audio file if that would somehow be useful in testing.
I was thinking some tests could be done fairly easily, such as:
1. Trigger a button press event, ensure that the state the button refers to is triggered
2. Call the various methods as normally, see if anything crashes/raises errors
However, checking if the audio sounds good seems more difficult because it is hard to quantify purely using tests, and it is subjective.
Does anyone have any ideas here? Thanks
https://redd.it/es3y5t
@r_devops
I have been using automated unit tests with TDD (test driven development) at work for physics software development and it made me wonder if audio DSP software could work with tests/TDD.
Some VST developers I know have posted videos about how debugging can be very time consuming for them, how they have noticed that certain parts of the audio processing are never actually executed (which I think is purely a code coverage issue), etc. which interests me in seeing if there is some way to do automated unit tests for TDD.
VSTs aren't standalone software, they run inside a VST host, such as a DAW (Digital Audio Workstation), almost all of which are graphical programs. So far the only way I have found to test them is to build to .dll file and use the VST in the DAW, which is purely manual testing. In addition some DAWs handle plugins differently.
I was thinking a sort of command line based VST host could suffice for setting parameters on the VST, hosting it, letting audio pass in and out, etc. [I did find Ecasound which apparently has command line support](https://lwn.net/Articles/509958/) but it is Linux only. But that is better than nothing.
I was also thinking I could use a recorder to write the output of the plugin to an audio file if that would somehow be useful in testing.
I was thinking some tests could be done fairly easily, such as:
1. Trigger a button press event, ensure that the state the button refers to is triggered
2. Call the various methods as normally, see if anything crashes/raises errors
However, checking if the audio sounds good seems more difficult because it is hard to quantify purely using tests, and it is subjective.
Does anyone have any ideas here? Thanks
https://redd.it/es3y5t
@r_devops
lwn.net
The Linux digital audio workstation - Part 1
The contemporary DAW—digital audio workstation—is a system of
hardware and software parts assembled to record, edit, and play digital
audio and MIDI (Musical Instrument Digital Interface) data. Hardware
components include the host computer, one or more interfaces…
hardware and software parts assembled to record, edit, and play digital
audio and MIDI (Musical Instrument Digital Interface) data. Hardware
components include the host computer, one or more interfaces…
Looking for feedback on tool to fetch all your SaaS audit logs
Hi all,
I am building a tool that fetches the audit logs from all your SaaS tools (think G Suite, Okta, Github, Zendesk, Dropbox, Salesforce, etc) and pushes them into whatever existing logging pipeline you have (Splunk, ELK, Kinesis, etc). The product is in a beta state and I'm searching for testers who can try it out, provide feedback, and help guide my roadmap. If this sounds interesting to you I would love to chat - you can either direct message me here on reddit or shoot me an email at arkadiy{at}logsnitch.com.
Hopefully this fits the promotion rules in this sub but if not I can delete this post.
Thanks very much,
https://redd.it/es2we6
@r_devops
Hi all,
I am building a tool that fetches the audit logs from all your SaaS tools (think G Suite, Okta, Github, Zendesk, Dropbox, Salesforce, etc) and pushes them into whatever existing logging pipeline you have (Splunk, ELK, Kinesis, etc). The product is in a beta state and I'm searching for testers who can try it out, provide feedback, and help guide my roadmap. If this sounds interesting to you I would love to chat - you can either direct message me here on reddit or shoot me an email at arkadiy{at}logsnitch.com.
Hopefully this fits the promotion rules in this sub but if not I can delete this post.
Thanks very much,
https://redd.it/es2we6
@r_devops
reddit
Looking for feedback on tool to fetch all your SaaS audit logs
Hi all, I am building a tool that fetches the audit logs from all your SaaS tools (think G Suite, Okta, Github, Zendesk, Dropbox, Salesforce,...
Do you often SSH into remote systems? What are your use cases? Do you have a plan to make it unnecessary in the near future?
https://redd.it/es5ztp
@r_devops
https://redd.it/es5ztp
@r_devops
reddit
Do you often SSH into remote systems? What are your use cases? Do...
Posted in r/devops by u/bad_boy_barry • 2 points and 0 comments
I'm using a makefile to automate terraform deployments. Does anyone know how to pass a Global Red Hat variable to a makefile so I can pass it via SSH agent forwarding. (code below)
echo "$efs_dns" | ssh -At ec2-user@$$(terraform output bastion-public_ip) 'ssh master.openshift.local "cat > efs_dns.txt"'
So this code block is supposed to get the global linux variable '$efs\_dns', pass it to 'master.openshift.local' jumping through a bastion to get the variable output to a file called 'efs\_dns.txt'. The problem is when it's all said and done efs\_dns.txt has some crap value instead of a dns name.
Edit: It seems like the bad output is a piece of the variable name..the variable is called $efs\_dns well the output text in the file is 'fs\_dns'
https://redd.it/es1chl
@r_devops
echo "$efs_dns" | ssh -At ec2-user@$$(terraform output bastion-public_ip) 'ssh master.openshift.local "cat > efs_dns.txt"'
So this code block is supposed to get the global linux variable '$efs\_dns', pass it to 'master.openshift.local' jumping through a bastion to get the variable output to a file called 'efs\_dns.txt'. The problem is when it's all said and done efs\_dns.txt has some crap value instead of a dns name.
Edit: It seems like the bad output is a piece of the variable name..the variable is called $efs\_dns well the output text in the file is 'fs\_dns'
https://redd.it/es1chl
@r_devops
reddit
I'm using a makefile to automate terraform deployments. Does...
echo "$efs_dns" | ssh -At ec2-user@$$(terraform output bastion-public_ip) 'ssh master.openshift.local "cat > efs_dns.txt"' So this code block is...
Moving from network engineering position to DevOps / software positions
​
Hi,
I'm a 23 years old network engineer with 4.5 years of experience at enterprises, I have the following knowledge:
\- Cisco networking - routers and switches also all the protocols.
\- Python scripting and network automation
\- Linux system administration
(not system admin experience but from network engineering perspective).
\- AWS fundamental knowledge
\- Check Point firewalls
\- Virtualization - VMware
​
These are my certs that I currently hold:
\- CCNP R&S
\- CCNA Security
\- AWS Cloud Practitioner
\- LPI Linux Essentials
I currently want to pursue a career in software development or devops and I'm not sure what is the best path for me.
I think about pursuing CS degree, but I got another feeling of doing AWS Solution Architect associate cert and Comptia Linux+ cert and go more to the "devops route"
(also learrning docker + ansible + jenkins afterwards).
I'm not sure if my best way is to pursue a degree or get certs for a better position (Devops/Software)
Thanks,
https://redd.it/ertlj4
@r_devops
​
Hi,
I'm a 23 years old network engineer with 4.5 years of experience at enterprises, I have the following knowledge:
\- Cisco networking - routers and switches also all the protocols.
\- Python scripting and network automation
\- Linux system administration
(not system admin experience but from network engineering perspective).
\- AWS fundamental knowledge
\- Check Point firewalls
\- Virtualization - VMware
​
These are my certs that I currently hold:
\- CCNP R&S
\- CCNA Security
\- AWS Cloud Practitioner
\- LPI Linux Essentials
I currently want to pursue a career in software development or devops and I'm not sure what is the best path for me.
I think about pursuing CS degree, but I got another feeling of doing AWS Solution Architect associate cert and Comptia Linux+ cert and go more to the "devops route"
(also learrning docker + ansible + jenkins afterwards).
I'm not sure if my best way is to pursue a degree or get certs for a better position (Devops/Software)
Thanks,
https://redd.it/ertlj4
@r_devops
reddit
Moving from network engineering position to DevOps / software...
Hi, I'm a 23 years old network engineer with 4.5 years of experience at enterprises, I have the following knowledge: \- Cisco...