Deprecating Autocloud

2019-04-23 Thread Sayan Chowdhury 
Hi all,

Autocloud[1] has been part of the early stages of the 2-week Atomic
release process. AFAIK, it was built as a quick solution until
taskotron was not ready. Autocloud has served us well but over the
last year, we haven't pushed much to Autocloud and it's also mostly in
maintenance mode. Another big reason now for deprecating Autocloud is
that it's still in Python2.

Are there any concerns if we go ahead deprecate Autocloud in Fedora 31?

[1] https://apps.fedoraproject.org/autocloud/

Sayan
-- 
Sayan Chowdhury <https://words.yudocaa.in/>
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Deployment of plume in Fedora Infrastructure

2019-04-22 Thread Sayan Chowdhury 
> finally deprecating plume.

Typo here "finally deprecating fedimg"



-- 
Sayan Chowdhury <https://words.yudocaa.in/>
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Deployment of plume in Fedora Infrastructure

2019-04-22 Thread Sayan Chowdhury 
Hi all,

Over the last few months, I was working on integrating Fedora as a
sub-system to plume. This is to migrate from fedimg to plume, and
finally deprecating plume.

The work on plume has been completed and over the next few days, I
prepare for the deployment of plume. I've prepared a spec document for
the same[1]. I plan to move this to Fedora wiki in some time but if
someone wants to do a review can have a look at it and post comments.

[1] https://hackmd.io/fpDWrtuJT7-jt8jy2yJC1Q?view

-- 
Sayan Chowdhury <https://words.yudocaa.in/>
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180923.0

2018-09-26 Thread Sayan Chowdhury 
On Tue, Sep 25, 2018 at 8:49 PM  wrote:
>
>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180923.0
> Commit(x86_64): 
> 8b82902a0ca203645e9e288b8a0bbf9fe525749ec67cd674e6715daa64e5b7dd
> Commit(aarch64): 
> 9303c782b619bfeccfc8b0fb86a16ebf40b48c7c65e08d16c999b1618fd8b417
> Commit(ppc64le): 
> d789fe23cb4bba0d5d24fd345358d122b8caef97ab2572ad23292025823888ff
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180923.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180923.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180923.0.iso
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
>
> ppc64le:
>

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180917.0

2018-09-18 Thread Sayan Chowdhury 
On Tue, Sep 18, 2018 at 12:49 AM  wrote:
>
>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180917.0
> Commit(x86_64):
17b11d74047ded1264a57555a64ae6fc5d02a332c556679bfcf32864fc91f11e
> Commit(aarch64):
95cdc6d02ed7f3645bdd513b07b2c2db9b04e91d8aae897fa88e378285a2b551
> Commit(ppc64le):
ca3012e5792f84499783510e5586526b9eaf8d98f535e3de0157ec7f7ad369ae
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180917.0.aarch64.qcow2
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180917.0.aarch64.raw.xz
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180917.0.iso
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180917.0.ppc64le.qcow2
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180917.0.ppc64le.raw.xz
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180917.0.iso
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180917.0.x86_64.qcow2
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180917.0.x86_64.raw.xz
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180917.0.x86_64.vagrant-libvirt.box
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180917.0.x86_64.vagrant-virtualbox.box
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180917.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180917.0-aarch64-CHECKSUM
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180917.0-aarch64-CHECKSUM
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180917.0-ppc64le-CHECKSUM
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180917.0-ppc64le-CHECKSUM
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180917.0-x86_64-CHECKSUM
>
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180917.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180917.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
>
> ppc64le:
>

Re: [atomic-devel] Fedora Atomic Host Two Week Release Announcement: 28.20180902.0

2018-09-05 Thread Sayan Chowdhury 
On 05/09/18, nore...@fedoraproject.org wrote:
> 
> A new Fedora Atomic Host update is available via an OSTree update:
> 
> Version: 28.20180902.0
> Commit(x86_64): 
> 24d4ceb612af5abfa84f275ca9d8aff862e69d47aaeb177c0d64f30865fd7a9f
> Commit(aarch64): 
> c4deda4174d1a8f92db430c4f9cd39f79976e6e1b220d310a8b4867b7dda4ab3
> Commit(ppc64le): 
> 05af7ceb30fd26545a8cd8e3f2af04bf87fa180bb1eb4e07808da09f5b8695fc
> 
> 
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
> 
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> 
> Corresponding image media for new installations can be downloaded from:
> 
> https://getfedora.org/en/atomic/download/
> 
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180902.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180902.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180902.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180902.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180902.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180902.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180902.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180902.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180902.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180902.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180902.0.iso
> 
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180902.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180902.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180902.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180902.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180902.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180902.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180902.0-x86_64-CHECKSUM
> 
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
> 
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
> 
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
> 
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename
> 
>

[cloud-sig] Issue #284: Deprecate releasing PV AMIs

2018-03-28 Thread Sayan Chowdhury 

sayanchowdhury reported a new issue against the project: `cloud-sig` that you 
are following:
``
Fedimg releases PV and HVM images. The use of PV images has dwindled over years 
along with that the  AWS support for it. Its better to deprecate the PV images. 
 
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/284
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: amazon ec2 new type c5

2017-11-22 Thread Sayan Chowdhury 
On Sun, Nov 19, 2017 at 7:34 PM, Muayyad AlSadi <als...@gmail.com> wrote:
> hi,
>
> amazon ec2 have a new type c5
> fedora is not available on that
>
> https://aws.amazon.com/ec2/instance-types/c5/

ENA will be supported on the next release of fedimg[1]. So, the images
will be available soon on the instances that require ENA

[1] https://pagure.io/atomic-wg/issue/271


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #280: new meeting time for cloud sig

2017-07-27 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
22:30 IST it is, but we have the Atomic WG meeting around the same time so 
works for me

``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/280
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #279: stop creating PV AMIs for cloud base image

2017-07-24 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
Yes, I also think that we stop producing the PV images.
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/279
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[cloud-sig] Issue #280: new meeting time for cloud sig

2017-07-24 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
How about 1700UTC?
``

To reply, visit the link below or just reply to this email
https://pagure.io/cloud-sig/issue/280
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #286: tracker: AMIs in non us-east-1 regions aren't accessible

2017-07-13 Thread Sayan Chowdhury 

The status of the issue: `tracker: AMIs in non us-east-1 regions aren't 
accessible` of project: `atomic-wg` has been updated to: Closed as Fixed by 
sayanchowdhury.

https://pagure.io/atomic-wg/issue/286
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #286: tracker: AMIs in non us-east-1 regions aren't accessible

2017-07-06 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
The last deployment missed the fact that the snapshot needs to be explicitly 
made public in each region. 
I did a new release of fedimg == 0.7.5 today. Everything seems fine on staging. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/286
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-06-26 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
Seems like few of the snapshots were not getting the proper permission. Fix has 
been deployed. Should be fine now.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/263
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #286: tracker: AMIs in non us-east-1 regions aren't accessible

2017-06-26 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
The fixes have been deployed. Will wait for the next round of upload and close 
the issue.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/286
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-06-16 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
The fix has been deployed to production. I will keep this issue open for the 
weekend just to see everything turns out fine.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/263
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-04-19 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
I emailed @dbruno who is the maintainer of the python-libcloud package. He will 
be working on the releasing the updated package today itself.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/263
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #263: open up read permission on our AMIs

2017-04-12 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
The patch is included in the latest release "2.0.0rc2". But, we need to package 
the latest release before we can go ahead. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/263
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #237 `Migrate fedimg EC2Service from libcloud to boto`

2017-03-01 Thread Sayan Chowdhury 

sayanchowdhury reported a new issue against the project: `atomic-wg` that you 
are following:
``
fedimg `EC2Service` right now uses libcloud to create the AMIs. Libcloud does 
not support a lot of features whereas boto has a better documentation and 
provides the missing bits. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/237
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Cloud AMIs are not readable

2017-03-01 Thread Sayan Chowdhury 
On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury
<sayan.chowdhury2...@gmail.com> wrote:
> On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen <smo...@gmail.com> 
> wrote:
>> We are still working on this.
>>
>> On 27 February 2017 at 20:11, Matthew Miller <mat...@fedoraproject.org> 
>> wrote:
>>> On Thu, Feb 23, 2017 at 09:40:53AM -0700, Kevin Fenzi wrote:
>>>> > Neither me or Kushal has access to the account. So, somebody who has
>>>> > access to the account can go to the snapshot page and make the
>>>> > Snapshots public.
>>>> Hum. Who would that be then? Just Dennis?
>>>
>>> Did we find the answer to this? I have the account information recorded
>>> in an encrypted file just in case.
>
> I have written a script just haven't tested it. The script makes all
> the snapshots we have public. That should work for now.
>

Here is the script[1] that should make all the AMIs ready to be copied
[1] https://gist.github.com/sayanchowdhury/ffbc1f847ba84d47a454e4fd3cc603fd


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Meeting Minutes - February 22, 2017

2017-02-22 Thread Sayan Chowdhury 

#fedora-meeting-1: atomic-wg



Meeting started by dustymabe at 17:05:08 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-22/atomic-wg.2017-02-22-17.05.log.html
.



Meeting summary
---
* roll call  (dustymabe, 17:05:12)

* action items from last meeting  (dustymabe, 17:08:33)
  * ACTION: jberkus to open issues around each proposed dockerfile
requirements change  (dustymabe, 17:09:31)
  * LINK: https://pagure.io/atomic-wg/issue/228   (dustymabe, 17:09:41)

* decide on version scheme and image naming scheme for f26  (dustymabe,
  17:10:54)
  * LINK: https://pagure.io/atomic-wg/issue/229   (dustymabe, 17:10:58)

* clarify policy on atomic host support for older Fedora "number"
  releases  (dustymabe, 17:14:38)
  * LINK: https://pagure.io/atomic-wg/issue/228   (dustymabe, 17:14:43)

* clarify policy on atomic host support for older Fedora "number"
  releases  (dustymabe, 17:15:06)
  * LINK: https://pagure.io/atomic-wg/issue/228   (dustymabe, 17:15:18)

* move ostree ref to be "container-host"  (dustymabe, 17:19:57)
  * LINK: https://pagure.io/atomic-wg/issue/198   (dustymabe, 17:20:08)

* Future of Fedora Dockerfiles  (dustymabe, 17:23:20)
  * LINK: https://pagure.io/atomic-wg/issue/180   (dustymabe, 17:23:23)
  * ACTION: dusty to close Future of Fedora Dockerfiles #180
(dustymabe, 17:23:48)

* Ship fedora-motd in F24 atomic image  (dustymabe, 17:24:11)
  * LINK: https://pagure.io/atomic-wg/issue/160   (dustymabe, 17:24:24)

* Spec for IRC bot to notify about blockers  (dustymabe, 17:30:29)
  * LINK: https://pagure.io/atomic-wg/issue/169   (dustymabe, 17:30:44)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  (dustymabe, 17:31:18)
  * LINK: https://pagure.io/atomic-wg/issue/153   (dustymabe, 17:31:26)

* open floor  (dustymabe, 17:35:25)
  * ACTION: dusty to create atomic-wg page for future VFAD topics
(dustymabe, 17:36:55)
  * ACTION: jberkus to follow-up with misc and quaid about location of
HW  (jberkus, 17:39:23)
  * ACTION: jberkus to create vfad idea list page  (jberkus, 17:48:34)
  * ACTION: sayan to create ticket on moving fedimg from libcloud to
boto  (sayan, 17:49:09)

Meeting ended at 17:50:36 UTC.




Action Items

* jberkus to open issues around each proposed dockerfile requirements
  change
* dusty to close Future of Fedora Dockerfiles #180
* dusty to create atomic-wg page for future VFAD topics
* jberkus to follow-up with misc and quaid about location of HW
* jberkus to create vfad idea list page
* sayan to create ticket on moving fedimg from libcloud to boto




Action Items, by person
---
* jberkus
  * jberkus to open issues around each proposed dockerfile requirements
change
  * jberkus to follow-up with misc and quaid about location of HW
  * jberkus to create vfad idea list page
* misc
  * jberkus to follow-up with misc and quaid about location of HW
* sayan
  * sayan to create ticket on moving fedimg from libcloud to boto
* **UNASSIGNED**
  * dusty to close Future of Fedora Dockerfiles #180
  * dusty to create atomic-wg page for future VFAD topics




People Present (lines said)
---
* dustymabe (121)
* jberkus (33)
* sayan (25)
* roshi (21)
* zodbot (13)
* rtnpro (12)
* walters (4)
* misc (3)
* bowlofeggs (2)
* jbrooks (2)
* marc84 (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

2017-02-22 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
I second @jberkus, year/month/day is easier to read and interpret quickly.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/229
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Cloud AMIs are not readable

2017-02-22 Thread Sayan Chowdhury 
On Wed, Feb 22, 2017 at 4:49 AM, Adam Miller
<maxamill...@fedoraproject.org> wrote:
> On Tue, Feb 21, 2017 at 3:44 PM, Stephen John Smoogen <smo...@gmail.com> 
> wrote:
>> There is an outstanding bug report
>> https://bugzilla.redhat.com/show_bug.cgi?id=1423753 that came up in
>> the Fedora Server meeting today.
>>
>> Does someone know who can make this fixed? And who owns the Amazon AMI
>> account so it can be fixed quickly in the future?

I just returned back from conference and catching up with my emails.

>
> To the best of my knowledge, Kushal and Sayan have access to the
> account and Sayan is primary contact for fedimg and AMI related
> issues.

Neither me or Kushal has access to the account. So, somebody who has
access to the account can go to the snapshot page and make the
Snapshots public.

Libcloud does not support modifying the snapshot attribute. I am
writing a patch for the same. Till the time the patch does not get
merged I can use boto to complete the job. Sounds good?


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: AMI retention & publish process to AWS

2017-01-31 Thread Sayan Chowdhury 
On Tue, Jan 31, 2017 at 1:55 AM,  <p...@wesleytech.com> wrote:
> Greetings! Can someone please explain the process for publishing Fedora AMI's 
> to AWS?
>
> I see the "official" Fedora Cloud page has 'Click to launch' base images for 
> AWS here: https://alt.fedoraproject.org/cloud/
>
> However, if I click to launch the GP2 HVM AMIs, I see the us-west-2 (Oregon) 
> AMI listed is ami-3dea475d, which was published 2016-11-15.
>
> Do new AMI's get published on a particular cadence? If so, how/when does that 
> happen?
>
> If I search for AMI's from the Fedora account ID (125523088429), I can see 
> AMI's as recent as January 29th.
> https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#Images:visibility=public-images;ownerAlias=125523088429;search=Fedora-Cloud-Base-25;creationDate=%3E2017-01-01T00:00-07:00;sort=name
>
> Are all images published by the Fedora account suitable/recommended for use?
>
> I'm assuming that the newest AMI's would have all updates and patches up to 
> date as of the publish date, is this correct?
>
> What is the retention policy on AMI's? Can we count on a particular AMI (eg; 
> ami-d27bc3b2 ) being available and not disappearing for a specific amount of 
> time?

Regarding the deletion of the AMIs, a policy is in place[1]

- Delete the pre-release AMI(s) after the final release.
- Delete the nightly build AMI(s) after 5 days of the build.

The script will be deployed in next few days. For now the nightly AMIs
are deleted manually periodically. So, the AMIs to consider should be
the released AMIs till EOL. We are yet to decide on the policy for the
deletion of the released AMIs but for now the it can be considered
that they will be available till EOL.

[1] https://pagure.io/atomic-wg/issue/99
-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`

2017-01-06 Thread Sayan Chowdhury 

sayanchowdhury added a new comment to an issue you are following:
``
The old boxes has been shutdown and now autocloud is showing the correct number 
of images. 

Going ahead and closing the issue.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/182
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora Atomic 2016-11-09 RC Testing == Nightly Testing

2016-11-09 Thread Sayan Chowdhury 
On Wed, Nov 9, 2016 at 10:58 PM, Dusty Mabe <du...@dustymabe.com> wrote:

> Hey all,
>
> In Fedora Atomic the release process is disjoint from the rest of
> Fedora in that our images aren't produced as part of the normal
> "production" composes and RCs.
>
> I will make it a point to send out an email like this on the same day
> that every RC is created in Fedora so that we can attempt to verify
> our images continue to work throughout the process.
>
> Please take some time and attempt to confirm our images from last
> nights compose is working:
>
> [qcow]
> http://kojipkgs.fedoraproject.org/compose/branched/Fedora-
> 25-20161109.n.0/compose/CloudImages/x86_64/images/
> Fedora-Atomic-25-20161109.n.0.x86_64.qcow2
>
> [vagrant-libvirt]
> http://kojipkgs.fedoraproject.org/compose/branched/Fedora-
> 25-20161109.n.0/compose/CloudImages/x86_64/images/
> Fedora-Atomic-Vagrant-25-20161109.n.0.x86_64.vagrant-libvirt.box
>
> [vagrant-virtualbox]
> http://kojipkgs.fedoraproject.org/compose/branched/Fedora-
> 25-20161109.n.0/compose/CloudImages/x86_64/images/
> Fedora-Atomic-Vagrant-25-20161109.n.0.x86_64.vagrant-virtualbox.box
>
>
> Note that currently the ISO images aren't getting created. This is
> tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1392698
>
>
> Dusty
> ___
> cloud mailing list -- cloud@lists.fedoraproject.org
> To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
>

Here is the list of AMIs

Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-west-2)
ami-2cdf7c4chvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-west-1)
ami-61164301hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (sa-east-1)
ami-14c15e78hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (eu-west-1)
ami-d17325a2hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (eu-central-1)
ami-5bf70d34hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-southeast-2)
ami-0c46796fhvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-southeast-1)
ami-3319b950hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-west-2)
ami-bfd97adfhvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-northeast-1)
ami-b0349ad1hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (sa-east-1)
ami-b1c05fddhvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-west-1)
ami-7c11441chvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (eu-central-1)
ami-53f70d3chvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (eu-west-1)
ami-4a732539hvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-southeast-2)
ami-13457a70hvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-southeast-1)
ami-2b19b948hvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-east-1)
ami-3fb69428hvm   standard
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (ap-northeast-1)
ami-923698f3hvm   gp2
Fedora-Atomic-25-20161109.n.0.x86_64  EC2 (us-east-1)
ami-dab597cdhvm   gp2


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [Test-Announce] Fedora 25 Candidate RC-1.1 Available Now!

2016-11-09 Thread Sayan Chowdhury 
-Base-25-1.1.x86_64   EC2 (ap-southeast-2)
ami-104e7173hvm   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-southeast-1)
ami-0f13b36chvm   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (us-west-2)
ami-61ca6901paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-northeast-1)
ami-b0248ad1hvm   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-northeast-1)
ami-0b248a6aparavirtual   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (sa-east-1)
ami-39e37c55hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (us-west-1)
ami-84f4bee4hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (eu-west-1)
ami-825f09f1hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (eu-central-1)
ami-eafc0685hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-southeast-2)
ami-43506f20hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-southeast-1)
ami-1612b275hvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-northeast-1)
ami-6b228c0ahvm   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (sa-east-1)
ami-38e37c54paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (sa-east-1)
ami-38e37c54paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (eu-west-1)
ami-27540254paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (eu-central-1)
ami-76f00a19paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-southeast-2)
ami-2a4d7249paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-southeast-1)
ami-ad14b4ceparavirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (ap-northeast-1)
ami-d02987b1paravirtual   gp2
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (us-east-1)
ami-63f1d374hvm   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (us-east-1)
ami-99f1d38eparavirtual   standard
Fedora-Cloud-Base-25-1.1.x86_64   EC2 (us-east-1)
ami-9df2d08aparavirtual   gp2

Fedora-Cloud-Base-25-1.1.x86_64 EC2 (us-east-1) ami-4cedcf5b hvm gp2



-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Cloud Meeting Minutes 05-10-2016

2016-10-05 Thread Sayan Chowdhury 
==
#fedora-meeting-1: fedora_cloud_wg
==


Meeting started by sayan at 17:01:16 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-10-05/fedora_cloud_wg.2016-10-05-17.01.log.html
.



Meeting summary
---
* Roll Call  (sayan, 17:01:23)

* Action items from last meeting  (sayan, 17:03:53)
  * LINK: https://stg.pagure.io/atomic-wg/issues   (kushal, 17:07:29)
  * LINK: https://github.com/rtnpro/motdgen   (kushal, 17:08:12)
  * ACTION: kushal will clean up the wiki next week.  (kushal, 17:13:52)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (sayan, 17:14:11)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659#c42
(kushal, 17:18:36)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  https://fedorahosted.org/cloud/ticket/153  (sayan, 17:20:30)

* make Fedora Atomic download page clearer
  https://fedorahosted.org/cloud/ticket/154  (sayan, 17:22:41)

* Decide on post-GA update cadence for various deliverables
  https://fedorahosted.org/cloud/ticket/155  (sayan, 17:23:50)

* Need complete Kickstart docs for Atomic Host
  https://fedorahosted.org/cloud/ticket/156  (sayan, 17:25:29)

* Ship fedora-motd in F24 atomic image
  https://fedorahosted.org/cloud/ticket/160  (sayan, 17:27:26)

* Finish new Fedora Cloud PRD https://fedorahosted.org/cloud/ticket/170
  (sayan, 17:29:46)

* Open Floor  (sayan, 17:38:40)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659
(jbrooks, 17:49:05)

Meeting ended at 18:00:28 UTC.




Action Items

* kushal will clean up the wiki next week.




Action Items, by person
---
* kushal
  * kushal will clean up the wiki next week.
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* kushal (73)
* sayan (59)
* jberkus (52)
* jbrooks (34)
* zodbot (18)
* scollier (11)
* rtnpro (10)
* maxamillion (9)
* gholms (8)
* dustymabe (7)
* walters (6)
* vvaldez (2)
* trishnag (2)
* tflink (1)
* imcleod (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: Fedora 25 atomic images?

2016-10-02 Thread Sayan Chowdhury 
On Mon, Oct 3, 2016 at 4:03 AM, Dennis Gilmore <den...@ausil.us> wrote:
> On Saturday, October 1, 2016 8:41:45 AM CDT Matthew Miller wrote:
>> I see Fedora Rawhide, just Fedora (cloud base, I assume) 25, and Fedora
>> Atomic 24 in https://apps.fedoraproject.org/autocloud/compose?limit=20.
>> Shouldn't there also be an Atomic 25 branch by now? (Shouldn't there be
>> one starting with branching, for that matter?) Or am I just missing it?
>
> atomic and cload images are made daily as part of the branched compose. If
> they do not show up in autocloud then I suspect that is an issue with
> autocloud.
>

Are the fedmsg messages getting published? I could not find them in
datagrepper[1]

[1] 
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.pungi.compose.status.change

-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Cloud Meeting Minutes 2016-09-21

2016-09-21 Thread Sayan Chowdhury 
==
#fedora-meeting-1: fedora_cloud_wg
==


Meeting started by sayan at 17:00:36 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-21/fedora_cloud_wg.2016-09-21-17.00.log.html
.



Meeting summary
---
* Roll Call  (sayan, 17:00:48)

* Action items from last meeting  (sayan, 17:04:12)
  * ACTION: Kushal will work on moving to Pagure from Trac  (sayan,
17:06:19)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (sayan, 17:06:51)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  https://fedorahosted.org/cloud/ticket/153  (sayan, 17:08:24)

* make Fedora Atomic download page clearer
  https://fedorahosted.org/cloud/ticket/154  (sayan, 17:11:28)

* Decide on post-GA update cadence for various deliverables
  https://fedorahosted.org/cloud/ticket/155  (sayan, 17:55:09)

* Need complete Kickstart docs for Atomic Host
  https://fedorahosted.org/cloud/ticket/156  (sayan, 17:56:20)

* Put OpenShift Origin in Container with Fedora Base
  https://fedorahosted.org/cloud/ticket/168  (sayan, 17:58:18)

* Open Floor  (sayan, 18:00:00)
  * ACTION: jbrooks to send out an email to the list regarding Test Day
(sayan, 18:01:56)

Meeting ended at 18:03:17 UTC.




Action Items

* Kushal will work on moving to Pagure from Trac
* jbrooks to send out an email to the list regarding Test Day




Action Items, by person
---
* jbrooks
  * jbrooks to send out an email to the list regarding Test Day
* **UNASSIGNED**
  * Kushal will work on moving to Pagure from Trac




People Present (lines said)
---
* sayan (68)
* dustymabe (63)
* jbrooks (51)
* maxamillion (30)
* zodbot (24)
* jberkus (23)
* smooge (11)
* kushal (10)
* scollier (9)
* bowlofeggs (5)
* trishnag (3)
* tflink (2)
* subho (1)
* nzwulfin (1)
* rtnpro (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Cloud Meeting Minutes 2016-09-14

2016-09-14 Thread Sayan Chowdhury 
==
#fedora-meeting-1: fedora_cloud_wg
==


Meeting started by sayan at 17:00:24 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-14/fedora_cloud_wg.2016-09-14-17.00.log.html
.



Meeting summary
---
* Roll Call  (sayan, 17:00:33)

* Action items from last meeting  (sayan, 17:02:51)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (sayan, 17:06:00)

* Don't overwrite download location for 2 week atomic images
  https://fedorahosted.org/cloud/ticket/147  (sayan, 17:16:33)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  https://fedorahosted.org/cloud/ticket/153  (sayan, 17:19:47)

* make Fedora Atomic download page clearer
  https://fedorahosted.org/cloud/ticket/154  (sayan, 17:22:46)
  * ACTION: Kushal will work on moving to Pagure from Trac  (kushal,
17:35:33)

* Decide on post-GA update cadence for various deliverables
  https://fedorahosted.org/cloud/ticket/155  (sayan, 17:36:25)

* Need complete Kickstart docs for Atomic Host
  https://fedorahosted.org/cloud/ticket/156  (sayan, 17:39:29)

* Ship fedora-motd in F24 atomic image
  https://fedorahosted.org/cloud/ticket/160  (sayan, 17:41:40)

* Decide a process about failed tests for Autocloud
  https://fedorahosted.org/cloud/ticket/167  (sayan, 17:43:40)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1265295 and
https://bugzilla.redhat.com/show_bug.cgi?id=1353688  (kushal,
17:44:40)

* Put OpenShift Origin in Container with Fedora Base
  https://fedorahosted.org/cloud/ticket/168  (sayan, 17:55:25)

* Spec for IRC bot to notify about blockers
  https://fedorahosted.org/cloud/ticket/169  (sayan, 17:56:38)

* Open Floor  (sayan, 17:58:11)
  * ACTION: kushal will create the vote ticket, and update the list :)
(kushal, 18:05:35)

Meeting ended at 18:05:57 UTC.




Action Items

* Kushal will work on moving to Pagure from Trac
* kushal will create the vote ticket, and update the list :)




Action Items, by person
---
* kushal
  * kushal will create the vote ticket, and update the list :)
* **UNASSIGNED**
  * Kushal will work on moving to Pagure from Trac




People Present (lines said)
---
* kushal (76)
* sayan (67)
* jberkus (61)
* jbrooks (39)
* dustymabe (33)
* maxamillion (32)
* zodbot (20)
* walters (11)
* imcleod (8)
* trishnag (7)
* rtnpro (2)
* tflink (1)
* jdetiber (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Cloud Meeting Minutes 2016-08-17

2016-08-17 Thread Sayan Chowdhury 
==
#fedora-meeting-1: fedora_cloud_wg
==


Meeting started by sayan at 17:01:40 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-08-17/fedora_cloud_wg.2016-08-17-17.01.log.html
.



Meeting summary
---
* Roll Call  (sayan, 17:01:48)
  * LINK: https://fedoraproject.org/wiki/Cloud/Cloud_PRD   (jbrooks,
17:17:22)
  * LINK:

https://pagure.io/fork/walters/workstation-ostree-config/branch/f24-continuous
(kushal, 17:21:53)
  * ACTION: kushal to start off the atomic workgroup discussion on
mailing list  (kushal, 17:28:05)

* Action items from last meeting  (sayan, 17:28:42)
  * ACTION: rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image  (sayan, 17:30:12)
  * ACTION: kushal to write to infra for permission to update Autocloud
tests while in freeze  (sayan, 17:31:38)

* Fedora-Dockerfiles examples for Kubernetes
  https://fedorahosted.org/cloud/ticket/125  (sayan, 17:32:04)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
  (sayan, 17:34:26)

* Don't overwrite download location for 2 week atomic images
  https://fedorahosted.org/cloud/ticket/147  (sayan, 17:35:50)

* design, deploy and document Fedora OpenShift Playground (FOSP)
  https://fedorahosted.org/cloud/ticket/153  (sayan, 17:39:27)

* make Fedora Atomic download page clearer
  https://fedorahosted.org/cloud/ticket/154  (sayan, 17:42:26)

* Decide on post-GA update cadence for various deliverables
  https://fedorahosted.org/cloud/ticket/155  (sayan, 17:44:51)

* Need complete Kickstart docs for Atomic Host
  https://fedorahosted.org/cloud/ticket/156  (sayan, 17:50:16)

* Ship fedora-motd in F24 atomic image
  https://fedorahosted.org/cloud/ticket/160  (sayan, 17:53:10)

* Decide a process about failed tests for Autocloud
  https://fedorahosted.org/cloud/ticket/167  (sayan, 17:54:59)

* Put OpenShift Origin in Container with Fedora Base
  https://fedorahosted.org/cloud/ticket/168  (sayan, 17:55:36)

* Open Floor  (sayan, 17:56:07)
  * LINK: http://fedoracloud.readthedocs.io/en/latest/   (kushal,
17:56:53)
  * ACTION: gholms to test updated cloud-init on f24 for f25  (gholms,
17:57:36)

Meeting ended at 18:01:19 UTC.




Action Items

* kushal to start off the atomic workgroup discussion on mailing list
* rtnpro will add test workflow (and test cases) for testing fedora-motd
  on F24 atomic image
* kushal to write to infra for permission to update Autocloud tests
  while in freeze
* gholms to test updated cloud-init on f24 for f25




Action Items, by person
---
* gholms
  * gholms to test updated cloud-init on f24 for f25
* kushal
  * kushal to start off the atomic workgroup discussion on mailing list
  * kushal to write to infra for permission to update Autocloud tests
while in freeze
* rtnpro
  * rtnpro will add test workflow (and test cases) for testing
fedora-motd on F24 atomic image




People Present (lines said)
---
* sayan (51)
* kushal (46)
* jberkus (27)
* zodbot (24)
* jbrooks (22)
* maxamillion (22)
* gholms (9)
* x3mboy (9)
* jzb (8)
* vvaldez (5)
* scollier (4)
* dustymabe (4)
* nzwulfin (3)
* rtnpro (3)
* walters (3)
* trishnag (2)
* bowlofeggs (1)

-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Cloud Meeting Minutes 2016-06-15

2016-06-15 Thread Sayan Chowdhury 
HTML Version:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_wg.2016-06-15-17.03.html
Full Log:
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_wg.2016-06-15-17.03.log.html

==
#fedora-meeting-1: fedora_cloud_wg
==

Meeting started by sayan at 17:03:39 UTC. The full logs are
available at 
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_wg.2016-06-15-17.03.log.html

Meeting summary
--

* Roll Call (sayan, 17:04:03)
* Action items from last meeting (sayan, 17:10:34)
* scollier to create ticket for migrating docker hub to org (sayan, 17:11:33)
* jzb to follow up on getting fedora cloud images onto Azure and other
providers (sayan, 17:12:30)
* Fedora Cloud FAD (late 2015/early 2016)
https://fedorahosted.org/cloud/ticket/115 (sayan, 17:16:29)
   * ACTION: sayan to close the ticket 115 (sayan, 17:19:53)


* Fedora-Dockerfiles examples for Kubernetes
https://fedorahosted.org/cloud/ticket/125 (sayan, 17:20:45)

* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
(sayan, 17:23:21)

* Don't overwrite download location for 2 week atomic images
https://fedorahosted.org/cloud/ticket/147 (sayan, 17:24:48)

* Container "Packager" Guildelines and Naming Conventions
https://fedorahosted.org/cloud/ticket/148 (sayan, 17:31:02)

* Need owner to define basic container smoke testing requirements
https://fedorahosted.org/cloud/ticket/151 (sayan, 17:35:42)

* Fedora Coud Test Day for F24
https://fedorahosted.org/cloud/ticket/152 (sayan, 17:36:59)

* design, deploy and document Fedora OpenShift Playground (FOSP)
https://fedorahosted.org/cloud/ticket/153 (sayan, 17:47:08)

* make Fedora Atomic download page clearer
https://fedorahosted.org/cloud/ticket/154 (sayan, 17:55:55)

* Decide on post-GA update cadence for various deliverables
https://fedorahosted.org/cloud/ticket/155 (sayan, 17:58:32)

  * https://public.etherpad-mozilla.org/p/FedoraCloud-WG-FAD-2016
(dustymabe, 18:02:15)

* Need complete Kickstart docs for Atomic Host
https://fedorahosted.org/cloud/ticket/15 (sayan, 18:06:49)

* Open Floor (sayan, 18:07:51)
 * ACTION: jzb to follow up on getting fedora cloud images onto Azure
and other providers (dustymabe, 18:14:25)
 * ACTION: jzb take another run at legal on azure cloud issue
(dustymabe, 18:14:34)

Meeting ended at 18:15:01 UTC.

Action items
--

* sayan to close the ticket 115
* jzb to follow up on getting fedora cloud images onto Azure and other providers
* jzb take another run at legal on azure cloud issue



Action items, by person
--

* jzb
  * jzb to follow up on getting fedora cloud images onto Azure and
other providers
  * jzb take another run at legal on azure cloud issue

* sayan
   * sayan to close the ticket 115



People present (lines said)
---

* dustymabe (96)
* sayan (64)
* jzb (26)
* maxamillion (22)
* zodbot (21)
* rtnpro (12)
* jberkus (10)
* scollier (9)
* tflink (8)
* coremodule (7)
* sjennings (4)
* bowlofeggs (3)
* gholms (1)



-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

AMIs list for F24 RC1.2

2016-06-14 Thread Sayan Chowdhury 
Hi,

Here is the list of AMIs uploaded today for the Fedora 24 RC1.2 -


Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-1)
ami-806722e0paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (sa-east-1)
ami-819319edparavirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-2)
ami-2945bf49paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-west-1)
ami-aaa43bd9paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-central-1)
ami-51db323eparavirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-2)
ami-95f7def6paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-1)
ami-a2d102c1paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (sa-east-1)
ami-c1961cadhvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-1)
ami-c06025a0hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-2)
ami-2a45bf4ahvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-west-1)
ami-415ec132hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-central-1)
ami-2ed83141hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-2)
ami-f7f6df94hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-1)
ami-21d60542hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-northeast-1)
ami-3a779c5bparavirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-northeast-1)
ami-84709be5hvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-2)
ami-af47bdcfhvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (sa-east-1)
ami-c3961cafparavirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-2)
ami-2c4ab04cparavirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-1)
ami-7e67221eparavirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-west-1)
ami-5fa33c2cparavirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-central-1)
ami-28d83147paravirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-2)
ami-66f6df05paravirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (sa-east-1)
ami-67971d0bhvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-west-1)
ami-2c67224chvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-west-1)
ami-1ca03f6fhvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-2)
ami-96f7def5hvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (eu-central-1)
ami-b6d930d9hvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-1)
ami-9fd003fchvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-northeast-1)
ami-ba759edbhvm   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-southeast-1)
ami-24d60547paravirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (ap-northeast-1)
ami-a8769dc9paravirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-east-1)
ami-cbf430a6paravirtual   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-east-1)
ami-72eb2f1fhvm   standard
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-east-1)
ami-3ae92d57paravirtual   gp2
Fedora-Cloud-Base-24-1.2.x86_64   EC2 (us-east-1)
ami-f0ea2e9dhvm   gp2




-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Re: Instances in AWS

2016-06-13 Thread Sayan Chowdhury 
On Mon, Jun 13, 2016 at 8:16 AM, Dusty Mabe <du...@dustymabe.com> wrote:
> There are some extra running instances in our AWS account.
>
> They are named "Fedimg AMI Tester" and they have been up since June 7th.
>
> Can these be cleaned up?

I have terminated the instances


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

List of AMIs uploaded in last 1 day

2016-06-07 Thread Sayan Chowdhury 
  EC2 (sa-east-1)
ami-d60c87baparavirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (eu-central-1)
ami-4508e62aparavirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (eu-west-1)
ami-76f66b05paravirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-southeast-2)
ami-d391bfb0paravirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-southeast-1)
ami-db06d6b8paravirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (eu-central-1)
ami-150be57ahvm   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-southeast-1)
ami-d806d6bbhvm   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-southeast-2)
ami-1590be76hvm   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-northeast-1)
ami-c8b35aa9hvm   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (ap-northeast-1)
ami-cfb059aeparavirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (us-east-1)
ami-1eed1473hvm   standard
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (us-east-1)
ami-7eed1413paravirtual   standard
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (us-east-1)
ami-f4ea1399paravirtual   gp2
Fedora-Cloud-Base-23-20160607.x86_64  EC2 (us-east-1)
ami-51ec153chvm   gp2


-- 
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13  AB3C B023 9931 9CD0 5C8B


Proud to work at The Open Organization!
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org

Proposal for AMI Lifetimes

2016-01-08 Thread Sayan Chowdhury 
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 led to humongous bills.

So, we need to delete the AMIs based on parameters on which we can de-register
the AMIs and delete the associated snapshots.

So, me and Kushal want to propose the following based on the
discussion on the trac[1] and mailing list[2]. We updated the
trac ticket[1] with this proposal.

1. Delete the pre-release AMIs after the final release.
2. Delete the nightly builds every five days.

Can all the WG members vote on the ticket?

[1] https://fedorahosted.org/cloud/ticket/99
[2] https://lists.fedoraproject.org/pipermail/cloud/2015-March/005087.html


Sayan
-- 
https://sayanchowdhury.dgplug.org
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org