Investigate and implement landscape-client support to expose Azure cloud instance metadata
Bug #1236559 reported by
Chad Smith
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
For Azure vm instances, we need to ensure landscape-client provides at cloud instance metadata on par with what we get for EC2 and Openstack instances. For azure we are looking for cloud metadata properties along the lines of: instance-type, instance-id and ami-id or whatever Azure exposes.
If there is an EC2-compatible api local to the instance, let's use that as we already have support for that in the client.
| tags: | removed: kanban |
| Changed in landscape-client: | |
| milestone: | 13.10 → 13.11 |
| Changed in landscape-client: | |
| milestone: | 13.11 → 13.12 |
| Changed in landscape-client: | |
| milestone: | 13.12 → 14.01 |
| Changed in landscape-client: | |
| milestone: | 14.01 → 14.02 |
| Changed in landscape-client: | |
| milestone: | 14.02 → 14.03 |
| Changed in landscape-client: | |
| milestone: | 14.03 → 14.04 |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Invalid |
To post a comment you must log in.
This bug has not seen any activity in the last 6 months, so it is being automatically closed.
If you are still experiencing this issue, please feel free to re-open.
Landscape Team