On 11/12/2016 09:31 AM, Akira Yoshiyama wrote:
Hi Stackers,
In TripleO, Ironic provides physical servers for an OpenStack
deployment but we have to configure physical storages manually, or
with any tool, if required. It's better that an OpenStack service
manages physical storages as same as Ironic for servers.
IMO, there are 2 plans to manage physical storages:
When you say "manage physical storage" are you referring to configuring
something like Ceph or GlusterFS or even NFS on a bunch of baremetal
servers?
That isn't a multi-tenant HTTP API service designed for lots of users
but rather a need to automate some mostly one-time storage setup actions.
If so, I think that is more the realm of configuration management
systems like Puppet or Ansible than OpenStack itself.
Best,
-jay
a) extends Ironic
b) creates a new service
Which is better? Any ideas?
Thank you,
Akira
__________________________________________________________________________
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
