Re: [openstack-dev] [kolla] Kolla configuration files owner and permission
It indeed makes me frightened when i just stopped at the part of "writable by a group" of configuration files and tried myself to figure out what you guys discussing on IRC. Thanks Steve for making clear about "group of operators". Cheers, Tuan On 08/23/2016 07:29 AM, Steven Dake (stdake) wrote: On 8/22/16, 7:24 PM, "duon...@vn.fujitsu.com" wrote: Hello Kollish, I am working on bp ansible-specific-task-become so I need community opinion about Kolla configuration files owner and permissions. For files in "/var/lib/kolla", it's quite clear that the owner should be 'root' as currently. For files in "/etc/kolla": After discussion with S.Dake on IRC, he recommends /etc/kolla is owned by root and all files in it is 660 (writable by a group). Just to add a bit of clarity, the rationale for this idea is that a group of operators could add themselves to the kolla group on all of the nodes and use their specific ssh keys to operate OpenStack. This is why the group concept in unix was invented 50 odd years ago ;) Regards -steve Anybody has idea about this topic? Best regards, Ha Quang Duong (Mr.) PODC - Fujitsu Vietnam Ltd. __ 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
Re: [openstack-dev] [Nova] Nova compute reports the disk usage
Hi Chris, We have tried to reproduce it in two blades that have the same configs. They are all empty of instance from very beginning. What we see that the scenario happens in one blade, another works as expect. Of course we use qcow image. If i use the below calculation, it can explain the scenario but why it does not happen in the another blade that has the same config? Does it relate to the worst case you mention? (Since there is no instance running before reproducing then i could not find out what worst case happening) - Free_disk = Total(file_system) - Total(actual disk used by instances) - _base directory - Overcommit = Total(virtual size of instances) - Total(actual disk used by instances) - Avai_disk_least = Free_disk - Overcommit Cheers, Tuan On 08/04/2016 05:03 PM, Tuan Luong wrote: Hi Chris, Actually, the system does not belong to us therefore we only had the log file. But it seems reasonable that besides the size of ephemeral diisk in _base, we also have the image of vm downloaded from Glance that consumes the disk capacity. That can make the strange value of disk_over_commit. I will check this situation later. Btw, thank you for your help. Tuan -Original Message- From: Chris Friesen [mailto:chris.frie...@windriver.com] Sent: August 04, 2016 15:57 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Nova compute reports the disk usage On 08/04/2016 02:42 AM, Tuan Luong wrote: Hi Chris, Yes we used qcow image. However I still have something not clear. What I know is that: - disk_available_least = free_disk - disk_over_commit - disk_over_commit = int(virt_size) - physical_disk_size Before launching: - free_disk = 1025 - disk_available_least = 1016 If we use the normal flavor with 600Gb disk and no ephemeral., the result is good with both above value subtract 600Gb. If we use the flavor without disk but 600Gb ephemeral, the result of disk_available_least = -184. Just a thought...did you clear out the _base directory between tests? Or is there maybe an extra backing file sitting there consuming space? Chris __ 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
Re: [openstack-dev] [Nova] Nova compute reports the disk usage
Hi Chris, Actually, the system does not belong to us therefore we only had the log file. But it seems reasonable that besides the size of ephemeral diisk in _base, we also have the image of vm downloaded from Glance that consumes the disk capacity. That can make the strange value of disk_over_commit. I will check this situation later. Btw, thank you for your help. Tuan -Original Message- From: Chris Friesen [mailto:chris.frie...@windriver.com] Sent: August 04, 2016 15:57 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Nova compute reports the disk usage On 08/04/2016 02:42 AM, Tuan Luong wrote: > Hi Chris, > > Yes we used qcow image. However I still have something not clear. What I know > is that: > > - disk_available_least = free_disk - disk_over_commit > - disk_over_commit = int(virt_size) - physical_disk_size > > Before launching: > - free_disk = 1025 > - disk_available_least = 1016 > > If we use the normal flavor with 600Gb disk and no ephemeral., the result is > good with both above value subtract 600Gb. > If we use the flavor without disk but 600Gb ephemeral, the result of > disk_available_least = -184. Just a thought...did you clear out the _base directory between tests? Or is there maybe an extra backing file sitting there consuming space? Chris __ 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
Re: [openstack-dev] [Nova] Nova compute reports the disk usage
Hi Chris, Yes we used qcow image. However I still have something not clear. What I know is that: - disk_available_least = free_disk - disk_over_commit - disk_over_commit = int(virt_size) - physical_disk_size Before launching: - free_disk = 1025 - disk_available_least = 1016 If we use the normal flavor with 600Gb disk and no ephemeral., the result is good with both above value subtract 600Gb. If we use the flavor without disk but 600Gb ephemeral, the result of disk_available_least = -184. The value of free_disk is still good with 425Gb. In this case, it seems that the value of disk_over_commit is 609Gb that is calculated from virt_size and physical_disk_size. What I think is the virt_size here is 600Gb and physical_disk_size is couple of Gb. How can the value 609Gb appear? I agree that the backing_file of ephemeral_disk is sparse and 600Gb. Best, Tuan -Original Message- From: Chris Friesen [mailto:chris.frie...@windriver.com] Sent: August 03, 2016 18:34 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Nova compute reports the disk usage On 08/03/2016 09:13 AM, Tuan Luong wrote: > Hi Jay, Thank you for the reply. Actually, I did ask this question to > make sure that everything is still going well with disk usage report > of Nova. We had the problem related to wrong report (IMHO it is > wrong). The situation is > below: > > - We launch an instance with 600Gb of ephemeral disk of flavor without > specifying extra ephemeral disk. The total free_disk before launching > is 1025Gb, the total disk_available_least is 1016Gb. - After > successful launching, what we have is the value of disk_available_disk > = -184Gb therefore we could not launch the next instance. > > It seems like the value of disk_available_disk decreases 2*600Gb when > I think it should be 600Gb. The value of free_disk after launching is > calculated well. I would not believe that the disk_over_commit in this case > is 600Gb. > Otherwise, we also check the instance that indeed it has only 600Gb > mounted as vdb. Assuming you're using qcow, the maximum disk space consumed by a qcow disk is "size of backing file" + "size of differences from backing file". Thus, if you have a single instance using a given backing file, the worst-case consumption is actually twice the size of your disk. I think the backing file for an ephemeral disk is actually a sparse file, but on a cursory examination it will appear to be consuming 600GB. Chris __ 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
Re: [openstack-dev] [Nova] Nova compute reports the disk usage
Hi Jay, Thank you for the reply. Actually, I did ask this question to make sure that everything is still going well with disk usage report of Nova. We had the problem related to wrong report (IMHO it is wrong). The situation is below: - We launch an instance with 600Gb of ephemeral disk of flavor without specifying extra ephemeral disk. The total free_disk before launching is 1025Gb, the total disk_available_least is 1016Gb. - After successful launching, what we have is the value of disk_available_disk = -184Gb therefore we could not launch the next instance. It seems like the value of disk_available_disk decreases 2*600Gb when I think it should be 600Gb. The value of free_disk after launching is calculated well. I would not believe that the disk_over_commit in this case is 600Gb. Otherwise, we also check the instance that indeed it has only 600Gb mounted as vdb. Best, Tuan -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: August 03, 2016 14:53 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova] Nova compute reports the disk usage On 08/03/2016 04:35 AM, Tuan Luong wrote: > Hi, > > When we try to add ephemeral disk in booting instance, as we know that > it will create disk.local and the backing file in _/base. Both of them > are referred to the ephemeral disk. When nova reports the disk usage > of compute, does it count both of them for the used disk? What I see > in the resource/_tracker that it calculates the instance['ephemeral_gb']. The resource tracker reports disk usage by adding up the root_gb + ephemeral_gb values of the *flavor* attribute of the instances assigned to that compute node. Does that answer your question? Best, -jay __ 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-dev] [Nova] Nova compute reports the disk usage
Hi, When we try to add ephemeral disk in booting instance, as we know that it will create disk.local and the backing file in _base. Both of them are referred to the ephemeral disk. When nova reports the disk usage of compute, does it count both of them for the used disk? What I see in the resource_tracker that it calculates the instance['ephemeral_gb']. Tuan __ 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
