這是擬真電腦動畫所必備的元件.
我已修改這裡的人形布偶, 讓它手腳僵硬 並加入手掌與大腳板.
希望它能站立,事實上很不容易, 需要加入平衡控制.
還有一大段路要走呢.
Chao-Yih Hsia (Mark Hsia) Founder of the CubicPower.idv.tw site. Focuses on animation, streaming data, big data engine and applications development. Twitter: Mark Hsia @HsiaMark
小雀說: | ||
小雀從筆記中找到, 有關作業員的職務重點有: 加班, 包裝, 作業, 操作, 配合, 生產, 時間, 產品, 內容, 經驗, ..等
|
小雀說: | ||
小雀從筆記中本看到,作業員的熱門區域有: 桃園縣龜山鄉, 桃園縣中壢市, 新北市中和區, 桃園縣蘆竹鄉, 新北市樹林區, ..等
|
小雀說: | ||
小雀從筆記中本看到,作業員的熱門城市有: 新北市, 桃園縣, 台中市, 台南市, 高雄市, ..等
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# yum install openstack-keystone python-keystoneclient
keystone
. Replace KEYSTONE_DBPASS
with a suitable password for the database user.# openstack-config --set /etc/keystone/keystone.conf \ database connection mysql://keystone:KEYSTONE_DBPASS
@controller
/keystone
keystone
database user:$ mysql -u root -p mysql> CREATE DATABASE keystone; mysql> GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'localhost' \ IDENTIFIED BY 'KEYSTONE_DBPASS
'; mysql> GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' \ IDENTIFIED BY 'KEYSTONE_DBPASS
'; mysql> exit
# su -s /bin/sh -c "keystone-manage db_sync" keystone
# ADMIN_TOKEN=$(openssl rand -hex 10) # echo $ADMIN_TOKEN # openstack-config --set /etc/keystone/keystone.conf DEFAULT \ admin_token $ADMIN_TOKEN
ADMIN_TOKEN.
# keystone-manage pki_setup --keystone-user keystone --keystone-group keystone # chown -R keystone:keystone /etc/keystone/ssl # chmod -R o-rwx /etc/keystone/ssl
# service openstack-keystone start # chkconfig openstack-keystone on
cron
to purge expired tokens hourly./var/log/keystone/keystone-tokenflush.log
:# (crontab -l 2>&1 | grep -q token_flush) || \ echo '@hourly /usr/bin/keystone-manage token_flush >/var/log/keystone/keystone-tokenflush.log 2>&1' >> /var/spool/cron/root
--os-token
option to the keystone command or set the OS_SERVICE_TOKEN
environment variable. Set OS_SERVICE_TOKEN
, as well as OS_SERVICE_ENDPOINT
to specify where the Identity Service is running. Replace ADMIN_TOKEN
with your authorization token.$ export OS_SERVICE_TOKEN=ADMIN_TOKEN
$ export OS_SERVICE_ENDPOINT=http://controller:35357/v2.0
_member_
role. The OpenStack dashboard automatically grants access to users with this role. You will give the admin
user access to this role in addition to the admin
role.Note | |
---|---|
Any role that you create must map to roles specified in the policy.json file included with each OpenStack service. The default policy file for most services grants administrative access to the admin role. |
admin
user:$ keystone user-create --name=admin --pass=ReplaceADMIN_PASS
--email=ADMIN_EMAIL
ADMIN_PASS
with a secure password and replace ADMIN_EMAIL
with an email address to associate with the account.ADMIN_PASS
就可以,記住這密碼.
admin
role:$ keystone role-create --name=admin
admin
tenant:$ keystone tenant-create --name=admin --description="Admin Tenant"
admin
user, admin
role, and admin
tenant together using the user-role-add
option:$ keystone user-role-add --user=admin --tenant=admin --role=admin
admin
user, _member_
role, and admin
tenant:$ keystone user-role-add --user=admin --role=_member_ --tenant=admin
_member_
role. You will use this account for daily non-administrative interaction with the OpenStack cloud. You can also repeat this procedure to create additional cloud users with different usernames and passwords. Skip the tenant creation step when creating these users.demo
user:$ keystone user-create --name=demo --pass=ReplaceDEMO_PASS
--email=DEMO_EMAIL
DEMO_PASS
with a secure password and replace DEMO_EMAIL
with an email address to associate with the account.DEMO
_PASS
就可以,記住這密碼.
demo
tenant:$ keystone tenant-create --name=demo --description="Demo Tenant"
Note | |
---|---|
Do not repeat this step when adding additional users. |
demo
user, _member_
role, and demo
tenant:$ keystone user-role-add --user=demo --role=_member_ --tenant=demo
service
tenantservice
.service
tenant:$ keystone tenant-create --name=service --description="Service Tenant"
OS_SERVICE_TOKEN
environment variable, as set previously, for authentication.$ keystone service-create --name=keystone --type=identity \ --description="OpenStack Identity" +-------------+----------------------------------+ | Property | Value | +-------------+----------------------------------+ | description | OpenStack Identity | | id | 15c11a23667e427e91bc31335b45f4bd | | name | keystone | | type | identity | +-------------+----------------------------------+The service ID is randomly generated and is different from the one shown here.
controller
host name is used. Note that the Identity Service uses a different port for the admin API.$ keystone endpoint-create \ --service-id=$(keystone service-list | awk '/ identity / {print $2}') \ --publicurl=http://controller
:5000/v2.0 \ --internalurl=http://controller
:5000/v2.0 \ --adminurl=http://controller
:35357/v2.0 +-------------+-----------------------------------+ | Property | Value | +-------------+-----------------------------------+ | adminurl | http://controller:35357/v2.0 | | id | 11f9c625a3b94a3f8e66bf4e5de2679f | | internalurl | http://controller:5000/v2.0 | | publicurl | http://controller:5000/v2.0 | | region | regionOne | | service_id | 15c11a23667e427e91bc31335b45f4bd | +-------------+-----------------------------------+
Note | |
---|---|
You will need to create an additional endpoint for each service added to your OpenStack environment. The sections of this guide associated with the installation of each service include the endpoint creation step specific to the service. |
OS_SERVICE_TOKEN
and OS_SERVICE_ENDPOINT
environment variables:$ unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINTThese variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed.
admin
user and the password you chose for that user:$ keystone --os-username=admin --os-password=ADMIN_PASS
\
--os-auth-url=http://controller:35357/v2.0 token-get
In response, you receive a token paired with your user ID. This verifies that the Identity Service is running on the expected endpoint and that your user account is established with the expected credentials.$ keystone --os-username=admin --os-password=ADMIN_PASS
\
--os-tenant-name=admin --os-auth-url=http://controller:35357/v2.0 \
token-get
In response, you receive a token that includes the ID of the tenant that you specified. This verifies that your user account has an explicitly defined role on the specified tenant and the tenant exists as expected.--os-*
variables in your environment to simplify command-line usage. Set up a admin-openrc.sh
file with the admin credentials and admin endpoint:
1
2
3
4
|
export OS_USERNAME=admin export OS_PASSWORD=ADMIN_PASS export OS_TENANT_NAME=admin export OS_AUTH_URL=http: //controller :35357 /v2 .0 |
$ source admin-openrc.sh
admin-openrc.sh
file is configured correctly. Run the same command without the --os-*
arguments:$ keystone token-getThe command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly.
$ keystone user-list +----------------------------------+-------+---------+-------------------+ | id | name | enabled | email | +----------------------------------+-------+---------+-------------------+ | afea5bde3be9413dbd60e479fddf9228 | admin | True | admin@example.com | | 32aca1f9a47540c29d6988091f76c934 | demo | True | demo@example.com | +----------------------------------+-------+---------+-------------------+
$ keystone user-role-list --user admin --tenant admin +----------------------------------+----------+----------------------------------+----------------------------------+ | id | name | user_id | tenant_id | +----------------------------------+----------+----------------------------------+----------------------------------+ | 9fe2ff9ee4384b1894a90878d3e92bab | _member_ | afea5bde3be9413dbd60e479fddf9228 | e519b772cb43474582fa303da62559e5 | | 5d3b60b66f1f438b80eaae41a77b5951 | admin | afea5bde3be9413dbd60e479fddf9228 | e519b772cb43474582fa303da62559e5 | +----------------------------------+----------+----------------------------------+----------------------------------+Seeing that the
id
in the output from the keystone user-list command matches the user_id
in the keystone user-role-list command, and that the admin role is listed for that user, for the related tenant, this verifies that your user account has the admin
role, which matches the role used in the Identity Service policy.json
file.SERVICE_PASS
is the password to access the service SERVICE
and SERVICE_DBPASS
is the database password used by the service SERVICE to access the database.Password name | Description |
---|---|
Database password (no variable used) | Root password for the database |
|
Database password of Identity service |
|
Password of user demo |
|
Password of user admin |
|
Database password for Image Service |
|
Password of Image Service user glance |
|
Database password for Compute service |
|
Password of Compute service user nova |
|
Database password for the dashboard |
|
Database password for the Block Storage service |
|
Password of Block Storage service user cinder |
|
Database password for the Networking service |
|
Password of Networking service user neutron |
|
Database password for the Orchestration service |
|
Password of Orchestration service user heat |
|
Database password for the Telemetry service |
|
Password of Telemetry service user ceilometer |
|
Database password of Database service |
|
Password of Database Service user trove |
# yum install mysql mysql-server MySQL-pythonThe MySQL configuration requires some changes to work with OpenStack.
/etc/my.cnf
file: 編輯此檔[mysqld]
section, set the bind-address
key to the management IP address of the controller node to enable access by other nodes via the management network:[mysqld] ... bind-address = 10.0.0.11
[mysqld]
section, set the following keys to enable InnoDB, UTF-8 character set, and UTF-8 collation by default:[mysqld] ... default-storage-engine = innodb collation-server = utf8_general_ci init-connect = 'SET NAMES utf8' character-set-server = utf8
# service mysqld start # chkconfig mysqld onFinally, you should set a root password for your MySQL database. The OpenStack programs that set up databases and tables prompt you for this password if it is set.
# mysql_install_db # mysql_secure_installationIf you have not already set a root database password, press ENTER when you are prompted for the password. This command presents a number of options for you to secure your database installation. Respond
yes
to all prompts unless you have a good reason to do otherwise.# yum install MySQL-python
OpenStack packages
# yum install qpid-cpp-server
INTERFACE_NAME
with the actual interface name. For example, eth2 or ens256./etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME
file to contain the following:HWADDR
and UUID
keys.DEVICE=INTERFACE_NAME
TYPE=Ethernet
ONBOOT="yes"
BOOTPROTO="none"
# service network restart
/etc/hosts
file to contain the following:# network 10.0.0.21 network # controller 10.0.0.11 controller # compute1 10.0.0.31 compute1
Note | |
---|---|
Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on. |
Note | |
---|---|
Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on. |
/etc/hosts
file to contain the following:# compute1 10.0.0.31 compute1 # controller 10.0.0.11 controller # network 10.0.0.21 network
# ping -c 4 openstack.org PING openstack.org (174.143.194.225) 56(84) bytes of data. 64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
# ping -c 4 network
PING network (10.0.0.21) 56(84) bytes of data.
64 bytes from network (10.0.0.21): icmp_seq=1 ttl=64 time=0.263 ms
# ping -c 4 compute1
PING compute1 (10.0.0.31) 56(84) bytes of data.
64 bytes from compute1 (10.0.0.31): icmp_seq=1 ttl=64 time=0.263 ms
# ping -c 4 openstack.org PING openstack.org (174.143.194.225) 56(84) bytes of data. 64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
# ping -c 4 controller
PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
# ping -c 4 10.0.1.31 PING 10.0.1.31 (10.0.1.31) 56(84) bytes of data. 64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=1 ttl=64 time=0.263 ms
# ping -c 4 openstack.org PING openstack.org (174.143.194.225) 56(84) bytes of data. 64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
# ping -c 4 controller
PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
# ping -c 4 10.0.1.21 PING 10.0.1.21 (10.0.1.21) 56(84) bytes of data. 64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=1 ttl=64 time=0.263 ms
小雀說: | ||
小雀從筆記中找到, 有關國內業務的職務重點有: 客戶, 業務, 開發, 產品, 銷售, 服務, 顧客, 經驗, 處理, 推廣, ..等
|
小雀說: | ||
小雀從筆記中本看到,國內業務的熱門區域有: 台北市中山區, 台北市內湖區, 台中市西屯區, 桃園縣桃園市, 新北市中和區, ..等
|
小雀說: | ||
小雀從筆記中本看到,國內業務的熱門城市有: 台北市, 新北市, 台中市, 桃園縣, 高雄市, ..等
|
小雀說: | ||
挑一個工作吧!
|
小雀說: | ||
小雀從筆記中找到, 有關半導體的職務重點有: 產品, 開發, 分析, 客戶, 設備, 製程, 執行, 技術, 改善, 設計, ..等
|
小雀說: | ||
小雀從筆記中本看到,半導體的熱門城市有: 新竹市, 台南市, 新竹縣, 台中市, 新北市, ..等
|
小雀說: | ||
小雀從筆記中本看到,半導體的熱門區域有: 新竹市, 台南市新市區, 新竹縣竹北市, 台中市潭子區, 新北市新店區, ..等
|
小雀說: | ||
想要指定資料來源嗎?
|
小雀說: | ||
可以Google 一下了!
|