#4250 Need: Account on Fedora's OpenStack to work on Fedora Cloud products
Closed: Fixed None Opened 10 years ago by red.

Being a voting member of the Fedora Cloud WG and effort-leader of the "Docker Host image" Fedora Cloud product, I need access to Fedora's own OpenStack instance to work on our cloud images. I must at least be able to upload and delete images, launch and terminate instances and create and delete snapshots. Access to Horizon would be nice, if available, but is obviously not necessary.

I'd recommend setting up a dedicated Cloud WG / Cloud SIG tenant as likely more people will require such an account in the future.

Thanks,
Sandro


What sort of work do you plan on doing on cloud images?

Testing changes?

Some things to note:

  • Our fedora infrastructure private cloud is not used to actually produce any images. They are all made in koji.

  • Currently we are running folsom and are pretty near capacity. We are going to be adding new hardware hopefully soon and installing a newer version on that.

  • We do have a cloudintern tenant setup, I can ask mattdm if we can just use that for this as well.

How much capacity do you plan on needing? Just single instances to test and quickly terminiated? Or longer running instances to run things?

How much would the cloud sig want/need?

Thanks for any info...

Testing changes and release candidates, yes.

I'm aware the cloud itself doesn't produce images and Folsom is good enough. "Pretty near capacity" isn't very concise but I myself will only just run 3-4 tiny instances in parallel tops. Each 1 VCPU, 512MB RAM and 1 GB Disk should be good enough for my current plans. If disk capacity isn't the bottleneck, 5 GBs could make work more comfortable. Also, I'll obviously need space to upload a few images.

Oftentimes, the instances will only run a few minutes but I'd also want the possibility to leave them running (or at least saved/non-terminated) for a bit longer. That's because I'd like to implement new changes by hand first before putting them into a ks file and building new images. Now, that sometimes can take a while and my available time is limited so I might need to interrupt my work and continue another day. But no instances will be running long-termish (or be seriously critical).

I do think the cloudintern tenant would be fine but mattdm will now better. He will also know better what the Cloud SIG need/want as he pulls most of the strings.

Might as well just add Matt as CC so he can answer some of Kevin's questions (see above) directly.

Can you please mail me a gpg key? I need that to encrypt your password. Thanks.

Just FYI, trac doesn't send any email notices when you only attach something. ;) You have to also add a comment...

Sent access info in email.

Login to comment on this ticket.

Metadata