Open Stack

Hi Davide,

➜  ~ cinder --version
1.9.0
➜  ~ cinder help | grep type-access
    type-access-add     Adds volume type access for the given project.
    type-access-list    Print access information about the given volume type.
    type-access-remove  Removes volume type access for the given project.

Can you check at your side?

Thanks,
Mohammed

On Tue, Nov 15, 2016 at 11:10 AM, Davide Panarese <dpanarese at enter.eu> wrote:
> Hi Mohammed,
> thanks for your explanation.
>
> But this commands are provided only from openstack client. I haven’t in
> cinder client.
>
> thanks
> Davide
>
> On 15 Nov 2016, at 16:21, Mohammed Naser <mnaser at vexxhost.com> wrote:
>
> is_public controls if it's public or not
> volume_type_projects controls which projects can access a specific flavor
>
> The cinder commands which are of your interest:
>
>    type-access-add     Adds volume type access for the given project.
>    type-access-list    Print access information about the given volume type.
>    type-access-remove  Removes volume type access for the given project.
>    type-create         Creates a volume type.
>
> Good luck!
>
> On Tue, Nov 15, 2016 at 10:03 AM, Davide Panarese <dpanarese at enter.eu>
> wrote:
>
> Hello,
> anyone of us have tried private volume types? How are they work?
> I know that were introduced from Kilo release and you can use with Cinder
> API v2.
>
> But who can define these? Just admins i guess, right? In API command you can
> choose only if is public or not and not the owner.
> In DB schema i don’t find anything about that:
>
> CREATE TABLE `volume_types` (
>    `created_at` datetime DEFAULT NULL,
>    `updated_at` datetime DEFAULT NULL,
>    `deleted_at` datetime DEFAULT NULL,
>    `deleted` tinyint(1) DEFAULT NULL,
>    `id` varchar(36) NOT NULL,
>    `name` varchar(255) DEFAULT NULL,
>    `qos_specs_id` varchar(36) DEFAULT NULL,
>    `is_public` tinyint(1) DEFAULT NULL,
>    `description` varchar(255) DEFAULT NULL,
>    PRIMARY KEY (`id`),
>    KEY `qos_specs_id` (`qos_specs_id`),
>    CONSTRAINT `volume_types_ibfk_1` FOREIGN KEY (`qos_specs_id`) REFERENCES
> `quality_of_service_specs` (`id`)
> ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
>
> Do i need Keystone v3 with RBAC to define who can use a specific volume
> type?
>
> Thanks for your help.
> Davide
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
>
> --
> Mohammed Naser — vexxhost
> -----------------------------------------------------
> D. 514-316-8872
> D. 800-910-1726 ext. 200
> E. mnaser at vexxhost.com
> W. http://vexxhost.com
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non
> infetto.
> Seguire il link qui sotto per segnalarlo come spam:
> http://mx01.enter.it/cgi-bin/learn-msg.cgi?id=F1D1F401F0.A96C6
>
>



-- 
Mohammed Naser — vexxhost
-----------------------------------------------------
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mnaser at vexxhost.com
W. http://vexxhost.com