Re: [openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

[Hou Ming Wang]

Adrian,
If need more than one alternates, I would like to be that.

Thanks & Best Regards
Hou Ming Wang

On Wed, Dec 2, 2015 at 2:32 PM, 王华 <wanghua.hum...@gmail.com> wrote:

> Adrian,
> I would like to be an alternate.
>
> Regards
> Wanghua
>
>
> On Wed, Dec 2, 2015 at 10:19 AM, Adrian Otto <adrian.o...@rackspace.com>
> wrote:
>
>> Everett,
>>
>> Thanks for reaching out. Eli is a good choice for this role. We should
>> also identify an alternate as well.
>>
>> Adrian
>>
>> --
>> Adrian
>>
>> > On Dec 1, 2015, at 6:15 PM, Qiao,Liyong <liyong.q...@intel.com> wrote:
>> >
>> > hi Everett
>> > I'd like to take it.
>> >
>> > thanks
>> > Eli.
>> >
>> >> On 2015年12月02日 05:18, Everett Toews wrote:
>> >> Hello Magnumites,
>> >>
>> >> The API Working Group [1] is looking for a Cross-Project Liaison [2]
>> from the Magnum project.
>> >>
>> >> What does such a role entail?
>> >>
>> >> The API Working Group seeks API subject matter experts for each
>> project to communicate plans for API updates, review API guidelines with
>> their project’s view in mind, and review the API Working Group guidelines
>> as they are drafted. The Cross-Project Liaison (CPL) should be familiar
>> with the project’s REST API design and future planning for changes to it.
>> >>
>> >> Please let us know if you're interested and we'll bring you on board!
>> >>
>> >> Cheers,
>> >> Everett
>> >>
>> >> [1] http://specs.openstack.org/openstack/api-wg/
>> >> [2] http://specs.openstack.org/openstack/api-wg/liaisons.html
>> >>
>> >>
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> > --
>> > BR, Eli(Li Yong)Qiao
>> >
>> > 
>> >
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Magnum] 'fixed_network' actually means 'fixed_subnet'. Which way is better to fix this?

[Hou Ming Wang]

Hi All,
I'm working on API related enhancement and encountered  the following issue:
bay-creation return 400 Bad Request with a valid fixed-network in baymodel(
https://bugs.launchpad.net/magnum/+bug/1519748 )

The 'fixed_network' actually means 'fixed_network_cidr', or more precisely
'fixed_subnet'. There're 2 possible ways to fix this:

1. Rename the 'fixed_network' to 'fixed_subnet', in Baymodel DB, Baymodel
Object and MagnumClient.

2. Leave 'fixed_network' alone, add a new field 'fixed_subnet' to Baymodel,
and use the 'fixed_subnet' to take the place of current 'fixed_network'.


Please don't hesitate to give some inputs of which one is better, by
comment in the bug or reply this mail.


Thanks & Best regards,

HouMing Wang
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev