From 9528b94a291d648bb62f28826e2b946a229c8cb0 Mon Sep 17 00:00:00 2001 From: Adrian Dudau Date: Wed, 30 Aug 2017 15:45:02 +0200 Subject: Initial commit Signed-off-by: Adrian Dudau --- COPYING.MIT | 17 ++ README | 71 +++++++ conf/layer.conf | 14 ++ conf/template.inteld1521-sdk/bblayers.conf.sample | 24 +++ conf/template.inteld1521-sdk/conf-notes.txt | 2 + conf/template.inteld1521-sdk/local.conf.sample | 239 ++++++++++++++++++++++ conf/template.inteld1521/bblayers.conf.sample | 24 +++ conf/template.inteld1521/conf-notes.txt | 4 + conf/template.inteld1521/local.conf.sample | 237 +++++++++++++++++++++ conf/template.qemux86-64/bblayers.conf.sample | 22 ++ conf/template.qemux86-64/conf-notes.txt | 3 + conf/template.qemux86-64/local.conf.sample | 237 +++++++++++++++++++++ images/build-qcow-image.inc | 10 + images/enea-image-nfv-access-common.inc | 13 ++ images/enea-image-nfv-access-guest-sdk.bb | 13 ++ images/enea-image-nfv-access-guest.bb | 9 + images/enea-image-nfv-access-host-common.inc | 12 ++ images/enea-image-nfv-access-host-odm.bb | 3 + images/enea-image-nfv-access-host-openstack.bb | 17 ++ images/enea-image-nfv-access-host-sdk.bb | 18 ++ images/enea-image-nfv-access-host.bb | 3 + 21 files changed, 992 insertions(+) create mode 100644 COPYING.MIT create mode 100644 README create mode 100644 conf/layer.conf create mode 100644 conf/template.inteld1521-sdk/bblayers.conf.sample create mode 100644 conf/template.inteld1521-sdk/conf-notes.txt create mode 100644 conf/template.inteld1521-sdk/local.conf.sample create mode 100644 conf/template.inteld1521/bblayers.conf.sample create mode 100644 conf/template.inteld1521/conf-notes.txt create mode 100644 conf/template.inteld1521/local.conf.sample create mode 100644 conf/template.qemux86-64/bblayers.conf.sample create mode 100644 conf/template.qemux86-64/conf-notes.txt create mode 100644 conf/template.qemux86-64/local.conf.sample create mode 100644 images/build-qcow-image.inc create mode 100644 images/enea-image-nfv-access-common.inc create mode 100644 images/enea-image-nfv-access-guest-sdk.bb create mode 100644 images/enea-image-nfv-access-guest.bb create mode 100644 images/enea-image-nfv-access-host-common.inc create mode 100644 images/enea-image-nfv-access-host-odm.bb create mode 100644 images/enea-image-nfv-access-host-openstack.bb create mode 100644 images/enea-image-nfv-access-host-sdk.bb create mode 100644 images/enea-image-nfv-access-host.bb diff --git a/COPYING.MIT b/COPYING.MIT new file mode 100644 index 0000000..89de354 --- /dev/null +++ b/COPYING.MIT @@ -0,0 +1,17 @@ +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in +all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN +THE SOFTWARE. diff --git a/README b/README new file mode 100644 index 0000000..de54856 --- /dev/null +++ b/README @@ -0,0 +1,71 @@ +meta-el-nfv-access +=================================================================== + +This layer contains distro customizations specific to the Enea Linux +NFV Access platform releases. + +Dependencies +============ + +This layer depends on: + + URI: git://git.yoctoproject.org/poky + branch: pyro + + URI: git://git.enea.com/linux/meta-el-common + branch: pyro + + URI: git://git.enea.com/linux/meta-enea-virtualization + branch: pyro + + URI: git://git.enea.com/linux/meta-cloud-services/meta-openstack + branch: pyro + + + +Source code +=========== + +git://git.enea.com/linux/meta-el-nfv-access.git + + +Patches +======= + +Please submit any patches against the el-nfv-access layer to the +following mailing list: linux@lists.enea.com + +Maintainers: +Adrian Dudau +Martin Borg + +Table +================= + + I. Adding the el-nfv-access layer to your build + II. Misc + + +I. Adding the el-nfv-access layer to your build +================================================= + +In order to use this layer, you need to make the build system aware of +it. + +Assuming the el-nfv-access layer exists at the top-level of your +yocto build tree, you can add it to the build system by adding the +location of the el-nfv-access layer to bblayers.conf, along with any +other layers needed. e.g.: + + + BBLAYERS ?= " \ + /path/to/yocto/meta \ + /path/to/yocto/meta-poky \ + /path/to/yocto/meta-el-common \ + /path/to/yocto/meta-enea-virtualization \ + /path/to/yocto/meta-cloud-services/meta-openstack \ + /path/to/yocto/meta-el-nfv-access \ + " + +II. Misc +======== diff --git a/conf/layer.conf b/conf/layer.conf new file mode 100644 index 0000000..04b8042 --- /dev/null +++ b/conf/layer.conf @@ -0,0 +1,14 @@ +# We have a conf and classes directory, add to BBPATH +BBPATH .= ":${LAYERDIR}" + +# We have recipes-* directories, add to BBFILES +BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \ + ${LAYERDIR}/images/* \ + ${LAYERDIR}/packagegroups/* \ + ${LAYERDIR}/recipes-*/*/*.bbappend" + +BBFILE_COLLECTIONS += "el-nfv-access" +BBFILE_PATTERN_el-nfv-access = "^${LAYERDIR}/" +BBFILE_PRIORITY_el-nfv-access = "7" +LAYERDEPENDS_el-nfv-access = "el-common enea-virtualization openstack-layer" +BBMASK += "/meta-cloud-services/meta-openstack/recipes-kernel/linux/" diff --git a/conf/template.inteld1521-sdk/bblayers.conf.sample b/conf/template.inteld1521-sdk/bblayers.conf.sample new file mode 100644 index 0000000..886166e --- /dev/null +++ b/conf/template.inteld1521-sdk/bblayers.conf.sample @@ -0,0 +1,24 @@ +# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf +# changes incompatibly +POKY_BBLAYERS_CONF_VERSION = "2" + +BBPATH = "${TOPDIR}" +BBFILES ?= "" + +BBLAYERS ?= " \ + ##OEROOT##/meta \ + ##OEROOT##/meta-el-common \ + ##OEROOT##/meta-el-nfv-access \ + ##OEROOT##/meta-enea-virtualization \ + ##OEROOT##/meta-enea-bsp-x86 \ + ##OEROOT##/meta-intel \ + ##OEROOT##/meta-openembedded/meta-oe \ + ##OEROOT##/meta-openembedded/meta-networking \ + ##OEROOT##/meta-openembedded/meta-filesystems \ + ##OEROOT##/meta-openembedded/meta-python \ + ##OEROOT##/meta-openembedded/meta-webserver \ + ##OEROOT##/meta-virtualization \ + ##OEROOT##/meta-poky \ + ##OEROOT##/meta-cloud-services \ + ##OEROOT##/meta-cloud-services/meta-openstack \ + " diff --git a/conf/template.inteld1521-sdk/conf-notes.txt b/conf/template.inteld1521-sdk/conf-notes.txt new file mode 100644 index 0000000..3dd7ea1 --- /dev/null +++ b/conf/template.inteld1521-sdk/conf-notes.txt @@ -0,0 +1,2 @@ +Common targets are: + enea-image-nfv-access-host-sdk diff --git a/conf/template.inteld1521-sdk/local.conf.sample b/conf/template.inteld1521-sdk/local.conf.sample new file mode 100644 index 0000000..a156f32 --- /dev/null +++ b/conf/template.inteld1521-sdk/local.conf.sample @@ -0,0 +1,239 @@ +# +# This file is your local configuration file and is where all local user settings +# are placed. The comments in this file give some guide to the options a new user +# to the system might want to change but pretty much any configuration option can +# be set in this file. More adventurous users can look at local.conf.extended +# which contains other examples of configuration which can be placed in this file +# but new users likely won't need any of them initially. +# +# Lines starting with the '#' character are commented out and in some cases the +# default values are provided as comments to show people example syntax. Enabling +# the option is a question of removing the # character and making any change to the +# variable as required. + +# +# Machine Selection +# +# You need to select a specific machine to target the build with. There are a selection +# of emulated machines available which can boot and run in the QEMU emulator: +# +#MACHINE ?= "qemuarm" +#MACHINE ?= "qemuarm64" +#MACHINE ?= "qemumips" +#MACHINE ?= "qemumips64" +#MACHINE ?= "qemuppc" +#MACHINE ?= "qemux86" +#MACHINE ?= "qemux86-64" +# +# There are also the following hardware board target machines included for +# demonstration purposes: +# +#MACHINE ?= "beaglebone" +#MACHINE ?= "genericx86" +#MACHINE ?= "genericx86-64" +#MACHINE ?= "mpc8315e-rdb" +#MACHINE ?= "edgerouter" +# +# This sets the default machine to be qemux86 if no other machine is selected: +MACHINE ?= "inteld1521" + +# +# Where to place downloads +# +# During a first build the system will download many different source code tarballs +# from various upstream projects. This can take a while, particularly if your network +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you +# can preserve this directory to speed up this part of subsequent builds. This directory +# is safe to share between multiple builds on the same machine too. +# +# The default is a downloads directory under TOPDIR which is the build directory. +# +#DL_DIR ?= "${TOPDIR}/downloads" + +# +# Where to place shared-state files +# +# BitBake has the capability to accelerate builds based on previously built output. +# This is done using "shared state" files which can be thought of as cache objects +# and this option determines where those files are placed. +# +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate +# from these files if no changes were made to the configuration. If changes were made +# to the configuration, only shared state files where the state was still valid would +# be used (done using checksums). +# +# The default is a sstate-cache directory under TOPDIR. +# +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" + +# +# Where to place the build output +# +# This option specifies where the bulk of the building work should be done and +# where BitBake should place its temporary files and output. Keep in mind that +# this includes the extraction and compilation of many applications and the toolchain +# which can use Gigabytes of hard disk space. +# +# The default is a tmp directory under TOPDIR. +# +#TMPDIR = "${TOPDIR}/tmp" + +# +# Default policy config +# +# The distribution setting controls which policy settings are used as defaults. +# The default value is fine for general Yocto project use, at least initially. +# Ultimately when creating custom policy, people will likely end up subclassing +# these defaults. +# +DISTRO ?= "enea" +# As an example of a subclass there is a "bleeding" edge policy configuration +# where many versions are set to the absolute latest code from the upstream +# source control systems. This is just mentioned here as an example, its not +# useful to most new users. +# DISTRO ?= "poky-bleeding" + +# +# Package Management configuration +# +# This variable lists which packaging formats to enable. Multiple package backends +# can be enabled at once and the first item listed in the variable will be used +# to generate the root filesystems. +# Options are: +# - 'package_deb' for debian style deb files +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) +# - 'package_rpm' for rpm style packages +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" +# We default to rpm: +PACKAGE_CLASSES ?= "package_deb" + +# +# SDK/ADT target architecture +# +# This variable specifies the architecture to build SDK/ADT items for and means +# you can build the SDK packages for architectures other than the machine you are +# running the build on (i.e. building i686 packages on an x86_64 host). +# Supported values are i686 and x86_64 +#SDKMACHINE ?= "i686" + +# +# Extra image configuration defaults +# +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated +# images. Some of these options are added to certain image types automatically. The +# variable can contain the following options: +# "dbg-pkgs" - add -dbg packages for all installed packages +# (adds symbol information for debugging/profiling) +# "dev-pkgs" - add -dev packages for all installed packages +# (useful if you want to develop against libs in the image) +# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages +# (useful if you want to run the package test suites) +# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) +# "tools-debug" - add debugging tools (gdb, strace) +# "eclipse-debug" - add Eclipse remote debugging support +# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) +# "debug-tweaks" - make an image suitable for development +# e.g. ssh root access has a blank password +# There are other application targets that can be used here too, see +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. +# We default to enabling the debugging tweaks. +EXTRA_IMAGE_FEATURES = "debug-tweaks" + +# +# Additional image features +# +# The following is a list of additional classes to use when building images which +# enable extra features. Some available options which can be included in this variable +# are: +# - 'buildstats' collect build statistics +# - 'image-mklibs' to reduce shared library files size for an image +# - 'image-prelink' in order to prelink the filesystem image +# - 'image-swab' to perform host system intrusion detection +# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink +# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended +USER_CLASSES ?= "buildstats image-mklibs image-prelink" + +# +# Runtime testing of images +# +# The build system can test booting virtual machine images under qemu (an emulator) +# after any root filesystems are created and run tests against those images. To +# enable this uncomment this line. See classes/testimage(-auto).bbclass for +# further details. +#TEST_IMAGE = "1" +# +# Interactive shell configuration +# +# Under certain circumstances the system may need input from you and to do this it +# can launch an interactive shell. It needs to do this since the build is +# multithreaded and needs to be able to handle the case where more than one parallel +# process may require the user's attention. The default is iterate over the available +# terminal types to find one that works. +# +# Examples of the occasions this may happen are when resolving patches which cannot +# be applied, to use the devshell or the kernel menuconfig +# +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none +# Note: currently, Konsole support only works for KDE 3.x due to the way +# newer Konsole versions behave +#OE_TERMINAL = "auto" +# By default disable interactive patch resolution (tasks will just fail instead): +PATCHRESOLVE = "noop" + +# +# Disk Space Monitoring during the build +# +# Monitor the disk space during the build. If there is less that 1GB of space or less +# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully +# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort +# of the build. The reason for this is that running completely out of space can corrupt +# files and damages the build in ways which may not be easily recoverable. +# It's necesary to monitor /tmp, if there is no space left the build will fail +# with very exotic errors. +BB_DISKMON_DIRS = "\ + STOPTASKS,${TMPDIR},1G,100K \ + STOPTASKS,${DL_DIR},1G,100K \ + STOPTASKS,${SSTATE_DIR},1G,100K \ + STOPTASKS,/tmp,100M,100K \ + ABORT,${TMPDIR},100M,1K \ + ABORT,${DL_DIR},100M,1K \ + ABORT,${SSTATE_DIR},100M,1K \ + ABORT,/tmp,10M,1K" + +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can +# used to accelerate build time. This variable can be used to configure the system +# to search other mirror locations for these objects before it builds the data itself. +# +# This can be a filesystem directory, or a remote url such as http or ftp. These +# would contain the sstate-cache results from previous builds (possibly from other +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the +# cache locations to check for the shared objects. +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH +# at the end as shown in the examples below. This will be substituted with the +# correct path within the directory structure. +#SSTATE_MIRRORS ?= "\ +#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ +#file://.* file:///some/local/dir/sstate/PATH" + + +# +# Qemu configuration +# +# By default qemu will build with a builtin VNC server where graphical output can be +# seen. The two lines below enable the SDL backend too. By default libsdl-native will +# be built, if you want to use your host's libSDL instead of the minimal libsdl built +# by libsdl-native then uncomment the ASSUME_PROVIDED line below. +PACKAGECONFIG_append_pn-qemu-native = " sdl" +PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" +#ASSUME_PROVIDED += "libsdl-native" + +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to +# track the version of this file when it was generated. This can safely be ignored if +# this doesn't mean anything to you. +CONF_VERSION = "1" + +PREFERRED_PROVIDER_virtual/kernel = "linux-intel-sdk" diff --git a/conf/template.inteld1521/bblayers.conf.sample b/conf/template.inteld1521/bblayers.conf.sample new file mode 100644 index 0000000..886166e --- /dev/null +++ b/conf/template.inteld1521/bblayers.conf.sample @@ -0,0 +1,24 @@ +# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf +# changes incompatibly +POKY_BBLAYERS_CONF_VERSION = "2" + +BBPATH = "${TOPDIR}" +BBFILES ?= "" + +BBLAYERS ?= " \ + ##OEROOT##/meta \ + ##OEROOT##/meta-el-common \ + ##OEROOT##/meta-el-nfv-access \ + ##OEROOT##/meta-enea-virtualization \ + ##OEROOT##/meta-enea-bsp-x86 \ + ##OEROOT##/meta-intel \ + ##OEROOT##/meta-openembedded/meta-oe \ + ##OEROOT##/meta-openembedded/meta-networking \ + ##OEROOT##/meta-openembedded/meta-filesystems \ + ##OEROOT##/meta-openembedded/meta-python \ + ##OEROOT##/meta-openembedded/meta-webserver \ + ##OEROOT##/meta-virtualization \ + ##OEROOT##/meta-poky \ + ##OEROOT##/meta-cloud-services \ + ##OEROOT##/meta-cloud-services/meta-openstack \ + " diff --git a/conf/template.inteld1521/conf-notes.txt b/conf/template.inteld1521/conf-notes.txt new file mode 100644 index 0000000..53ebbe6 --- /dev/null +++ b/conf/template.inteld1521/conf-notes.txt @@ -0,0 +1,4 @@ +Common targets are: + enea-image-nfv-access-host + enea-image-nfv-access-host-odm + enea-image-nfv-access-host-openstack diff --git a/conf/template.inteld1521/local.conf.sample b/conf/template.inteld1521/local.conf.sample new file mode 100644 index 0000000..1a7e915 --- /dev/null +++ b/conf/template.inteld1521/local.conf.sample @@ -0,0 +1,237 @@ +# +# This file is your local configuration file and is where all local user settings +# are placed. The comments in this file give some guide to the options a new user +# to the system might want to change but pretty much any configuration option can +# be set in this file. More adventurous users can look at local.conf.extended +# which contains other examples of configuration which can be placed in this file +# but new users likely won't need any of them initially. +# +# Lines starting with the '#' character are commented out and in some cases the +# default values are provided as comments to show people example syntax. Enabling +# the option is a question of removing the # character and making any change to the +# variable as required. + +# +# Machine Selection +# +# You need to select a specific machine to target the build with. There are a selection +# of emulated machines available which can boot and run in the QEMU emulator: +# +#MACHINE ?= "qemuarm" +#MACHINE ?= "qemuarm64" +#MACHINE ?= "qemumips" +#MACHINE ?= "qemumips64" +#MACHINE ?= "qemuppc" +#MACHINE ?= "qemux86" +#MACHINE ?= "qemux86-64" +# +# There are also the following hardware board target machines included for +# demonstration purposes: +# +#MACHINE ?= "beaglebone" +#MACHINE ?= "genericx86" +#MACHINE ?= "genericx86-64" +#MACHINE ?= "mpc8315e-rdb" +#MACHINE ?= "edgerouter" +# +# This sets the default machine to be qemux86 if no other machine is selected: +MACHINE ?= "inteld1521" + +# +# Where to place downloads +# +# During a first build the system will download many different source code tarballs +# from various upstream projects. This can take a while, particularly if your network +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you +# can preserve this directory to speed up this part of subsequent builds. This directory +# is safe to share between multiple builds on the same machine too. +# +# The default is a downloads directory under TOPDIR which is the build directory. +# +#DL_DIR ?= "${TOPDIR}/downloads" + +# +# Where to place shared-state files +# +# BitBake has the capability to accelerate builds based on previously built output. +# This is done using "shared state" files which can be thought of as cache objects +# and this option determines where those files are placed. +# +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate +# from these files if no changes were made to the configuration. If changes were made +# to the configuration, only shared state files where the state was still valid would +# be used (done using checksums). +# +# The default is a sstate-cache directory under TOPDIR. +# +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" + +# +# Where to place the build output +# +# This option specifies where the bulk of the building work should be done and +# where BitBake should place its temporary files and output. Keep in mind that +# this includes the extraction and compilation of many applications and the toolchain +# which can use Gigabytes of hard disk space. +# +# The default is a tmp directory under TOPDIR. +# +#TMPDIR = "${TOPDIR}/tmp" + +# +# Default policy config +# +# The distribution setting controls which policy settings are used as defaults. +# The default value is fine for general Yocto project use, at least initially. +# Ultimately when creating custom policy, people will likely end up subclassing +# these defaults. +# +DISTRO ?= "enea" +# As an example of a subclass there is a "bleeding" edge policy configuration +# where many versions are set to the absolute latest code from the upstream +# source control systems. This is just mentioned here as an example, its not +# useful to most new users. +# DISTRO ?= "poky-bleeding" + +# +# Package Management configuration +# +# This variable lists which packaging formats to enable. Multiple package backends +# can be enabled at once and the first item listed in the variable will be used +# to generate the root filesystems. +# Options are: +# - 'package_deb' for debian style deb files +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) +# - 'package_rpm' for rpm style packages +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" +# We default to rpm: +PACKAGE_CLASSES ?= "package_deb" + +# +# SDK/ADT target architecture +# +# This variable specifies the architecture to build SDK/ADT items for and means +# you can build the SDK packages for architectures other than the machine you are +# running the build on (i.e. building i686 packages on an x86_64 host). +# Supported values are i686 and x86_64 +#SDKMACHINE ?= "i686" + +# +# Extra image configuration defaults +# +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated +# images. Some of these options are added to certain image types automatically. The +# variable can contain the following options: +# "dbg-pkgs" - add -dbg packages for all installed packages +# (adds symbol information for debugging/profiling) +# "dev-pkgs" - add -dev packages for all installed packages +# (useful if you want to develop against libs in the image) +# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages +# (useful if you want to run the package test suites) +# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) +# "tools-debug" - add debugging tools (gdb, strace) +# "eclipse-debug" - add Eclipse remote debugging support +# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) +# "debug-tweaks" - make an image suitable for development +# e.g. ssh root access has a blank password +# There are other application targets that can be used here too, see +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. +# We default to enabling the debugging tweaks. +EXTRA_IMAGE_FEATURES = "debug-tweaks" + +# +# Additional image features +# +# The following is a list of additional classes to use when building images which +# enable extra features. Some available options which can be included in this variable +# are: +# - 'buildstats' collect build statistics +# - 'image-mklibs' to reduce shared library files size for an image +# - 'image-prelink' in order to prelink the filesystem image +# - 'image-swab' to perform host system intrusion detection +# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink +# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended +USER_CLASSES ?= "buildstats image-mklibs image-prelink" + +# +# Runtime testing of images +# +# The build system can test booting virtual machine images under qemu (an emulator) +# after any root filesystems are created and run tests against those images. To +# enable this uncomment this line. See classes/testimage(-auto).bbclass for +# further details. +#TEST_IMAGE = "1" +# +# Interactive shell configuration +# +# Under certain circumstances the system may need input from you and to do this it +# can launch an interactive shell. It needs to do this since the build is +# multithreaded and needs to be able to handle the case where more than one parallel +# process may require the user's attention. The default is iterate over the available +# terminal types to find one that works. +# +# Examples of the occasions this may happen are when resolving patches which cannot +# be applied, to use the devshell or the kernel menuconfig +# +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none +# Note: currently, Konsole support only works for KDE 3.x due to the way +# newer Konsole versions behave +#OE_TERMINAL = "auto" +# By default disable interactive patch resolution (tasks will just fail instead): +PATCHRESOLVE = "noop" + +# +# Disk Space Monitoring during the build +# +# Monitor the disk space during the build. If there is less that 1GB of space or less +# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully +# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort +# of the build. The reason for this is that running completely out of space can corrupt +# files and damages the build in ways which may not be easily recoverable. +# It's necesary to monitor /tmp, if there is no space left the build will fail +# with very exotic errors. +BB_DISKMON_DIRS = "\ + STOPTASKS,${TMPDIR},1G,100K \ + STOPTASKS,${DL_DIR},1G,100K \ + STOPTASKS,${SSTATE_DIR},1G,100K \ + STOPTASKS,/tmp,100M,100K \ + ABORT,${TMPDIR},100M,1K \ + ABORT,${DL_DIR},100M,1K \ + ABORT,${SSTATE_DIR},100M,1K \ + ABORT,/tmp,10M,1K" + +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can +# used to accelerate build time. This variable can be used to configure the system +# to search other mirror locations for these objects before it builds the data itself. +# +# This can be a filesystem directory, or a remote url such as http or ftp. These +# would contain the sstate-cache results from previous builds (possibly from other +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the +# cache locations to check for the shared objects. +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH +# at the end as shown in the examples below. This will be substituted with the +# correct path within the directory structure. +#SSTATE_MIRRORS ?= "\ +#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ +#file://.* file:///some/local/dir/sstate/PATH" + + +# +# Qemu configuration +# +# By default qemu will build with a builtin VNC server where graphical output can be +# seen. The two lines below enable the SDL backend too. By default libsdl-native will +# be built, if you want to use your host's libSDL instead of the minimal libsdl built +# by libsdl-native then uncomment the ASSUME_PROVIDED line below. +PACKAGECONFIG_append_pn-qemu-native = " sdl" +PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" +#ASSUME_PROVIDED += "libsdl-native" + +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to +# track the version of this file when it was generated. This can safely be ignored if +# this doesn't mean anything to you. +CONF_VERSION = "1" diff --git a/conf/template.qemux86-64/bblayers.conf.sample b/conf/template.qemux86-64/bblayers.conf.sample new file mode 100644 index 0000000..3ef85d8 --- /dev/null +++ b/conf/template.qemux86-64/bblayers.conf.sample @@ -0,0 +1,22 @@ +# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf +# changes incompatibly +POKY_BBLAYERS_CONF_VERSION = "2" + +BBPATH = "${TOPDIR}" +BBFILES ?= "" + +BBLAYERS ?= " \ + ##OEROOT##/meta \ + ##OEROOT##/meta-el-common \ + ##OEROOT##/meta-el-nfv-access \ + ##OEROOT##/meta-enea-virtualization \ + ##OEROOT##/meta-enea-bsp-x86 \ + ##OEROOT##/meta-intel \ + ##OEROOT##/meta-openembedded/meta-oe \ + ##OEROOT##/meta-openembedded/meta-networking \ + ##OEROOT##/meta-openembedded/meta-filesystems \ + ##OEROOT##/meta-openembedded/meta-python \ + ##OEROOT##/meta-virtualization \ + ##OEROOT##/meta-poky \ + ##OEROOT##/meta-cloud-services/meta-openstack \ + " diff --git a/conf/template.qemux86-64/conf-notes.txt b/conf/template.qemux86-64/conf-notes.txt new file mode 100644 index 0000000..8df5560 --- /dev/null +++ b/conf/template.qemux86-64/conf-notes.txt @@ -0,0 +1,3 @@ +Common targets are: + enea-image-nfv-access-guest + enea-image-nfv-access-guest-sdk diff --git a/conf/template.qemux86-64/local.conf.sample b/conf/template.qemux86-64/local.conf.sample new file mode 100644 index 0000000..1d9beaf --- /dev/null +++ b/conf/template.qemux86-64/local.conf.sample @@ -0,0 +1,237 @@ +# +# This file is your local configuration file and is where all local user settings +# are placed. The comments in this file give some guide to the options a new user +# to the system might want to change but pretty much any configuration option can +# be set in this file. More adventurous users can look at local.conf.extended +# which contains other examples of configuration which can be placed in this file +# but new users likely won't need any of them initially. +# +# Lines starting with the '#' character are commented out and in some cases the +# default values are provided as comments to show people example syntax. Enabling +# the option is a question of removing the # character and making any change to the +# variable as required. + +# +# Machine Selection +# +# You need to select a specific machine to target the build with. There are a selection +# of emulated machines available which can boot and run in the QEMU emulator: +# +#MACHINE ?= "qemuarm" +#MACHINE ?= "qemuarm64" +#MACHINE ?= "qemumips" +#MACHINE ?= "qemumips64" +#MACHINE ?= "qemuppc" +#MACHINE ?= "qemux86" +#MACHINE ?= "qemux86-64" +# +# There are also the following hardware board target machines included for +# demonstration purposes: +# +#MACHINE ?= "beaglebone" +#MACHINE ?= "genericx86" +#MACHINE ?= "genericx86-64" +#MACHINE ?= "mpc8315e-rdb" +#MACHINE ?= "edgerouter" +# +# This sets the default machine to be qemux86 if no other machine is selected: +MACHINE ?= "qemux86-64" + +# +# Where to place downloads +# +# During a first build the system will download many different source code tarballs +# from various upstream projects. This can take a while, particularly if your network +# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you +# can preserve this directory to speed up this part of subsequent builds. This directory +# is safe to share between multiple builds on the same machine too. +# +# The default is a downloads directory under TOPDIR which is the build directory. +# +#DL_DIR ?= "${TOPDIR}/downloads" + +# +# Where to place shared-state files +# +# BitBake has the capability to accelerate builds based on previously built output. +# This is done using "shared state" files which can be thought of as cache objects +# and this option determines where those files are placed. +# +# You can wipe out TMPDIR leaving this directory intact and the build would regenerate +# from these files if no changes were made to the configuration. If changes were made +# to the configuration, only shared state files where the state was still valid would +# be used (done using checksums). +# +# The default is a sstate-cache directory under TOPDIR. +# +#SSTATE_DIR ?= "${TOPDIR}/sstate-cache" + +# +# Where to place the build output +# +# This option specifies where the bulk of the building work should be done and +# where BitBake should place its temporary files and output. Keep in mind that +# this includes the extraction and compilation of many applications and the toolchain +# which can use Gigabytes of hard disk space. +# +# The default is a tmp directory under TOPDIR. +# +#TMPDIR = "${TOPDIR}/tmp" + +# +# Default policy config +# +# The distribution setting controls which policy settings are used as defaults. +# The default value is fine for general Yocto project use, at least initially. +# Ultimately when creating custom policy, people will likely end up subclassing +# these defaults. +# +DISTRO ?= "enea" +# As an example of a subclass there is a "bleeding" edge policy configuration +# where many versions are set to the absolute latest code from the upstream +# source control systems. This is just mentioned here as an example, its not +# useful to most new users. +# DISTRO ?= "poky-bleeding" + +# +# Package Management configuration +# +# This variable lists which packaging formats to enable. Multiple package backends +# can be enabled at once and the first item listed in the variable will be used +# to generate the root filesystems. +# Options are: +# - 'package_deb' for debian style deb files +# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager) +# - 'package_rpm' for rpm style packages +# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk" +# We default to rpm: +PACKAGE_CLASSES ?= "package_deb" + +# +# SDK/ADT target architecture +# +# This variable specifies the architecture to build SDK/ADT items for and means +# you can build the SDK packages for architectures other than the machine you are +# running the build on (i.e. building i686 packages on an x86_64 host). +# Supported values are i686 and x86_64 +#SDKMACHINE ?= "i686" + +# +# Extra image configuration defaults +# +# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated +# images. Some of these options are added to certain image types automatically. The +# variable can contain the following options: +# "dbg-pkgs" - add -dbg packages for all installed packages +# (adds symbol information for debugging/profiling) +# "dev-pkgs" - add -dev packages for all installed packages +# (useful if you want to develop against libs in the image) +# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages +# (useful if you want to run the package test suites) +# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.) +# "tools-debug" - add debugging tools (gdb, strace) +# "eclipse-debug" - add Eclipse remote debugging support +# "tools-profile" - add profiling tools (oprofile, lttng, valgrind) +# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.) +# "debug-tweaks" - make an image suitable for development +# e.g. ssh root access has a blank password +# There are other application targets that can be used here too, see +# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details. +# We default to enabling the debugging tweaks. +EXTRA_IMAGE_FEATURES = "debug-tweaks" + +# +# Additional image features +# +# The following is a list of additional classes to use when building images which +# enable extra features. Some available options which can be included in this variable +# are: +# - 'buildstats' collect build statistics +# - 'image-mklibs' to reduce shared library files size for an image +# - 'image-prelink' in order to prelink the filesystem image +# - 'image-swab' to perform host system intrusion detection +# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink +# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended +USER_CLASSES ?= "buildstats image-mklibs image-prelink" + +# +# Runtime testing of images +# +# The build system can test booting virtual machine images under qemu (an emulator) +# after any root filesystems are created and run tests against those images. To +# enable this uncomment this line. See classes/testimage(-auto).bbclass for +# further details. +#TEST_IMAGE = "1" +# +# Interactive shell configuration +# +# Under certain circumstances the system may need input from you and to do this it +# can launch an interactive shell. It needs to do this since the build is +# multithreaded and needs to be able to handle the case where more than one parallel +# process may require the user's attention. The default is iterate over the available +# terminal types to find one that works. +# +# Examples of the occasions this may happen are when resolving patches which cannot +# be applied, to use the devshell or the kernel menuconfig +# +# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none +# Note: currently, Konsole support only works for KDE 3.x due to the way +# newer Konsole versions behave +#OE_TERMINAL = "auto" +# By default disable interactive patch resolution (tasks will just fail instead): +PATCHRESOLVE = "noop" + +# +# Disk Space Monitoring during the build +# +# Monitor the disk space during the build. If there is less that 1GB of space or less +# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully +# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort +# of the build. The reason for this is that running completely out of space can corrupt +# files and damages the build in ways which may not be easily recoverable. +# It's necesary to monitor /tmp, if there is no space left the build will fail +# with very exotic errors. +BB_DISKMON_DIRS = "\ + STOPTASKS,${TMPDIR},1G,100K \ + STOPTASKS,${DL_DIR},1G,100K \ + STOPTASKS,${SSTATE_DIR},1G,100K \ + STOPTASKS,/tmp,100M,100K \ + ABORT,${TMPDIR},100M,1K \ + ABORT,${DL_DIR},100M,1K \ + ABORT,${SSTATE_DIR},100M,1K \ + ABORT,/tmp,10M,1K" + +# +# Shared-state files from other locations +# +# As mentioned above, shared state files are prebuilt cache data objects which can +# used to accelerate build time. This variable can be used to configure the system +# to search other mirror locations for these objects before it builds the data itself. +# +# This can be a filesystem directory, or a remote url such as http or ftp. These +# would contain the sstate-cache results from previous builds (possibly from other +# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the +# cache locations to check for the shared objects. +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH +# at the end as shown in the examples below. This will be substituted with the +# correct path within the directory structure. +#SSTATE_MIRRORS ?= "\ +#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \ +#file://.* file:///some/local/dir/sstate/PATH" + + +# +# Qemu configuration +# +# By default qemu will build with a builtin VNC server where graphical output can be +# seen. The two lines below enable the SDL backend too. By default libsdl-native will +# be built, if you want to use your host's libSDL instead of the minimal libsdl built +# by libsdl-native then uncomment the ASSUME_PROVIDED line below. +PACKAGECONFIG_append_pn-qemu-native = " sdl" +PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" +#ASSUME_PROVIDED += "libsdl-native" + +# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to +# track the version of this file when it was generated. This can safely be ignored if +# this doesn't mean anything to you. +CONF_VERSION = "1" diff --git a/images/build-qcow-image.inc b/images/build-qcow-image.inc new file mode 100644 index 0000000..deace60 --- /dev/null +++ b/images/build-qcow-image.inc @@ -0,0 +1,10 @@ +inherit image-vm +IMAGE_FSTYPES += "qcow2" + +# To reduce storage size remove the intermediate images +do_clean_unused_img() { + rm ${IMGDEPLOYDIR}/*.hdddirect + rm ${IMGDEPLOYDIR}/*.ext4 +} + +addtask clean_unused_img after do_vmimg before do_image_complete diff --git a/images/enea-image-nfv-access-common.inc b/images/enea-image-nfv-access-common.inc new file mode 100644 index 0000000..453d152 --- /dev/null +++ b/images/enea-image-nfv-access-common.inc @@ -0,0 +1,13 @@ +require images/enea-image-common.inc + +IMAGE_INSTALL += " \ + packagegroup-enea-virtualization \ + kernel-modules \ + " + +IMAGE_FSTYPES = "ext4.gz" + +#keep only the archive +do_image_ext4_append() { + rm ${IMGDEPLOYDIR}/*.ext4 +} diff --git a/images/enea-image-nfv-access-guest-sdk.bb b/images/enea-image-nfv-access-guest-sdk.bb new file mode 100644 index 0000000..0e909b1 --- /dev/null +++ b/images/enea-image-nfv-access-guest-sdk.bb @@ -0,0 +1,13 @@ +DESCRIPTION = "Image for the guest side of the Enea NFV Access Platform" + +require images/enea-image-nfv-access-common.inc + +IMAGE_INSTALL += " \ + packagegroup-enea-virtualization-guest \ + packagegroup-enea-virtualization-tools \ + kernel-devsrc \ + " + +IMAGE_FEATURES += "dbg-pkgs dev-pkgs" + +require images/build-qcow-image.inc diff --git a/images/enea-image-nfv-access-guest.bb b/images/enea-image-nfv-access-guest.bb new file mode 100644 index 0000000..2317e23 --- /dev/null +++ b/images/enea-image-nfv-access-guest.bb @@ -0,0 +1,9 @@ +DESCRIPTION = "Image for the guest side of the Enea NFV Access Platform" + +require images/enea-image-nfv-access-common.inc + +IMAGE_INSTALL += " \ + packagegroup-enea-virtualization-guest \ + " + +require images/build-qcow-image.inc diff --git a/images/enea-image-nfv-access-host-common.inc b/images/enea-image-nfv-access-host-common.inc new file mode 100644 index 0000000..f3c673a --- /dev/null +++ b/images/enea-image-nfv-access-host-common.inc @@ -0,0 +1,12 @@ +require images/enea-image-nfv-access-common.inc + +IMAGE_INSTALL += " \ + packagegroup-enea-virtualization-host \ + " + +IMAGE_FSTYPES += "tar.gz" + +# Due to a legacy include from corei7 machine we need to stop building following images +NOHDD = "1" +NOISO = "1" +INITRD_IMAGE_LIVE = "" diff --git a/images/enea-image-nfv-access-host-odm.bb b/images/enea-image-nfv-access-host-odm.bb new file mode 100644 index 0000000..d325588 --- /dev/null +++ b/images/enea-image-nfv-access-host-odm.bb @@ -0,0 +1,3 @@ +DESCRIPTION = "Image for the host side of the Enea NFV Access Platform that provides ODM support" + +require enea-image-nfv-access-host.bb diff --git a/images/enea-image-nfv-access-host-openstack.bb b/images/enea-image-nfv-access-host-openstack.bb new file mode 100644 index 0000000..3429c94 --- /dev/null +++ b/images/enea-image-nfv-access-host-openstack.bb @@ -0,0 +1,17 @@ +DESCRIPTION = "Image for the host side of the Enea NFV Access Platform that provides Oopenstack support" + +require images/enea-image-nfv-access-host-common.inc + +IMAGE_INSTALL = " \ + packagegroup-core-boot \ + packagegroup-cloud-compute \ + packagegroup-cloud-debug \ + packagegroup-cloud-extras \ + " + +IMAGE_FEATURES += "ssh-server-openssh" + +inherit openstack-base +inherit monitor + +IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000" diff --git a/images/enea-image-nfv-access-host-sdk.bb b/images/enea-image-nfv-access-host-sdk.bb new file mode 100644 index 0000000..add2689 --- /dev/null +++ b/images/enea-image-nfv-access-host-sdk.bb @@ -0,0 +1,18 @@ +DESCRIPTION = "Image for the host side of the Enea NFV Access Platform" + +require images/enea-image-nfv-access-common.inc + +IMAGE_INSTALL += " \ + packagegroup-enea-virtualization-host \ + packagegroup-enea-virtualization-tools \ + kernel-devsrc \ + " + +IMAGE_FEATURES += "dbg-pkgs dev-pkgs" + +IMAGE_FSTYPES += "tar.gz" + +# Due to a legacy include from corei7 machine we need to stop building following images +NOHDD = "1" +NOISO = "1" +INITRD_IMAGE_LIVE = "" diff --git a/images/enea-image-nfv-access-host.bb b/images/enea-image-nfv-access-host.bb new file mode 100644 index 0000000..0f5faae --- /dev/null +++ b/images/enea-image-nfv-access-host.bb @@ -0,0 +1,3 @@ +DESCRIPTION = "Image for the host side of the Enea NFV Access Platform" + +require images/enea-image-nfv-access-host-common.inc -- cgit v1.2.3-54-g00ecf