From: "Dingo" <dingo@optimcloud.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] is meta-cloud-services/meta-openstack useable, or a WIP ?
Date: Tue, 27 Oct 2020 19:28:15 +0700 [thread overview]
Message-ID: <f0be59b1-3e21-8520-ecc4-934d0a84df38@optimcloud.com> (raw)
In-Reply-To: <CADkTA4MwLP4ScGjjZN4uhA=sAj1g2fZefWj71rpotrPrhVdLXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On 10/27/20 7:07 PM, Bruce Ashfield wrote:
> On Tue, Oct 27, 2020 at 5:16 AM Yocto <yocto@optimcloud.com> wrote:
>> okay reading the doc README it states
>>
>> There are six openstack layers that are used to build a controller/compute
>> node image pair. The dependencies of these layers are also required for a
>> build, and are listed in the layers themselves.
>>
>> - meta-cloud-services/meta-openstack
>> - meta-cloud-services/meta-openstack-compute-deploy
>> - meta-cloud-services/meta-openstack-controller-deploy
>> - meta-cloud-services/meta-openstack-qemu
>> - meta-cloud-services/meta-openstack-compute-test-config
>> - meta-cloud-services/meta-openstack-controller-test-config
>>
>> so the question is, is this actually usable to bitbake openstack based images ? or a Work in progress ?
>>
> They are now a work in progress. They *worked*, but we didn't have a
> dedicated maintainer, so we make sure the re-usable recipes work (and
> a few have migrated to the main meta-virt over time), but to build and
> deploy working controller and compute nodes, they wouldn't be usable
> out of the box.
>
> Bruce
So they need updating, maintaining, i see alot of python2 and python3
mixed in here.
guess they would have to be gone through one by one to get it back to
functional.
Ill take a look.
>
>>
>>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2458 bytes --]
prev parent reply other threads:[~2020-10-27 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 9:16 is meta-cloud-services/meta-openstack useable, or a WIP ? Yocto
2020-10-27 9:30 ` [meta-virtualization] " Paul Barker
2020-10-27 10:04 ` Yocto
2020-10-27 12:05 ` Bruce Ashfield
2020-10-27 12:27 ` Dingo
[not found] ` <1641D1540454F162.12047@lists.yoctoproject.org>
2020-10-27 10:29 ` Yocto
2020-10-27 12:07 ` Bruce Ashfield
2020-10-27 12:28 ` Dingo [this message]
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=f0be59b1-3e21-8520-ecc4-934d0a84df38@optimcloud.com \
--to=dingo@optimcloud.com \
--cc=meta-virtualization@lists.yoctoproject.org \
/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.