[05:21] <firstofth300> rharper: The problem I'm facing is that I don't necessarily know any of the information ahead of time. It's all queried at runtime through the DigitalOcean data source. One of the pieces is the presence of an anchor IP which is only provided via the metadata server which I potentially could be using for floating IPs. If I could just configure the
[05:21] <firstofth300> VPC with proper routes, I would. I really wish that cloud-init would provide an option to append routes as that seems like it is a potentially more common use case for the smaller independent clouds like DO and Linode.
[05:22] <firstofth300> It would make things more portable in case I need to use a combination of CentOS/Debian/Ubuntu, etc.
[05:26] <firstofth300> I suppose since I'm using a combination of Saltstack and cloud-init that I can just runcmd this and then use a salt state to add the routes itself.
=== andrewbogott is now known as Guest7322
=== Guest7322 is now known as andrewbogott
=== esv_ is now known as esv
[17:30] <rharper> firstofth300: yeah, the challenge as you mentioned, is knowing certain info ahead of time; that's what the platform tells cloud-init;   If there is additional metadata from DO about the route you need to configure, then the DO datasource could be updated to include that route when it renders networking.  
[18:08] <firstofth300> Yeah, I suppose there could be some sort of metadata set ahead of time that specifies routes to add.
[18:08] <firstofth300> I solved the problem using runcmd and Saltstack though which I'm happy enough with.
[18:09] <firstofth300> runcmd to configure the networking to be able to reach the Salt master and salt to actually render the routes.