+1 great addition to the team
From: Hongbin Lu
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, 22 July 2016 at 21:27
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum
The discussion at the summit was very positive around this requirement but as
this change will make a large impact to Magnum it will need a spec.
On the API of things, I was thinking a slightly more generic approach to
incorporate other lifecycle operations into the same API.
Eg:
magnum bay-mana
I’m in broad agreement with Hongbin. Having tried a patch to use jinja2 in the
templates, it certainly adds complexity. I am in favor of using conditionals
and consuming the latest version of heat. If we intend to support older
versions of OpenStack this should be a clearly defined goal and need
The canonical place for the help/documentation must be the online
documentation. We must provide information in the docs first, additional
content should be added to the CLI help. The labels field contains arbitrary
metadata which can be consumed and used by the COE/bay, it has no set structure
Thanks for the write up Hongbin and thanks to all those who contributed to the
design summit. A few comments on the summaries below.
6. Ironic Integration:
https://etherpad.openstack.org/p/newton-magnum-ironic-integration
- Start the implementation immediately
- Prefer quick work-around for iden
+1
From: Hongbin Lu
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, 31 March 2016 at 19:18
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer
team
Hi all,
One of the main reasons for moving to a "bay driver” model was to allow us to
focus our efforts. We talked about focusing our support to the distros with a
religion around them, e.g. Ubuntu and a Red Hat derivative.
Being frank, I do not see much benefit in supporting a small distro if we have
sup
+1+1
Well deserved!
On 01/02/2016, 15:58, "Adrian Otto" wrote:
>Magnum Core Team,
>
>I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core Reviewers.
>Please respond with your votes.
>
>Thanks,
>
>Adrian Otto
>_
gt;[1]
>http://docs.openstack.org/developer/nova/api_microversions.html#removing-a
>n-api-method
>
>Best regards,
>Hongbin
>
>-Original Message-
>From: Cammann, Tom [mailto:tom.camm...@hpe.com]
>Sent: December-16-15 8:21 AM
>To: OpenStack Development Mailing List (no
I have been noticing a fair amount of redundant work going on in magnum,
python-magnumclient and magnum-ui with regards to APIs we have been intending
to drop support for. During the Tokyo summit it was decided that we should
support for only COE APIs that all COEs can support which means droppi
10 matches
Mail list logo
