0 comments on “Podcast – Ash Young talks Everything in your PC is IoT”

Podcast – Ash Young talks Everything in your PC is IoT

Joining us this week is Ash Young, Chief Evangelist of Cachengo and OPNFV Ambassador. Cachengo builds smart, predictive storage for machine learning.

NOTE – We had a microphone problem that is solved at the 9 minute 19 second mark of the podcast. Start there if you find the clicking noise an issue


  • 1 min 34 sec: Time to Change Basic Storage Architecture
    • Converged Protocol Appliances & Nothing has changed form early 90s
  • 7 min 8 sec: Sounds like Hadoop?
    • Underlying hardware still used proprietary protocols
  • 9 min 19 sec: Single Drive Cluster – it’s built?
    • 24 Servers and 24 Drives in a 1U ; has done 48 drives
    • Working on a new design for 96 drives in a 1U
  • 11 min 52 sec: Truly a Distributed Storage Array
    • Storage focused microservers
  • 13 min 24 sec: Limitations in Operations with Hardware
    • Hinders Innovation
  • 15 min 40 sec: Lessons Learned on Managing Devices
    • Over-dependence on tunneling protocols requiring full networking (e.g. VPN)
    • Move to peer-to-peer network slicing
  • 17 min 28 sec: Software Defined Networking Topology
    • Introduce devices to each other and get out of the way
  • 18 min 33sec: Every Storage Node is Part of the Network
    • Moves into a world of networking challenges
    • Ipv4 cannot support this model
  • 21 min 06 sec: Networking Magic in the Model
    • Peer to Peer w/ Broker Introduction and then Removal from Traffic
    • Scale out for Edge Computing Requires this New Model
    • 5G Energy Cost Savings are a Must
  • 27 min 28 sec: Issues of Powering On/Off Machines to Save Money
    • Creating a massive array of smaller GPUs for Machine Learning
    • Build a fast, cheap, lower power storage system to get started in the model
  • 34 min 09 sec: Doesn’t fit the model that Edge infrastructure will be Cloud patterned
    • Rob makes a point to listeners to consider various ideas in future Edge infrastructure
  • 36 min 48 sec: State of Open Source?
    • Consortium’s and open source standards
    • Creating the lowest common denominator free thing so competitors can build differentiation on top of it for revenue
    • Not a fan of open core models
  • 41 min 44 sec: Does Open Source include Supporting Implementation?
    • Look at the old WINE project financing
    • You can’t just deploy people onsite for free<
  • 48 min 24 sec: Wrap-Up

Podcast Guest: Ash Young,Chief Evangelist of Cachengo

Technology leader with over 20 years experience, primarily in storage. Created the first open source NAS (network attached storage) stack, the first unified block/file storage stack for Linux, the first storage management software, and the list goes on.

Since 2012, I have been heavily involved in NFV (Network Functions Virtualization). I wrote a bunch of the standards and was editor for the Compute/Storage Domain in the Infrastructure Working Group for NFV. And then I started up the open source effort to close the gaps for achieving our vision of the NFVI. This was the precursor to OPNFV.

The best way to understand what I do is to imagine being a high-level marketing exec who comes up with a whiz bang product and business idea, including business plan, competitive analysis, MRD, everything, but now comes the hand-off with your engineering organization, only to hear a litany of nos. Well, I got tired of being told “No, it can’t be done” or “No, we don’t know how to do it”, so I started doing it myself. I call this skill “Rapid Prototyping”, and over the years I have found it to be a very missing gap in the product development process. When Marketing comes up with ideas, we need a way to very efficiently validate the technology and business concepts before we commit to a lengthy engineering cycle.

I’m just one person, working in a company of over 180,000 people and in a very dynamic industry. My ability to get creative and to influence businesses is never a dull moment; and I will probably be 100 years old and still writing open source software.

0 comments on “Create your first CentOS 7 Machine on RackN Portal with Digital Rebar Provision”

Create your first CentOS 7 Machine on RackN Portal with Digital Rebar Provision

This is the third blog in a series demonstrating the steps required to complete a series of tasks in the RackN Portal using Digital Rebar Provision.


You will need an account on the RackN Portal with an active Digital Rebar Provision endpoint running. In this How To, I am using Packet.net for my infrastructure as I have no local hardware available to build a local system.

For information on creating a Digital Rebar Provision endpoint and connecting it to a RackN Portal please see these two prior How To blogs:

Step 1 : Create a new Machine on Packet.net

The RackN Portal needs a physical machine for Digital Rebar Provision (DRP) to discover and track in the Machine section of the UX. I am providing steps to create that machine on my Packet.net account:

  • Login into your Packet.net account

In the image above, I show my DRP endpoint (spectordemo-drp-ewr1-00) and a machine (spectordemo-machines-ewr1-01) I created during the Deploy and Test DRP in less than 10 Minutes How To guide. Note – my machines are Type 0 which is about $0.07 an hour to run and the location is at the EWR1 Packet.net data center.

  • Select +Add New to create a new physical machine on Packet.net

Enter the following information for the entry fields on the “Deploy on Demand” page:

  • Hostname: Enter anything you want with a .com (e.g. spectortest.com)
  • Location: Choose the same location of your endpoint – see screen above (e.g. EWR1)
  • Type: Type 0 (cheapest machine ~ $.07 per hour)
  • OS: Custom iPXE ; a new window will appear below that selection area after choosing Custom iPXE
    • Enter the http address of your Endpoint along with “:default.ipxe” at then end so you get “http://#.#.#.#:8091:default.ipxe” (NOTE – the RackN portal address will have :8092, be sure to switch here to :8091)
  • Select the “User Data” button and a new pop-up screen will appear; select SAVE

Packet will then show the new machine as it is setup with the color going from yellow to green during setup. If you click “View Progress” you can monitor the machine start.

Within a few minutes, the machine will switch from yellow to green at which point you will have created a new physical machine to provision with DRP.

Step 2 : Provision a new CentOS 7 Machine from with the RackN Portal 

  • Prepare the Global Workflow

The default Workflow available needs to be removed if you are working with Packet.net machines. If your screen does not look like the final Workflow image shown below, take the following steps:

  1. Delete the Workflow by clicking “Remove” on each step until it is removed
  2. Click the Workflow Wizard to create the 3 Stages shown below

The final Workflow page should look like the image below with three separate Stages and follow-on steps for processing.

  • Confirm new Machine is Visible to RackN Portal

The newly created machine on Packet.net should now be visible in your Bulk Actions page as shown below. The Stage will be set to “sledgehammer-wait and BootEnv to “sledgehammer.”

If the Stage for the new machine is not correct, reboot the machine using the Plugin Action -> powercycle option. The machine should then set to the proper Stage and BootEnv as shown above.

  • Change the Stage and BootEnv to CentOS 7 Settings

Before this final step, be sure to check the machine in the Packet.net settings that it is set for PXE Boot to YES/ON.

In the Bulk Action page, you can change the Stage and BootEnv settings. Select the newly created machine and set the Stages to “centos-7-install” as shown below and then click the 4-arrow button.

Once complete you will see the following setup on the Bulk Action page.

  • Reboot the new Machine in Packet.net

The final step to provision this new machine from DRP is to change the Plugin Action option to “powercycle” and press the hand with figure down. Of course, make sure your machine is selected as show in the image above.

Step 3 : Monitor the Installation of CentOS 7 on the new Machine

To monitor the activity on your new machine you will need to ssh into that machine from a terminal window. To get the ssh key, I selected the new machine in the RackN Portal and grabbed the content from the >_packet/sos: line below. In this case I used 9a17d7d1-fa74-4757-8683-82b57e8e3ed2@sos.sjc1.packet.net.

In the same directory you ran the “pkt-demo” How To in the first blog, you will see a file like “spectordemo-machines-ssh-key” depending on the names you used in the first blog.  Run this command:

ssh -i spectordemo-machines-ssh-key 9a17d7d1-fa74-4757-8683-82b57e8e3ed2@sos.sjc1.packet.net

This will connect to the new machine so you can see activity. For the machine waiting at sledgehammer-wait you will see the following image:

Once the reboot is executed in STEP 3 / (Reboot the New Machine in Packet.net) you will see the machine shut down and disconnect you. Run the same ssh command and you will see this screen while the machine reboots:

The machine will then move into the CentOS 7 install and you will see a sequence of Linux install information such as the following:

This completes the provisioning of a new machine on Packet.net using the RackN Portal Workflow process.

0 comments on “Redefining PXE Boot Provisioning for the Modern Data Center”

Redefining PXE Boot Provisioning for the Modern Data Center

Over the past 20 years, Linux admins have defined provisioning with a limited scope; PXE boot with Cobbler. This approach continues to be popular today even though it only installs an operating system limiting the operators’ ability to move beyond this outdated paradigm

Digital Rebar is the answer operators have been looking for as provisioning has taken on a new role within the data center to include workflow management, infrastructure automation, bare metal, virtual machines inside and outside the firewall as well as the coming need for edge IoT management. The active open source community is expanding the capabilities of provisioning ensuring operators a new foundational technology to rethink how data centers can be managed to meet today’s rapid delivery requirements.

Digital Rebar was architected with the global Cobbler user-base in mind to not only simplify the transition but also offer a set of common packages that are shareable across the community to simplify and automate repetitive tasks; freeing up operators to spend more time focusing on key issues instead of finding new OS packages for example.

I encourage you to take 15 minutes and visit the Digital Rebar community to learn more about this technology and how you can up-level your organization’s capability to automate infrastructure at scale,

%d bloggers like this: