cwielenb/CNCF-Dataset huggingface dataset:
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-01-14-mesoscon-2015-earlybird-registration-now-open.md

layout: post title: MesosCon Early-Bird Registration Now Open permalink: /blog/mesoscon-2015-earlybird-registration-now-open/ published: true post_author: display_name: Dave Lester twitter: davelester tags: MesosCon, Announcement A limited number of early-bird tickets are now available for , an annual conference organized by the Apache Mesos community. MesosCon brings together users and developers to share and learn about the project and its growing ecosystem, and will take place in Seattle, WA. <blockquote class="twitter-tweet" lang="en"><p>.<a href="https://twitter.com/mesoscon">@MesosCon</a> early-bird registration is now open to the first 140 attendees! Join us! <a href="http://t.co/LcIclfttgq">http://t.co/LcIclfttgq</a> More info: <a href="http://t.co/Dnd5XWhoOH">http://t.co/Dnd5XWhoOH</a></p>&mdash; Apache Mesos (@ApacheMesos) <a href="https://twitter.com/ApacheMesos/status/555445970595368960">January 14, 2015</a></blockquote> to the first 140 attendees / through February 14th, 2015. MesosCon will take place August 20 - 21, 2015 at Sheraton Seattle in Seattle, WA. The cost of early-bird registration is US$299. The standard attendee registration fee will be US$399 (Through July 31, 2015), and late registration US$499 beginning August 1, 2015. Students are eligible for a special registration fee of US$99 (Note that a valid student id will be required at onsite check-in). As part of the registration process, you'll have an opportunity to donate to a which has been established for the conference. MesosCons scholarship program provides support to women, people of color, and people with disabilities who may not otherwise have the opportunity to attend MesosCon for financial reasons. Equal access and diversity are important to MesosCon, and we aim to remove this obstacle for underrepresented attendee groups. We encourage you to donate what you can! If you have any questions regarding the diversity scholarship, please contact . On behalf of the #MesosCon Program Committee, we couldnt be more excited about this years conference and what this means for the open source projects community. We hope that youll join us!
Project: Fluid (Orchestration & Management / Scheduling & Orchestration)
File: SECURITY.md

Join the [kubernetes-security-announce] group for security and vulnerability announcements. You can also subscribe to an RSS feed of the above using . Instructions for reporting a vulnerability can be found on the [Kubernetes Security and Disclosure Information] page. Information about supported Kubernetes versions can be found on the [Kubernetes version and version skew support policy] page on the Kubernetes website.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2015-03-25-mesos-0-22-0-released.md

layout: post title: Apache Mesos 0.22.0 Released permalink: /blog/mesos-0-22-0-released/ published: true post_author: display_name: Niklas Q. Nielsen twitter: quarfot tags: Release The latest Mesos release, 0.22.0, is now available for . This release includes several major features: Disk quota isolation in Mesos containerizer; refer to the to enable disk quota monitoring and enforcement. Support for explicitly sending status updates acknowledgements from schedulers; refer to the for upgrading schedulers. Rate-limiting slave removal, to safeguard against unforeseen bugs which may lead to widespread slave removal. Support for module hooks in task launch sequence. Refer to the for more information. Anonymous modules: a new kind of module that does not receive any callbacks but coexists with its parent process. New service discovery info in task info allows framework users to specify discoverability of tasks for external service discovery systems. Refer to the for more information. Furthermore, many bugs have been fixed in this release. For full release notes with all features and bug fixes, please refer to the . Rolling upgrades may be done seamlessly, however some things have changed in 0.22.0 with regard to external tooling and upgrade paths; please refer to the for detailed information on upgrading to this release from a 0.21.1 cluster. Thanks to the 35 contributors who made 0.22.0 possible: Adam B, Alexander Rojas, Alexander Rukletsov, Ankur Chauhan, Benjamin Hindman, Benjamin Mahler, Bernd Mathiske, Chengwei Yang, Chi Zhang, Christos Kozyrakis, Cody Maloney, Connor Doyle, Dario Rexin, Dave Lester, David Robinson, Dominic Hamon, Evelina Dumitrescu, Gabriel Monroy, Ian Downes, Jake Farrell, Jiang Yan Xu, Jie Yu, Joerg Schad, Joris Van Remoortere, Kapil Arya, Kiyonari Harigae, Michael Park, Niklas Nielsen, Palak Choudhary, R.B. Boyer, Ryan Thomas, Samuel, Till Toenshoff, Timothy Chen and Vinod Kone.
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: task-instance.md

Click `Project Management -> Workflow -> Task Instance` to enter the task instance page, as shown in the figure below, click the name of the workflow instance to jump to the DAG diagram of the workflow instance to view the task status. Click the `View Log` button in the operation column to view the log of the task execution -Switch to the stream task instance page, as shown in the following figure: SavePoint: Click the `SavePoint` button in the operation column to do stream task savepoint. Stop: Click the `Stop` button in the operation column to stop the stream task.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_route.md

title: "glooctl route" weight: 5 subcommands for interacting with routes within virtual services ``` -h, --help help for route --name string name of the resource to read or write -n, --namespace string namespace for reading or writing resources (default "gloo-system") ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - CLI for Gloo - sort routes on an existing virtual service
Project: Serverless Devs (Orchestration & Management / Scheduling & Orchestration)
File: preview.md

title: Preview Command description: 'Preview Command' position: 9 category: 'Commands' The `preview` command is used to preview the rendering results of Serverless Devs Yaml files. - After executing `s preview -h`, you can view the relevant help information: ```shell script Usage: s preview [options] Application preview. Example: $ s preview Document: https://serverless.help/t/s/preview Options: --env <envName> Specify the environment name -h, --help Display help for command ``` | Full Parameter | Abbreviation | Required | Meaning | |--|--|--|--| | env | - | Optional | Specify the environment for execution | By executing the `s preview` command, you can view the rendering results of the resource description Yaml file. For example, if the original content of `s.yaml` is as follows: ```yaml edition: 3.0.0 # Command line YAML specification version, following Semantic Versioning name: framework # Project name access: "default" vars: region: cn-huhehaote resources: next_demo: component: fc3 props: # Component properties region: ${vars.region} function: functionName: "next-start-hello" runtime: "nodejs16" code: ./code environmentVariables: name: ${this.name} code: ${this.props.function.code} demo: component: fc3 props: # Component properties region: ${vars.region} function: functionName: "start-hello" runtime: "nodejs16" code: ./code ``` Then the result of executing `s preview` would be: ```yaml edition: 3.0.0 name: framework access: default vars: region: cn-huhehaote resources: next_demo: component: fc3 props: region: cn-huhehaote function: functionName: next-start-hello runtime: nodejs16 code: ./code environmentVariables: name: next_demo code: ./code demo: component: fc3 props: region: cn-huhehaote function: functionName: start-hello runtime: nodejs16 code: ./code ```
Project: Kubernetes (Orchestration & Management / Scheduling & Orchestration)
File: SUPPORT.md

Welcome to Kubernetes! We use GitHub for tracking bugs and feature requests. This isn't the right place to get support for using Kubernetes, but the following resources are available below, thanks for understanding. The Kubernetes Community is active on Stack Overflow, you can post your questions there: * Here are some tips for . Don't forget to check to see . (): The `#kubernetes-users` and `#kubernetes-novice` channels are usual places where people offer support.
Project: Apache Mesos (Orchestration & Management / Scheduling & Orchestration)
File: 2016-12-20-mesos-0-28-3-released.md

layout: post title: Apache Mesos 0.28.3 Released permalink: /blog/mesos-0-28-3-released/ published: true post_author: display_name: Anand Mazumdar tags: Release The latest Mesos release, 0.28.3, is now available for . This release includes some important bug fixes and improvements on top of 0.28.2. It is highly recommended that users use this version if you are considering using Mesos 0.28. More specifically, this release includes the following major fixes and improvements: - Framework auth fail with timeout error and never get authenticated - Scheduler JNI throws exception when the major versions of JAR and libmesos don't match. - SSL downgrade support will leak sockets in CLOSE_WAIT status. - Quota sorter not updated for resource changes at agent. - SSL-enabled libprocess will leak incoming links to forks. - Task stuck in fetching is not cleaned up after --executorregistrationtimeout. - Stale socket FD usage when using libevent + SSL. - Incremental http parsing of URLs leads to decoder error. - SSL Socket CHECK can fail after socket receives EOF. - Potential FD double close in libevent's - Frameworks may RESERVE for an arbitrary role. - Master CHECK fails during recovery while relinking to other masters. - Master doesn't remove task from pending when it is invalid. - Tasks shouldn't transition from TASKKILLING to TASKRUNNING. - \version uses incorrect MESOS{MAJOR,MINOR,PATCH}_VERSION in libmesos java binding. - Memory leak in the libprocess request decoder. - SSL downgrade path will CHECK-fail when using both temporary and persistent sockets. Full release notes are available in the release Rolling upgrades from a Mesos 0.28.2 cluster to Mesos 0.28.3 are straightforward. Please refer to the for detailed information on upgrading to Mesos 0.28.3. 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 15 contributors who made 0.28.3 possible: Anand Mazumdar, Benjamin Bannier, Benjamin Mahler, David Robinson, Gastn Kleiman, Gilbert Song, Greg Mann, Joris Van Remoortere, Joseph Wu, Neil Conway, Silas Snider, Vinod Kone, Yan Xu, Zhitao Li, Zhou Xing
Project: Avro (Orchestration & Management / Remote Procedure Call)
File: avro-1.10.2-released.md

title: "Avro 1.10.2" linkTitle: "Avro 1.10.2" date: 2021-03-15 <!-- 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.10.2 has been released!
Project: Gloo (Orchestration & Management / API Gateway)
File: circuit_breaker.proto.sk.md

title: "circuit_breaker.proto" weight: 5 <!-- Code generated by solo-kit. DO NOT EDIT. --> CircuitBreakerConfig contains the options for customizing circuit breaking behavior. See the for the meaning of these values. ```yaml "maxConnections": .google.protobuf.UInt32Value "maxPendingRequests": .google.protobuf.UInt32Value "maxRequests": .google.protobuf.UInt32Value "maxRetries": .google.protobuf.UInt32Value ``` | Field | Type | Description | | -- | - | -- | | `maxConnections` | | | | `maxPendingRequests` | | | | `maxRequests` | | | | `maxRetries` | | | <!-- Start of HubSpot Embed Code --> <script type="text/javascript" id="hs-script-loader" async defer src="//js.hs-scripts.com/5130874.js"></script> <!-- End of HubSpot Embed Code -->
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: java.md

This node is for executing java-type tasks and supports using files and jar packages as program entries. Click on `Project Management` -> `Project Name` -> `Workflow Definition`, click on the Create workflow button, go to the DAG edit page: Drag the toolbar's Java task node to the palette. Please refer to `Default Task Parameters` section for default parameters. | Parameter | Description | |--|--| | Module Path | pick Java 9 + 's modularity feature, put all resources into-module-path, and require that the JDK version in your worker supports modularity. | | Main Parameter | Java program main method entry parameter. | | Java VM Parameters | JVM startup parameters. | | Script | You need to write Java code if you use the Java run type. The public class must exist in the code without writing a package statement. | | Resources | External JAR packages or other resource files that are added to the classpath or module path and can be easily retrieved in your JAVA script. | Java type tasks have two modes of execution, here is a demonstration of executing tasks in Java mode. The main configuration parameters are as follows: Run Type Module Path Main Parameters Java VM Parameters Script When you run the task in JAVA execution mode, the public class must exist in the code, and you could omit writing a package statement. For security reasons, when executing JAVA tasks, please use the environment management module to configure the JDK environment, such as `JAVA_HOME` and other environment variables.
Project: Gravitee.io (Orchestration & Management / API Gateway)
File: management-configuration-policies.md

Policies let you customize, enhance API behavior and functionalities. Policies can enforce security, enhance performance, transform request/response and let you implement some logic via the Groovy Policy or dynamic routing policy. Policy can be chained, applied to root path (/) or for specific paths. You can drag and drop policy at the center of the screen to apply policy for a specific path, and the right part of the screen let you configure your policy. The (+) button let you create a new path to specify its behavior via the policies. As an Organization user, you can define platform flows. Each flow will apply to a path in the order defined. You can define a name and a description but if empty the name of the flow will be generated with the operator ("Starts with" or "Equals"), the path and the HTTP methods. You can configure one or more sharding tags. The flows will only be executed on APIs with a sharding tag that matches. If it is empty, the flows will be executed on all the APIs. You can also define an Expression Language (EL) type condition. This expression language is a powerful language that supports querying and manipulating an object graph and is based on the SpEL (Spring Expression Language). This means that you can do everything described in the link. Get the value of the property my-property defined in properties: `{#properties['my-property']}` Get the value of the Content-Type header for an incoming HTTP request: `{#request.headers['content-type']}` Get the second part of the request path: `{#request.paths[1]}` Get the value of the user-id attribute for an incoming HTTP request `{#context.attributes['user-id']}` Get the value of the plan attribute for an incoming HTTP request `{#context.attributes['plan']}`
Project: DolphinScheduler (Orchestration & Management / Scheduling & Orchestration)
File: intro.md

The Resource Center is typically used for uploading files, UDF functions, and task group management. For a stand-alone environment, you can select the local file directory as the upload folder (this operation does not require Hadoop or HDFS deployment). Of course, you can also choose to upload to Hadoop or MinIO cluster. In this case, you need to have Hadoop (2.6+) or MinIO and other related environments.
Project: Gloo (Orchestration & Management / API Gateway)
File: glooctl_debug_yaml.md

title: "glooctl debug yaml" weight: 5 Dump YAML representing the current Gloo state (requires Gloo running on Kubernetes) ``` glooctl debug yaml [flags] ``` ``` -f, --file string file to be read or written to -h, --help help for yaml -n, --namespace string namespace for reading or writing resources (default "gloo-system") ``` ``` -c, --config string set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml") --consul-address string address of the Consul server. Use with --use-consul (default "127.0.0.1:8500") --consul-allow-stale-reads Allows reading using Consul's stale consistency mode. --consul-datacenter string Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul --consul-root-key string key prefix for for Consul key-value storage. (default "gloo") --consul-scheme string URI scheme for the Consul server. Use with --use-consul (default "http") --consul-token string Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul -i, --interactive use interactive mode --kube-context string kube context to use when interacting with kubernetes --kubeconfig string kubeconfig to use, if not standard one --use-consul use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies) ``` - Debug a Gloo resource (requires Gloo running on Kubernetes)
Project: Tengine (Orchestration & Management / Service Proxy)
File: ngx_http_limit_req_module.md

Name ==== limit_req module Description =========== This is the enhanced version of nginx's limit_req module with white list support, and more limit conditions are allowed in a single location. Directives ========== limitreqzone Syntax: limit_req_zone $session_variable1 $session_variable2 ... zone=name_of_zone:size rate=rate | rate=$limit_variable Default: none Context: http Support more than one limit variables. For example: limitreqzone $binaryremoteaddr $uri zone=one:3m rate=1r/s; limitreqzone $binaryremoteaddr $request_uri zone=two:3m rate=1r/s; The last line of the above example indicates a client can access a specific URI only once in a second. Support variable for rate. For example: limitreqzone $binaryremoteaddr zone=three:3m rate=$limit_count; Prior to tengine version 2.3.0, requests with any empty variable are not accounted. From tengine version 2.3.0, requests with all empty variables are not accounted. The variable can contain text, variables, and their combination. For example: limitreqzone $binaryremoteaddr$request_uri zone=two:3m rate=1r/s; limit_req Syntax: limit_req [off] | zone=zone_name [burst=burst] \[forbid_action=action\] \[nodelay\] Default: none Context: http, server, location Multiple limit conditions are allowed in a single block. And all the conditions are examined in order. You can turn this directive on or off (default is on). 'forbid_action' specifies the action URL to redirect. It can be a named location. By default, tengine will return 503. For example: limitreqzone $binaryremoteaddr zone=one:3m rate=1r/s; limitreqzone $binaryremoteaddr $uri zone=two:3m rate=1r/s; limitreqzone $binaryremoteaddr $request_uri zone=three:3m rate=1r/s; limitreqzone $binaryremoteaddr $requesturi zone=four:3m rate=$limitcount; location / { limit_req zone=one burst=5; limitreq zone=two forbidaction=@test1; limitreq zone=three burst=3 forbidaction=@test2; set $limit_count "10r/s"; if ($httpuseragent ~* "Android") { set $limit_count "1r/s"; } if ($httpuseragent ~* "Iphone") { set $limit_count "100r/s"; } limitreq zone=four burst=3 forbidaction=@test2; } location /off { limit_req off; } location @test1 { rewrite ^ /test1.html; } location @test2 { rewrite ^ /test2.html; } limitreqwhitelist Syntax: limit_req_whitelist geo_var_name=var_name geo_var_value=var_value Default: none Context: http, server, location Set the whitelist. This directive needs work with the geo module. The 'geovarname' is the variable name declared in the geo module, 'geovarvalue' is its value. For example: geo $white_ip { ranges; default 0; 127.0.0.1-127.0.0.255 1; } limitreqwhitelist geovarname=whiteip geovar_value=1; It means requests from IP (127.0.0.1 to 127.0.0.255) will be considered safe and let pass.
Project: KubeBrain (Orchestration & Management / Coordination & Service Discovery)
File: CONTRIBUTING.md

We use github for our codebase. You can start by reading . We keep the stable code in branch `main` like `golang.org/x`. Development base on branch `develop`. And we promise the Forward Compatibility by adding new package directory with suffix `v2/v3` when code has break changes. We use as our branch organization, as known as We are using for our public bugs. We keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new task, try to make sure your problem doesn't already exist. Providing a reduced test code is a recommended way for reporting issues. Then can placed in: Just in issues Please do not report the safe disclosure of bugs to public issues. Contact us by Before you submit your Pull Request (PR) consider the following guidelines: Search for an open or closed PR that relates to your submission. You don't want to duplicate existing efforts. Please submit an issue instead of PR if you have a better suggestion for format tools. We won't accept a lot of file changes directly without issue statement and assignment. Be sure that the issue describes the problem you're fixing, or documents the design for the feature you'd like to add. Before we accepting your work, we need to conduct some checks and evaluations. So, It will be better if you can discuss the design with us. the bytedance/kubewharf repo. In your forked repository, make your changes in a new git branch: ``` git checkout -b my-fix-branch develop ``` Create your patch, including appropriate test cases. Follow our . Commit your changes using a descriptive commit message that follows . Adherence to these conventions is necessary because release notes are automatically generated from these messages. Push your branch to GitHub: ``` git push origin my-fix-branch ``` In GitHub, send a pull request to `kubewharf:develop` with a clear and unambiguous title. Our development environment keeps up with . You need fully checking with lint tools before submit your pull request. and You are familiar with Maybe you need familiar with (our default workflow tool). See . Good resources: