lp:~rackspace-titan/nova/fix_osapi_use_ipv6_flag_error
- Get this branch:
- bzr branch lp:~rackspace-titan/nova/fix_osapi_use_ipv6_flag_error
Branch merges
- OpenStack release team: Pending requested
-
Diff: 22 lines (+2/-2)2 files modifiednova/flags.py (+2/-0)
nova/network/manager.py (+0/-2)
- Brian Lamar (community): Approve
- Brian Waldon (community): Approve
-
Diff: 22 lines (+2/-2)2 files modifiednova/flags.py (+2/-0)
nova/network/manager.py (+0/-2)
Related bugs
Bug #832012: OSAPI list servers causes 'AttributeError: use_ipv6' | Medium | Fix Released |
Related blueprints
Branch information
Recent revisions
- 1480. By Dan Prince
-
Move use_ipv6 into flags. Its used in multiple places (network manager and the OSAPI) and should be defined at the top level.
- 1478. By Vish Ishaya
-
This branch does the final tear out of AuthManager from the main code. The NoAuth middlewares (active by default) allow a user to specify any user and project id through headers (os_api) or access key (ec2_api).
The plan is to leave the auth manager code in but mention that it is deprecated. There is a sample paste config in ini to still allow old auth. Immediately after the diablo release we can tear out all of the Auth related code and not support the deprecated auth anymore.
- 1477. By Christopher MacGown <email address hidden>
-
Implements first-pass of config-drive that adds a vfat format drive to a vm when config_drive is True (or an image id).
- 1476. By Tushar Patil
-
Our goal is to add optional parameter to the Create server OS 1.0 and 1.1 API to achieve following objectives:-
1) Specify number and order of networks to the create server API.
In the current implementation every instance you launch for a project having 3 networks assigned to it will always have 3 vnics. In this case it is not possible to have one instance with 2 vnics ,another with 1 vnic and so on. This is not flexible enough and the network resources are not used effectively.
2) Specify fixed IP address to the vnic at the boot time. When you launch a server, you can specify the fixed IP address you want to be assigned to the vnic from a particular network. If this fixed IP address is already in use, it will give exception.
Example of Server Create API request XML:
<?xml version="1.0" encoding="UTF-8"?><server xmlns="http://
docs.nttpflab. com/servers/ api/v1. 0"
name=" new-server- test" imageId="1" flavorId="1">
<metadata>
<meta key="My Server Name">Apache1</meta>
</metadata>
<personality>
<file path="/etc/banner. txt">
ICAgICAgDQoiQS BjbG91ZCBkb2VzI G5vdCBrbm93IHdo eSBp
</file>
</personality>
<networks>
<network uuid="6622436e-5289-460f- 8479-e4dcc63f16 c5" fixed_ip= "10.0.0. 3">
<network uuid="d97efefc-e071-4174- b6dd-b33af0a377 06" fixed_ip= "10.0.1. 3">
</networks>
</server>3) Networks is an optional parameter, so if you don't provide any networks to the server Create API, it will behave exactly the same as of today.
This feature is supported to all of the network models.
- 1475. By Alex Meade
-
Fixes bug 831627 where nova-manage does not exit when given a non-existent network address
- 1473. By Alex Meade
-
The FixedIpCommands
TestCase in test_nova_manage previously accessed the database. This branch stubs out the database for these tests, lowering their run time from 104 secs -> .02 secs total. I have verified the tested functionality is still being tested.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~hudson-openstack/nova/trunk