no cloud agents: openstack

[dustymabe]

In #12 we decided that we'd like to try to not ship cloud agents. This ticket will document investigation and strategy for shipping without a cloud agent on the openstack cloud platform.

See also #41 for a discussion of how to ship cloud specific bits using ignition.

[dustymabe]

@larsks - we don't think there are any cloud agents required for openstack. Is there any such thing that exists in newer versions of openstack that we are overlooking? We are planning to ship ignition and not cloud-init, so it is also worth asking: "Is there anything specific that cloud-init does that openstack needs?"

Thanks for any input/insight you can help us with.

[cgwalters]

We are planning to ship ignition and not cloud-init

It's important to note here we are also planning to ship coreos-metadata for FCOS, and that takes over some important basic roles from cloud-init today.

[larsks]

In the general sense, OpenStack doesn't particular care about cloud-init.

If you're trying to use something like Heat then there are explicit assumptions there about how your user-data blob will be processed. Other than that, I can't think of anything that would matter. As long as ignition and/or coreos-metadata take care of:

• Resizing the root disk
• Provisioning ssh keys
• Configuring networking
• Running some sort of script specified through the user-data mechanism

Then I think people will be happy, or at least they'll be able to work around any differences.

[dustymabe]

It's important to note here we are also planning to ship coreos-metadata for FCOS, and that takes over some important basic roles from cloud-init today.

yes, thanks for pointing that out

[dustymabe]

Other than that, I can't think of anything that would matter. As long as ignition and/or coreos-metadata take care of:

thanks @larsks !

[dustymabe]

PR to the design document has merged (#117) - closing this.