The self-hosted web IRC client
Always connected.

Varlink is an interface description format and protocol that aims to make services accessible to both humans and machines in the simplest feasible way.

A varlink interface combines the classic UNIX command line options, STDIN/OUT/ERROR text formats, man pages, service metadata and provides the equivalent over a single file descriptor, a.k.a. “FD3”.

Varlink is plain-text, type-safe, discoverable, self-documenting, remotable, testable, easy to debug. Varlink is accessible from any programming environment. See the Ideals page for more. And everybody likes Screenshots.

Modern, scalable and powerful
Productivity first and foremost
Loved by business, devs and IT

Build and orchestrate integration services, expose new or existing APIs, either cloud or on-premise, and use a wide range of connectors, data formats and protocols.

Zato facilitates intercommunication across applications and data sources spanning your organization's business or technical boundaries and beyond, enabling you to access, design, develop or discover new opportunities and processes.

S3 is a product from Amazon, and as such, it includes “features” that are outside the scope of Swift itself. For example, Swift doesn’t have anything to do with billing, whereas S3 buckets can be tied to Amazon’s billing system. Similarly, log delivery is a service outside of Swift. It’s entirely possible for a Swift deployment to provide that functionality, but it is not part of Swift itself. Likewise, a Swift deployment can provide similar geographic availability as S3, but this is tied to the deployer’s willingness to build the infrastructure and support systems to do so.

General note concerning the use of guest agent interfaces:

"unsupported" is a higher-level error than the errors that individual commands might document. The caller should always be prepared to receive QERR_UNSUPPORTED, even if the given command doesn’t specify it, or doesn’t document any failure mode at all.

Broad, standards-compliant support for both DHCPv4 and DHCPv6

• Free-open source, shared under MPL 2.0 licensing

• Direct address assignment (DHCPv4 and DHCPv6) or DHCPv6 prefix delegation

• Dynamic IP addressing and static host reservations

• Dynamic DNS for updating DNS records as leases are renewed or expired

• Tracking of MAC addresses, even in DHCPv6

• Extend and customize Kea through Hooks

• Add and change subnets and pools without restarting Kea

• Store leases and host reservations in a MySQL, PostgreSQL or Cassandra database rather than a text file

• Replace the entire Kea configuration, or separately manage leases, subnets and host reservations through a REST API

• Comprehensive Developer and Administrator documentation.

• ISC offers commercial 7 x 24 support for Kea, as well as consulting and contract development to assist in implementing Kea, including migration from ISC DHCP.

Kea runs on Linux, BSD, and MacOS, like ISC DHCP. The Kea distribution does not yet include a DHCP client or relay, but because both are standards-based, the ISC DHCP client works fine with the Kea DHCP server. Kea is under active development.

NAPALM (Network Automation and Programmability Abstraction Layer with Multivendor support) is a Python library that implements a set of functions to interact with different network device Operating Systems using a unified API.

NAPALM supports several methods to connect to the devices, to manipulate configurations or to retrieve data.

HashiCorp Vault secures, stores, and tightly controls access to tokens, passwords, certificates, API keys, and other secrets in modern computing. Vault handles leasing, key revocation, key rolling, and auditing. Through a unified API, users can access an encrypted Key/Value store and network encryption-as-a-service, or generate AWS IAM/STS credentials, SQL/NoSQL databases, X.509 certificates, SSH credentials, and more.

phpipam-pyclient is a REST-client CLI tool to interface with phpipam REST API. phpipam-pyclient leverages python fire and requests under the hood, some high level functions have been implementend to allow the user to quickly query certain information about the devices on phpipam. In addition, you can use this library to build your Ansible inventory by filtering a field/column of the devices on phpipam.

This tutorial provides a basic Python programmer’s introduction to working with gRPC.

By walking through this example you’ll learn how to:

Define a service in a .proto file.
Generate server and client code using the protocol buffer compiler.
Use the Python gRPC API to write a simple client and server for your service.

It assumes that you have read the Overview and are familiar with protocol buffers. Note that the example in this tutorial uses the proto3 version of the protocol buffers language, which is currently in beta release: you can find out more in the proto3 language guide and Python generated code guide, and see the release notes for the new version in the protocol buffers Github repository.

This wiki page is a resource for some brainstorming around the possibility of a Python Graph API in the form of an informational PEP, similar to PEP 249, the Python DB API. The goal would be, in other words, to define how a graph (or various kinds of graphs) would be expected to behave (possibly from different perspectives) in order to increase interoperability among graph algorithms. The numeric array interface, recently developed by the Numeric Python community to increase interoperability between array-handling software, illustrates the general idea.

The KV endpoint is used to access Consul's simple key/value store, useful for storing service configuration or other metadata.

DMTF Redfish LogoScalability in today’s data center is increasingly achieved with horizontal, scale-out solutions, which often include large quantities of simple servers. The usage model of scale-out hardware is drastically different than that of traditional enterprise platforms, and requires a new approach to management.

Designed to meet the expectations of end users for simple, modern and secure management of scalable platform hardware, the DMTF’s Redfish is an open industry standard specification and schema that specifies a RESTful interface and utilizes JSON and OData to help customers integrate solutions within their existing tool chains.

Industry feedback has been incorporated into each work-in-progress release and previous versions of the standard have converged into Redfish 1.0.