configure exchange and ping URLs from EC2 user data
Bug #343947 reported by
Christopher Armstrong
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: landscape-client
When the client is starting up in cloud mode, it should fetch the exchange and ping URLs to use from the EC2 user data. This would allow alternative deployments of the Landscape service to specify the URLs to which the client should connect.
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package landscape-client - 1.0.28-
---------------
landscape-client (1.0.28-
* Fix minor packaging issues in last release (LP: #343954)
- Version number in landscape.VERSION is now correct
- Fixed package version number to maintain convention
* The following changes are in the 1.0.28 release:
- Invalidate package cache when server UUID changes (LP: #339948)
- Improve the "cloud mode" introduced in 1.0.26 to send more
disambigu
the exchange and ping URLs (LP: #343947)
- Allow importing of initial configurations (along with public SSL
certificates) when running landscape-config (LP: #341705)
- Support a non-root mode which allows running the client without the
management functionality (LP: #82159)
- Automatic cloud registration when there's no user-data to specify an OTP
now works (LP: #344323)
-- Christopher Armstrong <email address hidden> Thu, 19 Mar 2009 09:52:03 -0400