New Meeting Time!

2015-06-16 Thread David Gay
Hi all!

We've received[1] only +1's (and plenty of them!) to move the weekly Cloud SIG 
meeting 2 hours earlier. Until further notice, the meeting will be held at 1700 
UTC on Wednesdays[2].

Congratulations to Kushal and the everyone else on that side of the rock. You 
can turn off your coffee pots a bit earlier. ;)

-- David

[1]: https://lists.fedoraproject.org/pipermail/cloud/2015-June/005419.html
[2]: https://apps.fedoraproject.org/calendar/meeting/1999/
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


[Vote] Retire 32 bit images

2015-06-16 Thread David Gay
For some time now, there's been discussion of ending production of 32 bit cloud 
images. Dusty's been kind enough to create a ticket regarding this matter[1].

Thoughts on this? +1/+0/-1? There could be a reason that we shouldn't stop 
producing 32 bit images that someone hasn't voiced yet. We can discuss during 
the meeting this week, as well.

-- David

[1]: https://fedorahosted.org/cloud/ticket/106#comment:2
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: [Cloud WG] meeting time change request

2015-06-10 Thread David Gay
- Original Message -
 From: Haïkel hgue...@fedoraproject.org
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Wednesday, June 10, 2015 11:54:56 AM
 Subject: [Cloud WG] meeting time change request
 
 Hi,
 
 I request that we change the meeting time to 5PM UTC.
 It should be fine for most of us, and we can't keep that current
 schedule.
 Please vote in that thread (-1/+0/+1)
 
 ---
 
 +1
 
 Regards,
 H.
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

+1 from me, as well.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


No meeting today

2015-06-10 Thread David Gay
Hi all,

We're a bit short on bodies today. A lot of people are out. So, no meeting this 
week.

Also, the meeting is quite late for folks like Kushal, who usually runs the 
meeting (12:30 AM his time). Make sure to vote on Haïkel's proposal to move the 
meeting two hours earlier[1], which should work for everyone.

Best,
David

[1]: https://lists.fedoraproject.org/pipermail/cloud/2015-June/005419.html
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: AMI ids for F22 final RC2?

2015-05-21 Thread David Gay
- Original Message -
 From: Matthew Miller mat...@fedoraproject.org
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Thursday, May 21, 2015 6:43:03 AM
 Subject: AMI ids for F22 final RC2?
 
 I know these are in fedmsg somewhere or something, but for testers'
 convenience, what are the AMI ids for RC2?
 
 --
 Matthew Miller
 mat...@fedoraproject.org
 Fedora Project Leader
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

I can send a list to this... list shortly. :)

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Final RC2 AMIs

2015-05-21 Thread David Gay
Good morning, everyone.

You'll find the final RC2 AMIs in any region by doing a search for 
Fedora-Cloud-Base-22-20150520 or Fedora-Cloud-Atomic-22-20150520. Let me 
know if there are any issues.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Screen in F22 Atomic?

2015-04-17 Thread David Gay
- Original Message -
 From: Matthew Miller mat...@fedoraproject.org
 To: j...@redhat.com, Fedora Cloud SIG cloud@lists.fedoraproject.org
 Cc: atomic-de...@projectatomic.io
 Sent: Friday, April 17, 2015 7:59:16 AM
 Subject: Re: Screen in F22 Atomic?
 
 On Fri, Apr 17, 2015 at 02:45:25AM -0400, Joe Brockmeier wrote:
  Did I miss something, or when did we decide to add screen? IIRC that
  was discussed and rejected, as we already provide tmux.
 
 +1 to just tmux
 
 --
 Matthew Miller
 mat...@fedoraproject.org
 Fedora Project Leader
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

Another +1 to just tmux.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: atomic and getfedora

2015-04-15 Thread David Gay
- Original Message -
 From: Matthew Miller mat...@fedoraproject.org
 To: j...@redhat.com, Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Wednesday, April 15, 2015 12:40:26 PM
 Subject: atomic and getfedora
 
 On Tue, Apr 14, 2015 at 09:58:28AM -0400, Joe Brockmeier wrote:
   That works for me. Any volunteers for actually working on making
   http://atomic.fedoraproject.org/?
   And to clarify, we're then backing out all of the Atomic bits in Fedora
   22
   mainline rel-eng such as the repository and cloud image, vagrant box,
   and installer?
  No - the plan is still to deliver F22 Atomic, though it's non-blocking.
  But we will not be doing an official F23 Atomic.
 
 So, in combination with what you posted earlier
 
 As in Fedora 21, the Fedora 22 Atomic image is a kind of snapshot
 of work in progress. The after F22 is released, we're actually
 moving Atomic to a different model, less coupled to Fedora
 releases, at least until the technology matures a little bit. The
 Fedora Atomic team intends to release these every two weeks on
 http://atomic.fedoraproject.org/, and you'll be able to do an
 atomic upgrade from the F22 release to that once it's ready.
 
 I'd still kind of like to think about moving the F22 atomic image
 release to http://atomic.fedoraproject.org/, too (especially since it's
 still non-blocking). Then, https://getfedora.org/en/cloud/download/
 could become a little less maze-like.
 
 I'm thinking we would add prominent links, with logos, to Fedora Atomic
 and to the Fedora Docker Base image (which already has a home at
 http://spins.fedoraproject.org/docker/). This could either be blocks on
 the right-side bar, or horizontal stripey panels in keeping with the
 new design.
 
 
 If this sounds good to people, I can start the conversation with the
 web team. The initial Atomic page will probably look basically like the
 Docker one linked above, but could eventually grow its own design.
 
 
 
 --
 Matthew Miller
 mat...@fedoraproject.org
 Fedora Project Leader
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

+1 from me!

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Testables for beta TC2

2015-03-31 Thread David Gay
- Original Message -
 From: M. Edward (Ed) Borasky zn...@znmeb.net
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Tuesday, March 31, 2015 5:31:28 PM
 Subject: Re: Testables for beta TC2
 
 Yeah - that's what I'm looking for. I must have missed an announcement.
 
 On Tue, Mar 31, 2015 at 4:42 PM, David Gay d...@redhat.com wrote:
  - Original Message -
  From: M. Edward (Ed) Borasky zn...@znmeb.net
  To: Fedora Cloud SIG cloud@lists.fedoraproject.org
  Sent: Tuesday, March 31, 2015 3:25:18 PM
  Subject: Re: Testables for beta TC2
 
  Is there going to be a new Atomic image soon? I've done pretty much
  all I can with TC2 - I got everything working except Cockpit, which
  doesn't seem to be in the image.
 
  Not sure if this is what you're looking for, but there are Atomic and
  Vagrant images for TC5 that have been out for a few days:
 
  http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC5/Cloud-Images/x86_64/Images/
 
  -- David
  ___
  cloud mailing list
  cloud@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/cloud
  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 
 
 
 --
 OSJourno: Robust Power Tools for Digital Journalists
 http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists
 
 Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

Yeah, it was announced on rel-eng list. Enjoy! :)

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Testables for beta TC2

2015-03-31 Thread David Gay
- Original Message -
 From: M. Edward (Ed) Borasky zn...@znmeb.net
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Tuesday, March 31, 2015 3:25:18 PM
 Subject: Re: Testables for beta TC2
 
 Is there going to be a new Atomic image soon? I've done pretty much
 all I can with TC2 - I got everything working except Cockpit, which
 doesn't seem to be in the image.

Not sure if this is what you're looking for, but there are Atomic and Vagrant 
images for TC5 that have been out for a few days:

http://dl.fedoraproject.org/pub/alt/stage/22_Beta_TC5/Cloud-Images/x86_64/Images/

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: [FINAL CONFIRMATION] Deleting pre-F21 AMIs

2015-03-25 Thread David Gay
- Original Message -
 From: Jay Greguske jgreg...@redhat.com
 To: cloud@lists.fedoraproject.org
 Sent: Wednesday, March 25, 2015 2:07:55 PM
 Subject: Re: [FINAL CONFIRMATION] Deleting pre-F21 AMIs
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 03/25/2015 04:59 PM, David Gay wrote:
  Greetings.
  
  As one of the things discussed in the AMI lifetimes thread this
  month, I would like to delete all Alpha, Beta, TC, RC, and other
  scratch AMIs pre-F21 from *both* our community cloud and official
  AWS accounts.
  
  I've gotten a +1 via list, and two +1s in the meeting today. There
  have been no objections on the list or in the meeting. This will
  save us a notable amount in AWS storage charges.
  
  Unless anyone has an objection, I'll start (carefully) deleting
  these AMIs in 24 hours.
  
  -- David ___ cloud
  mailing list cloud@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code
  of Conduct: http://fedoraproject.org/code-of-conduct
  
 
 For what it's worth, AWS prevents you from deleting an EBS snapshot
 that backs an AMI. So if you de-register the wrong one, you can still
 re-register it back from that. You'll get a different AMI ID though,
 and there is nothing I'm aware of that you can do about that.
 
 - - Jay

Ah yeah, I recall that. The problem is the ID though, which yeah, you can't get 
back. Don't want to accidentally delete something people might be using in 
their scripts.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


[FINAL CONFIRMATION] Deleting pre-F21 AMIs

2015-03-25 Thread David Gay
Greetings.

As one of the things discussed in the AMI lifetimes thread this month, I 
would like to delete all Alpha, Beta, TC, RC, and other scratch AMIs pre-F21 
from *both* our community cloud and official AWS accounts.

I've gotten a +1 via list, and two +1s in the meeting today. There have been no 
objections on the list or in the meeting. This will save us a notable amount in 
AWS storage charges.

Unless anyone has an objection, I'll start (carefully) deleting these AMIs in 
24 hours.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Password policy changes

2015-03-24 Thread David Gay
- Original Message -
 From: Matthew Miller mat...@fedoraproject.org
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Cc: desk...@lists.fedoraproject.org, ser...@lists.fedoraproject.org, 
 k...@lists.fedoraproject.org
 Sent: Tuesday, March 24, 2015 2:25:02 PM
 Subject: Re: Password policy changes
 
 On Tue, Mar 24, 2015 at 08:36:28AM -0700, Adam Williamson wrote:
  I'm wondering if those products/spins intending to set a policy weaker
  than the default could all agree on the same one, so there'd only be
  at most two policies to care about (and if all products/spins overrode
  the upstream default, there'd only be one).
 
 I won't speak for everyone, but I *think* the general cloud attitude
 here is to use private/public keys and certificate-based auth instead of
 passwords in any case.
 
 --
 Matthew Miller
 mat...@fedoraproject.org
 Fedora Project Leader
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

That's been my experience, as well.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Fedora EC2 Amis: SriovNetSupport

2015-03-24 Thread David Gay
- Original Message -
 From: milanisko k vetri...@gmail.com
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Friday, March 20, 2015 7:52:21 AM
 Subject: Re: Fedora EC2 Amis: SriovNetSupport
 
 That would be one way.
 However, since it actually is a majority of the instance types[1] that
 support this feature, I'd vote to make it the default.
 That's unless it prevents using/booting the small instances of course,
 what AFAIK isn't the case --- I was able to create a snapshot ami from an F21
 instance,
 register it with the sriov flag and boot both a t2 and an r3 instances
 without any issue and confirmed the sriov flag was in effect on the r3
 instance.
 The only limit I know of is the ami has to be HVM[2].
 Moreover, the feature is for free, no extra charges apply so why not to take
 advantage of lower latencies on the instances.
 
 Cheers,
 milan
 
 [1] Enhanced Networking Support, The Instance Types Matrix,
 http://aws.amazon.com/ec2/instance-types/
 [2] Enabling Enhanced Networking on Other Linux Distributions,
 http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html
 
 
 
 2015-03-19 18:39 GMT+01:00 Garrett Holmstrom  gho...@fedoraproject.org  :
 
 
 On 2015-03-19 9 :11, milanisko k wrote:
 
 
 I'd like to ask about the status/plan of SriovNet support[1] for Fedora
 Amazon images.
 I was able to set this up manually for recent F21 ami ami-5cd9ea41, but
 it is quite an inconvenient experience --- one has to instantiate, stop,
 set attribute value through the CLI tool and start again to enable the
 feature.
 Would it be possible to register future Fedora amis with the enhanced
 networking flag enabled[1]?
 As far as motivation is concerned, please check the blog post[2] for
 some performance evaluation.
 
 Since that only works for some types of instances it wouldn't make sense to
 do that for all images, but registering a separate image (from the same
 bundle/snapshot) with that enabled would be reasonable.
 
 --
 Garrett Holmstrom
 __ _
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject. org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code- of-conduct
 
 
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

I'm responsible for Fedimg which uploads our AMIs. Seems to be a reasonable 
thing to get people's opinions on. Do you *have* to start the instance up then 
stop it and do all the stuff at [1]? If that has to be done for every HVM 
upload we provide, that might add some significant time and oddness to the 
automatic upload process. I don't see a way to just simply toggle a flag at AMI 
registration time, but then again, I'm not familiar with enhanced networking on 
AWS.

-- David

[1]: 
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux
 under Enabling Enhanced Networking on Other Linux Distributions
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Cloud image lifetimes

2015-03-24 Thread David Gay
Cool, thanks for the input everyone. A short summary of what's been discussed:

1. Everyone seems to agree that we should hope to get usage data from AWS, but 
as Dennis mentioned (and I expect), there isn't any usage data available for 
AMIs. If there is such a console, I've never seen one.

2. Q: If a user spins up an AMI and then it's deleted by the provider, do they
still have their instance(s) or do they lose the ability to create new
images?
  A: The instances they already started would still run and be available, but
  they wouldn't be able to spin up anything new. If creating/killing
  instances is something they do a lot (autoscaling groups, worker farms,
  etc) then that could hose them just as surely as killing their existing
  instances.

3. We should probably look into how other projects handle their AMIs. I think 
the consensus here though is that whatever lifetime we have for releases, the 
alpha, beta, TC, RC, and other testing builds can -- and should -- be safely 
eliminated after the release. There's no good reason I can think of that 
someone would yell at us for deleting a test build AMI of a release that's 
already happened.

4. Anyone have an opinion on jzb wondering if we should run this by FESCo?

5. Regarding this exchange:

at around $5/month, so each final AMI built will cost $5 * 13-16
months, or $65-$80. Not expensive, but not exactly free. Costs will, of
course, vary for other cloud providers.
  your math is off, there should only be 9 Atomic as we only build it for 
x86_64
  where we build the base for i386 and x86_64  so you have two arches by 2 image
  types by 9 regions

Whatever the costs will be per AMI, I can tell you that what I've heard from 
people in the cloud WG is that we want a number of different AMIs *per build*. 
A new build currently results in 6 AMIs: 2 for atomic (standard + gp2) and 4 
for base (standard + gp2, both for HVM and paravirtual virtualization). I spoke 
with gholms some time back and I think we determined that we're also going to 
want instance-store AMIs, as well as *encrypted* EBS AMIs. So, maybe there 
should be some discussion on that with the full group, since that will result 
in a large number of AMIs. If we end up building that many different 
combinations of storage types, volume types, and virtualization types, we're 
talking a fair amount of AMIs being kept up during the release process, because 
of how many image builds go through Koji. Dennis mentioned to me that there is 
some sort of Koji bug that, if fixed, would builds be marked as either real 
life or scratch, so we could at least cut down a bit on the number of AMIs 
being built.

I think this discussion should continue a bit more based on all that. However, 
I *do* move that I immediately delete at least all the alpha, beta, TC, and RC 
builds that were created back when we were working on F21.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Fedora Cloud Docs

2015-03-24 Thread David Gay
- Original Message -
 From: Pete Travis li...@petetravis.com
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org, j...@redhat.com
 Sent: Tuesday, March 24, 2015 11:04:00 AM
 Subject: Re: Fedora Cloud Docs
 
 
 
 
 On Mar 24, 2015 11:38 AM, Joe Brockmeier  j...@redhat.com  wrote:
  
  On 03/24/2015 01:01 PM, Jared K. Smith wrote:
   
   If there's a particular cloud-related topic you'd like to write about --
   go write! And then we can worry about the tooling, once there's some
   content to work with.
  
  I agree...ish. If Kushal, myself, mattdm, and jbrooks (for example) are
  collaborating on a document, we really need a single format to target.
  
  Best,
  
  jzb
  --
  
 
 I was actually polling about preferred markup format, because I am writing
 tools, but Jared is right: don't let things like my misadventures with
 python hold you back! Start now, don't worry about formats, docs will handle
 the business of publishing and converting.
 
 --Pete
 
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

I think it'd be good to have at least all *our* (Cloud) docs in one format. I 
think it'd be a good idea to have that vote on markdown, rst, or otherwise.

Of course, not being sure of that format yet doesn't mean you can't do some 
writing now.

My two cents.
-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Cloud image lifetimes

2015-03-18 Thread David Gay
Greetings!

We sort of ran out of time in today's Cloud WG meeting, but I did want to ask:

What are your thoughts on AMI lifetimes? That is to say, how long should EC2 
AMIs exist before they're deleted? A few points to consider:

- AMIs only cost us for storage, so it's not a *huge* cost to maintain a public 
AMI
  - At the same time, there are a lot of AMIs, since we build 2-4 per AWS 
region per build, and that number is growing
- There are 9 regions now, and we have 2 virtualization types, and 2 volume 
types, as well (9 regions * 2 * 2 = 36 AMIs per Base image build, 18 for Atomic 
builds (since they are only available in HVM format))
  - This total number will only grow larger as we add instance-store AMIs, 
and so on
- This isn't even taking into account any costs we'll have once we secure a 
deal with other providers like HP, Rackspace, and GCE, to maintain public 
images on their services

I propose we have some sort of discussion regarding how long cloud image builds 
should be available on services like AWS. I suspect this will resolve to having 
different lifetimes for scratch, test, RC, final, and maybe other build types.

Any input is appreciated. We can certainly talk about this at next week's 
meeting, as well.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: dnf migration period

2015-03-13 Thread David Gay
- Original Message -
 From: Mike Ruckman ro...@fedoraproject.org
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Friday, March 13, 2015 11:29:28 AM
 Subject: dnf migration period
 
 Greetings fellow cloudies!
 
 This bug (https://bugzilla.redhat.com/show_bug.cgi?id=1201655) spawned a
 conversation on IRC that we thought should be moved here to the list.
 
 With the migration from yum to dnf in full swing, we've got to figure
 out what the intent translates to regarding packages installed on the
 cloud image. Currently, yum is not installed on the cloud images, only
 dnf. Judging by this discussion during a fesco meeting [0], this is
 known and expected.
 
 The other flavors (Workstation and Server) both have yum installed upon
 fresh installation. libreport pulls yum in as a dep - so yum is only
 there until libreport gets migrated. The question for us is, do we want
 a migration period for cloud users to have time to migrate their tools
 to dnf? I think from a mere usability standpoint, it makes sense to have
 yum and dnf installed alongside each other so things don't break; but I
 can see both sides of the argument.
 
 More information on the history of this discussion can be found in the
 meeting log [0], and this fesco ticket [1].
 
 Thoughts?
 
 [0]
 http://meetbot.fedoraproject.org/teams/fesco/fesco.2015-02-25-18.01.log.html
 [1] https://fedorahosted.org/fesco/ticket/1312
 
 --
 // Mike
 --
 Fedora QA
 freenode: roshi
 http://roshi.fedorapeople.org
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

I don't see a problem with keeping both installed alongside each other for now, 
as long as people are aware that they *need* to migrate to dnf. We don't want a 
Python 2 - 3 migration period. :P

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Fresh F22 Alpha AMIs for testing

2015-03-09 Thread David Gay
Greetings!

Attached is a list of F22 Cloud AMIs for the latest image build done today. 
They could use some testing love!

-- David

f22_cloud_amis_20150309.txt.gpg
Description: application/pgp-encrypted
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


[Needs action] Vagrant images on prerelease page

2015-03-06 Thread David Gay
Greetings.

If we want the vagrant images to be listed on the prerelease page, the web team 
needs some text to put with them, like we do for the other images. I pinged a 
few vagrant-connected folks in IRC, but it seems they're not around. Assuming 
we *do* want these images listed, can someone with knowledge of them produce 
some sort of text to send to the web team?

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


F22 Alpha AMIs

2015-03-06 Thread David Gay
Greetings, and congratulations on F22 Alpha!

Attached is a list of official F22 Alpha AMIs. Robyduck will take care of 
putting them on the website.

-- David

f22_cloud_alpha_amis.txt.gpg
Description: application/pgp-encrypted
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Fresh AMIs (official Fedora acct, min vol size)

2015-02-03 Thread David Gay
- Original Message -
 From: Dusty Mabe du...@dustymabe.com
 To: cloud@lists.fedoraproject.org
 Sent: Tuesday, February 3, 2015 7:19:09 AM
 Subject: Re: Fresh AMIs (official Fedora acct, min vol size)
 
 On Mon, Feb 02, 2015 at 11:00:27PM -0500, David Gay wrote:
  Hello, cloud friends.
  
  I've attached a signed list of fresh AMIs for the images we provide through
  [1]. If no one sees any problems here, we could ask someone from the web
  team to update that page with these new AMIs.
  

[snip]

 A few questions/comments:
 
 - Do these images include updates? I think our AMI release cadence should
   mirror our release schedule for the xz/qcow2 images.

These AMIs were created from the images we provide at [1]. Specifically, [2] 
and [3]. Whatever's in those images is what's in these AMIs. Is there another 
image they should have been built from? If so, I'm missing something. My 
understanding is that a new image build would have shown up in Koji. That's 
what triggers Fedimg. Apparently, there hasn't been a successful createImage 
task in weeks[4].

[1]: 
https://getfedora.org/en/cloud/download/#Amazon%20Public%20Cloud%20EC2%20Images
[2]: 
http://download.fedoraproject.org/pub/fedora/linux/releases/21/Cloud/Images/x86_64/Fedora-Cloud-Base-20141203-21.x86_64.raw.xz
[3]: 
http://download.fedoraproject.org/pub/fedora/linux/releases/21/Cloud/Images/x86_64/Fedora-Cloud-Atomic-20141203-21.x86_64.raw.xz
[4]: 
http://koji.fedoraproject.org/koji/tasks?state=allview=flatmethod=createImageorder=-id

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: EC2 cloud image size

2015-01-30 Thread David Gay
- Original Message -
 From: Dmitry Makovey dmi...@athabascau.ca
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Thursday, January 29, 2015 11:50:52 AM
 Subject: Re: EC2 cloud image size
 
 On 01/02/2015 05:46 PM, David Gay wrote:
  Hey -- I actually solved this problem during the holidays. Lowered
  the size to 3 GB as suggested. There just haven't been any new builds
  that have gone through, and I haven't cut a new version just yet
  anyway (due to the holidays). It's no problem for me to send someone
  a list of fresh AMIs of the F21 cloud build with the lowered size
  tomorrow, if someone can toss them on the official website, as well.
  But yeah, this is all done. Just had to tweak two numbers is all.
  
 
 OK, So David's part is done, however AWS still shows old AMI's. Does it
 mean we have to nudge/bump someone to push new images over?

The AMIs need to be updated on the web team's side. I'm told I'd probably have 
to send a patch in rather than get commit access. I'd like to provide them with 
a list of entirely fresh AMIs with the smaller volume size, including the new 
base HVM images. Do we have someone who's looped in with the web team (maybe 
robyduck?) who can manage this? I could write a patch myself, but I've looked 
at the code and I'm unfamiliar with the particular templating language and JS 
used on that area of the page, and also, we need a new 
button/selector/something so that users can choose paravirtual or HVM when they 
select Fedora Cloud base. I figured the implementation of that new 
button/selector/whatever should be left up to the web team.

All that being said, if someone can connect us to the web team on this one, I 
can send out a fresh, signed list of AMIs to this list. From there, the web 
team can update the page with the new AMI IDs however they see fit.

-- David
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: F21 base AMIs available in both HVM and PV, plus smaller disk size

2015-01-09 Thread David Gay


- Original Message -
 From: Jay Greguske jgreg...@redhat.com
 To: cloud@lists.fedoraproject.org
 Sent: Friday, January 9, 2015 10:17:56 AM
 Subject: Re: F21 base AMIs available in both HVM and PV, plus smaller disk 
 size
 
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 On 01/08/2015 04:20 PM, David Gay wrote:
  Hey nerds,
  
  I've got Fedimg properly registering cloud base images as both HVM
  and PV. (I also added multithreading to the upload process!)
  Previously, base images were only available as PV. Now, base images
  are available in both formats. (Atomic images will never be
  available in PV, as they require HVM).
  
 
 A thread per region? Which regions are you sending to?

There's not a thread per region. Just a thread per upload process. Right now, 
it's just the EC2 HVM AMI creation happening at the same time as the PV-grub 
AMI creation. (In truth, a lot of the process is duplicated, but just running 
one process per AMI type is a quick 'fix' for now.) The image is registered in 
one region, and then a test is run on the created AMI. If the test passes, a 
region-to-region copy is done to all of the other regions. The threading is 
useful even though there are currently only 1-2 processes running 
simultaneously, because the upload processes involve a lot of waiting for 
things to happen on EC2's side.

I hope that made some sense... :P

-- oddshocks

 
  Also, as per a previous thread on this list, I've reduced the disk
  requirement from 12 GB to our minimum, 3 GB.
  
  Attached is a signed text file containing a list of AMIs that were
  just registered today. I used the official F21 x86_64 base cloud
  image that we have as the official download on our website.
  Everything seems to be working for me, but in case I missed
  something, or if you have something to say, please let me know.
  
  -- oddshocks
  
  
  
  ___ cloud mailing list
  cloud@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code
  of Conduct: http://fedoraproject.org/code-of-conduct
  
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.14 (GNU/Linux)
 
 iQEcBAEBAgAGBQJUsBtUAAoJEMzORChHoQ3a9sIH/RLLHZwC/Qx6zen0UvZiMpFq
 ZD4qGNreloYaufD66rvbCpBPE4n7VfJzWyirjfKDAegs5UxdtyHH1TciLu6Doe9g
 iDS0oh3+uwTgybxF8vrhFzc8MFUHrrju5jTxZQdmoBEc0SXzSpuMQgOAlhtO+KXT
 67Dwu2JFNsMu/INW3t0Kpb8IhNRuLGEfwnG/DnCOd4hi2zHztJMA8taFOGn0YsJD
 MRGHylxLOelRC1fRW4nzsreOZ/f3q9xsduGzX+mvrW9AKzBQrcohGEqTQdsyky4S
 XKxwyoZtq2WsjW4po65FEO8FSiU5iIgdW+ehO2cN3OSPC0tzNYEAwDhIihZXT0Q=
 =u9o4
 -END PGP SIGNATURE-
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: EC2 cloud image size

2015-01-08 Thread David Gay
- Original Message -
 From: David Gay d...@redhat.com
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Friday, January 2, 2015 4:46:44 PM
 Subject: Re: EC2 cloud image size
 
 - Original Message -
  From: Dmitry Makovey dmi...@athabascau.ca
  To: Fedora Cloud SIG cloud@lists.fedoraproject.org
  Sent: Friday, January 2, 2015 3:02:20 PM
  Subject: Re: EC2 cloud image size
  
  On 12/17/2014 02:09 PM, David Gay wrote:
   On Tue, Dec 16, 2014 at 03:07:12PM -0700, Dmitry Makovey wrote:
   Does it mean that soon enough we'll see an updated AMI with
   moderate disk demands?
   
   For some value of soon enough, yeah. Sorry about that -- I'm
   checking with David Gay, who wrote the uploader.
   
   Yeah, this was my oversight. Seems the cloud base image is only 425
   MB. I can produce new AMIs right now. Do you think a 1 GB or 500 MB
   drive would be best, or something else?
  
  /gentle/ bump?
  
  Is any help required to get F21 smaller images to AWS? I'd love to
  help (if I can) since I'm interested in the outcome myself.
  
  --
  Dmitry Makovey
  Web Systems Administrator
  Athabasca University
  (780) 675-6245
  ---
  Confidence is what you have before you understand the problem
  Woody Allen
  
  When in trouble when in doubt run in circles scream and shout
   http://www.wordwizard.com/phpbb3/viewtopic.php?f=16t=19330
  
  
  ___
  cloud mailing list
  cloud@lists.fedoraproject.org
  https://admin.fedoraproject.org/mailman/listinfo/cloud
  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
  
 
 Hey -- I actually solved this problem during the holidays. Lowered the size
 to 3 GB as suggested. There just haven't been any new builds that have gone
 through, and I haven't cut a new version just yet anyway (due to the
 holidays). It's no problem for me to send someone a list of fresh AMIs of
 the F21 cloud build with the lowered size tomorrow, if someone can toss them
 on the official website, as well. But yeah, this is all done. Just had to
 tweak two numbers is all.
 
 -- oddshocks
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

Regarding this, I've published a list of new F21 cloud x86_64 base AMIs -- in 
both HVM and PV -- to this list[1]. These AMIs have been registered with our 
minimum size requirement, 3 GB. Much smaller than the previous 12 GB 
registrations. Hopefully, this solves everyone's issues for now. If desired, I 
can send out a list of fresh Atomic AMIs with the lower 3 GB requirement, too. 
That email was mostly an announcement that base images are now available in 
HVM, though.

[1]: https://lists.fedoraproject.org/pipermail/cloud/2015-January/004831.html

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: EC2 cloud image size

2015-01-02 Thread David Gay
- Original Message -
 From: Dmitry Makovey dmi...@athabascau.ca
 To: Fedora Cloud SIG cloud@lists.fedoraproject.org
 Sent: Friday, January 2, 2015 3:02:20 PM
 Subject: Re: EC2 cloud image size
 
 On 12/17/2014 02:09 PM, David Gay wrote:
  On Tue, Dec 16, 2014 at 03:07:12PM -0700, Dmitry Makovey wrote:
  Does it mean that soon enough we'll see an updated AMI with
  moderate disk demands?
  
  For some value of soon enough, yeah. Sorry about that -- I'm
  checking with David Gay, who wrote the uploader.
  
  Yeah, this was my oversight. Seems the cloud base image is only 425
  MB. I can produce new AMIs right now. Do you think a 1 GB or 500 MB
  drive would be best, or something else?
 
 /gentle/ bump?
 
 Is any help required to get F21 smaller images to AWS? I'd love to
 help (if I can) since I'm interested in the outcome myself.
 
 --
 Dmitry Makovey
 Web Systems Administrator
 Athabasca University
 (780) 675-6245
 ---
 Confidence is what you have before you understand the problem
 Woody Allen
 
 When in trouble when in doubt run in circles scream and shout
  http://www.wordwizard.com/phpbb3/viewtopic.php?f=16t=19330
 
 
 ___
 cloud mailing list
 cloud@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/cloud
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 

Hey -- I actually solved this problem during the holidays. Lowered the size to 
3 GB as suggested. There just haven't been any new builds that have gone 
through, and I haven't cut a new version just yet anyway (due to the holidays). 
It's no problem for me to send someone a list of fresh AMIs of the F21 cloud 
build with the lowered size tomorrow, if someone can toss them on the official 
website, as well. But yeah, this is all done. Just had to tweak two numbers is 
all.

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


oddshocks in Raleigh for FAD Dec 3-9

2014-12-04 Thread David Gay
Hi all,

Sorry that I wasn't able to attend the WG meeting yesterday -- I was on a 
flight to Raleigh. I'm at Red Hat Tower for a MirrorManager 2 / Infrastructure 
FAD. I'll be here until the 9th. I should be in IRC as normal for most of the 
time. We hope to do some work on Fedimg during this time, as well.

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: oddshocks in Raleigh for FAD Dec 3-9

2014-12-04 Thread David Gay
 On 12/04/2014 09:38 AM, David Gay wrote:
  Sorry that I wasn't able to attend the WG meeting yesterday -- I was on
  a flight to Raleigh. I'm at Red Hat Tower for a MirrorManager 2 /
  Infrastructure FAD. I'll be here until the 9th. I should be in IRC as
  normal for most of the time. We hope to do some work on Fedimg during
  this time, as well.
 
 What room is this in?
 
 I'm in RDU right now as well.
 
 Best,
 
 jzb

We're in 9S416, just around the corner from the cafe. It's myself, Ralph, 
Pierre, Luke, and also Matt Domsch at the moment. Kevin, Patrick, Paul, and 
Smooge are here for the FAD as well, but they're off doing some datacenter 
stuff until 3 PM.

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


TC4 AMIs now available

2014-11-25 Thread David Gay
TC4 x86_64 base and atomic AMIs are now available in all EC2 regions.

For those of you unaware, I've taken to adding AMI IDs for our purposes on the 
wiki, at https://fedoraproject.org/wiki/Cloud/Images. I figured it was a better 
place than my Fedora People page or personal website. Feel free to message me 
with any questions, comments, or concerns.

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


fresh AMIs for the recent atomic build

2014-11-13 Thread David Gay
Hi all,

I've attached a signed text file containing a list of AMIs for the recent 
Atomic-20141112-21.x86_64 build.

The Koji task for this build can be found here: 
http://koji.fedoraproject.org/koji/taskinfo?taskID=8118904

Please let me know if there are any issues, or further action I can take on 
these builds.

-- David

atomic-20141112-21-amis.txt.sig
Description: PGP signature
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Meeting On Wednesday at 19:00 UTC

2014-11-04 Thread David Gay
 One slight problem I just realized is that Daylight Savings ends on
 November 2nd so this may change some member's availability.

Bit late on this one, but that time works fine for me regardless of the DST 
change. :)

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Both atomic and base F21 beta AMIs available

2014-11-04 Thread David Gay
Good news, everyone!

Both base and atomic AMIs seem to be working properly (x86_64). As per our 
previous discussion, the 32 bit cloud base image needs to be rebuilt due to a 
PAE kernel problem, so that won't be available for now.

robyduck has said that he'll be able to add the AMI IDs to the official page in 
a couple hours, but for now, you can find them on my FedoraPeople page: 
https://oddshocks.fedorapeople.org/

They're public and good to go, so you should be able to boot them and SSH in 
with the username 'fedora'. Let me know if there are any problems!

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: 32 bit AMI registration boot problem: explaination and possible solutions

2014-11-03 Thread David Gay
Andy:

  2.  You cannot have an instance that is both 32 bit architecture and
  EBS-optimized.
 
 EBS-optimized is just a storage performance thing, and has nothing
 to do with whether the image boots.

Yeah, that's fine. What I was saying is simply that there are no instance types 
in EC2 which support both EBS and 32 bit.



Mike:

 The more I think about it - why do we need 32bit AMIs in the first place?
 EC2, Openstack, and company all support 64bit OOTB. Is there an instance
 where you would pick a 32bit cloud instance *over* a 64bit on? I can't
 think of any instances where that would be the case. But then again, I could
 be wrong and it's more common/needed than I know.
 
 If there isn't a clearcut case for 32 bit cloud images, I say we just cut
 them all together.

I'm with you on that. I don't know many people who use 32 bit cloud images. 64 
bit is available for every EC2 instance type, and like you said, other services 
support it. I'm likely not the best person to ask why we provide 32 bit images, 
though. It could be a legacy thing, but it might also be habit.



-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


ostree/atomic composes + MM update

2014-10-23 Thread David Gay
Hey --

An update on progress with the ostree/atomic work:

lmacken has written up a Fedmsg-triggered composer that runs ostree composes 
when repos are updated: https://github.com/fedora-infra/fedmsg-atomic-composer. 
As of our conversation earlier today, it's almost ready for testing in stg. 
We're thinking that we'll use compose01.stg for this purpose temporarily, since 
nothing's running on it at the moment. We'll stand up MM1 there and see if we 
can get it to play with the composer. The idea lmacken suggested is to inject 
the ostree summary data into the yum metadata, pointing repomd.xml at it (using 
modifyrepo). IMO this sounds like a solid plan.

That's about it for now. Another update in a few days.

-- oddshocks
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: Updated Atomic alpha w/Bash update(s)?

2014-09-25 Thread David Gay
 I'm doing a new compose now, and it does have bash-4.3.24-2.fc22.
 (Which, AIUI, may not actually fix everything per
 https://lists.fedoraproject.org/pipermail/test/2014-September/122976.html
 ...but we'll keep the trees flowing)

Hey -- any chance you can send me the Koji IDs for the createImage tasks when 
they're done? Then I can register new AMIs.
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct