Accessing the metadata API?
andres.rodriguez at canonical.com
Fri Feb 3 14:06:50 UTC 2017
On Wed, Feb 1, 2017 at 4:47 PM, Jim Tilander <jim at tilander.org> wrote:
> * Is there a stable API endpoint that one can call during deployment
> If you are trying to get status of the machine, you could use the machines
> endpoint to see its status, or the events endpoint to show the events for
> the specific machine. Is there any specific information you are looking
What’s the URL for the machines that I would use? Wouldn’t I need my own ID
> for that?
Yes you would need to be logged in into the API.
> All I wanted to do was to reliably lookup my own FQDN, as well optionally
> get some custom payload for each node into a script that runs during setup.
I would need more context than that, but you could get the FQDN of a
deploying machine in the preseeds context (i.e. node.fqdn()). That said,
you could also do post_install configuration via preseeds.
You could inject user_data on the deployment (if doing so via the API of
> * Can one call the metadata API post deployment?
>> * How are the nodes supposed to authenticate? I keep getting Forbidden
> This may be an indication of mis-configuration. Please make sure that
> /etc/maas/rackd.conf points to an IP the machines you are
> commissioning/deploying can access to, and in port 5240. (e.g. maas_url:
> I’m fairly certain that it works, as when I mess up that URL, the boot
> process stops much earlier than my curtin scripts fire. (I tried to use
> https, which didn’t work, but it did prove that the setting is used during
> the boot process).
Engineering Manager, MAAS
Canonical USA, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Maas-devel