Re: [OpenStack-Infra] Adding ARM64 cloud to infra
On 01/12/2018 07:21 PM, Clark Boylan wrote:
> On Fri, Jan 12, 2018, at 3:27 PM, Dan Radez wrote:
>> fwiw
>> We've been building arm images for tripleo and posting them.
>> https://images.rdoproject.org/aarch64/pike/delorean/current-tripleo-rdo/
>>
>>
>> This uses delorean and overcloud build:
>>
>> DIB_YUM_REPO_CONF+="/etc/yum.repos.d/delorean-deps-${OSVER}.repo
>> /etc/yum.repos.d/delorean-${OSVER}.repo /etc/yum.repos.d/ceph.repo
>> /etc/yum.repos.d/epel.repo /etc/yum.repos.d/radez.fedorapeople.repo" \
>> openstack --debug overcloud image build \
>> --config-file overcloud-aarch64.yaml \
>> --config-file
>> /usr/share/openstack-tripleo-common/image-yaml/overcloud-images.yaml \
>> --config-file
>> /usr/share/openstack-tripleo-common/image-yaml/overcloud-images-centos7.yaml
>> # --config-file overcloud-images.yaml --config-file
>> overcloud-images-centos7.yaml --config-file aarch64-gumpf.yaml --image-name
>> #openstack --debug overcloud image build --type overcloud-full
>> --node-arch aarch64
>>
>> It's not quite an orthodox RDO build, There are still a few things in
>> place that work around arm related packaging discrepancies or x86
>> related configs. But we get good builds from it.
>>
>> I don't know the details of what overcloud build does to the dib builds,
>> Though I don't believe these are whole disk images. I think the
>> overcloud and undercloud are root partition images and the kernel an
>> initrd are composed into the disk for the overcloud by OOO and we direct
>> boot them to launch a undercloud VM.
>>
>> Happy to share details if anyone wants more.
>>
>> Radez
> Looking into this a big more `openstack overcloud image build` takes in the
> yaml config files you list and converts that into a forked diskimage-builder
> process to build an image. The centos7 dib element in particular seems to
> have aarch64 support via building on top of the upstream centos7 aarch64
> image. We do use the centos-minimal element for our images though as it
> allows us to do things like install glean. Chances are we still need need to
> sort out UEFI and GPT for general dib use.
>
> Just to be sure there isn't any other magic going on can you provide the
> contents of the overcloud-aarch64.yaml or point to where it can be found? It
> doesn't appear to be in tripleo-common with the other configs.
>
> It is good to know that this is working in some cases though.
>
> Clark
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
The centos support that's there is because I added it. :)
Here's the overcloud-aarch64 file, Its purpose is just to switch the
arch for the two images built.
I think the packages reference was because there was a missing dep that
has since been resolved.
[stack@localhost ~]$ cat overcloud-aarch64.yaml
disk_images:
-
imagename: overcloud-full
arch: arm64
packages:
- os-collect-config
-
imagename: ironic-python-agent
arch: arm64
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Adding ARM64 cloud to infra
fwiw
We've been building arm images for tripleo and posting them.
https://images.rdoproject.org/aarch64/pike/delorean/current-tripleo-rdo/
This uses delorean and overcloud build:
DIB_YUM_REPO_CONF+="/etc/yum.repos.d/delorean-deps-${OSVER}.repo
/etc/yum.repos.d/delorean-${OSVER}.repo /etc/yum.repos.d/ceph.repo
/etc/yum.repos.d/epel.repo /etc/yum.repos.d/radez.fedorapeople.repo" \
openstack --debug overcloud image build \
--config-file overcloud-aarch64.yaml \
--config-file
/usr/share/openstack-tripleo-common/image-yaml/overcloud-images.yaml \
--config-file
/usr/share/openstack-tripleo-common/image-yaml/overcloud-images-centos7.yaml
# --config-file overcloud-images.yaml --config-file
overcloud-images-centos7.yaml --config-file aarch64-gumpf.yaml --image-name
#openstack --debug overcloud image build --type overcloud-full
--node-arch aarch64
It's not quite an orthodox RDO build, There are still a few things in
place that work around arm related packaging discrepancies or x86
related configs. But we get good builds from it.
I don't know the details of what overcloud build does to the dib builds,
Though I don't believe these are whole disk images. I think the
overcloud and undercloud are root partition images and the kernel an
initrd are composed into the disk for the overcloud by OOO and we direct
boot them to launch a undercloud VM.
Happy to share details if anyone wants more.
Radez
On 01/12/2018 09:59 AM, Jeremy Stanley wrote:
> On 2018-01-12 11:17:33 +0100 (+0100), Marcin Juszkiewicz wrote:
> [...]
>> I am aware that you like to build disk images on your own but have
>> you considered using virt-install with generated preseed/kickstart
>> files? It would move several arch related things (like bootloader)
>> to be handled by distribution rules instead of handling them again
>> in code.
> [...]
>
> We pre-generate and upload images via Glance because it allows us to
> upload the same image to all providers (modulo processor
> architecture in this case obviously). Once we have more than one
> arm64 deployment to integrate, being able to know that we're
> uploading identical images to all of them will be useful from a
> consistency standpoint. Honestly, getting EFI bits into DIB is
> probably no harder than writing a new nodepool builder backend to do
> remote virt-install, and would be of use to a lot more people when
> implemented.
>
> If you look in
> http://git.openstack.org/cgit/openstack/diskimage-builder/tree/diskimage_builder/elements/bootloader/finalise.d/50-bootloader
> there's support for setting up ppc64 PReP boot partitions... I don't
> expect getting correct EFI partition creation integrated would be
> much tougher? That said, it's something the DIB maintainers will
> want to weigh in on obviously.
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] openstackid.org
On 01/06/2015 01:24 PM, Jeremy Stanley wrote: On 2015-01-06 07:13:27 +0100 (+0100), Marton Kiss wrote: Let's talk I can help you. You have two options here, implement an OpenID authentication, or use the Oauth2 for the login. For community portal we are just finishing the migration to oauth2 because it can additionally provide user pictures. We also running a staging server at openstackid-dev.openstack.org for development purposes. Based on Morgan's response in IRC that Keystone doesn't support OAuth2 (only a funky 1.1 implementation), it sounds like you're stuck using the OpenID (oidc) support in Keystone's master branch. Thx for bringing this up, I didn't see the comment about 1.1 only. Dan ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
