jonamiki.com

Leveraging Google’s Tensorflow Machine Learning libraries for item recognition in images is fantastically easy to get going. The below Dockerfile will setup a container with everything required and allow the user to feed a URL to a file for classification:

Dockerfile:
Download raw from here: https://pastebin.com/raw/mdJ225vp

FROM ubuntu:16.04

RUN apt-get update && apt-get install -y openssh-server
RUN mkdir /var/run/sshd
RUN echo 'root:tensorflow' | chpasswd
RUN sed -i 's/PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config

# SSH login fix. Otherwise user is kicked off after login
RUN sed 's@session\s*required\s*pam_loginuid.so@session optional pam_loginuid.so@g' -i /etc/pam.d/sshd

ENV NOTVISIBLE "in users profile"
RUN echo "export VISIBLE=now" >> /etc/profile

EXPOSE 22
CMD ["/usr/sbin/sshd", "-D"]

RUN apt-get install -y python-pip git
RUN pip install numpy tensorflow 

RUN git clone https://github.com/jonas-werner/tf_item_recognition.git

Save the above into a file called “Dockerfile”.
Enter the directory where the Dockerfile is saved and build the Docker image:

docker build -t tf-image_recognition .

Verify the Docker image:

jonas@continuity:~/CODE/tf-image_recognition$ docker image ls
REPOSITORY                       TAG                 IMAGE ID            CREATED             SIZE
tf-image_recognition             latest              cd28f91139a2        6 minutes ago       1.07GB

Run the image. We’ll expose SSH on port 22 on the container as 2222 on the host:

docker run -it -d -P -p 2222:22 tf-image_recognition

Verify the local Docker gateway IP using the container ID (81f13360885f in this case – use “docker ps” to find out):

jonas@continuity:~/CODE/tf-image_recognition$ docker inspect 81f13360885f | grep Gateway
            "Gateway": "172.17.0.1",
            "IPv6Gateway": "",
                    "Gateway": "172.17.0.1",
                    "IPv6Gateway": "",

SSH and execute the image classification script (password: “tensorflow”):

ssh root@172.17.0.1 -p 2222 "wget https://jonamiki.com/wp-content/uploads/2013/07/wpid-IMAG0438_1.jpg; python /tf_item_recognition/classify_image.py --image_file ~/*.jpg; rm ~/*.jpg"

This is the image we’ve pulled down:

And this is the classification result:

motor scooter, scooter (score = 0.89661)
moped (score = 0.04356)
disk brake, disc brake (score = 0.00290)
crash helmet (score = 0.00289)
snowmobile (score = 0.00216)

Not too bad 🙂 Tensorflow accurately detects that the image contains a scooter, a crash helmet and even sees the disk brake on the scooter! Try with any image URL to see what Tensorflow will classify your image as. Have fun!

While I’d normally use “hostnamectl set-hostname ” to modify the hostname of a Linux box, that doesn’t work for Ubuntu 18.04. The hostname will remain unchanged. Instead, modify as follows.

In /etc/cloud/cloud.cfg, modify “preserve_hostname” from “false” to “true”:

vi /etc/cloud/cloud.cfg

Modify hostname to the value you want in /etc/hostname:

vi /etc/hostname

Reboot

The recently released version 1.1 adds streaming Server Configuration File (SCP) support, enhanced RAID creation and many other goodies! See the release notes here for details: Dell EMC Ansible modules version 1.1

Below are some installation instructions (in particular for those who have been using the original Ansible modules).

System used:
CentOS 7.5

Get the new Ansible modules for iDRAC off Github:

git clone https://github.com/dell/Dell-EMC-Ansible-Modules-for-iDRAC.git

Get the Dell EMC OpenManage Python SDK off Github:

git clone https://github.com/dell/omsdk.git

Remove some packages or we will run into errors during the SDK install:
NOTE: This will uninstall Ansible. Backup your /etc/ansible/hosts file prior to Ansible removal!

[jonas@centossysmgmt01 omsdk]$ sudo yum remove python2-enum34.noarch python-enum34.noarch PyYAM

Install the Dell EMC OpenManage Python SDK prerequisites:

[jonas@centossysmgmt01 Redfish]$ cd omsdk/
[jonas@centossysmgmt01 omsdk]$ sudo -H pip install -r requirements-python2x.txt

Reinstall Ansible:

 [jonas@centossysmgmt01 omsdk]$ sudo yum install ansible -y

Install wheel:

 [jonas@centossysmgmt01 omsdk]$ sudo -H pip install wheel

Build .whl file:

 [jonas@centossysmgmt01 omsdk]$ sh ./build.sh 1.2 345

Install the newly built module:

[jonas@centossysmgmt01 omsdk]$ cd dist/
[jonas@centossysmgmt01 dist]$ sudo pip install omsdk-1.2.345_-py2.py3-none-any.whl

Install the new Dell EMC Ansible modules for iDRAC:

[jonas@centossysmgmt01 dist]$ cd ../../Dell-EMC-Ansible-Modules-for-iDRAC/
[jonas@centossysmgmt01 Dell-EMC-Ansible-Modules-for-iDRAC]$
[jonas@centossysmgmt01 Dell-EMC-Ansible-Modules-for-iDRAC]$ sudo python ./install.py
Dell EMC OpenManage Ansible Modules installation has started.
Checking prerequisites...

OpenManage Software Development Kit is installed.
Installing Dell EMC OpenManage Ansible Modules specific folders and files...
SUCCESS: Dell EMC OpenManage Ansible Modules is installed successfully.

All done! The new Ansible modules are installed.

Modifying /etc/ansible/hosts:
The previous version of the Dell EMC Ansible modules for iDRAC required the following format:

[myhosts]
# hostname OOB controller IP/NAME
r730xd baseuri=192.168.1.1
r620 baseuri=192.168.1.2

The new modules require some different variables:

[hosts]
# hostname     OOB controller IP/NAME
r730xd         idrac_ip=192.168.1.1 idrac_user=root idrac_pwd=calvin
r620           idrac_ip=192.168.1.2 idrac_user=root idrac_pwd=calvin
fm120_1a       idrac_ip=192.168.1.11 idrac_user=root idrac_pwd=calvin
fm120_1c       idrac_ip=192.168.1.13 idrac_user=root idrac_pwd=calvin
fm120_1d       idrac_ip=192.168.1.14 idrac_user=root idrac_pwd=calvin
#fm120_2b       idrac_ip=192.168.1.16 idrac_user=root idrac_pwd=calvin
fm120_2c       idrac_ip=192.168.1.17 idrac_user=root idrac_pwd=calvin
#fm120_2d       idrac_ip=192.168.1.18 idrac_user=root idrac_pwd=calvin
fc620           idrac_ip=192.168.1.19 idrac_user=root idrac_pwd=calvin

Trying it out:

Working perfectly 🙂

Using an Arduino UNO and 8 strips of Neopixel ws2812 strips (60 LED/m) I was able to recreate the awesome LED sign created by Josh here: https://youtu.be/k-SYMPO8-f8

Needed some text to test it and picked the cf push haiku by Onsi Fakhouri:

“cf push haiku here is my source code run it on the cloud for me i do not care how”

By default, if the new installer is utilized when deploying Ubuntu server 18.04, the /etc/apt/sources.list will contain only two entries. This doesn’t cover much, so to expand it to be a bit more useful we replace it with:

deb http://jp.archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://jp.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://jp.archive.ubuntu.com/ubuntu/ bionic universe
deb http://jp.archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://jp.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://jp.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://jp.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse

Note that this is for Japan (“jp”). Change this to “us” or similar to match your region if not in Japan.