Thanks very much.

I tried lot of combinations, I thought I tried this one, but obviously not
:)

For debian 8 hvm, the right configuration is :

            "launch_block_device_mappings": [
                {
                    "device_name": "/dev/xvda",
                    "delete_on_termination": true,
                    "volume_size": 20,
                    "volume_type": "gp2"
                }



2016-12-22 13:01 GMT+01:00 Loren Gordon <lo...@fleet-it.com>:

> I do that with "launch_block_device_mappings". An example is below. The
> "device_name" for the root device will depend a bit on the underlying AMI,
> and whether it is PVM or HVM, but it should be the same as the Root Device
> Name associated with the AMI itself.
>
>             "launch_block_device_mappings": [
>                 {
>                     "device_name": "/dev/sda1",
>                     "delete_on_termination": true,
>                     "volume_size": 20,
>                     "volume_type": "gp2"
>                 }
>             ],
>
> -Loren
>
>
> On Thursday, December 22, 2016 at 5:05:21 AM UTC-5, Pierre Freund wrote:
>>
>> Hello,
>>
>> I would like to create an AMI of a database with data inside, for dev
>> environments. I am using Terraform / Packer / Chef-solo.
>> The chef receipe download dumps from S3, and load it into the mongodb
>> database.
>>
>> I can't find how to tell Packer that my root volume device should be like
>> 30Go, and not the default value 8Go.
>>
>> The EBS-backed documentation shows how to add another disk with
>> "launch_block_device_mappings", but I don't want to add a new one and
>> make all the filesystems command.
>> If I try to modify xvda, Packer tells me that the volume is already in
>> use.
>>
>> I just want to set the root volume size, as it is possible natively in
>> AWS.
>>
>> How can I do ?
>>
>> Thanks,
>>
>> Pierre Freund
>>
> --
> 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/packer/issues
> IRC: #packer-tool on Freenode
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Packer" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/packer-tool/45tyuM68vWo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> packer-tool+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/packer-tool/d3670898-45e7-4bcc-981e-e4bca951eeea%40googlegroups.com
> <https://groups.google.com/d/msgid/packer-tool/d3670898-45e7-4bcc-981e-e4bca951eeea%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/packer/issues
IRC: #packer-tool on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to packer-tool+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/packer-tool/CAMJ_%2BCqrrts%3D1-aEKU%3DtxL4hSw6oJkeawPe7miSGCDcj9krvuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to