Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[installer]: support new onie machine.conf format #1468

Merged
merged 2 commits into from
Mar 18, 2018

Conversation

lguohan
Copy link
Collaborator

@lguohan lguohan commented Mar 7, 2018

onie_* variable are generated at runtime in /etc/machine.conf.
We can no longer copy the static machine.conf into sonic image.

- What I did
support new onie machine.conf format

- How I did it
export the onie_* varilable into sonic static machine.conf

- How to verify it
alphanetwork validated.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Copy link
Collaborator

@qiluo-msft qiluo-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As comment

if [ -f /etc/machine-build.conf ]; then
# onie_ variable are generate at runtime.
# they are no longer hardcoded in /etc/machine.conf
set | grep onie_ > $demo_mnt/machine.conf
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why use 'set' instead of 'env'?
Suggest grep 'onie_' at the line beginning. Maybe

env | grep ^onie_

Not sure it is available in ONIE environment.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since the variables are not exported, so they are not env

lguohan added 2 commits March 17, 2018 21:51
onie_* variable are generated at runtime in /etc/machine.conf.
We can no longer copy the static machine.conf into sonic image.
Signed-off-by: Guohan Lu <gulv@microsoft.com>
@fillmorechen0928
Copy link

/host/machine.conf is incorrent for other application.

Please remove quote.

@daall daall mentioned this pull request Oct 26, 2020
3 tasks
abdosi added a commit that referenced this pull request Mar 7, 2021
9e740759c370645b4367acf22856aebcfb7fce45 (HEAD -> 201911, origin/201911) [201911][multi asic] show ip bgp summary changes for bgp mon (#1483)
fa07245786df11e6df902c33fcd9c7115a7c5380 [CLI][techsupport] Merge 'show techsupport' changes from master (#1468)

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
theasianpianist pushed a commit to theasianpianist/sonic-buildimage that referenced this pull request Feb 5, 2022
mssonicbld added a commit that referenced this pull request Dec 11, 2024
…tically (#21001)

#### Why I did it
src/sonic-sairedis
```
* e7dc0d2b - (HEAD -> 202405, origin/202405) [202405] Fix compilation error on Buster (#1483) (18 hours ago) [Junchao-Mellanox]
* 06d34610 - Support SAI_QUEUE_ATTR_TYPE on vs platform simulating MLNX2700 (#1459) (6 days ago) [Stephen Sun]
* 0bd015e3 - Do not poll counters in bulk mode during initialization for objects that support bulk per CLI option (#1437) (8 days ago) [Stephen Sun]
* 497bd053 - [fastboot] Notify SAI that fastboot is done (#1396) (#1468) (8 days ago) [Junchao-Mellanox]
```
#### How I did it
#### How to verify it
#### Description for the changelog
lguohan pushed a commit that referenced this pull request Dec 11, 2024
Why I did it

e7dc0d2b (HEAD, origin/202405) [202405] Fix compilation error on Buster (#1483)
06d34610 Support SAI_QUEUE_ATTR_TYPE on vs platform simulating MLNX2700 (#1459)
0bd015e3 Do not poll counters in bulk mode during initialization for objects that support bulk per CLI option (#1437)
497bd053 [fastboot] Notify SAI that fastboot is done (#1396) (#1468)

PR #21001 raised by automation failed at PR checker. The issue has been fixed and raised a new PR to advance pointer to sonic-sairedis repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants