cpopa's profile - activity

Hello,

It does, but the code is not released yet, being part of 0.9.9 (https://github.com/stackforge/cloudba...)

We're trying to release it pretty soon, in the following week or so.

Thank you.

Hi HD. I tried to debug this, but unfortunately I'm not able to reproduce it. I got the following log using the stable cloudbaseinit and the official Windows 10 release: http://paste.openstack.org/show/406901/. The hostname changes and it's persistent across restarts.

Hi. Could you provide the cloudbaseinit's logs? You can find them in C:\Program Files(x86)\Cloudbase Solutions\Cloudbase-init\logs.

The password can be injected, but it will be in plain text. You'll have to use the password-less login mechanism if you want to prevent that. We put one of our engineers to work on a new cloud-config plugin for changing the hostname through userdata, I'll keep you informed on its progress.

Hi, The certificate passed through admin_cert is not used for encrypting the admin pass, unfortunately, but for having password-less logins. See this article for a more detailed explanation http://www.cloudbase.it/windows-without-passwords-in-openstack/. Regarding your problem with the hostname key, you're right, the metadata options can't be overridden by the user at the moment. Would it help you if we'll add the same operation as a cloud-config plugin (`set_hostname: your_desired_hostname` for instance) or a mechanism for overriding metadata values from the meta subdictionary? We'll try to push the documentation this week on http://review.openstack.org, we'll keep you informed when that will happen.

Hi. We plan to have a first good documentation on readthedocs in about one week or two. For your current question, probably you're interested in the "hostname" key name. In the mean time, if you have any question, don't hesitate to ask it here.

Hi. Could you post the part of the Heat template where the actual powershell script is? Also, it seems you are using a really old cloudbase-init version, consider using the latest version.

FYI, we have VFAT ConfigDrive support since march.

Hi.

The reason is that cloudbase-init takes a while to load the metadata service, by trying to "load" one of the supported metadata service until the first one responds. As deduced from your configuration file, you are using HTTP service by default, which takes a little time to get loaded, just waiting a couple of extra minutes should be enough.

Do you have the cloudbase-init log? It will help us if there's any problem with the feature.

VFAT support landed in cloudbase-init last night: https://github.com/stackforge/cloudbase-init/commit/2026ee8e0f766f91cf62904ceca3de7382eea787.

Hi. Could you be a little more specific, please? The metadata is retrieved from the HTTP transport here: https://github.com/stackforge/cloudba.... Basically, there are some methods for manipulating it and they are doing API calls under the hood.

It will happen most likely this week.

Just a heads up, the patch is ready for review https://review.openstack.org/#/c/158249/. It will probably need some modifications in the installer to go along with it.

Hello. It seems that you are using a very old cloudbaseinit since the function cloudbaseinit.plugins.windows.userdata.UserDataPlugin._processuserdata isn't called like that anymore since january 2014. Using a newer installer should fix the problem with your Powershell script.