Claudiu Belu's profile - activity

Hello, No, there's only the config option you've mentioned. The config option has to be set in the compute nodes' nova.

Hello, os_brick only supports the Windows SMBFS connector; there are no Linux SMBFS connectors defined, which means tha

I've updated by reply to respond to your comments.

Hello Luc, Just a small bit of information about how cold resize / migration generally works. Pretty much all of the No

Hello Luc, Just a small bit of information about how cold resize / migration generally works. Pretty much all of the No

Hello Luc, Just a small bit of information about how cold resize / migration generally works. Pretty much all of the No

Thanks for posting the solution, it will be helpful for other people in the future. :) Also, just an FYI, it's a good t

Hello, The warning you've mentioned in the Hyper-V nova-compute logs has nothing to do with not being able to spawn ins

And lastly, flat networking should be mostly used for the public networks. For tenant / private networks you should use

Thirdly, When a PortBindingFailed exception occurs and you see it in the logs, it will tell you to look into the Neutron

Secondly, could you share the neutron config files (neutron.conf and ml2conf.ini) for both the Controller and compute no

Hm, there isn't enough information to pinpoint the exact problem, but I'd say that there might be some misconfiguration

Hello, What OpenStack version are you using? If it's Ocata or newer, then it is as awestin says, you will have to execu

Hello, What OpenStack version are you using? If it's Ocata or newer, then it is as awestin says, you will have to execu

Hello, This sounds a bit peculiar. I'm wondering if it actually hangs while loading the driver (shouldn't be any reason

Hello, This sounds a bit peculiar. I'm wondering if it actually hangs while loading the driver (shouldn't be any reason

Hello, Well, first of all, quotas refer to the amount of resources a tenant / user is allowed to use, and they are set

No problem. :) Since the hyperv mechanism driver resides in networking-hyperv, there was no way for neutron to succeed i

You can check by running: pip freeze | grep networking-hyperv For Ocata, it should be version 4.0.0.

You can check by running: pip freeze | grep networking-hyperv For Ocata, it should be version 4.0.0.

Hello. Just an FYI, Neutron Ocata doesn't fail to start if a configured mechanism_driver is not installed, AFAIK. Can yo

Hello,

In order to have OVS DVR, the neutron-l3-agent is required to also run on Windows, which is not supported at the moment.

Best regards,

Claudiu Belu

Hello,

It would be a lot easier to understand the logs you've provided if they would be included in a paste, like: http://paste.openstack.org/ or any other paste.

From what I can understand, 2 errors occured: the first one while connecting the iSCSI volume, and the second one while formatting the exception message.

In order to better understand the issue, a few more bits of information would be useful:

What kind of iSCSI backend are you using?

What locale do you use in this environment?

Best regards,

Claudiu Belu

Hello,

The article you mentioned is passing the x509 certificate to the instance through instance user_data, not as a keypair:

nova boot --flavor 2 --image your_windows_image --key-name key1 vm1 --user_data=your_cert.pem

That being said, since then, support for x509 has been added to nova-api (but not horizon). See the help for the nova keypair-add command:

usage: nova keypair-add [--pub-key <pub-key>] [--key-type <key-type>]
                        [--user <user-id>]
                        <name>

Create a new key pair for use with servers.

Positional arguments:
  <name>                 Name of key.

Optional arguments:
  --pub-key <pub-key>    Path to a public ssh key.
  --key-type <key-type>  Keypair type. Can be ssh or x509. (Supported by API
                         versions '2.2' - '2.latest')
  --user <user-id>       ID of user to whom to add key-pair (Admin only).
                         (Supported by API versions '2.10' - '2.latest')

This has been introduced in nova-api v2.1 (microversion 2.2), so make sure you have that registered as an endpoint:

openstack endpoint list
# you should see something like this:
# | 34291deac24a4a9195c340b70f03830f | RegionOne | nova         | compute        | True    | admin     | http://10.14.0.149:8774/v2.1              |

If not, you'll have to register a new endpoint for the /v2.1 URL, and then run a command like this:

nova --service-type endpoint_name keypair-add ...

By default, the microversion 2.latest is used, but if not, you will probably want to be explicit:

nova --service-type endpoint_name --os-compute-api-version 2.2 keypair-add ...

Best regards,

Claudiu Belu

gwmi -Namespace 'root/virtualization/v2' -Class Msvm_SyntheticEthernetPortSettingData | ? ElementName -eq 3cef1e9b-9925-4926-83ae-e90d3824fc2b There should only be one WMI object returned.

Hi! It's a very bizarre exception, IMO. It basically means that there are at least 2 switch ports with the same ElementName on the same host, which should not be possible. On the host on which you are getting this exception, can you run the following command in powershell:

Hello!

As previously mentioned, Hyper-V supports only VHD / VHDX images. You can find some already prepared images here: [1]

Secondly, make sure that you have the hyperv mechanism driver added in the Neutron server's ml2_conf.ini file in the mechanism_drivers list. Keep in mind that the neutron-hyperv-agent agent doesn't support VXLAN networks [2]. If you want VXLAN / GRE or other network types, you should take a look at Windows OVS + neutron-ovs-agent instead.

[1] https://cloudbase.it/windows-cloud-im...

[2] https://cloudbase.it/neutron-hyper-v-...

[3] https://cloudbase.it/openvswitch/

Best regards,

Claudiu

Also, neutron-hyperv-agent / neutron-ovs-agent logs what ports it processed in its logs. A VM's NIC name is the same as its neutron port name. Also, Windows / Hyper-V Server 2016 has been released, you can give it a try. :) https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

You will have to set debug=True and verbose=True in the compute node's nova.conf file. Then, when you spawn a VM, and it is waiting for a Neutron VIF plug event, it should look like this in the logs: http://paste.openstack.org/show/589616/

Hello,

You can simply snapshot the instance after the setup, and you will have the final sysprepped image you need.

Also, the guide you have linked is a bit outdated. We have a much simpler and updated guide here: [1]

[1] https://github.com/cloudbase/windows-...

Best regards,

Claudiu Belu

Hello,

Unfortunately, some bits regarding how the drivers are loaded changed in Newton, and now the valid drivers are:

# clustered driver
compute_driver=compute_hyperv.cluster.driver.HyperVClusterDriver

# regular driver
compute_driver=compute_hyperv.driver.HyperVDriver

Let us know if you have any further questions!

Best regards,

Claudiu Belu

Hello,

This is might not directly answer your question, but regarding the "unreachable network error", the symptoms you're describing sound like the VM's neutron ports were bound after the VM started.

There is a feature in nova, which basically makes nova-compute wait for Neutron vif plug events before starting the VMs. This ensures that the VMs neutron ports and security groups are already processed and bound, ensuring that the VM will have network connectivity. The config option is called vif_plugging_timeout [1]. There is also a config option calledvif_plugging_is_fatal, which will cause the VM to fail to spawn on a host, if the Neutron vif plug events did not occur during the vif_plugging_is_fatal period.

We've introduced this feature into compute-hyperv in Mitaka.

What OpenStack version are you using? What hypervisor are you using?

[1] http://docs.openstack.org/kilo/config...

Best regards,

Claudiu Belu

When i RDP to the Windows host using cloudbase web browser it very slow if i click on any icon it take time on come up and perform the action .

Please let me know how i increase the speed .

(duplicate question)

When i RDP to the Windows host using cloudbase web browser it very slow if i click on any icon it take time on come up and perform the action .

Please let me know how i increase the speed .

Hi,

I notice when using freerdp to log in to a Windows 2012 R2 server that the username and password are remembered between sessions. Is there a way to force freerdp to require that the user retype the username and password?

(duplicate question)

I notice that when I use FreeRDP to connect to Windows Server 2012 and subsequently log off, that when I go back to the FreeRDP login screen that it retains my credentials.

Is there a way to force FreeRDP to blank out the User ID and password fields so they need to be re-entered?

Hello,

From what I can see in the trace, it seems that there are some configurations missing from the neutron section of the Hyper-V compute node's nova.conf file, in particular, configurations regarding keytone authentication.

Our Hyper-V Nova compute installer already takes care of such configurations.

Also, make sure that you put traces like this into http://paste.openstack.org . This will make reading traces / logs a lot easier. [1] https://github.com/cloudbase/hyperv-n...

Best regards,

Claudiu Belu

Hello,

1. The driver was developed and tested under the Kilo release of OpenStack.

2. Devstack is not mandatory.

Please do keep in mind that the VirtualBoxDriver is meant for development only.

Best regards,

Claudiu Belu

Hello,

The article you've linked is already linking to the latest stable release [1].

[1] https://www.cloudbase.it/downloads/Fr...

Best regards,

Claudiu Belu

Hello,

No, it is not possible, for many possible reasons. In nova, you cannot simply live / cold migrate across hypervisors. Plus, there are many other things to consider, like adding / removing certain drivers (VirtIO, Linux Integration Services, etc.).

The easiest approach to this would be using Coriolis [1], which will help you migrate your VMs accross hypervisors, and to / from public clouds like Azure, AWS, etc. Not to mention that it has integration with Keystone, which means that it'll magically fit in your OpenStack deployment.

[1] https://cloudbase.it/coriolis/

Best regards,

Claudiu Belu

Hello,

FreeRDP's / FreeRDP-WebConnect's performance has increased in the meanwhile. Download the latest stable version and try it out.

Best regards,

Claudiu Belu

Hello,

Yes, it is possible. Please see more details about Coriolis [1]

[1] https://cloudbase.it/coriolis/

Best regards,

Claudiu Belu

Hello,

The trace you've posted is not the cause of your problem (but the source of it has been fixed).

It seems that there is a misconfiguration in your environment. You should take a look at the Hyper-V Neutron Agent guide [1] for debugging networking issues, but my guess is that you have not configured Neutron to use the hyperv mechanism_driver. More details in the article.

[1] https://cloudbase.it/neutron-hyper-v-...

Best regards,

Claudiu Belu

Hello,

In order to bind Neutron ports on Hyper-V, make sure you have networking-hyperv installed on your Neutron controller node (for liberty, use 1.0.4: pip install networking-hyperv==1.0.4). Afterwards, make sure to configure your Neutron server to use the hyperv mechanism_driver, by adding it to the mechanism_drivers config option in /etc/neutron/plugins/ml2/ml2_conf.ini. You should have something like: mechanism_drivers=openvswitch,hyperv. You can have any other mechanism drivers in the list.

For more details and more help in setting up and debugging any networking issues, please follow the article:

[1] https://cloudbase.it/neutron-hyper-v-...

Best regards,

Claudiu Belu