39 lines
908 B
Markdown
39 lines
908 B
Markdown
title: How to build an OpenStack alternative: Step 4, the metadata service
|
|
---
|
|
pub_date: 2020-01-14
|
|
---
|
|
author: ungleich virtualisation team
|
|
---
|
|
twitter_handle: ungleich
|
|
---
|
|
_hidden: yes
|
|
---
|
|
_discoverable: yes
|
|
---
|
|
abstract:
|
|
Passing meta information into the VM
|
|
---
|
|
body:
|
|
|
|
This time we describe how to pass information to the virtual machines
|
|
in uncloud.
|
|
|
|
The previous time we described
|
|
[how to generate MAC
|
|
addresses(../how-to-build-an-openstack-alternative-step-3-automating-mac-addresses/),
|
|
a key element of uncloud.
|
|
|
|
## Metadata
|
|
|
|
|
|
|
|
## Status
|
|
|
|
While being a small and very specific tool, the mac address generator
|
|
is actually a key element of creating a virtualisation
|
|
framework. Without it, it is practically impossible to spawn a dynamic
|
|
amount of virtual machines.
|
|
|
|
With our prototype, a secured network and the mac address generator we
|
|
are not far from being able to migrate some test VMs to uncloud.!
|