[nova][libvirt] Support for MIPS architecture?
Hi I'm trying to run openstack on a host with MIPS architecture, but got some errors, and I have fixed them. Many people around me use hosts with MIPS architecture. We hope the official can add support for MIPS and we can maintain it. Thanks, xiaolin
On Fri, 2020-06-05 at 17:51 +0800, 赵晓琳 wrote:
Hi I'm trying to run openstack on a host with MIPS architecture, but got some errors, and I have fixed them. Many people around me use hosts with MIPS architecture. We hope the official can add support for MIPS and we can maintain it. Thanks, xiaolin to state that mips is fully supported would require an automated ci running on mips hardware. if you can provide ci resources either to the first party ci or via a third party ci that projects can consume we may be able to test that the basic functionality works. in the long run support for other architectures really required a concerted effort from a vendor or community that runs openstack on that architecture.
there recently has been a effort to add more aarch64 testing but traditionally anything that was not x86 fell to third party hardware vendors to test via third party ci. i.e. the ibm provided powerVM and power KVM CIs to test nova on power pc.
OpenStack also has a Multi-Arch Special Interest Group: https://docs.openstack.org/multi-arch-sig/latest/index.html Although (as Sean says) most non-x86 efforts are currently around aarch64, the Multi-Arch Special Interest Group is still interested in tracking (and, if possible, facilitating) MIPS-related efforts. On Fri, Jun 5, 2020 at 7:39 AM Sean Mooney <smooney@redhat.com> wrote:
On Fri, 2020-06-05 at 17:51 +0800, 赵晓琳 wrote:
Hi I'm trying to run openstack on a host with MIPS architecture, but got some errors, and I have fixed them. Many people around me use hosts with MIPS architecture. We hope the official can add support for MIPS and we can maintain it. Thanks, xiaolin to state that mips is fully supported would require an automated ci running on mips hardware. if you can provide ci resources either to the first party ci or via a third party ci that projects can consume we may be able to test that the basic functionality works. in the long run support for other architectures really required a concerted effort from a vendor or community that runs openstack on that architecture.
there recently has been a effort to add more aarch64 testing but traditionally anything that was not x86 fell to third party hardware vendors to test via third party ci. i.e. the ibm provided powerVM and power KVM CIs to test nova on power pc.
Thanks for the help. We will pay attention to the Multi-Arch Special Interest Group, and provide CI resources to the openstack community as soon as possible. > > OpenStack also has a Multi-Arch Special Interest Group: > https://docs.openstack.org/multi-arch-sig/latest/index.html > > Although (as Sean says) most non-x86 efforts are currently around > aarch64, the Multi-Arch Special Interest Group is still interested in > tracking (and, if possible, facilitating) MIPS-related efforts. > > > > On Fri, Jun 5, 2020 at 7:39 AM Sean Mooney <smooney@redhat.com> wrote: > > > > On Fri, 2020-06-05 at 17:51 +0800, 赵晓琳 wrote: > > > Hi I'm trying to run openstack on a host with MIPS architecture, but got some errors, and I have fixed > > > them. Many people around me use hosts with MIPS architecture. We hope the official can add support for MIPS and we > > > can maintain it. Thanks, xiaolin > > to state that mips is fully supported would require an automated ci running on mips hardware. > > if you can provide ci resources either to the first party ci or via a third party ci that projects can consume > > we may be able to test that the basic functionality works. in the long run support for other architectures really > > required a concerted effort from a vendor or community that runs openstack on that architecture. > > > > there recently has been a effort to add more aarch64 testing but traditionally anything that was not x86 fell to > > third party hardware vendors to test via third party ci. i.e. the ibm provided powerVM and power KVM CIs to test nova on > > power pc. > > > > </smooney@redhat.com>
We can provide ci resources to the first party. But, sorry, what detailed ci resources do we need to provide? and how to provide? Do you mean KVM and hosts with MIPS architecture? On Fri, Jun 5, 2020 at 7:39 AM Sean Mooney <smooney@redhat.com> wrote: > > On Fri, 2020-06-05 at 17:51 +0800, 赵晓琳 wrote: > > Hi I'm trying to run openstack on a host with MIPS architecture, but got some errors, and I have fixed > > them. Many people around me use hosts with MIPS architecture. We hope the official can add support for MIPS and we > > can maintain it. Thanks, xiaolin > to state that mips is fully supported would require an automated ci running on mips hardware. > if you can provide ci resources either to the first party ci or via a third party ci that projects can consume > we may be able to test that the basic functionality works. in the long run support for other architectures really > required a concerted effort from a vendor or community that runs openstack on that architecture. > > there recently has been a effort to add more aarch64 testing but traditionally anything that was not x86 fell to > third party hardware vendors to test via third party ci. i.e. the ibm provided powerVM and power KVM CIs to test nova on > power pc. </smooney@redhat.com>
On 2020-06-06 14:35:41 +0800 (+0800), 赵晓琳 wrote:
We can provide ci resources to the first party. But, sorry, what detailed ci resources do we need to provide? and how to provide? Do you mean KVM and hosts with MIPS architecture? [...]
Here's a bit of documentation on the process and what you can expect: https://docs.opendev.org/opendev/system-config/latest/contribute-cloud.html -- Jeremy Stanley
participants (4)
-
Jeremy Freudberg
-
Jeremy Stanley
-
Sean Mooney
-
赵晓琳