| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: Icf3c3b623297afc267c27427fb964a5876915c65
|
| |
|
|
| |
Change-Id: I5e413e133281a7753b2acc67819af9a2d47537ff
|
| |
|
|
| |
Change-Id: I32298ed75f4106dab6c8b8df760811b7dd0b4245
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
7627e1bae53747e1471caf632dfc1b6edf2e26cf introduced new code to add the
environment to the files mapping, so server side resolution of multiple
environments is possible.
However, the environment added is wrong when you're handling those with
relative paths inside, we must add the resolved version or the keys
don't map to keys in the files map, an you get an error when we try
to locate the file on the server.
Evidently we lack adequate functional test coverage of this, which can
be addressed via a heat patch, but I added a unit test illustrating
the problem.
Change-Id: I3bd2cd48623e4ad1b4067f4cefc7ddff30b9e88d
Closes-Bug: #1560106
|
| |
|
|
| |
Change-Id: I9dd80f7a53bf6644030caba95f86ff1aaf2618fd
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a --follow option which is similar to the --wait logging
behaviour in changes like I72421c1adf9220e3440179fec672f49803a6cde2
except that --follow doesn't exit until the user does ctrl-c.
This change also includes:
- always sort events ascending for all formatters - the newest events
should always be at the bottom of the screen as they are generally the
most interesting
- get_event marker handling tolerates the marker not being in the event
list. --follow was triggering this, but ignoring the marker in this
case has not lead to events being printed more than once
Change-Id: Ie0964918fc1d05e7e18aa39ceea6d4777deeb87e
Blueprint: heat-support-python-openstackclient
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change implements the "openstack orchestration service list" command
Based on the existing heat command: heat service-list
Change-Id: I9ded1f344dabbb8579005923d68d3ebb4f296ed5
Blueprint: heat-support-python-openstackclient
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
Change-Id: Ie918e095e7d67c94991f1a7e4b0ede9127134936
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change implements the "openstack stack resource mark unhealthy" command
Based on the existing heat command: heat resource-mark-unhealthy
Change-Id: I8b4735085e1656f991b648d094f690b8d7df451d
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This change implements the "openstack orchestration build info" command
Based on the existing heat command: heat build-info
Change-Id: I8801d56fbe8119c47f708e620f35215c8664cda7
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case the template has any whitespace
we should strip it before checking if the
first character is a "{" to determine that its
a json template
Change-Id: Ia25444a2fde7019aa9fdf0d782599be78305ae9c
Closes-Bug: #1546166
|
| |\ \ \
| |/ /
|/| | |
|
| | |/
| |
| |
| |
| |
| |
| |
| | |
Replace assertEqual(None, *) with assertIsNone in tests to have
more clear messages in case of failure.
Change-Id: I9a30b67f0329280e06e746af9b82b448552a2a52
Closes-bug: #1280522
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
Change-Id: I4965bf4c24bbc9911837d8578d852b324f7645f7
Closes-bug: #1494058
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Added a few more basic tests
Blueprint: heat-support-python-openstackclient
Change-Id: Ifbc97d849c23cd622b62b52b84d8634b8c8658db
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
OpenstackClient has a consistent pattern for the metavars on their
arguments. Heatclient's plugin should follow that pattern.
Blueprint: heat-support-python-openstackclient
Change-Id: Ie2fdb2a985c4c41235916f0745138ea9c812b4ac
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add a new command to set resource's health.
The command takes the following format:
heat resource-mark-unhealthy [--reset]
<NAME or ID> <RESOURCE>
reason
Change-Id: I4e0a127343e591c176f451172a1c8a59bf36f6eb
Partially-implements: blueprint mark-unhealthy
Depends-On: Ifa48b179723a2100fff548467db9e162bc669d13
|
| | |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
These are treated like the poll_for_events for stack update, except for
the cancel action which stops polling on any COMPLETE or FAILED state.
Change-Id: I3723bde4f26abb12674d15df65764fb6d8a67a56
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Change-Id: I2fe9fd46846393dca7958cf0793ecb1d93e5b841
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This differs from "stack create" in that an event marker needs to be
discoverd first, and the stack name needs to be fetched from a stack get
rather than arguments.
Change-Id: Ibb1a7d19a8319ee6d7c99d25ddd0dbc061485a15
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will print progress to the user, and event polling should be less
resource instensive on the heat service than stack polling.
Change-Id: I72421c1adf9220e3440179fec672f49803a6cde2
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This checks the stack status with a stack get if there have been two
event polls which return no events. This handles the cases where an
event may have been lost, or older heat versions which didn't generate
"resource" events for stack state changes.
Change-Id: I0db71aecbd828c9b7dba0df8e548ba48f83436c2
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Adds support in template_utils to optionally produce an ordered list of
environment file names and include the environment file contents in the
files dict. This will be passed to the server to trigger the server-side
handling of resolving overrides for multiple environments.
The original behavior of merging the environments client-side is left in
for backward compatibility purposes. Both are sent to the server. For
mitaka and newer, the client-submitted environment is ignored and the
merging is done server-side. For liberty and older, the
environment_files list is ignored entirely and the passed in environment
is used.
Note that the merging, regardless if it is done client or server-side,
is handled by the same code; it has not been copied or duplicated in the
server.
Change-Id: If187c8ca3d80008c21e8f6066d335ab0c30315e6
Implements: blueprint multi-environments
Depends-On: Ibe46fd35de7988920c101a83259c06c8f8a3ed0b
|
| |\ \ \ \ \ |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
yaml.load() provides the ability to construct an arbitrary python object
that may be dangerous. yaml.safe_load() limits this ability to simple
python objects like integers or lists.
ref: https://en.wikipedia.org/wiki/YAML#Security
Change-Id: Ic8313b4042aad1e077ba1fbb68979f8745adfe3d
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
"openstack update" collides/hides with "openstack update cancel"
I discussed a few possible solutions in the bug report.
Will change to have a new "openstack stack cancel" command
and it will cancel the pending action, for now just supporting
update.
Blueprint: heat-support-python-openstackclient
Change-Id: I7e054ecffea5b03a815f69515651e9c377ff68c2
Closes-Bug: #1545131
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Currently only used by "heat stack-create --poll", moving this function
will allow all new openstack client commands to use for their --wait
implementation.
This change also adds unit tests for this function.
Change-Id: I642797b08cd13c0c50169071d998cf5ba8b397a3
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Ignore restricted_actions key in resolve_environment_urls.
Change-Id: Ia29441751be7a7f0752ce73c71d34e34b62c9d5a
Blueprint: stack-update-restrict
|
| |\ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Refactor existing hook helper fuctions into utilites.
based upon heat clis:
heat hook-poll
hest hook-clear
Change-Id: Ib46634cc62369fb5932dcd0967ae492446c79a88
Blueprint: heat-support-python-openstackclient
|
| |\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change implements the "openstack software deployment output show" command
Based from the existing heat command:
heat deployment-output-show
Change-Id: Ide607c925a15071c0c02c8cdb1ba20d9a745f9a9
Blueprint: heat-support-python-openstackclient
|