PHPor 的Blog – 第31页

mac brew HOMEBREW_NO_GITHUB_API

brew install spinx-build 的时候可能会遇到如下错误：

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:353:in `open_http': 422 Unprocessable Entity (GitHub::Error)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:709:in `buffer_open'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:210:in `block in open_loop'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:208:in `catch'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:208:in `open_loop'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:149:in `open_uri'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:689:in `open'
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:30:in `open'
	from /usr/local/Library/Homebrew/utils.rb:367:in `open'
	from /usr/local/Library/Homebrew/utils.rb:397:in `issues_matching'
	from /usr/local/Library/Homebrew/utils.rb:425:in `issues_for_formula'
	from /usr/local/Library/Homebrew/exceptions.rb:145:in `fetch_issues'
	from /usr/local/Library/Homebrew/exceptions.rb:141:in `issues'
	from /usr/local/Library/Homebrew/exceptions.rb:184:in `dump'
	from /usr/local/Library/brew.rb:167:in `rescue in <main>'
	from /usr/local/Library/brew.rb:65:in `<main>'

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:353:in `open_http': 422 Unprocessable Entity (GitHub::Error)

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:709:in `buffer_open'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:210:in `block in open_loop'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:208:in `catch'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:208:in `open_loop'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:149:in `open_uri'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:689:in `open'

from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb:30:in `open'

from /usr/local/Library/Homebrew/utils.rb:367:in `open'

from /usr/local/Library/Homebrew/utils.rb:397:in `issues_matching'

from /usr/local/Library/Homebrew/utils.rb:425:in `issues_for_formula'

from /usr/local/Library/Homebrew/exceptions.rb:145:in `fetch_issues'

from /usr/local/Library/Homebrew/exceptions.rb:141:in `issues'

from /usr/local/Library/Homebrew/exceptions.rb:184:in `dump'

from /usr/local/Library/brew.rb:167:in `rescue in <main>'

from /usr/local/Library/brew.rb:65:in `<main>'

修改 /usr/local/Library/Homebrew/utils.rb 的代码，打印url看看：

https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&amp;per_page=100

1	https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&per_page=100

莫非访问不了api.github.com ？

$ curl "https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&per_page=100"
{
  "message": "Validation Failed",
  "errors": [
    {
      "message": "The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.",
      "resource": "Search",
      "field": "q",
      "code": "invalid"
    }
  ],
  "documentation_url": "https://developer.github.com/v3/search/"
}

$ curl "https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&per_page=100"

{

"message": "Validation Failed",

"errors": [

{

"message": "The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.",

"resource": "Search",

"field": "q",

"code": "invalid"

}

"documentation_url": "https://developer.github.com/v3/search/"

}

看起来是有返回值的，而且是合法的json，继续看 /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb 的代码，发现很可能是httpcode的问题：

curl -v "https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&amp;per_page=100"

1	curl -v "https://api.github.com/search/issues?q=sphinx+repo:Homebrew/homebrew+in:title+state:open&per_page=100"

发现http code为 422 ，而/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb 遇到 422 是走异常逻辑的，如果能简单修改代码使其认为是正常似乎是可以的；但是mac 不让修改/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/open-uri.rb ， root账号也不行

回头看 /usr/local/Library/Homebrew/utils.rb ，发现如下逻辑：

export HOMEBREW_NO_GITHUB_API=1

问题解决

其实 spinx-build 是在生成man page的时候用到的，某些情况下，大可不必非要去生成man page

虚拟机镜像操作

软件包： libguestfs-tools

这里的 guestfish 挺不错的

查看镜像分区及其使用情况：

# virt-df -a centos7.3.raw -h|column -t
文件系统 大小 已用空间 可用空间 使用百分比%
centos7.3.raw:/dev/sda2 497M 147M 350M 30%
centos7.3.raw:/dev/sda5 100M 0 100M 0%
centos7.3.raw:/dev/sda6 42G 2.1G 40G 5%

# virt-df -a centos7.3.raw -h|column -t

文件系统大小已用空间可用空间使用百分比%

centos7.3.raw:/dev/sda2 497M 147M 350M 30%

centos7.3.raw:/dev/sda5 100M 0 100M 0%

centos7.3.raw:/dev/sda6 42G 2.1G 40G 5%

查看镜像中的文件信息

virt-ls -a centos7.3.img -l /

1

virt-ls -a centos7.3.img -l /
copy 文件到镜像

virt-copy-in -a centos7.3.img /tmp/hello.txt /tmp/

1

virt-copy-in -a centos7.3.img /tmp/hello.txt /tmp/
查看镜像中的文件

virt-cat -a centos7.3.img /tmp/hello.txt

1

virt-cat -a centos7.3.img /tmp/hello.txt
查看镜像中的文件系统分区信息： virt-filesystems –long –parts –blkdevs -h -a CentOS-7-x86_64-GenericCloud-1708.raw

virt-resize: –shrink 并不能让镜像文件变的更小（反而变大了）

virt-sparsify 可以使得一个镜像文件变成一个稀疏文件，对于发布、存储镜像很有必要

Building a cloud ready linux image locally using KVM | Ravello Blog

https://blogs.oracle.com/ravello/kvm-for-cloud-linux-image

Refactoring a Dockerfile for Image Size

http://blog.replicated.com/refactoring-a-dockerfile-for-image-size/

1. 尽量减少不必要的包

2. 包管理器自动安装的包不一定都是必须的，可能只是建议安装

resolv.conf 之options都有啥

你没法通过options来禁用ipv6解析
single-request：用来指定分别执行A和AAAA解析；即，收到A记录解析的结果后在发送AAAA记录解析请求；默认情况下，同时在一个连接上发送A和AAAA的解析，这样效率会高一倍；然而，有些dns server不能很好地处理这种请求方式，很可能不能正确地返回AAAA的响应，以至于请求会超时
single-request-reopen：强制A和AAAA的解析在两个连接中处理（主要体现在连接的源端口不同）

参考：

http://man7.org/linux/man-pages/man5/resolv.conf.5.html

openstack 与 ldap的集成

按照下面参考中的做法，添加一个认证的中间件就可以搞定

参考： https://docs.openstack.org/keystone/latest/advanced-topics/external-auth.html

openstack dashboard之session timeout

文档中说在 /etc/openstack-dashboard/local_settings 中修改（或添加）SESSION_TIMEOUT 可以控制dashboard的过期时间，但是修改了怎么也不生效，后看代码发现：

dashboard登录后总是去keystone获取一个token的，token总有过期时间的，所以，dashboard的session过期时间就是自己定义的过期时间和token的过期时间取小的那个。

keystone 的token过期时间配置参考： /etc/keystone/kestone.conf

ceph 之osd 分类（class）

ceph不能自动识别磁盘类型
设置osd分类前osd需要是未分类的，即：修改osd分类的做法是，先移除原有的分类，在添加新的分类：

ceph osd crush rm-device-class ssd osd.5 osd.6 osd.7 ceph osd crush set-device-class ssd osd.5 osd.6 osd.7

1
2

ceph osd crush rm-device-class ssd osd.5 osd.6 osd.7
ceph osd crush set-device-class ssd osd.5 osd.6 osd.7
操作osd分类使用的不是ceph osd crush class *
根据磁盘分类查看osd：

# ceph osd crush class ls [ "hdd", "ssd" ] # ceph osd crush class ls-osd hdd 0 1 2 3 4 # ceph osd crush class ls-osd ssd 5 6 7

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# ceph osd crush class ls
[
"hdd",
"ssd"
]
# ceph osd crush class ls-osd hdd
0
1
2
3
4
# ceph osd crush class ls-osd ssd
5
6
7
然后参考ceph osd crush rule 来创建自己的规则，如只存放在hdd上，或只存放在ssd上的规则，然后对pool设置响应的规则

class 不需要预先创建：

[root@ceph-test-1 mnt]# ceph osd crush rm-device-class osd.1
done removing class of osd(s): 1
[root@ceph-test-1 mnt]# ceph osd crush set-device-class ssd osd.1
set osd(s) 1 to class 'ssd'
[root@ceph-test-1 mnt]# ceph osd crush class ls-osd ssd
1
[root@ceph-test-1 mnt]# ceph osd crush class ls
[
    "hdd",
    "ssd"
]

[root@ceph-test-1 mnt]# ceph osd crush rm-device-class osd.1

done removing class of osd(s): 1

[root@ceph-test-1 mnt]# ceph osd crush set-device-class ssd osd.1

set osd(s) 1 to class 'ssd'

[root@ceph-test-1 mnt]# ceph osd crush class ls-osd ssd

[root@ceph-test-1 mnt]# ceph osd crush class ls

[

"hdd",

"ssd"

]

没有提供一个方法add class ssd，也没看到一个方法可以del class ssd

参考： http://docs.ceph.com/docs/master/rados/operations/crush-map/

Introduction to librados — Ceph Documentation

http://docs.ceph.com/docs/master/rados/api/librados-intro/

通过virsh创建基于lvm的pool

参考：

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-lvm_based_storage_pools#sect-LVM_based_storage_pools-Creating_an_LVM_based_storage_pool_with_virsh

示例：

#virsh
virsh # pool-define-as kvm-pool logical - - /dev/sda6 kvm-pool /dev/kvm-pool
定义池 kvm-pool


virsh # pool-build kvm-pool --overwrite
构建池 kvm-pool

virsh # pool-start kvm-pool
池 kvm-pool 已启动

#virsh

virsh # pool-define-as kvm-pool logical - - /dev/sda6 kvm-pool /dev/kvm-pool

定义池 kvm-pool

virsh # pool-build kvm-pool --overwrite

构建池 kvm-pool

virsh # pool-start kvm-pool

池 kvm-pool 已启动

将一个img 磁盘文件导入kvm-pool (结果总是失败)

创建一个volume：

virsh vol-create-as kvm-pool ceph-3 50g --format raw

1

virsh vol-create-as kvm-pool ceph-3 50g --format raw
导入img文件：

virsh vol-upload --pool kvm-pool ceph-3 ./centos7.3.img

1

virsh vol-upload --pool kvm-pool ceph-3 ./centos7.3.img

总是提示：无法关闭卷ceph-3；然后将无法从ceph-3启动虚拟机
使用新的volume启动虚拟机

成功的做法

定义一个ceph-3.xml

<volume type='block'>
  <name>ceph-3</name>
  <source>
    <device path='/dev/sda6'>
    </device>
  </source>
  <target>
    <path>/dev/kvm-pool/ceph-3</path>
  </target>
</volume>

</device>

</source>

</target>

</volume>

将centos7.3.img 放到 /var/lib/libvirt/images 下面，然后：

virsh vol-create-from --pool kvm-pool --file ceph-3.xml --vol centos7.3.img --inputpool default

1

virsh vol-create-from --pool kvm-pool --file ceph-3.xml --vol centos7.3.img --inputpool default