want to find a way to move local laptop dev environment/images to aws

[Krist Jin]

Hi all,

What kind of vagrant box (virtualbox or vmware or aws etc. whatever) should I have on my laptop so that after I change it and package it, it can be deployed/moved to aws? I can't run a aws box on my laptop, right? 

What I want here is trying to find a solution where my laptop environment can be moved smoothly to aws. It's different from provision.

I also posted this question to stackoverflow

Thanks in advance!

[Alvaro Miranda Aguilera]

Hello,

The boxes shouldn't be important, what's important is the APP or code.

With that mindset, you can look into packer.io (also a hashicorp
product) and with that you can build the same box for AWS and Vagrant

So once you app/code is complete, you just spin a new AWS box and put
the code on top.

As Vagrant and AWS will be using the same box, it will work without problems.

Have a look at packer.io

Thanks
Alvaro.

> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/b1783a36-3a72-4024-a745-dce717bddc33%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Krist Jin]

Hi Alvaro,

Thanks for the reply.

Packer.io is a great tool, but I think it's not the suitable one for me here. According to my understanding, what it does is to create a bunch of same machine image for different platform (virtualbox, aws etc.) from a single configuration. But what I need here is to pack up local image and deploy it on aws, so there is no configuration here. All I have is a local running environment.

You mentioned "you just spin a new AWS box and put the code on top" but I don't get it. How can I move my environment (like installed packages etc.) to that aws box? Could you please elaborate on it a little bit?

Thank you so much!

-- 

Best Wishes,

Bo Jin (Krist)

Candidate, M.S. in Computer Science

Columbia University - School of Engineering and Applied Science

(917) 714-4594

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/mOR4gAh4Ckk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exWoMFxdyKcEBx%3DX8oS5%2BKZZMLjvS4azAPO3jmaB40zHQ%40mail.gmail.com.

[Alvaro Miranda Aguilera]

On Wed, Oct 7, 2015 at 2:17 AM, Krist Jin <krist.j...@gmail.com> wrote:
> for me here. According to my understanding, what it does is to create a
> bunch of same machine image for different platform (virtualbox, aws etc.)
> from a single configuration

Hello,

There is a way to import boxes in AWS, however I think is too complex,
and I haven't used.

So my suggestion was:

- Using Vagrant, you should have 2 sets of task
= Scripts that setup the base box
= The Code you use. or application.

Packer will help you to put into the base box the OS and those
provisioning scripts. The advantage of this will be faster vagrant up,
and that you can have multiple clouds base boxes.

On top of this, you can have some release process that take the
app/code, and will allow you to deploy this to a new box.

This may sound overkill, but is where I see the process is going.

So in your particular case, perhaps the best will be use the
vagrant-aws plugin, and develop directly on AWS ?

Thanks
Alvaro.