history command available in Bash is a useful tool, and you probably use it frequently in your daily routine jobs to check the history of the commands executed by the user. In this blog, we will see how an equivalent tool in Chameleon can help you check the experiment setup events you performed on Chameleon.
Jupyter notebooks are a great tool for structuring your computer science experiments on Chameleon because they allow you to iterate on your idea interactively, intuitively, and quickly. But, it may not be obvious how you can leverage this tool for running an experiment...
Did you ever want to create a lease for a specific node? Did you ever want to create a lease that does NOT include a specific node? Ignore a node that has been reserved? Reserve a whole rack perhaps? Or just a few nodes but on the same rack? Then look no farther; here are five tips and tricks for node selection and node avoidance!
Chameleon's DirectStitch capabilities enable isolated direct OSI layer 2 connections between tenant networks and external facilities, including other Chameleon sites.
Many things can go wrong when deploying a large cluster of nodes. We thought it would be helpful for some of you to include some useful tips and tricks for deploying 20+ node clusters when some of the nodes may cause you problems.
Have you ever lost your data after your instance failed, or are your instances failing to launch with a custom image? You may be handling your data incorrectly in the cloud. Read on to learn how to keep your data persistent and your custom images small.
IPv4 address exhaustion, along with natural resources depletion and global warming, has long been recognized as one of the greatest environmental threats facing humanity. Read on to learn how to keep floating IPs afloat!
Chamaleon now supports isloated OpenFlow experiements controlled by users. This tips blog post shows you how to get started using OpenFlow on Chameleon.
Did you ever wonder how much power was consumed by executing a program? The Chameleon team recently implemented a feature that automatically collects power usage data on all low power nodes in the system. Instantaneous power usage data (in watts) are collected through the IPMI interface on the chassis controller for the nodes. This “out-of-band” approach does not consume additional power on the node itself and runs even when the node is powered off. Low power nodes for which power usage data are now being collected include all Intel Atoms, low power Xeons, and ARM64s. In this blog post ...
Did you ever find yourself spending half of your 7 day lease iterating on the environment configuration for your experiment and worried that the remaining 4 days are not enough to run it? If so read on: we are aware that configuring your experimental environment can be a bit of a journey and have packed the system with tools and features that will make it smoother.