DOCSLIB.ORG

Chef Client Policy

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Chef Client Policy Dear Participants, • Chef Mailing List Welcome to the course DevOps with Chef on FreeBSD. In • Git website this course, we’ll cover lot of theory and practical aspects. • Ruby Website We’ll focus on the core topics as mentioned in the agenda, Hardware/Software Requirement and we assume that you already know the prerequisites. If • 2 FreeBSD 11 systems/machines (Virtual or Physical), with not, then you might have to learn additional topics such Internet access and bash as the default shell with root as Git, Ruby and FreeBSD first. login over ssh or a normal user with sudo access. • A free account on Hosted Chef. The learning curve for Chef is a little steep at times. There, fore, just be patient and keep working on it, and you’ll eventually be done with the course. We’ll certainly help you throughout the course. But, be prepared to do a lot of self-study as well. Bear in mind that the best way to learn Chef is to just use it. Prerequisites • Knowledge of how to use version control system, pref, erably Git. • Basic Knowledge of FreeBSD OS Administration. • Basic knowledge of any scripting language, preferably Ruby. • Working knowledge of any text/code editor. Resources • FreeBSD • FreeBSD Documentation • Download FreeBSD • Chef Website • Chef Documentation • Chef IRC Channel TABLE OF CONTENTS Module 1: Introduction to Chef.................................................................................................................................................................3 Module 2: Resources.................................................................................................................................................................................7 Module 3: Setup the workstation............................................................................................................................................................10 Module 4: Bootstrap a node with Chef....................................................................................................................................................11 Module 5: Get started with writing your first cookbook........................................................................................................................14 Module 6: Deep Dive into Chef cookbook development.......................................................................................................................20 Module 7: Advanced chef concepts........................................................................................................................................................26 Module 8: Using syntax and linting tools like: Foodcritic and RuboCop..............................................................................................33 Module 9:Writing unit test and integration tests..................................................................................................................................38 ii MODULE 1 What is automation? Introduction to Chef Its definition depends on the context and situation. In general, automation is a non-manual way of performing What is DevOps? certain set of tasks. In automation of IT infrastructure, According to Wikipedia, “DevOps (a clipped compound of this set of tasks could be: creating new servers and infra, development and operations) is a culture, movement or structure, managing existing servers, deploying applica, practice that emphasizes the collaboration and commu, tions, updating both servers and applications, monitor, nication of both software developers and other ing servers and apps, gathering metrics, graphs, scaling information-technology (IT) professionals while automat, up or down the infrastructure and many more. ing the process of software delivery and infrastructural Why is it needed? changes.” Virtualization and Cloud have forced the need for auto, mation. In the earlier days (The Iron Age), IT infrastruc, ture growth was dependent on the physical hardware pur, chasing cycle. It used to take weeks from ordering an ac, tual server to it being delivered, and then deploying the OS and having the server ready for use. What are the diferent tools/platforms available? The most popular tools/platform available, as of now, for IT infrastructure automation are: ● Chef. ● Puppet. ● Ansible. 3 What is Chef? Overview of Chef. Chef is a powerful automation platform that transforms infrastructure into code. It’s open source. Its DSL is writ, Chef Architecture. ten in Ruby. And it’s supported by almost all major Linux, Unix, Windows, cloud and container platforms. It’s re, leased under Apache2 license. The project was started in 2008, and has been growing ever since. It has a large com, munity and is backed by a commercial for profit company/entity called “Chef”. Chef is being used by startups and Fortune 100 compa, nies, like Facebook, GE Capital and more. 4 Chef Components templates, etc. This repo could be managed by ver, sion control system such as Git. Chef Workstation Knife A workstation is a computer configured to run various chef command line tools, that interact with chef server It’s the command line tool to interact with chef server and nodes. It’s also used to create and maintain cook, as well as nodes. books. Chef DK Chef Server It’s a package that contains everything to get started A chef server acts as a single point of contact for worksta, with chef. Unfortunately, it’s not available for BSD as tion as well as the nodes/client. All the code (cookbooks/ of now. recipes) are uploaded to chef server. Chefspec Chef node It’s the unit test framework for chef. A node is any machine – physical, virtual, cloud, etc. – that Cookbook is managed by chef. A cookbook is a fundamental unit of configuration or Chef client policy. Following are the cookbook components: Chef client is a software or agent that runs on chef •Attributes nodes. It contacts chef server periodically and downloads the code (recipes, etc) and executes them. Attributes can be defined in files and can be overrid, den. They help in making configuration dynamic. Chef Workstation Components •Recipes Chef repo It’s the most fundamental configuration element. It’s It’s a repository structure, used to create and maintain authored in ruby. It must be stored within a cook, chef cookbooks. Cookbooks contains recipes, attributes, book. It’s a collection of resources, and can be in, 5 cluded, and can have dependencies. • Files Files inside the files directory are copied to the target node, just like scp. • Libraries It’s arbitrary ruby code to be included in a cookbook. • Templates A cookbook template is an embedded ruby file that’s used to dynamically generate static text file. • Metadata It’s a file that stores metadata about a cookbook. Typical Chef cookbook Workflow. • Create or Edit a cookbook. • Upload cookbook. • Provision machine. • Bootstrap machine. • Run Chef-client. • Ssh and validate. 6 MODULE 2 Resources Every resource has its own set of actions and properties. Most properties have default values. Some properties are available What is a resource? to all resources, for example, those used to send notifications to other resources and guards that help ensure that some re- A resource is a building block of recipes. They represent a sources are idempotent. piece of a system, e.g.: A package or directory, file, network, service, etc. It describes: For example, a resource that is used to install a tar package for version 1.16.1 may look something like this: • The desired state of the configured element/item. package 'tar' do • Steps needed to achieve that desired state. version '1.16.1' • Additional properties (called resource properties), if neces- sary. action :install End • The type of resource. Resource syntax: Common Functionality A resource is a Ruby block with four components: a type, a All resources (including custom resources) share a set of com- name, one (or more) properties (with values), and one (or mon actions, properties, conditional executions, notifications, more) actions. The syntax for a resource is like this: and relative path options. type 'name' do Actions property 'value' Actions could be :start, :stop, :restart, :reload or :nothing action :type_of_action end 7 Properties RESOURCE DESCRIPTION Following properties are common to every resource: ig- freebsd_package Use this to manage freebsd packages. nore_failure, retries, retry_delay, provider and Use cron resource to manage cron entries supports cron for time based scheduling. Guards Use it to install gems only to the instance of chef_gem ruby that is dedicated to chef-client. The not_if and only_if conditional executions can be used to Use this to execute scripts using the bash put additional guards for certain resources, so that they are bash interpreter. only run when the condition is met. package Use it to manage packages. Notifications Use this resource to add, remove, modify Notifies and subscribes notifications can be used with any re- user users and their attributes, e.g.: password, source. home directory, default shell, etc. Use this resource to add, remove, modify Common or most used resources group group and their attributes, e.g.: group members, etc. RESOURCE DESCRIPTION link Use it to create a symbolic or hard links. directory Use directory resource to manage directory. log Use this resource to create log entries. Use this resource to copy file from local Use it to copy directories from workstation cookbook_file remote_directory workstation to the node. to node. Use this to create and manage files on the Use this to copy/download
Load more

Recommended publications
  • Tsuru Documentation Release 1.6.2
    tsuru Documentation Release 1.6.2 tsuru Oct 04, 2018 Contents 1 Understanding 3 1.1 Overview.................................................3 1.2 Concepts.................................................4 1.3 Architecture...............................................5 2 Installing 7 2.1 tsuru Installer...............................................7 2.2 Installing tsuru components....................................... 12 3 Managing 21 3.1 Installing platforms............................................ 21 3.2 Creating a platform............................................ 22 3.3 Using Pools................................................ 23 3.4 Provisioners............................................... 25 3.5 Clusters.................................................. 26 3.6 Segregate Scheduler........................................... 27 3.7 Upgrading Docker............................................ 27 3.8 Managing Git repositories and SSH keys................................ 28 3.9 Managing users and permissions..................................... 28 3.10 Managing Application Logs....................................... 32 3.11 Debugging and Troubleshooting..................................... 33 3.12 Volumes................................................. 34 3.13 Event webhooks............................................. 35 4 Using 39 4.1 Installing tsuru client........................................... 39 4.2 Deploying................................................ 40 4.3 App-Deploy..............................................
    [Show full text]
  • Rmenu Raspberry PI 3B+ Rmenu 環境構築 Raspberry PI3B+ Rmenu
    RaspberryPi3-20190706 RaspberryPI3 Rmenu VPS Rmenu Raspberry PI 3B+ Rmenu 環境構築 Raspberry PI3B+ Rmenu development term 2019/07/06 1 目次 第１章 はじめに ................................................................................................................................... 4 第２章 構築作業、SD イメージ作成 ................................................................................................... 5 １． Raspbian Buster Lite を ダウンロード ......................................................................... 5 ２． SD メモリカードフォーマッターを取得しインストール ................................................ 6 ３． SD カードをフォーマットします ................................................................................... 8 ４． img ファイルの書き込みプログラムのインストール...................................................... 9 ５． img ファイルの書き込み ................................................................................................ 9 ６． ssh ファイルの書き込み ............................................................................................... 10 ７． SD カードを取り付け、電源を入れる .......................................................................... 11 第３章 最初のログイン ...................................................................................................................... 12 １． ルータが付与した IP アドレスへログイン ................................................................... 12 第４章 Linux raspberrypi 初期設定 ................................................................................................. 13 １． ログイン .....................................................................................................................
    [Show full text]
  • Building Blocks of a Scalable Web Crawler
    Building blocks of a scalable web crawler Marc Seeger Computer Science and Media Stuttgart Media University September 15, 2010 A Thesis Submitted in Fulfilment of the Requirements for a Degree of Master of Science in Computer Science and Media Primary thesis advisor: Prof. Walter Kriha Secondary thesis advisor: Dr. Dries Buytaert I I Abstract The purpose of this thesis was the investigation and implementation of a good architecture for collecting, analysing and managing website data on a scale of millions of domains. The final project is able to automatically collect data about websites and analyse the content management system they are using. To be able to do this efficiently, different possible storage back-ends were examined and a system was implemented that is able to gather and store data at a fast pace while still keeping it searchable. This thesis is a collection of the lessons learned while working on the project combined with the necessary knowledge that went into architectural decisions. It presents an overview of the different infrastructure possibilities and general approaches and as well as explaining the choices that have been made for the implemented system. II Acknowledgements I would like to thank Acquia and Dries Buytaert for allowing me to experience life in the USA while working on a great project. I would also like to thank Chris Brookins for showing me what agile project management is all about. Working at Acquia combined a great infrastructure and atmosphere with a pool of knowledgeable people. Both these things helped me immensely when trying to find and evaluate a matching architecture to this project.
    [Show full text]
  • Open Source Code Acknowledgements & Package List
    Open Source Code Acknowledgements & Package List Copyright © 2010 ‐ 2020 Spectra Logic Corporation. All rights reserved. This appendix contains the licenses and notices for open source software used in the product. If you have any questions or want to receive a copy of the free/open source software to which you are entitled under the applicable free/open source license(s) (such as the Common Development and Distribution License (CCDL)), contact Spectra Logic Technical Support. APACHE Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE‐2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “A S IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. FREEBSD Copyright © 1992‐2020 The FreeBSD Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS ISʹʹ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
    [Show full text]
  • Open Source Licenses 1. Apache-2.0 2. BSD-2-Clause 3
    Open source licenses 1. Apache-2.0 2. BSD-2-Clause 3. BSD-3-Clause 4. BSL-1.0 5. CCPL 6. ISC 7. JSON 8. MIT 9. Zlib Please note, this list may be modified at any time. ------------------------------------------------------------------------------------------------------------------------------------------ Apache License, Version 2.0 adal-node version 0.1.28, Copyright (c) Microsoft Open Technologies, Inc. All rights reserved. adbkit-apkreader version 3.1.2, Copyright © 2013 CyberAgent, Inc., Copyright © 2016 The OpenSTF Project addressable version 2.7.0, Copyright © Bob Aman AWSAPIGateway version 2.6.35, Copyright 2017 - 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved. gson version 2.3.1, Copyright 2008 Google Inc. libphonenumber version 7.0.5, Copyright 2014 The Chromium Authors. All rights reserved. dagger version 2.5, Copyright 2012 The Dagger Authors retrofit1-okhttp3-client version 1.0.2, Copyright 2016 Jake Wharton commons-io version 2.5, Copyright 2002-2021 The Apache Software Foundation okhttp version 3.2.0, Copyright 2019 Square, Inc. okio version 1.6.0, Copyright 2013 Square, Inc. retrofit version 1.9.0, Copyright 2013 Square, Inc. detect-libc version 1.0.3, Copyright 2017 Lovell Fuller ecdsa-sig-formatter versions 1.0.9 and 1.0.11, Copyright 2015 D2L Corporation ejs version 2.5.7, EJS Embedded JavaScript templates copyright 2112 [email protected]. FirebaseAuth version 5.0.1, FirebaseCore version 5.0.4, [email protected], FirebaseInstanceID version 3.1.1, [email protected], Copyright 2018 Google LLC rxjava-async-util version 0.21.0, Copyright 2012 Netflix, Inc. rxjava-debug version 1.0.1, Copyright (c) 2016-present, RxJava Contributors.
    [Show full text]
  • Getting Started with Appium
    E-BOOK Getting Started With Appium RUBY EDITION 2018.1 LEARN MORE AT SAUCELABS.COM BY JONATHAN LIPPS TABLE OF CONTENTS 3 Preface 20 Chapter 4: Writing Your First Test 4 Chapter 1: Introduction 25 Chapter 5: Introduction to Page Objects 4 The Appium Vision 30 Chapter 6: Android Joins the Party 5 The Appium Drivers 35 Chapter 7: Running Local Tests With Rake 6 The Appium Clients 36 Chapter 8: Running Tests in the Sauce Labs Cloud 7 Chapter 2: Getting Set Up 40 Annotating Tests on Sauce 7 Assumed Knowledge 41 Chapter 9: Automating Test Runs with a CI Server 7 iOS-specific System Setup 41 Setting Up Jenkins 7 Android-Specific System Setup 42 Creating an Android Build 8 Appium Setup 44 Creating an iOS Build 10 Ruby Client Setup 44 Running on Sauce 10 Project Setup 45 Jenkins for Production 11 Known Working Versions 46 Chapter 10: Heading Out on Your Own 12 Chapter 3: Exploring Your App 46 Resources 12 Using the Appium Ruby Console 47 Support 17 Using the Appium Desktop Inspector PREFACE This little e-book will help you get started with Appium using the Ruby programming language. It is a complete revision from the ground up of an earlier guide written by Dave Haeffner, who along with Matthew Edwards deserves a lot of thanks for all the work put into the first edition. Appium is an open source project that is always changing, and guides like this one will never be accurate forever. When possible I will indicate which versions of various software are being used, which might help in ensuring reproducibility of the code samples used here.
    [Show full text]
  • Bigfix Inventory Open Source Licenses and Notices
    ---------------------------------- BigFix Inventory 10.0 July 2021 ---------------------------------- ------------------------------------------------------------------------- ------------------------------------------------------------------------- The HCL license agreement and any applicable information on the web download page for HCL products refers Licensee to this file for details concerning notices applicable to code included in the products listed above ("the Program"). Notwithstanding the terms and conditions of any other agreement Licensee may have with HCL or any of its related or affiliated entities (collectively "HCL"), the third party code identified below is subject to the terms and conditions of the HCL license agreement for the Program and not the license terms that may be contained in the notices below. The notices are provided for informational purposes. Please note: This Notices file may identify information that is not used by, or that was not shipped with, the Program as Licensee installed it. IMPORTANT: HCL does not represent or warrant that the information in this NOTICES file is accurate. Third party websites are independent of HCL and HCL does not represent or warrant that the information on any third party website referenced in this NOTICES file is accurate. HCL disclaims any and all liability for errors and omissions or for any damages accruing from the use of this NOTICES file or its contents, including without limitation URLs or references to any third party websites. -------------------------------------------------------------------------
    [Show full text]
  • The Ruby Way: Solutions and Techniques in Ruby Programming
    Praise for The Ruby Way, Third Edition “Sticking to its tried and tested formula of cutting right to the techniques the modern day Rubyist needs to know, the latest edition of The Ruby Way keeps its strong reputation going for the latest generation of the Ruby language.” Peter Cooper Editor of Ruby Weekly “The authors’ excellent work and meticulous attention to detail continues in this lat- est update; this book remains an outstanding reference for the beginning Ruby pro- grammer—as well as the seasoned developer who needs a quick refresh on Ruby. Highly recommended for anyone interested in Ruby programming.” Kelvin Meeks Enterprise Architect Praise for Previous Editions of The Ruby Way “Among other things, this book excels at explaining metaprogramming, one of the most interesting aspects of Ruby. Many of the early ideas for Rails were inspired by the first edition, especially what is now Chapter 11. It puts you on a rollercoaster ride between ‘How could I use this?’ and ‘This is so cool!’ Once you get on that roller- coaster, there’s no turning back.” David Heinemeier Hansson Creator of Ruby on Rails, Founder at Basecamp “The appearance of the second edition of this classic book is an exciting event for Rubyists—and for lovers of superb technical writing in general. Hal Fulton brings a lively erudition and an engaging, lucid style to bear on a thorough and meticulously exact exposition of Ruby. You palpably feel the presence of a teacher who knows a tremendous amount and really wants to help you know it too.” David Alan Black Author of The Well-Grounded Rubyist “This is an excellent resource for gaining insight into how and why Ruby works.
    [Show full text]
  • Abusing XSLT for Practical Attacks White Paper
    WHITE PAPER Abusing XSLT for Practical Attacks White Paper Fernando Arnaboldi IOActive Senior Security Consultant Abstract Over the years, XML has been a rich target for attackers due to flaws in its design as well as implementations. It is a tempting target because it is used by other programming languages to interconnect applications and is supported by web browsers. In this talk, I will demonstrate how to use XSLT to produce documents that are vulnerable to new exploits. XSLT can be leveraged to affect the integrity of arithmetic operations, lead to code logic failure, or cause random values to use the same initialization vector. Error disclosure has always provided valuable information, but thanks to XSLT, it is possible to partially read system files that could disclose service or system passwords. Finally, XSLT can be used to compromise end-user confidentiality by abusing the same-origin policy concept present in web browsers. This document includes proof-of-concept attacks demonstrating XSLT potential to affect production systems, along with recommendations for safe development. © 2015 IOActive, Inc. All Rights Reserved Contents Abstract ......................................................................................................................... 1 Introduction ................................................................................................................... 3 Processors ............................................................................................................................. 3 Gathering
    [Show full text]
  • Imperative Vs. Object- Oriented Paradigms
    11/11/14 CSCI-2325 Object-Oriented Paradigm: Ruby Mohammad T. Irfan Imperative vs. object- oriented paradigms 1 11/11/14 Imperative vs. object-oriented u Imperative u Procedural decomposition u Procedures are all powerful u Data is helpless, at the mercy of procedures u Object-oriented (OO) u Data-centric: data governs the decomposition u Classes – templates/patterns, abstracts away data u Objects – actual things/instantiations of classes u Advantages of OO paradigm u Collaboration u Debugging u Reuse Roadmap u Learn the basics of Ruby today u Investigate Ruby’s object-oriented design principles u Ruby on Rails for web programming 2 11/11/14 Ruby Installation u Several ways to install, as described here: https://www.ruby-lang.org/en/downloads/ u Mac/Linux: Use RVM (https://rvm.io/rvm/install) u Command line$ \curl -sSL https://get.rvm.io | bash -s stable –ruby u Then, follow the instruction given in terminal u To test, commands are: u ruby –v u rvm –v u If you get errors, run the following commands (assuming 2.1.4 is the latest version—look up rvm website for it) u brew update && brew upgrade u rvm reinstall 2.1.4 --disable-binary u Windows: Install Ruby 2.0.0 from RubyInstaller.org http://rubyinstaller.org/downloads/ u Recommended IDE u Aptana Studio 3 http://www.aptana.com/ Ruby resources u Learning u English translation of the creator’s user guide (by Mark Slagell) u http://www.rubyist.net/~slagell/ruby/index.html u Go to reference u Documentation: http://ruby-doc.org/core-2.0.0/ u http://www.tutorialspoint.com/ruby/ u Interactive tutorial using only your web-browser u http://tryruby.org 3 11/11/14 Origin u Designed by Yukihiro Matsumoto (Matz) in early 1990s u Inspired by Perl and Python u Less scripting than Perl u More object-oriented than Python u Happy experience! Quotes u Bruce Stewart (2001): Did you have a guiding philosophy when designing Ruby? u Matz: Yes, it's called the "principle of least surprise." I believe people want to express themselves when they program.
    [Show full text]
  • Pagealyzer Installation and Configuration Manual
    Pagealyzer Installation and Configuration Manual Andrés Sanoja, LIP6 / Université Pierre et Marie Curie Responsables WP : Matthieu CORD/UPMC Stéphane GANÇARSKI/UPMC This work was partially supported by the SCAPE Project. The SCAPE project is co-funded by the European Union under FP7 ICT-2009.4.1 (Grant Agreement number 270137). Enviroment Verification and Configuration The tools pageanalyzer.rb, change_detection.rb and capture.rb are written in Ruby 1.9.1. In the other hand for the change detection process others tools are used that are written in Java, therefore this should be taken into account in the enviroment verification process. The development enviroment was Linux Ubuntu 11.40, the package description is done following its repositories, but in theory should be compatible with debien repos. Ruby Installation We need to be carefull with this step because the software won't work on the 1.8.x versions of Ruby. sudo apt-get install ruby1.9.1-full After that we should check that both, ruby and rubygems, are been properly installed. $ ruby -v 1.9.2p290 (2011-07-09 revision 32533) [i686-linux] It is enough to match the version number. Any doubts there are several tutorials to do this [1]. Now we check the rubygems package manager: $ gem -v 1.3.7 Installing Dependencies After the language and the package manager are properly configured and installed, we may proceed to install the dependencies: sudo gem install --version '= 0.8.6' hpricot sudo apt-get install libxslt-dev libxml2-dev sudo gem install --version '= 1.5.5' nokogiri sudo gem install --version '= 2.0.3' sanitize sudo gem install --version '= 2.25.0' selenium-webdriver sudo apt-get install openjdk-6-jdk sudo apt-get install imagemagick Note1: Installing the selenium-webdriver can cause some warnings in text encoding that should be fine, in almost all the cases.
    [Show full text]
  • Ecosystems in Github and a Method for Ecosystem Identification Using
    Ecosystems in GitHub and a Method for Ecosystem Identification using Reference Coupling Kelly Blincoe, Francis Harrison and Daniela Damian Software Engineering Global InterAction Lab University of Victoria Victoria, BC, Canada Email: [email protected], [email protected], [email protected] Abstract—Software projects are not developed in isolation. To identify technical dependencies, we turn to cross- Recent research has shifted to studying software ecosystems, references on GitHub, a social code hosting service. GitHub communities of projects that depend on each other and are encourages collaboration between users both within and across developed together. However, identifying technical dependencies at the ecosystem level can be challenging. In this paper, we projects through its transparent interface and built-in social 1 propose a new method, known as reference coupling, for detecting features. With GitHub Flavored Markdown , when a user technical dependencies between projects. The method establishes cross-references another repository in a pull request, issue or dependencies through user-specified cross-references between commit comment a link to the other repository is automati- projects. We use our method to identify ecosystems in GitHub- cally created. This introduces a way for developers to bring hosted projects, and we identify several characteristics of the identified ecosystems. We find that most ecosystems are centered awareness across repositories. In this paper, we investigate around one project and are interconnected with other ecosystems. whether these cross-references indicate a technical dependency The predominant type of ecosystems are those that develop between the two repositories by examining a set of these tools to support software development. We also found that the cross-references.
    [Show full text]