Bug 11192 - Generate development image suitable for all RefKit profiles
Summary: Generate development image suitable for all RefKit profiles
Status: RESOLVED NOTABUG
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-profile-gateway (show other bugs)
Version: 2.3
Hardware: x86 x86_64
: Medium enhancement
Target Milestone: 2.4 M2
Assignee: Jaska Uimonen
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-03-20 22:27 UTC by Ulf Hofemeier
Modified: 2017-05-15 09:52 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulf Hofemeier 2017-03-20 22:27:52 UTC 
I'm using the latest RefKit gateway image with the IoT to Cloud Smart Home demo. Good news is: I'm able to run the IoT REST API service fine with the stock image configuration. Good work guys
Comment 1 Geoffroy Van Cutsem 2017-03-21 14:20:44 UTC 
It looks like there is more details about this here: https://github.com/intel/intel-iot-refkit/issues/84. Which should be used for tracking purposes?
Comment 2 Ulf Hofemeier 2017-03-21 14:50:14 UTC 
For some reason the comment got chopped off. Here's what posted in the GitHub issue tracker for intel-iot-refkit. 

I'm using the latest RefKit gateway image with the IoT to Cloud Smart Home demo. Good news is: I'm able to run the IoT REST API service fine with the stock image configuration. Good work guys
Comment 3 Ulf Hofemeier 2017-03-21 15:23:27 UTC 
I'm using the latest RefKit gateway image with the IoT to Cloud Smart Home demo. Good news is: I'm able to run the IoT REST API service fine with the stock image configuration. Good work guys!

What I would like to do is run the "cloud side" docker app to access the REST API. Unfortunately the requirements to install the binary version of Docker on RefKit aren't met. According to the Docker documentation a few packages are missing in the image:

https://docs.docker.com/engine/installation/binaries/#install-daemon-and-client-binaries-on-linux

What do you think about generating one dev image that can be used to modify and debug code on target regardless of the RefKit profile that is being used? Such an image should contain Autotools, compiler, git, all editors for Linux and header files for all packages, etc. Yes, the image would be rather large, but installing a large image installed once still beats the task to generate image(s) for the purpose of on-target development by far :-)
Comment 4 Ulf Hofemeier 2017-05-10 17:29:39 UTC 
Marking as closed.
Comment 5 Matti-Pekka Sivosuo 2017-05-12 13:48:36 UTC 
(In reply to comment #4)
> Marking as closed.

Could you also share the verification criteria you were using when declaring this as fixed.
Comment 6 Ulf Hofemeier 2017-05-12 15:09:51 UTC 
I can't provide verification criteria for a bug we never really worked on. Let's replace it with a better bug that defines how on-target development using RefKit can be accomplished and determine for what milestone it will be done.
Comment 7 Matti-Pekka Sivosuo 2017-05-15 09:52:21 UTC 
(In reply to comment #6)
> I can't provide verification criteria for a bug we never really worked on.
> Let's replace it with a better bug that defines how on-target development
> using RefKit can be accomplished and determine for what milestone it will be
> done.

Sounds good, please work with Jaska on this. Also couldn't we use this bug for that purpose instead of creating a new one?