Thanks again for all of the help, Waldek!  I've been sidetracked but am 
finally getting back around to this.  :)

On Tuesday, January 8, 2019 at 7:47:42 AM UTC-5, Waldek Kozaczuk wrote:
>
> I think you should be using HVM-based instance types, so I think you are 
> fine. I know there are certain new EC2 instance types announced in 2017 
> that are KVM based and use ENA and NVMe drivers which OSv does not support. 
> Please see this - https://github.com/cloudius-systems/osv/issues/924.  
>

Yeah, it looks like networking is working.

 

> I have a modern version of this script and others. So if you care I can 
>> dig it up. 
>>
>
I've managed to cobble something together with the AWS API directly, so 
hopefully I'm good there :)


Additionally I am not sure you are familiar with capstan tool that can 
> build OSv images Docker compose style - 
> https://github.com/cloudius-systems/osv/wiki/Build-and-run-apps-on-OSv-using-Capstan.
>  
> You need new mikelangelo capstan - 
> https://github.com/mikelangelo-project/capstan 
>

I've seen it but haven't messed with it yet.  Maybe that's the way I need 
to go, I'll have to throw together a container and see how it works.


Is it OSv cloud-init module that fails to get metadata (
> https://github.com/cloudius-systems/osv/blob/master/modules/cloud-init/data-source.cc)
>  
> or your app? I wonder if your problems are Golang specific.
>

Neither sees any init data, both elements report that the internal AWS IP 
that contains host metadata is unreachable.

 

> I might have some time this week to create an EC2 instance and try a 
> Golang app myself. Which instance type are you using - 
> https://aws.amazon.com/ec2/instance-types/?
>

I was trying with t2.micro, which I thought was the most basic and generic 
instance I could get.  Is there a better option?

Thanks again for all of your help!  :)

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to