Most of the current formatters for Python --- e.g., autopep8, and pep8ify --- are made to remove lint errors from code. This has some obvious limitations. For instance, code that conforms to the PEP 8 guidelines may not be reformatted. But it doesn't mean that the code looks good.

YAPF takes a different approach. It's based off of 'clang-format', developed by Daniel Jasper. In essence, the algorithm takes the code and reformats it to the best formatting that conforms to the style guide, even if the original code didn't violate the style guide. The idea is also similar to the 'gofmt' tool for the Go programming language: end all holy wars about formatting - if the whole codebase of a project is simply piped through YAPF whenever modifications are made, the style remains consistent throughout the project and there's no point arguing about style in every code review.

The ultimate goal is that the code YAPF produces is as good as the code that a programmer would write if they were following the style guide. It takes away some of the drudgery of maintaining your code.

Python is the main scripting language used at Google. This style guide is a list of dos and don'ts for Python programs.

To help you format code correctly, we've created a settings file for Vim[1]. For Emacs, the default settings should be fine.

[1] https://google.github.io/styleguide/google_python_style.vim

On 28 March 2016 Guy Martin set the World Record for the fastest person on a Wall of Death at 78.15 mph. This is the behind the scenes programme aired 27 November 2016 with aerial footage by Kurnia Aerial Photography.

On 28 March 2016 Guy Martin set the World Record for the fastest person on a Wall of Death at 78.15 mph. Kurnia Aerial Photography were commissioned to film for the science and build sequences for the pre-recorded part of the live show that went out on Channel 4. This short clip contains our footage from both outside and inside the hanger.

This is an Ansible role that manages network interface configuration as it is found on Debian/Ubuntu servers

...is a unit testing framework for Shell scripts - namely Bash.

This is a very light weight (as in one file) unit testing library for Bash scripts. It functions similarly to Java's JUnit.

You do not need to touch any of your shell scripts to run unit tests against it. That is to say, that your original source code does not need to know about the BSTL in order for the unit tests to work.

The installation of the Openvswitch on Ubuntu brings an automatic integration into the boot sequence. When Ubuntu is booted, the Openvswitch is also started. Any bridge or port, which has been defined in previous sessions, is restored.
BUT: No L3 interfaces are set up, junk interfaces, which have been defined in previous sessions, are restored.

These instructions will walk you through booting Container Linux via iPXE on real or virtual hardware. By default, this will run Container Linux completely out of RAM. Container Linux can also be installed to disk.

A mininum of 1024M of RAM is required to boot Container Linux via PXE.

Bootkube is a helper tool for launching self-hosted Kubernetes clusters.

When launched, bootkube will act as a temporary Kubernetes control-plane (api-server, scheduler, controller-manager), which operates long enough to bootstrap a replacement self-hosted control-plane.

Additionally, bootkube can be used to generate all of the necessary assets for use in bootstrapping a new cluster. These assets can then be modified to support any additional configuration options.

If you are interested in the design and details see the Kubernetes self-hosted design document which provides an architecture overview.

Every Kubernetes cluster has a cluster root Certificate Authority (CA). The CA is generally used by cluster components to validate the API server’s certificate, by the API server to validate kubelet client certificates, etc. To support this, the CA certificate bundle is distributed to every node in the cluster and is distributed as a secret attached to default service accounts. Optionally, your workloads can use this CA to establish trust. Your application can request a certificate signing using the certificates.k8s.io API using a protocol that is similar to the ACME draft.

Note that the knowledge for each level is cumulative; being at
level n implies that you also know everything from the
levels lower than n.

Tectonic is built on pure-upstream Kubernetes but has an opinion on the best way to install and run a Kubernetes cluster. This project helps you install a Kubernetes cluster the "Tectonic Way". It provides good defaults, enables install automation, and is customizable to meet your infrastructure needs.

Goals of the project:

Installation of Self-Hosted Kubernetes Cluster
Secure by default (use TLS, RBAC by default, OIDC AuthN, etcd)
Automatable install process for scripts and CI/CD
Deploy Tectonic on any infrastructure (Amazon, Azure, OpenStack, GCP, etc)
Runs Tectonic on any OS (Container Linux, RHEL, CentOS, etc)
Customizable and modular (change DNS providers, security settings, etc)
HA by default (deploy all Kubernetes components HA, use etcd Operator)

Note: This repo does not yet haveTectonic is built on pure-upstream Kubernetes but has an opinion on the best way to install and run a Kubernetes cluster. This project helps you install a Kubernetes cluster the "Tectonic Way". It provides good defaults, enables install automation, and is customizable to meet your infrastructure needs.

Goals of the project:

Installation of Self-Hosted Kubernetes Cluster
Secure by default (use TLS, RBAC by default, OIDC AuthN, etcd)
Automatable install process for scripts and CI/CD
Deploy Tectonic on any infrastructure (Amazon, Azure, OpenStack, GCP, etc)
Runs Tectonic on any OS (Container Linux, RHEL, CentOS, etc)
Customizable and modular (change DNS providers, security settings, etc)
HA by default (deploy all Kubernetes components HA, use etcd Operator)

Note: This repo does not yet have all Tectonic Installer features imported. This will happen over the coming weeks as we are able to make some of the surrounding infrastructure public as well. This notice will be removed once the AWS and Baremetal graphical installer code has been fully integrated.

Checkout the ROADMAP for details on where the project is headed. all Tectonic Installer features imported. This will happen over the coming weeks as we are able to make some of the surrounding infrastructure public as well. This notice will be removed once the AWS and Baremetal graphical installer code has been fully integrated.

Checkout the ROADMAP for details on where the project is headed.

This guide walks through a bare-metal installation of Tectonic utilizing PXE-based tools.

One of the most popular SAS 6.0gbps/ SATA III controllers for enthusiasts is the IBM M1015. In its native form, it is a very capable host bus adapter (HBA) based on the LSI SAS2008 chip. With the low price on places such as ebay (see here for an ebay search for the M1015) and an enthusiastic community that has learned to unlock many features, it has quickly become a go-to choice for low-cost SATA III connectivity. This series of articles was written by Pieter Schaar perhaps best known as the one behind laptopvideo2go.com. He has been a regular contributor in the STH forums and has been detailing his learning in threads such as these. I do want to note that these modifications are not endorsed by this site, LSI, IBM or others and the information herein is purely for educational purposes. If you do encounter problems, you are solely responsible for those consequences.