--Michael
On Tuesday, January 17, 2012 at 11:14 AM, Mann, Owen wrote: > > I've felt that power management could use some streamlining. I have ideas but > I'm not any good at Python. > > > Particularly I don't like the "lowest common denominator" aspect of the fence > agents (e.g. "reboot" being implemented as "power off, pause, power on"). I > created a "PXE button for IPMI-over-LAN" patch for 1.6, but haven't figured > out how to replicate that for 2.x. > > > > *nod* Supporting direct reboot does not seem to need what the email below is about, though. > > > > > > > > > > > So, I don't have strong opinions on NUT integration, but if someone good at > Python updated the power stuff, that might be a good thing… > > > > Can you speak in terms of use cases -- what do you want it to do other than replace the start/stop with a reboot? > > > > > From: cobbler-devel-boun...@lists.fedorahosted.org > [mailto:cobbler-devel-boun...@lists.fedorahosted.org] On Behalf Of Michael > DeHaan > Sent: Monday, January 16, 2012 10:46 AM > To: cobbler development list > Subject: Re: Self introduction and Power management improvements > > > > > > First off, thanks for the interest. This is the first I've heard of this > app…. > > > > > > > > The 77 page manual for this app is a bit too long for me at the moment, nor > something I think we can require everyone to read & understand. For it to > be a clear logical fit, you'll need to be able to make that case to everyone > who is using the power management support today. > > > > > > > > I'd like to know more. What are the Elevator pitch and use cases around > this? For new features to be integrated, we need to know how many other > people in Cobbler land are already using this tool, and have supported > hardware. Then, we need to see the proposed setup steps, command line > changes, and use cases -- to show what we can achieve and how this will > affect existing users if any. Do you plan a hard requirement on the tool? > What are you planning with regard to the fence scripts, etc? (Keep in mind, > people are using these now…and we can't disrupt them) … What are the > improvements to the handling of fence scripts that you plan? > > > > > > > > (All this aside -- though the change to fix sorting is fine, your pull > request has been rejected because it adds a power type of "[nut]" with no > support or script for it) > > > > > > > > Let me know more and hopefully there's a good fit here -- but if not, perhaps > this is something you can configure via --ksmeta and an snippet (or similar) > -- or drive through configuration management integration. We want to avoid > > > > Cobbler becoming a "webmin" like tool for all sorts of apps, but there may be > a very strong logical fit here. I need you to help me understand what this > integration would look like, and what it would do. > > > > > > > > Do other folks on the list have thoughts? > > > > > > > > --Michael > > > > > > > > > > > -- Michael > > > > > > > > On Monday, January 16, 2012 at 6:56 AM, Arnaud Quette wrote: > > > > Dear Cobbler fellows, > > > > First, to introduce myself, I'm Arnaud Quette. > > I'm mainly in charge of the NUT - Network UPS Tools [1] project. > > NUT is the main project for power devices (UPS, PDU, PSU, ... ) management > > and protection, and provides the broadest list of supported devices in the > > field [2]. > > I'm also working on several infrastructure and cloud power management > > related topics. > > > > As such, I've been looking at Cobbler in 2 ways: > > 1) improving existing power management (Ie, fence-agents integration) > > 2) proposing a design (and latter implementing) for power protection. > > > > For point (1), I've already made a few fixes, with a stagging pull request > > on Github [3]: > > - actually make a combo list for "Type", with a sorted list of scripts > > (since it's a finite list, depending on the available power templates), > > - Reword "Type" tooltip, for more clarity, > > - Rename from "Power" to "Power management", to prepare for the upcoming > > "Power protection" section (latter RFC), > > - Remove "Power" from the various fields (Type, Address, Username, > > Password, ID) to avoid redundancy. > > > > I'm also working on creating a "fence_nut" agent. > > Once submitted upstream to Marek (Grac) and Fabio (M. Di Nitto), I'll also > > submit the Cobbler template through a pull request... > > > > For point (2), I'm still working on a design to submit you, but have a few > > questions to ask you you before. > > > > - the general idea is to make it easy to deploy power protection on the > > provisioned servers, using the NUT packages, > > - this implies some configuration, to point at the protecting and feeding > > devices (UPS at least, but also PDU and servers power supply units), > > - I'm intending to create a new "Power protection" section, still in the > > system page, to allow for setting up these values, > > I've made good progress on this part. > > - I'm working with inventory systems (OCS Inventory NG and Fusion > > Inventory) to discover power devices (through USB, SNMP and IPMI). > > The aim is then to be able to retrieve inventory data into cobbler (through > > web service interfaces), and provide users with the list of physical > > servers and power devices to help filling the various forms . > > As a complement, NUT also provides a tool (nut-scanner, which is used by > > inventory systems), to discover NUT supported devices. > > It is currently available as a command line, but Python and Perl wrapper > > are underway. > > This can be a fallback, in case inventory systems are not available. > > > > Now, the questions: > > - do you have any input or comment on point (1) and (2)? > > - once everything is setup in the UI, how can we enable installation of NUT > > packages and push the configuration done by the user? > > > > I'll get back to you soon with more details on point (2). > > > > cheers, > > Arnaud > > -- > > [1] http://www.networkupstools.org/ > > [2] http://www.networkupstools.org/stable-hcl.html > > [3] https://github.com/cobbler/cobbler/pull/46 > > -- > > Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com > > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > > Debian Developer - http://www.debian.org > > Free Software Developer - http://arnaud.quette.free.fr/ > > > > > > > > _______________________________________________ > > > > > > > > cobbler-devel mailing list > > > > > > > > cobbler-devel@lists.fedorahosted.org > > (mailto:cobbler-devel@lists.fedorahosted.org) > > > > > > > > https://fedorahosted.org/mailman/listinfo/cobbler-devel > > > > > > > > > > > > > > > > > > > ******************************************************* > This message (including any files transmitted with it) may contain > confidential and/or proprietary information, is the property of Interactive > Data Corporation and/or its subsidiaries, and is directed only to the > addressee(s). If you are not the designated recipient or have reason to > believe you received this message in error, please delete this message from > your system and notify the sender immediately. An unintended recipient's > disclosure, copying, distribution, or use of this message or any attachments > is prohibited and may be unlawful. > ******************************************************* > _______________________________________________ > cobbler-devel mailing list > cobbler-devel@lists.fedorahosted.org > (mailto:cobbler-devel@lists.fedorahosted.org) > https://fedorahosted.org/mailman/listinfo/cobbler-devel > >
_______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
