Chao-Yih Hsia: The way it works

2014-06-26

今天王宇佐在溫布頓網球賽拍倒俄羅斯名將尤茲尼，首次闖進第3輪。

我們看看去年的今天看看的今天發生了什麼事:

CubicPower 歷史印象20130626

王宇佐.歐斯尼克.選手.二輪.小時.以後.晉級.第十局.

台將3連勝王宇佐5盤戰晉級溫網第二輪- 中時電子報

2013年6月26日 - 接續謝淑薇、盧彥勳之後，王宇佐昨晚經歷五盤大戰，最後險勝對手，成為 ... 訪問時說，今天他和對手的表現都很好，上場前他就很清楚奧迪斯尼克的優缺點，對他的打法並不驚訝，從一開始到結束，他都按照自己的方式打球，沒有因 ... 賽末點時自己些微落後也沒有緊張，「沒有放棄，一直堅持下去，是今天獲勝的關鍵」。

盧彥勳.莫瑞.英國.球場.今天.比賽.加油.好手.自己.表現.冠軍.拿下.溫網.壓力.擊敗.

對戰莫瑞盧彥勳：拼戰到底- 中時電子報

www.chinatimes.com › 即時新聞 › 中央社 › 體育

2013年6月25日 - 台灣網球好手盧彥勳今天在溫布頓網球賽順利取得第1勝後，26日將與 ... 溫網擊敗美國好手羅迪克（Andy Roddick），打進8強，在草地球場表現很好，「所以我需要做一些準備」。 盧彥勳被問到將迎戰莫瑞的比賽時說，「這將是一場很艱難的比賽」， ... 莫瑞仗著地主球星優勢，背負拿下英國77年來溫網第1個冠軍的壓力， ...

歷史印象目錄

前日 次日

航空.廉價.機場.國際.公司.民航.門檻.設立.

東北.野生.野獸.發現.

連坐.行政.長官.討論.酒駕.處分.人員.軍公教.富源.會議.人事.直屬.表示.部分.嚴厲.

律法.伊斯蘭教.麥當勞.餐點.伯恩.符合.分店.迪爾.美元.不合.消費.連鎖.

麥當勞.公司.王女.盧小慧.人員.右昌店.用餐.服務.致歉.處理.營運.

股東.股利.鴻海.通過.

股東.阿土伯.建議.鴻海.股利.郭董.出席.加碼.現場.支持.代表.今天.加發.投資.郭台銘.電視.

鴻海.集團.計畫.航空.郭台銘.可以.股東.獨立.分拆.出去.它們.母艦.金雞.戰鬥.競爭.

談判.郭台銘.我們.股東.繼續.不急.他們.的是.時間.無奈.對象.鴻夏戀.鴻海.

高鐵.台灣.列車.成長.人次.去年.旅客.

高捷.營運.市府.公司.表示.陳存永.增資.

工讀.勞工.家庭.報名.面試.職缺.370個.5日.子女.名額.相關.重建.高市.暑假.暑期.學子.

運動.體育.教育.產業.白皮書.健康.國際.競技.10年.未來.全民.政策.提升.發展.優質.

燕鷗.馬祖.生態.馬管處.

銀行.香港.大陸.中國.公司.貸款.穆迪.有限.恆生.這些.增加.聲明.

食品.添加.登錄.業者.衛生.今天.強制.上路.公開.可以.希望.物業.原料.統一.資訊.實施.管理.

食品.台灣.大陸.王志剛.協會.美國.5展.北國.去年.表示.促成.美元.國際.採購.買主.預計.廠商.舉辦.

攻擊.網站.政府.北韓.南韓.今天.匿名.媒體.駭客.聲明.

創新.施振榮.人文.科技.整合.人才.挑戰.競爭.必須.困難.表示.青年.突破.瓶頸.創造.價值.

發票.電子.中獎.列印.財政.實體.沒有.

天氣.機會.今天.午後.昨天.暴雨.穩定.山區.不過.中部.比較.而且.局部.注意.南方.南部.特別.晴朗.發生.發展.

兩岸.交通.運輸.大陸.海運.貨運.客運.持續.統計.增加.

兩岸.大陸.問題.公權.表示.力行.討論.部門.可以.政治.范麗青.實務.台灣.交流.合作.使的.協議.孫亞夫.涉及.學者.關係.

中國.居民.人民.人員.大陸.存款.使館.機構.外國.境內.領館.數據.

額度.人民.國際.銀行.仲利.租賃.動用.資金.

太空.返回.大陸.3名.著陸.進入.地面.降落.神十.報導.

銀行.大陸.影子.利率.借貸.中小企業.溫州.經濟.融資.20.放款.表示.根據.人民.中心.分析.打擊.民間.服務.的溫州.流動.國內.登記.總體.證券.體系.

海監.直升.大陸.執法.報導.海洋.這2艘.廣東省.10.20.中國.巡航.昨天.首航.國家.船及.新造.總隊.

中國.大陸.店內.公民.報導.遇害.

改造.棚戶.會議.投資.城市.政策.大陸.引導.支持.安置.國務.

品牌.價值.中國.最貴.發布.

杭州.東站.樞紐.鐵路.火車.高鐵.啟用.

發射.火箭.長征.袁潔.大陸.太空.任務.研製.航太.運載.5號.中國.能力.

大陸.謝長廷.研討.許世銓.政策.訪問.他說.台研所.民進黨.兩岸.中國.研究.問題.

兩岸.大陸.協商.互不.公權.交流.存在.否認.事實.討論.陸委會.

服務.協議.兩岸.貿易.協商.開放.服貿.效益.基礎.陸委會.雙方.大陸.市場.合作.自由.承諾.區域.經濟.

投資.服務.大陸.來台.貿易.開放.人員.協議.專業.陸委會.國內.陸資來台.就業.影響.市場.兩岸.針對.規定.評估.經濟.人及.台灣.白領.立法.行政.沒有.依據.承諾.現行.進行.管理.

中國.協議.服務.規定.開放.證照.大陸.任何.承諾.專業.採認.現行.陸委會.勞工.

城鎮.城市.人口.報告.發展.轉移.大陸.規劃.農業.市民.推進.落戶.中國.今天.有序.形態.保障.能力.條件.提高.

美國.史諾登.不過.厄瓜多.其他.專家.關係.議題.大陸.可能.表示.威脅.要求.國家.提出.避免.

人大.大學.在等你.官網.美女.畢業.不過.中國.老師.走紅.首頁.康逸琨.意外.

費用.違規.大陸.單位.公務.金額.審計.預算.購置.支出.出國.年度.報告.運行.公費.外交.個中.部門.農業.

太空.大陸.載人.神舟十號.天宮.航太.發射.一號.工程.今天.王兆耀.表示.實驗.對接.應用.

陳偉殷.如果.聯盟.以後.最後.復健.

消防.阿里.分隊.救災.嘉義.廳舍.海拔.辦公.

2014-06-23

在Windows上的VMWare CentOS Linux上安裝OpenStack IceHouse 步驟3 KeyStone安裝

OpenStack Keystone 是負責User 與Service的管理的,所以是第一個要裝的Package. Keystone 沒裝好　後面所有的Package都不能裝.
Identity Service concepts

Identity Service concepts

The Identity Service performs the following functions:

User management. Tracks users and their permissions.
Service catalog. Provides a catalog of available services with their API endpoints.

Install the Identity Service

Install the OpenStack Identity Service on the controller node, together with python-keystoneclient (which is a dependency):
```
# yum install openstack-keystone python-keystoneclient
```
The Identity Service uses a database to store information. Specify the location of the database in the configuration file. In this guide, we use a MySQL database on the controller node with the username 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
```

Use the password that you set previously to log in as root. Create a 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

Create the database tables for the Identity Service:

# su -s /bin/sh -c "keystone-manage db_sync" keystone

Define an authorization token to use as a shared secret between the Identity Service and other OpenStack services. Use openssl to generate a random token and store it in the configuration file:
```
# ADMIN_TOKEN=$(openssl rand -hex 10)
# echo $ADMIN_TOKEN
# openstack-config --set /etc/keystone/keystone.conf DEFAULT \
   admin_token $ADMIN_TOKEN
```

直接設andim_token 為 ADMIN_TOKEN 就可以,　後面範例也都用ADMIN_TOKEN.

By default, Keystone uses PKI tokens. Create the signing keys and certificates and restrict access to the generated data:

# keystone-manage pki_setup --keystone-user keystone --keystone-group keystone
# chown -R keystone:keystone /etc/keystone/ssl
# chmod -R o-rwx /etc/keystone/ssl

Start the Identity Service and enable it to start when the system boots:
```
# service openstack-keystone start
# chkconfig openstack-keystone on
```
By default, the Identity Service stores expired tokens in the database indefinitely. While potentially useful for auditing in production environments, the accumulation of expired tokens will considerably increase database size and may decrease service performance, particularly in test environments with limited resources. We recommend configuring a periodic task using cron to purge expired tokens hourly.
1. Run the following command to purge expired tokens every hour and log the output to /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
```

Define users, tenants, and roles

After you install the Identity Service, set up users, tenants, and roles to authenticate against. These are used to allow access to services and endpoints, described in the next section.
Typically, you would indicate a user and password to authenticate with the Identity Service. At this point, however, you have not created any users, so you have to use the authorization token created in an earlier step, see the section called “Install the Identity Service” for further details. You can pass this with the --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

Create an administrative user

Follow these steps to create an administrative user, role, and tenant. You will use this account for administrative interaction with the OpenStack cloud.
By default, the Identity Service creates a special _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.

Create the admin user:
```
$ keystone user-create --name=admin --pass=ADMIN_PASS --email=ADMIN_EMAIL
```
Replace ADMIN_PASS with a secure password and replace ADMIN_EMAIL with an email address to associate with the account.

直接用ADMIN_PASS就可以,記住這密碼.

Create the admin role:
```
$ keystone role-create --name=admin
```

Create the admin tenant:

$ keystone tenant-create --name=admin --description="Admin Tenant"

You must now link the admin user, admin role, and admin tenant together using the user-role-add option:
```
$ keystone user-role-add --user=admin --tenant=admin --role=admin
```

Link the admin user, _member_ role, and admin tenant:

$ keystone user-role-add --user=admin --role=_member_ --tenant=admin

Create a normal user

Follow these steps to create a normal user and tenant, and link them to the special _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.

Create the demo user:
```
$ keystone user-create --name=demo --pass=DEMO_PASS --email=DEMO_EMAIL
```
Replace DEMO_PASS with a secure password and replace DEMO_EMAIL with an email address to associate with the account.

直接用DEMO_PASS就可以,記住這密碼.

Create the demo tenant:
```
$ keystone tenant-create --name=demo --description="Demo Tenant"
```
Note

Do not repeat this step when adding additional users.

Link the demo user, _member_ role, and demo tenant:

$ keystone user-role-add --user=demo --role=_member_ --tenant=demo

Create a service tenant

OpenStack services also require a username, tenant, and role to access other OpenStack services. In a basic installation, OpenStack services typically share a single tenant named service.
You will create additional usernames and roles under this tenant as you install and configure each service.

Create the service tenant:

$ keystone tenant-create --name=service --description="Service Tenant"

Define services and API endpoints

So that the Identity Service can track which OpenStack services are installed and where they are located on the network, you must register each service in your OpenStack installation. To register a service, run these commands:

keystone service-create. Describes the service.
keystone endpoint-create. Associates API endpoints with the service.

You must also register the Identity Service itself. Use the OS_SERVICE_TOKEN environment variable, as set previously, for authentication.

Create a service entry for the Identity Service:

$ 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.

Specify an API endpoint for the Identity Service by using the returned service ID. When you specify an endpoint, you provide URLs for the public API, internal API, and admin API. In this guide, the 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.

Verify the Identity Service installation

To verify that the Identity Service is installed and configured correctly, clear the values in the OS_SERVICE_TOKEN and OS_SERVICE_ENDPOINT environment variables:
```
$ unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
```
These variables, which were used to bootstrap the administrative user and register the Identity Service, are no longer needed.
You can now use regular user name-based authentication.
Request a authentication token by using the 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.
Verify that authorization behaves as expected. To do so, request authorization on a tenant:
```
$ 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.
You can also set your --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 this file to read in the environment variables:
```
$ source admin-openrc.sh
```
Verify that your admin-openrc.sh file is configured correctly. Run the same command without the --os-* arguments:
```
$ keystone token-get
```
The command returns a token and the ID of the specified tenant. This verifies that you have configured your environment variables correctly.

Verify that your admin account has authorization to perform administrative commands:

$ 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.

在Windows上的VMWare CentOS Linux上安裝OpenStack IceHouse 步驟2-1 基礎設定

-密碼最好用下表, 這樣就不需改範例指令.
-有 # 開頭的就是指令 Copy 貼上Terminal執行就可.
2. Basic environment configuration
Passwords
This guide uses the convention that 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.
The complete list of passwords you need to define in this guide are:

Table 2.1. Passwords
Password name	Description
Database password (no variable used)	Root password for the database
`KEYSTONE_DBPASS`	Database password of Identity service
`DEMO_PASS`	Password of user `demo`
`ADMIN_PASS`	Password of user `admin`
`GLANCE_DBPASS`	Database password for Image Service
`GLANCE_PASS`	Password of Image Service user `glance`
`NOVA_DBPASS`	Database password for Compute service
`NOVA_PASS`	Password of Compute service user `nova`
`DASH_DBPASS`	Database password for the dashboard
`CINDER_DBPASS`	Database password for the Block Storage service
`CINDER_PASS`	Password of Block Storage service user `cinder`
`NEUTRON_DBPASS`	Database password for the Networking service
`NEUTRON_PASS`	Password of Networking service user `neutron`
`HEAT_DBPASS`	Database password for the Orchestration service
`HEAT_PASS`	Password of Orchestration service user `heat`
`CEILOMETER_DBPASS`	Database password for the Telemetry service
`CEILOMETER_PASS`	Password of Telemetry service user `ceilometer`
`TROVE_DBPASS`	Database password of Database service
`TROVE_PASS`	Password of Database Service user `trove`

Database

Controller setup

Controller setup

On the controller node, install the MySQL client and server packages, and the Python library.

# yum install mysql mysql-server MySQL-python

The MySQL configuration requires some changes to work with OpenStack.

Edit the /etc/my.cnf file: 編輯此檔
1. Under the [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
```
2. Under the [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
```

Start the MySQL database server and set it to start automatically when the system boots:

# service mysqld start
# chkconfig mysqld on

Finally, 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.
You must delete the anonymous users that are created when the database is first started. Otherwise, database connection problems occur when you follow the instructions in this guide. To do this, use the mysql_secure_installation command. Note that if mysql_secure_installation fails you might need to use mysql_install_db first:

# mysql_install_db
# mysql_secure_installation

If 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.
Node setup

Node setup

On all nodes other than the controller node, install the MySQL Python library:

# yum install MySQL-python

OpenStack packages

OpenStack packages

Distributions might release OpenStack packages as part of their distribution or through other methods because the OpenStack and distribution release times are independent of each other.
This section describes the configuration you must complete after you configure machines to install the latest OpenStack packages.
The examples in this guide use the OpenStack packages from the RDO repository. These packages work on Red Hat Enterprise Linux 6, compatible versions of CentOS, and Fedora 20. To enable the RDO repository, download and install the rdo-release-icehouse package:
# yum install http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/rdo-release-icehouse-3.noarch.rpm
The EPEL package includes GPG keys for package signing and repository information. This should only be installed on Red Hat Enterprise Linux and CentOS, not Fedora. Install the latest epel-release package (see http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html). For example:
# yum install http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
The openstack-utils package contains utility programs that make installation and configuration easier. These programs are used throughout this guide. Install openstack-utils. This verifies that you can access the RDO repository:

# yum install openstack-utils

The openstack-selinux package includes the policy files that are required to configure SELinux during OpenStack installation on RHEL and CentOS. This step is not required during OpenStack installation on Fedora. Install openstack-selinux:# yum install openstack-selinux

Upgrade your system packages:
# yum upgrade
If the upgrade included a new kernel package, reboot the system to ensure the new kernel is running:

# reboot

Messaging server

OpenStack uses a message broker to coordinate operations and status information among services. The message broker service typically runs on the controller node. OpenStack supports several message brokers including RabbitMQ, Qpid, and ZeroMQ. However, most distributions that package OpenStack support a particular message broker. This guide covers the message broker supported by each distribution. If you prefer to implement a different message broker, consult the documentation associated with it.

To install the message broker service

Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux, and Fedora use Qpid.
```
# yum install qpid-cpp-server
```

To configure the message broker service

To simplify installation of your test environment, we recommend that you disable authentication.
Edit the /etc/qpidd.conf file and change the following key:編輯此檔
```
auth=no
```

To finalize installation

Start the message broker service and configure it to start when the system boots:
```
# service qpidd start
# chkconfig qpidd on
```

Congratulations, now you are ready to install OpenStack services!

在Windows上的VMWare CentOS Linux上安裝OpenStack IceHouse 步驟第二章

上週參加Taiwan OpenStack User Group (TWOSUG) 1st Meetup in 2014, 有百餘人參加.
主講者Tom Fifield表示他就是在Notebook的VMWare上裝OpenStack的. 最新的 Ice House 版安裝說明已由20餘萬字大幅縮減至2萬餘字所以應該是很容易了解的
到OpenStack 上找到 RedHat/ CentOS 的安裝說明如下連結:
Installation Guide for Red Hat Enterprise Linux, CentOS, and Fedora
有14大項. 研討會主持人表示能在兩日內裝完就已是神人.
我由第二章開始嘗試.
先在VMware上安裝CentOS 64Bit V6.5
除自動產生的NAT網卡外另新加5張固定IP的網卡
10.0.0.11
10.0.0.21
10.0.0.31
10.0.1.21
10.0.1.31
2. Basic environment configuration

Figure 2.1. Three-node architecture with OpenStack Networking (neutron)

Controller node

To configure networking:

Configure the first interface as the management interface:
IP address: 10.0.0.11
Network mask: 255.255.255.0 (or /24)
Default gateway: 10.0.0.1

Network node

To configure networking:

Configure the first interface as the management interface:
IP address: 10.0.0.21
Network mask: 255.255.255.0 (or /24)
Default gateway: 10.0.0.1
Configure the second interface as the instance tunnels interface:
IP address: 10.0.1.21
Network mask: 255.255.255.0 (or /24)
The external interface uses a special configuration without an IP address assigned to it. Configure the third interface as the external interface:
Replace INTERFACE_NAME with the actual interface name. For example, eth2 or ens256.
1. Edit the /etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME file to contain the following:
  Do not change the HWADDR and UUID keys.
```
DEVICE=INTERFACE_NAME
TYPE=Ethernet
ONBOOT="yes"
BOOTPROTO="none"
```
Restart networking:
```
# service network restart
```

To configure name resolution:

Edit the /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

Compute node

To configure networking:

Configure the first interface as the management interface:
IP address: 10.0.0.31
Network mask: 255.255.255.0 (or /24)
Default gateway: 10.0.0.1

Note

Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on.
Configure the second interface as the instance tunnels interface:
IP address: 10.0.1.31
Network mask: 255.255.255.0 (or /24)

Note

Additional compute nodes should use 10.0.1.32, 10.0.1.33, and so on.

To configure name resolution:

Edit the /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

Verify connectivity

We recommend that you verify network connectivity to the internet and among the nodes before proceeding further.

From the controller node, ping a site on the internet:

# 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

From the controller node, ping the management interface on the network node:

# 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

From the controller node, ping the management interface on the compute node:

# 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

From the network node, ping a site on the internet:

# 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

From the network node, ping the management interface on the controller node:

# 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

From the network node, ping the instance tunnels interface on the compute node:

# 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

From the compute node, ping a site on the internet:

# 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

From the compute node, ping the management interface on the controller node:

# 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

From the compute node, ping the instance tunnels interface on the network node:

# 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

2014-06-21

工作問小雀:最熱門職缺第三名-國內業務

從工作問小雀雲端資料分析APP 中,我們可以發現,
今年最熱門的職缺第三名是"國內業務".
工作問小雀從雲端蒐集資料, 加以歸納分析後 ,得到今年的職缺分布狀態.
問小雀會告訴我們, 關於這"國內業務"的職務重點:

小雀說:
	小雀從筆記中找到, 有關國內業務的職務重點有: 客戶, 業務, 開發, 產品, 銷售, 服務, 顧客, 經驗, 處理, 推廣, ..等

從這些關鍵字, 我們可以很快的有一個關於這工作的輪廓.
接下來再問最熱門區域.

小雀說:
	小雀從筆記中本看到,國內業務的熱門區域有: 台北市中山區, 台北市內湖區, 台中市西屯區, 桃園縣桃園市, 新北市中和區, ..等

台北市中山區是國內業務最熱門的區域.

再更進一步的問小雀 , 職缺的熱門城市為何?

小雀說:
	小雀從筆記中本看到,國內業務的熱門城市有: 台北市, 新北市, 台中市, 桃園縣, 高雄市, ..等

而新北市是排名第二的城市.
如果對這職缺興趣, 可藉由小雀的幫忙, 經由 Google的搜索,
直接找到各家人力銀行的職缺.
立刻使用: 工作問小雀

CubicPower 工作問小雀有關半導體的職務重點

在 CubicPower 工作問小雀中,我挑了半導體的職務.
然後選熱門城市, 或熱門區域, 指定104 後就可找到想要的職缺.
過程如下: 進入 工作問小雀

小雀說:
	挑一個工作吧!

小雀說:
	小雀從筆記中找到, 有關半導體的職務重點有: 產品, 開發, 分析, 客戶, 設備, 製程, 執行, 技術, 改善, 設計, ..等

小雀說:
	小雀從筆記中本看到,半導體的熱門城市有: 新竹市, 台南市, 新竹縣, 台中市, 新北市, ..等

小雀說:
	小雀從筆記中本看到,半導體的熱門區域有: 新竹市, 台南市新市區, 新竹縣竹北市, 台中市潭子區, 新北市新店區, ..等

小雀說:
	想要指定資料來源嗎?

小雀說:
	可以Google 一下了!

之後就Show 出Google的結果:

約有 1,100,000 項結果 (搜尋時間：0.49 秒)

搜尋結果

半導體業工作專區- 104 人力銀行

www.104.com.tw/jb/category/?cat=3&no=1001006000
半導體業工作專區。104人力銀行提供台灣、海外、中國…等各地區半導體業工作，透過半導體業工作專區幫您找到理想工作。
台灣半導體股份有限公司＜公司簡介及所有工作機會＞104 ...

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
台灣半導體股份有限公司,半導體製造業,- 台灣半導體股份有限公司於1979年元月創立於台北縣土城鄉 - 1988年宜蘭廠新建完成，年產12億只整流器 - 1990年購入 ...
飛鳥半導體股份有限公司＜公司簡介及所有工作機會＞104 ...

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
飛鳥半導體股份有限公司,其他半導體相關業,尋找對生命有思考的人! 尋找不願渾渾噩噩過一生的人! 讓工作展現它的意義及樂趣，讓生命因為您的努力而綻放光芒為 ...
MStar_晨星半導體股份有限公司 - 104人力銀行

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
跳到工作機會(52) - 6~10人應徵工作經歷不拘，專科、大學、碩士學歷. 1. TV 軟體測試 ... 對Physical Design, APR 工作有熱忱、耐心，能吃苦耐勞配合加班。
盛群半導體股份有限公司＜公司簡介及所有工作機會＞104 ...

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
盛群半導體股份有限公司,半導體製造業,盛群半導體為國內專業微控制器IC設計領導廠商，營業範圍主要包括微控制器IC及其周邊元件之設計、研發與銷售。自1998年 ...
日月光半導體製造股份有限公司 - 104人力銀行

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
跳到工作機會(149) - 11~30人應徵工作經歷不拘，大學以上學歷. 1.SMT相關改善專案執行2.被動元件評估及材料管理3.SMT technology and roadmap ...
晶宏半導體股份有限公司＜公司簡介及所有工作機會＞104 ...

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
晶宏半導體股份有限公司,IC設計相關業,晶宏半導體為一專業IC設計公司, 專注於Mixed-Signal & LCD Driver IC 之設計及行銷. 是台灣少數擁有自行開發手機及各式 ...
羅姆半導體股份有限公司＜公司簡介及所有工作機會＞104 ...

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
羅姆半導體股份有限公司,IC設計相關業,ROHM CO., LTD.創立於1958年。 ROHM SEMICONDUCTOR TAIWAN CO., LTD.於1987設立。台灣羅姆成立於1987年， ...
昇陽國際半導體股份有限公司 - 104人力銀行

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
跳到工作機會(17) - 11~30人應徵工作經歷不拘，碩士以上學歷. 1.三五族鍺元素及碳化矽材料開發2.18吋製程、Glass. Poly.Oxide CMP新產品開發. 06/18.
萬有半導體有限公司＜公司簡介及所有工作機會＞104人力銀行

www.104.com.tw/jobbank/custjob/index.php?r=cust&j...
萬有半導體有限公司,半導體製造業,萬有半導體成立於2000年10月，總部設於美國加州矽谷，我們擁有高潛力的研發團隊，致力於關鍵技術的研究發展，以提供客戶 ...

科技大廠急徵半導體人才‎

廣告www.yes123.com.tw/‎

釋出職缺薪水高福利好有前景搶進熱門產業快投履歷

2014-06-19

複利終值係數 (FVIF) CubicPower 行動理財規劃

行動理財雲算

複利終值係數 (FVIF)

讀紅樓夢筆記第一回甄士隱夢幻識通靈賈雨村風塵懷閨秀

夏肇毅編寫 2014/6/713:30
一切皆因一塊女媧補天時所棄頑石而起。
紅樓夢第1回-3 原來女媧氏煉石補天之時，於大荒山無稽崖煉...

後來茫茫大士、渺渺真人將這石化做一塊寶玉，攜入紅塵，開始了這一切。
整個故事才叫石頭記，情僧錄，紅樓夢或風月寶鑒。
紅樓夢第1回-9 空空道人聽如此說，思忖半晌，將這《石頭記...
作者感嘆：滿紙荒唐言，一把辛酸淚！都云作者痴，誰解其中味？
紅樓夢第1回-10 滿紙荒唐言，一把辛酸淚！都云作者痴，誰解...

故事開始，姑蘇葫蘆廟旁住著一家鄉宦甄士隱。
年已半百，只有一女乳名英蓮，年三歲。
紅樓夢第1回-13 當日地陷東南，這東南一隅有處曰姑蘇，有城...
在隔壁葫蘆廟裏，寄居著一個窮儒姓賈名化，別號雨村，甄士隱常與他來往。
紅樓夢第1回-20 這士隱正痴想，忽見隔壁葫蘆廟內寄居的一個...
賈雨村看著甄家丫鬟擷了花，見她回了頭，以為這女子心中有意於他，狂喜不已。
紅樓夢第1回-21 這裡雨村且翻弄書籍解悶。忽聽得窗外有女子...
後來甄士隱封五十兩白銀，並兩套冬衣，助賈雨村進京趕考。
紅樓夢第1回-29 士隱聽了，大叫：「妙哉！吾每謂兄必非久居...
有次元霄佳節，甄士隱命家人霍啟抱了英蓮去看焰火花燈。
霍啟因要小解，便將英蓮放在一家門檻上坐著。
待他來抱時，已不見英蓮的蹤影。
甄士隱令家人遍尋不著，傷心不已。
紅樓夢第1回-31 真是閒處光陰易過，倏忽又是元霄佳節矣。士...
三月十五，葫蘆廟中炸供，和尚們不小心，使油鍋火逸。
一條街燒得如火焰山一般。
甄士隱只得將田莊都折變了，攜了妻子與兩個丫鬟投他岳丈封肅家去。
紅樓夢第1回-33 不想這日三月十五，葫蘆廟中炸供，那些和尚...
一日甄士隱到街前散散心時，忽見一個跛足道人口內唸著：
世人都曉神仙好，惟有功名忘不了。...
世人都曉神仙好，只有金銀忘不了。...
世人都曉神仙好，只有姣妻忘不了。...
世人都曉神仙好，只有兒孫忘不了。...
紅樓夢第1回-36 世人都曉神仙好，惟有功名忘不了。古今將相...
甄士隱說了一聲「走罷！」竟不回家，同了瘋道人飄飄而去。
紅樓夢第1回-39 那瘋跛道人聽了，拍掌笑道：「解得切！解得...
有天甄家大丫鬟在門前買線，忽然聽到街上喝道之聲，眾人都說新太爺到任。
大轎抬著一個烏帽猩袍的官府過去。
丫鬟發了個愣，心想：這官好面熟，倒像在那裡見過的。
紅樓夢第1回-41 這日，那甄家大丫鬟在門前買線，忽聽街上喝...

工作問小雀:專櫃門市最熱門的職缺第二名

從工作問小雀雲端資料分析APP 中,我們可以發現,
今年最熱門的職缺第二名是"專櫃門市".
工作問小雀從雲端蒐集資料, 加以歸納分析後 ,得到今年的職缺分布狀態.
免費試用: 工作問小雀
小雀告訴我們, 這"專櫃門市"的職務重點有:
的職務重點有: 商品, 銷售, 服務, 門市, 顧客, 管理, 經驗, 陳列, 獎金, 清潔, ..等
從這些關鍵字, 我們可以很快的有一個關於這工作的輪廓.
而專櫃門市的熱門區域有:
台北市大安區, 台北市中山區, 台北市信義區, 台北市中正區, 台中市西屯區, ..等
可以看出, 專櫃門市最熱門區域幾乎都在台北市.
再更進一步的問小雀 , 可以問到 "專櫃門市" 的職缺熱門城市前五名為:
台北市, 新北市, 台中市, 高雄市, 桃園縣, ..等
而新北市雖不如台北那麼密集, 但也是第二的城市.
如果對這職缺興趣, 可藉由小雀的幫忙, 經由 Google的搜索,
直接找到各家人力銀行的職缺.

工作問小雀:餐飲服務最熱門的職缺第一名

免費試用: 工作問小雀
從工作問小雀雲端資料分析APP 中,我們可以發現,
今年最熱門的職缺第一名是"餐飲服務".
工作問小雀從雲端蒐集資料, 加以歸納分析後 ,得到今年的職缺分布狀態.
小雀告訴我們, 這"餐飲服務"的職務重點有:
服務, 顧客, 餐飲, 清潔, 環境, 外場, 客人, 點餐, 用餐和時間.
從這些關鍵字, 我們可以很快的有一個關於這工作的輪廓.
再更進一步的問小雀 , 可以問到 "餐飲服務" 的職缺熱門城市前五名為:
台北市, 台中市, 新北市, 高雄市, 桃園縣
而餐飲服務的熱門區域有:
台北市大安區, 台北市中山區, 台北市信義區, 台北市中正區, 台北市松山區
可以看出, 餐飲服務最熱門區域幾乎都在台北市.
而台中市雖不如台北那麼密集, 但也是擠進排名第二的城市.
對這職缺興趣的朋友, 可藉由小雀的幫忙, 經由 Google的搜索,
直接找到各家人力銀行的職缺.
簡單的說,
工作問小雀找熱門工作, 找熱門區域, 並找出熱門關鍵字.

影片示範:

CubicPower 工作問小雀雲端APP 找最熱門職缺

雲端APP 整合雲端資料讓你透過Google 搜索各家職缺
A liittle birdy told me!
告訴你相關職務最重要的10個關鍵字
找最熱門職缺
找最熱門城市
找最熱門區域
開始使用: CubicPower 工作問小雀找最熱門職缺
影片示範:

2013-12-28

YourGates: Mobile Browser-Books

YourGates- Gates on your hands:

YourGates: Mobile Browser-Books

http://www.yourgates.com/Yo...
http://www.yourgates.com/
http://www.yourgates.com/YourGates/Books/Day/20131201.htm
http://www.yourgates.com/
-Books of Days
-Books of Previous Days
-Books of Previous Months
-Books of Previous Years
-Books of Previous Decades
-You may also like these books

訂閱：文章 (Atom)

	Note
	Additional compute nodes should use 10.0.0.32, 10.0.0.33, and so on.

2014-06-26

今天王宇佐在溫布頓網球賽拍倒俄羅斯名將尤茲尼，首次闖進第3輪。

我們看看去年的今天看看的今天發生了什麼事:

CubicPower 歷史印象20130626

2014-06-23

Identity Service concepts

Install the Identity Service

Define users, tenants, and roles

Define services and API endpoints

Verify the Identity Service installation

Controller setup

Node setup

OpenStack packages

Messaging server

Controller node

Network node

Compute node

Verify connectivity

2014-06-21

搜尋結果

2014-06-19

2013-12-28

2013-12-08