Brian O'Connor

Get all Bazel targets to "run"

3

So that queries over entry tree don't fail parse first, compile second, tests 3rd

Per the TST discussion, we want to improve documentation on how to use tofino-model. We should also add a section that explains the differences between tofino-model and bmv2 and provides...

With the plugin model for PHAL, revisit the flags used to enable/disable various pieces.

Allow users to provide an `openconfig.Device` proto instead of the `ChassisConfig` when starting or reconfiguring Stratum. Demote `ChassisConfig` to an internal representation hidden from most users. - [ ] Develop...

Clean up Stratum log on startup

3

The log contains several errors and warnings that are expected on startup. We should consider removing and downgrading some these. For example, ``` E20201217 21:01:52.398595 1 utils.cc:109] StratumErrorSpace::ERR_FILE_NOT_FOUND: /var/run/stratum/pipeline_cfg.pb.txt not...

https://github.com/stratum/stratum/blob/9798d8ed6ba37718572c0a1f682c1cc73af6654a/stratum/hal/bin/barefoot/docker/start-tofino-model.sh#L12 Allow uses to optionally pass conf.json from bf-p4c to `--p4-target-config` for improved logging / symbol resolution. Maybe derive this from the p4_device_config and unpack before starting tofino-model

Today we just use 0.0.1

Also maybe the most recent tag https://github.com/stratum/stratum/issues/484#issue-776197164

Simplify BfrtDeviceConfig

2

https://github.com/stratum/stratum/blob/d5937f77c756d8296ed47397fb81718d18a0fcf9/stratum/hal/lib/barefoot/bf.proto#L29-L42 Instead consider: ```proto message BfrtDeviceConfig { message P4Program { p4.config.v1.P4Info p4info = 3; BfPipelineConfig config = 5; } repeated P4Program programs = 1; } ```