Ask Your Question

William Wang's profile - activity

2018-12-04 03:32:34 -0500 received badge  Popular Question (source)
2017-01-16 07:28:31 -0500 received badge  Student (source)
2016-10-21 05:08:04 -0500 received badge  Famous Question (source)
2016-08-31 14:30:52 -0500 answered a question OpenStack on Virtualbox - For home practice

I did some on CentOS and Ubuntu VM, Ubuntu is an easer one to play with: if you want to play with Openstack, you may refer to guidelines (

You may just install Keystone, Nova, Neutron, Cinder, Heat and Horizon to start with, note that your VM should have storage size > 64GB, to play with some guest applications.

Good luck

2016-08-17 08:05:13 -0500 received badge  Notable Question (source)
2016-08-08 11:56:29 -0500 answered a question i am new to openstack. i need to configure and install openstack on desktop using vm. from where should i start? any help would be helpfull

You can deploy openstack environment on various host OS, for me the easiest is using ubuntu trusty server image. If okay with you, go ahead download ubuntu server ISO from and create a Virtualbox VM with 4KRAM and 20GB storage.

Then, if you want to get a first-look on openstack, you can deploy openstack on the ubuntu VM you created. Read and follow steps on (

If you want to try some code change, you can deploy openstack development environment on the ubuntu VM you created. Read and follow steps on (

Good luck

2016-07-29 07:31:57 -0500 received badge  Popular Question (source)
2016-07-20 12:38:59 -0500 commented answer tacker vnf-create: how to customize my VNF ?

Thanks! but I am not sure if I fully understand what you said: are you saying that Tacker is now not capable of specifying security groups and/or networks when creating a VNFD? Do you know where can I find more information about tacker private YAML format?

2016-07-19 14:00:01 -0500 asked a question tacker vnf-create: how to customize my VNF ?

I am new to tacker, I am able to bring simple VNF, but I would like to customize my VNF with: - particular security group (I am able to create my own using HEAT template) - stack IP from private network (I Do not know what does "pkt_in:" and "pkt_out:" meaning in Tacker's sample template) - floating IP. ( (I am able to associate floating IP using HEAT template, but do not know how to to it in Tacker)

I saw two options in tacker vnf-create: --config-file CONFIG_FILE] [--config CONFIG] [--param-file PARAM_FILE] what is the format for either file. Thanks

2016-07-11 21:59:44 -0500 received badge  Famous Question (source)
2016-07-05 10:18:30 -0500 received badge  Enthusiast
2016-06-29 09:00:06 -0500 commented answer mirantis-8: how to change fuel master SSH listening IP

Thanks for your information, I tried to manually change the listening IP, and did couple of master reboot, have not found any side effect yet. Still don't understand why by-default the listening IP was bound to the admin interface, not public interface though.

2016-06-29 04:15:24 -0500 received badge  Notable Question (source)
2016-06-28 23:55:34 -0500 received badge  Popular Question (source)
2016-06-26 18:14:26 -0500 answered a question mirantis 8.0 fuel master node change ip

I am not export on this, but per my deploy experiences, probably you have to to re-deploy it. I had similar issue to change admin IP after mos8.0 ISO installed. you may try to use "Automated installation using the Mirantis VirtualBox scripts" (download from Mirantis site). Before executing the script you may modify IPs in to have your own IP network settings. (you can download scripts from (download from Mirantis site).

2016-06-26 17:52:49 -0500 asked a question mirantis-8: how to change fuel master SSH listening IP

I manually installed Mirantis MOS8.0 Fuel Master on one of the bare machine server, after installation, I found that SSH listening IP was bound to the Fuel Master's admin IP, not the external IP. I have to ssh to other server on the same subnet of the public network and ssh to the MOS8.0 Fuel Master. I am thinking to change the listening IP manually, but see one comment that says the file is managaged by Puppet, I wonder if it is save to change it ? If not, what is the safe way to change ?

[...]# cat /etc/ssh/sshd_config

File is managed by Puppet

Port 22 ListenAddress <--- this is the admin IP, not the pubich IP. ...


2016-06-25 14:15:14 -0500 received badge  Popular Question (source)
2016-05-27 09:47:33 -0500 commented question Mitaka: ceilometer-alarm-evaluator unmet dependencies during installation

Some exports from my company mentioned that it could be a Ubuntu package version lineup issue for OS-Mitaka. I deployed OS-liberty, no same issue found.

2016-05-26 10:01:12 -0500 asked a question Mitaka: ceilometer-alarm-evaluator unmet dependencies during installation

I encountered a issue when deploy ceilometer with cloud-archive:mitaka, below were the error messages:

The following packages have unmet dependencies: ceilometer-alarm-evaluator : Depends: ceilometer-common (= 1:5.0.0-0ubuntu1~cloud0) but 1:6.0.0-0ubuntu1~cloud0 is to be installed ceilometer-alarm-notifier : Depends: ceilometer-common (= 1:5.0.0-0ubuntu1~cloud0) but 1:6.0.0-0ubuntu1~cloud0 is to be installed E: Unable to correct problems, you have held broken packages.

I am doing openstack-mitaka deployment on Ubuntu 14.04 kvm virtual machine and deployment steps below:

ubuntu: Swappiness set to 0 Apport disabled

openstack: ###As root, add the mitaka cloud archive and reboot: apt-get install software-properties-common add-apt-repository cloud-archive:mitaka

  apt-get update && apt-get dist-upgrade

###As root, install the openstack client: apt-get install python-openstackclient

##Install MariaDB and Rabbit ##install and deploy Keystone ... ##Ceilometer ##As root, install MongoDB: ... ##As root, create the ceilometer database: ##As root, install ceilometer: failed here..

2016-05-04 21:14:09 -0500 asked a question NOVA API: how to test new microversion under tests/unit

I am new and working on a NOVA API bug. would like to know know to test new microversion under tests/unit/test code. I am able to test new microversion under /tests/functional/test code