ok this is strange

gmake world keeps failing when trying to update the javascriptlint module for ur-agent

specifically it's timing out connecting to github

for _just_ that repo

and it's been doing it for > 24 hours now

Wow, I see jperkin also put the tailscale and wireguard packages into the tools package lists. Nice!

yeh I figured they would be useful in the GZ

definitely

ooh, and I see bootstrap tarballs...

I'll try to find some time to test those in the next day or two.

Hey all, does anyone here know if Triton Cloudapi provides functionality to pass a cloud config json string to cloud-init? Can I pass a cloud-config(mainly network config) in json to cloud-init in a way similar to the customer_metadata property in a SmartOS json VM file which gets imported by vmadm?

I would like to provide cloud-init with this kind of information: pastebin.com/JMVZu5zd

TheTim0Nat0r: Yes, you can. Specify it as the user-script.

For Linux OS instances, if the user-script is a cloud-init script it will be passed verbatim to cloud-init. If it's anything else, it'll be executed with bash during boot.

I don't think that'll override the network settings.

Or at least, doing what the API isn't doing won't end well.

Yeah, the network settings are controlled by the hypervisor. Adding incompatible networking directives to the cloud-config will render the instance unreachable.

TheTim0Nat0r: What is it about the network config you want to change?

bahamat: I would like to bypass the incapability of Triton SDC to provision VMs and containers with ipv6 addresses and routing by communicating directly with cloud/init

I need to be able to provide each cm and container with a static ipv6 address and gateway through an api

Well that's not going to work for you right off.

SmartOS has protections in it to prevent instances from using IPs other than the ones they're directly assigned.

But, I do have this: github.com/TritonDataCenter/triton-cloudapi-plugins

One of the plugins in that repo will allow certain trusted users to automatically enable allow_ip_spoofing, which will let you bring up v6 addresses in the guest.

Okay, so if I understand well, I can not use the current apis to pass a config string to cloud/init on creatiOn of a vm to have cloud/init configure a static ipv6 address and gateway in that vm

Not alone, no.

Instances need to allow_ip_spoofing to be able to do that.

TheTim0Nat0r: Sounds like you're using Triton on-prem? It might be good to get in touch with us.

TheTim0Nat0r: slaac doesn't work ?

Even with slaac you need to allow_ip_spoofing

I mean the question is kind of if just using slaac (which does give a predicable ipv6 at least) would be enough. that only needs allow_ip_spoofing for bhyve/kvm guests

(and yes, it would be nice if it didn't)