All of lore.kernel.org
 help / color / mirror / Atom feed
From: Two Spirit <twospirit6905@gmail.com>
To: Sage Weil <sweil@redhat.com>
Cc: Alfredo Deza <adeza@redhat.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Bug? luminous pkg missing ceph-osd ceph-mon 32bit
Date: Wed, 30 Aug 2017 08:38:04 -0700	[thread overview]
Message-ID: <CAKRxpuvZKNMaMdUsSSNy+7CDG5sL=o=C+bsEBYs-RFPz=Fnpbw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1708292138430.20435@piezo.novalocal>

Thanks for the reply. I totally understand the limited resource thing.
I'd totally would do it, but my skills in configuration management is
out of date.

If you guys can build a 32 bit version, I will add equipment to test it.

From my perspective, the cost of doing large scale simulated testing
is lower with the 32 bit support.

The same goes for support for Ubuntu's non LTS releases.

I support a lot of heterogeneous networks. The sell is harder to get
clients to give a lot of money to setup a whole new unproven file
system and R&D time. It's got to work on existing equipment. I see two
environments. One that needs stable production environment, and one
that needs the latest and greatest(for it's time), and that equipment
is not running LTS releases.

If I can't install it, I can't test it.

On Tue, Aug 29, 2017 at 2:41 PM, Sage Weil <sweil@redhat.com> wrote:
> On Tue, 29 Aug 2017, Two Spirit wrote:
>> is it the plan to eventually support 32 bit, or is it only supported on
>> 64 bit?
>
> It depends on whether someone is willing to fix the 32-bit build issues
> and get a 32-bit jenkins builder set up (so that new build problems aren't
> introduced).  There isn't much interest among the current devs, but nobody
> is opposed!
>
> Actually producing release artifacts for 32-bit is a bit more work; that
> depends on how slow and/or reliable the 32-bit build is.
>
> There has never been (and likely won't ever be?) any real QA done on the
> 32-bit builds.
>
> sage
>
>
>>
>> On Mon, Aug 28, 2017 at 5:11 AM, Alfredo Deza <adeza@redhat.com> wrote:
>> > On Fri, Aug 25, 2017 at 11:40 AM, Two Spirit <twospirit6905@gmail.com> wrote:
>> >> the target osd was a ubuntu 16.04 x32
>> >>
>> >> On Fri, Aug 25, 2017 at 8:35 AM, Two Spirit <twospirit6905@gmail.com> wrote:
>> >>> I built 64 bit ubuntu 16.04 and 14.04 (using crush tunables legacy)
>> >>> systems, and I tried to build a 32 bit system, and it complained
>> >>> about missing packages so if there is such a thing, I think it might
>> >>> be related to 32 bit repository. ubuntu 15.04 doesn't work either, but
>> >>> I'm not sure if it is supported.
>> >
>> > We haven't built any 32bit binaries in a while although the repos
>> > might exist (although they are empty).
>> >
>> >>>
>> >>> adminhost$ ceph-deploy install --release luminous vm143
>> >>>
>> >>> [vm143][DEBUG ] Get:2 http://us.archive.ubuntu.com/ubuntu
>> >>> xenial-updates InRelease [102 kB]
>> >>> [vm143][DEBUG ] Get:3 http://security.ubuntu.com/ubuntu
>> >>> xenial-security InRelease [102 kB]
>> >>> [vm143][DEBUG ] Get:4 http://us.archive.ubuntu.com/ubuntu
>> >>> xenial-backports InRelease [102 kB]
>> >>> [vm143][DEBUG ] Hit:5 https://download.ceph.com/debian-luminous xenial InRelease
>> >>> [vm143][DEBUG ] Fetched 306 kB in 1s (172 kB/s)
>> >>> [vm143][DEBUG ] Reading package lists...
>> >>> [vm143][INFO  ] Running command: sudo env
>> >>> DEBIAN_FRONTEND=noninteractive DEBIAN_PRIORITY=critical apt-get
>> >>> --assume-yes -q --no-install-recommends install -o
>> >>> Dpkg::Options::=--force-confnew ceph ceph-osd ceph-mds ceph-mon
>> >>> radosgw
>> >>> [vm143][DEBUG ] Reading package lists...
>> >>> [vm143][DEBUG ] Building dependency tree...
>> >>> [vm143][DEBUG ] Reading state information...
>> >>> [vm143][WARNING] E: Unable to locate package ceph-osd
>> >>> [vm143][WARNING] E: Unable to locate package ceph-mon
>> >>> [vm143][ERROR ] RuntimeError: command returned non-zero exit status: 100
>> >>> [ceph_deploy][ERROR ] RuntimeError: Failed to execute command: env
>> >>> DEBIAN_FRONTEND=noninteractive DEBIAN_PRIORITY=critical apt-get
>> >>> --assume-yes -q --no-install-recommends install -o
>> >>> Dpkg::Options::=--force-confnew ceph ceph-osd ceph-mds ceph-mon
>> >>> radosgw
>> >>> <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
>> >>> <table style="border-top: 1px solid #D3D4DE;">
>> >>>         <tr>
>> >>>         <td style="width: 55px; padding-top: 13px;"><a
>> >>> href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
>> >>> target="_blank"><img
>> >>> src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png"
>> >>> alt="" width="46" height="29" style="width: 46px; height: 29px;"
>> >>> /></a></td>
>> >>>                 <td style="width: 470px; padding-top: 12px; color: #41424e;
>> >>> font-size: 13px; font-family: Arial, Helvetica, sans-serif;
>> >>> line-height: 18px;">Virus-free. <a
>> >>> href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
>> >>> target="_blank" style="color: #4453ea;">www.avg.com</a>
>> >>>                 </td>
>> >>>         </tr>
>> >>> </table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1"
>> >>> height="1"></a></div>
>> >> --
>> >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> >> the body of a message to majordomo@vger.kernel.org
>> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>

  reply	other threads:[~2017-08-30 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 15:35 Bug? luminous pkg missing ceph-osd ceph-mon 32bit Two Spirit
2017-08-25 15:40 ` Two Spirit
2017-08-28 12:11   ` Alfredo Deza
2017-08-29 21:36     ` Two Spirit
2017-08-29 21:41       ` Sage Weil
2017-08-30 15:38         ` Two Spirit [this message]
2017-08-30 16:58           ` Two Spirit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKRxpuvZKNMaMdUsSSNy+7CDG5sL=o=C+bsEBYs-RFPz=Fnpbw@mail.gmail.com' \
    --to=twospirit6905@gmail.com \
    --cc=adeza@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.