[prev in list] [next in list] [prev in thread] [next in thread]
List: cobbler
Subject: Re: [cobbler] Ipmitool and ipmilan woes and power resetting and PXE Mode issues.
From: Scott Mattan <s-mattan () niscom ! co ! jp>
Date: 2015-08-10 0:53:12
Message-ID: CAP5r1A9OMniaTX4LVY2JNcSbiHyAp_4R_7gDtAKH80TqMh2amA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Nish,
Sorry for the late response, I would love to write an article on my setup,
unfortunately, I am bound by company restrictions.
That being said, it isn't a customer facing setup so the process does have
some security issues that I need to eventually work out.
(although being on an isolated network, I am not too worried)
I would also love to commit to the project, although at the moment my
python skills are non-existant so everything that my setup is running on is
either BASH, AWK, SED, or Ruby scripts.
It may be possible to order your servers with SeaBios(also known as
coreboot or openbios), which is open source legacy BIOS implementation and
therefore you should be able to write code against it... I haven't taken a
look into it much myself yet. (although I have heard that there are still a
good many issues with some of the more advanced features)
My reasoning for wanting to see the ability to configure the BIOS is that
once you have the Server set to PXE boot (preferably factory set) I would
rather not have to jump into the BIOS of each individual server to change a
single setting here and or there based on some SLA that is in place.
Although I realize that this is more of a far off dream at the moment for
cobbler, I know that using proprietary tools that this likely currently
being done by industry giants such as Google and Amazon.
In anycase, I will keep my eye open, and if I have the chance to contribute
something, even if its a simple bash script (albeit slightly edited as my
current scripts have a couple of issues related to security as mentioned
earlier) I will do so.
Scott Mattan
On Fri, Aug 7, 2015 at 12:42 AM, Nishanth Aravamudan <
nacc@linux.vnet.ibm.com> wrote:
> On 06.08.2015 [14:32:47 +0900], Scott Mattan wrote:
> > Jennifer,
> >
> > You are specifying that on a system already registered in cobbler
> > that you want to be able to switch the BIOS setting for boot source?
> > As Alvin mentioned, at the moment this is not possible, as an
> > alternative you could script it yourself... I am however, curious to
> > understand the reason for your needing this functionality provided
> > that you can tell me.
>
> I assumed, based upon the context in the first e-mail, that Jennifer's
> SuperMicro systems (note also mentioned working around the SuperMicro
> tool) are somehow "broken" at the BIOS level and don't maintain this
> setting.
>
> > The reason why I am curious is mainly due to the fact that once
> > your server is set to boot from PXE you shouldn't need to have it
> > changed. Unless you are pre-defining your servers in cobbler and then
> > using it to deploy each one?
>
> I agree with you -- it's unclear why that's a necessary step.
>
> > My set up uses the default system settings to install a base
> > operating system, automatically register the system to cobbler,
> > determine the system type (virtual or physical) , reinstall the
> > correct OS/Profile, and then configure it automatically. This allows
> > me to get my servers from the factory preset to PXE, press the power
> > button and go.
>
> It would be great to see an article about your setup (presuming your
> allowed by your employer to publish it) or maybe contrib some of your
> tooling around cobbler!
>
> > I would like to see various functionality like this integrated
> > into the cobbler framework however... of particular interest is
> > turning on and off CPU components i.e. hyperthreading or
> > virtualization at the BIOS level.
>
> I'd be pretty impressed if BIOS level settings are so
> standardized/exposed that it could really be integrated -- and would
> actually work -- in Cobbler!
>
> I'm not sure how much makes sense to integrate into cobbler proper
> (given that cobbler's sole goal should be installation of clients, not
> the configuration of the clients in some sense) but maybe in snippets
> (if the BIOS is exposed to the client from within the client).
>
> -Nish
>
>
[Attachment #5 (text/html)]
<div dir="ltr">Nish, <div><br></div><div>Sorry for the late response, I would love \
to write an article on my setup, unfortunately, I am bound by company \
restrictions.</div><div><br></div><div>That being said, it isn't a customer \
facing setup so the process does have some security issues that I need to eventually \
work out.</div><div>(although being on an isolated network, I am not too worried) \
</div><div><br></div><div>I would also love to commit to the project, although at the \
moment my python skills are non-existant so everything that my setup is running on is \
either BASH, AWK, SED, or Ruby scripts. </div><div><br></div><div>It may be \
possible to order your servers with SeaBios(also known as coreboot or openbios), \
which is open source legacy BIOS implementation and therefore you should be able to \
write code against it... I haven't taken a look into it much myself yet. \
(although I have heard that there are still a good many issues with some of the more \
advanced features) </div><div><br></div><div>My reasoning for wanting to see the \
ability to configure the BIOS is that once you have the Server set to PXE boot \
(preferably factory set) I would rather not have to jump into the BIOS of each \
individual server to change a single setting here and or there based on some SLA that \
is in place. Although I realize that this is more of a far off dream at the moment \
for cobbler, I know that using proprietary tools that this likely currently being \
done by industry giants such as Google and Amazon. </div><div><br></div><div>In \
anycase, I will keep my eye open, and if I have the chance to contribute something, \
even if its a simple bash script (albeit slightly edited as my current scripts have a \
couple of issues related to security as mentioned earlier) I will do \
so.</div><div><br></div><div>Scott Mattan </div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 7, 2015 at 12:42 AM, \
Nishanth Aravamudan <span dir="ltr"><<a href="mailto:nacc@linux.vnet.ibm.com" \
target="_blank">nacc@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class="">On 06.08.2015 [14:32:47 +0900], Scott Mattan \
wrote:<br> > Jennifer,<br>
><br>
> You are specifying that on a system already registered in cobbler<br>
> that you want to be able to switch the BIOS setting for boot source?<br>
> As Alvin mentioned, at the moment this is not possible, as an<br>
> alternative you could script it yourself... I am however, curious to<br>
> understand the reason for your needing this functionality provided<br>
> that you can tell me.<br>
<br>
</span>I assumed, based upon the context in the first e-mail, that Jennifer's<br>
SuperMicro systems (note also mentioned working around the SuperMicro<br>
tool) are somehow "broken" at the BIOS level and don't maintain \
this<br> setting.<br>
<span class=""><br>
> The reason why I am curious is mainly due to the fact that once<br>
> your server is set to boot from PXE you shouldn't need to have it<br>
> changed. Unless you are pre-defining your servers in cobbler and then<br>
> using it to deploy each one?<br>
<br>
</span>I agree with you -- it's unclear why that's a necessary step.<br>
<span class=""><br>
> My set up uses the default system settings to install a base<br>
> operating system, automatically register the system to cobbler,<br>
> determine the system type (virtual or physical) , reinstall the<br>
> correct OS/Profile, and then configure it automatically. This allows<br>
> me to get my servers from the factory preset to PXE, press the power<br>
> button and go.<br>
<br>
</span>It would be great to see an article about your setup (presuming your<br>
allowed by your employer to publish it) or maybe contrib some of your<br>
tooling around cobbler!<br>
<span class=""><br>
> I would like to see various functionality like this integrated<br>
> into the cobbler framework however... of particular interest is<br>
> turning on and off CPU components i.e. hyperthreading or<br>
> virtualization at the BIOS level.<br>
<br>
</span>I'd be pretty impressed if BIOS level settings are so<br>
standardized/exposed that it could really be integrated -- and would<br>
actually work -- in Cobbler!<br>
<br>
I'm not sure how much makes sense to integrate into cobbler proper<br>
(given that cobbler's sole goal should be installation of clients, not<br>
the configuration of the clients in some sense) but maybe in snippets<br>
(if the BIOS is exposed to the client from within the client).<br>
<br>
-Nish<br>
<br>
</blockquote></div><br></div>
[Attachment #6 (text/plain)]
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic