Thanks for the reply, Waldek!
For my use case, I do need to be able to provide application configuration
via cloud-init, operating system configuration isn't necessarily required
(as long as it can pick up all of the settings it needs while booting on
EC2). When I put the build together for testing, I'm adding it as an
HVM-based AMI. Is that the new type, or should I be using
Paravirtualization (PV) instead?
Application is pretty simple so far, it's under heavy development - All
built in Golang on Ubuntu 18.04. The build process is fairly standard --
I've added the application under the apps folder in the OSv directory,
created a module.py that references golang and sets the command line to
"--verbose /go.so /app.so" (I've tried adding the cloud-init module to this
too, but it doesn't seem to help), then build it with "./scripts/build
image=app fs_size_mb=100", then "./scripts/convert/raw."
I tried using the release-ec2.sh script to upload it to EC2 but that
appears to be woefully out of date (the AWS command line package no longer
includes the ec2-import-volume and ec2-run-instances commands, for
example). So instead I manually:
aws s3 cp ./build/release.x64/osv.raw s3://bucket-name/app.raw
and then
aws ec2 import-snapshot --description "testing" --disk-container
"Format=raw,UserBucket={S3Bucket=bucket-name,S3Key=app.raw}"
and once that's completed, I right click on the Snapshot in the EC2 console
and select Make Image to configure it as an AMI suitable for booting.
Once all of that's done, the system boots up correctly, and appears to get
a DHCP IP okay. But DNS doesn't work, and like I mentioned in the opening
remarks, the Metadata loopback addresses are not accessible.
Is there an older version of OSv that I should try this on to see if maybe
it's a recent change that's broken this? Or is my build process woefully
inadequate? :)
On Friday, January 4, 2019 at 12:49:14 AM UTC-5, Waldek Kozaczuk wrote:
>
> Hi Brian,
>
> Welcome to OSv mailing list. It has been at least a year I deployed OSv to
> an EC2 instance. And I have never used cloud-init which is what I am
> assuming you are using.
>
> Can you provide us with some details about the EC2 instance type you are
> trying to deploy OSv to? Is it new KVM type or old XEN? Can you tell us a
> little bit about the app? Did you try to prepend the OSv boot command line
> with '--verbose ' to see what happens during boot time.
>
> The second thing you are mentioned kind of reminds of some problems I had
> with vertx.io app (that uses netty). Is it by any chance this?
>
> Waldek
>
> On Wednesday, January 2, 2019 at 5:34:08 PM UTC-5, Brian Ledbetter wrote:
>>
>> I'm working on trying to deploy an application built on OSv 0.52.0 to
>> EC2, and am hitting a couple of snags -
>>
>> - Both the system and the application seem to be unable to find the
>> Amazon metadata address 169.254.169.254 (connection times out)
>> - Any web requests from the application to known hostnames (
>> ec2.amazonaws.com) fail with DNS lookups (returning address ::1 -
>> IPv6 isn't implemented within OSv yet, right?)
>>
>> Has anyone else hit this problem before? Or is this something I am doing
>> wrong?
>>
>> I couldn't find anything on the list about it. :)
>>
>
--
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.
