part 1 of blueprint separate-nova-metadata
* adds api/metadata/ and moves code from ec2
* moves metadata into separate binary
* changes metadata forward to use metadata host and port
* moves the metadata accept rule to the metadata api
* adds nova-api-* to setup.py
Change-Id: I7f5d8e6cafc55b5c383cd88991f29c6059fb8d82
This indicates the failure to the user through the exit status.
Original author: Renuka Apte <renuka.apte@citrix.com>
Change-Id: I73fc2cc35530e7ee7f113f5aaec7b577663e4dc1
This introduces a new flag "quantum_use_dhcp=<boolean>" which indicates whether
or not to enable dhcp for all of the networks. If it is set then we start
dnsmasq (and provide it with the IP/MACs from Melange) similar to how this was
done in linux_net before.
Prior to this if you enabled dhcp then you would also get a gateway device..
some people may not want that so we now require that you specify the gateway
when creating the network in order to end up with a device that will act as a
gateway. If you're using Melange IPAM and you don't specify the gateway you
still end up with one because it doesn't allow you to not have one. This lays
the groundwork for the option of not having one in the future, at least :)
Also, fix quantum/melange ipam interaction
We now query for the subnets by net_id/vif_id instead of searching through all
the blocks to find the right one. Both of the allocate and deallocate for
instance calls are now using the vif_id -> network_id mapping instead of
searching the quantum networks. get_port_by_attachment was also changed to
take a net_id so that we don't have to search through all of the quantum
networks to find the corresponding port.
Change-Id: I6a84da35237b6c5f5cdee91ada92642103439a97
With melange it will be possible to have overlapping cidrs so it would be
better to specify the uuid of the network to delete.
Change-Id: I6781225d587952cbab3387cd40164d8ac77c58d6
Add in a log report to nova-manage
Usages:
Get the last errors in the nova logs
nova-manage logs errors
Get the last x nova messages in the syslog. The default is 10
nova-manage logs syslog <x>
Change-Id: Id5d3a546051e25175b6523711f437618d07c3f19
nova-ajax-console-proxy is overriding the logging configuration carefully
set up by nova.log. There's no reason for it to do this, and it's the only
script in nova/bin that does. I've removed that code.
Change-Id: I5b2d5026d529a20d26ba3bb721b15f235f6fdda8
Add a handler for URLError, so that we print a nicer error message if stack
cannot connect to the server.
Change-Id: I24f977dcb12bee3bb21057fe9b19823d98581141
With this modification both nova-manage and scheduler use the flag
service_down_time and check positive and negative values in a
correct way.
Fixes bug: 867674.
Change-Id: I15c48d80cafa2089cd228c09c61b0a1e513730e8
Adds in bandwidth, state and IP data on standard notifications,
and new notifications on add/remove IP.
These were missing before, and are needed to meet spec.
This fixes bug 849117
Change-Id: Ie586ff3a91a56e5f5eff8abc6905ba6a0b624451
* Removes Ata Over Ethernet
* Adds drivers to libvirt for volumes
* Adds initialize_connection and terminate_connection to volume api
* Passes connection info back through volume api
Change-Id: I1b1626f40bebe8466ab410fb174683293c7c474f
Vishvananda Ishaya