** Changed in: ledmon (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
Thank you for the review Christian! Due to lack of possible testing
hardware, no critical use cases and lack of resources, we have decided
to postpone this MIR until needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: oem-priority
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
Review for Package: ledmon
[Summary]
Since the last time we looked at that plenty of rules got improved
and a re-review was likely to discover things we would have missed in the
past.
Indeed I found some things that are required and some that are recommended
to be resolved before a promotion to
Thanks Łukasz for clarifying that!
Comments:
- #4 was almost an MIR Ack
- #9 confirmed that a security review should not be needed.
All this happened long time in the past, I'm rechecking the state as of
today but most likely we will approve this rather soon.
--
You received this bug
Ok, after discussing this with multiple people, we have decided to go
ahead. The Foundations team is willing to take ownership of this package
in main.
Dear MIR team: can we continue the MIR process?
** Changed in: ledmon (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: ledmon
** Description changed:
== Requirements ==
[Availability]
Currently in universe.
Package in LP: https://launchpad.net/ubuntu/+source/ledmon
Upstream: https://github.com/intel/ledmon
[Rationale]
1.OEM projects needs to include ledmon for VROC suport (LP: #1759225)
2.Intel
@Łukasz I think for OEM images for HW that have the corresponding
component, we should include those by default.
Given that, I think we should include it in main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The ledmon have the different partners of blinking helps the user to
understand the status of the disk and raid, it's critical feature for
user experience.
I would suggest to include ledmon to offer better support. ledmon is
been preloaded on workstations of major OEMs in the factory image, and
Ok, so I jumped in to see if there's anything I can do to help getting
this moving. Per Christian's question about the rationale of this MIR
and if it still holds, I asked Michael if subiquity has any plans of
using ledmon by default for VROC / RST support and he said that there
are no plans right
** Tags added: fr-1336
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
note #15 is test on focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
per test today, I set up the vroc nvme raid on a dell machine.
On that, I can use a command like
ledctl locate=/dev/nvme0n1
to make the led on the encluse module blink.
And use command
ledctl locate_off=/dev/nvme0n1
to make the led stop blinking.
As I config two nvme a mirror raid as the
I think I've done my part to test it and provide the use case. Give so,
mark fix committed in oem-priority.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
** Tags added: originate-1912445
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
** Changed in: oem-priority
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
# Rechecking #
Resolved:
- The old issue of being slightly outdated is resolved (we have regular updates
recently).
- the package indeed now has services to start properly on install
Left open:
- I'm unsure about the reasoning. The initial one in #1759225 counts as
resolved since 2018-11-02
** Changed in: ledmon (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about
per check ledmon in focal, it does run as a daemon.
I got access to a machine that can use ledctl from ledmon to control the
led status of the nvme module enclosure.
AI: try to build vroc raid on it, and check if the raid status will
cause the led pattern change in certain statuses of the raid
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[Expired for ledmon (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ledmon (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
** Changed in: ledmon (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
Hi Patricia,
I agree with Steve mentioned that ledmon should *not* be critical
requirement for VROC but more likely accessory to me, especially ledmon
package is not covering the systemd unit to trigger the service when
it's installed. What OEM Base image project proposed to include ledmon
was
Woodrow - Would you please provide clarity regarding Steve's comments
(see #7). I would like clarity before signing up the foundations team
for maintenance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Christian, actually, the security team doesn't typically decide if it
needs a security review; that is part of the ubuntu-mir team's review.
We have criteria for when something requires it:
https://wiki.ubuntu.com/MIRTeam#Security. If it doesn't meet those (or
similar) criteria, then it doesn't
Subscribing Pat, who would ultimately decide on Foundations maintenance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage notifications about this bug go to:
> 1. OEM projects needs to include ledmon for VROC support
It remains unclear to me why this is the case. The ledmon package ships
a daemon but provides no integration to cause it to start by default.
It also ships a 'ledctl' command to allow manually changing the status
LEDs on a disk
Hi Christian,
Thanks for sharing more information for above, and seems like we'll just
follow Intel's changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794219
Title:
[MIR] ledmon
To manage
Package quality, dependencies and all else LGTM and review is rather easy as it
is a relative small codebase ~9kloc.
I ran a few code checkers and they only found minor things not worth to bother.
Also the packaging seems fine since the major update by xnox.
Expecting the subscription by the
@Woodrow: please realize that the Debian Maintainer Daniel Jared
Dominguez is @Dell.com and Dell stopped at Version 0.79 - Intel pushed
it forward to 0.90 of today, but I'd assume Dell has no business to
pushing this further anymore. You had xnox do the update for you, but
this might have to
Hi Christian,
As we're discussing with foundation team about ledmon, the reason behind
this MIR is OEM base image would include ledmon. However the foundation
team suggests we may need to file a MIR request and they will make a
decision for figuring out the resource of maintenance.
For me, I'm
Thanks Woodrow,
If Foundations will subscribe to that they need to do so on
https://launchpad.net/ubuntu/+source/ledmon
I'm subscribing xnox (last upload) and Steve as Team Lead to consider
doing so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+ == Requirements ==
+
[Availability]
Currently in universe.
+ Package in LP: https://launchpad.net/ubuntu/+source/ledmon
+ Upstream: https://github.com/intel/ledmon
[Rationale]
1.OEM projects needs to include ledmon for VROC suport (LP: #1759225)
2.Intel
Hi Woodrow,
AFAIK the sections above are non optional.
Please use [1] to fill out all of them.
Especially Package ownership is a gating thing, someone responsible has to own
it.
Since you wrote TBD I assume you know that and will update it later on.
It seems this originally was [3] but intel
36 matches
Mail list logo
