Samuel, I cases like glance, and nova, you will likely want the volumes still because they are still used in some cases as cache(glance), operational files(nova-compute), or even interim storage(nova-compute) of snapshots. We keep them around even when we use Ceph.
In the case of cinder, I'm assuming you mean the cinder vg created from the cinder storage role. You should not need to deploy this role as it's only necessary for lvm/iSCSI which it sounds like you are replacing. Finally, if you truly don't want the allocations you would have to remove them from the base releases data [1], As Evgeniy noted the role api won't do this for you, you would have to update this using the release API or by replacing the base data that is loaded from [1] as fuel initalizes. [1] https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L243-355 On Wed, May 27, 2015 at 1:27 AM Evgeniy L <e...@mirantis.com> wrote: > Hi Samuel, > > Currently it's not possible to change partitioning schema of Fuel roles, > but you can change partitioning in post_deployment tasks of your plugin. > > Thanks, > > On Wed, May 27, 2015 at 9:38 AM, Samuel Bartel < > samuel.bartel....@gmail.com> wrote: > >> Hi folks >> >> In some plugin such as the nfs for glance or nova and the netapp for >> cinder, we have replaced the lvm by nfs mount point. However we still have >> partition setup for glance, cinder, nova which are not used anymore. >> we can still int the disk configure allocate the minimum space to these >> partitions. but is it possible in the plugin to chache the disk >> configuration in order to reallocate thiese partition to a different used? >> >> regards >> >> Samuel >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
