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

2015-12-01 Thread 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


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

2015-12-01 Thread Kai Qiang Wu
Hi HouMing,

I checked the heat templates again, and check with heat developers.
For heat stack creation now, it can not directly use existed network when
create new stack. which means, it need create a new net and subnet.
So for fixed_network, the name is still need. just like when you create
network in neutron, you need network and subnet.

I think right now, so for magnum point of view what can be controlled is,
1. network name related properties settting.  2. subnetwork related
properties. like CIDR.


So for fixed_network, give it still what role should be.

Add a new fixed_subnet for that.


Of course, this can also be discussed in weekly meeting if needed.


Thanks

Best Wishes,

Kai Qiang Wu (吴开强  Kennan)
IBM China System and Technology Lab, Beijing

E-mail: wk...@cn.ibm.com
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
 No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China
100193

Follow your heart. You are miracle!



From:   Hou Ming Wang <houming.wang...@gmail.com>
To: openstack-dev@lists.openstack.org
Date:   01/12/2015 05:49 pm
Subject:    [openstack-dev] [Magnum] 'fixed_network' actually means
    'fixed_subnet'. Which way is better to fix this?



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


__
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