cwielenb/CNCF-Dataset huggingface dataset:
Project: CoreDNS (Orchestration & Management / Coordination & Service Discovery)
File: coredns-1.6.1.md

+++ title = "CoreDNS-1.6.1 Release" description = "CoreDNS-1.6.1 Release Notes." tags = ["Release", "1.6.1", "Notes"] release = "1.6.1" date = 2019-08-02T14:35:47+01:00 author = "coredns" +++ The CoreDNS team has released . This is a small (bug fix) release. Fix a panic in the plugin. The now detects changes in files imported from the main Corefile. increases the paging size when talking to the AWS API, this decreases the chances of getting throttled. Alan, AllenZMC, dzzg, Erik Wilson, Matt Kulka, Miek Gieben, Yong Tang. core: log panics (https://github.com/coredns/coredns/pull/3072) plugin/hosts: create inline map in setup (https://github.com/coredns/coredns/pull/3071) plugin/reload: Graceful reload of imported files (https://github.com/coredns/coredns/pull/3068) plugin/route53: Increase ListResourceRecordSets paging size. (https://github.com/coredns/coredns/pull/3073)
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2016-03-07-mesos-0-27-2-released.md

layout: post title: Apache Mesos 0.27.2 Released permalink: /blog/mesos-0-27-2-released/ published: true post_author: display_name: Michael Park gravatar: 2ab9cab3a7cf782261c583c1f48a81b0 twitter: mcypark tags: Release The latest Mesos release, 0.27.2, is now available for . This release includes fixes and improvements for the following: - Variable shadowing in HookManager::slavePreLaunchDockerHook. - Race condition in libevent poll implementation causes crash. - The "executors" field is exposed under a backwards incompatible schema. - Implement reliable floating point for scalar resources. Full release notes are available in the release . Rolling upgrades from a Mesos 0.27.1 cluster to Mesos 0.27.2 are straightforward. Please refer to the for detailed information on upgrading to Mesos 0.27.2. We encourage you to try out this release and let us know what you think. If you run into any issues, please let us know on the . Thanks to the 4 contributors who made 0.27.2 possible: Alexander Rojas, Kevin Devroede, Michael Park, Neil Conway
Project: BFE (Orchestration & Management / Service Proxy)
File: feature_request.md

name: Feature request about: Suggest an idea for this project title: '' labels: '' assignees: '' Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Describe the solution you'd like A clear and concise description of what you want to happen. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.
Project: Traefik (Orchestration & Management / API Gateway)
File: thank-you.md

title: "Traefik Contribution Documentation" description: "Thank you to all those who have contributed! Traefik Proxy is an open-source project that thrives with the support of our passionate community." You Made It {: .subtitle} Traefik Proxy truly is an , and wouldn't have become what it is today without the help of our , not accounting for people having helped with issues, tests, comments, articles, ... or just enjoy using Traefik Proxy and share with others. So once again, thank you for your invaluable help in making Traefik such a good product! !!! question "Where to Go Next?" If you want to: Propose an idea, request a feature, or report a bug, then read . Discover how to make an efficient contribution, then read . Learn how to build and test Traefik, then the page is for you. Contribute to the documentation, then read the page about . Understand how do we learn about Traefik usage, read the page. Spread the love about Traefik, please check the page. Learn about who are the maintainers and how they work on the project, read the and pages.
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: emr.md

Amazon EMR task type, for operation EMR clusters on AWS and running computing tasks. Using in the background code, to transfer JSON parameters to task object and submit to AWS, Two program types are currently supported: `RUNJOBFLOW` Using submit object `ADDJOBFLOW_STEPS` Using submit object Click `Project Management -> Project Name -> Workflow Definition`, click the `Create Workflow` button to enter the DAG editing page. Drag `AmazonEMR` task from the toolbar to the artboard to complete the creation. Please refer to `Default Task Parameters` section for default parameters. | Parameter | Description | |-|-| | Program Type | Select the program type. If it is `RUNJOBFLOW`, you need to fill in `jobFlowDefineJson`, if it is `ADDJOBFLOW_STEPS`, you need to fill in `stepsDefineJson`. | | jobFlowDefineJson | JSON corresponding to the object, for details refer to . | | stepsDefineJson | JSON corresponding to the object, for details refer to . | This example shows how to create an `EMR` task node of type `RUNJOBFLOW`. Taking the execution of `SparkPi` as an example, the task will create an `EMR` cluster and execute the `SparkPi` sample program. jobFlowDefineJson example ```json { "Name": "SparkPi", "ReleaseLabel": "emr-5.34.0", "Applications": [ { "Name": "Spark" } ], "Instances": { "InstanceGroups": [ { "Name": "Primary node", "InstanceRole": "MASTER", "InstanceType": "m4.xlarge", "InstanceCount": 1 } ], "KeepJobFlowAliveWhenNoSteps": false, "TerminationProtected": false }, "Steps": [ { "Name": "calculate_pi", "ActionOnFailure": "CONTINUE", "HadoopJarStep": { "Jar": "command-runner.jar", "Args": [ "/usr/lib/spark/bin/run-example", "SparkPi", "15" ] } } ], "JobFlowRole": "EMREC2DefaultRole", "ServiceRole": "EMR_DefaultRole" } ``` This example shows how to create an `EMR` task node of type `ADDJOBFLOW_STEPS`. Taking the execution of `SparkPi` as an example, the task will add a `SparkPi` sample program to the running `EMR` cluster. stepsDefineJson example ```json { "JobFlowId": "j-3V628TKAERHP8", "Steps": [ { "Name": "calculate_pi", "ActionOnFailure": "CONTINUE", "HadoopJarStep": { "Jar": "command-runner.jar", "Args": [ "/usr/lib/spark/bin/run-example", "SparkPi", "15" ] } } ] } ``` Failover on EMR Task type has not been implemented. In this time, DolphinScheduler only supports failover on yarn task type . Other task type, such as EMR task, k8s task not ready yet. `stepsDefineJson` A task definition only supports the association of a single step, which can better ensure the reliability of the task state.
Project: Service Mesh Interface (SMI) (Orchestration & Management / Service Mesh)
File: CONTRIBUTING.md

All changes to the spec should be committed to the draft branch. This is the branch where we iterate on the specification until it is ready for a release. The sign-off is a simple line at the end of the explanation for a commit. All commits needs to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material. The rules are pretty simple, if you can certify the below (from ): ```text Developer Certificate of Origin Version 1.1 Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129 Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Developer's Certificate of Origin 1.1 By making a contribution to this project, I certify that: (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. ``` Then you just add a line to every git commit message: ```text Signed-off-by: Joe Smith <joe.smith@example.com> ``` Use your real name (sorry, no pseudonyms or anonymous contributions.) If you set your `user.name` and `user.email` git configs, you can sign your commit automatically with `git commit -s`. Note: If your git config information is set properly then viewing the `git log` information for your commit will look something like this: ```text Author: Joe Smith <joe.smith@example.com> Date: Thu Feb 2 11:41:15 2018 -0800 Update README Signed-off-by: Joe Smith <joe.smith@example.com> ``` Notice the `Author` and `Signed-off-by` lines match. If they don't your PR will be rejected by the automated DCO check. Project maintainership is outlined in the file.
Project: Azure API Management (Orchestration & Management / API Gateway)
File: CONTRIBUTIONS.md

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com. When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the . For more information see the or contact with any additional questions or comments.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: resource-provider.md

title: Apache Mesos - Resource Provider layout: documentation Resource provider is a new abstraction introduced in Mesos 1.5. Leveraging this, the resource-providing part of Mesos can be easily extended and customized. Before 1.5, this part of the logic is hard-coded in the agent. Resource providers are mainly responsible for updating Mesos about available resources and handling operations on those resources. There are two types of resource providers: Local Resource Providers (LRP) and External Resource Providers (ERP). Local resource providers only provide resources that are tied to a particular agent node, while external resource providers provide resources that are not tied to any agent node (a.k.a. global resources). The resource provider API is designed in such a way that it works for both types of resource providers. In Mesos 1.5, only local resource providers are supported. The resource provider API is an HTTP-based API, allowing resource providers to be running outside the Mesos master or agent. This is important for ERPs. There is a component in the agent, called the Resource Provider Manager, that monitors and manages LRPs on that agent. The same component will be running in the master in the future to monitor ERPs.
Project: Contour (Orchestration & Management / Service Proxy)
File: README.md

The script will bring up a local kind cluster. This underlying VM forwards the Envoy ports 80 and 443 locally as port 9080 and 9443. The script installs , which is needed for tests that use TLS. The script builds and installs Contour from the working repository. The script installs a specified Contour release. This is useful for doing upgrade testing. For example: ```bash $ ./install-contour-release.sh v1.9.0 ... ``` To run the tests, it's best to install on your development machine. The e2e tests deploy an Envoy Service and Daemonset in your local kind cluster and run Contour as a process on your local machine, subscribing to k8s resources the tests create. Some configurations are available to modify your test environment: the `CONTOURE2ELOCAL_HOST` environment variable is required and must be set to an address Envoy can use to connect to the Contour xDS server `CONTOURE2ELOCAL_PORT` can be used to customize the port Contour's xDS server will listen on, defaults to `8001` set the `KUBECONFIG` environment variable to provide Contour a specific k8s config to use To run a single test (spec): ``` ginkgo -tags=e2e -r -v -focus "001-required-field-validation" ./test/e2e ``` To run all tests for a given API: ``` ginkgo -tags=e2e -keepGoing -randomizeSuites -randomizeAllSpecs -r -v ./test/e2e/httpproxy ``` To run all tests for all APIs: ``` ginkgo -tags=e2e -keepGoing -randomizeSuites -randomizeAllSpecs -r -v ./test/e2e ```
Project: Prefect (Orchestration & Management / Scheduling & Orchestration)
File: service-accounts.md

description: Workspaces are isolated environments for flows and deployments within Prefect Cloud. tags: UI Prefect Cloud workspaces deployments search: boost: 2 Service accounts enable you to create a Prefect Cloud API key that is not associated with a user account. Service accounts are typically used to configure API access for running workers or executing deployment flow runs on remote infrastructure. Service accounts are non-user accounts that have the following features: Prefect Cloud and permissions Using service account credentials, you can to interact with your Prefect Cloud workspaces without a user having to manually log in from that environment. Service accounts may be created, added to workspaces, have their roles changed, or deleted without affecting other user accounts. Select Service Accounts to view, create, or edit service accounts. Service accounts are created at the account level, but individual workspaces may be shared with the service account. See for more information. !!! tip "Service account credentials" When you create a service account, Prefect Cloud creates a new API key for the account and provides the API configuration command for the execution environment. Save these to a safe location for future use. If the access credentials are lost or compromised, you should regenerate the credentials from the service account page. !!! note "Service account roles" Service accounts are created at the account level, and can then be added to workspaces within the account. You may apply any valid workspace-level role to a service account. Within your account, on the Service Accounts page, select the + icon to create a new service account. You'll be prompted to configure: The service account name. This name must be unique within your account. An expiration date, or the Never Expire option. !!! note "Service account roles" A service account may only be a Member of an account. You may apply any valid workspace-level role to a service account when it is . Select Create to create the new service account. !!! warning Note that an API key cannot be revealed again in the UI after it is generated, so copy the key to a secure location. You can change the API key and expiration for a service account by rotating the API key. Select Rotate API Key from the menu on the left side of the service account's information on this page. Optionally, you can set a period of time for your old service account key to remain active. To delete a service account, select Remove from the menu on the left side of the service account's information.
Project: Traefik (Orchestration & Management / API Gateway)
File: include-api-examples.md

```yaml tab="Docker & Swarm" labels: "traefik.http.routers.api.rule=Host(`traefik.example.com`)" "traefik.http.routers.api.service=api@internal" "traefik.http.routers.api.middlewares=auth" "traefik.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0" ``` ```yaml tab="Docker (Swarm)" deploy: labels: "traefik.http.routers.api.rule=Host(`traefik.example.com`)" "traefik.http.routers.api.service=api@internal" "traefik.http.routers.api.middlewares=auth" "traefik.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0" "traefik.http.services.dummy-svc.loadbalancer.server.port=9999" ``` ```yaml tab="Kubernetes CRD" apiVersion: traefik.io/v1alpha1 kind: IngressRoute metadata: name: traefik-dashboard spec: routes: match: Host(`traefik.example.com`) kind: Rule services: name: api@internal kind: TraefikService middlewares: name: auth apiVersion: traefik.io/v1alpha1 kind: Middleware metadata: name: auth spec: basicAuth: secret: secretName # Kubernetes secret named "secretName" ``` ```yaml tab="Consul Catalog" "traefik.http.routers.api.rule=Host(`traefik.example.com`)" "traefik.http.routers.api.service=api@internal" "traefik.http.routers.api.middlewares=auth" "traefik.http.middlewares.auth.basicauth.users=test:$$apr1$$H6uskkkW$$IgXLP6ewTrSuBkTrqE8wj/,test2:$$apr1$$d9hr9HBB$$4HxwgUir3HP4EsggP/QNo0" ``` ```yaml tab="File (YAML)" http: routers: api: rule: Host(`traefik.example.com`) service: api@internal middlewares: auth middlewares: auth: basicAuth: users: "test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/" "test2:$apr1$d9hr9HBB$4HxwgUir3HP4EsggP/QNo0" ``` ```toml tab="File (TOML)" [http.routers.my-api] rule = "Host(`traefik.example.com`)" service = "api@internal" middlewares = ["auth"] [http.middlewares.auth.basicAuth] users = [ "test:$apr1$H6uskkkW$IgXLP6ewTrSuBkTrqE8wj/", "test2:$apr1$d9hr9HBB$4HxwgUir3HP4EsggP/QNo0", ] ```
Project: Gloo (Orchestration & Management / API Gateway)
File: flaky-tests.md

Tests must account for the eventually consistent nature of Gloo Edge. Writing deterministic end-to-end tests can be challenging, and at times a test will fail in our CI pipeline non-deterministically. We refer to these failures as flakes. We have found the most common flakes occur as a result of: Test pollution: another test in the same suite does not clean up resources Eventual consistency: the test does not wait long enough for resources to be applied and processed correctly The best way to identify that a flake occurred is to run the test locally. First, we recommend to ensure that no other tests are causing an impact, and following the Ginkgo recommendations for . If running the test alone does not reproduce the error, it is likely the failure is caused by test pollution. Repeat the above process, but this time move the focus one level up, so that other tests which may be creating or deleting resources are also run, repeating as necessary until the whole suite is focused. An additional suggestion is to add highly verbose, even excessive, debug logging, and then run the test repeatedly until the flake occurs, use the logging to trace back the buggy behavior If a test failure is deemed to be a flake, we take the following steps: Determine if there is a tracking the existence of that test flake Investigate the flake, timeboxing to a reasonable amount of time (an hour is suggested). Flakes impact the developer experience, and we want to resolve them as soon as they are identified If a solution can not be determined within the timebox, create a GitHub issue to track it If no issue exists, create one and include the `Type: CI Test Flake` . If an issue already exists, add a comment with the logs for the failed run. We use comment frequency as a mechanism for determining frequency of flakes Retry the test (specific steps can be found in a README of each test suite) and comment on the Pull Request with a link to the GitHub issue tracking the flake
Project: Apache Thrift (Orchestration & Management / Remote Procedure Call)
File: debian.md

The following command will install tools and libraries required to build and install the Apache Thrift compiler and C++ libraries on a Debian/Ubuntu Linux based system. sudo apt-get install automake bison flex g++ git libboost-all-dev libevent-dev libssl-dev libtool make pkg-config Debian 7/Ubuntu 12 users need to manually install a more recent version of automake and (for C++ library and test support) boost: wget http://ftp.debian.org/debian/pool/main/a/automake-1.15/automake1.15-3all.deb sudo dpkg -i automake1.15-3all.deb wget http://sourceforge.net/projects/boost/files/boost/1.60.0/boost1600.tar.gz tar xvf boost1600.tar.gz cd boost160_0 ./bootstrap.sh sudo ./b2 install If you would like to build Apache Thrift libraries for other programming languages you may need to install additional packages. The following languages require the specified additional packages: Java packages: gradle (version 8.4) You will also need Java JDK v1.8 or higher. Type javac to see a list of available packages, pick the one you prefer and apt-get install* it (e.g. default-jdk). Ruby ruby-full ruby-dev ruby-rspec rake rubygems bundler Python python-all python-all-dev python-all-dbg Perl libbit-vector-perl libclass-accessor-class-perl Php, install php5-dev php5-cli phpunit C_glib libglib2.0-dev Erlang erlang-base erlang-eunit erlang-dev rebar NetStd apt-transport-https dotnet-sdk-6.0 aspnetcore-runtime-6.0 Thrift Compiler for Windows mingw-w64 mingw-w64-x86-64-dev nsis Rust rustc cargo Haxe haxe Lua lua5.3 liblua5.3-dev NodeJs nodejs npm dotnetcore https://www.microsoft.com/net/learn/get-started/linuxubuntu d-lang curl -fsS https://dlang.org/install.sh | bash -s dmd dart & pub https://www.dartlang.org/install/linux https://www.dartlang.org/tools/pub/installing For more information on the requirements see: For more information on building and installing Thrift see:
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.3.2-released.md

title: "Avro 1.3.2" linkTitle: "Avro 1.3.2" date: 2010-03-31 <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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 https://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 "AS 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. --> Apache Avro 1.3.2 has been released!
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: protobuf.md

https://github.com/google/protobuf ``` curl -L -O https://github.com/google/protobuf/archive/<version>.tar.gz tar -xzf <version>.tar.gz cd <version> ./autogen.sh cd .. tar -czf <version>.tar.gz <version> ``` We bundle 3.5.0 in order to take advantage of C++ move support and additional optimizations.