Tested on latest "current" source tree build. Works fine and solves the "old syntax" cache file issue. Thank you for the quick and responsive fix.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 19 2023
Apr 18 2023
That would be great!
In T1237#147125, @Harliff wrote:Sorry, missed some messages.
In T1237#146586, @Viacheslav wrote:We have targets-checks 203.0.113.1, 192.0.2.1, and if any of these targets are unreachable, we delete this route.
Is it correct?It is not correct. I think it would be better to remove the route if ALL of corresponding targets are unreachable.
A target may become unreachable due to a problem of its own rather than an uplink failure. This is the reason why I asked to add multiple targets per uplink.
In T1237#146839, @Viacheslav wrote:@Harliff Could you re-check?
Sorry, missed some messages.
In T5144#147087, @Viacheslav wrote:
PR for the fix: https://github.com/vyos/vyos-1x/pull/1962
Apr 17 2023
The issue does not exit in the recent release 1.4-rolling-202304130846
Apr 16 2023
Apr 15 2023
This commit was not authored by me…
Apr 14 2023
submitted this PR: https://github.com/vyos/vyos-1x/pull/1958
In T5157#147008, @sdev wrote:Just to clarify, it changes again to pod-networkname in https://github.com/vyos/vyos-1x/commit/2a876059826927ef204e359a40395955f27503ce (next rolling image) to avoid name constraint issues.
Just to clarify, it changes again to pod-networkname in https://github.com/vyos/vyos-1x/commit/2a876059826927ef204e359a40395955f27503ce (next rolling image) to avoid name constraint issues.
In T5157#147001, @Viacheslav wrote:It uses other names in the newest versions, not cni-xxx
In T5156#147003, @Viacheslav wrote:Provide your configuration
It is difficult to say without it
Provide your configuration
It is difficult to say without it
It uses other names in the newest versions, not cni-xxx
#!/usr/bin/env python3 # # Copyright (C) 2022 VyOS maintainers and contributors # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License version 2 or later as # published by the Free Software Foundation. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/>. #
Apr 13 2023
In T5157#146979, @sdev wrote:Can you share container config section?
Can you share container config section?
If I need to guess, it is just an issue that the BGP session gets configured before the route-maps
As I said, this happens with any config that includes route maps
Self-configuration of the http-api calls a service restart from the config mode script: some re-configuration should be possible without restart; the remaining should provide an explanatory 'success' response. Move to high-priority to address.
This is available in Sagitta thanks to the PKI subsystem; backport depends on backport of that subsystem.
Thanks for clarifying. Yes , I also saw the possibility of extending role based IAM to add on-premise image (that could be interesting for VyOS).
Could you share configuration ? where attached RM and BGP settings:
We can add guidelines about running vyos on LXC/LXD in the documentation
Must run in physical NIC pass-through mode
It is recommended to execute the container in privileged mode
This is currently only an initial implementation!
This should be implemented under the rewrite of system-image-tools:
https://vyos.dev/T4516
This has not been seen subsequently. Close unless recurrence.
Discussed, and ready to be implemented shortly.
Related to T3651.
This will be integrated with the PKI subsystem, using the ideas there.
- In order to apply SSM auto-configuration of the CloudWatch agent, an SSM agent must be installed that installs the CloudWatch agent with the necessary configuration. Currently, there is no SSM agent inside VyOS AWS images, and I haven't heard anything about willingness to include it.
- The amazon-cloudwatch-agent package has only one dependency, libc6. Therefore, it does not need the aws-cli to be configured or set up at all.
- Granting access to the CloudWatch service from an EC2 instance is done by applying the corresponding IAM role to the instance. While it is possible to do this via manual credential input, it is an unwanted practice inside AWS.
- The possible scenario of sending data to CloudWatch out of AWS is unique and requires another Phorge task, I think.
@unity when you need AWS credential , will they be automatically deployed from SSM or will we have to add those credentials in the virtual machine? ? shouldn't aws-cli be integrated?