Ali84's profile - activity

2017-01-25 03:40:30 -0500 received badge  Famous Question (source)
2017-01-24 13:28:47 -0500 received badge  Notable Question (source)
2017-01-22 11:14:10 -0500 received badge  Notable Question (source)
2017-01-22 02:49:32 -0500 received badge  Popular Question (source)
2017-01-21 06:58:14 -0500 commented answer How can I measure live migration duration of a VM?

Thank you so much

2017-01-21 04:51:11 -0500 asked a question How can I measure live migration duration of a VM?

Hi, I wonder if anyone mind explaining how we can measure live migration duration. I’m conducting some straightforward experiment on an small Openstack deployment on three nodes regarding performance interference of VMs & I wanna take into observation this metric too. What I got so far searching is to ping the migrating VM therefore we'll be able to calculate the downtime period somehow but not the whole procedure of migration! Any tools or method for that?

Thank you in advance.

2017-01-02 23:20:23 -0500 received badge  Famous Question (source)
2016-12-30 21:09:23 -0500 received badge  Popular Question (source)
2016-12-29 12:07:07 -0500 commented answer Why can I not get CPU steal time (%st) for co-located VMs?

.. Do I need to disable cores on the host itself which I don't have any idea how to do it besides this would result that one single core serves VMs as well as host processes which is not a valid senario in our experiment.

I would be very grateful for any further assistance.

2016-12-29 11:59:59 -0500 commented answer Why can I not get CPU steal time (%st) for co-located VMs?

So considering the latter I guess the only option would be disabling all cores but one so the VMs automatically would be placed together & remain there. But the question here is shall I do this by setting vcpu_pin_set key to for example 0 on nova.conf file in the respective host or ..

2016-12-29 11:48:39 -0500 commented answer Why can I not get CPU steal time (%st) for co-located VMs?

Hi, thank you so much.

I may clarify that 1st my sole purpose of pinning was a.Prevent VMs from floating freely on different cores and b.Keep them both together on a same core. 2nd it is desirable to have a VM's time stolen only by having load on other neighboring VMs not by host's processes.

2016-12-29 01:03:08 -0500 asked a question Why can I not get CPU steal time (%st) for co-located VMs?

I'm trying to carry out a series of experiments regarding VM performance. I've already placed two VMs on a same physical core of one host (setting flavor extra-spec & host aggregate or using only virsh vcpupin ...) and imposed high load (%70 to even %100) on one VM (by running stress-ng or bench utilities or infinite loop) and ran some CPU intensive application such as compressing utility to make a big file on the other. Unfortunately all the way through from the beginning top on none of the VMs shows any amount for cpu steal time (%st) which implies that no interference & contention exists between two VMs while using the shared CPU. I can't configure why we observe such a behavior. Anyone know how I can set up a senario so there will be contention between two co-located VMs and get some amount for %st parameter? It would be of great assistance , thanks.

PS: My Openstack deployment consists of 2 compute node each including 8 physical core.

2016-12-25 05:28:08 -0500 received badge  Popular Question (source)
2016-12-24 08:42:21 -0500 received badge  Scholar (source)
2016-12-24 08:42:13 -0500 commented answer Is there any way to determine which physical core of a host an instance has been placed on

Thank you so much. Although virsh vcpupin did not report exactly what I was looking for but it gives a very related facility in regard to pinning vcpu to a pcpu that I was totally unaware of. After using it this virsh dumpxml <instance id> | grep vcpupin displayed what I was looking for.

2016-12-24 02:47:12 -0500 asked a question Is there any way to determine which physical core of a host an instance has been placed on

I'm gonna create a new flavor with --vcpus attribute set to 1 and set the --property hw:cpu_policy to dedicated so any instance launched with that flavor would be pinned on a fixed physical core on that host. I also assume if I make a host aggregate then another newly launched instance in that host aggregate & with the same flavor as first instance would be located beside the first one on the same physical core. Now I wounded if there's any way that I could check if they'd actually been located on the same physical core or not. So far all the command I came into just display the host node on which instances has been placed but not the specific physical core. If I'm lost on the topic please any idea how I could have co-located instances on a single physical core?

2016-11-12 00:38:12 -0500 received badge  Enthusiast
2016-11-02 23:35:47 -0500 commented question New Juno install - Unable to boot instance, neutron client auth issue

I have Mitaka installed and in some point I received Error: No valid host was found. Personelly I didn't figure it out what was the core issue but did manage to get a way around it by simply using other user credentials than admin to launch an instance and it worked.

2016-10-26 04:27:59 -0500 received badge  Famous Question (source)
2016-10-24 13:54:58 -0500 commented answer Where should I look for user credentials to work with nova commandline?

Thanks, I learn a lot, however my question was where I can find those values in the first place when you have an Autopilot Openstack deployment.

2016-10-24 13:49:12 -0500 received badge  Notable Question (source)
2016-10-24 08:03:47 -0500 received badge  Editor (source)
2016-10-24 07:57:13 -0500 answered a question The instance launched by openstack autopilot Fails to start Raise network interfaces

Finally I came across the neutron-ovs-cleanup service log which was error-ridden with

ImportError: cannot import name deploy

Then the quick guide given in this page (https://ask.openstack.org/en/question/11458/keystone-all-importerror-cannot-import-name-deploy/ (https://ask.openstack.org/en/question...)) did the rest. Well it was the incompatible version of this Python library (PasteDeploy) I guess that made the service fail and consequently led to other related networking services failure as well. So I ran pip uninstall --yes PasteDeploy && pip install 'PasteDeploy>=1.5.0' as instructed on the page above and all of a sudden it worked :-)

2016-10-24 07:52:20 -0500 received badge  Notable Question (source)
2016-10-19 03:07:59 -0500 received badge  Popular Question (source)
2016-10-18 23:29:31 -0500 received badge  Popular Question (source)
2016-10-10 06:31:45 -0500 answered a question Where should I look for user credentials to work with nova commandline?

Well it turned out that there is a link labelled "Download OpenStack RC file for admin" under the OpenStack tab of Landscape gui to get a file with all the credentials needed to talk to openstack services via command line interface.

2016-10-10 06:02:50 -0500 asked a question Where should I look for user credentials to work with nova commandline?

Hey, I deployed Openstack Autopilot on physical machines. I have some debugging to do concerning vms not getting ip addresses so I came across some guide that had me peek into compute nodes and others using nova command line interface. When I tried them I was prompted that I need to be authenticated for using nova command.

ERROR (CommandError): You must provide a username or user ID via --os-username, --os-user-id, env[OS_USERNAME] or env[OS_USER_ID]

I have no clue where I can obtain them. Well please forgive my ingenuousness in this field and help me figure it out. Thanks in advanced.

2016-10-09 21:05:53 -0500 asked a question The instance launched by openstack autopilot Fails to start Raise network interfaces

I installed openstack Autopilot on physical machines. Now I can launch instances but they seems not to get an ip from any dhcp server so obviously I have no access to them. For example when I launch an instance with Xenial image in its log after going through a lot of lines like this:

...[[0m[0;31m*     [0m] A start job is running for Raise network interfaces...

It declares that Failed to start Raise network interfaces

Also juju status reports that

    neutron-gateway/0:
       workload-status:       
       current: blocked
       message: 'Services not running that should be: neutron dhcp-agent, neutron-vpn-agent'

Running neutron agent-listcommand reveals that many other services are not working probably either.

I tried to manually start "neutron dhcp-agent" on a node where neutron-gateway is placed but got this error

start: Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=99077 comm="start neutron-dhcp-agent ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init ")

Now I'm stranded by this mess not knowing what to do next. Please somebody help me out. Any hint would be greatly appreciated.