I think the actual question is how to create a service that responds to metadata requests. In that case, it is a bit hard to say from the outside, because it is very dependent on what software-defined-networking you're using.
169.254.169.254 is a link-local address, which means it can't be routed across the network. So you have to have your SDN know where to send your packets (it effectively looks like the switch is the thing running the metadata server, because that's the only thing on the other side of a link-local connection). I don't have any specific information about how it is done on the various clouds. Though you could look at openstack which also implements a metadata-server and is open source code. John =:-> On Wed, Apr 11, 2018 at 7:58 PM, Heather Lanigan < heather.lani...@canonical.com> wrote: > Hi Drew, > > Juju uses cloud-init currently when provisioning machines today. We've > recently added a bootstrap configuration option to allow for cloud-init > yaml to > be passed through. > > Details can be found in an old bug: https://bugs.launchpad. > net/juju/+bug/1535891 > > I need to get this added to the docs. There is a known issue using lists > in the yaml file, but strings work fine. > > -Heather > > On Wed, Mar 28, 2018 at 4:16 PM, Drew Wells <drew.well...@gmail.com> > wrote: > >> I want to implement an aws user-data like interface. So the Ubuntu host >> would respond on 169.254.169.254 and this address would be routable by >> every juju managed machine and the containers running on those machines. >> >> Where would I get started for setting something like this up? >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/juju >> >> > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju