[Docker] Nutanix容器卷插件

\n
\nHowever, I did notice that this looks to be redhat tested only. Is there a Ubuntu version of this? Do we know if there is one in the works?In my company we are heavy docker users, but we use Ubuntu as the base, so it would be wonderful to try that.","quoteUsername":"Justin-DynamicD","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

@tperelle<\/user-mention> @aluciani<\/user-mention> on CentOS. At first I used the docker version that comes with the distribution and docker complained about an unknown -console options. So I switched to docker repo and now I keep getting \/run\/docker\/plugins\/...\/nutanix.sock no such file or directory","quoteUsername":"sks","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

@tperelle<\/user-mention> @sks<\/user-mention> @Justin-DynamicD<\/user-mention> - Best to share your experiences here in the forums. I'll ping the team and see what we can do to help here. Thanks","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

\r\n
\r\nFor those just finding this thread We have implemented this in our corp services division and leverage it in conjunction with Docker + Nomad to provide a complete container solution that runs very well.
\r\n
\r\nEssentially we can declare the storage requirements in our nomad storage stanza, and the requested volume will be mounted if present, and created if missing. We then use the data protection feature to snapshot the data volumes so that we have a complete backup solution that works with containers. Pretty elegant all in all!","quoteUsername":"Justin-DynamicD","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

@smoodo<\/user-mention> I will pass this along to the team and see if I can get you an answer.","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

@aluciani<\/user-mention> Thank you for responding. We have one open #00338948. I am happy to contribute findings back to the community. The prospects of having this working are exciting.","quoteUsername":"smoodo","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

\r\n
\r\nBasics:
\r\niSCSI initiator tools that you can see in Centos (iscsi-initiator-utils) and Ubuntu (open-iscsi)
\r\nhttps:\/\/store.docker.com\/plugins\/nutanix-dvp-docker-volume-plug-in
\r\n
\r\nWhat those instructions do not tell you is the following.
\r\nYou will need to get the initiator id out of your CentOS or Ubuntu and add it to a Nutanix Volume Group as 'clients'. The Nutanix Volume Group does not have to have disks. I think this is because Nutanix needed a way to know that the VM's are allowed access to the iSCSI targets that get created through 'docker volume create' stanzas. On my system if I did not have the iqn added to a Volume Group, the docker_volume_plugin would create volumes and disks in those volumes, but they would not be usable by containers running within the VM. iSCSI would report that the disk could not be found. You could, in fact, see it within the Nutanix Storage section. The initiator id on my CentOS 7 system ended up within \/etc\/iscsi\/initiatorname.iscsi and looked like iqn.1994-05.com.redhat:cefadfb997de the one for Ubuntu was in the same place but looked like iqn.1993-08.org.debian:01:70a35537367
\r\n
\r\nAnother stumbling block was accidentally typing the password wrong and in another iteration trying a Nutanix Volume Group name for the 'DEFAULT_CONTAINER' parameter, which should have been the Nutanix Storage Container name. In all cases of getting something wrong, the only error you will get is about the nutanix.sock file not being found. I have not found a way to change an already installed plugin's configuration. Doing a 'docker plugin rm nutanix' was sufficient and then I reran the docker plugin install line.
\r\n
\r\nA small detail on the plugin install line is the \"--alias nutanix\" part. That is from docker, and allows you to use the \"--driver nutanix\" versus the more verbose \"--driver ntnx\/nutanix_volume_plugin:1.1.1\".
\r\n
\r\nThese issues were hard to resolve because various sets of instructions left out details or the labs or tutorials assumed perfection. Another helpful tidbit came from a Nutanix Tech video locked within a series about improvements (so you have to wade through the whole series) where they explain that the docker volume plugin is essentially using the REST calls to orchestrate creating and destorying volumes used with Docker. Perhaps that should have been more obvious in hindsight, but knowing that told me how to think about what could go wrong with the plugin. (Password changes, port 443 problems, iscsi issues).
\r\n
\r\nIt looks like there will be some lasting burdens from the configuration:
\r\nThe DATASERVICES_IP is an IP that is accessible in the IP Range of the Nutanix Cluster. Said in a fancier way 'in the same subnet'. There is nothing mysterious about it, but once you set it and start to configure things to expect it, you will have to own all of those configuration changes down the line. Password changes will probably not be elegant either, so a service account might be appropriate for production.
\r\n
\r\nMy production use cases will be multi-docker-container clustered databases and clustered application specific repositories. We will likely try the orchestration on Kubernetes next, but first some experimentation with docker swarm and stacks.","quoteUsername":"smoodo","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

• 喜欢
• 引用

• 喜欢
• 引用