9

Personally I don't see any reason for which an Artefact Repository - the recommeneded DevOps tool of managing artefacts - wouldn't be applicable to trained neural nets or other artefacts. The artefact size might have some upper limit for a particular artefact repository, but in such case it would be a technical or policy limitation one, not a fundamental/...


8

The key difference between DevOps in the context of Avionics and, aircraft/spacecraft merely has to do with deployment velocity due to FAA certifications, Aircraft re-grooms and the way in which the Airline industry releases their changes. But ultimately, DevOps is not exclusive to High Velocity delivery methods (like Agile). And can be done in the context ...


8

Since you've tagged this question as "culture", I'm assuming you're not interested in a specific application, but in the broader questions of workflow and management. I'd probably start with "The DevOps Handbook"; it's a good overview of different things to consider, without diving too deep. "Continuous Delivery" by Jez Humble is also often referenced; I ...


7

According to Wikipedia, the first reference you linked, In computer science and information science, an ontology is a formal naming and definition of the types, properties, and interrelationships of the entities that really or fundamentally exist for a particular domain of discourse. It is thus a practical application of philosophical ontology, with a ...


7

This is not about DevOps, but straight software development, I assume. I want to understand the culture better Well, the big thing in straight development (without the "DevOps" angle) is certainly "agile", i.e. for the most part SCRUM. You might do worse than to sit down and read the Agile Manifesto or a primer on SCRUM, or Kanban for the more day-to-...


6

Large enterprises will commonly adopt a delivery framework, or operating model, that has been built to support large enterprises. From an Agile/DevOps perspective, which is my area of expertise there are three frameworks of interest: Scaled Agile Framework (SAFe®) defines DevOps as delivering business value through the successful operation of software in ...


5

This question perfectly illustrates the different approaches in adopting DevOps by organizations. While both approaches target the 3rd circle on the culture model - the traditional corporations - there is a difference in aim and results. Adopt DevOps best practices and tools for increased effectiveness. Adopt DevOps culture and values for organizational ...


5

As far as I can read between the lines, you want your upper management to support you in introducing the 12-factor approach to your company's software development. In that respect, you do not want to explain each of the 12 factors to them. If they really were interested in that, then you could just send them the 12-factor website you have linked in your ...


5

Yes, DMAIC makes sense. If processes like CD need to be improved it is important to have a baseline. Therefore the Measure step is useful. The team investigates the status of process X, e.g. CD by documenting the current status.


4

I would recommend taking a look at DVC - an open source version control system for data science projects. One of the basic things that it perfectly handles is managing data files (along with code) - inputs, outputs (models), intermediate results. Semantically it's similar to git-lfs but unlike git-lfs it is capable of managing files like 100GB and what is ...


4

We are a product development shop - and in fact we build a Kanban tool (SwiftKanban), in addition to others. We have a lot of experience with Kanban and DevOps and separate boards for epic/ story detailing vs. dev/ ps tracking. Our DevOps setup is still being fully automated and being gradually fleshed out. We've been on this journey since 2010-11 - and we ...


4

Have you been in this scenario before? Yes. Pretty standard scenario in my experience. How did you address and overcome these obstacles? In very small steps. How long did it take to implement? (as a rough idea) Very long; in one rather large extreme case: over 10 years, and still ongoing. How would you prioritize the tasks listed above? My ...


4

I. Codebase One codebase tracked in revision control, many deploys Version Control System (VCS) II. Dependencies Explicitly declare and isolate dependencies Use a package manager tool III. Config Store config in the environment Environment variables IV. Backing services Treat backing services as attached resources The code ...


3

You want the execution speed of the CI pipeline as fast as (practically) possible, irrespective of being a local or shared setup or the time required to set it up - this is what effectively dictates the overall development speed in the respective project. But it should be noted that by speed here I don't mean the duration of each CI execution. The duration ...


3

In terms of development procedure, you should consider using the agile method. This is the most widely used method of software development and has proven itself. Within the scope of the agile method Pair programming will allow you to spool up another developer to assist with your projects when you are ready and find that you have more work than you can ...


3

Yes but It is hard to deny James and Tensibai's sentiments that we are hard to define. I've probably offended a few job interviewers by pointing out DevOps means whatever you want it to mean at the time. Vendors and the press in computing are not very motivated by correctness or conformity so any popular term will get muddied in a similar fashion. There is ...


2

I suspect I'm late to the party, but I've survived a few similar scenarios and might have some tips for you. It sounds like your team has been over-managed and has grown hostile to process or rules in general. Do not go directly to Agile and sprint based development. Consider going with Kanban, and link work items to an epic/larger context. Sometimes ...


2

Pipeline as Code (PaC) means that the CI/CD configuration will be stored in the VCS instead of in the CI/CD tool itself, e.g. configuring it manually by using a UI. Any experiences what can be the "critical mass" where this investment is a clear pay-off and not an overkill? Imagine that more than 100 jobs have been configured manually the last couple ...


2

Inability to report progress consistently across multiple development teams, for example, if one team reports their progress in terms of the number of equally sized stories completed in 2 weeks; whereas another team reports in storypoints completed in a three-week sprint. Inconsistent application of a practice means team members can not easily move between ...


2

None of the issues you present appear to be DevOps-specific to me. Some of the pitfalls organisations are trying to avoid are: Inability to report progress consistently across multiple development teams, for example, if one team reports their progress in terms of the number of equally sized stories completed in 2 weeks; whereas another team reports in ...


2

The beauty of a kanban board is that it lets you see what everyone on the team is working on; if work is related, it should be on a common board (in my opinion). However, one way to deal with specialization of teams is to use swimlanes, particularly if the tasks have common phases. Take a simple board for example, with a To Do pile, a Doing pile, and a ...


2

First, DevOps is a journey, not a destination. Not every organization approaches similar problems with the same solution; while automation is a component of a DevOps platform, it's not the single defining characteristic. The role and responsibilities of QA professionals haven't really changed; they're still responsible for validating that code is ready for ...


2

According to Facebook Production Engineering at Facebook is a hybrid between software and systems engineering; it keeps Facebook running smoothly and scaling efficiently. The Production Engineering team works within Facebook’s product and infrastructure teams to make sure our services are reliable and scalable. The team writes code and debugs hard ...


2

If you are dealing with application logs, here are the three broad categories of information that a good log file should cover: basic context (timestamp, log level, application name, source file name, source module/function, source line number, log message) server context (host name, data center name unless host name has it encoded, cluster/pod info, ...


2

You're basically describing GitOps. Here's how I've followed that for a containerized microservices build and deploy pipeline: Each service repo includes it's own Dockerfile, Kubernetes manifests, and anything else needed to locally build and test the project. The base image for the Dockerfile will likely be managed from another repo but built and hosted by ...


1

This is opinionated I feel. But for me I think the relation between the 2 is actually a massive mistake made by a lot of companies. There are a ton of software-systems hybrid jobs out there, and I've worked both ends of the spectrum, and in between. DevOps is a buzzword and it's new and shiny, so everything that falls in that realm is instantly deemed DevOps....


1

I'd prioritize things like this: put all projects in version control automate the builds and immediately/simultaneously bring up CI with those builds - this is important to prevent the teams not yet used with version control from falling into the branching nightmare trap - they will start appreciating the CI fast feedback, even if just for the build portion,...


1

The key aspect in a Dev(Sec)Ops-oriented organisation is the inter-field communication and collaboration. From this perspective, the QA role can include activities such as: continuous improvement of automated QA coverage/effectiveness, reliability, performance (which ideally should target CI/CD, but not always is/can be) direct, active/constant involvement ...


1

This is an open-ended question, which is why the following answer is an opinion. The focus of QA (quality assurance) in the DevOps field is to monitor the deployment metrics to ensure that faults are caught before they can manifest. The most direct metrics of application health include application availability and errors. These can be directly extracted ...


1

For your own personal use, I think a GitHub repository with all of your bootstrap and installation scripts is a great idea. It serves as a portable way to download and distribute any scripts you need where firewalls and restrictions aren't an issue. As for within your organization, one suggestion that your IT might be open to as a compromise is to create a ...


Only top voted, non community-wiki answers of a minimum length are eligible