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?
On Tue, Feb 21, 2017 at 3:44 PM, Stephen John Smoogen smooge@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?
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.
-AdamM
-- Stephen J Smoogen. _______________________________________________ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org
On Wed, Feb 22, 2017 at 4:49 AM, Adam Miller maxamillion@fedoraproject.org wrote:
On Tue, Feb 21, 2017 at 3:44 PM, Stephen John Smoogen smooge@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?
On Wed, 22 Feb 2017 16:13:09 +0530 Sayan Chowdhury sayan.chowdhury2012@gmail.com wrote:
On Wed, Feb 22, 2017 at 4:49 AM, Adam Miller maxamillion@fedoraproject.org wrote:
On Tue, Feb 21, 2017 at 3:44 PM, Stephen John Smoogen smooge@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.
Hum. Who would that be then? Just Dennis?
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?
Might update the bug with any progress...
kevin
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.
We are still working on this.
On 27 February 2017 at 20:11, Matthew Miller mattdm@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.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen smooge@gmail.com wrote:
We are still working on this.
On 27 February 2017 at 20:11, Matthew Miller mattdm@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.
On Tue, Feb 28, 2017 at 9:43 PM, Sayan Chowdhury sayan.chowdhury2012@gmail.com wrote:
On Tue, Feb 28, 2017 at 8:25 PM, Stephen John Smoogen smooge@gmail.com wrote:
We are still working on this.
On 27 February 2017 at 20:11, Matthew Miller mattdm@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
infrastructure@lists.fedoraproject.org