10:24 p.m.
Hi,
Last week I asked RDO related question in CentOS-devel mail list, you
can see the question from bottom link [1]. Thanks for Alfredo kindly
help.
After we do some POC to build packages in link [2] , I still have some
questions:
1. We want contribute to RDO community, let RDO add s390x architecture
build. As there is no CentOS s390x architecture build in CentOS
repositories, we can only build and test RDO packages in RHEL, Is it
possiable we add RDO s390x build without CentOS s390x architecture
build? Build CentOS might need much more effort and time.
2. I'm trying building RDO Train packages in [2] in RHEL 8 on LinuxONE,
seems there are some package missing, such as python-d2to1. Should I
switch to build RDO Train in RHEL 7 as the start step, wait until RDO
train for CentOS 8 is ready?
3. For RDO Train on RHEL 8, can I expect python 3 is the default Python
interpreter for all OpenStack packages and dependecy packages?
Thank you.
[1]
https://lists.centos.org/pipermail/centos-devel/2019-October/017948.html
[2] https://trunk.rdoproject.org/rhel8-master/
--
Shi Lin, Huang
shilinh(a)cn.ibm.com
IBM China Systems Lab, Beijing, China
3:21 a.m.
1. We want contribute to RDO community, let RDO add s390x
architecture
build. As there is no CentOS s390x architecture build in CentOS
repositories, we can only build and test RDO packages in RHEL, Is it
possiable we add RDO s390x build without CentOS s390x architecture
build? Build CentOS might need much more effort and time.
yes, we could publish your RHEL rebuilds as an experimental repo
outside CentOS CloudSIG
2. I'm trying building RDO Train packages in [2] in RHEL 8 on
LinuxONE,
seems there are some package missing, such as python-d2to1. Should I
switch to build RDO Train in RHEL 7 as the start step, wait until RDO
train for CentOS 8 is ready?
Build dependency d2to1 should have been gone, we need to fix that.
In which package did you hit it?
3. For RDO Train on RHEL 8, can I expect python 3 is the default
Python
interpreter for all OpenStack packages and dependecy packages?
yes, RHEL8 is python3 only
Cheers,
Alan
4:15 a.m.
On Fri, Oct 18, 2019 at 10:22 AM Alan Pevec <apevec(a)redhat.com> wrote:
> 1. We want contribute to RDO community, let RDO add s390x
architecture
> build. As there is no CentOS s390x architecture build in CentOS
> repositories, we can only build and test RDO packages in RHEL, Is it
> possiable we add RDO s390x build without CentOS s390x architecture
> build? Build CentOS might need much more effort and time.
yes, we could publish your RHEL rebuilds as an experimental repo
outside CentOS CloudSIG
> 2. I'm trying building RDO Train packages in [2] in RHEL 8 on LinuxONE,
> seems there are some package missing, such as python-d2to1. Should I
> switch to build RDO Train in RHEL 7 as the start step, wait until RDO
> train for CentOS 8 is ready?
Build dependency d2to1 should have been gone, we need to fix that.
In which package did you hit it?
It's still in several packages:
https://codesearch.rdoproject.org/?q=d2to1&i=nope&files=&repos=
It may be worthy to check if those are actually required or we can clean it
up. Until then, you can try to rebuild it from fedora:
https://src.fedoraproject.org/rpms/python-d2to1
> 3. For RDO Train on RHEL 8, can I expect python 3 is the default
Python
> interpreter for all OpenStack packages and dependecy packages?
yes, RHEL8 is python3 only
Cheers,
Alan
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
4:48 a.m.
> Build dependency d2to1 should have been gone, we need to fix
that.
> In which package did you hit it?
>
It's still in several packages:
https://codesearch.rdoproject.org/?q=d2to1&i=nope&files=&repos=
It may be worthy to check if those are actually required or we can clean it up. Until
then, you can try to rebuild it from fedora:
afact it's just leftover copy/paste all the way from original
nova.spec, I've opened
https://trello.com/c/HGvX9Xat/720-cleanup-br-d2to1
Cheers,
Alan
5:23 a.m.
On Fri, Oct 18, 2019 at 11:48 AM Alan Pevec <apevec(a)redhat.com> wrote:
>> Build dependency d2to1 should have been gone, we need to fix
that.
>> In which package did you hit it?
>>
>
> It's still in several packages:
>
> https://codesearch.rdoproject.org/?q=d2to1&i=nope&files=&repos=
>
> It may be worthy to check if those are actually required or we can clean
it up. Until then, you can try to rebuild it from fedora:
afact it's just leftover copy/paste all the way from original
nova.spec, I've opened
https://trello.com/c/HGvX9Xat/720-cleanup-br-d2to1
Yes, it seems it's not longer used upstream:
http://codesearch.openstack.org/?q=d2to1&i=nope&files=.*requireme...
Cheers,
Alan
8:04 p.m.
On 2019-10-18 16:21, Alan Pevec wrote:
> 1. We want contribute to RDO community, let RDO add s390x
architecture
> build. As there is no CentOS s390x architecture build in CentOS
> repositories, we can only build and test RDO packages in RHEL, Is it
> possiable we add RDO s390x build without CentOS s390x architecture
> build? Build CentOS might need much more effort and time.
yes, we could publish your RHEL rebuilds as an experimental repo
outside CentOS CloudSIG
Hi Alan,
Now we are able to run OpenStack Train version on RHEL 8 on LinuxONE.
These are what we've archived:
1. We can use PackStack to install/deploy OpenStack on LinuxONE, we
tested all-in-one mode and multipul compute nodes mode.
2. We've run basic OpenStack test cases. We've test Keystone, Glance,
Nova, Neutron, Heat, Horizon, Placement, Ceilometer etc.
3. We will continue to build new packages once RDO Train(for rhel8) has
packages update
As a follow-up and we want to contribute those LinuxONE packages to
RDO community, we have some questions need help:
1. Is there a server we can upload those packages for LinuxONE? E.g, use
this repo as a experimental repo for LinuxONE.
2. Now we run test with Packstack on RHEL8 manually, if we want to make
RDO support LinuxONE officially, is CI system a requiment?
--
Shi Lin, Huang
shilinh(a)cn.ibm.com
IBM China Systems Lab, Beijing, China
4:31 a.m.
Hi,
thanks for the update!
1. Is there a server we can upload those packages for LinuxONE? E.g,
use
this repo as a experimental repo for LinuxONE.
Since those packages are built outside RDO infra, please publish them
at your public location and we can link to it in the docs.
Since we do not have this hardware available in the community infra,
we would rely on you to write a howto documentation and send PR to
github.com/redhat-openstack/website/
it would fit under https://www.rdoproject.org/install/
2. Now we run test with Packstack on RHEL8 manually, if we want to
make
RDO support LinuxONE officially, is CI system a requiment?
Please note "support" is an overloaded term, for community projects
that means we as a community tried it and it worked, and yes CI would
definitely be a part of our community release criteria.
For "official official" we would also need to build packages in the
CentOS build system which then requires this arch in CentOS first and
that will take time.
I think for now external repo with a doc how to set it up on ONE will
be good progress!
Also, OpenStack packages are noarch so we could combine RDO Trunk and
your repo with arch-specific dependencies.
I'm looking forward to your howto to see how you're actually running it now.
Cheers,
Alan
2:11 a.m.
Hi Alan,
Finally, we prepared all we need to make RDO for LinuxONE avaiable.
We've prepared HowTo docs, and create a PR to RDO website project,
the PR link is:
https://github.com/redhat-openstack/website/pull/1355
In the PR you can find RDO dependency packages for LinuxONE s390x
architecture. The link is:
http://linuxone.cloud.marist.edu:8080/repos/rdo/rhel8.0
Now we've tested deploy RDO Train version on RHEL 8.0, we will
continue to update this doc once we make more progress, such as
test on RHEL 8.1 etc.
Thank you for all your helping in past several months.
--
Shi Lin, Huang
shilinh(a)cn.ibm.com
IBM China Systems Lab, Beijing, China
1:09 a.m.
Hi Alan and the Admin Team,
Much appreciate for the help in our previous project phase!!!
Now, we can share the built with worldwide users & fans, it's really a
valuable milestone for our efforts!
No doubt, this is just the beginning of our contribution to the
community, we will try our best to continuously feedback and improve the
delivery to community and end users.
I'm the project manager of the OpenStack Enablement on LinuxONE and we
would like to go further to seriously consider the "official official"
step you mentioned in last mail.
We want to have a deep collaboration with CentOS community to make the
CentOS for s390x architect available first and then the CI env.
But we only have a little idea about building, testing and releasing a
Linux operating system, not actually knowing how much processes, skills
and efforts involved and in which part of the processes need IBM team's
input/efforts.
We may can managed to afford a remote hardware resource to share to
community inside US for this purpose and so need a detailed resource
requirements for further evaluation inside our business unit.
Would you like to shed light on the overall processes, step by step
procedures/requirements and a roughly estimation for enablement duration?
Thanks in advance!
Cheers
FuLong
On 1/10/20 18:31, Alan Pevec wrote:
Hi,
thanks for the update!
> 1. Is there a server we can upload those packages for LinuxONE? E.g, use
> this repo as a experimental repo for LinuxONE.
Since those packages are built outside RDO infra, please publish them
at your public location and we can link to it in the docs.
Since we do not have this hardware available in the community infra,
we would rely on you to write a howto documentation and send PR to
github.com/redhat-openstack/website/
it would fit underhttps://www.rdoproject.org/install/
> 2. Now we run test with Packstack on RHEL8 manually, if we want to make
> RDO support LinuxONE officially, is CI system a requiment?
Please note "support" is an overloaded term, for community projects
that means we as a community tried it and it worked, and yes CI would
definitely be a part of our community release criteria.
For "official official" we would also need to build packages in the
CentOS build system which then requires this arch in CentOS first and
that will take time.
I think for now external repo with a doc how to set it up on ONE will
be good progress!
Also, OpenStack packages are noarch so we could combine RDO Trunk and
your repo with arch-specific dependencies.
I'm looking forward to your howto to see how you're actually running it now.
Cheers,
Alan
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe:dev-unsubscribe@lists.rdoproject.org
--
FuLong Wang
fulong.wang(a)cn.ibm.com
IBM China Systems Lab, Beijing, China
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe:dev-unsubscribe@lists.rdoproject.org
1861
days inactive
2006
days old
8 comments
4 participants
participants (4)
-
Alan Pevec -
Alfredo Moralejo Alonso -
FuLong Wang -
Shi Lin Huang