We have added a new container to the OverC framework to handle
networking services for the cube-lan. Although this functionality has
been available since commit ad749f0c06 [cube-vrf: Introduce the
cube-vrf container], we have yet to include it in documents and system
scripts. Add references to cube-vrf where needed.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
In commit 7132ee0f30 [images: bump essential PV and remove dom1] we
removed dom1 from the OverC framework. However, several references to
dom1 remained which we are now removing.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
It is desirable to allow pflask to work with what ever hardware is
detected as well as specific hardware. The --netif=Interface was
extended with this patch to allow a "+" which will match any other
interface with the same prefix. For example --netif=enp+:enp+ will
select all available interfaces that start with enp like enp0s3,
enp0s4, etc...
Also clean up instances of NETWORK_DEVICE_CLASSES which is no longer used.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Since builder.cfg will disable preempt in kernel. We disable this kernel
fragment by default.
If user want to enable builder.cfg for cube-builder project, need add
following line in local.conf:
OVERC_PLATFORM_TUNING += "builder"
Signed-off-by: Jiang Lu <lu.jiang@windriver.com>
Add notes in Readme.install:
1.Limitation of read-only essential rootfs.
2.How to change rw attribute for essential.
Signed-off-by: Jiang Lu <lu.jiang@windriver.com>
The cube-domE name is confusing, and we constantly have to explain what
the "E" stands for.
Also, as the design progressed, domE is not an essential part of the
system .. it is optional. As such, it shouldn't be designated as a
"domain".
By dropping the domE and making it cube-desktop, we resolve both the
confusion and the inconsistency.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The overc-installer is still on github but the organization has
switched from WindRiver-OpenSourceLabs to OverC.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
The puppet will be used in masterless mode to complete configuration
of the images during installation and eventually to ensure persistent
configurations remain after completing system upgrades.
This requires that meta-cloud-services is added to the list of
required layers. Documentation, sample configs etc. have been updated
to reflect this.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When the usb-creator.sh script was renamed to cubeit the options to
invoke installer creation also changed. Previously this was just an
ordered option but now is prefixed.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
'pods' are used in many projects and places. To clear up the namespace, we now
call the building blocks of an OverC system 'cubes'.
This switches the images, variables and READMEs to talk about 'cubes'.
We also move the distro conf to meta-overc, and ensure the distro is "overc".
And finally, the meta-cube layer priority is bumped to ensure its configs take
precence.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The installation scripts now support the use of puppet during the
creation of the install media and while installing the target. Here we
are adding notes on how puppet is setup for use. For now we are
leaving the use of puppet as an optional feature, at a later point in
time it will most likely be the default and at that time we can remove
what we are adding here and replace it with more details about how to
work with the puppet configuration to achieve specific configuration
goals.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
This is a rough outline of the steps required to build and install OverC.
It is incomplete, but serves as our baseline instructions.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
