Re: RFC: Disk specification by classes/tags
Thomas Sanders <[email protected]> Tue, 6 Sep 2016 13:14:13 -0700
| Newsgroups | gmane.linux.redhat.kickstart.general |
|---|---|
| Message-ID | <CAD3gjcHdGVscbKoX6=217Tyn6Nq5XsZj5uDpDdF13SE5L_u_Pg@mail.gmail.com> |
--===============3435912267459592580== Content-Type: multipart/alternative; boundary=001a11446ebcbf8d2f053bdc70ec --001a11446ebcbf8d2f053bdc70ec Content-Type: text/plain; charset=UTF-8 +1 @local etc. I like the idea that C. Petro has of setting up tags in %PRE, however @local and possibly others should be immutable. On Tue, Aug 30, 2016 at 1:36 PM, C. Petro <[email protected]> wrote: > > I know we can already hardcode which disk to use (--ondisk=sda) > > When building a kickstart configuration for two or more types of > machines sometimes that *doesn't* work. > > Last time I went through that I had Dell R620XDs (IIRC) and these > awful SuperMicro boxes that had a windows only raid controller and I > had to scriptomagically bang sdb and sdc together to get a predictable > MD0. The sda device was present, but didn't work. > > What would be *really* cool is a couple of built in tags (@local, > @remote, etc.) but also a way to define NEW tags on the fly--for > example having a PRE script that creates an MD device then tags that > as @fred or one that goes looking for a drive with particular > characteristics (say for example I have a HP DL380G8 with 3 onboard > RAID controllers and want to strip my data RAID across them, I can > look for the first drive on each controller and make them a RAID 1, > then the next X drives as a PV, and the last Y drives as a second PV > etc.. > > > but I'd like to be able to tell kickstart to use only the 1st disk > found, or at > least confine the kickstart to 1 drive. > > On Mon, Aug 29, 2016 at 6:31 PM, Steve Rikli <[email protected]> wrote: > > On Mon, Aug 29, 2016 at 03:44:09PM -0400, David Lehman wrote: > >> > >> I work on blivet, which is the storage management backend for > >> anaconda/kickstart. I'm working on a feature that was inspired by > >> discussion on this list: specification of disks by class/tag. > >> Eventually, I imagine this capability will be plumbed through kickstart > >> and anaconda. > >> > >> In the interest of determining how much machinery I should build into > >> this, I'm soliciting use-cases for this type of filtering. Here's what > >> I have so far: > >> > >> # do autopart, but only use local drives > >> ignoredisk --onlyuse=@local > >> autopart > >> > >> # make sure /boot goes on a local drive > >> part /boot??--ondisk=@local > >> > >> # make sure a pv that backs an lvm cache lv goes on the ssd > >> part pv.cache.0 --fstype=lvmpv --size=4096 --grow --ondisk=@ssd > >> > >> # put a data volume on a shared SAN volume > >> part /shared --size=100000 --grow --ondisk=@remote > >> > >> > >> What kinds of restrictions do you wish you could easily place on disk > >> sets in your kickstart configurations? > > > > I know we can already hardcode which disk to use (--ondisk=sda) but I'd > > like to be able to tell kickstart to use only the 1st disk found, or at > > least confine the kickstart to 1 drive. > > > > You're in the same ballpark with @local (+ @<disktype> maybe?) but e.g. > > if I have a pair of SSD and I want the 2nd one to be used for non-sysdisk > > duties, today I think I have to use disk names. > > > > Thanks for looking into this sort of enhancement. Even just the above > > ideas are potentially helpful. > > > > sr. > > > > _______________________________________________ > > Kickstart-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/kickstart-list > --001a11446ebcbf8d2f053bdc70ec Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">+1 @local etc.<div>I like the idea that C. Petro has of se= tting up tags in %PRE, however @local and possibly others should be immutab= le.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On= Tue, Aug 30, 2016 at 1:36 PM, C. Petro <span dir=3D"ltr"><<a href=3D"ma= ilto:[email protected]" target=3D"_blank">[email protected]</a>></span> wrot= e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l= eft:1px #ccc solid;padding-left:1ex"><span class=3D"">> I know we can al= ready hardcode which disk to use (--ondisk=3Dsda)<br> <br> </span>When building a kickstart configuration for two or more types of<br> machines sometimes that *doesn't* work.<br> <br> Last time I went through that I had Dell R620XDs (IIRC) and these<br> awful SuperMicro boxes that had a windows only raid controller and I<br> had to scriptomagically bang sdb and sdc together to get a predictable<br> MD0. The sda device was present, but didn't work.<br> <br> What would be *really* cool is a couple of built in tags (@local,<br> @remote, etc.) but also a way to define NEW tags on the fly--for<br> example having a PRE script that creates an MD device then tags that<br> as @fred or one that goes looking for a drive with particular<br> characteristics (say for example I have a HP DL380G8 with 3 onboard<br> RAID controllers and want to strip my data RAID across them, I can<br> look for the first drive on each controller and make them a RAID 1,<br> then the next X drives as a PV, and the last Y drives as a second PV<br> etc..<br> <span class=3D"im HOEnZb"><br> > but I'd like to be able to tell kickstart to use only the 1st disk= found, or at<br> least confine the kickstart to 1 drive.<br> <br> </span><div class=3D"HOEnZb"><div class=3D"h5">On Mon, Aug 29, 2016 at 6:31= PM, Steve Rikli <<a href=3D"mailto:[email protected]">[email protected]</a>= > wrote:<br> > On Mon, Aug 29, 2016 at 03:44:09PM -0400, David Lehman wrote:<br> >><br> >> I work on blivet, which is the storage management backend for<br> >> anaconda/kickstart. I'm working on a feature that was inspired= by<br> >> discussion on this list: specification of disks by class/tag.<br> >> Eventually, I imagine this capability will be plumbed through kick= start<br> >> and anaconda.<br> >><br> >> In the interest of determining how much machinery I should build i= nto<br> >> this, I'm soliciting use-cases for this type of filtering. Her= e's what<br> >> I have so far:<br> >><br> >> # do autopart, but only use local drives<br> >> ignoredisk --onlyuse=3D@local<br> >> autopart<br> >><br> >> # make sure /boot goes on a local drive<br> >> part /boot??--ondisk=3D@local<br> >><br> >> # make sure a pv that backs an lvm cache lv goes on the ssd<br> >> part pv.cache.0 --fstype=3Dlvmpv --size=3D4096 --grow --ondisk=3D@= ssd<br> >><br> >> # put a data volume on a shared SAN volume<br> >> part /shared --size=3D100000 --grow --ondisk=3D@remote<br> >><br> >><br> >> What kinds of restrictions do you wish you could easily place on d= isk<br> >> sets in your kickstart configurations?<br> ><br> > I know we can already hardcode which disk to use (--ondisk=3Dsda) but = I'd<br> > like to be able to tell kickstart to use only the 1st disk found, or a= t<br> > least confine the kickstart to 1 drive.<br> ><br> > You're in the same ballpark with @local (+ @<disktype> maybe= ?) but e.g.<br> > if I have a pair of SSD and I want the 2nd one to be used for non-sysd= isk<br> > duties, today I think I have to use disk names.<br> ><br> > Thanks for looking into this sort of enhancement.=C2=A0 Even just the = above<br> > ideas are potentially helpful.<br> ><br> > sr.<br> ><br> > ______________________________<wbr>_________________<br> > Kickstart-list mailing list<br> > <a href=3D"mailto:[email protected]">[email protected]= </a><br> > <a href=3D"https://www.redhat.com/mailman/listinfo/kickstart-list" rel= =3D"noreferrer" target=3D"_blank">https://www.redhat.com/<wbr>mailman/listi= nfo/kickstart-<wbr>list</a><br> <br> ______________________________<wbr>_________________<br> Kickstart-list mailing list<br> <a href=3D"mailto:[email protected]">[email protected]</a><= br> <a href=3D"https://www.redhat.com/mailman/listinfo/kickstart-list" rel=3D"n= oreferrer" target=3D"_blank">https://www.redhat.com/<wbr>mailman/listinfo/k= ickstart-<wbr>list</a><br> </div></div></blockquote></div><br></div> --001a11446ebcbf8d2f053bdc70ec-- --===============3435912267459592580== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kickstart-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/kickstart-list --===============3435912267459592580==--