#99: AMI lifetimes (Cloud WG members vote needed)
--+
Reporter: oddshocks | Owner: oddshocks
Type: task | Status: new
Priority: normal
#99: AMI lifetimes (Cloud WG members vote needed)
--+
Reporter: oddshocks | Owner: oddshocks
Type: task | Status: new
Priority: normal
#99: AMI lifetimes (Cloud WG members vote needed)
--+
Reporter: oddshocks | Owner: oddshocks
Type: task | Status: new
Priority: normal
On Sat, Jan 9, 2016 at 1:26 AM, Sayan Chowdhury <
sayan.chowdhury2...@gmail.com> wrote:
> Hi,
>
> Currently, We don't delete any of the AMIs that are created by fedimg. Even
> though Amazon does not charge for the AMIs but snapshots which back
> the AMIs does cost us. We cannot delete the snapshot
#99: AMI lifetimes (Cloud WG members vote needed)
--+
Reporter: oddshocks | Owner: oddshocks
Type: task | Status: new
Priority: normal
Hi,
Currently, We don't delete any of the AMIs that are created by fedimg. Even
though Amazon does not charge for the AMIs but snapshots which back
the AMIs does cost us. We cannot delete the snapshots until the AMIs
are deregistered. In the
last few months the number of AMIs has grown which has l
I looked into this a bit more. Cloud-init provides an easy way to
give a fallback datasource when all other sources fail. It tries
multiple networked datasources before that.
For each of them, there is a 'timeout' and a 'max_wait' field. The
former is the timeout per connection attempt, and the la
