Google And Friends Add Prometheus To Kubernetes Platform
There are a lot of moving parts in a modern platform, and in this regard, they are no different from the platforms made a generation earlier. But a modern platform has a lot more automation and is handling more dynamic workloads that are popping into and out of existence on different parts of a cluster like quantum particles, and it takes a higher level of sophistication to monitor and manage the stack and the apps running on it.
Frustration with existing open source monitoring tools like Nagios and Ganglia is why the hyperscaler giants created their own tools – Google …
Google And Friends Add Prometheus To Kubernetes Platform was written by Timothy Prickett Morgan at The Next Platform.
python-cloudflare
Using the CloudFlare API via Python
Very early on in the company’s history we decided that everything that CloudFlare does on behalf of its customer-base should be controllable via an API. In fact, when you login to the CloudFlare control panel, you’re really just making API calls to our backend services. Over time that API has matured and improved. We are now on v4 of that API.
The current CloudFlare API is documented here and it’s used by both the CloudFlare control panel and directly by umpteen customers every minute of every day. The new API is designed with a clean naming structure and consistent data representation for data. It’s also extensible.
This blog entry introduces python-cloudflare, a Python wrapper providing full access to the CloudFlare v4 API.
An example
Let’s get right into the thick-of-it with the simplest coding example available to show python-cloudflare in action. This example lists all your domains (zones) and also checks some basic features for each zone.
#!/usr/bin/env python
import CloudFlare
def main():
cf = CloudFlare.CloudFlare()
zones = cf.zones.get(params={'per_page':50})
for zone in zones:
zone_name = zone['name']
zone_id = zone['id']
settings_ipv6 = cf.zones.settings.ipv6.get(zone_id)
ipv6_on = settings_ipv6['value']
Continue readingNext Generation Supercomputing Strikes Data, Compute Balance
Although the future of exascale computing might be garnering the most deadlines in high performance computing, one of the most important stories unfolding in the supercomputing space, at least from a system design angle, is the merging of compute and data-intensive machines.
In many ways, merging both the compute horsepower of today’s top systems with the data-intensive support in terms of data movement, storage, and software is directly at odds with current visions of exascale supercomputers. Hence there appear to be two camps forming on either side of the Top 500 level centers; one that argues strongly in favor of …
Next Generation Supercomputing Strikes Data, Compute Balance was written by Nicole Hemsoth at The Next Platform.
Sunsetting API v1 In Favor Of CloudFlare’s Current Client API: API v4
Today we’re announcing the sunsetting of CloudFlare’s first client API, API v1. Starting November 9th, 2016 at noon Pacific Time (20:00 UTC), CloudFlare will no longer be supporting API v1.
While it is bittersweet to let our first API from CloudFlare’s early days go, we are so excited to show you all of the great things about our latest API: API v4. We’re confident that once you get started using it, you’ll see how easy API v4 makes managing your CloudFlare settings.
(For those of you who are curious where CloudFlare’s API v2 and v3 went, they ran away with IPv5 and PHP 6.)
If you are using API v1 and need to migrate to API v4, we’ve written extensive migration docs here for you to follow. They contain every API call from v1 and their equivalent in v4 side by side.
What will happen after the sunset?
After CloudFlare discontinues support for API v1 in November 2016, any calls to API v1 will return the HTTP status code 410 Gone with the message: “This API has been deprecated in favor of API v4, available at https://api.cloudflare.com.”
What can you do with API v4?
CloudFlare uses Continue reading
Network Break 86: Open Source & The Enterprise; Cloud-Managed Networks
On today's Network Break we recap Greg's Interop panel on open source and the enterprise, examine the impetus behind a $28 million funding round for CoreOS, and more.
The post Network Break 86: Open Source & The Enterprise; Cloud-Managed Networks appeared first on Packet Pushers.
Network Break 86: Open Source & The Enterprise; Cloud-Managed Networks
On today's Network Break we recap Greg's Interop panel on open source and the enterprise, examine the impetus behind a $28 million funding round for CoreOS, and more.
The post Network Break 86: Open Source & The Enterprise; Cloud-Managed Networks appeared first on Packet Pushers.
SigFox vs. LTE-M: IoT’s Competing Connectivity Options
Only 3GPP-based networks are considering SDN and NFV today.
SDN Manages the Electric Grid, Too
A new use case for software defined networking.
Calico + Flannel = Tigera, a New Container Networking Startup
A project called Canal applies overlays to containers.
CoreOS Raises $28M With Backing From Google & Intel
Google Ventures re-ups for CoreOS's Series B.
Back to Basics: Cooling – Part 2
This is the second and final part of the Back to Basics: Cooling – Part 1 article. Here we will cover: Relative Humidity Calculating Cooling Capacity Converting Between Units For handy references and info, download my Power & Cooling Cheat Sheet to the right Approx Reading Time: 10-15 Minutes Relative Humidity The datacenter may seem […]
The post Back to Basics: Cooling – Part 2 appeared first on Packet Pushers.
Back to Basics: Cooling – Part 2
This is the second and final part of the Back to Basics: Cooling – Part 1 article. Here we will cover: Relative Humidity Calculating Cooling Capacity Converting Between Units For handy references and info, download my Power & Cooling Cheat Sheet to the right Approx Reading Time: 10-15 Minutes Relative Humidity The datacenter may seem […]
The post Back to Basics: Cooling – Part 2 appeared first on Packet Pushers.