| Age | Commit message (Collapse) | Author |
|---|
|
run-postinsts is now installed by default in image.bbclass, so no need
to include it in each image.
Reference: OE-core rev 529244ee212fe14019e35a5f163fab705ddbf141
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes:
base_contains is deprecated, please use bb.utils.contains instead.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Instead of having a central file or group of files to
describe what data resources should be monitored. The
content of these files will depend on what core system
monitoring is used ((e.g. Nagios or Monasca).
It's desirable to have each recipe describes what
it wants be monitored in generic way such that various system
monitors can understand and convert these into their format.
If a recipe wishes to register itself to system monitor, it
inherits monitor bbclass and use MONITOR_SERVICE_PACKAGES and
MONITOR_SERVICE_<package name> to indicate what processes
should should be monitored. Also MONITOR_CHECKS_<package name>
variale can be used to pass list of scripts which will be run
on target and if any of these scripts fail then will report.
Eventually monitor.bbclass will be expanded to allow recipe
to describe more complicated information passed down to
system monitor (e.g. Nagios or Monasca)
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
Instead of creating tenant/user/role and service/endpoint for all
openstack services in keystone postinstall, now each of the services
creates its own keystone identities by queueing them up in its postinstall
to a file /etc/keystone/service-user-setup. service-user-setup
script, when run as the last postinstall, calls identity.sh with keystone
identity parameters to create necessary identities for the services.
Signed-off-by: Andy Ning <andy.ning@windriver.com>
|
|
Include Rally benchmarking feature into all-in-one
image when OPENSTACK_EXTRA_FEATURES variable
includes "benchmarking" feature.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
Create new benchmarking packagegroup bb. Benchmarking
packagegroup can be included into final image to include
all required packages for benchmarking OpenStack at scale.
Currently OpenStack benchmarking is provided by OpenStack
component Rally.
Also introducing new Yocto variable OPENSTACK_EXTRA_FEATURES
which can be used to inform what feature should be included in
meta-cloud-services OpenStack final image.
To include benchmarking packagegroup in local.conf have
OPENSTACK_EXTRA_FEATURES += " benchmarking"
Signed-off-by: Vu Tran <vu.tran@windriver.com>
|
|
Introduce image openstack-image-aio, integrating both compute and controller functionality
Signed-off-by: Amy Fong <amy.fong@windriver.com>
|
|
To ensure that the free space required for proper operation is not
clobber by other layers manipulating the extra space variable, we make
our additions additive versus absolute.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Add the extras and debug package groups by default. These can later be
convered to image or distro features, but for now, we turn them on
universally.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Commit 91c372f287732cdedbd7c1204c6ba5f34e5b93f6 [core-image-basic /
packagegroup-core-basic: rename to *-full-cmdline] in yocto renamed
these tasks so we need to reflect that change here.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Allow the final controller node image rootfs extra space
to be configurable.
Signed-off-by: Vu Tran <vu.tran@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
By default the controller and compute images use IMAGE_INSTALL= to
set their package lists. This doesn't allow a local.conf to add
packages via IMAGE_INSTALL += <FOO>.
To allow package addition, but yet still control the base package list,
there are two variables that can now be used to add packages:
${OPENSTACK_COMPUTE_EXTRA_INSTALL}
${OPENSTACK_CONTROLLER_EXTRA_INSTALL}
Which variable does what, should be self explanitory.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Various components (such as rabbitmq) have checks for minimum amounts
of free space on a image. If those checks fail, the service exits in
a hard to debug manner. To ensure that these services run, and meet
typical usage scenarios, we increase the free space in the image to 3G.
Finally, we inherit openstack-image-base, to trigger simple rootfs
configuration and deployment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Various components (such as rabbitmq) have checks for minimum amounts
of free space on a image. If those checks fail, the service exits in
a hard to debug manner. To ensure that these services run, and meet
typical usage scenarios, we increase the free space in the image to 3G.
We also automatically include the network node packages into this image
type, to ensure that full quantum functionality is available.
Finally, we inherit openstack-image-base, to trigger simple rootfs
configuration and deployment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
-Updated recipe to use a packagegroup;
-Removed some image features that are no longer used;
Signed-off-by: Mihai Prica <prica.mihai@gmail.com>
|
|
Signed-off-by: Mihai Prica <prica.mihai@gmail.com>
|
|
Signed-off-by: Mihai Prica <prica.mihai@gmail.com>
|
Adrian Dudau
Mark Asselstine
Bruce Ashfield
Vu Tran
Amy Fong
Andy Ning
Mihai Prica