Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Pavel Zhukov authored 3 years ago and Stefan Schmidt committed 3 years ago

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Closes: https://git.ostc-eu.org/OSTC/planning/maintenance/-/issues/29

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Updated the defninition Project name  value

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>

URL updated

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>

* Project rename
* adr directory removed
* Closes distro/docs#77

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>

Zephyr and FreeRTOS jobs do not require 16GB of RAM to build and
constitute the bulk of our CI (by number) quota usage. By moving them to
smaller instances, with 4GB of RAM, we can use the remaining quota
better.

On the infrastructure side we now have a new auto-scaling pool, with
s3.large.2 instances. Those join the existing s3.xlarge.4 (formerly
known as "heavy") and s3.large.8 (formerly known as "light").

The .workspace job uses the s2.large.8 by default, making a safe (but
expensive) default. Specific jobs deviate as follows:

 - zephyr and freertos jobs use s3.large.2
 - two blueprint jobs with more recipes use s3.xlarge.4

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This was missed as CI was not operational during the big move.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Most things are moved unchanged. The relatively few changes are to the
documentation, as the split between the meta-ohos and manifest is gone,
as well as to the actual CI definitions for the workspace directory,
since the sources/ sub-directory is gone, and there was some
backwards-compatibility code that no longer makes sense to maintain.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

The .ostc-ci directory becomes .oniro-ci

The various CI variables names are now all uniformly named CI_ONIRO_.
Some specific variables were further trimmed to avoid using "CI" twice.

Remaining uses of OSTC and OHOS are for URLs, container images and
branch names.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

Forwarded: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/256
Relate-to: https://git.ostc-eu.org/OSTC/OHOS/manifest/-/issues/69


Signed-off-by: Philippe Coval <philippe.coval@huawei.com>

Signed-off-by: Sebastian Serewa <sebastian.serewa@huawei.com>

* All project name replaced with tag
* definitions.rst reference added
* Closes: OSTC/OHOS/docs#77

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>

The "Vending Machine" blueprint takes advantage of two Linux
applications: a UI and a Control one. These applications will exchange
messages over a defined interface using a specific protocol. This
documentation provides the specification of the communication protocol,
message format, schemas and more.

Fixes https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/224

Relate-to: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/282


Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
Signed-off-by: Philippe Coval <philippe.coval@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

For now the gateway blueprint testing is limited to raspberrypi4-64. We
are not actively excluding other boards, but at least wifi and a USB
host for an OpenThread dongle is needed. Better state the tested board
only in the docs until we expand the testing.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

Relate-to: https://git.ostc-eu.org/OSTC/OHOS/docs/-/issues/74


Thanks-to: Marta Rybczynska <marta.rybczynska@huawei.com>
Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

I have observed this in several places,
Without it's still understandable but it requiered me an extra effort.

This makes me think I think there are standards to check if
"Simple English" is used, this could help community adoption of project.

Forwarded: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/233


Signed-off-by: Philippe Coval <philippe.coval@astrolabe.coop>

philippe coval authored 3 years ago and philippe coval committed 3 years ago

List didn't display fine, if not prefixed by empty line.

Relate-to: https://allscenarios.readthedocs.io/en/latest/meta-ohos/blueprints/touchpanel.html
Forwarded: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/226


Signed-off-by: Philippe Coval <rzr@users.sf.net>

Document how to wire the breadboards for the door lock blueprint

Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>

Clarify the image name we use for the blueprint as well as the used
distro config.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

This is a first stab at documenting the network properties used in the
gateway blueprint. It reflects the current status and needs to be kept
in sync with changes.

Fixes: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/201



Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Without the extra empty line the formatting for the numbered would not
kick in.

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

These are generic HW modules that can be used across several blueprints
to depict basic input/output interactions with the system.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Set up the structure for how the blueprint documents will live

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Describe the purpose of a blueprint in All Scenarios OS to set
the right expectations.

Signed-off-by: Amit Kucheria <amit.kucheria.ext@huawei.com>

Gururaj Shetty authored 3 years ago and Stefan Schmidt committed 3 years ago

Initially, Arudino did not enable USB CDC_ACM interface,
due to which once flashed, the user was forced to connect
an external USB TTL cable to connect the board.

This limitation is now resolved; hence, connecting USB
TTL cable information is removed.

Signed-off-by: Gururaj Shetty <gururaj.shetty@huawei.com>