Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploading to cloud platforms: Azure #148

Open
dustymabe opened this issue Feb 20, 2019 · 14 comments
Open

Uploading to cloud platforms: Azure #148

dustymabe opened this issue Feb 20, 2019 · 14 comments
Labels
cloud* related to public/private clouds jira for syncing to jira

Comments

@dustymabe
Copy link
Member

This is part of #146 and tracks the work/discussion around uploading to Azure.

@dustymabe dustymabe added the cloud* related to public/private clouds label Feb 20, 2019
@bgilbert
Copy link
Contributor

bgilbert commented Mar 14, 2019

I think this involves the following:

  • Create (or identify) an Azure subscription that should host the images.
  • Agree to Azure publishing agreement.
  • Adapt plume for FCOS and update it to use the current Azure Marketplace APIs.
  • Upload FCOS images to Azure CI.
  • Add Azure support to kola.
  • Get whitelisted for Azure EUAP regions and run kola there periodically.

@bgilbert
Copy link
Contributor

@bgilbert
Copy link
Contributor

Generation 2 VMs are in public preview. Among other things, they boot via UEFI. The generation is a property of the image, not the disk; the typical approach is apparently to create two linked images (for each of gens 1 and 2) backed by the same disk. That approach would require coreos/coreos-assembler#334.

@miabbott miabbott added the jira for syncing to jira label Sep 13, 2019
@dustymabe
Copy link
Member Author

We just added Azure images to be output by our build pipeline. We are not uploading to Azure yet, but a user can workaround by uploading the image to their account directly.

@jomeier
Copy link

jomeier commented Dec 15, 2019

Great! I'll try it out today :-)

@jomeier
Copy link

jomeier commented Dec 15, 2019

Looks good. It seems as if the VM needs one (sometimes a few) reboot before it gets Azure DNS servers in /etc/resolv.conf. Don't know where that comes from.

okd-project/okd#13

@LorbusChris
Copy link
Contributor

xref: #361

@LorbusChris
Copy link
Contributor

how can we push this forward?

@dustymabe
Copy link
Member Author

assuming you're talking about uploading directly to Azure:

  • step 1: find a magic wand
  • step 2: wave it

Our hands are tied right now. We need a legal agreement and then accounts created. It's being worked on in the background.

@jomeier
Copy link

jomeier commented Jul 14, 2020

Hi. Any news about that? Will FCOS ever get on the Azure Marketplace?

Azure is the only major Cloud Provider of the "big three" not having FCOS in the Marketplace that's embarassing.

@dustymabe
Copy link
Member Author

No update.

@jomeier
Copy link

jomeier commented Oct 4, 2020

@dustymabe :
Just me regular question: any updates about that ?

@bgilbert
Copy link
Contributor

bgilbert commented Oct 5, 2020

The situation is still as described in #148 (comment). Locking the issue to reduce noise.

@coreos coreos locked and limited conversation to collaborators Oct 5, 2020
@dustymabe
Copy link
Member Author

dustymabe commented Jun 15, 2022

It appears Azure now has a community gallery (preview) that we should be able to use to share images that we create publicly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cloud* related to public/private clouds jira for syncing to jira
Projects
None yet
Development

No branches or pull requests

5 participants