Comments (10)
Allegedly -- and I've asked for documentation -- but AzureStack does not support the instance meta-data service.
from afterburn.
Allegedly -- and I've asked for documentation -- but AzureStack does not support the instance meta-data service.
got the documentation for you https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-vm-considerations?view=azs-2002
Azure Instance Metadata Service | The Azure Instance Metadata Service provides info about running VM instances that can be used to manage and set up your VM. | The Azure Instance Metadata Service isn't supported on Azure Stack Hub.
from afterburn.
As it turns out, we need to implement check-in support. FCOS will boot, but it will NOT check-in and get a hostname.
from afterburn.
Since this AzureStack and its not a supported variant (AFAIK), I'm calling this a feature request and NOT a bug. Unless other victim are eager to work on this, I'd like to volunteer myself.
Work on this is tenatively scheduled for the 4.7 OCP cycle.
from afterburn.
/cc @cfBrianMiller
from afterburn.
option private_245 => 'a8:3f:81:10'
This in fact 168.63.129.16
. So, bad that we don't have #146 but good that the fallback worked there too.
http://169.254.169.254/metadata/instance/compute/name?api-version=2017-08-01&format=text
According to coreos/fedora-coreos-tracker#476 (comment) the problem is with the API version. Which is weird because the (Azure) platform docs at https://docs.microsoft.com/en-us/azure/virtual-machines/windows/instance-metadata-service#versioning explicitly mention the version we are using. See https://docs.microsoft.com/en-us/azure-stack/user/azure-stack-vm-considerations?view=azs-2002#api-versions on API versions for AzureStack.
Going a bit further, the hostname is the simplest logic on Azure, so it's concerning that already this one fails on AzureStack. How do SSH keys logic and boot check-in logic behave on such platform?
from afterburn.
Which then makes me wonder, where does an AzureStack instance get its hostname? Is that in the DHCP options?
from afterburn.
Now that Ignition [1] treats Azure Stack as a separate platform, we might have "just enough" to get FCOS/RHCOS booted on Azure{Stack,Hub} [1a, 1b]. The provided OVF from Microsoft looks suspect to me; the XML looks like its describing a Windows instance. Regardless the OVF XML given to us for AzureStack deviates substantially from what we know exists on Azure.
I started a stub [3], but after looking FCOS [4] packaging and RHCOS's previous failure to boot (caused by Afterburn checking in as if it was on AzureStack) is really superfluous.
The next steps are:
- Confirm that the OVF provided by MS is, in fact, from a Linux VM
- Attempt to boot RHCOS 4.6 or FCOS and see what happens
[1] https://github.com/coreos/ignition/blob/master/internal/providers/azurestack/azurestack.go
[1a] caveat emptor: this has not been tested on Azure Stack
[1b] caveat emptor: "just enough" is assumed to mean basic function means booting to a console. No Afterburn support. Remote access would be dependant on SSH keys provided by Ignition. Node is likely unusable beyond a POC.
[2] #463 (comment)
[3] 40f00e8
[4] https://src.fedoraproject.org/rpms/rust-afterburn/blob/master/f/rust-afterburn.spec#_49-53 uses the defaults set in
https://github.com/coreos/afterburn/blob/master/systemd/afterburn-checkin.service which would not apply to AzureStack
from afterburn.
from afterburn.
Done in #561
from afterburn.
Related Issues (20)
- Release 5.0.0 HOT 1
- Release 5.1.0 HOT 1
- afterburn writes authorized keys even when it gets a 404 from openstack metadata service
- 30s delay on Azure boot: "Failed to get fabric address from DHCP" HOT 1
- Release 5.2.0 HOT 2
- systemd: excessive Requires/After can result in dependency failure HOT 2
- Test `providers::aws::mock_tests::test_aws_basic` is flaky HOT 2
- Test `providers::aws::mock_tests::test_aws_imds_versions` is flaky HOT 3
- Support IPv6 on AWS HOT 1
- Release 5.3.0 HOT 3
- afterburn-sshkeys fails if no ssh key in metadata on ibmcloud HOT 1
- Consider switching argument parsing to `clap_derive`
- Consolidate CloudStack metadata providers
- Consider enabling hostname service on subsequent boots
- Release Afterburn 5.4.0 HOT 2
- Release Afterburn 5.4.1 HOT 1
- configure user account based on azure provider specific information HOT 1
- Release Afterburn 5.4.2 HOT 7
- Afterburn reports incorrect OpenStack instance id HOT 2
- Release Afterburn 5.4.3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from afterburn.