Created by Ben McGraw and last modified
Get this branch:
bzr branch lp:~mcgrue/nova/volume-cleanup
Only Ben McGraw can upload to this branch. If you are Ben McGraw please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Ben McGraw
OpenStack Compute (nova)

Recent revisions

1484. By Ben McGraw

resolving conflicts.

1483. By Vish Ishaya

Adds a use_deprecated_auth flag to make sure creds generated using nova-manage commands will work with noauth.

1482. By Nachi Ueno

I added notifications decorator for each API call using monkey_patching.
By this merge, users can get API call notification from any modules.

1481. By Brian Waldon

Fixes bug that causes 400 status code when an instance wasn't attached to a network.

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.

1479. By Thierry Carrez

Refresh translations

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">
    <meta key="My Server Name">Apache1</meta>
    <file path="/etc/banner.txt">
      <network uuid="6622436e-5289-460f-8479-e4dcc63f16c5" fixed_ip="">
      <network uuid="d97efefc-e071-4174-b6dd-b33af0a37706" fixed_ip="">

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

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.