New Question

lpetrut's profile - activity

2020-02-07 09:48:17 +0300 commented answer windows image for kubevirt

You can use qemu-img to retrieve the interal image size. The actual file size can be much lower when dealing with dynami

2020-02-04 09:31:16 +0300 commented answer FreeRDP Webconnect and Openstack Train

It's useful to have both API and hypervisor side logs so that we can correlate them. I'd be interested to see when the r

2020-02-03 17:04:59 +0300 answered a question FreeRDP Webconnect and Openstack Train

Hi, I suggest enabling debug logging and follow the request id. You should be able to see the following in your nova co

2020-01-27 14:29:20 +0300 answered a question Storage migration options for Cinder SMB driver

One option would be to use the "manage volume" feature. You'd request Cinder to "unmanage" it, manually move it and then

2020-01-14 18:15:40 +0300 edited answer automatic stop action for hyper-v

Sure, just set the following in nova.conf: [hyperv] instance_automatic_shutdown = true Note that changing this option

2020-01-14 18:15:17 +0300 edited answer automatic stop action for hyper-v

Sure, just set the following: [hyperv] instance_automatic_shutdown = true Note that changing this option won't affect

2020-01-14 18:13:57 +0300 answered a question automatic stop action for hyper-v

Sure, just set the following: [hyperv] instanceautomaticshutdown = true Note that changing this option won't affect al

2020-01-08 10:09:29 +0300 answered a question Glance to Cinder optimization

Hi, Not at the moment. There's been an inline TODO since forever but it never got implemented: https://github.com/opens

2019-11-24 16:49:05 +0300 commented answer OpenV switch neutron error

Judging by your error message, looks like ovsdb-monitor is still connecting to that "pipe" instead of the 6640 tcp port.

2019-11-24 16:47:52 +0300 commented answer OpenV switch neutron error

Judging by your error message, looks like ovsdb-monitor is still connecting to that "pipe" instead of the 6640 tcp port.

2019-11-24 16:46:22 +0300 commented answer OpenV switch neutron error

Hmm, recent Windows Sever versions include ovsdb binaries that may not work properly with neutron. One idea would be to

2019-11-21 15:32:30 +0300 edited answer OpenV switch neutron error

Hi, ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the fol

2019-11-21 15:14:29 +0300 answered a question OpenV switch neutron error

Hi, ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the fol

2019-11-18 17:30:32 +0300 commented answer Openstack nic not getting attached to vm switch

Small update: networking-hyperv 7.0.1 has been released. In case you want to stick to the current configuration, you may

2019-11-14 19:46:31 +0300 answered a question VM creating without default virtual switch

The bad news is that it's a networking-hyperv bug, the good news is that I sent a fix and we'll soon have updated MSIs.

2019-11-14 19:44:37 +0300 commented answer Openstack nic not getting attached to vm switch

Thanks for the logs, those helped me find the issue. I sent a fix and by next week we should have updated MSIs as well a

2019-11-14 15:05:20 +0300 commented question VM creating without default virtual switch

About Data Center edition, it's definitely supported. In fact, it's required by S2D. It's most probably a configuration

2019-11-14 12:47:45 +0300 commented question VM creating without default virtual switch

If the issue doesn't come up, feel free to contact us at https://cloudbase.it/about/#contact, we may schedule a call and

2019-11-14 12:45:39 +0300 commented question VM creating without default virtual switch

Getting back to your error, I suggest checking the neutron api logs (or neutron server, some deployment tools use a diff

2019-11-14 12:43:42 +0300 commented question VM creating without default virtual switch

Our Openstack services are compatible with all Windows Server editions starting with WS 2012 R2.

2019-11-13 15:24:23 +0300 commented question VM creating without default virtual switch

There seems to be something wrong with the neutron server, which could not provide the port details. Can you please chec

2019-11-12 18:00:21 +0300 commented question VM creating without default virtual switch

I suggest enabling debug mode for the neutron services (hyper-v as well as neutron server) and check the logs. You may s

2019-11-12 17:59:10 +0300 commented answer Openstack nic not getting attached to vm switch

I suggest enabling debug mode for the neutron services (hyper-v as well as neutron server) and check the logs. You may s

2019-11-11 13:00:32 +0300 commented question VM creating without default virtual switch

Just to make sure, your hyper-v switch is named "hyperv", right? Also, don't forget to install networking-hyperv on your

2019-11-11 10:26:08 +0300 commented question VM creating without default virtual switch

Which neutron agent are you using ("neutron-ovs-agent" or "neutron-hyperv-agent")? What network type are you using (flat

2019-11-04 11:59:37 +0300 answered a question Openstack nic not getting attached to vm switch

Hi, Make sure to also enable the hyperv ml2 plugin as described here: https://compute-hyperv.readthedocs.io/en/latest/i

2019-09-09 11:33:26 +0300 commented answer neutron-ovs-cleanup.exe

No, that's the right way to do it. neutron-ovs-cleanup would do the same thing.

2019-09-03 09:18:44 +0300 edited answer neutron-ovs-cleanup.exe

Hi, This was fixed in Queens, Mitaka is no longer supported. We were considering configuring neutron-ovs-cleanup as a N

2019-09-03 09:17:20 +0300 answered a question neutron-ovs-cleanup.exe

Hi, This was fixed in Queens, Mitaka is no longer supported. We were considering configuring neutron-ovs-cleanup as a N

2019-07-10 11:10:54 +0300 commented answer ServiceTooOld

I can also provide some beta MSIs. Those use the upstream stable packages, tested by our CIs. Usually we do a lot more t

2019-07-10 11:10:34 +0300 commented answer ServiceTooOld

About the Stein MSI release date, I can't provide a date, unfortunately. It could take a couple of weeks or a couple of

2019-07-10 11:10:14 +0300 commented answer ServiceTooOld

It would work as Nova is backwards compatible in order to allow rolling upgrades. Some features may not be available whe

2019-07-10 09:18:41 +0300 answered a question ServiceTooOld

Hi, Nova doesn't allow you to add compute nodes using older versions than the rest of the deployment. I think you're us

2019-07-02 13:35:35 +0300 edited answer v-magine and OpenStack Windows Storage

Hi, There should be a Linux VM that acts as your Openstack controller. I think you should be able to access that VM and

2019-07-02 13:35:12 +0300 edited answer v-magine and OpenStack Windows Storage

Hi, There should be a Linux VM that acts as your Openstack controller. I think you should be able to access that VM and

2019-07-02 13:34:00 +0300 answered a question v-magine and OpenStack Windows Storage

There should be a Linux VM that acts as your Openstack controller. I think you should be able to access that VM and fetc

2019-06-21 11:23:33 +0300 commented answer Random - Truncating host name for Netbios compatibility

You may use pastebin if the log is not too large, otherwise some file sharing service such as dropbox, onedrive, etc.

2019-06-07 09:08:40 +0300 commented answer Exception during mounting need more than 0 values to unpack

Oh, one minor update about my previous comment. It's Cinder that you're currently debugging, not Nova. Instead of lookin

2019-06-06 10:58:19 +0300 commented answer Exception during mounting need more than 0 values to unpack

Just do a pip install eventlet==0.22.0. Make sure that you're using the correct Python environment. Here's a small snipp

2019-06-06 10:56:22 +0300 commented answer Exception during mounting need more than 0 values to unpack

Just do a pip install eventlet==0.22.0. Make sure that you're using the correct Python environment. Here's a small snipp

2019-06-05 09:56:13 +0300 commented answer Exception during mounting need more than 0 values to unpack

Feel free to use eventlet 0.25.0 if that works for you though.

2019-06-05 09:55:52 +0300 commented answer Exception during mounting need more than 0 values to unpack

There's a list of Openstack requirement versions that gets tested by the CIs: https://github.com/openstack/requirements/

2019-06-05 09:53:28 +0300 commented answer Exception during mounting need more than 0 values to unpack

I got that wrong, sorry about that. The host name is clusterhfc.kcs.cloud. Did anything change after upgrading eventlet

2019-06-04 09:22:28 +0300 commented answer Exception during mounting need more than 0 values to unpack

To bring some context, eventlet embeds a copy of dnspython, which is used to resolve host names as opposed to using nati

2019-06-04 09:21:00 +0300 commented answer Exception during mounting need more than 0 values to unpack

To bring some context, eventlet embeds a copy of dnspython, which is used to resolve host name as opposed to using nativ

2019-06-04 09:18:13 +0300 commented answer Exception during mounting need more than 0 values to unpack

That's great, that helps us pinpoint the issue. Cinder fails to resolve the share host name (HYPERVMEX2). Can you double

2019-06-03 20:54:05 +0300 commented answer Exception during mounting need more than 0 values to unpack

I don't like asking this, but the easiest way to get straight to the error would be to make a minor change in the code h

2019-06-03 20:47:36 +0300 commented answer Exception during mounting need more than 0 values to unpack

Ok, so debug logging is enabled and the driver seems properly configured. Can you please paste the log output that shows

2019-06-03 16:33:18 +0300 answered a question Cinder stopped working with hyper-v

This seems to be a duplicate of https://ask.cloudbase.it/question/3023/exception-during-mounting-need-more-than-0-values

2019-06-03 15:56:34 +0300 edited answer Exception during mounting need more than 0 values to unpack

Hi, That's quite odd. Could you please provide more details about the environment? Which OpenStack release are you usin