| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
