New oslo config patch causes services to fail to launch, with
"ImportError: No module named oslo.config", bumping to
oslo-config-2013.1b4.tar appears to fix the problem
fixes bug 1131135
Change-Id: I460564be19fc97bd54bb59c759c1148e7ead774b
This is so you can make a custom loadbalancer that can reference the
group's instance ip's.
fixes bug #1131025
Change-Id: I32d76d3627704ad503e2ec06bf0da39cf79f33d2
We need to update the stack dependencies each time we modify the
resources list, otherwise in the event of a failure, the resources
returned from the iterator methods don't match with those found via
getitem/contains (which is important for rollback)
blueprint update-rollback
Change-Id: Ia47f84291f50c33fc052b7b33fa0c1f9e8430ab4
When doing an update, we want to fail immediately, instead of
collecting the resource update errors and continuing. This is
particularly important for update rollback, where we want to
declare failure ASAP to simplify and speed up the rollback
blueprint update-rollback
Change-Id: I56133254036d8aac592dcf3cda2ca7928cc02fa9
Boto does not, by default, validate https ceritificates on endpoints. We
now provide a way to specify it in the heat configuration along side
is_secure. Heat deployers may also need to turn this off if boto ever
does make it default and they want to use self signed certs.
Fixes bug #1130345
Change-Id: I09b684dd28a8a57c6ce514d1df1e699e7c8b182e
Avoid the possibility of returning an empty string (when Exceptions
have not got a string message), or parser.py will treat the error
as success and the resource operation failure will not be correctly
reflected in the resource state.
fixes bug 1130270
Change-Id: I1c55dea1f9615cd4b037802ff8c1066694bffea6
Implement stack rollback for create_stack, so if a stack
creation fails we automatically rollback (ie delete) the
stack
NOTE : this option defaults to on, so use the --disable-rollback
option to the CLI tools if you want to disable this feature
blueprint stack-rollback
Change-Id: I70a3822426706d0787e571517e059baff1406c0f
Only create the stack periodic watcher task if the stack create
completed successfully, since we don't want a watcher task if
the stack ended up rolling back (or just in CREATE_FAILED state)
Change-Id: I5592fa106f740eb2e1dcf40e98a2656627715b6f
Make the stack_delete_after decorator try/except so it doesn't cause a
test failure if the test has already done a delete during the test
Change-Id: I4a5e096478ece0de02cc910366a5d361d5ee45e0
When rollback is implemented it will default on, like aws
so this option allows stack rollback on create to be disabled
blueprint stack-rollback
Change-Id: I02fcaaa656219b1c65729cecdd473e0a5bd86036
The tests which store a stack in the DB should delete it
at the end of the test, otherwise any cut/paste test
which uses the same stack name will always fail
Change-Id: Ib2e26480924bfe65a2f6fe8ae55076466394bcee
Previously we ignored DisableRollback for create/update,
pass it to the engine since the engine API now supports it
blueprint stack-rollback
Change-Id: I926d843a88449fa61b665bd1b47946724f6d2ce5
Allow API's to pass string or bool format True/False flag
for the disable_rollback argument to the engine RPC API
Change-Id: I1886263ac2487c4cb36c8bd93fd1d09b04abe813
I ran into a bug which caused a bt when the flavor is missing on the
targetted system. This patch makes it throw a proper exception and a
useful error message.
Fixes: bug #1129388
Change-Id: I545fce32732522053e2a4a113a02883a89045910
Signed-off-by: Ian Main <imain@redhat.com>
Looks for the AvailabilityZone property in the instance's
resource section. For example:
"Resources" : {
"Properties": {
"AvailabilityZone" : "nova",
...
Fixes bug #1096006
Change-Id: I3333b5f909b27e53f6985713de58dd30efc1a80a
Signed-off-by: Jeff Peeler <jpeeler@redhat.com>
The cfg API is now available via the oslo-config library, so switch to
it and remove the copied-and-pasted version.
Add the 2013.1b3 tarball to tools/pip-requires - this will be changed
to 'oslo-config>=2013.1' when oslo-config is published to pypi. This
will happen in time for grizzly final.
Add dependency_links to setup.py so that oslo-config can be installed
from the tarball URL specified in pip-requires.
Remove the 'deps = pep8==1.3.4' from tox.ini as it means all the other
deps get installed with easy_install which can't install oslo-config
from the URL.
Excluded code from oslo-incubator in the pep8 check.
Retain dummy cfg.py file until keystoneclient middleware has been
updated (I18c450174277c8e2d15ed93879da6cd92074c27a).
Change-Id: I4815aeb8a9341a31a250e920157f15ee15cfc5bc
Adds support for a disable_rollback parameter to the engine API
which will allow us to control rollback of create/update
blueprint stack-rollback
Change-Id: I832f26c917d8fc178b925ce49a2366faf6e3dc0e
Signed-off-by: Steven Hardy <shardy@redhat.com>
Please note that this takes a different approach for
all VPC resources types. Previously the resource_id matched
the underlying quantum resource UUID (or a composite of the
underlying UUIDs)
This had some problems, including:
- it was resource_id abuse
- it required extra quantum _list and _show calls to get enough
data to wire up new resources
- it made the already difficult job of mapping VPC <-> quantum
even harder
The new approach is to store all quantum UUIDs in resource metadata.
The resource id is just the resource name, so resources can easily
fetch other resources from the stack by ref/name then look up
their metadata to find the underlying quantum UUIDs to perform
operations with.
Implements blueprint resource-type-internetgateway
Change-Id: I69937254566b74f173439b3c5ce4c4e8d8c49afa
When the User resource doesn't have the `Policies` property specified,
the policy checking code raised an error because it tried to iterate
over `None`.
Change-Id: I1ad0a051c837744d8ec0a343929918c92fa78437
Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
