I reviewed octavia 1:10.0.0-0ubuntu1 as checked into jammy. This shouldn't
be considered a full audit but rather a quick gauge of maintainability.
octavia is a load balancer used with the OpenStack cloud infrastructure.
Therefore, it is one of the network services inside OpenStack components.
-
** Changed in: octavia (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => Rodrigo Figueiredo
Zaiden (rodrigo-zaiden)
** Changed in: octavia (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: octavia (Ubuntu)
Milestone: ubuntu-20.10 => ubuntu-22.04-feature-freeze
** Changed in: octavia (Ubuntu)
Milestone: ubuntu-22.04-feature-freeze => ubuntu-22.04-beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>> bugs reported upstream as potential security issues <<
An upstream developer responded to the bugs reported - the code
identified relates to the amphora agent which is internal to octavia,
and requires communication from the main octavia control process to the
HTTP server in the amphora agent t
>From the MIR meeting:
[16:33] jamespage: if you think with your explanations it should go
back to re-review by them assign them
[16:34] I'll mark it incomplete for now as it does not seem to need
a new MIR review
** Changed in: octavia (Ubuntu)
Status: New => Incomplete
--
You receiv
>> debian/*.init.in <<
You'll find this pattern across all of the packages in the OpenStack
package set; rather than maintain init scripts/systemd units/upstart
configurations across > 100 daemons the Debian OpenStack team came up
with a simple method of using a set of variables to generate all of
>> Unit Test Verbosity <<
I agree that the build log (specifically the unit test execution) is
somewhat verbose during execution - I had a look through some of the
references you made and it appears that the application logging in
octavia is directly configured to stdout during unit test execution
I have serious reservations about this package.
The build logs are very messy and report a LOT of problems. How does one
tell "these problems are completely normal" from "these problems
indicate a regression in the package"?
There's many cases of building strings to execute, either via simple
one
I'm starting in on this MIR and I'm surprised how many errors there are
in the buildlogs. Both a version I built locally and some buildd build
logs are noisy:
https://launchpad.net/ubuntu/+source/octavia/1:7.0.0+git2021012713.fbbc5f90-0ubuntu1/+build/20944559/+files
/buildlog_ubuntu-hirsute-
amd64
[Summary]
Octavia provides Loadbalancing as a service as part of an OpenStack Cloud
deployment.
Loadbalancers are provided as virtual machine appliances which run the
Octavia amphorae agent for management control between the Octavia
control plan and the loadbalancers (typically via a dedicated pr
** Changed in: octavia (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888309
Title:
[MIR] octavia
To manage notifications about this
11 matches
Mail list logo
