Re: [OSR-devel] Bug reports / fixes and iSCSI

[Gordan B. <go...@bo...>]

On Wed, 10 Oct 2007, Marc Grimme wrote:

>> 1) Python libraries assume python 2.3. RHEL5 (CentOS5 in my case) uses
>> python 2.4. That means that if this is intended for RHEL5, the libraries
>> should end up in /usr/lib/python2.4/site-packages/comoonics
>> At the moment, they end up in /usr/lib/python2.3/site-packages/comoonics,
>> which means they don't work.
> There should be a rhel5 channel available. It's not yet official but it proves
> to be quite stable. We are right now in the last steps before qa-ing.
> Use the following yum.repositories.
>
> [comoonics-preview]
> name=Packages for the comoonics shared root cluster
> baseurl=http://download.atix.de/yum/comoonics/redhat-el5/preview/noarch/
> enabled=1
> gpgcheck=1
> gpgkey=http://download.atix.de/yum/comoonics/comoonics-RPM-GPG.key
>
> [comoonics-preview-i386]
> name=Packages for the comoonics shared root cluster
> baseurl=http://download.atix.de/yum/comoonics/redhat-el5/preview/$arch
> enabled=1
> gpgcheck=1
> gpgkey=http://download.atix.de/yum/comoonics/comoonics-RPM-GPG.key
>
> [comoonics-addons]
> name=Addon Packages for utilities
> baseurl=http://download.atix.de/yum/comoonics/redhat-el5/addons/noarch/
> enabled=1
> gpgcheck=1
> gpgkey=http://download.atix.de/yum/comoonics/comoonics-RPM-GPG.key
>
> That will be anounced recently on www.opensharedroot.org.

OK, that seems to solve the problem of el4 packages creeping in and 
breaking things. :-)

>> 2) When making the initrd:
>>
>> 2.1) Extracting rpms...Cannot find rpm "comoonics-cs". Skipping.
>> Cannot find rpm "GFS". Skipping.
>> Cannot find rpm "ccs". Skipping.
>> Cannot find rpm "dlm". Skipping.
>> Cannot find rpm "fence". Skipping.
>> Cannot find rpm "magma". Skipping.
>> Cannot find rpm "magma-plugins". Skipping.
>> Cannot find rpm "OpenIPMI-tools". Skipping.
>>
>> Where can these be found, and where should they be put for this step to
>> find them?
> Follow the instructions on
> http://www.opensharedroot.org/documentation/rhel5-gfs-shared-root-mini-howto

I did. Nowhere does it manage yum installing packages GFS, ccs, dlm, 
fence, magma, magma-plugins or OpenIPMI-tools.

>> 2.2) Retrieving dependent
>> files.../opt/atix/comoonics-bootimage/boot-scripts/etc/chroot-lib.sh: line
>> 333: [: !=: unary operator expected
> you can ignore that.
>> found 3545
>>
>> What is actually causing this? I looked at the script, and I have a
>> feeling it's caused by the '#' comparison, but I'm not sure.
>
> We are aware of that *warning* but you can savely ignore it.

OK. Is it the '#' that kills it? What about "\#"?

>> 3) iSCSI - this doesn't appear to get included on the initrd. This is kind
>> of important. How do I add it, so that I can mount the SAN being used for
>> the shared GFS root?
>
> We did not implement it yet. Feel free to do it. Use the latest rpms and adapt
> the code. Latest HEAD rpms are attached.
> Please edit against them. And send either patches or the changed files
> directly to me.

OK. Presumably, this would mean:

1) Install standard iscsi-initiator-utils rpm into the OSR initrd.
2) Copy the /etc/iscsi/iscsid.conf /var/lib/iscsi/* into the OSR initrd
3) Add iscsi and iscsid init scripts to the relevant run-level on OSR 
initrd.

On a separate note - the instructions say that /etc/sysconfig/network is 
to be unshared. I think /etc/sysconfig/network-scripts should be unshared, 
too, unless all IPs are assigned via DHCP - which may or may not be the 
case. Although if they were assigned by DHCP, that would be kind of neat 
because it would mean you can purely network boot them via PXE (even if 
the initrd is 50MB+!).

> Find more information here:
> http://www.opensharedroot.org/Members/marc/blog/comoonics-bootimage/concept-of-integrating-iscsi-support-to-latest-bootimage
> You should be able to add comments or just send me an email on what you think.

Hmm. Do we need this specified in cluster.conf?
Are the rootsource, rootvolume and chrootenv tags the standard way to 
achieve this?

> If you need more bins or rpms included in the initrd (which I expect to be)
> have a look at /etc/comoonics/bootimage/files.initrd.d
> and /etc/comoonics/bootimage/rpms.initrd.d.

Thanks for that. Do you envisage anything over and above what I listed 
above to be required? I'm not quite up to speed on the cluster.conf stuff, 
but would the 3 steps to get iSCSI going be sufficient to get the initrd 
connectable to the SAN at least? Once it gets that far, even mounting the 
root manually wouldn't be too bad.

Incidentally, how is the fencing/cluster stuff handled in the initrd? I 
didn't notice cman being included.

> Have fun and thanks (hope you'll enjoy the open-sharedroot concept as much as
> we do)

Thank you for responding, I appreciate it.

Gordan