Thanks a lot for your sharing, that's good info, just curious why [1] need
zip and base64 encode if my understand is correct
I was told nova need format should be pure vfat or iso9660, I assume it's
because actually the config drive itself is making by iso by default
then wrap a zip/base64 format ... thanks


Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet:
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC

From:   Jim Rollenhagen <>
To:     "OpenStack Development Mailing List (not for usage questions)"
Date:   04/19/2018 12:02 AM
Subject:        Re: [openstack-dev] [Nova] z/VM introducing a new config

On Wed, Apr 18, 2018 at 10:56 AM, Matthew Booth <> wrote:

  > I agree with Mikal that needing more agent behavior than cloud-init
  > a disservice to the users.
  > I feel like we get a lot of "but no, my hypervisor is special!"
  > reasoning when people go to add a driver to nova. So far, I think
  > they're a lot more similar than people think. Ironic is the weirdest
  > we have (IMHO and no offense to the ironic folks) and it can support
  > configdrive properly.

  I was going to ask this. Even if the contents of the disk can't be
  transferred in advance... how does ironic do this? There must be a

I'm not sure if this is a rhetorical question, so I'll just answer it. :)
We basically build the configdrive in nova-compute, then gzip and base64
it, and send it to ironic with the deploy request. On the ironic side, we
unpack it and write it to the end of the boot disk.

// jim
OpenStack Development Mailing List (not for usage questions)

OpenStack Development Mailing List (not for usage questions)

Reply via email to