On 06/18/13 at 09:31am, Bob Ball wrote: >I'm not sure I understand why the user might want to access the disk_config value from within the guest? I have this same feeling. It really has no bearing on the guest once it's running. It's has an effect on API calls and is readily available in that context. > >This seems to be something they could infer from the partition structure - i.e. if the whole drive is partitioned then disk_config was AUTO when the instance was created. > >Bob > >From: Navneet Kumar [mailto:navneetk at thoughtworks.com] >Sent: 18 June 2013 04:52 >To: openstack-dev at lists.openstack.org >Subject: [openstack-dev] Discussion around blueprint https://blueprints.launchpad.net/nova/+spec/add-disk-config-to-xenstore > >Hi, >disk_config has been introduced by the extension 'DiskConfig'( [[http://docs.rackspace.com/openstack-extensions/compute/rax-dcf/content/rax-dcf.pdf]] ) .This extension exposes api to set and retrieve the disk_config values ( either 'MANUAL" or "AUTO' ) .As a user one wants to access the value of disk_config from inside of instance but currently there is no way to get the value of disk_config from inside of instance. >To get any metadata/userdata of the instance a config drive ( [[http://docs.openstack.org/trunk/openstack-compute/admin/content/config-drive.html]] ) can be attached to the instance during boot-up.So disk_drive information can also be included in the config drive. > >Should we include this value in the config drive and xen store as well ? Do you have a use case for this what would help explain why this is useful? > >-- >----------------------------- >Navneet Kumar >Application Developer >Thoughtworks India >Mob: +91 9686577076 > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev